yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
Don't think so. I believe the Touch HD + Dream have same SD hardware.

We need a hardware sheet for that.
[Tilt, TyTN II, MDA Vario III Android Development] jcahill84:
Has anyone thought of contacting the android OSC to work on the driver? There's a googler over there named San Mehat that works on the MSM MMC driver. His last few changes were mainly cleanup, but there might be some promise. The URL to his Gerret shenanigans is: http://review.source.android.com/user/san,,google.com and his e-mail is san@google.com.

Probably won't work... But it was worth a shot. There's a ton of other stuff to be done on top of the MMC driver being completed, but it may be nice to see if the OSC is interested in developing and official Kaiser kernel to work with android.

Maybe then we could get some work started over at the android internals thread within the Kaiser-MSM7200 context: http://groups.google.com/group/android-internals...

Anyway, keep up the good work homies.
[Tilt, TyTN II, MDA Vario III Android Development] BARIO:
Petition for SD driver on HTC?

Hi guys,

I've been quietly following this thread for a while now. I'm not a coder myself, so don't expect me to sit and code the solution to this SD driver issue :o

What I think is the following: I guess that google has interest in having as many Android systems out, and considering how many kaiser were sold (don't know the figure but I guess a lot...), I believe it could make sense doing some lobbying and organize an online petition asking google to write a working SD driver in the same fashion as the online petition for the 3D drivers to HTC?

Something similar has been done, (with no success) here:

http://www.htcclassaction.org/

and here:

http://www.petitiononline.com/tytn2vid/

Now, while

HTC has a big interest in not releasing

3D Drivers for a phone that has already sold many units (like Kaiser) but to release new models with 3D Support and sell some more,

Google probably has more interest in having Android ported to as many systems as possible

.

Therefore, I believe that if our scream is loud enough to reach Google's Product Managers, maybe something could happen.

The htcclassaction.org site is probably a good place to start, and maybe we could ask them to create a section about Android and the SD driver? I guess that if Android 1.0 can be properly ported to Kaiser, than the whole 3D driver discussion will start looking different...

Again, while I can't code, I guess I can write emails, so if you guys believe that my idea makes sense, I could try and get in touch with the htcclassaction.org people and see if we can merge our two quests.

Well, these are my 50 cents for today :-)

Best regards to all of you who believe in open source OS!
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
So I decided I'd give android a shot for giggles and to see just how buggy it is. For the record, I'm running Dutty's Hybrid 6.1 (I'll check the version if there's enough interest).

I know a lot of people are having issues just getting haret to launch linux consistently.

I had the most consistent success when using a couple tricks.

1. Launch haret.exe

2. Someone mentioned pressing Check for Network Connection button before clicking run.

-haret will continue to check for network (never completes in my experience)

3. Click Run even while it continues to check for network connection.

4. When the loading bar has passed 50-75% I clicked softkey keyboard icon to bring it up.

When using these steps I had much success just booting into Android.

Doing just steps 1 and 2, I noticed that haret would finish loading (100%) but would just lock up. More often than not tapping the softkey keyboard contributed to android booting fully.

For the record, Android is quite buggy. Launching the SMS application it nearly right away. The force quit dialog box opened and I selected force quit which ultimately caused Android to lock up definitively.

Also launching a myriad of other options or programs, like developers tools, or Android (icon of a clock), caused Android to lock up irrecoverably.

Anyway, I just thought I'd share my experiences with everyone else. If there's anything I can do to be of assistance (lacking much coding experience I doubt it) let me know.

If anyone has any suggestions as to anything they'd like me to try in Android, drop me a line and I can give it a shot.
[Tilt, TyTN II, MDA Vario III Android Development] cboy007:
that sounds like a good idea, but i'm wondering if just asking google would suffice...depending on how long it takes to write an SD driver. i feel like they would be a generous enough company that if they saw a thread like this where TONS of people are interested in getting THEIR os on the same phone, then google might just pitch in and have someone write the SD driver.

i'd say start with that...just pointing them here and asking them for assistance before doing something that would take more work and probably take longer to take effect.
[Tilt, TyTN II, MDA Vario III Android Development] BARIO:
I believe that the way you ask is the thing that makes the difference...

