Develop Bugs

[APP] XDApp/LibXDA- XDA-Devs on your phone / in your app! (Semi-nightly builds!)

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Summary:
XDA users no longer have to deal with the hassle of using an inefficient browser to view the forum which provides the liveblood of their devices. Now, the Mobile XDApp gives you options to help eliminate load times and increase your productivity as you view fourms, read and reply to posts, start new threads, upload files, download files, manage your account and more!
Progress towards next release:
Code:
[|||||||||||||||_____] 75%
Latest Nightly: 00230
Updates:
Development is temporarily slowed, as I'll be very busy with work from here until late December. You have to do what you have to do, right? I'm trying to fit the XDApp in as best I can. Development is happening- it's just much slower.
Have a great idea for your own XDA-based application? I'll be releasing LibXDA soon, a .NET library that will allow you to interface with the XDA-developers forum. Check the forums directly from your app, or make a post from your application. Support for .NET and COM inter-ops, so it's extremely easy to use .NET applications, and usable from C++.
(Of course, if you're going to run the application from C++, the library will still suffer that 'managed overhead' that C# programs suffer from.)
---
I'm releasing 'nightly' builds whenever I have time for development. They're pretty much in-progress snapshots, and they're open to the public. I'll be releasing a 'more official' Alpha tomorrow, which means a lot of people will be getting e-mails with passwords. For those of you who want to see the app but don't get an e-mail, you can still run the next nightly (which will probably be further along in development than the Alpha), even though you won't be able to help right away with testing.
Here's the build number scheme, if you want to know:
VXBBB
V- Released Version- the last released major (integer) version at the time of the release.
X- Development 'branch'; 0- Backend Development (utilizing the lite version as a frontend); 1- XDApp Lite; 2- XDApp Professional; 3- Alternate Build (i.e. for testing an extension)
BBB- the build number, which starts from 0 in the version or branch and increments each time I hit the 'build' button
Features:
Complete Features:
-Dynamic multi-screen rendering library supports any screen of any size, shape, and DPI. Tested and works on QVGA, WVGA, VGA, and Square VGA. Theoretically should work with much larger screens, including large-screen RedFly devices/software.
-GZIP compression, which decreases load times by more than 80%. That's more efficient than Opera Mini! See below for compression statistics.
-Full, automatic authentication protocols mean you never have to waste time logging in again!
-Automatic server-side thumbnailing of images for much reduced image transfer.
-Unique 'superheader' view organizes forums, making it easier to navigate the forums!
Features in testing (otherwise polished):
-Full finger-friendly kinetic scrolling in all applicable views.
-Ability to 'filter' the super-headers view, showing only relevant devices.
-Fast encryption for storing user information.
-Non-touchscreen device operability.
Working features (may require polish):
-Complete user-skinability via text-based theme files.
-Finger gestures (on touchscreen devices.)
-View fora (plural forums) including post previews, with much faster rendering times than using a traditional broswer, finger friendly controls, and views optimized for mobile devices.
-Lightning-fast post rendering, both in fully formatted mode and plain-text mode.
-'Lite version' for devices using native controls for slower/older devices.
-Reply to threads and posts, and start new threads from your mobile!
Near-complete features:
-Edit your posts.
-Pre-fetching allows commonly viewed threads to load when you first start the app, completely eliminating load times later.
-Extensible external framework will allow other applications to utilize its features: e.g. allow a user to directly post a bug-report, complete with attached memdump, to a developer's thread.
In Progress:
-Download files and attachments instantly, without even opening a browser.
-Bookmarks!
Pending development:
-Lose connection while typing a post? XDApp has an option to automatically queue your post and finish sending it next time you have a connection!
-Private message handling.
Future releases:
-Wiki view.
-Upload a picture or file directly from the phone.
-Take a screenshot of one's phone, and upload it directly as an attachment.
-Update threads via psuedo-push: trigger notification/update of thread upon recipet of subscription e-mail.
-Real-time update checking; i.e. no need to constantly refresh the thread you're on.
-Full WYSIWYG editing of BB-code post formatting.
-Push-style notifications on private messages and subscribed threads.
-Interconnections with my sensor control project which will allow use of the g-sensor, light sensor, capacitive button sensors, stylus sensor and camera to support various types of gestures and inter activities. For example, use the light sensor to automatically switch to a theatre or meeting-friendly 'night mode'.

[APP] XDApp- XDA-Devs on your phone! Releasing 'Nightly' pre-Alphas. (Latest V:00230)
Most Recent Screenshots:
Rhodium/manila like theme:
(Rhodium Manila-like theme.)
Original XDA Theme:
iPhone-like Theme:
Bounty:
Currently at: $176
jmckeejr: paid! for a fully functioning app with at least abilty to reply to posts without waiting for 5 minutes and trying to chase Opera around to see what I'm typing.
dnieman13: $10
apreichner: $5
codybear: $5 Around $5 if it works with Windows Mobile 6.5 and works better than using the Opera browser
uniqueboy: paid!
krook6023: $15 for a working version with all the bells and whistles described
akp99: $10
Bijdehandje: $35 Exact: € 25 For a working Kaiser version that is a quality and complete app
greeneyemonstruo: paid!
acidbath5546: $10
sinoo: $7 Exact: 5€ for a reliable and fully functional tool
jor3l: $10
x|Lukas|x: $14 Exact: €10
If you'd like to, you can add to the bounty. It's completely optional, as I write applications because I enjoy programming, not for money.
Also, if you'd like, you can donate using the link in my signature (via PayPal). The money will be used to pay for the server I currently use for testing and soon will be using to provide an optimizing, compressing, streamlining proxy to reduce your forum load-times.
Many thanks for generous donations from: ljinsane, uniqueboy, greeneyemonstruo, jmckeejr, mostberg, SoundMind.us

Compression Statistics:
These compression statistics are without any server-side streamlining. (Compression is server-side.)
This page:
Original (uncompressed) size: 129,071 bytes (126.0 KiB)
GZIP Compressed size: 22, 816 bytes (22.3 KiB)
Compression Ratio: 82.3%
Forum index:
Original (uncompressed) size: 304,301 bytes (297.2 KiB)
GZIP Compressed size: 34,894 bytes (34.1 KiB)
Compression Ratio: 88.5%
Many thanks to:
Those who have pledged to the bounty. At the time of your donation, you will be thanked here.
ace10134- who started this whole movement, and is thus responsible for bringing this app to you guys in the first place.
Jenn, who has been unendingly patient while I sit here coding instead of paying attention to her.
Preview Releases:
First Feature Preview (password protected ZIP file, not for general public)
If you're interested in testing 'feature previews', go ahead and shoot me an e-mail ([email protected]) with the subject line "feature tester". Debugging experience helps, but isn't necessary.

Showing a bit of interest here (Plus Im not too bad at reverse engineering )

Good to see progress being made . I'll be sending you an email soon(hope I can help) and I'll get that donation ready

Ok, I got the old thread all set up to be locked.
No one make a post on the old thread!!! I'm waiting for it to be locked, and I want the thread re-direction to be the last post. Thanks to everyone who showed interest/donated/motivated/etc. And the biggest thanks to the developer.
Now keep this thread up to date!!! And a working version to test would be awesome.
Thanks everyone,
Andrew

ktemkin said:
Bounty:
Currently at: $135
Click to expand...
Click to collapse
Can't believe it. I've been lurking around this site for over a year and this is the first time I saw the XDA 'bounty' (I've only recently heard about it at all).
Anyway, this is an interesting concept. I'm pretty much fine with using Opera Mini to browse XDA, but this could potentially turn out great. I hope all the best to you and your work, Ktemkin!

+5€ for a reliable and fully functional tool!
Can't wait to try it!

Looking very good.
I closed the old thread, and stickied this one instead of the old one.

I found this, what you are doing is what they have done.
3Gtan---A great web Browser for forum
unfortunately its in Chinese

Looks promising, well done!

sinoo said:
+5€ for a reliable and fully functional tool!
Can't wait to try it!
Click to expand...
Click to collapse
5 Euros is about $7 USD, (7.11540 USD), when you update the bounty.
l3v5y said:
Looking very good.
I closed the old thread, and stickied this one instead of the old one.
Click to expand...
Click to collapse
Thanks!

topsign said:
I found this, what you are doing is what they have done.
3Gtan---A great web Browser for forum
unfortunately its in Chinese
Click to expand...
Click to collapse
That seems to work pretty well, but, unfortunately:
-is Completely in Chinese.
-is Closed Source
-takes up a lot of the screen with useless icons and buttons.
-doesn't support downloads/uploads, or most of the advanced features planned for the XDApp project.
Might be useful for people to use in the interim- if they can figure out how to use it.
---
On a more XDApp-related note, I have a few questions for the end-user:
1) Icons: are they worth the screen space? They would only be 5-6 pixels wide (10-12 on double VGA systems), and they'd appear in the following places:
-In front of posts, displaying the the 'new', 'popular', 'you replied here', etc. icons.
-Real icons for things like quote and edit. Right now, the design is that you quote, edit, reply, etc. by right clicking (click and hold) and selecting that option from a menu. Would finger-sized icons in each post be better?
2) Mobile posts- when posting from the a mobile phone, should the XDApp (have an option to) auto-insert a small icon on each post it makes? For example, a post from a mobile phone might look like:
--
Just checking up on the status of the project. Looking forward to your next ROM release!

