Database Info

[REF] Detailed Review of XT720 2.1 vs 2.2 (1.1a)

Edit, 02/10/2011:
Please keep in mind this post was based on the original release, some things have been fixed/changed since then. See post 1 in the dev thread for full update details.
Original Post:
My wife and I both have XT720, I left her's with stock 2.1, mine I just upgraded to Dexter's 2.2.1 (1.1a release) so I was able to compare the two side-by-side.
I wanted to list some of the differences for people, almost all of these are trivial items but just so you know what you may or may not see:
Menu options missing in Settings are:
Wireless & Network Setings
- Control background data
Call Settings
- TTY mode
- Hearing aids
HDMI
- HDMI Format
Location & Security Settings
- My Location
- Use assisted GPS
- Compass
- Calibrate Compass
Applications
- Double tap home launch
Search
- Google search settings
- Searchable items
- Clear search shortcuts
Language & Keyboard Settings
- Enable cursor positioning
Text to Speech
- Listen to an example
- Install voice data
- Always use my settings
- Speech rate
- Language
Click to expand...
Click to collapse
Some of these may have been depreciated with 2.2 and may be why they are gone. Others not so sure, but all of very low priority in my opinion (except A-GPS and Compass).
* Assisted GPS is useful to lock onto GPS faster, this can also be downloaded with many apps in market. I use "GPS Status & Toolbox" by EclipSim which can also download the A-GPS data.
* Compass does not seem to work at all, always stays within a few degrees of the orientation it thinks it is in. As the menu settings were missing (per above) I have used alternate calibrate and compass functions also in the "GPS Status & Toolbox" app to test. Does not seem to change direction again, more than just a few degrees.
* Proximity sensor does not seem to work, cover it with finger and screen does not go black as expected. This is a problem when using the Phone with dialpad open as I usually manage to press buttons with my ear while talking. I think this proximity sensor issue is biggest problem left (for me).
* Noticed as well, when scrolling a list (like when in Settings menus) that the haptic/audible feedback when you hit the very top or bottom of a long list no longer happens in 2.2.
* Also an app note, when first trying to load Latitude in Google Maps app, it gives errors that it cant connect to your Google account and goes to the add account screen. If you cancel the add account screen, you will see an alert of a notification - this is asking to allow Latitude to access your Google Account. Once approved, Latitude worked fine.
* Noticed in About phone, kernel version says "[email protected] #1" under where it says 2.6.29-omap1, what is this?
* The haptic feedback (vibrations) seems to be much lighter/fainter than in 2.1.
* Bottom 4 lights were stuck in Off until I used the Power Widget to change the screen brightness.
* No Phone or Messaging buttons next to app drawer on home screen.
* Camera mode - stitching, supposed to let you take 6 photos and stitch them together but when you try to take the second photo it just saves the first one only.
Click to expand...
Click to collapse
Again as I said, almost all of these observations are inconsequential - I just wanted to list them in one place for peoples comparison.
Oh, and Google Goggles works in 2.2, it never worked in 2.1 (always scanned as a blank green sceen).
Thanks Dexter for all your hard work in getting this far so quickly!
edit: Home screen and Quadrant score:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Cant post to the other thread, so adding some feedback here .. mods can maybe move some of these posts?
Click to expand...
Click to collapse
I reposted your post at the other thread.

Wow!, thank you for such a detailed review of the outstanding issues, functionality and missing features between the versions
now people can think ahead if they are willing to lose some of those functionality or not before upgrading

