search

Azurami / wagic

Automatically exported from code.google.com/p/wagic
Other
0 stars 0 forks source link

Wagic hangs after unlocking phone (Android) #929

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Launch Wagic
2. Lock phone
3. Unlock it

What is the expected output? What do you see instead?
Actual result: Wagic hangs and force closing window appears

Expected result: Wagic will open its previous window.

What version of the product are you using? On what operating system?
Issue was successfully reproduced using latest Wagic 0.18.6 on Android 
4.1.2(Samsung Galaxy S i9000)

Please provide any additional information below.
Screenshot and log attached. Tried to wait couple times via force close window 
but unsuccessfully.

Note: I will be glad to help you in testing and maybe even in coding also.

Original issue reported on code.google.com by vladimir...@gmail.com on 11 Jan 2013 at 1:18

Attachments:

GoogleCodeExporter commented 9 years ago 
my phone is Samsung Galaxy Ace S5830 on Android 2.3.6 using wagic 0.18.6 svn 
r4515 and it works great even locking it. I'll try to compile on latest svn and 
see if there is an issue like that... anyway what revision are you using? 
official?

Original comment by anthonyc...@gmail.com on 11 Jan 2013 at 6:08

GoogleCodeExporter commented 9 years ago 
Sure I use latest official release. Just tested it with Galaxy Ase 
S5830(android 2.3.3). Issue appears the same

Original comment by vladimir...@gmail.com on 11 Jan 2013 at 10:52

GoogleCodeExporter commented 9 years ago 
I think this is fixed in the current SVN, rolzad73 fixed it on r4490, I think 
the official 0.18.6 is r4457 which has this bug. I will keep this open for a 
little while.

Original comment by anthonyc...@gmail.com on 11 Jan 2013 at 11:11

GoogleCodeExporter commented 9 years ago 
It does sound like the issue that I fixed.  Does anyone know when the plans for 
another official build is?

Original comment by rolzad73@gmail.com on 18 Feb 2013 at 4:42

GoogleCodeExporter commented 9 years ago 
I am using the latest (r4862) svn build right now and can confirm that the 
issue still appears. (I have Samsung Galaxy S3)

Original comment by pank...@gmail.com on 25 Sep 2013 at 8:04

GoogleCodeExporter commented 9 years ago 
pank.dm,
could you reproduce it and attach a logcat?

Original comment by rolzad73@gmail.com on 26 Sep 2013 at 2:14

GoogleCodeExporter commented 9 years ago 
I decided to doublecheck and build and install again the last revision. And 
couldn't reproduce it. Sorry for bothering you. Probably I was mistakenly using 
not the last build.

Original comment by pank...@gmail.com on 26 Sep 2013 at 8:59