Database Info

[Q] activesync / exchange 2010 sp1 issues - update for corporate email app?

we've got a new exchange 2010 server with sp1 installed and are having some strange issues. it seems that there is something about the activesync implementation that is not playing nice with certain versions of android/corporate email app. we can get touchdown and a droid 2 to work without issue, but droid 1 and evo aren't working properly.
when we try to configure the droid 1 or evo, the quick setup errors out with "username or password incorrect." forcing it into the advanced setup causes it to error with "unable to open connection to server."
going into owa > options > phone to check the details, here's what we see for the droid 1
touchdown:
====================================
View Mobile Phone Details
Status: OK
First sync:
9/24/2010 12:39 AM
Last successful sync: 10/3/2010 2:27 PM
Folders synced: 21
Device name:
Not Available
Device model: Android
Phone number: Not Available
Mobile network: Not Available
Device type: Android
Device ID: XXREDACTEDXXX
Device IMEI: Not Available
Device OS:
Not Available
Device language: Not Available
User agent: TouchDown(MSRPC)/6.1.0007
Access state:
Access Granted
Access set by: Global Permissions
Policy applied:
Default - Applied in full
Policy updated: 10/3/2010 2:27 PM
ActiveSync version: 12.1
====================================
droid corporate app:
====================================
View Mobile Phone Details
Status: OK
First sync:
10/3/2010 5:11 PM
Last successful sync: Not Available
Folders synced: 0
Device name:
Not Available
Device model: Android
Phone number: Not Available
Mobile network: Not Available
Device type: Android
Device ID: validate
Device IMEI: Not Available
Device OS:
Not Available
Device language: Not Available
User agent: Android/0.3
Access state:
Access Denied
Access set by: Security Policy Application
Policy applied:
Default - Not applied
Policy updated: Not Available
ActiveSync version: 12.0
====================================
we've checked the security policy and the default policy and they're wide open - at least until we get things working.
the only thing that seems really different is the activesync version. for the droid 2, the user agent is different than the droid 1, my apologies but i can't paste that result in here at the moment.
any idea if there is a way to update the corporate email app on the droid 1 and evo to whatever the droid 2 is using?
some googling turns up the following thread which seems to indicate that it's a client side issue and that there is a fix pending, any thoughts on why it would work for a droid 2 currently? - code.google.com/p/android/issues/detail?id=11272 and code.google.com/p/android/issues/detail?id=11177
thanks for any assistance,
philo

Answer & Callback

Auto answer or callback on the selected numbers.
If you hands are full and you want to have your phone automatically answer and called back to the selected number, Answer & Callback program for you.
Program features:
- Auto answer, if the number is in your contacts.
- Auto reply to selected number.
- Call to the selected number.
- It works only when a headset is connected.
- The task execution delays.
XDA:DevDB Information
Answer & Callback, App for all devices (see above for details)
Contributors
[email protected]
Source Code: https://play.google.com/store/apps/details?id=mag.com.tel.autoanswer
Version Information
Status: Alpha
Current Stable Version: 1.1
Current Beta Version: 1.2
Created 2015-12-21
Last Updated 2016-09-13

Reserved

Reserved

Apk updating, V1.7

Promo codes:

Thank you... Used the first one and gave rating on playstore aswell

I wonder how it works on Android 7?

New Pro version https://play.google.com/store/apps/details?id=mag.com.infotel

New version.
Interface material design.
Support Android 7.
Fix problem Android 5.1

Amazon store https://www.amazon.com/gp/product/B01N3CXNXB

This app runing for Anronoid 8, result is excellent

Ever want to let the phone answers the call automatically when you are driving, or riding a bicycle, or busy doing something with both hands, or simply don't want to press that little button because your hands are dirty, then this app is for you.
"Smart Answer & Callback" does only one thing and it does it well, it auto answers your calls for you so now it can truly be called "hands-free".
Even more, it can also detect that a Bluetooth hands-free device is connected and automatically enable the auto answer, then disable auto answer when the Bluetooth device is disconnected.
Program features:
- Auto answer, if the call is in your contacts.
- Auto callback to selected call.
- Call to the selected.
- It works only when a headset is connected.
- The task execution delays.

Very good application. Works perfectly
Thanks a lot!

https://play.google.com/store/apps/details?id=mag.com.tel.autoanswer
New version app. Support Android 8.
Program features:
- Auto answer, if the call is in your contacts.
- Auto callback to selected call.
- Call to the selected.
- It works only when a headset is connected.
- The task execution delays.

New version 2.5 Sunnport Android API 27

New version V2.6
Added widget.
Support Android 9.

New version V2.7 https://play.google.com/store/apps/details?id=mag.com.tel.autoanswer
Added widget.
Support Android 9.
Fixsed bug