A) One thing is pointing a busy manager to a 1500-posts messy thread talking about 200 different issues...

B) A different thing is creating a petition called "We need an SD driver for HTC-Kaiser to fully port Android" and as soon as it gets to 5000 signatures (not at all impossible) you point this web-phenomenon out to some relevant audience... no? :eek:
[Tilt, TyTN II, MDA Vario III Android Development] veyron3:
Engadget

What if we could get someone at Engadget to do a quick write up about this, like with the Kaiser class action.org. Someone is bound to see it that could help. Just a thought
[Tilt, TyTN II, MDA Vario III Android Development] Akya:
isnt there a google forum for android? anyone a member? I would think someone there might know something about writing the sd driver? or has that been tried?

there is a bunch of info on the nand in the kaiser i just googled it. its even in the wiki i dont know what it means but im sure it could help porting?

i found this with a search

http://www.datasheetcatalog.org/datasheet/SamsungElectronic/mXxqvsw.pdf

and also

http://wiki.xda-developers.com/index.php?pagename=KaiserNAND

but this is probably already well known too isnt it?
[Tilt, TyTN II, MDA Vario III Android Development] mikemorris:
AKYA i think this is what you are looking for.

http://groups.google.com/group/android-developers

That is the developer forum for Android.
[Tilt, TyTN II, MDA Vario III Android Development] paede:
Another hint:

Telnet Root Access to the G1:

http://xdaforums.com/showthread.php?p=2864346
[Tilt, TyTN II, MDA Vario III Android Development] segy2g:
Can we stick to the issue at hand?

I'd think the issue at hand did not involve Nigeria? Maybe we should stick with what is in hand rather than tossing mud around.....
[Tilt, TyTN II, MDA Vario III Android Development] cboy007:
wow. your first post and that has already been discussed like 50 pages back. let's not bring that whole thing up again.
[Tilt, TyTN II, MDA Vario III Android Development] icewhitenewyear:
I completely agree with you, if you contact me... we could get something like this started.

I think that if we get enough people involved (which i think there would be) then it would ABSOLUTELY attract google, they are all about the mass amounts no matter if they are making money on it or not, and they are all about open-source.

Let me Know, If anyone else would like to be involved with this sned me a message and im sure we can start something out.

You can also email me at icewhitenewyear@hotmail.com

Thanks.
[Tilt, TyTN II, MDA Vario III Android Development] shadowline:
I know I am just one of many, but I would sign a petition for google to work on android for our kaisers. Or at least for them to lend a helping hand.
[Tilt, TyTN II, MDA Vario III Android Development] Darius_:
I want this android working now! on my kaiser. so where to sign? :D

anyway nice progress so far and looking forward to your further codding...
[Tilt, TyTN II, MDA Vario III Android Development] milas:
While posting on the the android-porting mailing list asking about the DMA errors with the sdcc driver could elicit some results, I don't think there is any point in creating a petition.

As mentioned, internet petitions are very ineffective. Also, while Google obviously wants Android on as many devices as possible, they have no real incentive to develop SD drivers for the Kaiser, as it is using a now outdated SD controller that they likely won't have to deal with in any new devices. Backporting is not their concern.
[Tilt, TyTN II, MDA Vario III Android Development] milas:
Sorry, I'm an idiot.
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
I posted, but not with more details. It would be great if someone with more knowledge about the exact problem could contact them and ask especifically what we need. Seems the experts are away at the moment : )

http://groups.google.com/group/android-kernel/browse_thread/thread/435ce9ade43ab538
[Tilt, TyTN II, MDA Vario III Android Development] milas:
I'm trying to poke at the SD issues right now, but every time I boot, I get to the terminal as expected since it tries to mount everything before the SD card is detected. Then the SD card gets detected fine and I can browse around/manipulate files on it.

However, when I run ./init again to try and get everything set up, I get:

Welcome to Vogue Linux
mount: mounting proc on /proc failed: Device or resource busy
mount: mounting sys on /sys failed: Device or resource busy
mount: mounting /dev/block/loop0 on /data failed: Invalid argument
Failed
Failed to mount /data
/bin/sh: can't access tty; job control turned off