is planed a multilang interface? would be cool and i can help with translations if needed

ktemkin said:
That seems to work pretty well, but, unfortunately:
-is Completely in Chinese.
-is Closed Source
-takes up a lot of the screen with useless icons and buttons.
-doesn't support downloads/uploads, or most of the advanced features planned for the XDApp project.
Might be useful for people to use in the interim- if they can figure out how to use it.
---
On a more XDApp-related note, I have a few questions for the end-user:
1) Icons: are they worth the screen space? They would only be 5-6 pixels wide (10-12 on double VGA systems), and they'd appear in the following places:
-In front of posts, displaying the the 'new', 'popular', 'you replied here', etc. icons.
-Real icons for things like quote and edit. Right now, the design is that you quote, edit, reply, etc. by right clicking (click and hold) and selecting that option from a menu. Would finger-sized icons in each post be better?
2) Mobile posts- when posting from the a mobile phone, should the XDApp (have an option to) auto-insert a small icon on each post it makes? For example, a post from a mobile phone might look like:
--
Just checking up on the status of the project. Looking forward to your next ROM release!
Click to expand...
Click to collapse
I for one like the Icon for mobile post. +1 for the right click option as it will not take as long to load on older devices without the icons.

ktemkin said:
On a more XDApp-related note, I have a few questions for the end-user:
1) Icons: are they worth the screen space? They would only be 5-6 pixels wide (10-12 on double VGA systems), and they'd appear in the following places:
-In front of posts, displaying the the 'new', 'popular', 'you replied here', etc. icons.
-Real icons for things like quote and edit. Right now, the design is that you quote, edit, reply, etc. by right clicking (click and hold) and selecting that option from a menu. Would finger-sized icons in each post be better?
2) Mobile posts- when posting from the a mobile phone, should the XDApp (have an option to) auto-insert a small icon on each post it makes? For example, a post from a mobile phone might look like:
--
Just checking up on the status of the project. Looking forward to your next ROM release!
Click to expand...
Click to collapse
1) - Icons in front of the posts aren't exactly necessary. I guess they could be nice, but I'd rather be able to read more text on the screen instead. The icons are rather small, though, so it's no big deal.
- About the "Quote" and "Edit" buttons...I say that the right clicking method is awesome! Otherwise seeing all of those "Quote" and "Edit" buttons on every single post is repetative. I like your right-clicking method. 1 vote for that.
2) the Mobile post thing is a cool idea, and you might as well have the option. But, a better location for the icon...You know how you can pick an icon for your reply? Such as how I picked the Cool Sunglasses Smiley? If we could somehow replace that with a mobile phone icon, that would be perfectly ideal. But, we'd have to get the Admins to do that. So...I'm for having the option of putting the "Mobile" icon, just like how you showed in the example.