[Completed] how to convert LTE TO VOLTE in samsung tab s sm T805

processors is EXYNOS octa 5420,baseband ver.T805DDU1CPH7,
KERNAL VER. 3.4.39-9123340
[email protected] #1
Tue Aug 3p 15:25:30 KST 2016 , Build number MMB29K.T805DDU1CPH7

XDA Visitor said:
processors is EXYNOS octa 5420,baseband ver.T805DDU1CPH7,
KERNAL VER. 3.4.39-9123340
[email protected] #1
Tue Aug 3p 15:25:30 KST 2016 , Build number MMB29K.T805DDU1CPH7
Click to expand...
Click to collapse
Hello,
LTE and VoLTE are completely different to each other.
VoLTE is better known as voice over LTE.
Voice over Long-Term Evolution (VoLTE) is a standard for high-speed wireless communication for mobile phones and data terminals. It is based on the IP Multimedia Subsystem (IMS) network, with specific profiles for control and media planes of voice service on LTE defined by GSMA
Click to expand...
Click to collapse
You can't convert it, your chipset needs to support it and your OEM has to push a required update for it to work.
Please register for XDA account to post and reply in the forum.
Regards
Vatsal,
Forum Moderator.

[GUIDE][DeX] Using DeX mode at custom resolutions (1440p+) on a rooted phone

Hello everyone. I've been looking around for ages to find out how to run DeX mode at my TV's resolution (3840x2160). I just wasn't satisfied with the FHD (1080p) limitation and was annoyed that WQHD (1440p) was greyed out (my TV did not support this resolution).
After buying multiple docks, messing with APKs, fiddling around in the terminal and endless amounts of frustration; I've finally found a work-around that will allow DeX to display a decent picture at UDH (2080p).
Before you get too excited, you should know this:
DeX CAN NOT natively render at 4k on the Galaxy S8. It is limited to its internal rendering resolution of 1440p. What you'll see is 1440p upscaled to 2160p (or whichever resolution you choose) by the phone.
You will need to repeat this trick every time you want to reach your desired resolution after re-connecting to your TV/monitor.
This will make your phone run hot, I have only tried this with success on the official Samsung DeX pad, which has fans to cool your phone.
Due to the 1440p limitation, you cannot actually view 4k content using DeX. You can verify this limitation by making a screenshot of your DeX desktop; it will be in 2560x1440.
The upscaling is performance-intensive, don't be surprised if you encounter some stuttering.
I have only tested this on the Exynos model of the Galaxy S8. I have also only tested 3840x2160.
You do this at your own risk. You agree that I will not be held responsible if things don't work or go wrong.
Now, that said, there is still benefit in this. You will be able to make better use of your screen real-estate even if the content is upscaled. However, I'd seriously recommend sticking to FHD if you're just watching videos.
Requirements:
Official Samsung firmware, preferably the latest version of Android 9 available.
Root access through SuperSU or equivalent.
A terminal emulator or shell, I use Termux.
Discipline to follow these steps exactly. Failure to do so will hard reset your phone.
(Optional) A mouse and keyboard for easier use of the terminal.
Now for the steps, please follow these exactly as listed.
Part A - steps to (re)activate your desired resolution:
Connect your phone to your TV/monitor and switch to DeX mode.
Use the DeX settings dialog to select the highest available resolution.
Open up your terminal emulator on the phone screen.
Use
Code:
su
to switch to the root user.
Change to the directory where we'll make changes with
Code:
cd /sys/class/dp_sec/
and use
Code:
ls
to verify that you have the "files" named "dex" and "forced_resolution".
Use this command:
Code:
echo 0 > dex
For some reason or the other, this won't disable DeX, but will screw with its rendering and allow you to make resolution changes.
Find your desired resolution using
Code:
cat forced_resolution
Mine looks like this:
Code:
0 : [email protected]
1 : [email protected]
2 : [email protected]
3 : [email protected]_RB
4 : [email protected]
5 : [email protected]
6 : [email protected]
7 : [email protected]
8 : [email protected]_98
9 : [email protected]
10 : [email protected]
11 : [email protected]
12 : [email protected]
13 : [email protected]
14 : [email protected]
15 : [email protected]_2
16 : [email protected]
17 : [email protected]
18 : [email protected]
19 : [email protected]
20 : [email protected]
21 : [email protected]
22 : [email protected]
23 : [email protected]
24 : [email protected]
25 : [email protected]
26 : [email protected]
27 : [email protected]
28 : [email protected]
29 : [email protected]_RB
30 : [email protected]
31 : [email protected]
32 : [email protected]
33 : [email protected]
To switch to your desired resolution, use the number listed on your device. For example, I want [email protected] My phone associates this resolution with number 31, so I use this command:
Code:
echo 31 > forced_resolution
If all went well, DeX is now outputting in WQHD, upscaled to your desired resolution. You can verify this in the DeX settings dialog (do not change this setting while running this hack).
Enjoy. When you're done with DeX, you must follow part B!. Failure to do so will cause a hard reset next time you plug in the phone again and switch to DeX mode.
Part B - required clean-up:
Ensure your phone is not in DeX mode nor Screen Mirror mode. Either disconnect from the dock, or switch to Fast Charging.
Follow steps 1 through 5 from part A.
Reset the forced resolution by using this command:
Code:
echo > forced_resolution
Hope this helps you! This stuff could probably be automated with Tasker and some shell scripts - but that's for sometime in the further (you can do it yourself if you'd like).
Let me know what your experience has been and if this is a successful hack for your TV/monitor.
Further things I am looking into:
Hacking the DeX .apk to support native 4k.
Porting the DeX system apps from newer Galaxy phones to the S8 (no luck yet, these apps crash even if API-compatible).
Automation of these steps for the sake of convenience and foolproof-ness.
If this stuff motivates you to do any of those things, feel free to discuss it in this thread and maybe we can make a community effort to improve this.

