Related
Well I am interested in developing an app but would like to gauge some interest. Here are the details of the app:
1. App will take advantage of built in light sensors to read your lights lummens output.
2. App will have a nutrient calculator based on (advanced Nutrients, Canna, Dutch Masters, and General Hydroponics)
3. App will also include nutrient charts for all the companies.
4. App will include a DB of pictures with descriptions of different plant diseases and deficiencies.
I have more ideas as well as in how to optimize air flow for your room and much more also will include for outdoor growing as well.
If your interested in seeing an app like this for our winmo phones let me know through this thread and i will post updates and beta versions once they are ready if there is enough interest in something like this.
Sounds nice. Good luck.
seems good,
later i will be doing some project may be i can seek you help then
It seems nice
can be useful
All the best
it is coming along. right now the strain app supports WVGA 480 x 800 resolution. follow my progress in the thread in my sig. I should be about a week away for the MJ's Strain Guide beta. all that is posted right now is an alpha so you get a feel for the UI. Still a lot to do.
Sounds good! Being completely crap at maintaining plants this seems quite useful
I know what you mean. I hope this app helps guide people but when it comes down to it a major factor in your outcome is the genetics. bad genetics of a good strain will give you bad results. i am attaching here a alpha version of my strain app. its also located in the HD2 app section. im not sure it will work on other phones as i have a hd2 right now. I due plan to port to other resolutions and sizes after completion. It will be easier as its just resizing of what i have done. I am also bringing in some friend to port the app to android and iphone/ipad and to make a windows pc based version. if anyone has suggestions or think they can help in anyway let me know. i can always use the help.
PS:
This is the 4th app i have ever made in my life.
Notes:
when app is installed and launched you will get pop up menus. These are due to the controls. Currently they are trail controls. I am sending a payment to get the full license to that will be removed by beta.
currently all list are populated but no data is inputted so when you try to launch a strain in kinetic scrolling it will do nothing. Only one works right now. It is located in Sativa Strains List. It is Cannalope Haze. Let me know what you think of how the data is displayed. If you install this on WVGA device 480x800 it should work so HD2/TP2 should look perfect. Let me know what device you have it installed on and your screen fitment issue only if its WVGA. QVGA and WQVGA are not supported.
enjoy!!
Update:
I have attached a newer version it is the latest i have made so far. I have updated the indica and sativa list and updated how the data is displayed for cannalope haze. The way the cab is made is different so now it will ask if you want to install on sd or phone. I also finally added an icon for the app. i still have a long way to go but i hope you like where its going.
Hey Everyone...I haven't been around these parts often, but I conceived a pretty good idea [I think]...
My friend recently got a Droid phone, and of course he was flaunting it to me...I love Android, honestly...but I love Windows Mobile too. SO! I thought "Why not merge the best of both worlds?"
Well obviously, I cannot make windows look 100% like Android...that would take tooooooo long. So instead, I thought "What about the Task Switcher!"
So I introduce to you, CTaskManager
Right now it is just a P.o.C (Proof Of Concept), but I have done my research and found pretty much all the API calls I will need [minus one or two, but I'll find those]. It will be fully in C++, and if I can get it working correctly, will be activated by the HOME button.
Attached is a proof of concept image [100% Photoshopped, not real at all].
In any case, this is how I forsee it working:
This will appear on top of any window
Activated by pressing [and holding?] HOME
1st Box will always be the Home Screen
2nd Box will always be the current Window (unless it is the HomeScreen)
You can switch between apps with 2 easy Clicks
First Select the Number of the Dialog
Second, Press CENTER or SPACE to switch to it, or press DEL to quit that app
The program's layout will vary depending on the number of Open Windows
Should be light, fast, and easy to use
Hopefully, since I forsee this to be a really easy project, I will have a release by later today! I am making it for my Excalibur users FIRST, because I owe it to this whole forum [And because I will be switching to an HD2 this upcoming monday, and I want to start a project up for a phone I use NOW]
-Until Later: CycloneZephyrxz7
sweet...thanks..will wait for your release and then will added to the sticky.
I am very pleased that the ONLY component I have yet to get working is getting the screen captures [and window titles]. I need to investigate this ... For some reason, I am getting the same window drawn OVER and OVER again. I think it is because the window handle I am getting from some of the methods is invalid...Its very odd ... I have to figure it out. I should be able to do this winthin the next hour or so
seems cool so its like a multitasker? or somthing
alexrodri0 said:
seems cool so its like a multitasker? or somthing
Click to expand...
Click to collapse
Exactly.
So this is the update:
I got the program to run on Home-Key Press ... Now I am going to just modify it and add a timer or something to get it to run on Home-Key Long Press [since just a press interferes with Smart ToolKit]
An odd bug I have encountered is that when I run this, and wait, the Smart Toolkit taskbar shows up (as it should), and the whole phone locks up...I think it is because both are competing for Keyboard privilages. [I have to use a Keyboard hook to get this working, and it is all undocumented APIs]
I have yet to get the actual Task part working Haha. I can't confirm whether or not it is working, because for some reason my Debugger is acting weird, and all the images are of the current screen. As it turns out, it is impossible to take a snapshot of a minimized / partially visible screen. It will take the screen coordinates, and take a picture of whatever is there right now. I will get that fixed [I am talking to another Dev to see if he will let me in on how he does it in his task manager].
I got the "back" key escape working. Relatively simple.
I have planned out Layouts. Such that when you have JUST the HomeScreen open, it will NOT run. When you have the HomeScreen and 1 OTHER window open, the two will be split on the screen [Maybe make each like 150x113]. When you have 3 to 4 total windows (Including HomeScreen), they will make a 4-quadrant layout. Where each will be around [120x90]. When you have 4 - 6 open, each will be [92x69] (as shown in the ScreenShot) and have a 6-block layout. When you have more than 6 (if that is possible on the Excalibur haha), it will make a second page, and the second page will adapt to however many excess processes there are.
I have to work on getting the Translucent Background working ... that shouldn't be too hard, I just have yet to look into it {I think I have to use AlphaBlend or TransparentBlt}.
In any case, there is actually very little that doesn't work yet haha, but of course it is the most essential parts that don't work.
I will keep you all updated
sweet
looking forward to this, my phone will live on!!!
Thanks to a bunch of help from another Dev, I confirmed that getting the image of a non-visible window is IMPOSSIBLE on windows mobile. [Although it gives me an idea to try to 'fix' that haha ... maybe after this]. In any case, I think I have figured out how to do it. Tomorrow I will write up the code, test it, and hopefully have an Initial release.
The way I see it the releases will be as follows:
1) Initial Release [Basic]
2) Fix-Up of any Bugs
3) Add some Effects
4) Add some customizations
5) Fix-Up of any Bugs
6) FINAL
Hopefully, I can do this in 6 or less releases [And in the meanwhile, adapt it to work on my new HD2 i will get on Monday ]
*PS: For those of you following my projects: Once I get my HD2, I am going to make a fixed up release of FFP_LS, and then open-source it. Thereafter, i won't work much on it anymore. This is so I can start working on my SUPER-HUGE project called "CMessage" ... Here are the contents of the 'sticky note' i have on the desktop reminding me of it:
Suite of Programs:
1. Transport DLL (Send/Receive SMS/MMS/EMail)
2. T-Mail.exe Client (Compose/View SMS/MMS/EMail)
3. Notifier (When new Message Arrives, Display Alert)
4. A new DLL for the HomeScreen [it probably won't be compatible with the old one]
5. API Docs (For future use and adaptation)
6. Sample Programs (I.E. HomeScreen Panel, SMS Games, etc.)
7. Filter Rules Program
8. Macro Program (Get Message ... Do Action)
9. Environment Set-Up DLL/Exe [Cache Contacts, create Message Stores, transfer over old stuff, etc. etc.]
It is going to be a VERY large project. Hopefully, it will also be a very successful one Say bye-bye to CE MAPI?
Cyclonezephyrxz7 said:
Thanks to a bunch of help from another Dev, I confirmed that getting the image of a non-visible window is IMPOSSIBLE on windows mobile. [Although it gives me an idea to try to 'fix' that haha ... maybe after this]. In any case, I think I have figured out how to do it. Tomorrow I will write up the code, test it, and hopefully have an Initial release.
The way I see it the releases will be as follows:
1) Initial Release [Basic]
2) Fix-Up of any Bugs
3) Add some Effects
4) Add some customizations
5) Fix-Up of any Bugs
6) FINAL
Hopefully, I can do this in 6 or less releases [And in the meanwhile, adapt it to work on my new HD2 i will get on Monday ]
*PS: For those of you following my projects: Once I get my HD2, I am going to make a fixed up release of FFP_LS, and then open-source it. Thereafter, i won't work much on it anymore. This is so I can start working on my SUPER-HUGE project called "CMessage" ... Here are the contents of the 'sticky note' i have on the desktop reminding me of it:
Suite of Programs:
1. Transport DLL (Send/Receive SMS/MMS/EMail)
2. T-Mail.exe Client (Compose/View SMS/MMS/EMail)
3. Notifier (When new Message Arrives, Display Alert)
4. A new DLL for the HomeScreen [it probably won't be compatible with the old one]
5. API Docs (For future use and adaptation)
6. Sample Programs (I.E. HomeScreen Panel, SMS Games, etc.)
7. Filter Rules Program
8. Macro Program (Get Message ... Do Action)
9. Environment Set-Up DLL/Exe [Cache Contacts, create Message Stores, transfer over old stuff, etc. etc.]
It is going to be a VERY large project. Hopefully, it will also be a very successful one Say bye-bye to CE MAPI?
Click to expand...
Click to collapse
can't wait!
This program is actually bugging me...haha [get the joke?].
In any case, it is becoming rather tough to get this actually working. Correction: To get it working efficiently. The dev making the 3D iManager app over in the Development/Hacking forum told me how he is doing it, but to me it just seems terribly inefficient (every 5 seconds, check for Foreground Window....LOTS OF BUGS). In any case, I am using a registry notification now, since Windows Mobile has a value that tells me the currently active program and the previously active program [and it updates!] ... this works out because then I can take a screenshot of the new-ly active program, AND check to see if the old one was minimized or closed. Unfortunately, it doesn't seem to be working as I would have hoped.
I don't have much time today for developing [Hooray for a 50 Page AP Government Outline] ... so I will probably get back to this tomorrow [NEW PHONE], or maybe tonight if I get a really good idea/inspiration to finish this!
Cyclonezephyrxz7 said:
This program is actually bugging me...haha [get the joke?].
In any case, it is becoming rather tough to get this actually working. Correction: To get it working efficiently. The dev making the 3D iManager app over in the Development/Hacking forum told me how he is doing it, but to me it just seems terribly inefficient (every 5 seconds, check for Foreground Window....LOTS OF BUGS). In any case, I am using a registry notification now, since Windows Mobile has a value that tells me the currently active program and the previously active program [and it updates!] ... this works out because then I can take a screenshot of the new-ly active program, AND check to see if the old one was minimized or closed. Unfortunately, it doesn't seem to be working as I would have hoped.
I don't have much time today for developing [Hooray for a 50 Page AP Government Outline] ... so I will probably get back to this tomorrow [NEW PHONE], or maybe tonight if I get a really good idea/inspiration to finish this!
Click to expand...
Click to collapse
keep the good work man and again thanks for your effort in developing new stuff for the dash.
Cheers,
So I finished my work
But that isn't pertinent to this forum. What it does mean is that I can work on my developing for today!
Counter-to-my-prior-plan, I am going to release a pretty flawed version of the program ... errr ... rather an Alpha that will run much less efficiently than the final product.
I hate announcing a project, thinking it will be easy, then taking forever with it ... so this is what I am going to do:
I will use the same timer-based approach that iManager 3D uses, but I might make it update more often [3 second intervals maybe] ... it won't be AT ALL battery efficient, but it should be pretty memory efficient. It will serve as NO MORE THAN A PROOF OF CONCEPT OF WHAT THE FINAL PRODUCT WILL BE. The final product should not have a major impact on battery life, and should leave the end user unaware that it is actually running when it is!
I am re-installing Visual Studio because it has been acting up, but once that is done, I should be able to pump out an ALPHA VERSION.
EDIT: Computer Issues ... Expect a release in the coming days. Sorry for the inconvenience.
Cyclonezephyrxz7 said:
So I finished my work
But that isn't pertinent to this forum. What it does mean is that I can work on my developing for today!
Counter-to-my-prior-plan, I am going to release a pretty flawed version of the program ... errr ... rather an Alpha that will run much less efficiently than the final product.
I hate announcing a project, thinking it will be easy, then taking forever with it ... so this is what I am going to do:
I will use the same timer-based approach that iManager 3D uses, but I might make it update more often [3 second intervals maybe] ... it won't be AT ALL battery efficient, but it should be pretty memory efficient. It will serve as NO MORE THAN A PROOF OF CONCEPT OF WHAT THE FINAL PRODUCT WILL BE. The final product should not have a major impact on battery life, and should leave the end user unaware that it is actually running when it is!
I am re-installing Visual Studio because it has been acting up, but once that is done, I should be able to pump out an ALPHA VERSION.
EDIT: Computer Issues ... Expect a release in the coming days. Sorry for the inconvenience.
Click to expand...
Click to collapse
Great! This sounds awesome! And yeah, we finally get more interests and development in non-touch devices! Good luck with building the program and don't forget to contact the News-Writers when it's ready!
This is actually quite upsetting ... I tried re-installing Visual Studio, because it was no longer giving me the 'code suggestions' for C++ ... [like if I typed in a function, it didn't tell me what the parameters were] ... and now it isnt set up for Windows Mobile 6 Standard/Pro anymore. So i tried reinstalling those SDKs .... no joy....I am going to uninstall EVERYTHING OF IT and start all over [backing up my projects of course ].
Hopefully I will get my computer in working condition by tonight.
I got my new HD2 [TMOUS] today I am very happy with it already. BUT I WILL NOT GIVE UP ON MAKING THINGS FOR THE DASH. Non-TouchScreen phones are highly under-appreciated, and I hate that so much [let alone the fact that WinMo is underappreciated] .... I NEED YOUR IDEAS TO MAKE THIS PHONE [Exca] BETTER! So toss me a PM with even the wildest Ideas, and I will try to figure something out
Cyclonezephyrxz7 said:
This is actually quite upsetting ... I tried re-installing Visual Studio, because it was no longer giving me the 'code suggestions' for C++ ... [like if I typed in a function, it didn't tell me what the parameters were] ... and now it isnt set up for Windows Mobile 6 Standard/Pro anymore. So i tried reinstalling those SDKs .... no joy....I am going to uninstall EVERYTHING OF IT and start all over [backing up my projects of course ].
Hopefully I will get my computer in working condition by tonight.
I got my new HD2 [TMOUS] today I am very happy with it already. BUT I WILL NOT GIVE UP ON MAKING THINGS FOR THE DASH. Non-TouchScreen phones are highly under-appreciated, and I hate that so much [let alone the fact that WinMo is underappreciated] .... I NEED YOUR IDEAS TO MAKE THIS PHONE [Exca] BETTER! So toss me a PM with even the wildest Ideas, and I will try to figure something out
Click to expand...
Click to collapse
congrats with your new phone!
"Non-TouchScreen phones are highly under-appreciated, and I hate that so much [let alone the fact that WinMo is underappreciated]!" Yeah that sucks, that's also why I keep developing Apps and ROMs!
Hope you can get VS working again!
This is a short summary of some important general points for posting new ROM's.
It should be considered as an optional "add-on" to the general thread:
"Galaxy S I9000 Android Development **STICKY THREAD** Read here first!"
The number of man hours spent working and developing new custom ROMs are astronomical! So why then, is it that so few new ROMs are successful? Basically because of lack of information and poor public visibility/involvement of the developers themselves. It's just like in any other successful business, you have to make your product or service stand out from the rest. Either by making an amazing product or by being a great inspiration for others to follow. Here I will try to explain and list some fundamental ideas, in order to make your ROM better and more popular.
When a would be ROM flasher is looking around for a new ROM, he searches the web and the XDA-forums for threads, usually beginning with the text "[ROM]". Next he/she look at the FIRST page where the developer (and his/her team) is presenting the various features of their new design. What is presented there will often be a decision maker for whether or not someone wants to try it out.
There are a few things that consistently differs between "good" ROMs and "bad/poor" ROM's. These things are often and naturally related to the amount of information available around the ROM in question. Someone who have put down enough mind, sweat and hart into the production (cooking) of a ROM, would also like to share his/her effort in the best possible way, not minding writing a detailed and useful description about their product. The items found below are part of some of these things that do MAKE A DIFFERENCE.
- Primary Purpose:
Essentially a description why you want to provide this ROM and why you think it is needed. What are the main features and driving forces for providing this ROM?
- Ultimate Gaming Experience
- Super stability
- Super Compatibility
- Great Battery Duration
- Minimalistic User Interface (UI)
- Simple to use functionality
- Latest and coolest never seen before interface behavior
- Fully loaded with ultimate editions of absolutely everything
- Mobile Penetration Testing Platform
- or perhaps just for educational or experimental purposes etc...
- Up-to-date Maintenance:
That means an active developer (or group of) who are readily available to answer questions from users of all levels, new or advanced! Often that they should be inhumanly available at all times of the day & night!
- Up-to-date Firmware Release:
That means the the source of your ROM is preferably based on the latest, but publicly available code/firmware. Not on some hidden leaks or old hacked code. When I say "hidden leaks" here, I mean the kind where the origin of the code (compiled or not) cannot be verified or downloaded. (BMW doesn't make car/sales advertisements using 2 year old engines from unknown/secret sources!)
- Detailed CHANGE-LOG:
People want to know that what they flash on their phones, is as close as possible to what they would like to see and use. Also from a paranoia perspective most of us would like to know that it doesn't contain 3rd party or other strange applications that we will never use, or which will give us trouble when we want to add/update applications, at a later time. A description of the various applications is also very useful. Most people would wonder what the "DarkBotSendHelper.apk" is doing on a phone.
A change-log would ideally consist of a list with:
- Title: Change Date and the custom ROM Version the changes apply to
- Full application name
- Full application version
- Short application description
- Link to application source-code, if available
- Link to application on "Android Market"
- Reference to what hacks has been made, if any
- Reason for why the hack is needed
- Unresolved BUG-LOG:
A brief log of bugs and unresolved issues that affects the current release. It is hard to explain without cussing how annoying it is to flash a new ROM, just to find out that some WiFi issue has not yet been resolved, which was posted on page 456/1200! If people post bugs/issues, that cannot be immediately resolved, please add those issues to the BUG-LOG, on the front page.
- Screen Shots! Updated Screen Shots!
The importance of good screen shots can never be enough emphasized! Many ROMs are updated continuously and if the screen-shots doesn't match what the user installs, he's gonna go WTF!, and will start to peppering your support threads with questions about how to install this and that, and how to get the same themes you are using in those screenshots, or from another different ROM altogether! You wouldn't be able to sell a new BMW with a picture of an old Volvo, would you? So why do you think a ROM would be any different? Also include a brief caption about the essential feature(s) shown, for each picture.
- Detailed Installation Instructions
This hardly need more explanation apart for making sure you also say something about:
- WIPE/No-WIPE
- Bootloader Requirements
- Recommended Procedure
- Detailed Device Compatibility List
Yes, the same gross model name/number of a particular device, may very well have some minor variations that can render the device completely incompatible with software from it's apparent twin-brother. Or even certain Firmwares may not be compatible to slight manufacturing variation. See for example the "Samsung Galaxy S" with their sub-models GT-I9000(B/M/T), and to complicate things further, even within the same model there may be slight differences, like in the PCB of the USB-port of the SGS2 GT-I9100.
- Detailed Language Compatibility
What do people use their phones for? Communication! Sure, some use them as a game pad, but after all it is primarily a browsing and communication device. So if you can't use your primary languages with your device, it is useless! Although some network operators are only beginning to understand that most of the connected world is at least bi-lingual and often much more. Thus it is of essence that your phone's keyboard, screen-reader and web-browser can read, display and understand most characters and alphabets around. (I.e. I still fail to understand why it is virtually impossible to find a phone with Russian, English, Spanish and Norwegian keyboard layouts/character sets or at least let me select these my self!) In addition it is very confusing for a first-time ROM flasher to understand the need for all the various PDA/PHONE and CSC region settings, which are often modified and re-packaged for a well cooked ROM, and thus no longer adhere to the original regional code.
So when you cook your ROM, please provide as much information as possible regarding how the user can adapt their phone to his/her own languages. This information includes at least:
- What languages are available for basic operation (the operating system)
- What languages are available for the keyboard mappings
- What keyboard applications can use these languages (Swype, Samsung Keyboard etc.)
- Simple instructions how to include, use and set the phone languages
- List of Technical Terms and Definitions that describe the ROM
The world of mobile device development is packed by technical jargon and abbreviated terms. Many times they are also abbreviated and used in the wrong context, although some the community know what it means. Simplify your vocabulary and clearly define your terms and stay with community standard ones!
- General Presentation
Like any other business presentation, please skip the HUGE fonts in a zillion colors. Most of us are neither blind nor illiterate, but you may risk to come across as being both, with those type of fonts. Remember "KISS"? - Keep It Simple Stupid.
- SPELL CHECK!!
It's embarrassing and very annoying to read descriptions of how great, professional and how well maintained a particular ROM is, when the text is riddled with misspellings, wrong words and childish grammatical errors. Although most of us are very understanding that we are living in a multicultural and multilingual society, sometimes all I think about is, how a person who doesn't know how to spell check, could ever be able to cook a mobile phone ROM. Most text editors feature at least some basic spell checking, bloody hell, USE IT!
- CREDITS
Most of the Android development community is completely driven by voluntary and open source work. Make sure to include the correct credits to those persons who have contributed to the various info/hacks/software that you include in your ROM. Use a separate list for the credits, that include the name (handle) and how/what he/she did to contribute.
2 Good Examples:
http://forum.xda-developers.com/showthread.php?t=1350763
http://forum.xda-developers.com/showthread.php?t=1155776
Final Words:
It is very likely I have missed something here, or that you (as a developer or moderator) disagree on something I have written here, if so, please provide your constructive comments how I can improve this list and post.
In Great Expectations and Hope for Many New Amazing ROMs!
- E:V:A -
PS. This was posted in the "Developer Section" as it applies only to new ROM development threads, and I wouldn't consider this neither as "Q/A" nor "General". But if OP/MOD know of a better suited place, please just move it there...
Also I am not aware of a similar post to this one, even after searching XDA quite a lot. So if it already exists, it is not easy to find and should be reposted or stickied!
<Reserved>
@E:V:A
The only thing that I missed so far is a thread like yours.
Agree on all requirements of released software.
Sometimes I wonder how some "devs" priorities are stacked regarding quality control vs. early delivery on pay-per-download sites.
Not sure what is best place for this thread. Counting # of posts in General asking Q already answered in stickies, it's kind of accepted to skip reading what's there. :-\
Perhaps keep it alive as hottest thread here?
Tapatalked - There's a Thanks button somewhere
I like this
One thing you must add while promoting your ROM.. That is CREDITS.
Rahulrulez said:
I like this
One thing you must add while promoting your ROM.. That is CREDITS.
Click to expand...
Click to collapse
YES! Not giving credit where due is horrible, basically just forgetting all the hard work another individual has put in to the "feature" of your ROM. Also, this should probably be in general.
Hi, I'm Trent and I co-created AppThwack, a service for on-demand automated testing of Android apps on real devices. Basically, you upload an apk and a couple minutes later you get screenshots and logcat dumps from actual phones and tablets we host.
Beta Users Needed
We're currently looking for devs to join our private beta. You can message me or sign up on our website and I'll get a beta code to you shortly. We're trying to stress the system and make additions/adjustments so the service is as useful as possible for developers.
Current Features
Real phones and tablets: About 20 high- and low-end devices and we add a few more every week.
Fast: See results in real time. Full test runs on all devices takes a minute or two to complete.
Selectable default tests: Install, launch, UI Monkey, Cleanup
Configurable tests: For example, specify the number of UI Monkey events and seed the randomizer
JUnit including Robotium support via uploaded test packages
Screenshots in portrait and landscape on all devices
Logcat and filterable logcat viewer
High-level results sortable by device or test
Full stack-traces for any exception that occurs
Future
We're working on adding more test frameworks like monkeyrunner and more default tests, particularly performance tests that measure battery consumption, CPU usage, etc. We're also adding more data visualization and charting so it's easy to see what some of the gathered statistics mean.
We plan to launch soon, but the beta program will remain in effect even after that. The service will follow a freemium model. Again, the beta is free and we're going to keep it in place even after we eventually launch.
Inter-device automation
Our back-end supports device-to-device automation, so if you have an app or scenario that you'd like to test that involves multiple devices or interaction with other devices, even non-Android devices, let me know. We're looking for people to help us develop how this service will be exposed.
Edit: I can't post links, but if you search for "appthwack" you'll find it. Btw, I've apparently lurked since October, 2008. Yikes.
Just wondering will this support of testing apps that require root?
Also any chance we can see like a live pic of the device when it installs the app and opens it?
Sent from my VS910 4G using xda premium
motodroidfreak said:
Just wondering will this support of testing apps that require root?
Click to expand...
Click to collapse
Right now it does not and all of our phones are as close to stock as possible. I'll look into making it an option so we automatically root before your app installs and then un-root after the tests are complete. Root opens up some new possibilities, both good and bad, so I'll need to think about it.
motodroidfreak said:
Also any chance we can see like a live pic of the device when it installs the app and opens it?
Click to expand...
Click to collapse
Yes! The launch test takes a screenshot in both landscape and portrait. You can see all screenshots sorted by device by clicking "By Device" or "By Test" and clicking the "Screenshots" link in the blue box at the top.
Screenshots also show up in each launch test log so you can see the context as the shot was captured. Logcat dumps show up in the same place (Link from the blue box at the top will open a filterable and highlighted log viewer).
Alright thanks I'll try it out tonight
Sent from my VS910 4G using xda premium
Holy cow. Didn't realize such web service existed.
I just signed up and currently having a look around. Is it possible for me to join the beta? Thanks!
Is it possible for a "free" upgrade for my account? Heh just asking
EDIT : Created a new project. Then I'm stuck. The "Runs" tab is empty.
EDIT again : Oh.. uploading had error previously. Uploading again.
Very interesting project. Good luck to your team and I hope I can be a good beta tester
Realy interesting, for us, almost of our apps needs root access, so please think about adding root to your service
Test on my Sensation
Will test on my sensation
test
nullFactory said:
Hi, I'm Trent and I co-created AppThwack, a service for on-demand automated testing of Android apps on real devices. Basically, you upload an apk and a couple minutes later you get screenshots and logcat dumps from actual phones and tablets we host.
Beta Users Needed
We're currently looking for devs to join our private beta. You can message me or sign up on our website and I'll get a beta code to you shortly. We're trying to stress the system and make additions/adjustments so the service is as useful as possible for developers.
Current Features
Real phones and tablets: About 20 high- and low-end devices and we add a few more every week.
Fast: See results in real time. Full test runs on all devices takes a minute or two to complete.
Selectable default tests: Install, launch, UI Monkey, Cleanup
Configurable tests: For example, specify the number of UI Monkey events and seed the randomizer
JUnit including Robotium support via uploaded test packages
Screenshots in portrait and landscape on all devices
Logcat and filterable logcat viewer
High-level results sortable by device or test
Full stack-traces for any exception that occurs
Future
We're working on adding more test frameworks like monkeyrunner and more default tests, particularly performance tests that measure battery consumption, CPU usage, etc. We're also adding more data visualization and charting so it's easy to see what some of the gathered statistics mean.
We plan to launch soon, but the beta program will remain in effect even after that. The service will follow a freemium model. Again, the beta is free and we're going to keep it in place even after we eventually launch.
Inter-device automation
Our back-end supports device-to-device automation, so if you have an app or scenario that you'd like to test that involves multiple devices or interaction with other devices, even non-Android devices, let me know. We're looking for people to help us develop how this service will be exposed.
Edit: I can't post links, but if you search for "appthwack" you'll find it. Btw, I've apparently lurked since October, 2008. Yikes.
Click to expand...
Click to collapse
I would like to test the tool, can you share with me..
Tested
Tested the tool, seems too good..
Suggestion : In-case if you want to reach maximum number of developer. Allow developer to use has free.
IDEA : You can request developer to post about you're tool on there app page, website & play store... As you're giving the tool as free you will get enough number of people to view & use the tool.. if the developer agree then you will allow him to use the tool for free of cost..
As a developer am ready to use the tool & post about you in my app & other places too...
This is a great tool, just uploaded an apk of my app that's in my signature and it worked, with a couple of NullPointers from the Play Store's licence service. That shouldn't happen, and doesn't on any of my devices, so I suspect it's an issue on your end. Any idea why?
HTML:
java.lang.NullPointerException at com.google.android.vending.licensing.LicenseValidator.verify(LicenseValidator.java:99) at com.google.android.vending.licensing.LicenseChecker$ResultListener$2.run(LicenseChecker.java:228) at android.os.Handler.handleCallback(Handler.java:605) at android.os.Handler.dispatchMessage(Handler.java:92) at android.os.Looper.loop(Looper.java:137) at android.os.HandlerThread.run(HandlerThread.java:60)
HTML:
FATAL EXCEPTION: background thread java.lang.NullPointerException at com.google.android.vending.licensing.LicenseValidator.verify(LicenseValidator.java:99) at com.google.android.vending.licensing.LicenseChecker$ResultListener$2.run(LicenseChecker.java:228) at android.os.Handler.handleCallback(Handler.java:608) at android.os.Handler.dispatchMessage(Handler.java:92) at android.os.Looper.loop(Looper.java:156) at android.os.HandlerThread.run(HandlerThread.java:60)
Borland
We are using Silk Mobile for end to end applications testing. Do you ever used this tool?
What an interesting service! I'll look into this from work tomorrow.
Not having used this at all, the first things which do spring to mind are:
-streaming realtime logcat
-a (skype?) connection with live streaming video of the app running, so you can see layouts/animations etc.
Anyway, I'm going to check this out tomorrow!
Quinny899 said:
This is a great tool, just uploaded an apk of my app that's in my signature and it worked, with a couple of NullPointers from the Play Store's licence service. That shouldn't happen, and doesn't on any of my devices, so I suspect it's an issue on your end. Any idea why?
Click to expand...
Click to collapse
Thanks for checking out the service. My immediate guess it that this is caused by the absence of a default Play account. Many devices have no account as one of our supported frameworks, calabash, removes accounts upon cleanup after script completion. On the plus-side, if you were to write scripts you should be able to add a temporary account from the test itself.
Highly unlikely you'd hit this bug in a real world situation, but it is a bug nonetheless.
Really awesome service! Can't test it for the moment as it doesn't support root apps, but this is really a great concept :good:
Maybe you could build a superuser permissions manager which would grant root access but makes sure to keep /system mounted as read-only, this way no harm could be done to the devices and us root apps devs could use your awesome service.
I actually got quite a few ideas, you could delete the mount binary in /system/xbin and use it in an internal appthwack app's private data, so that it's the only app able to call this binary and thus to mount /system.
I'd definitely subscribe to AppThwack if it had root support.
If you want help with developing this kind of secure root environment for the testing, I'd gladly contribute.
EDIT : Strangely enough, I just tested it with my app (which asks for root in the launcher activity, so I really didn't expect it to work) and had 0 failures, 75 pass.
How comes ? Have you already added root support ?^^
Either way this is really cool, I'm going to spread the words and most likely subscribe a paid account :good:
Is there somewhere we can see pictures of your device lab? Gotta be one hell of a device museum you got over there^^
Androguide.fr said:
Really awesome service! Can't test it for the moment as it doesn't support root apps, but this is really a great concept :good:
Click to expand...
Click to collapse
Awesome, thanks for the kind words!
EDIT : Strangely enough, I just tested it with my app (which asks for root in the launcher activity, so I really didn't expect it to work) and had 0 failures, 75 pass.
How comes ? Have you already added root support ?^^
Click to expand...
Click to collapse
This is pretty interesting. The only two rooted devices are a couple running CM. I'll look into this further, and if you have any ideas I'd love to hear them as well.
Either way this is really cool, I'm going to spread the words and most likely subscribe a paid account :good:
Is there somewhere we can see pictures of your device lab? Gotta be one hell of a device museum you got over there^^
Click to expand...
Click to collapse
Sweet, I really appreciate it. As soon as I have the number of posts to do so I'll post a pic of the lab.
Some things can not be automated, like scanning a QR code or reading/writing to an NFC tag. Do you plan on adding "manual tests" for a fee?
This would be really great to test apps on specific hardware.
worldtiki said:
Some things can not be automated, like scanning a QR code or reading/writing to an NFC tag. Do you plan on adding "manual tests" for a fee?
This would be really great to test apps on specific hardware.
Click to expand...
Click to collapse
Thanks for the question! Our primary focus is on automation. There are existing test houses and services that will execute manual tests like those you describe, but of course because of the manual component they're slow and expensive.
We often push folks to break their testing down into more granular chunks. For instance, verify you can take a picture and deal with the image, even if it's not the QR code or whatever your app usually consumes. This will find problems with simply using the camera and resulting image location. Now, have a separate test that processes a photo of a QR code, but feed the image in as part of the test. This removes the camera component from the analysis part, meaning it's now possible to benchmark the image analysis algorithm on all devices.
With a combination of a service like ours where you test very, very quickly on tons of devices, you can now do some more UX/end-to-end tests on a handful of devices yourself. This hybrid approach is great for finding the vast majority of issues before release.
nice post
Realy interesting, for us
Awesome tool !
No Developer can test his/her app on many devices. But your tool ... A W E S O M E ! ... I Used it yesterday to test two of my new apps ... Found some error is my app on certain devices which i'd have never found without AppThwack .. :good: :good:
Alright guys. Heres a little project I have been working on that I think will all save us some time. If you remember the RDF finder I wrote in the past. It was pretty quick and dirty and you needed to run it on Windows and have the snippet compiler installed and was C# based. It worked but probably wasnt the most ideal solution. So I figured want not write a better android version. So thats what I did and hear it is. Febby if you like it and want to link it to the OP thats cool. Feel free to PM any bugs you find guys. And before anybody asks why not use the /latest URL format to grab the latest RDF. Well I am sure you all know there are many occasions when /latest is NOT always accurate. So this tool will basically attempt a brute force scan for any range you specify to hunt for RDF's.
Usage Instructions:
-Download and install
-Use a range (does not need to be known range) for example:
FJ00 - FJ31 would scan for all RDF files dropped in the month of October (as of this writing there are only drops for Virgin mobile)
-Press Find
-When search is complete a dialog will be displayed letting you know. The output textbox will contain the results of the scan.
Enjoy!
Updated 10/5/2012
-Bug fix around upper casing range codes. Now happens on Find press
-Added Quit menu item which can now be selected via the menu button to exit the app gracefully.
ATTACHED THUMBNAILS
Reserved..... Cause everyone does this...
Awesome work! Thanks!