Database Users

FroYo update- software issues fixed & should be fixes

People running on 2.2 please let the world know about software issues which were fixed. Which weren't fixed?

Since this is only a test-version of Froyo, some issues are still to be ironed out on the final OTA release.
But so far what i have found:
-Wi-Fi always on [fixed]
-Volume speaker and music audio playback seems louder
-Bluetooth issues seems fixed (i don't use BT but have read things are working now)
-Better 3G (for some.. all dependable on your area)
-Improved capacitive buttons response

Also message delivery reports seem to work now.

No crazy screen either that required turning off screen then back on.

The issue that i have is that the screen sometimes won't wake up. You have black screen but the lights of the buttons go on. Next sometimes ot doesn't recognize the sd card ( 16gb class 4) reboot fixes it.
For the rest i'm very pleased with the phone many issues are fixed. Battery life is also great.
-------------------------------------
Sent via the XDA Tapatalk App

i downloaded the froyo update from the phandroid website. the first 3 days no complaints , but since last night the phone froze 5 times. uninstalled flash 10.1 and the phone is working ok now.

hope they'r listening
hope google is listening, to fix this before the official OTA update is out!!!
keep this goin guys i think this would address alot of issues n1 froyo is having.
*maybe hackers could even find a fix for our issues!!!!

-Crazy screen is still here, yesterday night I couldn't use some widgets because they were opening menus,nor shut it down unless taking out the battery.
-Volume is louder but just 5% while we need at least +25%
-No 4-5x faster menus
-No trackball wake or color config
-No FM radio
...

vegetaleb said:
-Crazy screen is still here, yesterday night I couldn't use some widgets because they were opening menus,nor shut it down unless taking out the battery.
-Volume is louder but just 5% while we need at least +25%
-No 4-5x faster menus
-No trackball wake or color config
-No FM radio
...
Click to expand...
Click to collapse
?4-5x faster menus?? JIT being there and menus opening faster have not much in common.
trackball APIs are there and are accessible. they are just not used in the google apps. devs are free to use them.

There will be bugs in everything. I for one think this rom has very few.

Especially pre-release ones.
Not that I have anything to complain about really though

I get handies from my phone now.

as someone pointed out earlier the crazy glitch screen is still in the Froyo test build..i sure hope this gets ironed out.

JCopernicus said:
I get handies from my phone now.
Click to expand...
Click to collapse
Haha you to?!? I thought I was the only one!

Well I noticed when I send a text or type something and Android doesnt know the word I get an option to add the word to the dictionairy. Also I can now take pictures and upload to FB while listening to music (music would stop playing when I opened the camera). Little things like this makes me proud to be a N1 owner =D

Market is veeery slow, not fixed yet
(used 2.2 rom from Paul)

Two things for me in the google chat/Talk app that are really frustrating -- can anyone reproduce???
1) Voice input in Talk app: If you rotate the screen at the same time as you are speaking a voice input, it cancels the voice input -- i.e. start talking and then accidently rotate the screen and it doesn't process.
2) You can no longer send messages when you don't have service. In the past, you could access messages and buddy list and draft messages that would be sent once you regain service. Now you just get the connection error. Can't even read messages :-(

10 things that I hate about Gingerbread!

I really wonder why there is none of such thread here!
Gingerbread unfortunately brought only bad things to my Nexus. I already forgot why I was so crazy about installing it.
What feature did it introduce again?
Okay the response is much better and everything seems faster...but with lots of bugs?
That screen off animation? Seriously?
Things that I hate now:
- Battery Time: this is bad, can't even run half a day with lot of usage, b
efore I could listen to mp3's one day, ie. more than 4 hours without any problems...now
- Camera: either Cam or Video, the application crashes after I take a photo or video and then I can not connect to it anymore
- Gallery: often crashes, especially if you have an online photo account connected
- unlock screen: I use a pattern, often there is no overlay of what pattern I drag, still the screen can be unlocked
- Market: even if automatic updates activated, it only updates if you open the market and go to the "my apps" tab
- 3G and Wifi: if you are connected to wifi more than 15 minutes and then disconnect from it you do not get any 3G, you have to go to airplane mode and back, this bug appeared ages ago and was fixed, now back again...tells you a lot about their merging control, ie. sucks
- notification led: you know...
- apps: there are a lot of apps running even though I never used them since restart (see it in a task killer app)
- gps: on a random bases it tries to lock even though no app that uses gps is running
- phone reboot: it even rebooted without any notice two times since I installed it
(- Contacts: I still can't enter a simple thing like a birthday on an expensive phone like this)
MOD EDIT: Borderline trolling removed. If you switch OSes, that's your own choice. No one here is stopping you.
Got any troubles? Tell here.

DarsVaeda said:
1. Battery Time
2. Market: even if automatic updates activated, it only updates if you open the market and go to the "my apps" tab
3. notification led: you know...
Click to expand...
Click to collapse
4. Blank keyboard- fixed by switching to another keyboard and back again, or a reset
5. Blank Launcher- fixed with reset
6. In the stock SMS app a long press>delete conversation doesn't always delete the selected conversation; sometimes you have to do it twice.
As far as battery goes, my display is still the thing that takes up the most battery (which is normal) but I had been experiencing severe declines in battery life. Does the switch to 32-bit color require more processing power and therefore battery?
I *#*#4636#*#*>phone information and saw it was set to WCDMA preferred. I remember playing with the option when froyo came out but didn't remember what it was set to (Maybe Gingerbread reset the option...?). I changed it to GSM PRL (Auto), and have experienced increases in battery life, as my phone isn't hunting for 3G all the time- it uses a service provided list of tower locations.
The LED REALLY bugs me.

Hate about Gingerbread
No trackball wake
Juice Defender Doesn't work (but Green Power does - works well but with less flexibility than JD)
Short battery life
Useless keyboard selection gimmicks

- Market: even if automatic updates activated, it only updates if you open the market and go to the "my apps" tab
Click to expand...
Click to collapse
Well, glad to know mine isn't the only one that does this!!
On Froyo I would wake up in the morning to freshly updated apps that had updated automatically over night.
I have not had this happen a single time on Gingerbread, and nearly every time I go in to the market there are updates waiting.
What is the point of the automatic update feature when it doesn't work???

NexusDro said:
To be fair, the OP did mention about switching to Apple.
Click to expand...
Click to collapse
GldRush98 said:
Well, glad to know mine isn't the only one that does this!!
On Froyo I would wake up in the morning to freshly updated apps that had updated automatically over night.
I have not had this happen a single time on Gingerbread, and nearly every time I go in to the market there are updates waiting.
What is the point of the automatic update feature when it doesn't work???
Click to expand...
Click to collapse
auto update never worked for me, even in froyo.

-Battery with CM7 roms
-Trackball wake blocked in non-CM7 roms
-More difficult to mod themes like statusbar (before we just had to change a png and now we have to edit a bunch of files)
So in summary GB roms are still not stable and complete, they have either TB wake missing or poor battery life too

My annoying issues?
- 2 second mic mute after I answer a call
- stock launcher choking after a while
Less annoying ones:
- Market does not automatically update apps
- gps activations without an apparent reason

My annoyances
In no particular order:
The cursor select triangle not lining up with the cursor
Launcher unresponsive/vanishing
Lockscreen pattern not showing (as in the OP)
Phone randomly stays awake at night
GPS turns itself off
Not able to view an apps wakelock any more
USB mount screen shows 'turn off' even when it isn't mounted (UK issue)
USB debugging icon doesn't appear, or doesn't turn off depending on how you enabled it
Exchange push is just crap now, I swear it's getting worse by the day

DarsVaeda said:
- Battery Time: this is bad, can't even run half a day with lot of usage, b
efore I could listen to mp3's one day, ie. more than 4 hours without any problems...now
- Camera: either Cam or Video, the application crashes after I take a photo or video and then I can not connect to it anymore
- Gallery: often crashes, especially if you have an online photo account connected
- unlock screen: I use a pattern, often there is no overlay of what pattern I drag, still the screen can be unlocked
- Market: even if automatic updates activated, it only updates if you open the market and go to the "my apps" tab
- 3G and Wifi: if you are connected to wifi more than 15 minutes and then disconnect from it you do not get any 3G, you have to go to airplane mode and back, this bug appeared ages ago and was fixed, now back again...tells you a lot about their merging control, ie. sucks
- notification led: you know...
- apps: there are a lot of apps running even though I never used them since restart (see it in a task killer app)
- gps: on a random bases it tries to lock even though no app that uses gps is running
- phone reboot: it even rebooted without any notice two times since I installed it
(- Contacts: I still can't enter a simple thing like a birthday on an expensive phone like this)
I think there is more if I think about it.
Seriously thinking about switching back.
Click to expand...
Click to collapse
While I'm not a big Gingerbread lover at all, here are answers to some of the points:
Battery time is fine, at least in freshly installed ROMs it far exceeds what Froyo mastered.
Camera is your own problem - you didn't update radio, or your update went bad.
Gallery never crashed - again, your own problem (you get the feeling now, right?).
3G and WiFi - again, your own problem. No bug.
Apps - and why do you care? Isn't the "DO NOT USE TASK KILLER" thread clear enough? 150-200MB free RAM aren't self-explanatory?
Due to your comments, you might really consider switching to Apple. It would be beneficial both for you and for this forum.
Or you could back up user data, wipe, install new radio and bootloader, load fresh Gingerbread ROM (NOT CM7 or CM7-based), and have most of your points addressed.
Now, having said that, if you want a much better overall feel - install Froyo-based Desire port, or if you don't have any use for Hotspot - DesireHD port. I hate using barebone Android after some experience with it.

have you guys heard about Cyanogenmod ROM? I am using CM7 RC4 and I have no problems that anyone mentioned in this thread....

Maybe you haven't heard that your experience not necessarily represents anything.
For me (and another 2 guys that asked me to reinstall other ROM on their Nexus Ones), CM7 was a huge, awful pile of bugs. Starting with the ill-famous "wonk".
Plus, again, after having some SenseUI I don't really want to go back to plain Android, and wouldn't suggest it to anyone looking for a good overall experience.

I have an occasional problem with the application tray where it stutters, flashes and doesn't scroll properly. It seems to happen only after exiting certain apps, and needs the launcher to be force closed to fix.

xxlikquidxx said:
have you guys heard about Cyanogenmod ROM? I am using CM7 RC4 and I have no problems that anyone mentioned in this thread....
Click to expand...
Click to collapse
Exactly my experience too. Absolutely brilliant ROM.
Jack_R1 said:
..after having some SenseUI I don't really want to go back to plain Android, and wouldn't suggest it to anyone looking for a good overall experience.
Click to expand...
Click to collapse
Just lost all credibility in my book...
I would suggest the OP decides what features he/she wants in a ROM and then try a few different ones out. There are plenty to cater to all tastes and i'm sure they'll be able to find one that works well for them.

1. exchange sync stops syncing without any reason. can't start a manual sync. only reboot of the phone helps for a short period of time. needs a fix very urgently.
2. TINY TINY notification icons...the worst idea google had for the GB update. i cannot see the difference between the gmail and exchange mail icon on normal usage in example.
There are some more points which i also mentioned in my blog about gingerbread for nexus one:
http://smartphoneblogging.com/2011/03/review-android-2-3-3-gingerbread-for-nexus-one/

Thread Cleaned
Let's play nicely in here and keep this on-topic. This is not the place to discuss other operating systems. This is about issues pertaining to the OTA Gingerbread updates.
Thanks,
Your loving moderator.

One bug and one annoying change:
- The instability of the launchers. I hope they address this.
- The inaccessible GPS toggle. Tasker can't access it and neither can the toggle widgets. Why did they change this?

my mms sometimes does not send if i configure 2 APNs (one for mobile data and one for mms), while i disable the one for mobile data...
it's working fine on Froyo and CM6 before

benjatt said:
- The inaccessible GPS toggle. Tasker can't access it and neither can the toggle widgets. Why did they change this?
Click to expand...
Click to collapse
QFT!!!!!!!!!!!!

Auto brightness adjustment no longer fades, now it just jump straight to the target brightness which is quite abrupt visually.
And of course... trackball wake is gone.

I concur with these points:
- Battery Time: this is bad, can't even run half a day
- Gallery: often crashes, especially if you have an online photo account connected
- Market: even if automatic updates activated, it only updates if you open the market and go to the "my apps" tab
- GPS: on a random bases it tries to lock even though no app that uses gps is running
- Creating shortcuts on desktop: sometimes you can't drag/drop icons to the desktop or to a different spot on the desktop.
- The cursor select triangle not lining up with the cursor
- Auto brightness adjustment no longer fades, now it just jump straight to full bright or full dim.
As for the people suggesting we update the radio and try different roms, while that is primarily what this board is about, it doesn't "solve" anything. This is a stock Nexus One with official everything. If it doesn't work then it doesn't work.

[Q] Most stable ROM with GPS + Camera

I know that there has been quite a lot of these threads, and I've gone through a lot of them, but I havent really found a pattern as to the suggested ROMs, so I'm going to have a go myself with a new thread and I hope you will bear with me...
The thing is that I need to use my HD2 with Android for work related use (self-employed freight carrier). And I only have a few specific requirements:
- SUPER stable!
- Working GPS (For use with both Google Navigation and CoPilot v8 Professionel)
- Working Camera (For taking a few pictures, if I come across damaged goods - video not required)
- Decent battery life (I don't need 160 hours of stand-by as it will be on cable in the car most of the time - but it would be nice if it could hold a weekend on pure standby)
- And then it will be using an app programmed by a local software house, but I do not know the requirements of this. But it is installed as a service and works together with the two navigation systems.
I will NOT be using it for phonecalls or text messages at all. There will only be a data SIM card in it.
Currently I have only tried NexusHD2 Gingerbread v3.2a NAND (installed with MAGLDR). And it usually reboots 3-4 times a day + Google Navigation closes a couple of times during a workday. And 1-2 times a day it locks up so I have to remove battery.
This is not acceptable for my use, when I'm driving a car and sometimes need to rely 100% on my navigation. No disrespect to tytung. I may just have a bad phone or have been very unlucky with your ROM.
I dont care what version of Android the ROM is built on as long as the above requirements are met.
Thanks a lot for your time and any suggestions.
// Martin

gpc v2.8
http://translate.googleusercontent....PLB8JH&usg=ALkJrhgYtN0WTwy1B4Snry54m_Ek_RSo4w

micavimale said:
http://translate.googleusercontent.c...9OYIuvQ253qMzw
Click to expand...
Click to collapse
Link is not working for me.

...corrected!!!
Recovery 5/150/5

Thanks, but I would prefer links to ROM threads rather than direct links to ROMs I know nothing about.

...your decision.
http://forum.xda-developers.com/showthread.php?t=909096&page=216

Thank you very much. I will have a look at it.
Other suggestions are still welcome.

[Solved] [Q] Battery drain due to "am2server" and "aes1750" on CM7

[Solved] [Q] Battery drain due to "am2server" and "aes1750" on CM7
Hello.
Lately after flashing CM7 weekly #4 (Dec 10), I noticed that sometimes my battery drains rather quickly and nothing unusual is shown in "Battery use" (The phone is awake a lot more than the screen is on but "that's normal" I guess).
After a bit of digging around I found, using android terminal and the top command, that the processes " /system/bin/am2server" and "aes1750" are at 50% CPU each.
Rebooting the device helps for a while and they go back to 0% each, but after a seemingly random amount of time they go back to 50% each.
Killing the processes with "kill" or "killall" does nothing at all (with root permissions of course).
Searching XDA site and with google gave no relevant results, mostly something about Intel vs AMD and "am2 servers".
Since I have no idea what those process do, I can't provide any relevant information.
I can add that this problem wasn't there with Ba2tF.
Also since weekly #4 has finger print support, which by the way doesn't really work for me*, I am guessing this is related to it but no way to confirm.
* I can set FP for the lock screen after a full wipe and it works fine, after a while I can no longer unlock the device with the sensor and then pressing "Settings > Device settings >Fingerprint sensor navigation" and the fingerprint option in lock options do nothing (no error, just nothing.)
Any help or pointers would be highly appreciated.

masmddr said:
Hello.
Lately after flashing CM7 weekly #4 (Dec 10), I noticed that sometimes my battery drains rather quickly and nothing unusual is shown in "Battery use" (The phone is awake a lot more than the screen is on but "that's normal" I guess).
After a bit of digging around I found, using android terminal and the top command, that the processes " /system/bin/am2server" and "aes1750" are at 50% CPU each.
Rebooting the device helps for a while and they go back to 0% each, but after a seemingly random amount of time they go back to 50% each.
Killing the processes with "kill" or "killall" does nothing at all (with root permissions of course).
Searching XDA site and with google gave no relevant results, mostly something about Intel vs AMD and "am2 servers".
Since I have no idea what those process do, I can't provide any relevant information.
I can add that this problem wasn't there with Ba2tF.
Also since weekly #4 has finger print support, which by the way doesn't really work for me*, I am guessing this is related to it but no way to confirm.
* I can set FP for the lock screen after a full wipe and it works fine, after a while I can no longer unlock the device with the sensor and then pressing "Settings > Device settings >Fingerprint sensor navigation" and the fingerprint option in lock options do nothing (no error, just nothing.)
Any help or pointers would be highly appreciated.
Click to expand...
Click to collapse
I had the same problems. I think it's because I went from a previous non-FP enabled build without wiping then all the subsequent FP builds had this issue. Data wipe fixes it is all I know, I'm afraid.

Thank you for replaying.
I moved from Ba2tF without a full wipe and anything related to the FP didn't work, trying to set a lock screen returned a couple of errors.
But afterwards I did a full wipe and reapplied the zip of weekly #4.
This fixed the FP sensor for about 20 minutes, I eventually gave up and decided to wait for CM9; hoping it will work better then.
I am much more interested in the battery drain.
I don't want to go back to Ba2tF because I like scrolling with the sensor and I find it very useful.
Edit : seems that the problem was "fast reboot " application.
Stopped using it and so far am2server and aes1750 are acting normally, plus the FP scanner works fine.
Sent from my MB860 using XDA App

[APP] Smartswitcher

Check out main thread here:
http://forum.xda-developers.com/showthread.php?t=1803902
# What it does #
Basically what it does is it makes it possible to launch androids taskswitcher (recent apps) or call another action such as home, back, menu or turn screen off by waving your finger past the proximity sensor. You can also set an action to run when your proximity sensor is covered. With a little practice this really makes multitasking much faster. There is now also actions for media like volume, play pause and such, aswell as a flashlight (only tested on galaxy note, probably wont work on all devices) The media-actions are not properly implemented yet, so all actions may not work on all devices. If media controls is what you really want, I think wave control is your app. They have media controls implemented properly.
There is now some other features aswell.
Smart keep screen on will keep your screen on as long as you hold the phone in your hand. When you put it down, it will let the screen go off. I have only tested it on a galaxy note. Feedback on this would be welcomed.
You can now also run an action to keep the screen on permanently, or atleast until you run the action again.
Feel free to try it out.
# Instructions #
Configure actions for each number of waves up to six. The action you choose will then be executed when you wave.
You can also configure an action to launch when you cover your proximity sensor and for when the device is shaken.
If you have trouble with the gestures and smartswitcher recognizes the wrong gesture, you can adjust the gesture sensitivity. If you put this on low, the response and gesture recognition will be fast, but you will have to wave fast also. On high, the opposite is true. If you are not Lucky Luke like me, medium or high should work.
# Planned features #
Suggestions, anyone?
# Known issues #
FIXED?
Sometimes Smartswitcher does not get superuser permissions at first try, if you are rooted and you are sure it should work on your device, this may be the problem. I am not sure why this is as it has never happened to me, but a few users have reported that installing it again or using supersu fixes the problem. Will try to get this fixed.
# Other #
The powerconsumption of the proximity sensor is extremely low so the impact on your battery should be fairly low. Did anyone using this notice a reduction of battery life, and I mean that in a more scientific way than just checking under battery in your system settings? Was it 5 minutes or 1 hour?
If you dont have root or smartswitcher wont work, please buy the excellent app wave control. (Or if you simply like it better)
Zenblom made a video of smartswitcher:
He also compiled a list on working devices:
# Confirmed working devices #
- Samsung Galaxy Note GT-N7000
- Samsung galaxy s3 i9300 international version
- Samsung Galaxy Tab 7.7 P6800
- Sony Ericsson xperia neo v
Thanks Zenblom!
# Changelog #
Version 1.1.3
- Added action keep device alive. If you run this, your device will not sleep until next time you run it, period. It wont activate if the device is already being kept awake by the smart keep screen on function, have not tested this very carefully. If you feel a burst of short vibrations, the device is being kept awake. If you use this, dont forget to turn it off, or it will drain your battery.
- Adjusted the shakedetection. It should now work much better and should notmake doubleactions. Try it and tell me if it is better or worse.
- Adjusted the smart keep screen on function to a little less sensitive. Sometimes it did not turn the screen of because i set the sensitivity too high so it detected movement event when it was fairly still. Try it and tell me if I made it better or worse.
- Added support for up to six waves by request. Tested it some, it seemed to work fine.
Version 1.1.2
- Added action flashlight. Will probably not work on all devices, but it works on my note atleast. Will add more variants for other devices.
- Added EXPERIMENTAL Smart keep screen on function. There is no adjustable settings yet, just on and off. You can try it by setting your screen timeout at a low value like 15 seconds. As long as you hold your phone in your hand, the screen should keep on. If you put it down the screen should go off in 30 seconds or so. I adjusted it to work on my device, but that does not mean it will work good on yours. There is no settings for it yet. Try it, if you dont like it, disable it. Will also spend some time on next version with the shake detection, Its really not what I wanted it to be. It works, but barely.
Version 1.1.1
- Added shakedetection. You can now set an action for shake. Note: Will cause the ui to crash, press backbutton to close smartswitcher settings before using it and it should work fine.
Version 1.1.0
- No visible changes, but lots of changes in the code. I hate spagetticode, so I spent some time removing and rewriting things. Sensorcovered will now really have zero delay if you set that.
- Made the number of proactions allowed to 20, as I said I had done. It seems it was only 10
Version 1.0.9
- Fixed sensor covered, now it wont trigger any action if you remove your finger within the delay time.
- Added a BUNCH of actions. Some will work on your device, some will not. (Depending on rom, installed apps etc) The new features are for the pro version (Yes I will make a pro version.) I am a nice guy so everything you had before still works, plus you can use the profeatures for a total of 20 times, after that they will reset to no action. You are free to select pro features again for another 20 times. Sorry about this, but I have spent quite a few hours on this app now, and I would not mind getting a few bucks for my work. Please tell me what price you find fair for this app, if any price at all
- Made it so that gestures will work on active phonecall. This means actions like for instance hangup will actually hangup the call. Sensor covered should not interfere with anything now.
Version 1.0.8
Note: Remaining bug, sensor covered works but the delaysetting does not do what it is supposed to do. That is, even if you remove your finger from the sensor within the delay time, the action will still trigger. Sorry about that, will fix. Too tired now
- Fixed the bug that caused settings to not save after a while. Should work fine now.
- Added configurable settings for sensor covered so you can now set any action for that event. If you have a device with slow sensor you should now be able to launch recent apps by setting sensor covered delay to 0 and action to recent apps. You can now also set screen off as action on any wave.
- Fixed vibration feedback for sensor covered event.
- Removed Screen off setting as it is no longer needed.
- fixed some other bits and pieces and cleaned up the code.
Version 1.0.7
- Completely rewrote all of the code for taking care of actions. If I am lucky this will take care of the strange superuser permissions error. Unfortunately this way will mean an ever so slightly slower response, but if it turns out this way works better, I will see if I can speed it up some.
- Lots of bugfixes. Wavesettings and gestures off in landscape SHOULD work properly now. So SHOULD the screen off feature.
- Added button to stop Smartswitcher from doing anything at all. Now, please tell me what I have broken this time
Version 1.0.6
- Added settings for all gestures. You can now disable/enable/configure individual gestures. I did test this, but not very carefully. I should stop doing this so late at night. Please tell me if you find problems.
Version 1.0.5
- Added option to disable gestures when phone is in landscapemode. Now you dont have to kill smartswitcher if you find it unusable in landscape and then start it again when back in portrait. Let me know if it does not work as intended.
- Changed the vibrationfeedback on recognized gesture to a more gentle level.
- Find my sensor-mode is gone. Kind of useless feature anyway, good riddance to bad feature.
Version 1.0.4
- Wave once for recent apps, twice for menu, three times for back, four for home. No customizable settings for this yet, I need to sleep now Oh, I broke find my sensor-mode.
Version 1.0.2
- Configurable delay for the screenoff when sensor covered-feature added
Version 1.0.1:
- Disableoption for screenoff "bug"
- Changed Get the feel-mode to Find my sensor-mode, hopefully this is not as confusing
More coming. If you have any ideas or suggestions, let me know.

Nice idea...but on my HOX screen goes off waving past proximity sensor...BUT really nice idea!!

Work with me fine , but I must wave to lunch it
Thank you
Sent from my GT-I9300 using xda app-developers app

HISOON said:
Work with me fine , but I must wave to lunch it
Thank you
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Cool, what phone do you use?

Samsung galaxy s 3 international version
Sent from my GT-I9300 using xda app-developers app

didn't work for me
the phone vibrate and all but no recent apps !!
i use a galaxy note

oaz63 said:
didn't work for me
the phone vibrate and all but no recent apps !!
i use a galaxy note
Click to expand...
Click to collapse
If it is rooted, it really should work. There is a bit of a trick to it, you have to wave your finger past the sensor and back within a fairly short amount of time. I did this because if I launched recent apps when you just come close to the sensor once, it launched when I did not want it to and was more of a pain than it was useful. Try setting the sensitivity to high and try a few more times. If it does not work then, we will have to figure out why. Plenty of people has tested it successfully on the note, thats why I am fairly sure that it should work but I could be wrong.

ssspeq said:
If it is rooted, it really should work. There is a bit of a trick to it, you have to wave your finger past the sensor and back within a fairly short amount of time. I did this because if I launched recent apps when you just come close to the sensor once, it launched when I did not want it to and was more of a pain than it was useful. Try setting the sensitivity to high and try a few more times. If it does not work then, we will have to figure out why. Plenty of people has tested it successfully on the note, thats why I am fairly sure that it should work but I could be wrong.
Click to expand...
Click to collapse
Stock NEE 4.0.4 on galaxy note,
Doesn't work :/ (rooted)
Sent from my GT-N7000 using Tapatalk 2

Racle90 said:
Stock NEE 4.0.4 on galaxy note,
Doesn't work :/ (rooted)
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Would you mind doing a logcat for me while you try to wave at the sensor? It has worked for the majority of testers, I need to figure out why it does not for a few. No hurry, I wont have the time to look at this for a few days anyway. Thanks for testing!

ssspeq said:
Would you mind doing a logcat for me while you try to wave at the sensor? It has worked for the majority of testers, I need to figure out why it does not for a few. No hurry, I wont have the time to look at this for a few days anyway. Thanks for testing!
Click to expand...
Click to collapse
Here's your logcat, (looks like spamming the same message, probably triggers the event (?) but doesn't execute that)

Tried on xperia ray. Doesn't work. Just vibrate that's all. Will attach logcat if possible.
Edit : not sure if I'm doing it right, but this is all I get.
l/Smartswitcherservice(27913): Räknare:1
I/Smartswitcherservice(27913): Räknare:2
I/Smartswitcherservice(27913): Timer done

Absolutely amazing idea. Sometimes it does shut the screen off, though. Other than that, it works perfectly on the S3.
Thanks for this.

Nice idea
But On HTC desire and Sony Live with Walkman
It just vibrates and turns the screen off

frenzyboi said:
Tried on xperia ray. Doesn't work. Just vibrate that's all. Will attach logcat if possible.
Edit : not sure if I'm doing it right, but this is all I get.
l/Smartswitcherservice(27913): Räknare:1
I/Smartswitcherservice(27913): Räknare:2
I/Smartswitcherservice(27913): Timer done
Click to expand...
Click to collapse
You are probably doing it right, its not that hard, most likely the sensor on your xperia ray is not updating its values fast enough. Räknare is swedish for counter You will need to get it up to 4 counts to trigger recent apps.If there are enough people with slow sensors Ill see if I can fix some other way of triggering it, maybe just covering the sensor but I am not sure if thats going to be useful. I dont have access to my computer right now.

fire_kid2003 said:
Nice idea
But On HTC desire and Sony Live with Walkman
It just vibrates and turns the screen off
Click to expand...
Click to collapse
The screen off thing is something that should not be there. I forgot to remove it after a failed experiment with a screen off feature, will be removing that. If you could check logcat while you try waving I would be happy. If you see something like the poster with a xperia ray, its probably the same problem.

This is working nicely for me. Sgs3 internationsl i 9300. Wanamlite rom.
I switched sensitivity to low and i think is better.
What i want ask. How is this for the battery and the sensor itself?
I think that this will fry it after some time.
Anyhow great thinking.
Sent from my GT-I9300 using xda premium

oaz63 said:
didn't work for me
the phone vibrate and all but no recent apps !!
i use a galaxy note
Click to expand...
Click to collapse
same here but with Motorola Defy

mariosraptor said:
This is working nicely for me. Sgs3 internationsl i 9300. Wanamlite rom.
I switched sensitivity to low and i think is better.
What i want ask. How is this for the battery and the sensor itself?
I think that this will fry it after some time.
Anyhow great thinking.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I have not noticed any negative impact on battery life, maybe someone else has, nobody has had any complaints about it so far. As for burning out the sensor, I dont think thats much to worry about. I used the sensor on my n900 for this for a very long time and its still working, although other parts of my beloved n900 has broken but not the sensor. If it makes you worried it might be best to not use this.

Downloaded the apk from galaxy note forum and it's working
Sent from my GT-N7000 using Tapatalk 2

Racle90 said:
Downloaded the apk from galaxy note forum and it's working
Sent from my GT-N7000 using Tapatalk 2
Click to expand...
Click to collapse
Cool! Its the same apk, but whatever makes it work is good