I'm using what I think is the latest initrd.gz from corvus (I believe he posted it...there are about 750 useless posts between here and there so I cant' see it)

I'm not sure why it's failed, I have data.img and system.img in the SD root, which is where it's looking for them. I get the same error if I manually issue the losetup/mount commands.
[Tilt, TyTN II, MDA Vario III Android Development] BARIO:
Yo guys,

I disagree on this, for several reasons:

I guess you can't tell a lot about how obsolete is the kaiser DMA controller and how similar will be the controllers used in the coming phones. Giving the success of Kaiser it wouldn't surprise me that they a similar/compatible hw setup over and over again.

If fixing an SD driver takes them 1 man/month of work, and in return they get 500k happy supporters, I guess it's a great deal for them!

Once again, this thread is probably the only place on the web to discuss about Android on Kaiser: it's a mess and it would discourage anyone who's not personally and deeply interested in the subject. Making a petition or web page that has some audience could do nothing but help the cause anyway...if not google, someone else might notice it.

To the guy who wrote me before: I'll send an email to you later on, thanks for support! :cool:
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Do you really still not have the SD driver working? It works perfectly on Vogue and that's essentially the same hardware. Have you tried tracing the gpio alternate config registers (non shadowed gpio1 base + 0x20,24 and gpio2 base +0x410,414) to see if it does anything special. Do you have all the same delays on initialisation and the same .config options for mmc. If somebody wants to lend me a kaiser, I'll have it running in no time (along with power collapse and audio!).
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
growing user base

I'm from Brazil, and I live in UK for almost four years. Although I have my kaiser for more than 6 months, just now it is been launched in Brazil, which is a very open source supporting and active community. I expect then that the number of kaisers will grow considerably, and hopefully a lot of support for linux/android to run on it!!

Dzo: if you were closer, I would definitelly take it to you personally!!! But maybe talking to someone that has a bit more of expertise than me, you could together try some conferencing and find a solution for the current problems in the sd drive?

regards

Emerson
[Tilt, TyTN II, MDA Vario III Android Development] ducamie:
someone lend a kaiser to dzo, stat.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Also, you know if its just dma that's the problem, the sdcc driver has a pio only mode.
[Tilt, TyTN II, MDA Vario III Android Development] milas:
Okay, I found out the issue with my Invalid Arguments was that it did not like the system and data img files I was using (from corvus' kaiserrootfs.rar). When I switched to using dzo's data.img and system.img with a Kaiser initrd, after hitting the terminal from the SD card not being detected, I then run ./init, it mounts happily, I get the A N D R O I D display, it does some modem set up stuff, then it goes into a black screen with a small white line the upper left hand corner and sits here frozen.

Nowhere in here did I get DMA errors..but obviously it is frozen which doesn't really help.
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
I was reading the Port Status and was wondering if anyone has done any in-depth testing to see what works and what is broken.

I myself, was playing around with Android and discovered a few things.

When in a call, the default source is the speakerphone and the source is not able to be switched.

SMS locks up often, but when working, does not actually send SMS messages despite the SENT message.

Also, there's a note on android on htc port status page that says that the screen calibration issues are fixed however I'm still having problems with the sensitivity and accuracy, especially/mostly/only in the dialer.

----------------------

Does anyone know if there is an area to access settings or if that is not implemented until .9 or 1.0? For example, the bluetooth/pairing/radio settings, volume, wallpaper, etc.

I'm still unable to access the developer settings section.

Overall, very buggy but more stable and more functional than I expected.
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
The issues you guys are having are still with version .8?

Also, what is the plan of attack? Are you guys working out the bugs with .8 and moving on to .9 and the 1.0 or what?

Do we have a compendium of bugs that we're currently working on other than the SD driver and the ones that are listed at http://www.androidonhtc.com/port_status ?

Thanks again for all your hard work guys.
[Tilt, TyTN II, MDA Vario III Android Development] infernix:
There are T-Mobile branded kaisers for sale on marktplaats.nl (a dutch ebay) for 150 to 250 euros.

If a few people are interested in making a small investment, I'll have no problem buying one and sending it off to dzo.

Who's interested in participating?
[Tilt, TyTN II, MDA Vario III Android Development] easedrop:
Is anyone actually using .8 on their Kaiser more than they are using wm or too many bugs?
[Tilt, TyTN II, MDA Vario III Android Development] SharpieMarker:
Too buggy. Impossible.
[Tilt, TyTN II, MDA Vario III Android Development] tone007:
Kaiser will never run Android satisfactorily.

Buy a G1.
[Tilt, TyTN II, MDA Vario III Android Development] dvkwong:
Kaiser for DZO

yep I would not mind donating sign me up, how do we do this?
[Tilt, TyTN II, MDA Vario III Android Development] ducamie:
not to fill this thread with junk, but thats simply not true. look at the vogue - its more than usable and android has barely been out a couple weeks.
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
True True, also if you see the other chinees phones with Android running fully on them.
[Tilt, TyTN II, MDA Vario III Android Development] infernix:
first i need to know how many people will participate.

Then i'll go and buy the cheapest kaiser i can find. i'll find out shipping costs to new zealand and then i know the total cost.

divide total cost with amount of participants = cost of getting dzo a kaiser for development.

I've seen an add for a working kaiser with a crack in the display for 100 euros, and refurbished or barely used kaisers for 150-200 euros.

Shipping to NZ would amount to 25 euros.

So lets say total cost = 200 euros. 10 participants. that would be 200 euros divided by 10+1 (me) = 18 euros.

I'm sure you can all do the math on how much we can save if we get many people aboard.

If interested, please send me a PM with your intention and amount you are willing to pay.

Current participants in funding for buying dzo a kaiser for development:

- eezak for max 20 euros

- BARIO

- echofloripa

- MooNWalker

- infernix :)
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
ok so work kept me from checking the forums. infernix told me about dzo's offer to help us with the kernel problems.

