• Welcome to SpeedSolving.com — the world’s largest puzzle community!

    You’re currently browsing as a guest, which means you have limited access to discussions, resources, member profiles, and community features.

    Join 50,000+ cubers and puzzle enthusiasts from around the world to ask questions, share solves, improve faster, and be part of the community.

    Registration is free, fast, and easy — create your account today.

    Already a member? Log in here to hide this message and start participating.

plusTimer - Open Source Android Timer with TNoodle Scrambles

The bug should be fixed in version 0.2.4. I've added your suggestion to the GitHub page: https://github.com/plusCubed/plusTimer/issues/35. Thank you!



Thanks you for that! I've actually just released 0.2.4 which has some new strings (temporarily for now they are just English) - if you could translate those that'd be great!



Fixed in 0.2.4. Thanks for reporting!

-------------------------------------------------------------
v0.2.4 released! I've added a few new settings, including scramble text size and preventing swiping between the tabs. Many bug fixes were made too.
You can check out the full changelog at the GitHub page, and the Google Play update should come out in 1 or 2 hours, as usual.

Again, if you would like to translate plusTimer into another language, please go to the Crowdin Page!
Thanks for everyone's continued support!
Looks perfect. I really appreciate the time and effort you take to make it bug-free! :)
 
v0.2.4 released! I've added a few new settings, including scramble text size...
Glad to see this new setting has been added. Up until now I haven't been able to make use of this app because the resolution of my device is so high that the default scramble text size is hard on my eyes, so this should help.

One thing I've noticed, however, is that instead of displaying the scramble text size in the settings page as intended, it is actually displaying whatever the timer text size was when you opened the settings page. I'd guess that it's an artifact of using copy and paste while coding. You copy code from one place to another, intending to adapt it, but end up forgetting one of the changes. I've made the same sort of error a number of times. :cool:
 
Looks perfect. I really appreciate the time and effort you take to make it bug-free! :)

Thanks!

Glad to see this new setting has been added. Up until now I haven't been able to make use of this app because the resolution of my device is so high that the default scramble text size is hard on my eyes, so this should help.

One thing I've noticed, however, is that instead of displaying the scramble text size in the settings page as intended, it is actually displaying whatever the timer text size was when you opened the settings page. I'd guess that it's an artifact of using copy and paste while coding. You copy code from one place to another, intending to adapt it, but end up forgetting one of the changes. I've made the same sort of error a number of times. :cool:

Yup, I realized almost as soon as I pushed the update :p... It's not a deal-breaker, so I'll let it sit while I add new stuff (fixed in the code already, but... yeah...haha)
 
Two things. Firstly, I'm done with the Korean translations. They're not perfect, since I don't have cubing experience from Korea and thus don't quite know the exact terms they use (for example, I'm not quite sure how they differentiate between mean and average), but they'll work.
Secondly, my data seems to be corrupted. I get a weird error when I open the app, saying that the scramble history could not be read. Can't access the last day's solves because of it. Thankfully I have daily backups of all my files, but an entire day's solves is quite a lot to lose.
 
I see. That reminds me, is there a way to start the timer before the scramble has generated because I normally hand scramble 7x7 and it can take a little while to load the scramble.

No, not currently. Good idea though - I've logged it here: https://github.com/plusCubed/plusTimer/issues/36.

Two things. Firstly, I'm done with the Korean translations. They're not perfect, since I don't have cubing experience from Korea and thus don't quite know the exact terms they use (for example, I'm not quite sure how they differentiate between mean and average), but they'll work.
Secondly, my data seems to be corrupted. I get a weird error when I open the app, saying that the scramble history could not be read. Can't access the last day's solves because of it. Thankfully I have daily backups of all my files, but an entire day's solves is quite a lot to lose.

Thank you for the translations, I'm sure they'll be fine! (as for mean and average, if Korean is anything like Chinese, it may be able to be translated like "average" and "average with ends removed"). As for the corruption issue, if you happen to have root on your Android device or have the corrupted files, please PM me - I'd like to take a look. Thanks!
 
Hi, I started using this timer about a week ago, and it is almost perfect I have to say. One issue that I have came after the last update, sometimes it keep crashing when I want to open the history of a certain puzzle, after submitting my solves. The data isn't lost however, so it's not that bad. I sent a crash report, maybe it helps.
The other things is a feature that I miss: it would be great to see in the history, how many solves I did, maybe in a graph too. Sometimes I do only three solves in a session, then twenty in an other, and can't tell later which is which.
If you could include this type of stats, it would be perfect.
 
5x5 always crashes, now I tried to add a time manually, and an error came up: solve #0 doesn't exist.
Can I fix it somehow?
if I reinstall the app, will I lose all my times?
 
Hi everyone,
I'm sorry about the lack of updates over the past 2 months. I've been working on various other app projects and such, so plusTimer had been sitting in the dust for a bit. Now that summer vacation is here, I plan to work on plusTimer a lot more.

For everyone having the history crashing issue, hold on tight, I'm working on completely re-writing the history system using databases. For now, if you go into About, press "Email History Data to Developer", and email a copy to yourself, that data will be salvageable later (I'll most likely write a tool for importing the old data into the new database structure) - then try wipe the data for the app to fix the crashing problem.

Thanks!
 
v0.3.0-beta1 is out! Finally switched to SQL (database) for storing solve data, which basically means the issues with storing large amounts of solves, crashes, etc. should be much better now.
In this first beta, you will NOT be able to access your old solve data using the History section!
Due to this I've decided not to upload this release to Google Play (even as a beta).

The history data will still be on the device. You can use the Email to Developer button in the About section to backup your data - I will be writing the transitioning code in the next beta.

Download link is at the GitHub releases page here: https://github.com/plusCubed/plusTimer/releases
Please join the Google+ community for beta testing later: https://plus.google.com/u/0/communities/113562908027612647654

Thanks everyone!
 
Back
Top