1 / 6

Week Goals: Database Usability Testing & Memory Leak Detection in Android App

This week, we will focus on testing the database's usability, particularly with SQLite in our Android application. We face challenges with memory leaks that escalate our app's memory usage, potentially leading to crashes. As we work to finalize the user interface (UI), we need to link the database effectively and incorporate necessary building floor plans. Key tasks include resolving memory issues in our database algorithm, fixing non-Java related errors, and enhancing the UI post database linkage. The final goal is to have a fully functional room locator.

romney
Télécharger la présentation

Week Goals: Database Usability Testing & Memory Leak Detection in Android App

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ECE 495 – Room Locator Aabhas Sharma Yehia “Yaya” Khoja VinayakGokhale

  2. Goals for the week - Test the data base for usability SQLlite Memory Leak Detection

  3. SQLite • SQLite databases can only be supported with a max filesize of 4.5 MB. • SQLite databases are local to the application in Android and doesn’t handle well with inter-application linking. • To examine the database you want to use the Android Debug Bridge • Through shell, you can reference the tag and check the database. • Example – sqlite3 database.db • Please refer to - http://www.screaming-penguin.com/node/7742 for an amazing tutorial

  4. Memory Leaks • The biggest hurdle while developing applications is MEMORY LEAKS. • They’re lines in your code that cause the following: • Your program uses memory that it is unable to release, which becomes a vicious cycle. • Your program will keep eating more and more memory and will keep accessing the ‘ram’ and will keep using up the battery and slowly it will drain your phone of the battery and crash its OS. • If you see the ‘Application Crashed’ message its PROBABLY a memory leak. • Read about it here - http://groups.google.com/group/android-porting/browse_thread/thread/9c84baa10cebbb68?pli=1 • Andhttp://developer.android.com/resources/articles/avoiding-memory-leaks.html

  5. The UI • The UI is almost complete. Some minor changes required once the database is linked (we still need the floor plansof the MSEE and EE buildings). • Once the plansare acquired, the arrays for the buildings and floors will be completed. • The plans will then be uploaded into the database and arrays in the UI will be modified. • DONE!

  6. Next four weeks – Complete the database – We currently have a memory leak occurring in the algorithm for the database. Needs to be fixed. Need to fix some non-java related errors – eclipse and recognizing android on some machines. Modify the UI to fit – Once the aforementioned errors have been fixed, we will need the floor plans (Prof. Allebach and Prof. Delp!!!!). Once the floor plans have been acquired, we need to add the buildings and floors to the user interface.

More Related