imo it would be good if somebody could send a kaiser to dzo. I would really like to lend him mine, but I use it on a daily basis now and a raphael as replacement is too expensive for me at this point.

edit: I guess there are some people out there who keep a spare one and have interest in linux/android on their device.
[Tilt, TyTN II, MDA Vario III Android Development] BARIO:
I am In!

hi everybody
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
count on me too!!!!
[Tilt, TyTN II, MDA Vario III Android Development] BARIO:
This post is a mess... :-|
[Tilt, TyTN II, MDA Vario III Android Development] BARIO:
Guys,

I too the liberty to write something here:

http://www.androidonhtc.com/financing_the_development

I don't even know who owns the site, but I guess the owner is happy of my initiative as well as the people writing in this thread.

(All I did was registering and I could create/edit everywhere on the site...I guess you all could do the same).

Once again: this thread is a mess. If we start collecting the info in a more systematic way, and arrange them in a user friendly way, I guess the community and work done would grow exponentially.

Greetz!
[Tilt, TyTN II, MDA Vario III Android Development] MooNWalker:
Count me in.
[Tilt, TyTN II, MDA Vario III Android Development] blogzter:
how is still able to keep track of this post?
[Tilt, TyTN II, MDA Vario III Android Development] grungysquash:
I'm a kiwi based in sydney with a Tytn ii - cracked screen - yours free if u need it. - PM me and I'll ship it over.
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
I've had a few offers of Kaisers but this sounds the easiest, I'll pm you and let the forum know how things are going. Thanks.
[Tilt, TyTN II, MDA Vario III Android Development] catchfire:
grungysquash and dzo..... two thumbs up :D
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
I'm glad a solution was found that quickly. thanks to everybody who offered to borrow their devices and to dzo for saving this 'project' :)

dzo: I just tried looking at the alternate config registers as you proposed but I'm not sure if I use the correct base. according to http://wiki.xda-developers.com/index.php?pagename=KaiserMemoryMap , MSM_GPIO1, DEX is at 0xa9200000 .

I ran "addlist mmutrace 0xa9200000 0x24" and "addlist mmutrace 0xa9300000 0x24" and ran wirq. it looks like there's nothing useful except for the usual display refresh and touchscreen irqs. I also wrote to the SD in case that's necessary.