Very nice man
:laugh:
maybe if you request a automation inside of this kernel
Hacking the DeX .apk to support native 4k.
Porting the DeX system apps from newer Galaxy phones to the S8 (no luck yet, these apps crash even if API-compatible).
Automation of these steps for the sake of convenience and foolproof-ness.
https://forum.xda-developers.com/ga...velopment/kernel-a2n-kernel-20181205-t3875640
the dev of this kernel has advanced skills to do that

rn2web said:
Very nice man
:laugh:
maybe if you request a automation inside of this kernel
Hacking the DeX .apk to support native 4k.
Porting the DeX system apps from newer Galaxy phones to the S8 (no luck yet, these apps crash even if API-compatible).
Automation of these steps for the sake of convenience and foolproof-ness.
https://forum.xda-developers.com/ga...velopment/kernel-a2n-kernel-20181205-t3875640
the dev of this kernel has advanced skills to do that
Click to expand...
Click to collapse
It's kinda confusing on Part B, bacause you stated at Part B, step 1.
Ensure your phone is not in DeX mode nor Screen Mirror mode. Either disconnect from the dock, or switch to Fast Charging. Then at Step 2 you say follow steps 1 through 5 at Part A, on which on Part A, step 1. Connect your phone to your TV/monitor and switch to DeX mode., this already a conflict to the Part B, step 1 rule. and you have a warning that failure to do so will cause a hard reset next time you plug in the phone again and switch to DeX mode.

