OK so after some fussing with gdb last night I tracked it down to /377 aka 255 is provided when a file pointer finished in at least this arm environment. So in read_line in pars.c I changed the condition with the getch call to check for 255 or -1, as a nasty workaround. Now I can run dispread and generate a ti3 file but when I use colprof on it, I get some very large error margins. I have turned off the dpms stuff the screen would normally do, so it sits at full brightness for the entire patch reading but I'm getting about 14 average error. It is only a medium quality shaper/matrix so maybe this is expected? I'll try a larger profile a little later and pull the quality option to high. Open to any suggestions, thanks, Daniel attaching the ti3 and icc files in case those are of use--the ti1 file is the same as the small one attached earlier in the thread. $ ./profile/colprof -v -D"Asus_TFP_brightness100" -qm -as ../target-chart No of test patches = 200 Creating matrix and curves... 100% Matrix = 0.374944 0.390730 0.222416 0.275879 0.756404 0.177861 0.067692 0.111364 1.087608 Input offset = -0.063462 -0.132334 -0.012725 Output offset = 0.016798 0.009681 0.011877 0 gamma = 1.970926 1.574419 1.825426 1 harmonics = 0.217738 -0.089309 -0.001754 2 harmonics = 0.608253 0.440239 0.479731 3 harmonics = -0.367972 -0.179178 -0.101397 4 harmonics = -0.404985 0.238357 0.286778 5 harmonics = -0.187394 0.059169 0.255883 6 harmonics = 0.120847 -0.006599 0.025147 7 harmonics = 0.116213 -0.115215 0.220402 Find white & black points Initial white point = 0.988090 1.210143 1.266664 Initial black point = 0.007598 0.004849 0.013465 Display Luminance = 360.878709 White point XYZ = 0.816507 1.000000 1.046706 Black point XYZ = 0.006279 0.004007 0.011127 Fixup matrix for white point After white point adjust: Matrix = 0.376314 0.421662 0.166224 0.247581 0.617980 0.134438 0.043507 0.074426 0.706967 Done gamma/shaper and matrix creation Profile done Profile check complete, peak err = 134.917420, avg err = 14.340426, RMS = 21.571368 On Wednesday, August 29, 2012, Dan Wilcox <dmwilcox@xxxxxxxxx> wrote: > Thanks Graeme, I'll take a look at using the web option. > > Daniel > > On Tuesday, August 28, 2012, Graeme Gill <graeme@xxxxxxxxxxxxx> wrote: >> Dan Wilcox wrote: >> >>> I noticed in the mailing list archives some Android profiling has come up >>> before, my attempt is slightly different as I'm using the tablet to profile >>> itself by way of a Debian chroot. As a result of the limitation of not >>> having either VideoLUT access or a native windowing display system (I'm >>> using VNC to provide Debian with an X environment) the attempt is here to >> >> Hi, >> note that another alternative is to use a web browser. >> See <http://www.argyllcms.com/doc/dispread.html#dweb>. >> >>> OK, now to sweat and tears, I have generated a target file with targen, >>> poured over documentation, tried a few different environments only to come >>> back to find that when dispread tries to load up the target patch file it >>> goes into an infinite loop, on the tablet--x86 laptop is fine of course. >> >>> read(16, "CTI1 \n\nDESCRIPTOR \"Argyll Cali"..., 4096) = 4096 >>> read(16, "7.642 39.734 73.389 18.751 \n79 7"..., 4096) = 4096 >>> read(16, "166 86.118 44.061 13.217 36.160 "..., 4096) = 3089 >>> read(16, "", 4096) = 0 >>> read(16, "", 4096) = 0 >>> read(16, "", 4096) = 0 >>> read(16, "", 4096) = 0 >> >> Please send the .ti1 file in question (debugging by remote control >> is not the most efficient method...) >> >> Cheers, >> >> Graeme Gill. >> >>