did I forget something? am I usin the correct bases?
[Tilt, TyTN II, MDA Vario III Android Development] dzo:
Those are physical addresses, you need to give mmutrace virtual addresses, probably 0xb2b00000 and 0xb2c00000 and you need to trace the correct range.

addlist mmutrace 0xb2b00000 0x00200000

should do it, but try dump mmu 2 0xa9200000 first to find all the mappings.
[Tilt, TyTN II, MDA Vario III Android Development] slovoflud:
oh, man i'm so happy there's some movement on the topic!

i say we all should meet up!

:)
[Tilt, TyTN II, MDA Vario III Android Development] o2xdaexec:
just a idea

dont shoot me down in flames guys

i think the thread needs to be a bit tidyer,on the kaiser main page we have main links...

genral,software,accs and rom section can we have a android section too it would make it alot better.and put a skicky on it noteing which android is working and which dont yet,and what android is.or links to like the wiki
[Tilt, TyTN II, MDA Vario III Android Development] noodlesgc:
Hey guys, thanks for all your work getting the android ported. If I understand correctly, In order to run the android (when it works ok) it has to be run off of a SD card because of size. Is this true?

I have 113mb of storage on my main drive.
[Tilt, TyTN II, MDA Vario III Android Development] cyberdrakula:
Nice. I have been following this topic for a while and nice to see more contributors.
[Tilt, TyTN II, MDA Vario III Android Development] xmoo:
I will also do 10 euros. Hope it's not paypall.....
[Tilt, TyTN II, MDA Vario III Android Development] echofloripa:
well well, it's space on the mobile... not on your computer :)
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
this sounds to me as if there's already enough devices available..
[Tilt, TyTN II, MDA Vario III Android Development] LOTG:
VMWare to the rescue?

VMWare MVP
[Tilt, TyTN II, MDA Vario III Android Development] Speaking_On:
Likely not any time soon. Reading through the press release, it seems pretty vague about availability: "to bring to the mobile phone market" is language that says "we've started talking" not "we've started shipping."

It's also not clear from that blurb whether they see this as something that would be shipped with the phone or something that could be done post-facto. Some of the virtualization solutions out there are "bare metal", so that they replace the underlying OS. Others have a full OS, a VM, then another full OS. Given the limitations of these devices, the latter would require some interesting changes to the current way of doing things.
[Tilt, TyTN II, MDA Vario III Android Development] Bimboy:
I prefer the current method of booting via haret into Andoid, than having VMWare running on the OS, and allowing you to emulate another OS over it. That seems very inefficient.
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
ok, didn't use haret for anything but booting in a while...

so 0xb2b00000 is mapped to 0xa9200000 but also b2b00000. I have seen that when we were working on the kaiser-smd. what's the use of that "double-mapping"?

btw, we are currently sorting a unified branch for most of the device: kaiser polaris nike (7200) raphael diamond (7201a) and their *800 versions (7501A), everything on the base of the g1 code. hope we can add the vogue titan etc too. I will notify you when we pushed it to the git

edit: it will go to the htc-msm-2.6.25 branch on linuxtogo where raphael and diamond reside currently
[Tilt, TyTN II, MDA Vario III Android Development] dcordes:
I doubt there are kaiser boards with the 7201a. are you ure it's not just a different rom version that causes wince to tell you it was?

can you boot the kaiser bootkit kernels on your 7201a kaiser ?
[Tilt, TyTN II, MDA Vario III Android Development] dalingrin:
its not 7201a its just 7201 as far as I know.

The reason for 7201 vs 7200 on kaiser is because of the lawsuit with broadcom. Essentially the same processor just tweaked something to get around lawsuit is what I heard.
[Tilt, TyTN II, MDA Vario III Android Development] Speaking_On:
You're right; I was wrong. Re-checking, it says "7201-400MHZ", not 7201a. Sorry for the error.
[Tilt, TyTN II, MDA Vario III Android Development] djmp89:
Interesting story on getting Debian on the G1....would love to get debain on my kaiser running Gnome Mobile!

http://www.saurik.com/id/10:D