hmm 2 qstions, 1. will have multilang support? and 2. you are doing a server side work or the app donwload the page and then fix it for the phone?

Good to see this is moving right along!!
Icons....are a good question...is pushing a icon that much more functional than right clicking? Icons for for things like quote and edit might give a more ascetic or native look but IMO they would add little to the usability. Icons in front of posts...I really don't care either way...and the Mobile Post thing is a very cool idea....ktemkin...I like the way you think...this app is going to be awesome!

This just keeps getting better and better. Up my pledge to $25 for a little extra motivation.

greeneyemonstruo said:
This just keeps getting better and better. Up my pledge to $25 for a little extra motivation.
Click to expand...
Click to collapse
Ktemin should be putting your bounty in the pot soon.
Ktemin (or however you spell that), you should put the bounty in the Thread Title, like it used to be. Well, actually, the bounty doesn't matter anymore, nvm then.
But, everyone, should we have buttons for "Quote", "Edit", etc? Or do you want to access those features by right clicking on the post, and then clicking them? By using the right-click method, we save space. By using the buttons method, we have quicker access. What do you think? (just repeating Ktemin's question).

[APP][ALPHA] G Force Logger for Vehicle Performance (no, not gPC)

Hi, my name is Eric. I've been working with WinCE for a long time (since WinCE 2.0 haha) and I've regained interest in PPC programming. Working with few things here and there, mostly experimenting.
In anycase, I've got an idea to record g forces on a vehicle while it's being tested to its limits (AutoX, drag race).
Now, I know there's already a piece of software out there, gPC, but it isn't completely refined (indepth calibration, angle corrections) or completely free (by donation).
The goal of the project is to create something similar to a device called gTech which goes upwards of $300 for the basic model.
Key features will include:
- a reset function + algorithms to compensate for device orientation
- graphs of resulting logged data
- logging of calibrated data and raw data
- Driving aids
- Flashing screen to indicate reaching of new peak G (separate indicators for forward and lateral)
- a screen showing realtime overlapping graphed data for all axis
- a 2d grid with a cursor indicating current forward and lateral g
- on the same 2d graph, a drawn boundary indicating limits of g achieved (this will eventually look like an egg after working the car hard)
- and finally, real time telemetry transmission via edge/3g to a receiving computer
The ultimate goal of this project is to provide reliable data for motor enthusiasts whether they would like to see if their shifting is smooth, or if they're braking, or powering on in the right places or if their car mods have had any effect (this last one is pretty useful to quantify). In addition, provide some rudimentary tools to assist in competitions and spirited driving in the form of g limit warnings (flashing screen, large indicators of current g). In the case of spirited driving on a mountain road, the device can warn when approaching loss of traction (after collecting limit data) to prevent going off a cliff.
Venues of use:
Auto Cross
Track Days
Drag Strip
Skidpad
Of course, I have to insert here, that this device can't save your bacon if you do something idiotic and by no means do I condone dangerous driving.
With that said, all the above is what I hope to achieve and any of your comments is well appreciated.
Current Release:
v0.1
Alpha stage, rudimentary raw data output via numbers and a line (indicating X and Y recorded g) and a circle (indicating Z g). The numbers shown are the raw numbers recorded from the accelerometer and not converted to m/s^2. Although, you can probably do that math on your own if you're smart enough (simple scaling). What I've discovered is that each accelerometer is different, and even going from a negative axis (eg, device upside down) to positive axis (device right side up) will give different numbers. In addition, if you run the program, you'll notice a lot of jitteriness. I hope it doesn't affect the accuracy once I smooth them out with a segmented average.
Executable is packaged in a zip. It contains an EXE which can be straight run with Dot NET CF v2.0 (basically, all WM 6.1 devices)

Hi Canagan,
Great idea, I will certainly be testing this out.
I would like to ask, would it be possible to be able to include 1/4 mile time, and 0-60 etc so we can work out HP of the car. There is a similar app for the Iphone called Dynolicious http://gizmodo.com/5030749/iphone-apps-we-like-dynolicious-car-performance-meter
Thanks.

Whoooaaa sound a really good app ! Will test it this weekend ! Thanks

PooleyUK said:
I would like to ask, would it be possible to be able to include 1/4 mile time, and 0-60 etc so we can work out HP of the car. There is a similar app for the Iphone called Dynolicious http://gizmodo.com/5030749/iphone-apps-we-like-dynolicious-car-performance-meter
Click to expand...
Click to collapse
Yes, I can do that if there's more of a demand for it. Calculating horsepower is fairly simple, however, I may put 1/4 mile times and 0-60 towards the end of development as they require tieing into the GPS.

Great idea.. I will test it also
It seemt to be working on my Touch HD. But are the meaning of all these numbers??

CanaganD said:
Yes, I can do that if there's more of a demand for it. Calculating horsepower is fairly simple, however, I may put 1/4 mile times and 0-60 towards the end of development as they require tieing into the GPS.
Click to expand...
Click to collapse
Cool, looking forward to seeing this develop.
So far the accelerator test seems to be working fine.

would be need ive i could see how many hp mycar has

Barcode scanner, offline (no internet connection needed)

Hi guys.
Who wanted a free barcode scanner? Here we are...
No network connection needed; app based on zxing library and Kevin Marshall's (from Clarity Consulting, can't remember his blog url now) code.
I just slightly modified the original code and added a few (probably useful but not sure ) services.
App interface is very simple: run application, focus on barcode, and wait until code is recognized. Touch handset screen to run recognition again.
Buttons description:
- "Save" saves captured barcode to jpeg;
- "Bing" and "Google" used for barcode web lookup (probably this part needs more work)
- "Mail" and "SMS" used for sending recognized code text.
Enjoy!
UPDATE 1: v 1.1, auto focus added;
UPDATE 2: v 1.2, orientation-less UI added, project moved to opensource at googlecode: http://code.google.com/p/barcodescan/
UPDATE 3: v 1.2.1, slightly changed autofocus logic, now works better on HTC. Download link: http://barcodescan.googlecode.com/files/BarcodeScanner.xap
UPDATE 4: v 1.2.2
- barcode search improved;
- added HTC detection, changes in autofocus logic;
http://barcodescan.googlecode.com/files/BarcodeScanner_1.2.2.xap