Reading this i think some understanding of functionality is left to consider?
*Compass
If you rotate the phone, should compass not STILL point the same direction? i think north is arrow points? i tested with GPS test and Compass app, and direction after calibration seems fine. (using the 8 rotation solution to solve calibration)
*Proximity sensor seems to have a long range estimation (tested with Z-devicetester) i made some changes and now it reflect 0cm -> 6cm , in 1.1a it seems to say 0 -> 217cm
*haptic feedback depends on devices, Milestone might just have different device, so they lowered it to make it less hard. cannot be easily fixed unless framework changes.
*Google account in general can report "no network connectivity" as it always try mobiledata before regular wifi, its comon problem on all phones, it does happens not only with maps or gmail/market.. (i see this on Galaxy S as well)
* No Phone or Messaging buttons next to app drawer on home screen.
Must be an observation as its not part of Google Stock , but is a way of design from vendors, motorola do it on some phones now..
LauncherPRO is an excellent way of getting custom buttons back. Stock launcher is always boring.
-----------------------
update to your old information versus new information.:
Wireless & Network Setings
- Control background data moved to Sync options
Location & Security Settings
- My Location still there but more defailed network+gps sat)
- Use assisted GPS always enabled on motorola phones
- Calibrate Compass (no need, sensor calibration using moving in 8 circle
Text to Speech now called Voice input&Output

Depends on the app how the compass rotation is displayed. What I am trying to say is that it does not point how it should. For example, when using Google Sky Map, I hold up the phone and it is always looking South no matter which way I am pointing.
For how much it gets used its not a big deal, just my observation. And thanks for the info on some of the menu options and where they moved.
For "Control Background Data" - I think this is a different option than the "Background Data" in sync as the option under Sync was there before too. The description in 2.1 for "Control Background Data" is "Control background data to extend battery based on network". The option under Sync of "Background data" says "Applications can sync, send, and receive data at any time". I have no idea what the functional difference is, maybe they both do something similar anyways.
Good to know on A-GPS being always on, was not aware of this.
And for Prox sensor, it started working after another reboot, not sure why. It works at the same distance (tested with side-by-side phones) as previously.
So aside from weird compass behavior here, everything seems to be working great now.

One more thing I just noticed with volume control, the explanation may not make sense but functionally when you are using the app it will be clearer.
In 2.1 when in landscape orientation (speaker on left, buttons on right), the volume Up and volume Down are reversed as they then correspond with the display on the screen.
ie. Pressing volume up button would actually turn the volume down, and down button would turn volume up as it was on the right, and that is how the volue bar is displayed on the screen.
In 2.2, volume up button remains as volume up in landscape mode, so when you rpess it and expect the volume slider display to move let (down) it actually goes the other way.
You can see this in Vevo or Angry Birds for example, expect to push left for volume down but it goes volume up. To me it makes sense for it to reverse the volume control buttons when in landscape orientation.

My problems:
1. if i enable auto-proximity sensor, and turn my phone 90° right side (so to east), the screen turns also 90°. so far, so good. but it stays like this the whole time, even if I turn my phone back 90° or 180° or so. sometimes it works normally, but not always does the screen follow the turns.
2. Languages are for example in the camera & task manager in English. But we already know that.
3. Games that are used with apps2sd are often laggy.
4. The button next to camera button does not work, for example when I open the camera and push that button next to camera button, the camera should change to gallery or to camcorder. But it doesn't.
5. For example playing games and I want to change the volume and press "up" at the volume button, the sound gets less loud and if I press "down" at volume button", the sound gets louder.
6. Using the web browser, the pages do not adapt to the screen like in 2.1.

I think there are some compromises we must make in order to have 2.2 on the xt720. The one issue that I am still having that I do not feel i should compromise on is the browser.
The stock browser is killed, not force closed, but killed while in use very often. I do not know what is causing the issue but I saw that users on the ROM thread are having the same problem.

warrenkb said:
I think there are some compromises we must make in order to have 2.2 on the xt720. The one issue that I am still having that I do not feel i should compromise on is the browser.
The stock browser is killed, not force closed, but killed while in use very often. I do not know what is causing the issue but I saw that users on the ROM thread are having the same problem.
Click to expand...
Click to collapse
i will of course follow up on this issue and the music scanning problem..
which for now is "major".. but ill report back on it asap when i got a solution.
and keep the update minimal so ppl do not need to make full flashes or wipe's
strange is that i played with a few flash sites with stock browser, and it did not crash then? can it be flash somehow crashing it or not being there?

nice comparison!

Thanks for the useful review

you should do a 1.2 review by now. so far, 1.2 is a lot better than 1.1+

Agreed, I also have it on my Starhub XT720, and thanks to it I am keeping the phone !

Is chinese language supported in this rom?If not in the future?

chaud said:
Is chinese language supported in this rom?If not in the future?
Click to expand...
Click to collapse
i know its there, so have a try and decide yourself, but for me , being danish, its looks different

Rotation seems to work in both directions rather than just one. I was wondering if there is a way to limit it to just one side again?

trajano said:
Rotation seems to work in both directions rather than just one. I was wondering if there is a way to limit it to just one side again?
Click to expand...
Click to collapse
i doubt it will be better.. most ppl prefer 360 rotation, but maybe disabling rotation will help?

There are Widgets to disable or to manually rotate your screen, you may want to try one of those ... I personally like the 270 degrees of rotation. Just wish the volume rocker would auto switch like in 2.1
Sent from my XT720 using XDA App

R-D said:
There are Widgets to disable or to manually rotate your screen, you may want to try one of those ... I personally like the 270 degrees of rotation. Just wish the volume rocker would auto switch like in 2.1
Click to expand...
Click to collapse
Yes I know about those, but I was wondering how we can have it so it is just 90 degrees. No biggie, but is is still a difference between 2.1 and 2.2 that you may want to add to the list.

SD Card feedback
I am also unable to locate where to disable the SD Card notifications

any setting to have keyboard backlight on always?

I know the backlight comes on when dark or when you cover the front camera, anybody know on a rooted phone how to set it to have it on always when keyboard is opened?
Thanks, David

For a cheaters fix you could cover the light sensor with your index finger.
Not sure where it is in code at the moment though...

Tasker is probably capable of doing this
sent from rubix ics 5.2 mt4gs

I checked out tasker and it mentioned keyboard backlight, but couldn't confirm it would do what I need on the MT4GS..
so no software tweak, so I did a hardware tweak. I covered up the light sensor in upper left corner with black tape. Its the light sensor, not the front camera that is used. I was incorrect previously..

daviddallas said:
I checked out tasker and it mentioned keyboard backlight, but couldn't confirm it would do what I need on the MT4GS..
so no software tweak, so I did a hardware tweak. I covered up the light sensor in upper left corner with black tape. Its the light sensor, not the front camera that is used. I was incorrect previously..
Click to expand...
Click to collapse
I'll try it on Tasker now, and let u know.
"Tbalden" had previously hacked the ICS kernel to always use backlights on... Ask him about it for more info.
Just my spare change.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Tasker works. Back light never turns off when KB is out.
Just my spare change.

CoNsPiRiSiZe said:
Tasker works. Back light never turns off when KB is out.
Just my spare change.
Click to expand...
Click to collapse
did this continue to work for you? it seemed to work like a charm for a day, then just stopped working,

yogi2010 said:
did this continue to work for you? it seemed to work like a charm for a day, then just stopped working,
Click to expand...
Click to collapse
I haven't needed to use this in a very long time... What rom are you using yogi?
::Respect::

wow, thanks for the fast response after i necro'd this thread lol. i'm just rooted on the latest stock ROM 1.63.531.2. i imagine some ROMs might have a fix implemented? the thing is, i really like the stock ROM, especially the camera app.

You could mod a framework file to implement this. I think it's on framework-res.apk. on res/values/arrays.xml you need to find the array with the name "auto_KeyboardBacklight" I think and change all it's values into 255.

yogi2010 said:
wow, thanks for the fast response after i necro'd this thread lol. i'm just rooted on the latest stock ROM 1.63.531.2. i imagine some ROMs might have a fix implemented? the thing is, i really like the stock ROM, especially the camera app.
Click to expand...
Click to collapse
Okay! Well do you have issues with keyboard lighting on the stock rom? I'm assuming you should not... As it is the stock rom. But I don't know..
Your kb lights should light up just fine without this. Did they before?
::Respect::

CoNsPiRiSiZe said:
Okay! Well do you have issues with keyboard lighting on the stock rom? I'm assuming you should not... As it is the stock rom. But I don't know..
Your kb lights should light up just fine without this. Did they before?
::Respect::
Click to expand...
Click to collapse
well, they do light up, but it has to be very dark. there are way too many times when it is too dark to read the keys, yet the backlight does not come on.
this issue is even mentioned in reviews of the device such as this(towards the end of the 3rd paragraph):
http://www.engadget.com/2011/08/02/t-mobile-mytouch-4g-slide-review/
it seemed that Tasker was the answer, but it just quit working! i believe i had it set up properly
---------- Post added at 11:10 PM ---------- Previous post was at 11:07 PM ----------
Riyal said:
You could mod a framework file to implement this. I think it's on framework-res.apk. on res/values/arrays.xml you need to find the array with the name "auto_KeyboardBacklight" I think and change all it's values into 255.
Click to expand...
Click to collapse
ok, i may look into doing something like this. i wonder if it could be switched on and off tho, like during the day when i wouldn't want the backlight to come on and waste battery?

you could make a script to set the values directly on the kernel but I forgot the path. Will put it later when I get home

Riyal said:
you could make a script to set the values directly on the kernel but I forgot the path. Will put it later when I get home
Click to expand...
Click to collapse
thanks buddy. might it be /sys/class/leds/keyboard-backlight/brightness? i notice that the value in that file is either 0 or 255, depending on whether the backlight is on or off.

Ahh yes! That's the right file. The number in that file represents how strong the led should light up. But in the case of keyboard backlight it's only 255 or 0 because it doesn't have any brightness control unlike LCD and camera flash.

yogi2010 said:
ok, i may look into doing something like this. i wonder if it could be switched on and off tho, like during the day when i wouldn't want the backlight to come on and waste battery?
Click to expand...
Click to collapse
Ideal situation would be to make the change in the kernel (it's in board.c if I remember right) and then write a skeleton app that works like a front-end to change the setting...or just mod the stock settings app to add it to the list.

Blue6IX said:
Ideal situation would be to make the change in the kernel (it's in board.c if I remember right) and then write a skeleton app that works like a front-end to change the setting...or just mod the stock settings app to add it to the list.
Click to expand...
Click to collapse
Like this one
Although this was made for g1 users but I think this should work also with doubleshot.

Riyal said:
you could make a script to set the values directly on the kernel but I forgot the path. Will put it later when I get home
Click to expand...
Click to collapse
The question that strikes me:
run script to set values pre-compile to save you from doing it manually, or are you talking about something to affect change to a live kernel?

Thanks guys for ganging up on this issue with me! I like the idea of adjusting the setting pre-compile..... I wonder if the backlight threshold can simply be lowered, so that it doesn't have to be so dark for it to come on? Is there a value for the light sensor perhaps that could be raised or lowered?
I appreciate the find of the Dark Key apk! I was actually looking for it, but it didn't seem to be in the market anymore. It does work and it seems decent as a toggle switch, but not perfect... It seems like when you toggle it on, it prevents the screen from going to sleep(I think anyway), and when you manually put the device to sleep and then wake it up, the apk turns the keyboard off for some reason.
I really like the way Tasker does it, if only it would continue working!

i figured out what is going with Tasker for me. it basically is working, but perhaps not exactly as i would like it to. it will indeed turn the keyboard backlight on anytime the phone is closed and i slide it open. however, if i leave the keyboard open, then put the device to sleep and wake it up, the setting reverts back to the light sensor being in charge... so it seems that the app needs the keyboard to open in order to trigger the setting... it does not simply detect that the keyboard is already open. oh well
ideally i would love to lower the threashold for the light sensor to turn on the backlight, probably in the source code itself. not sure how that would be done, plus i haven't even been able to get the newest source to boot up.
update: i figured out how the make Tasker do what i want by adding a second profile to also turn the keyboard backlight on when the device is unlocked! it works! yay
as you were....

[APP][FREE] Keep Screen ON in a smart way

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
After the success of Smart Screen OFF and Smart Screen ON... Here is Keep Screen ON!
Keep Screen ON is an innovative free app that allow you to keep your smartphone screen ON in a smart way. This app will help you saving battery keeping the screen on only when you are holding it. This works thanks to orientation sensor built in your device (smartphone or tablet).
HOW DOES IT WORK?
When you are using your device, you hold it in a specific position. Keep Screen ON let you select the range of activation of the screen brightness based on the device inclination (more smart ways are coming soon).
WHY DOES IT SHOULD IMPROVE BATTERY LIFE?
You know for sure that screen brightness is the most important factor in battery life and you will find it always at the top of the most consuming factors in Android statistics. Keep Screen ON as name implies, keeps brightness enabled only when you are holding it: as soon as you left it on the table, the screen will turn off.
SO WHAT?
Download the app and extend your battery life!
FUTURE
This is first version and powerful improvements are coming soon.
+Battery tab
+Screen settings
+Brightness settings
I WOULD LIKE TO SUGGEST
I'm always open to users suggestions, simply contact me using the forum.
KEEP SCREEN ON PRO

AW: [APP][FREE] Keep Screen ON in a smart way
Cause of your great apps screen off/on and your great support I'll try keep screen on.
I'm using successfuly screebl beta for this since years.
Let the challenge begin

davall said:
Cause of your great apps screen off/on and your great support I'll try keep screen on.
I'm using successfuly screebl beta for this since years.
Let the challenge begin
Click to expand...
Click to collapse
Thanks. I hope you'll like it!

Very nice app, been looking for something like this for a while now.
I have one problem with it, when my phone is in its cradle it falls within the setting range and the screen times never times out.
It would be great if in the future there could a setting to disable the app when connected to an external pwr source and/or an option to let the screen time out after a specific time without any movement.

kantjer said:
Very nice app, been looking for something like this for a while now.
I have one problem with it, when my phone is in its cradle it falls within the setting range and the screen times never times out.
It would be great if in the future there could a setting to disable the app when connected to an external pwr source and/or an option to let the screen time out after a specific time without any movement.
Click to expand...
Click to collapse
Yes, that's a good idea. Disable during charge will be implemented in one of next releases.
I'll also implement a new way to react to movements in the space. :good:

[1.0.1] Little Bug fix for link to PlayStore developer page

AW: [APP][FREE] Keep Screen ON in a smart way
Hide Icon did not work.
After a reboot it works. :thumbup:
Gesendet von meinem GT-N7100

In test mode the model turns green in my hand and grey when the phone is placed on the desk.
When the app is activated proper, I don't notice any change.
Should the screen be turning off and on based on the test model? Am I mistaking the uses of this app, please tell.

Mayday_XL said:
Hide Icon did not work.
After a reboot it works. :thumbup:
Gesendet von meinem GT-N7100
Click to expand...
Click to collapse
Yeah, always make sure to "Save and restart the app" every change you make. If something doesn't work properly, rebooting could do the trick.
noble8 said:
In test mode the model turns green in my hand and grey when the phone is placed on the desk.
When the app is activated proper, I don't notice any change.
Should the screen be turning off and on based on the test model? Am I mistaking the uses of this app, please tell.
Click to expand...
Click to collapse
When you are using the phone, the brightness will never be turned off (screen won't turn off and brightness won't be dimmed).
As soon as you are not using phone anymore (you place it on your desk for example), the app will let screen turn off.
More settings about delay are coming soon :good:

Since some user asked, I will implement an in-app billing system to remove ads from app. It will be available in one of next releases with a couple of new features.

it doesnt work for galaxy s with cm 10.1 but it works for nexus 4

gomek111222 said:
it doesnt work for galaxy s with cm 10.1 but it works for nexus 4
Click to expand...
Click to collapse
Uhm, interesting... Maybe Cyanogen guys missed something orientation related in the rom.
Great to hear it works for Nexus 4, thanks for your feedback.

does not work on the HTC One X

crazyAlex2 said:
does not work on the HTC One X
Click to expand...
Click to collapse
Could you provide a logcat when running the app? After you have turned ON the app and pushed "Save and restart app".
[email protected]
Thanks

This app seems to work (till now) on my P970

DDeleted said:
Uhm, interesting... Maybe Cyanogen guys missed something orientation related in the rom.
Great to hear it works for Nexus 4, thanks for your feedback.
Click to expand...
Click to collapse
it work in the test screen but when i back to home screen the green man doenst change to grey man whe i put the phone plz solve this

(Please delete)

feature request
DDeleted said:
Yes, that's a good idea. Disable during charge will be implemented in one of next releases.
I'll also implement a new way to react to movements in the space. :good:
Click to expand...
Click to collapse
excellent application. its very useful. I would like to request you to implement a few extra features that will be handful in saving battery.
1. warning notification/dialogue for checking screen on time for more than 5 to 30 minutes. (even if the device is in motion or touchevents)
2. need screen timeout option to detect stillness. 1 min to 15 min
3. need to set screen off if the device is held vertical or horizontal ( bcoz we will not hold mobiles in 90 degree except when using camera.

Love this app!!
Using it in conjunction with your other screen off app, and between the two, my screen only ever comes on when actually in use. This is awesome yet so simple, great idea, looking forward to further development.
RR

gomek111222 said:
it work in the test screen but when i back to home screen the green man doenst change to grey man whe i put the phone plz solve this
Click to expand...
Click to collapse
Do you mean the guy in the notification bar doesn't change colour?
martinvillar said:
I hope it doesn't kill my battery!
Click to expand...
Click to collapse
It should not, at all.
shameemindia said:
excellent application. its very useful. I would like to request you to implement a few extra features that will be handful in saving battery.
1. warning notification/dialogue for checking screen on time for more than 5 to 30 minutes. (even if the device is in motion or touchevents)
2. need screen timeout option to detect stillness. 1 min to 15 min
3. need to set screen off if the device is held vertical or horizontal ( bcoz we will not hold mobiles in 90 degree except when using camera.
Click to expand...
Click to collapse
More battery related features are coming in the PRO version. And another free feature to set accuracy has just been added to lite version too.
Thanks for your suggestions.
richierich said:
Love this app!!
Using it in conjunction with your other screen off app, and between the two, my screen only ever comes on when actually in use. This is awesome yet so simple, great idea, looking forward to further development.
RR
Click to expand...
Click to collapse
Glad you are enjoyng the smartness

[APP][2.3+][FREE] IntelliCover 2.0 - Display Automation using Proximity/Light

Hi there xda. A few months ago I posted my first app, IntelliCover, on xda-developers. It got a great response here and was featured on the front page of xda-developers and went on to feature on Discovery Channel's App Snap. Of course, being the smart person that I am...Well, let's just say I lost it...Yes, lost the app...Don't ask how. Anyways, I saw this as a chance to rebuild the app with all your suggestions in mind, from the ground up. So here it is, IntelliCover 2.0!
※ DESCRIPTION
IntelliCover 2.0 is a utility which uses your device’s proximity sensor, light sensor and/or accelerometer to turn the screen on and off, allowing fast and efficient access to your phone or tablet.
It turns the screen off automatically when you put your device in your pockets, close its flip cover, store the device in a bag, or even just leave the device facing down on a table. As soon as the device is back in your hand the proximity/light sensor is triggered again, the screen turns back on and your device in instantly ready for use. This improves productivity immensely on large devices or devices that do not have physical hardware buttons.
IntelliCover 2.0 is the completely revamped and redesigned version of IntelliCover, rebuilt from scratch after listening to the feedback of thousands of users.
※ COMPATIBILITY
IntelliCover works on all Android devices that have a light or proximity sensor, or an accelerometer. It does NOT require your device to be rooted.
※ FEATURES
• Sensor Calibration: Screen On Delay, Screen Off Delay, Suspension Timers, Application Suspension, Light/Shake Sensitivity Calibration
• Application Settings: Disable in Portrait/Landscape Mode, Go to Home Screen, Remove Lock Screen, Screen Off Only, Screen On Only, Start on Boot, Save Profile (Settings), Restore Profile, Restore Default Settings
• Modes: Proximity Mode, Shake Mode, Light Mode, Proximity and Light Combo Mode
• Notifications: Proximity Warning (Vibration), Status Bar Notification
• Toggles(Screen On/Off): Airplane Mode, Auto Sync, Bluetooth, Ringer Mode, Wi-fi
※ SCREENSHOTS
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
※ CHANGELOG
Version 1.0.5 (07/09/2013)
•Fixed problems caused by previous update
Version 1.0.4 (07/09/2013)
•Added Russian language
•Added Pocket Protector Mode
•Fixed crashes, wakelock problems and screen timeout issues
•More battery optimization
Version 1.0.3 (24/08/2013)
•Fixed the crashes caused by previous update.
Version 1.0.2 (24/08/2013)
•Fixed both crashing issues
•Fixed "Remove Lock Screen"
•Fixed "Go to Home Screen" for ignored apps (Application Blacklist)
•Fixed toggles for "Start on Boot"
•Added Widget
•Added Screen Timeout patch
•Removed multiple memory leaks (Battery Optimization)
•"Screen Off Only"/"Screen On Only" now completely turns off proximity sensor when display turns off/on
•Reformatted all text to make it translation-ready (Turkish/Italian versions coming soon)
Version 1.0.1 (15/08/2013)
• Fixed Device Admin cancellation bug.
• Removed all Device Admin permissions except for Force Lock.
Version 1.0.0 (14/08/2013)
- Application released.
※ DOWNLOAD
Link to the Play Store: IntelliCover 2.0 v1.0.5

Awesome app!
Thanks a lot! The app works flawlessly on my Note, really handy indeed.
One question, is this app compatible with tablets, specifically, Nexus 7? I'm not sure if I'm doing something wrong but I couldn't get it to work on that device.

samsung_karl said:
Thanks a lot! The app works flawlessly on my Note, really handy indeed.
One question, is this app compatible with tablets, specifically, Nexus 7? I'm not sure if I'm doing something wrong but I couldn't get it to work on that device.
Click to expand...
Click to collapse
I'm glad you like the app.
Yes, the app is designed to work on all tablets, and has been tested for compatibility on Nexus 7 specifically. Tablets do not have proximity sensor (usually) so you'll have to use it in "Light Mode" which uses the light sensor instead. Don't worry, it works just as well as the proximity sensor. If you are already using light mode, please let me know and I'll try to help you. Can you tell me which Android version you're using?

dragonnis said:
I'm glad you like the app.
Yes, the app is designed to work on all tablets, and has been tested for compatibility on Nexus 7 specifically. Tablets do not have proximity sensor (usually) so you'll have to use it in "Light Mode" which uses the light sensor instead. Don't worry, it works just as well as the proximity sensor. If you are already using light mode, please let me know and I'll try to help you. Can you tell me which Android version you're using?
Click to expand...
Click to collapse
Ah, sorry, my bad. It works great in light mode. I assumed tablets had a proximity sensor (I'm kinda new around here ).
One more thing. I'm not sure if this is a bug, but when the Device Administrator page popped up, I clicked cancel by mistake, but it kept showing up again and again until I clicked Activate. It kept reappearing unless I accepted it.
Thanks again!

samsung_karl said:
Ah, sorry, my bad. It works great in light mode. I assumed tablets had a proximity sensor (I'm kinda new around here ).
One more thing. I'm not sure if this is a bug, but when the Device Administrator page popped up, I clicked cancel by mistake, but it kept showing up again and again until I clicked Activate. It kept reappearing unless I accepted it.
Thanks again!
Click to expand...
Click to collapse
Whoops, that's a weird bug. This is what I get for adding last minute untested modifications. I should've known better. =/ Thanks for the tip, I'll fix it by the next update. =)

Released an absolutely vital mini update. If you are on V1.0.0, please update ASAP.
Version 1.0.1 (15/08/2013)
• Fixed Device Admin cancellation bug.
• Removed all Device Admin permissions except for Force Lock.

Hi Dev.
Thanks for making a very good apps for us.
I am using your Original IntelliCover & its work great
on my Nexus 4 with Cover Case, I am loving it.
Should I need to uninstall the IntelliCover 1 & install the IntelliCover 2...?
Google Play doesn't show up update alert for the new v2....???!!!!
Whats the different between IntelliCover 1 & 2, I see the new one have
much larger file size, 1000k vs 4000k, Which version will work
best on my Nexus 4...?
Thanks...!

Its good but takes lot of RAM compared to intellicover 1 (almost three times). Thank you for making this app anyways but I am still fine with intellicover 1 and that works great. I have to say one thing, for me both work flawless. Please keep intellicover 1 also on google play. Looks like it is removed now.

Small bug that annoy me a lot and improvement request
Bug
1. Remove lock screen will work for sometimes only. It will not work after sometime. It will go back to lock screen mode automatically even the option I already select.
Improvement request
1. When manually press the power button to off the screen, set the program off for temporary so it won't auto screen on again.
Other than that, it is one of the best app I like :laugh:

Talon88 said:
Hi Dev.
Thanks for making a very good apps for us.
I am using your Original IntelliCover & its work great
on my Nexus 4 with Cover Case, I am loving it.
Should I need to uninstall the IntelliCover 1 & install the IntelliCover 2...?
Google Play doesn't show up update alert for the new v2....???!!!!
Whats the different between IntelliCover 1 & 2, I see the new one have
much larger file size, 1000k vs 4000k, Which version will work
best on my Nexus 4...?
Thanks...!
Click to expand...
Click to collapse
I would recommend installing the new version since I will not be updating the old version anymore and the new one has more features. But the new version is still a little buggy since I had to rebuild the whole app, so if you want to wait a little bit, that makes sense too. I couldn't post an update on the old one because I lost the keys for the app and all its data as well. =( That's one reason I had to rebuild it. That's also why the old one hasn't been updated in months. The new one is a bigger filesize because it has a lot more features and a big UI upgrade. =)
raj_k_r said:
Its good but takes lot of RAM compared to intellicover 1 (almost three times). Thank you for making this app anyways but I am still fine with intellicover 1 and that works great. I have to say one thing, for me both work flawless. Please keep intellicover 1 also on google play. Looks like it is removed now.
Click to expand...
Click to collapse
Yes, I realize it is taking up quite a bit of RAM for some reason. I wanted to get the app out there but I haven't started optimizing it completely yet. It makes sense for you to use IntelliCover 1 for now, but I plan on rolling out alot of updates soon that will optimize it, so keep an eye out.
phonixloo said:
Bug
1. Remove lock screen will work for sometimes only. It will not work after sometime. It will go back to lock screen mode automatically even the option I already select.
Improvement request
1. When manually press the power button to off the screen, set the program off for temporary so it won't auto screen on again.
Other than that, it is one of the best app I like :laugh:
Click to expand...
Click to collapse
The lock screen issue is a known bug. I'm working on fixing it as soon as I can, hopefully by next update. Manually pressing the power button should keep the screen off...Hmmm...are you using the proximity sensor or the light sensor?

dragonnis said:
The lock screen issue is a known bug. I'm working on fixing it as soon as I can, hopefully by next update. Manually pressing the power button should keep the screen off...Hmmm...are you using the proximity sensor or the light sensor?
Click to expand...
Click to collapse
In fact I would like to have featured once press the power button to shut off screen, it can automatically disable the program until we manually unlock the screen.
By the way I use proximity sensor only.
Sent from my HTC One X using xda premium

phonixloo said:
In fact I would like to have featured once press the power button to shut off screen, it can automatically disable the program until we manually unlock the screen.
By the way I use proximity sensor only.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Yes, I'm adding that option too. It's been requested by many users, so I'll add it to "Screen Off Only" for the next update. =)

@dragonnis
im using galaxy tab which have no proximity only light sensor.
the program shut my screen too often while im still using the tab.
i have calibrated the app but still it is not working.
i do hope you can include a option to activate in lock screen or similar.
also would like to have tasker/llama/locale option of enabling dissabling of the app.
thanks

eclair88 said:
@dragonnis
im using galaxy tab which have no proximity only light sensor.
the program shut my screen too often while im still using the tab.
i have calibrated the app but still it is not working.
i do hope you can include a option to activate in lock screen or similar.
also would like to have tasker/llama/locale option of enabling dissabling of the app.
thanks
Click to expand...
Click to collapse
Once you calibrate the light sensor to a specific value, it will turn off as soon as it reaches that value. So if you have calibrated it for your bag, the screen may also turn off if you are in a pitch black room, because it has the same light sensor value. I've made the only workaround to this that I can think of, which is that if you are in a dark room, and you press the power button to turn the screen on, it won't turn off again automatically until the light value changes or you press the power button again.
But yes, I will be adding the "Only activate during lockscreen" option in a future update. =)
Edit: Not sure about how to create tasker/llama/locale plugins but I'll check it out as soon as I have time.

Pretty massive update. Fixes alot of common bugs. Thanks for sending in your reports! =)
Version 1.0.2 (24/08/2013)
•Fixed both crashing issues
•Fixed "Remove Lock Screen"
•Fixed "Go to Home Screen" for ignored apps (Application Blacklist)
•Fixed toggles for "Start on Boot"
•Added Widget
•Added Screen Timeout patch
•Removed multiple memory leaks (Battery Optimization)
•"Screen Off Only"/"Screen On Only" now completely turns off proximity sensor when display turns off/on
•Reformatted all text to make it translation-ready (Turkish/Italian versions coming soon)

Hi there, I cannot get this to work correctly on my HTC One. I have tried with both Sense and Aosp lockscreens. Is there something I need to do instead? I wave my hand in front and I can see the screen blink for a second and then that's it. Any help is appreciated. Thanks!

pmt223 said:
Hi there, I cannot get this to work correctly on my HTC One. I have tried with both Sense and Aosp lockscreens. Is there something I need to do instead? I wave my hand in front and I can see the screen blink for a second and then that's it. Any help is appreciated. Thanks!
Click to expand...
Click to collapse
Hello. Interesting, I've tried on the International HTC One but I've received a couple reports about the Sprint version having issues. Could you please tell me which model your phone is? I'm having a little trouble analyzing the issue without a device because turning the screen off is a native Android function that I just need to call upon so I'm not sure where the error lies but I'll try to get my hands on a device. Did the app ask you for Administrator Privileges? Also, if you turn on "Proximity Warning" from the Application Settings menu, do you feel a vibration on triggering the proximity sensor (Just to make sure the proximity sensor's being triggered)?
One last thing I'd like to ask is, does it work when you use your finger instead of a cover? Many proximity sensors don't do well with specific colors. I've had to stick a little piece of paper on my own cover where the proximity sensor lies because the dark brown leather makes the sensor go nuts.
EDIT: Just saw your signature and realized you have the AT&T version. Did anything I mentioned above work?

Released a quick-fix update. Please update to v1.0.3 to avoid the crashes caused by the v1.0.2 update

Awesome, the lock screen removal is fixed. :good:

samsung_karl said:
Awesome, the lock screen removal is fixed. :good:
Click to expand...
Click to collapse
Yup. Tested for a long time before I realized the issue was caused because whenever a notification in the status bar is clicked, the KeyGuard (Lock Screen) gets reset. I just had to detect when one of those notifications is clicked and run the deactivation process again.

proximity sensor issue

hello,
I've got issue with my S7. The proximity sensor doesn't always work with the phone app, or with the alwaysOn display to switch it off in the pocket. I have tested it with the *#0*# code. This shows a well working sensor.
Has someone an idea of what could disable the proximity sensor for apps?
Thank you for answers.
Regards
Frederic B.

I have the same problem, I don't know how to resolve that, please help someone

Hello.
I had the same problem. I didn't know if it was because of the last update or because of some packages I disabled with Package Disable Pro. I resolved the problem by reactivate all the packages and restart the phone. I again disabled some stuff and the proximity sensor is still working now.
Sent from my SM-G930K using XDA-Developers mobile app

...does NOT switch back
I have an issue, my sensor switches the screen black while doing a call, but does NOT switch back. So it's hard for me to finish a call. Checking with *#0*# code tells: away=8cm, near=0cm. but never switches back to 8cm if away from ear.
Stock Samsung, Factory reset didn't solve this. Is the sensor defective itself?

Hi, I also have a problem with my S7 proximity sensor. By checking *#0*# it seems to be totally dead. Is there anything I can do to try to fix it?

I also have same problem, my proximity sensor is not working. Please see attached images, the PROXIMITY always stays 0. So does that means proximity sensor is dead. Phone is still on warranty so I intend to take it back for repair.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I have a similar problem. The proximity sensor itself works flawlessly during calls and in the test menu, but even though I have the "don't wake up in pocket" enabled in the screen settings, it always wakes and turns the screen on (and starts to make accidental clicks) when in pocket and the home button is accidentally pressed by my leg/pocket. I made a factory reset which didn't help. I don't use Package Disabler Pro, so that shouldn't cause the issue. Any help on this?

Proximity sensor
I have found that if you uninstall Samsung pay the proximity sensor works correctly. For me it's still worked when I reinstalled Samsung pay but stopped working when I added the first credit card.

JMM_AZ said:
I have found that if you uninstall Samsung pay the proximity sensor works correctly. For me it's still worked when I reinstalled Samsung pay but stopped working when I added the first credit card.
Click to expand...
Click to collapse
I had the problem until I went into the settings of SP and unticked the option to use "favourite card", the thing that makes the tip of a card sit at the bottom edge of the screen all the time.

Mine also stopped working, i was thinking of giving it back on warranty for further checking but as a last resort I reset my phone and now it started working just fine. Not sure what was the reason, I installed everything through backs back to phone and sensor is still working.

Same problem here.
I have done a Factory Reset but the trouble still persists...
Anyone else has had this trouble??

In my case i was abt to give it back in warranty. To prepare for that i backed uo and did a factory reset and since then sensor is working fine.
Sent from my SM-G935F using Tapatalk

lazers378 said:
In my case i was abt to give it back in warranty. To prepare for that i backed uo and did a factory reset and since then sensor is working fine.
Sent from my SM-G935F using Tapatalk
Click to expand...
Click to collapse
I have done a factory reset, but I'm on Superman ROM..... maybe I should flash a normal ROM??? I have tried two different versions of this rom, and always worked fine...

RinCEWinG said:
I have done a factory reset, but I'm on Superman ROM..... maybe I should flash a normal ROM??? I have tried two different versions of this rom, and always worked fine...
Click to expand...
Click to collapse
Well i think you should try. I am on stock ROM. Prior to reset i was also convinced that it is hardware issue but turned out otherwise.
Sent from my SM-G935F using Tapatalk

Let's see if this works
gerhard_wa said:
I had the problem until I went into the settings of SP and unticked the option to use "favourite card", the thing that makes the tip of a card sit at the bottom edge of the screen all the time.
Click to expand...
Click to collapse
I have been plagued by this problem for months now. It just seemed to pop up all of the sudden.
Either the screen would come on in my pocket, even though my screen is always off, or I'd go to pick up the phone to see what time it was and a proxemity warning , LARGE and ANNOYING, would cover the entire screen... sucks at 2am in the dark.
So...
SamPay has three options in Use favorite cards setting
O Lock Screen
O Home screen
O Screen off
All three were "on"
I will disable 'Screen off' first and see if that fixes my problem. If not I will work my way up the list.
I will (hopefully) report back in a day or two. IF it works for me, perhaps it will work for others.
Really what I want is an unlocked bootloader damnit.
Science is like sex,
Sometimes something good comes
but that's not the reason for doing it.
R. Feynman

Factory reset helped me when I had this issue. Good Luck!

Had the issue with a non working proximity sensor just out of the box and after the initial consequent updates all the way to Nougat. Found this thread and one day before sending it to the service center, tried the factory reset and works flawlessly ever after! Probably confirming the rule to reset once after every major update...!

Hello!
I have a problem with my proximity sensor and lights sensor too (see attached screenshot).
I have checked it with *#0*#.
It seems that the sensors will not be detected. The LED ist working.
A Factory reset didn't help.
What could be the problem?

Hello, any idea of what happened with all this sensors and the solution??
My problem is worst, because NONE sensor is working :crying: :crying:
Image of what is happening when i open the sensors!