Obsolete
Status Update
No update yet.
Comments
kp...@gmail.com
Sounds like the same thing as my
kp...@gmail.com
Sounds like the same thing as my
ja...@yahoo.com
Seems like same problem for me, nexus one, stock froyo 2.2.2.
wb...@gmail.com
Appears to be a duplicate of
(It looks like
(It looks like
je...@gmail.com
[Comment deleted]
je...@gmail.com
I have been using my Nexus one, Android Version 2.2.2, build number FRG83G, since December. I had no problem moving icons on the screen for two months.
Lately, I think after the latest update asking to restart the android (several weeks ago), I noticed that I was not able to move the icons and widgets any more, that they would either refuse to move, disappear or be moved to some random folder on another screen (hence seemingly disappearing), and that even when there was a single icon on an otherwise empty page.
At first I thought it was a general bug which would be corrected by a following update, but it has been some time now, and googling for such bug did not yield any result, so that I first thought that I was the only one suffering from such a problem: I am glad to have been pointed out to this bug report, which seems to describe exactly the same situation.
Lately, I think after the latest update asking to restart the android (several weeks ago), I noticed that I was not able to move the icons and widgets any more, that they would either refuse to move, disappear or be moved to some random folder on another screen (hence seemingly disappearing), and that even when there was a single icon on an otherwise empty page.
At first I thought it was a general bug which would be corrected by a following update, but it has been some time now, and googling for such bug did not yield any result, so that I first thought that I was the only one suffering from such a problem: I am glad to have been pointed out to this bug report, which seems to describe exactly the same situation.
gi...@gmail.com
Still a problem for me in 2.3.3
tr...@gmail.com
Have the same problem with Nexus S running 2.3.2
bl...@gmail.com
Same problem on brand new Nexus S 2.3.3 (I changed it as I thought it was the device screen)... same problem on the second one (LCD screen)
do...@gmail.com
Same issue with Nexus S 2.3.3
pf...@gmail.com
This issue has not been fixed in 2.3.4 either.
ke...@gmail.com
Just had this exact problem happen for me on my NEXUS ONE no more than an hour after updating to 2.3.4 (Gingerbread MR2 2.3.4 was the update name).
So no, still not fixed on 2.3.4.
So no, still not fixed on 2.3.4.
bi...@gmail.com
[Comment deleted]
bi...@gmail.com
For the past year at least this same has been happening to me as well. I have had my Nexus One since January 2010.
It seems to get have gotten worse lately. It use to be that if I rebooted, then dragging and dropping a shortcut would work properly for a while and then after the system had been running a while, the problem would occur. Now, the problem happens immediately after a reboot even.
I am currently running Android 2.3.4. Still same problem.
It seems to get have gotten worse lately. It use to be that if I rebooted, then dragging and dropping a shortcut would work properly for a while and then after the system had been running a while, the problem would occur. Now, the problem happens immediately after a reboot even.
I am currently running Android 2.3.4. Still same problem.
ru...@gmail.com
[Comment deleted]
ru...@gmail.com
I have my N1 sinceApril last year and I am also having this bug, I had my screens full of icons and now they are all almost gone!! What the Hell
"It seems to get have gotten worse lately. It use to be that if I rebooted, then dragging and dropping a shortcut would work properly for a while and then after the system had been running a while, the problem would occur. Now, the problem happens immediately after a reboot even." plus one
C`mon Google do something I do not have time to root my phone neither to arrange an alternatice Launcher abñd rearrange all again, This is a big bug Asap fix needed
"It seems to get have gotten worse lately. It use to be that if I rebooted, then dragging and dropping a shortcut would work properly for a while and then after the system had been running a while, the problem would occur. Now, the problem happens immediately after a reboot even." plus one
C`mon Google do something I do not have time to root my phone neither to arrange an alternatice Launcher abñd rearrange all again, This is a big bug Asap fix needed
kr...@gmail.com
I know this isn't a fix, but you don't have to root your phone to install a
different launcher. This big pissed me off one too many times and I just
installed the free version of "launcher pro" and haven't looked back since.
There are plenty of other launchers in the app store as well if launcher pro
doesn't work for you.
That said, this really does need to be fixed.
Jay Deiman
rebooted,
bug
different launcher. This big pissed me off one too many times and I just
installed the free version of "launcher pro" and haven't looked back since.
There are plenty of other launchers in the app store as well if launcher pro
doesn't work for you.
That said, this really does need to be fixed.
Jay Deiman
rebooted,
bug
bh...@gmail.com
Same issue with my LG Optimux 2x running Android 2.2.2 - thought I was going mental because my icons kept disappearing and only a reboot would show where they actually are. Have gone to another launcher since it's a very annoying bug.
sa...@google.com
Thank you for your feedback. We assure you that we are doing our best to address the issue reported, however our product team has shifted work priority that doesn't include this issue. For now, we will be closing the issue as won't fix obsolete. If this issue currently still exists, we request that you log a new issue along with latest bug report here https://goo.gl/TbMiIO .
Description
To replicate:
Open the App Tray (pop-up window of all installed apps) and press and hold one icon to drag it to a home screen. Locate the final position and release. This should locate the icon on the visible home screen in the location you released it. In some conditions though the icon will just disappear seeming to have been deleted. Often frequent attempts to place the icon in the same location will result in the same effect, the icon disappears.
Here is what is happening: The 'drop' functionality is confused as to what page it is currently on. IF there is a folder located on another home screen in the same X and Y position as the desired location on this home screen the icon will be added to that folder instead. Repeated attempts to add the icon to the same location will result in multiple icons being added to that folder on the other screen.
What makes it even more mystical is this. It seems that even though the icon has been added to the wrong folder, the 'refresh' routine for that folder's UI is never called, so opening that folder immediately after will not show the 'missing' icon. However if the device is rebooted all of the 'missing' icons will now appear in their folders since the folder contents have been reloaded.
Unfortunately I have not yet been able to figure out what conditions cause this to happen. Frequently I can add icons with no issues but then suddenly the problem will begin to occur and it is 100% repeatable there-after.
I should also mention that using the home screen options menu to add an application shortcut (vs. using the app-tray to drag it out) does not exhibit this bug. This is my present work around to the issue.
Step by step reproduction:
1. Choose 2 home screens...
2. On home screen A add a blank folder in the 1x1 icon position
3. Change to home screen B and open the App Tray
4. Press and hold and icon to drag it to the 1x1 position of home screen B
5. Release the icon and it disappears
6. Open the folder on home screen A and it will be empty
7. Reboot the OS and open the folder on home screen A and the icon will be there.
Work around:
Use the "Add" function on the home screen options menu to add a shortcut. Works every time no matter the icon location, even when the above bug is happening.
If I can narrow down the conditions that start this bug occurring I will further update this report. At the moment on my device it seems to be about 40% of the time on average.
I am a developer and available to aid in testing if so desired.