Natrox said:
Hello everyone. I've been looking around for ages to find out how to run DeX mode at my TV's resolution (3840x2160). I just wasn't satisfied with the FHD (1080p) limitation and was annoyed that WQHD (1440p) was greyed out (my TV did not support this resolution).
After buying multiple docks, messing with APKs, fiddling around in the terminal and endless amounts of frustration; I've finally found a work-around that will allow DeX to display a decent picture at UDH (2080p).
Before you get too excited, you should know this:
DeX CAN NOT natively render at 4k on the Galaxy S8. It is limited to its internal rendering resolution of 1440p. What you'll see is 1440p upscaled to 2160p (or whichever resolution you choose) by the phone.
You will need to repeat this trick every time you want to reach your desired resolution after re-connecting to your TV/monitor.
This will make your phone run hot, I have only tried this with success on the official Samsung DeX pad, which has fans to cool your phone.
Due to the 1440p limitation, you cannot actually view 4k content using DeX. You can verify this limitation by making a screenshot of your DeX desktop; it will be in 2560x1440.
The upscaling is performance-intensive, don't be surprised if you encounter some stuttering.
I have only tested this on the Exynos model of the Galaxy S8. I have also only tested 3840x2160.
You do this at your own risk. You agree that I will not be held responsible if things don't work or go wrong.
Now, that said, there is still benefit in this. You will be able to make better use of your screen real-estate even if the content is upscaled. However, I'd seriously recommend sticking to FHD if you're just watching videos.
Requirements:
Official Samsung firmware, preferably the latest version of Android 9 available.
Root access through SuperSU or equivalent.
A terminal emulator or shell, I use Termux.
Discipline to follow these steps exactly. Failure to do so will hard reset your phone.
(Optional) A mouse and keyboard for easier use of the terminal.
Now for the steps, please follow these exactly as listed.
Part A - steps to (re)activate your desired resolution:
Connect your phone to your TV/monitor and switch to DeX mode.
Use the DeX settings dialog to select the highest available resolution.
Open up your terminal emulator on the phone screen.
Use
Code:
su
to switch to the root user.
Change to the directory where we'll make changes with
Code:
cd /sys/class/dp_sec/
and use
Code:
ls
to verify that you have the "files" named "dex" and "forced_resolution".
Use this command:
Code:
echo 0 > dex
For some reason or the other, this won't disable DeX, but will screw with its rendering and allow you to make resolution changes.
Find your desired resolution using
Code:
cat forced_resolution
Mine looks like this:
Code:
0 : [email protected]
1 : [email protected]
2 : [email protected]
3 : [email protected]_RB
4 : [email protected]
5 : [email protected]
6 : [email protected]
7 : [email protected]
8 : [email protected]_98
9 : [email protected]
10 : 1920x[email protected]
11 : [email protected]
12 : [email protected]
13 : [email protected]
14 : [email protected]
15 : [email protected]_2
16 : [email protected]
17 : [email protected]
18 : [email protected]
19 : [email protected]
20 : [email protected]
21 : [email protected]
22 : [email protected]
23 : [email protected]
24 : [email protected]
25 : [email protected]
26 : [email protected]
27 : [email protected]
28 : [email protected]
29 : [email protected]_RB
30 : [email protected]
31 : [email protected]
32 : [email protected]
33 : [email protected]
To switch to your desired resolution, use the number listed on your device. For example, I want [email protected] My phone associates this resolution with number 31, so I use this command:
Code:
echo 31 > forced_resolution
If all went well, DeX is now outputting in WQHD, upscaled to your desired resolution. You can verify this in the DeX settings dialog (do not change this setting while running this hack).
Enjoy. When you're done with DeX, you must follow part B!. Failure to do so will cause a hard reset next time you plug in the phone again and switch to DeX mode.
Part B - required clean-up:
Ensure your phone is not in DeX mode nor Screen Mirror mode. Either disconnect from the dock, or switch to Fast Charging.
Follow steps 1 through 5 from part A.
Reset the forced resolution by using this command:
Code:
echo > forced_resolution
Hope this helps you! This stuff could probably be automated with Tasker and some shell scripts - but that's for sometime in the further (you can do it yourself if you'd like).
Let me know what your experience has been and if this is a successful hack for your TV/monitor.
Further things I am looking into:
Hacking the DeX .apk to support native 4k.
Porting the DeX system apps from newer Galaxy phones to the S8 (no luck yet, these apps crash even if API-compatible).
Automation of these steps for the sake of convenience and foolproof-ness.
If this stuff motivates you to do any of those things, feel free to discuss it in this thread and maybe we can make a community effort to improve this.
Click to expand...
Click to collapse
It's kinda confusing on Part B, bacause you stated at Part B, step 1.
Ensure your phone is not in DeX mode nor Screen Mirror mode. Either disconnect from the dock, or switch to Fast Charging. Then at Step 2 you say follow steps 1 through 5 at Part A, on which on Part A, step 1. Connect your phone to your TV/monitor and switch to DeX mode., this already a conflict to the Part B, step 1 rule. and you have a warning that failure to do so will cause a hard reset next time you plug in the phone again and switch to DeX mode.

How to install samsung Dex on one ui core. On my tab a7

Support desired px3 update

Hello,
First of all, I would like to let you know through this way that English is not my native language and therefore the sentences and words will not always be fluent.
Secondly, I don't know if I posted this question in the right subtopic. Moderators, please feel free to move this question.
I recently purchased a 2012 Volkswagen Polo. This, when purchased, already had an Android tablet built in. I have no idea what model tablet it is but I have the following information available:
Model:
px3 (1024x600 O)
Android version:
7.1.2
Level of Android security patch:
May 5, 2017
Kernel version:
3.0.101+
[email protected] #894
Thu Jan 25 18:26:25 CST 2018
Build number:
px3-usrdebug 7.1.2 NHG47L eng.hct.20180131.123949 test-keys
MCU version:
MTCE_GS_V2.83_3
Apr 13 2018 21:00:04
CPU:
ARM Coretex-A9 @1.6GHz (x4)
Memory:
2048 MB
I was curious if I can find a newer firmware version somewhere for this tablet incl. instructions on how to install it.
I have sporadic problems with the radio (it sometimes goes louder unwanted or forgets my set favorites). In addition, I see several videos passing by where the interface is just a bit more slick and updated.
Can anyone help me with this? Thanks in advance and apologies if I seem a bit stupid / ignorant (I am however an ICT-er so I understand somewhat how certain things work).

You might be better off replacing the unit.
You could replace the SOM with a PX6 board (4gb+ ram) and then upgrade to Android 11, but these MTCx units remain behind on what is offered by the FYT units with UIS7862 processors.