Is this a marketplace app?

sensboston said:
Hi guys.
Who wanted a free barcode scanner? Here we are...
No network connection needed; app based on zxing library and Kevin Marshall's (from Clarity Consulting, can't remember his blog url now) code.
I just slightly modified the original code and added a few (probably useful but not sure ) services.
App interface is very simple: run application, focus on barcode, and wait until code is recognized. Touch handset screen to run recognition again.
Buttons description:
- "Save" saves captured barcode to jpeg;
- "Bing" and "Google" used for barcode web lookup (probably this part needs more work)
- "Mail" and "SMS" used for sending recognized code text.
Enjoy!
Click to expand...
Click to collapse
I can't seem to get it to do anything. It says 'Scanning...' and I'm trying different distances to codes, but nothing ever happens. Any pointers?

Is this limited to any country or is it just reading out what the barcode says?

OK, lets go through step by step:
- it's not a marketplace app and have no chance to be published 'cause it uses undocumented camera API; you should download and unpack attachment and sideload the app;
- if you can't capture the barcode, try better lighting. Also, move a handset to autofocus camera. In my tests the scanner captured 100% of barcodes: from books, computer part boxes, foodstuff...
- it's not limited to US 'cause (I believe) the barcodes are international. And yes, it's just reads the barcode; however you may bing or google results, in the most cases search engines able to find product/book description or specifications.
It's a very basic scanner; if someone can recommend online API/service to parse barcode value, I can add it to the program (but I really do not want to spend much time for this)

It technically works but the issue is lack of AF or Macro access.
On my Focus, it only works if I scan a barcode off of my PC (do an image search for one) --then it's super fast and quick.
Books, CDs, etc. do not work, regardless of lighting or distance--I suspect because the camera is not trying to AF. Any work around to that?

I've tested first on HTC Surround - work perfect (I can prove). But you've right about Focus'es bad autofocus (LOL, sound nonsense - "Focus have no autofocus"!).
Will see what I can do... Any other suggestions or wishes (about barcode lookup, UI, etc.)?
P.S. Fixed (reload version from the first post), now working good on Samsung Focus.

sensboston said:
I've tested first on HTC Surround - work perfect (I can prove). But you've right about Focus'es bad autofocus (LOL, sound nonsense - "Focus have no autofocus"!).
Will see what I can do... Any other suggestions or wishes (about barcode lookup, UI, etc.)?
P.S. Fixed (reload version from the first post), now working good on Samsung Focus.
Click to expand...
Click to collapse
Boom.
Working great on Focus now. Nice job. Think I'll try an LG next... bwahaha
As far as changes, no none right now. I'm sure what other apps use for barcode price comparisons--but perhaps a tie into Amazon or eBay would be good. Too bad you can't just jack into ShopSavvy's system with it, lol. If I think of any, will post back.
Edit: Working on LG Quantum too!

sensboston said:
I've tested first on HTC Surround - work perfect (I can prove). But you've right about Focus'es bad autofocus (LOL, sound nonsense - "Focus have no autofocus"!).
Will see what I can do... Any other suggestions or wishes (about barcode lookup, UI, etc.)?
P.S. Fixed (reload version from the first post), now working good on Samsung Focus.
Click to expand...
Click to collapse
hmm, 1.0 wasn't upside down, but 1.1 is upside down on my Focus. Anyone else see this?

davux said:
hmm, 1.0 wasn't upside down, but 1.1 is upside down on my Focus. Anyone else see this?
Click to expand...
Click to collapse
Nope. Fine on my Focus. It does work with accelerometer, you sure that isn't it?

Works well on my HD7! Great job! Hopefully it will tie in with Amazon and save previous searches within the app etc

sensboston said:
Hi guys.
Who wanted a free barcode scanner? Here we are...
No network connection needed; app based on zxing library and Kevin Marshall's (from Clarity Consulting, can't remember his blog url now) code.
Enjoy!
UPDATE: v 1.1, auto focus added;
Click to expand...
Click to collapse
Do you have any interest in releasing the source? I may have some time to improve upon this a bit, but I'd rather not start from scratch (or step on any toes re-creating virtually the same thing).
malatesta said:
Nope. Fine on my Focus. It does work with accelerometer, you sure that isn't it?
Click to expand...
Click to collapse
Good call, I was holding it strangely every time I opened it before. It works great.

davux said:
Do you have any interest in releasing the source? I may have some time to improve upon this a bit, but I'd rather not start from scratch (or step on any toes re-creating virtually the same thing).
Click to expand...
Click to collapse
Why not? I'm really do not have time for that project...
Here we are: http://code.google.com/p/barcodescan/
Send me a PM with your gmail and I'll add you to the project contributors. Do not forget comment each commit, increment solution version and promptly build community release (and upload xap to the project's download page!) - and you allset
BTW, there are many things to improve: better UI (completely orientation-less), additional functionality - commit found barcodes to database etc. etc. etc.

