tag:blogger.com,1999:blog-8953969431955539216.post7619211977946392198..comments2023-09-26T10:48:06.099+01:00Comments on Paul's Blog: Axdroid 2010-08-30Paul Burtonhttp://www.blogger.com/profile/14101828631122688548noreply@blogger.comBlogger39125tag:blogger.com,1999:blog-8953969431955539216.post-55455388481457588202011-11-28T22:12:17.420+00:002011-11-28T22:12:17.420+00:00This comment has been removed by the author.Danyhttps://www.blogger.com/profile/13567704945860801768noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-5563468832863510462011-11-28T22:10:35.210+00:002011-11-28T22:10:35.210+00:00Hi Paul!i have dell axim x50.will this droid os wo...Hi Paul!i have dell axim x50.will this droid os work on it?(CPU5520MHz,RAM64MB) thanksDanyhttps://www.blogger.com/profile/13567704945860801768noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-51552563314128158222010-09-08T15:24:40.735+01:002010-09-08T15:24:40.735+01:00I have a X51 with LennySH's WM6.0 L03 Alpha 1 ...I have a X51 with LennySH's WM6.0 L03 Alpha 1 installed. I've tried various AxDroid releases and here's what I've noticed:<br /><br />20100625: Locks up on load, gets to i2c lines and locks up<br /><br />20100801: Loads into AxDroid, screen is distorted (pre-QVGA fix)<br /><br />20100831r2: Gets to initial screen about "Loading Kernel" (before the Tux screen), then the screen progressively gets whiter and whiter with horizontal scanlines<br /><br />20100906: Loads beautifully into AxDroid, correct aspect ratio. Touchscreen positioning is way off.Unknownhttps://www.blogger.com/profile/14100461395563298971noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-23000620406998260922010-09-07T22:28:20.758+01:002010-09-07T22:28:20.758+01:00Try http://www.paulburton.eu/project/axdroid/axdro...Try http://www.paulburton.eu/project/axdroid/axdroid_20100906_rel.zip :)Paul Burtonhttps://www.blogger.com/profile/14101828631122688548noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-52419664495083838542010-09-07T22:26:06.170+01:002010-09-07T22:26:06.170+01:00Hi There,
I have a Dell Axim x50v, but when I boo...Hi There,<br /><br />I have a Dell Axim x50v, but when I boot axdroid_20100831_rel2.zip up, the touchscreen doesn't work.<br /><br />lcd_detect shows:<br /><br />Cached: 2<br />FPGA: 3.7" Sharp (0)<br />AximSDK: 3.7" TFT Sharp<br /><br />Hope that helps?!<br />When is the fix planned to be released? Can't wait to start using it!! :D<br /><br />Thanks,<br />TomTom Medhursthttps://www.blogger.com/profile/00417661263384409665noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-5374368686111653702010-09-07T10:22:12.874+01:002010-09-07T10:22:12.874+01:00I've a dell axim x51v
that's the output of...I've a dell axim x51v<br />that's the output of the tool:<br /><br />Cached: 2<br />FPGA: 3.7" Sharp (0)<br />AximSDK: 3.7 TFT SharpJorghehttps://www.blogger.com/profile/05801773779872457379noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-11402212938622386592010-09-06T18:33:50.870+01:002010-09-06T18:33:50.870+01:00Paul: Yeah go ahead and put it in the Git.
Also, ...Paul: Yeah go ahead and put it in the Git.<br /><br />Also, my X51 is slowly charging. I either need to buy a dock and not charge through the sync cable or I need to buy a new battery. If anyone has an extra dock, email me at max@maxfierke.comAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-48693454592622349072010-09-06T08:08:47.098+01:002010-09-06T08:08:47.098+01:00Max: It's prettier than my attempt at graphics...Max: It's prettier than my attempt at graphics :) Is it OK to put it in Git?<br /><br />Natestera: Fantastic, LCD fixed :D One thing is that you're running a debug build (or a test build, I didn't check which that is) which will be a little slower than a release build. Although, don't expect the release to be speedy just yet :) SD is likely a source of slowness, all I can suggest is use the fastest card you have because it does make a difference. After work today I plan to spend some time looking at WiFi, and then the next major things on my list are the internal flash (twice, since X50 & X51 are different here) and power management.Paul Burtonhttps://www.blogger.com/profile/14101828631122688548noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-22442596492968258032010-09-06T04:29:26.645+01:002010-09-06T04:29:26.645+01:00It booted and finally get the UI...wow!!
It is v...It booted and finally get the UI...wow!! <br /><br />It is veeeerrrryyy slooooow, but I guess that could be the SD card causing that? I am quite impressed! Any tips on speeding it up a bit? Should I reformat the card completely? What settings do you recommend when reformatting FAT?Natesterahttps://www.blogger.com/profile/15079187178437996148noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-20359636903435600152010-09-06T02:43:16.644+01:002010-09-06T02:43:16.644+01:00Unrelated note:
I made a new boot logo for fun. T...Unrelated note:<br /><br />I made a new boot logo for fun. Tell me what you think:<br /><br />http://maxfierke.com/graphicdesign/axdroid_bootlogoVGA.png<br /><br />http://maxfierke.com/graphicdesign/axdroid_bootlogoQVGA.pngAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-56027972855027138342010-09-05T22:53:34.646+01:002010-09-05T22:53:34.646+01:00Hah, I wouldn't recommend reading it front to ...Hah, I wouldn't recommend reading it front to back :P It's really useful when you spot a memory access to a register area though, as you can dump the WinCE memory map with HaRET, find the physical address and then look that up in the PXA manual.Paul Burtonhttps://www.blogger.com/profile/14101828631122688548noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-49546871701017784922010-09-05T04:19:34.103+01:002010-09-05T04:19:34.103+01:00After looking at the PXA270 developer's manual...After looking at the PXA270 developer's manual it does seem that the pixclock value should be 134615. <br /><br />To be honest I had no knowledge of the PXA270 manual so I wasn't exactly sure what the LCCR0 and LCCR3 values meant, except that HaRET told me what they should be.<br /><br />I really need to learn more about the PXA270. It's time to read all 1242 pages! :)Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-73797063921752170262010-09-05T02:48:23.467+01:002010-09-05T02:48:23.467+01:00My X51 is refusing to charge (I think I may need a...My X51 is refusing to charge (I think I may need a new battery) but I've compiled a debug build straight from Git:<br /><br />http://axdroid.co.cc/builds/debug/axdroid_20100904_dbg.zip<br /><br />Can anyone else with an X51 test this build and post if Android loads up successfully?Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-45314424008932256412010-09-04T22:31:03.934+01:002010-09-04T22:31:03.934+01:00Max: take a look at mach-pxa/include/mach/pxafb.h ...Max: take a look at mach-pxa/include/mach/pxafb.h and the PXA270 developers manual if you want to see what the value means, and which bits should be left out.<br /><br />I adjusted the lccr0 value earlier today, it is using the macros but matches your value (and that of the X50/type 1). Are you absolutely sure the pixclock needs to be that? In lccr3 the divider is set to 7 which is (pretty much) exactly the ratio between your pixclock and that of everything else. Does the current code in git definitely not work on the X51? (Please, try it before saying no)Paul Burtonhttps://www.blogger.com/profile/14101828631122688548noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-5370418113531996522010-09-04T22:15:15.993+01:002010-09-04T22:15:15.993+01:00Natestera: X51 support is broken right now.
Paul:...Natestera: X51 support is broken right now.<br /><br />Paul: My fixes seem to have disappeared from the Git repo. For X51 support, the QVGA pixclock needs to be 19230. The lccr0 value needs to be 0x01b008f9. It could be in macros also. I don't know where the LCCR0 macros are coming from but there's probably a way for them to equal that value. The LCCR3 value needs to be 0x04f00007. The X51 will not work without these exact values.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-75170446657522855122010-09-04T05:02:06.207+01:002010-09-04T05:02:06.207+01:00Sorry, relative n00b here with an old X51. The scr...Sorry, relative n00b here with an old X51. The screen goes white and seems to stay that way after bootloader starts...<br /><br />Using a 1G SanDisk card.Natesterahttps://www.blogger.com/profile/15079187178437996148noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-81328505838562134142010-09-03T01:34:43.313+01:002010-09-03T01:34:43.313+01:00Thought I'd share a glimpse at what I've j...Thought I'd share a glimpse at what I've just been working on, this is from the kernel log on my X51v:<br /><br />[ 160.577899] Detected machine: X51v (0x11)<br /><br />and on an X50 low:<br /><br />[ 43.966928] Detected machine: X50 (0x00)<br /><br />Isn't that exciting :D It means the touchscreen should work for _everybody_ in the next build.Paul Burtonhttps://www.blogger.com/profile/14101828631122688548noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-18648506599318695452010-09-02T20:18:28.079+01:002010-09-02T20:18:28.079+01:00Jaziri: thanks, looks like the X50v has the same t...Jaziri: thanks, looks like the X50v has the same type of screen as the X51v, so I can't use that to figure out which it is (which is why the touchscreen doesn't work, X50 is hooked up differently to X51). I'll have to come up with some other way to detect which device we're running on. The handhelds.org port (which was Linux, but not Android) is what Axdroid began with, but I've developed it further since. For example, they didn't have audio, 2700g setup & RAM, power controls for SD/USB, had to have separate builds for each device due to LCD setup etc etc.Paul Burtonhttps://www.blogger.com/profile/14101828631122688548noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-60293801963480229562010-09-02T15:04:08.998+01:002010-09-02T15:04:08.998+01:00Sorry for the comment flood, but I just remembered...Sorry for the comment flood, but I just remembered something :)<br /><br />Before android was even heard of, the guys at handhelds.org were trying to port Linux over to the Android. This worked about as much as your effort. I think they even got Bluetooth working in the end, but they had the same problems with the touchscreen - it was misaligned, essentially "tilted" 90° to the left.<br /><br />It is the exact same I was experiencing now. If I want to use the search box, I have to click the right side of the screen. If I want to access the buttons on the lower side, I have to click the middle of the left side. I think they fixed it in the end, but it's been years since my last using the port, so I'm not sure. Essentially, all coordinates are just read wrong. Maybe you'll find something on their mailing list? (http://www.handhelds.org/hypermail/aximx50-port/current/)Unknownhttps://www.blogger.com/profile/06008362349420135560noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-21620435114304824882010-09-02T14:53:37.948+01:002010-09-02T14:53:37.948+01:00Alright... so it is indeed working, but I have to ...Alright... so it is indeed working, but I have to wait for several seconds up to minutes anytime I decide to tap the screen. Plus it seems kind of misaligned which doesn't make things easier. Can't really confirm that yet, though.<br /><br />Say, even if a wifi scan doesn't give you results, is it possible to enter the channel, SSID and name of the network and then having it connect?Unknownhttps://www.blogger.com/profile/06008362349420135560noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-18499822412723563642010-09-02T14:20:09.289+01:002010-09-02T14:20:09.289+01:00lcd_detect tells me this about my X50v:
Cached: 2...lcd_detect tells me this about my X50v:<br /><br />Cached: 2<br />FPGA: 3.7" Sharp (0)<br />AximSDK: 3.7 TFT Sharp<br /><br />I use Windows Mobile 6.5 on it, perhaps that's why I'm getting a different result than the others.<br /><br />Sadly, though, while Android boots (sloowly...), I can't seem to use it since no touch inputs are registered. Perhaps I was too impatient, but it just didn't do anything even after waiting for some time. I'll just have to wait :)Unknownhttps://www.blogger.com/profile/06008362349420135560noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-91658322687832369562010-09-02T14:03:15.427+01:002010-09-02T14:03:15.427+01:00keep up the great work! :)
you dont even know how ...keep up the great work! :)<br />you dont even know how many are there lurking in the shadows to grab that latest release of yours :)Anonymoushttps://www.blogger.com/profile/14476530686131181552noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-11134041199971461712010-09-02T10:43:19.984+01:002010-09-02T10:43:19.984+01:00tried with x50V: no touchscreen recognized/enabled...tried with x50V: no touchscreen recognized/enabled.<br /><br />I confirm the value indicated from Fergus for the LCD type.Unknownhttps://www.blogger.com/profile/09269443432941461816noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-12402909806252273032010-09-02T02:26:45.304+01:002010-09-02T02:26:45.304+01:00Axim X50v
Cached:2
FPGA:3.7" Sharp(0)
AximS...Axim X50v <br />Cached:2<br />FPGA:3.7" Sharp(0)<br />AximSDK:0" Unknown<br /><br />Home Screen<br />21:18<br />Tuesday ,Jan 4 Connect your charger<br />Mail Button goes to Home screen.<br />WM2003se reset back to 1999 installation goneMathttps://www.blogger.com/profile/02711718608162736565noreply@blogger.comtag:blogger.com,1999:blog-8953969431955539216.post-37150390799775331012010-09-01T04:42:02.188+01:002010-09-01T04:42:02.188+01:00X50v I'll try, as soon as I figure how to back...X50v I'll try, as soon as I figure how to backup my re-install, from the last time. FWIW the OLPC images install to nand flash.Mathttps://www.blogger.com/profile/02711718608162736565noreply@blogger.com