search

laito / droidstack

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

Unable to leave reputation activity #28

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. receive rep notification
2. click it
3. try to get to the sites activity

What is the expected output? What do you see instead?

I'd expect the back button to go back to the site picker. Instead, the app 
closes.
Unfortunately, starting the app from the menu again lands me in the replist 
screen, and using the backbutton.... you guessed it drops me out of Droidstack 
completely.

What version of the product are you using? On what operating system?
droidstack 1.0-11a

Please provide any additional information below.
Android 2.2, HTC Desire HD

Original issue reported on code.google.com by sghee...@gmail.com on 1 Apr 2011 at 12:05

GoogleCodeExporter commented 9 years ago 
The app closing when first pressing back (after clicking the notification) is 
normal (it takes you *back* where you came from -- the homescreen).

However, it is not normal that the next time you start the app from the app 
drawer it starts in the replist. It might very well be an HTC bug.

Does the third time work (if you try to launch it from the app drawer a second 
time)? If yes, it means it's a problem with how HTC launches stuff from 
notifications.

If not, does killing the app (from a task killer or Settings -> Applications -> 
Manage Applications) help?

Original comment by felix.og...@gmail.com on 1 Apr 2011 at 12:18

GoogleCodeExporter commented 9 years ago 
No a third time launch (and subsequent) doesn't improve things

No a kill (using Advanced Task Manager) doesn't seem to help. A reboot does.
I'll see if I can find additional ways to 'unwedge' the situation, and post
info if I do

Seth

Original comment by sghee...@gmail.com on 1 Apr 2011 at 1:58

GoogleCodeExporter commented 9 years ago 
Just confirmed: killing driodstack with Advanced Task Manager does _not_
solve the situation

Original comment by sghee...@gmail.com on 1 Apr 2011 at 2:00

GoogleCodeExporter commented 9 years ago 
Are you running any kind of custom ROM? I'm going to try this on a friend's 
Wildfire, in hoping the OS is similar enough to duplicate the problem.

Original comment by felix.og...@gmail.com on 1 Apr 2011 at 2:01

GoogleCodeExporter commented 9 years ago 
Shute. I wasn't very exact there: it _does_ help for launching from the app
menu, but still not when picking droidstack from the "recent apps" list
(longpress the home-button or top button bar in notification screen)

So this is possibly confusing a bit. After successfully launching the main
screen from the app menu again, the buttons in "recen apps list" also take
me to the main screen of droidstack.

So currently the steps would be:

to wedge

   1. get a rep notification
   2. click notification
   3. land in reputation activity of droidstack

no way out now, except, to unwedge:

   1. kill droidstack process
   2. start it from the 'global' app menu (important!)
   3. all further launches are ok, until you wedge it again :)

HTH
Seth

Original comment by sghee...@gmail.com on 1 Apr 2011 at 2:05

GoogleCodeExporter commented 9 years ago 
Not running custom rom. 

Model number: HTC Desire A9191
Android 2.2

Baseband version: 12.28b.60.140eU_26.03.02.26_M

Kernel 2.6.32.21-gf3f553d htc-kernel@and18-2 #1 Thu Oct 28 13:23:11 CST 2010

Build number 1.32.405.6 CL278359 release-keys

Software number: 1.32.405.6

Browser version: 3.1

Original comment by sghee...@gmail.com on 1 Apr 2011 at 2:08

GoogleCodeExporter commented 9 years ago 
It would make sense for it to launch the replist if picked from the "recent 
apps" list (it takes you where you last were in the app), although the "google 
experience" doesn't do this.

One thing is still not 100% clear. Do you _need_ to kill droidstack before 
launching it from the app drawer in order to unwedge it? Or does the problem 
_only_ occur when using the recent apps list?

Original comment by felix.og...@gmail.com on 1 Apr 2011 at 3:25

GoogleCodeExporter commented 9 years ago 
ermmm it _was_ not unclear (I mentioned I _had_ to explicitely). However, I
just retried and this time it _did_ go to the main screen.
Feel free to close the bug, I'll reopen if I can reproduce it

Original comment by sghee...@gmail.com on 1 Apr 2011 at 3:30

GoogleCodeExporter commented 9 years ago 
Thanks for taking the time to test this.

Original comment by felix.og...@gmail.com on 1 Apr 2011 at 9:50