Please review and follow these rules, it appears you aren't following them, you most likely aren't following the template. So fix it quick . It is not a harsh criticism, it is just for consistency and better for the user. PM me for help or support!
If this post is here and your thread is closed, it means that you aren't following them and your intentions are for gain only.​
~~Tito~~

problem htc hd7
how do i copy this scanner programme to my htc hd7
i really hate this phone i had a htc touch pro 2 and it was far better can someone help me out here and also if some one can teach me how to customize personal ringtone would be great

Thx for the code. Really usefull to learn from this
Sometimes when you scan a barcode and touch the screen to start again. After a few seconds it stops and shows the last barcode again.
It looks like the UI thread is catching up scanning some images. How to get rid of this?

ajhvdb said:
It looks like the UI thread is catching up scanning some images. How to get rid of this?
Click to expand...
Click to collapse
Sorry, I don't have a time for that application now but it should be significantly refactored.If you want you may join the project and continue development, we can share some ideas for app improvement etc.
As for problem u described, you should play with the different capture resolutions or give some hardcoded "pause" to recognition library Also, MS camera API (still not officially allowed) is not documented and very poor... However it's a great field for experiments and hacks

Thanks! That works great on my HD7.

~~Tito~~ said:
Please review and follow these rules, it appears you aren't following them, you most likely aren't following the template. So fix it quick . It is not a harsh criticism, it is just for consistency and better for the user. PM me for help or support!
If this post is here and your thread is closed, it means that you aren't following them and your intentions are for gain only.​
~~Tito~~
Click to expand...
Click to collapse
Please follow up on this!

sensboston said:
Sorry, I don't have a time for that application now but it should be significantly refactored.
Click to expand...
Click to collapse
Im not that experienced in multiple threads. Do you think the problem is in the Zxing lib?
Looking at the code the Zxing lib should have a completed event from which you can restart or show the image.
This code works but is racing and racing in the UI thread and after finding a barcode and restarting it looks like something from a buffer is used..
Code:
private void GrabFrame()
{
Dispatcher.BeginInvoke(() =>
{
if (_Camera != null && CameraVisualizer.Visibility == Visibility.Visible)
{
WriteableBitmap wb = new WriteableBitmap(640, 480);
_Camera.GetCurrentFrame(wb);
wb.Invalidate();
ScanBarcode(wb);
wb.DisposeIfPossible();
GrabFrame();
}
});
}

FBReaderJ Partial Refresh Now Works on Nook2!

I spent some time looking into the Nook2 device and have just got partial refresh working for FBReaderJ. And well, theoretically speaking we can get it work for anything as long as we have the source code.
Attached is my build of FBReader. You'll need to sign it and adb install it to your device. Some settings (turn off animation, colors...) will be necessary and bugs may exist as it's an early build.
----- Technical Details -----
There're two ways for Nook2 to determine which way to refresh:
1. Automatica - in an onDraw() session, if the sum of drawBitmap's Rect is larger than 50% of screen (the number's based on test, not so sure), go whole page refreshing
2. Manual - will have to choose the mode through JNI calls to Epson's e-ink library.
In the Nook2 release, somehow B&N didn't obfuscate the code, nor remove the tracing message, which makes analysis possible.
The screen-refreshing code of built-in reader lies in - /system/app/Reader.apk ->com.bn.reader.ui.ReadingViewSimpleMode
The JNI bridge java code is in - system/lib/framework.apk -> com.android.hardware.EpdController
There're three modes of screen-refreshing (with notions in EpdController.Wave)
DU/GU - Partial refresh
GC - Whole-page refresh
A2 - The built-in reader's magical fast-refreshing mode. Creates very little artifacts/ghosting.
Rest of the work's trivial. Used Java Reflection to re-encapsulate the Epd driver code and modified the FBReader ZLibrary.
Hope my work helps and encourages new ideas to come!

Could you share source code of your patch?
I'm going to add support of Nook Touch refresh settings to CoolReader app.

You know we have the source for the entire OS.

Actually A2 mode is not for fast page turns. It is intended for 1-bit animations - only black pixels are drawn. GL16 + ACTIVE mode is used for fast page turns and GL16 + ONESHOT_ALL is used for regular mode.

Yes you're right.... that was a misinterpretation for me before...
I'm currently in the office and I'll release the Epd source class tonight when I get back home. Now all Nook supported modes, GC, GU, GL16 and A2 are implemented.
I'm working on a Nook2 friendly launcher now and hopefully will have some results in couple of days.
NomadRunserver said:
Actually A2 mode is not for fast page turns. It is intended for 1-bit animations - only black pixels are drawn. GL16 + ACTIVE mode is used for fast page turns and GL16 + ONESHOT_ALL is used for regular mode.
Click to expand...
Click to collapse

Great news!
DairyKnight said:
Yes you're right.... that was a misinterpretation for me before...
I'm currently in the office and I'll release the Epd source class tonight when I get back home. Now all Nook supported modes, GC, GU, GL16 and A2 are implemented.
I'm working on a Nook2 friendly launcher now and hopefully will have some results in couple of days.
Click to expand...
Click to collapse
This is fantastic news! I can't wait to try out the results. Thank you in advance for your efforts!

Possibility of Game and Watch style games?
NomadRunserver said:
Actually A2 mode is not for fast page turns. It is intended for 1-bit animations - only black pixels are drawn. GL16 + ACTIVE mode is used for fast page turns and GL16 + ONESHOT_ALL is used for regular mode.
Click to expand...
Click to collapse
I wonder if it would be possible (and effective) to use the 1 bit animation mode to mimic the functionality of Game and Watch type games. As long as there is no scrolling (which would never happen on a segmented display) and if the imagery is small enough, the results might be very good!

