My phone is currently subscribed to a CDMA network. I am able to receive text messages fine in WinMo, but when I boot FRX07.1 I am unable to receive them.
I can send and receive calls, and send texts with no problem. I have tried a variety of radio roms, and I have also set up the "special" RIL that is in the frx07 thread.
I am running energyROM in winmo world.
Can anyone shed some light on this issue for me?
scottrea said:
My phone is currently subscribed to a CDMA network. I am able to receive text messages fine in WinMo, but when I boot FRX07.1 I am unable to receive them.
I can send and receive calls, and send texts with no problem. I have tried a variety of radio roms, and I have also set up the "special" RIL that is in the frx07 thread.
I am running energyROM in winmo world.
Can anyone shed some light on this issue for me?
Click to expand...
Click to collapse
Last time I checked, this is the WinMo section not the Android section... You should've posted in the build thread. I know, you probably tried and it said you don't have enough posts .
Anyhoo, boot Android with WinMo in airplane mode. No radios should on in WinMo when booting Android.
Also might be a good idea to make sure your phone is on the latest radio firmware. I don't think there's any "special" RIL needed if you follow the steps above.
The description of this section makes no reference to one OS or the other...
Anyway,
I am currently on "Other" carrier, (tbaytel, municipally owned provider in Ontario Canada)
Do you have a suggestion for the radio? I have tried:
SPCS 2.32.00WF
Telus_1.92.00WV
2.37WV (from Neodium rom install)
Tried the airplane mode on boot thing with no luck.
The RIL fix I tried was posted by you actually: http://forum.xda-developers.com/showpost.php?p=17783461&postcount=1269
scottrea said:
The description of this section makes no reference to one OS or the other...
Anyway,
I am currently on "Other" carrier, (tbaytel, municipally owned provider in Ontario Canada)
Do you have a suggestion for the radio? I have tried:
SPCS 2.32.00WF
Telus_1.92.00WV
2.37WV (from Neodium rom install)
Tried the airplane mode on boot thing with no luck.
The RIL fix I tried was posted by you actually: http://forum.xda-developers.com/showpost.php?p=17783461&postcount=1269
Click to expand...
Click to collapse
You're not very observant, are you.
First, that post was clearly made by detule (he only quoted my directions on where to put it/how to bind mount it). Second, booting Android while WinMo is in airplane mode fixes the issue that is patched in that RIL, so if that doesn't fix the problem than the RIL won't do anything either.
Third, of course this section is for WinMo. It's the Touch Pro2 "General" section - last time I checked, WinMo was made for this device from the factory, and Android is just an add-on/port that currently sits on top of WinMo. Hence the Android section .
I use 2.37WV, which is the newest Verizon radio. I have a Sprint device, but this new radio seems to work really well, despite the provider being different.
I grabbed this log after sending a sms to the phone, which was not received. Would anyone be interested in looking at it?
Edit: I ran GetLogs again and found the following lines in the radio log:
12-06 11:38:54.650 D/RILC ( 1335): Inside responseCdmaSms
12-06 11:38:54.660 D/RILJ ( 1433): [UNSL]< UNSOL_RESPONSE_CDMA_NEW_SMS
12-06 11:38:54.660 D/SMS ( 1433): New SMS Message Received
12-06 11:38:54.660 E/SMS ( 1433): BearerData decode failed: com.android.internal.telephony.cdma.sms.BearerData$CodingException: invalid SMS address DTMF code (0)
12-06 11:38:54.670 E/SMS ( 1433): Exception dispatching message
12-06 11:38:54.670 E/SMS ( 1433): java.lang.NullPointerException
12-06 11:38:54.670 E/SMS ( 1433): at com.android.internal.telephony.cdma.SmsMessage.parseSms(SmsMessage.java:552)
12-06 11:38:54.670 E/SMS ( 1433): at com.android.internal.telephony.cdma.CdmaSMSDispatcher.dispatchMessage(CdmaSMSDispatcher.java:121)
12-06 11:38:54.670 E/SMS ( 1433): at com.android.internal.telephony.SMSDispatcher.handleMessage(SMSDispatcher.java:307)
12-06 11:38:54.670 E/SMS ( 1433): at android.os.Handler.dispatchMessage(Handler.java:99)
12-06 11:38:54.670 E/SMS ( 1433): at android.os.Looper.loop(Looper.java:123)
12-06 11:38:54.670 E/SMS ( 1433): at android.app.ActivityThread.main(ActivityThread.java:4627)
12-06 11:38:54.670 E/SMS ( 1433): at java.lang.reflect.Method.invokeNative(Native Method)
12-06 11:38:54.670 E/SMS ( 1433): at java.lang.reflect.Method.invoke(Method.java:521)
12-06 11:38:54.670 E/SMS ( 1433): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:858)
12-06 11:38:54.670 E/SMS ( 1433): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
12-06 11:38:54.670 E/SMS ( 1433): at dalvik.system.NativeStart.main(Native Method)
12-06 11:38:54.680 D/RILJ ( 1433): [0032]> RIL_REQUEST_CDMA_SMS_ACKNOWLEDGE false 96
12-06 11:38:54.690 D/RIL ( 1335): onRequest: CDMA_SMS_ACKNOWLEDGE (88)
12-06 11:38:54.690 D/RILJ ( 1433): [0032]< RIL_REQUEST_CDMA_SMS_ACKNOWLEDGE
12-06 11:38:54.960 D/AT ( 1335): AT< [MSM] Call End, curr_mode 2, call_type 3, end_status 25
DTMF code 0 is not caught in this code:
private static String decodeDtmfSmsAddress(byte[] rawData, int numFields)
throws CodingException
{
/* DTMF 4-bit digit encoding, defined in at
* 3GPP2 C.S005-D, v2.0, table 2.7.1.3.2.4-4 */
StringBuffer strBuf = new StringBuffer(numFields);
for (int i = 0; i < numFields; i++) {
int val = 0x0F & (rawData[i / 2] >>> (4 - ((i % 2) * 4)));
if ((val >= 1) && (val <= 9)) strBuf.append(Integer.toString(val, 10));
else if (val == 10) strBuf.append('0');
else if (val == 11) strBuf.append('*');
else if (val == 12) strBuf.append('#');
else throw new CodingException("invalid SMS address DTMF code (" + val + ")");
}
return strBuf.toString();
}
This must be an issue with the provider. Can I fool this into working somehow by changing the source?
Edit: adding the line:
else if (val == 0) strBuf.append('0');
fixed the issue. Sms now received.
Had to move to GB as I could not get Froyo to compile.
I've never heard of this (on CDMA). What carrier?
He gave the carrier in one of his previous posts, no name canadian carrier. Anyways, we had a similar problem with Sprint, apparently the way some carriers choose to encode their sms messages is inconsistent and thus a Mms.apk modification is needed to support the non-standard encoding. If your carrier has a native android phone, see if you can find a Mms.apk from it, if you can you can replace yours with that one and it should work. If not, you'd really need to wireshark your mms download and analyze the format as opposed to a dump of a working mms, or "step into" the process and watch what happens as it tries to decode it, if you want to make the change in code. It's certainly not easy, luckily for sprint highlandsun was willing to take a look at it for us. It still took us days to get it solved properly.
Based on what rpierce99 has said above and some Googling, I think I have the file you need.
Edit: Didn't read that last part of his log post. Oh well, disregard this unless it has some pertinence to you.
JDog2pt0 said:
Based on what rpierce99 has said above and some Googling, I think I have the file you need.
Edit: Didn't read that last part of his log post. Oh well, disregard this unless it has some pertinence to you.
Click to expand...
Click to collapse
If that's the Mms.apk from a native android device on this local canadian carrier, then it should fix the problem.
rpierce99 said:
If that's the Mms.apk from a native android device on this local canadian carrier, then it should fix the problem.
Click to expand...
Click to collapse
If he wants to use Froyo. He's got it working in GB. Anyways, a Google search pulled up this http://www.droidforums.net/forum/hacking-help/81656-no-incoming-texts-unless-using-zeusdroid.html and after some digging I found a working zeusdroid download where I extracted the mms.apk
Can I say for sure it'll work? No, but based on what I found it should.
JDog2pt0 said:
If he wants to use Froyo. He's got it working in GB. Anyways, a Google search pulled up this http://www.droidforums.net/forum/hacking-help/81656-no-incoming-texts-unless-using-zeusdroid.html and after some digging I found a working zeusdroid download where I extracted the mms.apk
Can I say for sure it'll work? No, but based on what I found it should.
Click to expand...
Click to collapse
Experiencing the same issue on a D2G, also on TBayTel's CDMA network. Tried swapping in Zeusdroid's mms.apk for the stock messaging.apk, to no avail. Any help in solving this would be appreciated... see my D2G thread here: http://forum.xda-developers.com/showthread.php?t=2156261
Thanks in advance!
kanuckdroid said:
Experiencing the same issue on a D2G, also on TBayTel's CDMA network. Tried swapping in Zeusdroid's mms.apk for the stock messaging.apk, to no avail. Any help in solving this would be appreciated... see my D2G thread here: http://forum.xda-developers.com/showthread.php?t=2156261
Thanks in advance!
Click to expand...
Click to collapse
Because asking for help for a device not supported by these forum groups, which we do not have access to, in a thread that is over a year old, which was posted in the wrong group to begin with, on an OS that is a generation behind what is being worked with.... is a brilliant idea. :victory:
Good luck with that:good:
wizardknight said:
Because asking for help for a device not supported by these forum groups, which we do not have access to, in a thread that is over a year old, which was posted in the wrong group to begin with, on an OS that is a generation behind what is being worked with.... is a brilliant idea. :victory:
Good luck with that:good:
Click to expand...
Click to collapse
Gee, Wiz, thanks for the warm welcome!
I'm a self-professed noob. In posting this in a new thread in the right group for the right phone, this thread came up as related. Since it has the same problem and a working solution on the same generation of the same OS, I thought I might post a link. I get that this thread is old and posted in the wrong group. I'm grasping at straws here... it's not a common problem.
Anyway, your point and the attached lashing are taken. Sorry for thinking I might find help here.
kanuckdroid said:
Gee, Wiz, thanks for the warm welcome!
I'm a self-professed noob. In posting this in a new thread in the right group for the right phone, this thread came up as related. Since it has the same problem and a working solution on the same generation of the same OS, I thought I might post a link. I get that this thread is old and posted in the wrong group. I'm grasping at straws here... it's not a common problem.
Anyway, your point and the attached lashing are taken. Sorry for thinking I might find help here.
Click to expand...
Click to collapse
Glad you found the right group.
Related
Hi guys, me again,
i just fixed Navigon Select to work with Gingerbread. It needs the replacement of libmedia because some interfaces got incompatible. Now i can finally use onboard Navigation on my CM7
Download
Just replace the file in /system/lib
cheers
Nice job, i don't use navigon just copilote, but I must congratulated you because you are making hardcore coding for HD2 scene.
Thanks
Cooooooooool !!! THX !!!
Ok, doesn't work for me ... :-/
Sent from my HTC HD2 using XDA App
cheezusweezel said:
Ok, doesn't work for me ... :-/
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Tell me what you get on logcat when Navigon starts up.. Using aLogcat from Market for example. And of course.. Update your Navigon Select to the latest version..
pack21 said:
Nice job, i don't use navigon just copilote, but I must congratulated you because you are making hardcore coding for HD2 scene.
Thanks
Click to expand...
Click to collapse
+1 your out of control, dude. Your an 86, just one more than me and you are making some major breakthroughs.. It makes me think I am really doing nothing with my life, lol.. But yeah, keep up the god work, man
Edit: I meant to say "good" work but swype has no problem also praising you it seems
Sent from my HTC HD2 using XDA App
Cool man, you rock!
Going to try to get Navigon to work following your instructions, now that you already fixed GPS.
[OT]:
Do you by chance also know how to fix camcorder for [email protected]?
I'm playing with PPC_SHIFTPDA_V2 [RAM] which i really like. Camcorder is one of the last issues i would like to fix.
[/OT]
Thanks! But no luck for me either!
gauner1986 said:
Tell me what you get on logcat when Navigon starts up.. Using aLogcat from Market for example. And of course.. Update your Navigon Select to the latest version..
Click to expand...
Click to collapse
Sure, latest version installed and logcat is:
I/ActivityThread( 1773): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 1773): pn: com.navigon.navigator_select
D/NaviApp ( 1773): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 1773): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051cc28
I/System.out( 1773): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 1773): Trying NavinativeD...
I/System.out( 1773): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 1773): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini is up-to-date
I/ActivityManager( 187): Displayed com.navigon.navigator_select/.hmi.CheckExistingRegistrationActivity: +384ms
W/dalvikvm( 1773): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
Awesome, it worked for me even with the old Navigon version. Thanks!
EDIT: nope, sorry. wrong information. it's not working. I guess, my GPS is not working either. Is there a gps test app? The one in market Force Closes when open in gingerbread
Could you guys try again with the file i attached? Maybe i uploaded the wrong one.
gnash.s said:
Awesome, it worked for me even with the old Navigon version. Thanks!
EDIT: nope, sorry. wrong information. it's not working. I guess, my GPS is not working either. Is there a gps test app? The one in market Force Closes when open in gingerbread
Click to expand...
Click to collapse
Use GPS Status from Market.
Nope, also the new file won't work (for me) ...
cheezusweezel said:
Sure, latest version installed and logcat is:
I/ActivityThread( 1773): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 1773): pn: com.navigon.navigator_select
D/NaviApp ( 1773): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 1773): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051cc28
I/System.out( 1773): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 1773): Trying NavinativeD...
I/System.out( 1773): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 1773): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 1773): NaviKernelConf.ini is up-to-date
I/ActivityManager( 187): Displayed com.navigon.navigator_select/.hmi.CheckExistingRegistrationActivity: +384ms
W/dalvikvm( 1773): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
Click to expand...
Click to collapse
So it has to work now.. I checked the .so file, the symbol is definetly present:
Code:
gauners-MacBook-Pro:~ gauner$ strings libmedia.so | grep "_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i"
_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i
_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_ii
Be sure to replace /system/lib/libmedia.so !
cheezusweezel said:
Nope, also the new file won't work (for me) ...
Click to expand...
Click to collapse
Could you check logcat again please?
Anyway.. I'll release a ROM based on CM7 soon.
Could you check logcat again please?
Anyway.. I'll release a ROM based on CM7 soon.
Click to expand...
Click to collapse
New logcat:
I/ActivityThread( 2812): Pub com.navigon.navigator_select.provider.naviprovider: com.navigon.navigator_select.provider.NaviProvider
D/NaviApp ( 2812): pn: com.navigon.navigator_select
D/NaviApp ( 2812): NaviKernel hasn't been started yet, ignore...
D/dalvikvm( 2812): Trying to load lib /data/data/com.navigon.navigator_select/lib/libNavinative.so 0x4051d788
I/System.out( 2812): Cannot load library: reloc_library[1311]: 147 cannot locate '_ZN7android10AudioTrackC2EijiiijPFviPvS1_ES1_i'...
I/System.out( 2812): Trying NavinativeD...
I/System.out( 2812): Couldn't load NavinativeD: findLibrary returned null
D/NaviKernelConnector( 2812): NaviKernelConf.ini pkg_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 2812): NaviKernelConf.ini ins_version = ANDROID_INI_VERSION = 1.5.8
D/NaviKernelConnector( 2812): NaviKernelConf.ini is up-to-date
W/dalvikvm( 2812): threadid=9: thread exiting with uncaught exception (group=0x4001d560)
I/Process ( 2812): Sending signal. PID: 2812 SIG: 9
And your ROM will be much appreciated !!!
gauner1986 said:
Anyway.. I'll release a ROM based on CM7 soon.
Click to expand...
Click to collapse
I read on mdj's thread that alot of ppl are complaining about lag in CM7, would you consider as AOSP release? Thanks soo much!!!
Had a FC when starting Navigon Select before applying the fixed library.
Replaced with your library now NS (&GPS) works without any problem!
Thx again!
Hopefully you guys did not forget to reboot? Otherwise i don't know!
another tip...
if you got a FC while starting Navigon Select, just remove the Navigon and reinstall it again
Should work afterwards.
Sounds like permission issues, check that the new files have the same permissions as others in the same folder.
Just tried this update with Navigon MobileNavigator on a Nexus S with Gingerbread(2.3.1) It's let me get past the spash screen without a FC. Just downloading the maps now. Hope the rest of the app doesn't have any other problems.
Many thanks for this fix.
(I did change the permissions and ownership of libmedia.so with these commands
chown root.root libmedia.so
chmod 644 libmedia.so
)
Rob
EDIT: Confirmed that this is working on my device. Thanks for a great fix.
hi there.
So i've asked a dev related questions here before but didnt get an answer... hoping to get one now!
--i didnt ask it in the DEV related forums because it doesnt seem like the place to ask a question--
and i've also searched for an answer, many times, but havent reached a solution
anyway, ...
I took the Dice_ml.apk from the sensation ROM and put it on my 2.3.3 deodexed (near to)stock-ROM, yet i get a 'Force Close'. i deodexed the dice_ml file and added the classes.dex file to the apk.
I 'logcat'ed and found that its missing a .so file, so i found it in the sensation ROM and copied it to the /system/lib folder, yet i still get the error, this is what it says:
I/ActivityManager( 1343): Start proc com.htc.dice.ml for activity com.htc.dice.m
l/.DiceActivity: pid=2762 uid=10130 gids={}
I/DiceActivity( 2762): onCreate()
I/DiceActivity( 2762): onResume()
D/DiceActivity( 2762): [onResume] mView is Null and postDelay
E/Dice ( 2762): Couldn't load libdice_ml.so!
W/dalvikvm( 1443): disableGcForExternalAlloc: false
D/DiceActivity( 2762): [DiceLib::getInstance] Null State
W/dalvikvm( 2762): No implementation found for native Lcom/htc/dice/ml/DiceLib;.
setResourcePath (Ljava/lang/String; )V
D/AndroidRuntime( 2762): Shutting down VM
W/dalvikvm( 2762): threadid=1: thread exiting with uncaught exception (group=0x4
001d5a0)
E/AndroidRuntime( 2762): FATAL EXCEPTION: main
E/AndroidRuntime( 2762): java.lang.UnsatisfiedLinkError: setResourcePath
E/AndroidRuntime( 2762): at com.htc.dice.ml.DiceLib.setResourcePath(Nativ
e Method)
Click to expand...
Click to collapse
The AndroidRuntime Error still goes on. What could be the problem (im kinda new to this moving from one ROM to the next)
And could i also ask how one changes the Resolution of an apk?
//----------------------------
Also, alot of people have this issue, which is that, after rooting, the headphone mic, and buttons dont work.
i also 'logcat'ed it, and sometimes the buttons send a signal to the OS, sometimes it takes a while for the OS to process the signal (or maybe get it?) and sometimes it doesnt receive it at all!(or maybe its taking to long to send the signal).
Anyway, when it does get a signal, it also says that a certain file is missing, heres the log:
W/KeyCharacterMap( 1443): Can't open keycharmap file
W/KeyCharacterMap( 1443): Error loading keycharmap file '/system/usr/keychars/h2
w_headset.kcm.bin'. hw.keyboards.65540.devname='h2w headset'
I/KeyCharacterMap( 1443): Using default keymap: /system/usr/keychars/qwerty.kcm.
bin
E/BroadcastReceiver( 1713): BroadcastReceiver trying to return result during a n
on-ordered broadcast
E/BroadcastReceiver( 1713): java.lang.RuntimeException: BroadcastReceiver trying
to return result during a non-ordered broadcast
E/BroadcastReceiver( 1713): at android.content.BroadcastReceiver.checkSynchr
onousHint(BroadcastReceiver.java:451)
E/BroadcastReceiver( 1713): at android.content.BroadcastReceiver.abortBroadc
ast(BroadcastReceiver.java:374)
Click to expand...
Click to collapse
and also the BroadcastReceiver Error continues in the log.
So i checked the 1.32 original stock rom(my buttons were working on that ROM before i rooted it), and i didnt find the 'h2w_headset.kcm.bin' file, so i thought maybe its from the 'qwerty.kcm.bin' file, thus i replaced it with the same file from 1.32, (and without restarting the phone) i tested the file and still, had the same problem.
My question for this part is ... Is that error normal? and can it be fixed?
and sorry for all this stuff!!!
Hoping for a reply!
hello guys this is my first fix. I hope it fixes the bluetooth bug on liquidsmooth 2.37 for galaxy ace 2 (http://forum.xda-developers.com/showthread.php?t=2573302)
As @judas1977 said it was from kernel and gives some help and idea how to change it, I tried to make a fix for it. just download and flash it from recovery It worked for my device and I hope it will work for you too =)
here is the link
https://drive.google.com/file/d/0B-8__H0BBJIJRkxYVmZxTXlSM00/edit?usp=sharing
thanks for
@judas1977
@Rox
@shine911
and everyone who helped to developed this awesome rom
development
If i find enough time i will try to update rom with new updates or some fixes
blastos01 said:
If i find enough time i will try to update rom with new updates or some fixes
Click to expand...
Click to collapse
While you're at it, you wouldn't happen to know the bluetooth fix for the GT-S7560?
fix
BT was the biggest for me. I changed the kernel with the latest cm10.2 kernel. So the patch has to change all kernel related issues.
idk
SamsungGalaxySamsung said:
While you're at it, you wouldn't happen to know the bluetooth fix for the GT-S7560?
Click to expand...
Click to collapse
As i dont have your device i dont know what is the problem with BT un your device. i think i need too much time for it.
Sorry for my bad english.
Thanks no problem
Sent from my GT-S7560 using XDA Premium 4 mobile app
wi-fi ?
I guess wi-fi feature has been improved. can any body confirm?
I think my device catches wi-fi signal more effectively after flashing patch
blastos01 said:
As i dont have your device i dont know what is the problem with BT un your device. i think i need too much time for it.
Sorry for my bad english.
Click to expand...
Click to collapse
Here is the logcat for BT on boot:
Code:
E/bt-btif ( 1433): btif_enable_service: current services:0x2000000
E/bt-btif ( 1433): btif_enable_service: current services:0x2000040
E/bt-btif ( 1433): btif_enable_service: current services:0x2040040
E/bt-btif ( 1433): warning : no command pending, ignore ack
E/bt-btif ( 1433): btif_enable_service: current services:0x2140040
E/bt_vendor_qcom( 1433): open(/sys/class/rfkill/rfkill1/type) failed: No such file or directory (2)
E/bt_vendor_qcom( 1433): open() failed: No such file or directory (2)
E/bt_vendor_qcom( 1433): open() failed: No such file or directory (2)
E/bt_h4 ( 1433): [h4] Unknown HCI message type drop this byte 0x0
E/BluetoothAdapterState( 1433): Error enabling Bluetooth
E/BluetoothManagerService( 896): recoverBluetoothServiceFromError
E/BluetoothServiceJni( 1433): Callback env check fail: env: 0x11ca8, callback: 0x62b00
E/BluetoothServiceJni( 1433): Callback: 'adapter_state_change_callback' is not called on the correct thread
Anas Karbila said:
Here is the logcat for BT on boot:
Code:
E/bt-btif ( 1433): btif_enable_service: current services:0x2000000
E/bt-btif ( 1433): btif_enable_service: current services:0x2000040
E/bt-btif ( 1433): btif_enable_service: current services:0x2040040
E/bt-btif ( 1433): warning : no command pending, ignore ack
E/bt-btif ( 1433): btif_enable_service: current services:0x2140040
E/bt_vendor_qcom( 1433): open(/sys/class/rfkill/rfkill1/type) failed: No such file or directory (2)
E/bt_vendor_qcom( 1433): open() failed: No such file or directory (2)
E/bt_vendor_qcom( 1433): open() failed: No such file or directory (2)
E/bt_h4 ( 1433): [h4] Unknown HCI message type drop this byte 0x0
E/BluetoothAdapterState( 1433): Error enabling Bluetooth
E/BluetoothManagerService( 896): recoverBluetoothServiceFromError
E/BluetoothServiceJni( 1433): Callback env check fail: env: 0x11ca8, callback: 0x62b00
E/BluetoothServiceJni( 1433): Callback: 'adapter_state_change_callback' is not called on the correct thread
Click to expand...
Click to collapse
I have exams and too much work with my master thesis. for now I can't tell you when will I try to change the problem or... sorry for these =(
blastos01 said:
I have exams and too much work with my master thesis. for now I can't tell you when will I try to change the problem or... sorry for these =(
Click to expand...
Click to collapse
Alright thanks for reply.
[Q&A] [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Q&A for [SM-T325] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 8.4 LTE (mondrianlte)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
alarm clock
Recently discussed the problem that the included headphones alarm clock rang only from external speakers. Now it rings only from the headphones. But it would be optimal to it when headphones are connected rang simultaneously and external speakers and headphone out. So it is correct and it is so sold on the official firmware.
Sorry for my bad English.
Del
---------- Post added at 03:30 AM ---------- Previous post was at 03:24 AM ----------
Hi, will snapshot m12 for LTE?
Do you just dirty flash the nightlife? I tried going the update route but it doesn't work.
Hi all!
First of all thank you for the Roma and the whole tutorial is perfect on my side on my "tab pro lte"
I would like to know how to overclock the processor above its Standard power?
sorry for the mistakes, I'm French and I use google translation ... oO
thank you!
No mobile data
Thanks to the dev for his continuous efforts on this rom, keep up the good work. However, i noticed that mobile data doesn't work for 2g networks. I've tried using the "preferred network type" and even changing the sim but it still won't work. When i get into 3g or LTE zonse the mobile data begins to work. Please could you suggest a fix. I'm currently limited to 2g so it would be a big help. Thanks
Any hints on building CM12 for this device ? I'm willing to do it if there is any documentation help.
Firmware crude
CM-12 test
Deleted
DensonX said:
Sorry if this is off-topic, but I have seen a lot of people requesting CyanogenMod 12 for this device. I managed to build CM-12 for the mondrianlte, however it does not flash on my device. I get an error saying E: error executing binary in zip. I suspect this may be due to the fact that I have a european Tab Pro, so if anyone with a US Tab Pro LTE wants to try to install it here's a file. https://drive.google.com/file/d/0Bxf2YUR9_3hDX3JUbnJYbWVfTTA/view?usp=sharing
Do NOT forget to backup before attempting to install this, as it likely will not work.
Also if anyone knows how to solve my problem with flashing this please let me know.
Click to expand...
Click to collapse
Please do not post links to other builds in my thread. Especially ones that you can't even flash because it doesn't work for you!
This only adds confusion.
I will try to release something soon. It may have a broken camera (the camera is broken on picassolte and if I can't figure it out I'll have to just leave it broken for both mondrianlte and picassolte for now) but otherwise has been working well for me on picassolte.
SM-T325, CM12 and encryption
Hello,
First Thank you crpalmer for your great work on mondrianlte. I've been using for roughly one month and did not encounter any serious issue, it is working so much better than stock Samsung ROMs ! I only got into problems when trying to encrypt the tablet (with cm-12-20150321-UNOFFICIAL-mondrianlte).
Once the process was started it rebooted very quickly and got stuck on the boot cyanogenmod screen. A forced off/on cycle was able to restore the tablet normal operation, but it had not been encrypted.
Relevant portions of the adb log seem to be :
(just after the beginning of the encrytion process)
Code:
E/Cryptfs ( 243): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
D/Cryptfs ( 243): Just asked init to shut down class main
and later when the tablet reboots :
Code:
D/Cryptfs ( 243): unmounting /data succeeded
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /vendor/firmware/keymaster/keymaster.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
D/QSEECOMAPI: ( 243): QSEECom_get_handle sb_length = 0x2000
D/QSEECOMAPI: ( 243): App is not loaded in QSEE
E/QSEECOMAPI: ( 243): Error::Cannot open the file /firmware/image/keymaste.mdt
E/QSEECOMAPI: ( 243): Error::Loading image failed with ret = -1
E/QCOMKeyMaster( 243): Loading keymaster app failed
E/Cryptfs ( 243): could not open keymaster device in keystore (Operation not permitted)
E/Cryptfs ( 243): Failed to init keymaster
--------- beginning of crash
F/libc ( 243): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x3c in tid 315 (vold)
F/libc ( 243): Unable to open connection to debuggerd: Connection refused
I/Vold (26973): Vold 2.1 (the revenge) firing up
D/Vold (26973): Volume sdcard1 state changing -1 (Initializing) -> 0 (No-Media)
D/Vold (26973): Volume usbdisk state changing -1 (Initializing) -> 0 (No-Media)
I/Cryptfs (26973): Check if PFE is activated on Boot
E/Cryptfs (26973): Bad magic for real block device /dev/block/platform/msm_sdcc.1/by-name/userdata
E/Cryptfs (26973): Error getting crypt footer and key
files /vendor/firmware/keymaster/keymaster.* have permission 644, user/group root, and are symlinks into /firmware/image/. In /firmware/image/, keymaste.* files have permission 440, user system, group drmrpc. Based on the QSEECOMAPI errors above, I am unable to determine whether these access rights are correct. I assume that even if they were, some incorrect SElinux configuration could cause access problems ?
Is anyone able to figure out what is happening ? Is it useful that I post a full log of the process ?
Hi,
I do my own builds of Lineage 14.1 (and CM before) since some years. Taking the standard repositories and repo-picking some of the not yet merged commits. It always worked flawlessly.
Since some days, I get an error when using repopick that seems to be connected with an SSL problem:
Traceback (most recent call last):
File "/home/wolli/cm14.1/vendor/cm/build/tools/repopick.py", line 275, in <module>
reviews = fetch_query(args.gerrit, ' OR '.join('change:{0}'.format(x.split('/')[0]) for x in change_numbers))
File "/home/wolli/cm14.1/vendor/cm/build/tools/repopick.py", line 141, in fetch_query
return fetch_query_via_http(remote_url, query.replace(' ', '+'))
File "/home/wolli/cm14.1/vendor/cm/build/tools/repopick.py", line 122, in fetch_query_via_http
data = requests.get(url)
File "/usr/lib/python2.7/dist-packages/requests/api.py", line 55, in get
return request('get', url, **kwargs)
File "/usr/lib/python2.7/dist-packages/requests/api.py", line 44, in request
return session.request(method=method, url=url, **kwargs)
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 455, in request
resp = self.send(prep, **send_kwargs)
File "/usr/lib/python2.7/dist-packages/requests/sessions.py", line 558, in send
r = adapter.send(request, **kwargs)
File "/usr/lib/python2.7/dist-packages/requests/adapters.py", line 385, in send
raise SSLError(e)
requests.exceptions.SSLError: hostname 'review.lineageos.org' doesn't match 'jira.lineageos.org'
Does anybody else also observe the problem? Is something wrong on my build machine (which made no problems since the last years)?
I would appreciate any help. Thanks!
Best regards,
Klaerchen