[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4692: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4694: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4695: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4696: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3823)
rSAP for Android Forum • View topic - Motorola / Lenovo Moto Z 2016/17 ?
It is currently Thu Aug 16, 2018 10:56 am

rSAP for Android Forum

Support forum for Android rSAP App

Motorola / Lenovo Moto Z 2016/17 ?

Discussions about running the rSAP app on Motorola phones
 
Posts: 14
Joined: Thu Sep 17, 2015 3:32 pm

Motorola / Lenovo Moto Z 2016/17 ?

Post by Liftboy » Mon Apr 24, 2017 2:33 pm

Hi !

Has somebody experience with the above model before I'll buy one? Das wäre doch schön ;)

Regards,

Frank

 
Posts: 14
Joined: Thu Sep 17, 2015 3:32 pm

Re: Moto Z - Problem

Post by Liftboy » Tue Apr 25, 2017 4:54 pm

With LineageOS and root:

Generisch Mk II:
- Systemdateien werden installiert
X Socket Verbindung
X SIM Verbindung

Generisch Mk III:
- Installierte Systemdatein:
Generic UIM SAP Mk.III 64bit - V3.04
- Socket Verbindung
X SIM Verbindung

Parameter 'StatusChange' hat nicht den Wert 'CardREset'
qmi_error = QMI_ERR_ACCESS_DENIED

O Recovery installation won't work

It will go on here?

http://www.android-rsap.com/enable-qual ... ccess.html

 
Posts: 4081
Joined: Wed Mar 23, 2011 4:12 pm

Re: Motorola / Lenovo Moto Z 2016/17 ?

Post by admin » Tue Apr 25, 2017 6:48 pm

Yes...

 
Posts: 14
Joined: Thu Sep 17, 2015 3:32 pm

Re: Motorola / Lenovo Moto Z 2016/17 ?

Post by Liftboy » Wed Apr 26, 2017 11:30 am

Sorry, before I start the procedure - this will be the soulution after the installer won't work for the 820 CPU in the Moto Z ?

Frank

 
Posts: 4081
Joined: Wed Mar 23, 2011 4:12 pm

Re: Motorola / Lenovo Moto Z 2016/17 ?

Post by admin » Wed Apr 26, 2017 3:34 pm


 
Posts: 14
Joined: Thu Sep 17, 2015 3:32 pm

Re: Moto Z - Problem

Post by Liftboy » Thu Apr 27, 2017 7:02 am


 
Posts: 4081
Joined: Wed Mar 23, 2011 4:12 pm

Re: Motorola / Lenovo Moto Z 2016/17 ?

Post by admin » Fri Apr 28, 2017 8:30 am

"Access Denied" muss mit QPST behoben werden, falls es die Installer App nicht automatisch hinbekommt. Dies ist der Fall, wenn ein bestimmter Treiber im Kernel fehlt, den man ansonsten nicht vermisst, wenn man nicht gerade rSAP freischalten möchte...

Es gibt allerdings noch die Variante, dass mit QPST zuerst der "Factory Test Mode" aktiviert und anschließend neu gebootet werden muss. Manche Telefone "vergessen" den Test Mode beim Booten, so dass es leider nicht möglich ist rSAP zu aktivieren. Wenn die Installer App bereits den Test Mode einschalten wollte und nach dem Reboot immer noch scheitert, hilf QPST ziemlich sicher auch nicht.

 
Posts: 14
Joined: Thu Sep 17, 2015 3:32 pm

Re: Motorola / Lenovo Moto Z 2016/17 ?

Post by Liftboy » Fri Apr 28, 2017 9:28 am

I'll try it with QST. The try about the installer TWRP out of the option from the Installation App won't work.

Ich werde es also mit QST probieren. Den Versuch über den Installer (TWRP) habe ich bereits mit der Option der Installations App "Recovery Installation verwenden" unternommen.

Ist der "Mangel" an Systemdateien ein Problem des LineageOS oder der Motorola Firma? Ich vermute das Baseband hat damit weniger zu tun.
LineageOS auf dem Nexus 6 beispielsweise läuft streßfrei mit der rSAP App seit Monaten. Auch ein Sony Z Gerät macht da wenig Probleme mit LineageOS bisher.

Mit den Moto Z wird gerade mit halben Preis der Markt "geflutet" und das Interesse wird sich häufen ;)

Vielen Dank bis hier hin!


Frank

 
Posts: 14
Joined: Thu Sep 17, 2015 3:32 pm

Re: Motorola / Lenovo Moto Z 2016/17 ?

Post by Liftboy » Sun Apr 30, 2017 4:41 pm

Should there be a soulution within the lineageOS?

https://forum.xda-developers.com/moto-z ... st72103011

Till now I didn't get a com port communicatoin with this Win10 and the phone. So I couldn't check out if the Qualcomm tool is working.



Frank

 
Posts: 4081
Joined: Wed Mar 23, 2011 4:12 pm

Re: Motorola / Lenovo Moto Z 2016/17 ?

Post by admin » Sun Apr 30, 2017 6:54 pm

I'll try to explain the whole rSAP problem:

All Qualcomm phones basically support rSAP inside their baseband software. But nearly all phones (except HTC, LG and some others) miss the software parts between Bluetooth and baseband. This is what my app does. It creates a Bluetooth service and routes the rSAP functions to the baseband/radio. The last step requires the system files, which hook into the "Radio Interface Layer".

Some time ago Qualcomm added another hurdle to access the rSAP functions in the baseband software. You need to create a file in the baseband file system. This is done with the QPST tool. If you don't, all rSAP functions return an "access denied" error. Recently newer phones don't even allow the creation of the file without a "Factory Test Mode" being active.

Maybe I should also mention that the baseband software is a whole system running next to Android which handles (among others) all radio connections and the SIM card. It is completely closed source! When you install LineageOS or some other custom ROM you still use the stock baseband software. So it doesn't really care which Android you use, except the ever increasing security restrictions of newer Android versions and Bluetooth problems because of the incomplete Android Bluetooth API.

Next

Return to Motorola

Who is online

Users browsing this forum: No registered users and 2 guests