Here's the Epd source as promised.
All modes should be there. Simplest way to use is putting:
setGL16Mode();
as the first line of your onDraw() listener.

DairyKnight
The current version FBReaderJ - 1.1.10 (more bugfixes).
Will make new patch?

It should be very straightforward. Only need to put one extra line in the source.
I'll try to contact geometers to see if it's possible to put a "Nook2 Mode" in the official FBReadeRJ release.
kaznelson said:
DairyKnight
The current version FBReaderJ - 1.1.10 (more bugfixes).
Will make new patch?
Click to expand...
Click to collapse

DairyKnight said:
Here's the Epd source as promised.
All modes should be there. Simplest way to use is putting:
setGL16Mode();
as the first line of your onDraw() listener.
Click to expand...
Click to collapse
Hello!
Can I use this code in my GPL app (e-book reader Cool Reader)?

DairyKnight
It is similar to calls, as in the version FBReaderJ for Spring Design Alex Reader?
github.com/geometer/FBReaderJ-alex/blob/master/src/org/geometerplus/android/fbreader/EPDView.java
PS: geometer's active thread about FBReaderJ:
4pda.ru/forum/index.php?showtopic=101249

Sure. Please move ahead.
I wrote the code in a rush and just realized that I didn't put in a Copyright note in it. So here it is - you're encouraged to use this piece of code for anything, either commercial or free, either close-sourced or open-sourced.
However, do put a line in your "About" section saying that you used a code from dairyknight ([email protected]). That's the only request from me.
Buggins said:
Hello!
Can I use this code in my GPL app (e-book reader Cool Reader)?
Click to expand...
Click to collapse

I don't think it's anything similar, unless they share the exact same vendor java driver code.
The 4PDA thread you provided is in Russian and unfortunately I don't understand a single word. If you can, get in touch with geometer and see what he thinks. I'll give all the assistance I can to get the official FBReaderJ working for Nook2.
kaznelson said:
DairyKnight
It is similar to calls, as in the version FBReaderJ for Spring Design Alex Reader?
github.com/geometer/FBReaderJ-alex/blob/master/src/org/geometerplus/android/fbreader/EPDView.java
PS: geometer's active thread about FBReaderJ:
4pda.ru/forum/index.php?showtopic=101249
Click to expand...
Click to collapse

DairyKnight
And I badly speak in english...
geometer e-mail:
geometer at fbreader dot org
www.fbreader.org/contacts.php
Arseny Shmartsev, CEO: [email protected]
Support: [email protected]

kaznelson said:
DairyKnight
geometer e-mail:
geometer at fbreader dot org
Click to expand...
Click to collapse
Nikolay Pultsin is main FBReader developer. Anybody can get in touch with him by supplied email, he understands and writes in english as well.
As another option... everyone can 'fork' fbreaderj main repositury on github, put patch in code, commit and make pull request to main code trunk.

DairyKnight, many thanks for your work!
There are some questions about your code.
I need to call setGL16Mode() for every page in GL16 mode, but A2 and DU modes required setting mode only once. I.e. if I skip setGL16Mode() before draw, device is fully refreshed. But how I can set "default mode" for DU, i.e?
Other issue is about same, but in other context - before calling "Setting Dialog" (or any other fullscreen dialog) I need to turn controller onto "default mode" - there are many artefacts on screen without this. With GL16 this is not question, but when selected DU or A2 mode... Temporarily I call setGL16Mode() - this is better then nothing.
Another question - NomadRunserver suggested GL16 + ACTIVE mode for fast page turns, but GL16 + ONESHOT_ALL in your code (in comments, if precise). This is better?
DairyKnight said:
Here's the Epd source as promised.
All modes should be there. Simplest way to use is putting:
setGL16Mode();
as the first line of your onDraw() listener.
Click to expand...
Click to collapse
update:
setGL16Mode() in DairyKnight code invokes GL16 + ONESHOT
other variants:
1 - ACTIVE
2 - ONESHOT
3 - CLEAR
4 - ACTIVE + ALL
5 - ONESHOT + ALL
6 - CLEAR + ALL
Modes 4, 5 and 6 are permanent, 1, 2, 3 - temporary.
CLEAR modes make full refresh.
I can't see much defferences between ONESHOT and ACTIVE, but last seems to be more clear. I preferred ACTIVE + ALL.
BTW, nook reader make full refresh on pages with images and next one. Wise decision, because partial refreshing lead to ghostings and artifacts in such cases.

DairyKnight said:
Sure. Please move ahead.
I wrote the code in a rush and just realized that I didn't put in a Copyright note in it. So here it is - you're encouraged to use this piece of code for anything, either commercial or free, either close-sourced or open-sourced.
However, do put a line in your "About" section saying that you used a code from dairyknight ([email protected]). That's the only request from me.
Click to expand...
Click to collapse
EPD settings for Nook Touch added to CoolReader
(thanks to a_lone)
Can be downloaded from sourceforge (crengine project). Can't publish link - antispam protection.
Your name is in about/third party, source code and git change history

CoolReader apk is attached.

Could you please post the build of fbreader with full page refresh? I'm rather new to Android development, and I'm not familiar with fbreader source; trying to figure out how to plug in N2EpdController into fbreader would take me a long time. Thanks!

[Q] Tap triggers swipe (aka sensitive screen)

Some people over at the fairphone.com forum reported a "sensitive" screen. They try to tap on a button (or link) and instead of triggering the button the fairphone starts scrolling. My fairphone also shows this behavior and I tried to find out why. Well, after trying for some time I realized that the shorter I tap on the screen the more likely it happens in a swipe/scroll.
So I enabled the "pointer position" option within the developer tools and shot two screen shots. In the first screenshot I tap for round about 500ms whereas in the second screenshot I tried to tap as short a possible. Like you would click with mouse. It show the error pretty obvious. Any ideas how to adjust that?

Hello
I noticed exactly this behaviour on my Fairphone, too.
That's why I started a thread on the official Fairphone website 22 days ago.
I'm not allowed to post direct links here, so I can give you only the head line here:
"Hyper-sensitive-touchscreen"
And on german Fairphone Freunde forum there's also a thread about this problem
Key-Word:
"Empfindlichkeit-des-Touchscreen"
So far, there is not very much response on these threads, but it seems that not all the handsets are affected, because not all of the answers confirmed the problems. One of the guys on fairphone website sent a request to the support team, a few days ago. Maybe he can forward the answer he gets... I'll ask him in his own fairphone thread - "Sensibility-and-reboots"
Unfortunately my phone broke after just one day, so I'm waiting for a replacement now and can't really offer a solution here...
But during the few hours, my phone worked, I entered the engineering mode (by typing *#*#3646633#*#* in the standard dialler app) and there were many options to manipulate the tuochscreen.
Maybe the more experienced guys here in the forum can work out a solution to solve the problem?!
Thank you in advance!

I have the same "hypersensitive screen" issue
Before I was used to briefly and lightly tapping/touching the screen, but with my Fairphone that often gives a scroll signal.
My developer crosshair option shows short lines, the touchpanel behaves as if I first tapped a few centimers away and then a split second later it registers where I actually touched the screen.
I had to learn to firmly tap and hold, otherwise I couldn't select anything on the screen.
It seems a sofware patch for the touchpanel is needed.
-----------------------------------------------
Fairphone FP1
Caju (v.1.1)

Touchscreen settings
I am copying this from the Fairphone forum, for future reference:
My settings, as copied from engineering mode:
tpd_em_log = 0
tpd_em_log_to_fs = 0
tpd_em_sample_cnt = 16
tpd_em_auto_time_interval = 10
tpd_em_pressure_threshold = 0
tpd_em_debounce_time = 0
tpd_em_debounce_time0 = 1
tpd_em_debounce_time1 = 4
tpd_em_spl_num = 1
tpd_em_asamp = 1
NOTE: Do NOT change any of the values (in this case, under Settings). I do not know what they do, really, and how your device might react! I just report mine, for your comparison.
Just FTR, my device works fine!
Any values different from yours? Then I would suggest reporting the issue to FP while including the link to our discussion here, and on the Fairphone forum. If we can narrow down the source of the problem to be caused by some settings, and not your environment or your specific devices hardware malfunctioning, @benkxda could report this to FP in his next mail.

boondiordna said:
I am copying this from the Fairphone forum, for future reference:
My settings, as copied from engineering mode:
tpd_em_log = 0
tpd_em_log_to_fs = 0
tpd_em_sample_cnt = 16
tpd_em_auto_time_interval = 10
tpd_em_pressure_threshold = 0
tpd_em_debounce_time = 0
tpd_em_debounce_time0 = 1
tpd_em_debounce_time1 = 4
tpd_em_spl_num = 1
tpd_em_asamp = 1
NOTE: Do NOT change any of the values (in this case, under Settings). I do not know what they do, really, and how your device might react! I just report mine, for your comparison.
Just FTR, my device works fine!
Any values different from yours? Then I would suggest reporting the issue to FP while including the link to our discussion here, and on the Fairphone forum. If we can narrow down the source of the problem to be caused by some settings, and not your environment or your specific devices hardware malfunctioning, @benkxda could report this to FP in his next mail.
Click to expand...
Click to collapse
I already put a link on fairphone.com to this XDA thread. Thanks for telling! Well, my settings looks identical to yours. I also played around with them. I have no idea if touch screens nowadays need deboucing or sth like that. So I changed these settings a bit...without improvement though. I am also wondering what tpd_em_log is. It is put to 0. I put it to 1 hoping there is some log written somewhere....but i could not find where unfortunately.

Hey there,
I have the same problem and no solution. But here is my input on that issue. Maybe it helps Fairphone when they investigate that issue, maybe not.
hanzano said:
Well, after trying for some time I realized that the shorter I tap on the screen the more likely it happens in a swipe/scroll.
Click to expand...
Click to collapse
I realized the same thing. BUT in addition, I figured out that it has also something to do with how soft you touch. If I try and touch my screen very very gently, I can reconstruct that behaviour every time. If I press a bit harder, it works better.
I attached a screenshot where I did soft touches, and you see a lot of wiggeling especially in the botom row

Yesterday I was annoyed by this issue. I was a bit in a hurry and the Fairphone touchscreen did not react properly
So I just debugged in Android Studio and this is what I logged:
Code:
12:07:48.874 MotionEvent.ACTION_DOWN: 300.44363, 485.4943
12:07:48.886 MotionEvent.ACTION_MOVE: 293.13342, 499.09888
12:07:48.901 MotionEvent.ACTION_MOVE: 293.45657, 497.48178
...
12:07:49.168 MotionEvent.ACTION_MOVE: 293.45657, 497.48178
12:07:49.183 MotionEvent.ACTION_MOVE: 291.2037, 497.48178
12:07:49.198 MotionEvent.ACTION_MOVE: 290.46213, 497.48178
...
12:07:49.403 MotionEvent.ACTION_MOVE: 290.46213, 497.48178
12:07:49.406 MotionEvent.ACTION_UP: 290.46213, 497.48178
12:07:49.406 event.getDownTime: 566
I tapped for 566ms. Pretty obvious that from ACTION_DOWN to the first ACTION_MOVE there is a big delta of ~14px (is it really pixel?) in y-direction.

Hey there,
probably this does not help anyone, but just for the sake of documentation: due to my headphone-jack issue, my fairphone got replaced by a new one. Now it seems that my sensitive screen issue is gone.

I don't know about how many sources you guys have, but if you have the kernel sources, someone could try to implement a filter (and enable debugging logs in the kmsg ofc) so touches under 400ms (just a value for explanation) are only getting registered as touches, but not as movements. However, this could also have some downsides (pretty fast swipes for example), therefore a sysfs option would be a nice idea
But this would at least be a workaround.

Hyst said:
Hey there,
probably this does not help anyone, but just for the sake of documentation: due to my headphone-jack issue, my fairphone got replaced by a new one. Now it seems that my sensitive screen issue is gone.
Click to expand...
Click to collapse
Hmm, ok.Would you mind doing another sreenshot like you did already? Just in order to see the difference.
laufersteppenwolf said:
I don't know about how many sources you guys have, but if you have the kernel sources, someone could try to implement a filter (and enable debugging logs in the kmsg ofc) so touches under 400ms (just a value for explanation) are only getting registered as touches, but not as movements. However, this could also have some downsides (pretty fast swipes for example), therefore a sysfs option would be a nice idea
But this would at least be a workaround.
Click to expand...
Click to collapse
That is what I also had in mind. I already had a look at Xposed framework trying to find out how to "intercept" global touches. With a normal Android Service it is unfortunately not possible at least what I have read so far.

hanzano said:
That is what I also had in mind. I already had a look at Xposed framework trying to find out how to "intercept" global touches. With a normal Android Service it is unfortunately not possible at least what I have read so far.
Click to expand...
Click to collapse
Xposed is a genious piece of work, however, this should be done via kernel.
Maybe @benkxda could have a chat with Fairphone about that?

hanzano said:
Hmm, ok.Would you mind doing another sreenshot like you did already? Just in order to see the difference.
Click to expand...
Click to collapse
no problem. Here you go!
As far as I am concerned I did the same thing. small fast touches.
although sometimes there is a long line, overall a lot less wiggeling.

Hyst said:
no problem. Here you go!
As far as I am concerned I did the same thing. small fast touches.
although sometimes there is a long line, overall a lot less wiggeling.
Click to expand...
Click to collapse
That looks much better than beforehand. I believe the red lines are not of interest. These just seem to be estimations. I had a look into Android source code com.android.internal.widget.PointerLocationView. The VelocityTracker has an Estimator which is drawn in light red. The MediaTek development tool seems to do it similar. So I would only count the green lines.
But I still think that this is not perfect either. I checked with my old Samsung Galaxy Ace and the Android location pointer which really gives points, no line at all when tapping shortly.

laufersteppenwolf said:
Xposed is a genious piece of work, however, this should be done via kernel.
Maybe @benkxda could have a chat with Fairphone about that?
Click to expand...
Click to collapse
I absolutely agree with you that this should actually be done on kernel/driver level. But I have no idea about Android's kernel structure or any driver layer at all. I used the Android SDK though. And unfortunately MediaTek is not giving all sources for the FairPhone
Where exactly do you expect touches to be evaluated and "forwarded" to Android? Do you have some example code of other phones probably? I am just interested how this works in software.

hanzano said:
I absolutely agree with you that this should actually be done on kernel/driver level. But I have no idea about Android's kernel structure or any driver layer at all. I used the Android SDK though. And unfortunately MediaTek is not giving all sources for the FairPhone
Where exactly do you expect touches to be evaluated and "forwarded" to Android? Do you have some example code of other phones probably? I am just interested how this works in software.
Click to expand...
Click to collapse
Sorry for the late answer, haven't seen you post
Well, kernel sources are quite easily structured, you've got the drivers, in there you find the input drivers, in which you also find the touchscreen drivers. in there are several drivers, you then need to find the correct one (in my case it's THIS file). In there are all functions to make your touchscreen work. This device also has a filter for "ghost" touches, just search for it inside this file
So, if you have located the driver of your device, you can there all needed stuff, such as the filter I mentioned

laufersteppenwolf said:
Sorry for the late answer, haven't seen you post
Click to expand...
Click to collapse
No prob
laufersteppenwolf said:
Well, kernel sources are quite easily structured, you've got the drivers, in there you find the input drivers, in which you also find the touchscreen drivers.
Click to expand...
Click to collapse
Ah ok, got it. In folder alps >> kernel >> drivers >> input >> touchscreen there are 68 files.
laufersteppenwolf said:
in there are several drivers, you then need to find the correct one (in my case it's THIS file).
Click to expand...
Click to collapse
Did you forget the link on "THIS" probably?
laufersteppenwolf said:
In there are all functions to make your touchscreen work. This device also has a filter for "ghost" touches, just search for it inside this file
So, if you have located the driver of your device, you can there all needed stuff, such as the filter I mentioned
Click to expand...
Click to collapse
Vielen Dank! Helps a lot

hanzano said:
Did you forget the link on "THIS" probably?
Click to expand...
Click to collapse
Ooops yeah, I did So HERE you go

Hello @Hyst
In the last week I was discussing with the support team pretty intensively about the touchscreen issue.
Now, they asked me to send them my phone, to see what happens on the device.
But, as I'm working abroad, its not that easy for me, to send it soon.
That's why I suggested, they should ask you, to get the IMEI of your old device - as you offered in the general thread.
Unfortunately Rick de Groot (the support guy) asked me again, to ask you for this number...
A little bit strange, but this is what I want to do now
Can you please send your old IMEI number and the RMA (repair form number) to this email:
<[email protected]>
That would be really great!
PS:
My Name is Florian W. if you want to quote me in your email.
Maybe this helps them to relate your email to my support request.
Thank you in advance!
Holzwurm86

Hi @Holzwurm86
sure thing. I've just send them an email.

Holzwurm86 said:
In the last week I was discussing with the support team pretty intensively about the touchscreen issue.
Now, they asked me to send them my phone, to see what happens on the device.
Click to expand...
Click to collapse
Good to see that there is still progress. The list of phones being affected gets bigger at the fairphone.com forum. If the engineers from Kwamecorp or Changhong need help like debugging or logging touches I am willing to help of course.