I don't have 10 posts yet, so I did this thread here.
Edit: these should be fixed on later builds
For this rom, I got gsm working when I changed Settings > More... (networks) > Mobile networks > Network Preferences > GSM/WCDMA (auto mode and manually selected network. But can't get data working (APN missing and can't add it manually) and phone thinks that I am roaming mode.
At least calls work.
Baseband should be right http://kuvaton.com/k/Y95r.png ?
I tried "auto" and "GSM only" but unfortunaly without any effect (Germany). Reboot didn't help either in both cases.
---------- Post added at 02:14 AM ---------- Previous post was at 02:07 AM ----------
I noticed another strange thing: When i press the power button for the reboot menu, in the menu "Aeroplane mode" is constantly switching on and off. Does anyone have that, too?
Sometimes when i want to change the settings the phone becomes really, really slow and stutters, sometimes something called "com.android.phone" is crashing. If I close it, the phone has normal speed again.
Sushi3110 said:
I tried "auto" and "GSM only" but unfortunaly without any effect (Germany). Reboot didn't help either in both cases.
---------- Post added at 02:14 AM ---------- Previous post was at 02:07 AM ----------
I noticed another strange thing: When i press the power button for the reboot menu, in the menu "Aeroplane mode" is constantly switching on and off. Does anyone have that, too?
Sometimes when i want to change the settings the phone becomes really, really slow and stutters, sometimes something called "com.android.phone" is crashing. If I close it, the phone has normal speed again.
Click to expand...
Click to collapse
The same to me.
I also experienced some random "reboots". Without Motorola Logo, it's as if just the CM reboots itself. I wasn't doing anything at that time, the phone was on the table.
I don't have 10 posts either and I feel so bad being a noob, but:
With tezet's CM10 USB tethering isn't working for me. Here's the logcat output after activating usb tethering:
Code:
D/MotUsbService( 2652): onReceive(), received intent:com.android.internal.usb.request_reconfigure
D/MotUsbService( 2652): Got reconfiguration request (functions rndis permanent false adb true)
D/MotUsbService( 2652): handleUsbEvent(), Received event: 7, current state: 1
D/UsbSettings( 2652): USB mode (UI) : 5
I/ ( 2137): opprofdaemon: OPPROF_DAEMON_translate_message(): Enter
I/ ( 2137): opprofdaemon: handle_bp_message(): Enter
I/ ( 2137): opprofdaemon: handle_log_all_ind(): Enter
I/ ( 2137): opprofdaemon: OPPROF_TRANSPORT_P.cc: handle_log_all_ind(): line=522: BP log all event=4
I/ ( 2137):
I/ ( 2137): opprofdaemon: OPPROF_DAEMON_handle_generic_events(): Enter
I/ ( 2137): opprofdaemon: OPPROF_DAEMON_handle_generic_events(): Exit
I/ ( 2137): opprofdaemon: OPPROF_TRANSPORT_P.cc: handle_log_all_ind(): line=568: OPPROF TL: log_all
I/ ( 2137): opprofdaemon: handle_log_all_ind(): Exit
I/ ( 2137): opprofdaemon: handle_bp_message(): Exit
I/ ( 2137): opprofdaemon: OPPROF_DAEMON_translate_message(): Exit
I/ ( 2137): opprofdaemon: OPPROF_DAEMON_translate_message(): Enter
I/ ( 2137): opprofdaemon: handle_bp_message(): Enter
I/ ( 2137): opprofdaemon: handle_log_all_ind(): Enter
I/ ( 2137): opprofdaemon: OPPROF_TRANSPORT_P.cc: handle_log_all_ind(): line=522: BP log all event=4
I/ ( 2137):
I/ ( 2137): opprofdaemon: OPPROF_DAEMON_handle_generic_events(): Enter
I/ ( 2137): opprofdaemon: OPPROF_DAEMON_handle_generic_events(): Exit
I/ ( 2137): opprofdaemon: OPPROF_TRANSPORT_P.cc: handle_log_all_ind(): line=568: OPPROF TL: log_all
I/ ( 2137): opprofdaemon: handle_log_all_ind(): Exit
I/ ( 2137): opprofdaemon: handle_bp_message(): Exit
I/ ( 2137): opprofdaemon: OPPROF_DAEMON_translate_message(): Exit
what about GPS, is it working?
mondkrater said:
what about GPS, is it working?
Click to expand...
Click to collapse
Everything works fine for me try changing your apn to your carriers Google it.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
okay, thanks! gonna try it
mondkrater said:
okay, thanks! gonna try it
Click to expand...
Click to collapse
Make sure you flash gapps with it so you don't kose your stock important apps.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
are led notification working on this rom? if have how to enable it.
I tried to post there too, but I don't have 10 posts...
I didn't tested the mobile data yet, but it seems to be working.
The only thing that I noticed is a little bug on the Wi-Fi. Sometimes, when the screen locks, the WiFi seems to be connected but don't load any page, then I have to reboot the device. I tried to reconnect to the router, but it didn't work.
Does anybody have the same bug?
The USB mass storage cant been used neither.
Finovsk said:
I tried to post there too, but I don't have 10 posts...
I didn't tested the mobile data yet, but it seems to be working.
The only thing that I noticed is a little bug on the Wi-Fi. Sometimes, when the screen locks, the WiFi seems to be connected but don't load any page, then I have to reboot the device. I tried to reconnect to the router, but it didn't work.
Does anybody have the same bug?
Click to expand...
Click to collapse
i don't have this prob, some time when go out WIFI era, re enable and it wiil ok.
simendavid said:
The USB mass storage cant been used neither.
Click to expand...
Click to collapse
Same here, using the latest GB Kernel Release. No notification or any other reaction when i plugin in USB.
Isn't there somekind fixed sbf for GB kernel? I installed this CM10 from stock 2.2.2 and can't get now CM9 back.
If you mean the SBF wich allows Froyo and GB Kernels to boot (aka downgrade), yes: http://forum.xda-developers.com/showpost.php?p=22532058&postcount=1
I can not send messages
I text the message them when i will send the message I receive a error.
Works fine here. Are you sure you have used the right ROM? I had the wrong combination wich caused many problems.
You should only upgrade the right kernel versions. If you have a GB CM or Stock use the GB CM10, if Froyo, use Froyo CM10 or reflash to you likings
I used the GB version on GB kernel.
PatrickDziura said:
I used the GB version on GB kernel.
Click to expand...
Click to collapse
Hm, strange. Just wrote a message just to verify, worked again without problems, checked if it arrived. too.
Related
I have rooted my phone and done all the fixes I can find, when enabling 4g it just indicates that its "scanning" I ran a few different fixes and cannot seem to find a good method to get 4g back. I did manage to capture this from logcat
D/ ( 84): WiMAX SDIO is ready, iface_name=wimax0
D/ ( 84): to configure wimax0 up
D/ ( 84): <jni> com_htc_net_wimax_StartDaemon
D/ ( 84): uid: 1000 -1
D/ ( 84): gid: 1000 -1
D/wimax ( 975): <sequansd> argv[0]=/system/bin/sequansd
D/wimax ( 975): <sequansd> argv[1]=/etc/wimax/sequansd/sequansd_app.xml
D/wimax ( 975): <sequansd> pid=976
D/wimax ( 975): <sequansd> pid_value=976
I/Wimax ( 84): <DC> Start DC.
I/Wimax ( 84): <DC> Try to establish a connection to DC server.
E/Wimax ( 84): <DC CONNECT> IO error: msg='/127.0.0.1:7771 - Connection refu
sed'
D/ ( 976): <sequansd> Waiting for connect...
I/Wimax ( 84): <DC> Try to establish a connection to DC server.
I/Wimax ( 84): <DC> Connected to DC server.
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=MsFatalError id=-2147221497
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=MsReady id=-2147221496
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=MsDetached id=-2147221495
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=MsLoading id=-2147221494
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=NeighborBsListChanged id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=SfCidUpdated id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=HandoverSucceeded id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=HandoverCanceled id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=HandoverStarted id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=Log id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=PowerCtlModeChanged id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=SsState id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=autodetectExitCriteriaMet id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=autodetectEntryCriteriaMet id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=scanBsFoundExtBand id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=scanBsFoundExt id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=scanBsFound id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=scanRoundCompleted id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=ndsStateChange id=-1
I/Wimax ( 84): <DCP DEBUG> Ntf push: name=MsDetected id=-2147221475
E/Wimax ( 84): <DCP> Bad return status 0xffffffff
D/BluetoothHandsfree( 177): cdmaDbmEcioToSignal(cdmaDbm:-85, cdmaEcio:-40)
D/BluetoothHandsfree( 177): cdmaDbmEcioToSignal(evdoEcio:-60, evdoSnr:1)
V/AlarmManager( 84): Alarm triggering: Alarm{4683c090 type 2 com.google.androi
d.apps.gtalkservice}
Trying to figure this out myself..
I ran back through the Simple Root process and 4G came back for me.
Simple root fails to work for me :-/
Me too. I think mine started happening after full nand rooting. Went back to stock by extracting the rom.zip out of the HTC OTA1 RUU and updating via recovery. just tried to go back to the original non-nand root with no dice either.
Hmmph.
Update..
So, I was able to get mine back by using SimpleRoot to do a full nand unlock (merely rooting it didn't fix it), then flashing my favorite custom rom AND upgrading the radio.
I'm wondering if this means I can't go back to completely stock without breaking 4G (since that may have been what caused it to break in the first place)..
edit: sure enough, running the OTA1 RUU broke my 4G again.
edit 2: and re-unlocking NAND fixed it again
4g comes and goes for me now, reception is quite bad after rooting and NAND unlocking, i will be flashing back to the default ROM and just waiting till this can be resolved.
Simple Root process or pretty much any root process for that matter does little to nothing to affect the radio as you should have the same radio on the phone after rooting as you would have if you flashed stock.
That said, if you think problems showed up after rooting I would recommend flashing a custom ROM. Most have the 4G fix already running which would take care of most problems. If you still have issues after that, flash the radio ROM, but only flash radio if you need it according to your ROM or if your problems do not seem to go away.
But I suspect flashing a custom ROM will help.
Hey guys,
I've had a notification issue on both 2.1 and 2.2.
The Issue, specifically: I go into Handcent SMS, select an SMS thread, go to change a person's notification tone, Open up System Notifications list-- when I select a notification tone, tone does not play, handcent crashes.
After that point, even if I go into change the default android sounds (in android settings), anytime that system ringtone/notification dialog window comes up, and I select a tone, it crashes (sometimes crashes phone with a chain of FCs).
Any time I wipe and reflash, it works fine for a short period of time (days).
Thinking it might be corrupted audio files, I've tried dropping a .nomedia file on my sdcard/media/ folder to isolate the /system rings, but no conclusive differences.
Another thing I noticed in the logs was references to DRM. I HAVE removed the 2 DRM apks from 2.2, if relevant (and had the 3 removed in 2.1)
It happened last night again, and I captured a log. I can identify where in the log it happens, but don't have much experience in debugging. The log is capturing exactly the process I explained in the beginning (repeated a few times). Can anyone help me get to the bottom of this? (or know any resources to troubleshoot with these logs?) I'm not looking to solve this--- more looking to understand it
Seemingly relevant portion of the log attached.
Here's a snippet too:
Code:
[SIZE="3"]V/WindowManager( 2381): Dsptch 1 x342.0 y153.0 > Window{48762a90 android/com.android.internal.app.RingtonePickerActivity paused=false}
E/RingtoneManager( 7705): getRingtone : content://media/internal/audio/media/86, streamType : 5
I/MediaPlayer( 7705): uri is:content://media/internal/audio/media/86
I/MediaPlayer( 7705): inside getAudioFilePath: content://media/internal/audio/media/86
I/MediaPlayer( 7705): The actual path is:/system/media/audio/notifications/Color.mp3
I/MediaPlayer( 7705): path is: /system/media/audio/notifications/Color.mp3
I/MediaPlayer( 7705): file path found for DRM file:path is: /system/media/audio/notifications/Color.mp3
I/Ringtone( 7705): openMediaPlayer() mUri: content://media/internal/audio/media/86
I/Ringtone( 7705): inside getAudioFilePath: content://media/internal/audio/media/86
I/Ringtone( 7705): The actual path is:/system/media/audio/notifications/Color.mp3
I/Ringtone( 7705): openMediaPlayer() isMidFile: false
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:CreatePlugIn() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:PVMFCPMKmjPlugInPLAYREADY() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:ThreadLogon() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:Init() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:QueueCommandL() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:Run() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:ProcessCommand() In CmdID:: 13
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:DoInit() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:CommandComplete() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:QueryInterface() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:QueueCommandL() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:Run() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:ProcessCommand() In CmdID:: 1
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:DoQueryInterface() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:queryInterface() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:CommandComplete() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:QueryInterface() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:QueueCommandL() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:Run() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:ProcessCommand() In CmdID:: 1
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:DoQueryInterface() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:queryInterface() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:CommandComplete() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:QueryInterface() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:QueueCommandL() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:Run() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:ProcessCommand() In CmdID:: 1
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:DoQueryInterface() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:queryInterface() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:CommandComplete() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:AuthenticateUser() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:QueueCommandL() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:Run() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:ProcessCommand() In CmdID:: 15
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:DoAuthenticate() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:CommandComplete() In
E/ ( 2301): PVMFCPMKmjPlugInPLAYREADY:SetSourceInitializationData in
E/ ( 2301): We use Normal Url Sent
E/ ( 2301): PlayReady_Engine_Check_FileType IN
E/ ( 2301): DRM_ASFVerify_Context_Initialize IN
E/ ( 2301): DRM file Name input: /system/media/audio/notifications/Color.mp3
E/ ( 2301): Trying to oepn [/system/media/audio/notifications/Color.mp3]
E/ ( 2301): , fullname: [/]
E/ ( 2301): Error in fopen(), = Unknown error: 0. for filename: /system/media/audio/notifications/Color.mp3
E/ ( 2301): Trying to oepn [/system/media/audio/notifications/Color.mp3]
E/ ( 2301): , fullname: [/]
E/ ( 2301): DRM_E_FILEREADERROR
E/ ( 2301): DRMTOOLS_OpenASF_File( inFileName, &((*in_oToolContext)->oMediaFile ))
E/ ( 2301):
E/ ( 2301): Call to DRMTOOLS_OpenASF_File Failed dr[0x8004c01a]
E/ ( 2301): DRM_ASFVerify_Context_Initialize OUT
E/ ( 2301): PlayReady_Engine_Check_FileType Failed dr = [0x1]
E/ ( 2301): DRM_ASFVerify_Context_Uninitialize IN
E/ ( 2301): *unin_oToolContext is null
E/ ( 2301): DRM_ASFVerify_Context_Uninitialize OUT
E/ ( 2301): File is not a DRM File
D/ ( 2301): After GetDurationFromNazcaScan: clipDuration=1593
D/ ( 2301): After GetDurationFromNazcaScan: clipDuration=1593
D/ ( 2301): After GetDurationFromNazcaScan: clipDuration=1593
D/ ( 2301): After GetDurationFromNazcaScan: clipDuration=1593
D/ ( 2301): After GetDurationFromNazcaScan: clipDuration=1593 [/SIZE]
Was my post too long? Someone's gotta know bump
..........
Ok.. I figured it out (this is the lonliest thread on the interweb)..
So, the issue was with the 2 drm apks that i have removed every time I've flashed a rom. I puled copies of them out of the latest quantum 1.2 rom and pushed them to my system/app/ , fixed permissions, restarted, and now, I can freely change my notification and ringtones without my device locking up or crashing. Joy.
What id like to know is, does the drm check all media files? Or is there drm inside the ogg, mp3 or wma tone or tones that I currently have? Or, is there something else I can get rid of that makes running the drm a requirement?
Since I reloaded the drm apks, everything sees to work fine, even if I kill the drm process, but that leads me to believe its still running somewhere. If anyone knows anything about this.. I'll start doing my research too.
Echo
Hey, I have the same problem. Can you explain in further detail how you solved it. Where can I get the .apk that you said you placed into /system/app/ ? I am running this on a Samsung Galaxy Tab.
I am writing an app, and all that I want to do is play some video files. The app works on every other android device that I have used, except this one. Any help is appreciated.
Neil
Pretty sure Deca is talking about drmprovider.apk. and drmUa.apk. They're like the main Drm apks on our epics if not the only.
nmonday said:
Hey, I have the same problem. Can you explain in further detail how you solved it. Where can I get the .apk that you said you placed into /system/app/ ? I am running this on a Samsung Galaxy Tab.
I am writing an app, and all that I want to do is play some video files. The app works on every other android device that I have used, except this one. Any help is appreciated.
Neil
Click to expand...
Click to collapse
I don't know what else to do.
Here's what i tried so far:
Flashed custom kernel
Flashed other rom (CM10.2)
Cleared Dalvik cache
Cleared cache partition
Flashed other modem
Reseted flash counter
Flashed back stock rom (4.2.2)
Upgraded to 4.3 (ota)
The problem remains.
Anything i forgot to try?
Any sugestions?
Thanks!
I think the only way to fix this would be to flash a complete official firmware package via Odin.
Sent from my GT-I9505 using Tapatalk
MegaMike604 said:
I think the only way to fix this would be to flash a complete official firmware package via Odin.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
I did that, no luck.
Try multiple times, boot directly to download mode, not from the rom and make sure to use the firmware that the custom ROM is based on. If that fails you may have a hardware issue, not sure what else to try.
Sent from my GT-I9505 using Tapatalk
What do you mean by "can't activate wifi" ?
planetf1 said:
What do you mean by "can't activate wifi" ?
Click to expand...
Click to collapse
I mean that i activate and it deactivate.
arleybarros said:
I mean that i activate and it deactivate.
Click to expand...
Click to collapse
Try using custom kernel and then flash mga wifi lte fix. Take out the battery and then use Odin.
Sent from my GT-I9505 using Tapatalk
MemoryController said:
Try using custom kernel and then flash mga wifi lte fix. Take out the battery and then use Odin.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Ty, but no luck yet.
Logcat says:
Code:
E/WifiHW ( 2016): Cannot open "/data/.cid.info": No such file or directory
D/WifiService( 2016): setWifiEnabled: true pid=2237, uid=10040
E/WifiHW ( 2016): ==========[WIFI] Station firmware load ===========
E/WifiStateMachine( 2016): Failed to load driver!
E/WifiStateMachine( 2016): DriverFailedState
Have you tried flashing a fix for your current modem? worked for me with Odin 3.04
I9505XXUEMJ7 was my modem (nordic countries)
http://d-h.st/users/DjeMBeY/?fld_id=16262
tried to flash all the "wifi fixers" available in this forum, and keep getting this errors on adb:
Code:
I/WifiManager( 1421): setWifiEnabled : true
I/WifiService( 879): setWifiEnabled: true pid=1421, uid=10141
E/WifiHW ( 879): ##################### set firmware type 0 #####################
E/WifiHW ( 879): Cannot open "/data/.cid.info": No such file or directory
E/WifiHW ( 879): ==========[WIFI] Station firmware load ===========
D/SSRMv2:Monitor( 879): SIOP:: AP = 400 (read only)
E/WifiHW ( 879): return of insmod : ret = -1, No such device
E/WifiStateMachine( 879): Failed to load driver
D/WfdService( 879): intent recieved android.net.wifi.WIFI_STATE_CHANGED
D/STATUSBAR-NetworkController( 1421): onReceive() - RSSI_CHANGED_ACTION, WIFI_STATE, NETWORK_STATE
D/STATUSBAR-NetworkController( 1421): Nothing, mRoamingIconId = 0
I/elm ( 2716): MainReceiver.onReceive() : android.net.wifi.WIFI_STATE_CHANGED
E/WifiStateMachine( 879): sendErrorBroadcast code:10
E/WifiController( 879): Wi-Fi driver is unstable. Received CMD_STATEMACHINE_RESET
I/elm ( 2716): MainReceiver.onReceive() END - - - - - : android.net.wifi.WIFI_STATE_CHANGED
D/elm ( 2716): ELMEngine.getInstance().
I/DownloadNowBroadcastReceiver( 3770): onReceive
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.TMNetworkReceiver() Enter 1 main
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.StartTMHandler - enter
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.StartTMHandler - exit
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Enter
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Action android.net.wifi.WIFI_STATE_CHANGED
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() UnHandled
D/TMSERVER/TMNetworkReceiver( 3738): TMNetworkReceiver.onReceive() Exit
D/MTPRx ( 4799): DRIVER_TIME_OUT 60s lapsed
current
Tried this?
http://www.alliance-rom.com/communi...-non-hlos-bin-temporary-flashing-method.8676/
After countless hours of frustration with all the steps you have tried, this finally solved my problem.
Geggan said:
Tried this?
http://www.alliance-rom.com/communi...-non-hlos-bin-temporary-flashing-method.8676/
After countless hours of frustration with all the steps you have tried, this finally solved my problem.
Click to expand...
Click to collapse
just tried, no luck.
Any luck on this? I've had a dead device for a while I would like to be able to connect to WiFi!
MegaMike604 said:
I think the only way to fix this would be to flash a complete official firmware package via Odin.
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Where can I get the complete offical firmware package?
nalitox said:
Where can I get the complete offical firmware package?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/
arleybarros said:
just tried, no luck.
Click to expand...
Click to collapse
The WIFI "Trick" in .zip form. Just flash it via Recovery to make your 4.3 work: HERE
Hi currently im building omnirom for GT-I9205,
Im having some issue with the bluetooth,
i can confirm the bluetooth will work in this device (work on CM11 base source).
here is my logcat, hoping someone will point me to correct direction
Code:
D/BluetoothManagerService( 914): BluetoothServiceConnection: com.android.bluetooth.btservice.AdapterService
D/BluetoothManagerService( 914): Message: 40
D/BluetoothManagerService( 914): MESSAGE_BLUETOOTH_SERVICE_CONNECTED: 1
---
D/BluetoothPanServiceJni( 1650): initializeNative(L110): pan
D/BluetoothTethering( 914): got CMD_CHANNEL_HALF_CONNECTED
E/BluetoothTethering( 914): Trying to set mAsyncChannel twice!
---
I/bluedroid( 1650): enable
I/bt_hci_bdroid( 1650): init
I/bt_vendor( 1650): bt-vendor : init
I/bt_hwcfg( 1650): Starting hciattach daemon
I/bt_hwcfg( 1650): try to set false
I/bt_hwcfg( 1650): Starting hciattach daemon
I/bt_hwcfg( 1650): try to set true
I/bt_hci_bdroid( 1650): bt_hc_worker_thread started
I/qcom-bluetooth( 3318): /system/etc/init.qcom.bt.sh: init.qcom.bt.sh config =
I/qcom-bluetooth( 3324): /system/etc/init.qcom.bt.sh: Transport : smd
I/qcom-bluetooth( 3325): /system/etc/init.qcom.bt.sh: ** Bluedroid stack **
I/qcom-bluetooth( 3332): /system/etc/init.qcom.bt.sh: Power Class: Ignored. Default(1) used (1-CLASS1/2-CLASS2/3-CUSTOM)
I/qcom-bluetooth( 3333): /system/etc/init.qcom.bt.sh: Power Class: To override, Before turning BT ON; setprop qcom.bt.dev_power_class <1 or 2 or 3>
I/qcom-bluetooth( 3334): /system/etc/init.qcom.bt.sh: LE Power Class: Ignored. Default(2) used (1-CLASS1/2-CLASS2/3-CUSTOM)
I/qcom-bluetooth( 3335): /system/etc/init.qcom.bt.sh: LE Power Class: To override, Before turning BT ON; setprop qcom.bt.le_dev_pwr_class <1 or 2 or 3>
I/qcom-bluetooth( 3340): /system/etc/init.qcom.bt.sh: Bluetooth QSoC firmware download succeeded,
I/qcom-bluetooth( 3341): /system/etc/init.qcom.bt.sh: ** Bluedroid stack **
I/bt_hwcfg( 1650): bluetooth satus is on
I/bt_userial_vendor( 1650): Done intiailizing UART
I/bt_userial_vendor( 1650): Done intiailizing UART
E/bt_userial( 1650): userial_open: wrong numbers of open fd in vendor lib [2]!
E/bt_userial( 1650): userial_open: HCI UART expects only one open fd
I/bt_vendor( 1650): Bluetooth Firmware and smd is initialized
I/GKI_LINUX( 1650): gki_task_entry: gki_task_entry task_id=0 [BTU] starting
I/bt-btu ( 1650): btu_task pending for preload complete event
I/bt-btu ( 1650): btu_task received preload complete event
I/ ( 1650): BTE_InitTraceLevels -- TRC_HCI
I/ ( 1650): BTE_InitTraceLevels -- TRC_L2CAP
I/ ( 1650): BTE_InitTraceLevels -- TRC_RFCOMM
I/ ( 1650): BTE_InitTraceLevels -- TRC_AVDT
I/ ( 1650): BTE_InitTraceLevels -- TRC_AVRC
I/ ( 1650): BTE_InitTraceLevels -- TRC_A2D
I/ ( 1650): BTE_InitTraceLevels -- TRC_BNEP
I/ ( 1650): BTE_InitTraceLevels -- TRC_BTM
I/ ( 1650): BTE_InitTraceLevels -- TRC_GAP
I/ ( 1650): BTE_InitTraceLevels -- TRC_PAN
I/ ( 1650): BTE_InitTraceLevels -- TRC_SDP
I/ ( 1650): BTE_InitTraceLevels -- TRC_GATT
I/ ( 1650): BTE_InitTraceLevels -- TRC_SMP
I/ ( 1650): BTE_InitTraceLevels -- TRC_BTAPP
I/ ( 1650): BTE_InitTraceLevels -- TRC_BTIF
W/qdhwcomposer( 215): Excessive delay reading vsync: took 3945 ms vsync_period 33 ms
D/BluetoothAdapterState( 1650): CURRENT_STATE=PENDING, MESSAGE = ENABLE_TIMEOUT, isTurningOn=true, isTurningOff=false
E/BluetoothAdapterState( 1650): Error enabling Bluetooth
i think the problem is most likely due to >> userial_open: wrong numbers of open fd in vendor lib [2]!
what exactly is "fd"?
I've been reading a lot over the web to find information about this issue I'm having, but by no means I could solve this issue.
I just got my S5. Here's a (very short) excerpt of the
Code:
adb shell dumpstate
command:
Code:
[ril.product_code]: [SM-G900MZWPZTO]
[ro.product.model]: [SM-G900M]
When I got the phone, the first thing I did, as it was used, was to factory-reset it, because I didn't want any data from the previous user. I did this through the phone UI, not from within recovery (wipe cache/wipe data).
Once reset was done, I put in my microSIM and turned it back on. I had no way to test wifi and bluetooth at that point, so I used the mobile network to update my personal info, etc.
By the end of the day, I got home and tried to turn on wireless. The normal behavior of the indicator when turning wifi on is GRAY->DARK GREEN->GREEN, but the phone goes GRAY->DARK GREEN and doesn't go further. It stays in DARK GREEN for a couple minutes, then it goes back to GRAY.
The same happens to bluetooth. The only difference is that bluetooth takes less time to go back to GRAY.
The Android version installed was 4.2.2.
There was an offer to update Android, so I thought that could solve the problem, so I updated Android to 5.0 over mobile network (no wifi, remember?).
After the update, wifi still didn't work. By dialing *#1234#, I noticed this:
Code:
AP: G900MUBU1BOC4
CP: G900MUBU1BOC3
CSC: G900MZTO1BOC4
AP and CP are different. Shouldn't they be equal?
Anyway, after seeing the update didn't solve the problem, I did a downgrade, again with no success. The *#1234# now shows this:
Code:
AP: G900MUBU1ANCE
CP: G900MUBU1ANCE
CSC: G900MZTO1ANCE
Wifi still don't go on.
I also tried to flash two Android 5.0 (Lollipop) versions available to my country (got them from sammobile dot com):
Code:
/firmwares/download/45787/G900MUBU1BOC4_G900MZTO1BOC4_ZTO/
Code:
/firmwares/download/44412/G900MUBU1BOC1_G900MZTO1BOC1_ZTO/
None worked.
I used ODIN for all updates. Some background on how to use ODIN can be found here:
www dot droidforums dot net threads guide-complete-samsung-odin-v3-xx-options-and-reference.278159
While inspecting the phone's dumpstate, I found this:
Code:
01-01 10:56:42.519 732 967 E WifiHW : ##################### set firmware type 0 #####################
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_fw_path(): fwpath = /system/etc/wifi/bcmdhd_sta.bin
01-01 10:56:42.519 252 914 E WifiHW : Cannot open "/data/.cid.info": No such file or directory
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_nvram_path() = /system/etc/wifi/nvram_net.txt
01-01 10:56:42.519 252 914 E WifiHW : TEMP_FAILURE_RETRY complete
.
.
.
01-01 10:56:42.529 732 967 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '16
01-01 10:56:42.529 732 967 E WifiHW : supplicant_name : p2p_supplicant
01-01 10:56:42.529 732 967 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
The following also appears from time to time along the log:
Code:
01-01 10:56:53.549 732 967 E WifiHW : Supplicant not running, cannot connect
I read a lot about wifi connections dropping, but none about not being able to turn on wifi on Samsung Galaxy S5. Got to some similar threads on S4 and previous versions, but none about S5, so I decided to post here.
Some questions arises:
1. Am I the only one having this issue?
2. Can it be hardware-related? And if yes, is there any way to check this?
3. Could the Factory Reset have done something nasty to wifi config files? I read some suggestions to erase wpa_supplicant config files.
4. When flashing a new rom, is any data kept inside the phone or everything is erased?
5. Is there a way to reset the wifi only or updating its firmware?
Thanks for helping!
There could be 3 causes for this...
1. Kernel WIFI modules doesn't match the kernel.
2. Hardware problem
3. Not sure about this since I'm just new to samsung but it could also be from a corrupt EFS partition.
But to further troubleshoot this problem can you do this for me?
1. Install terminal emulator from playstore.
2. execute this command from there
Code:
svc wifi enable
See if it shows some errors, warnings or whatever text it will print.
if not type logcat and paste here the last 100 to 150 lines of the output.
htimsxela said:
I've been reading a lot over the web to find information about this issue I'm having, but by no means I could solve this issue.
I just got my S5. Here's a (very short) excerpt of the
Code:
adb shell dumpstate
command:
Code:
[ril.product_code]: [SM-G900MZWPZTO]
[ro.product.model]: [SM-G900M]
When I got the phone, the first thing I did, as it was used, was to factory-reset it, because I didn't want any data from the previous user. I did this through the phone UI, not from within recovery (wipe cache/wipe data).
Once reset was done, I put in my microSIM and turned it back on. I had no way to test wifi and bluetooth at that point, so I used the mobile network to update my personal info, etc.
By the end of the day, I got home and tried to turn on wireless. The normal behavior of the indicator when turning wifi on is GRAY->DARK GREEN->GREEN, but the phone goes GRAY->DARK GREEN and doesn't go further. It stays in DARK GREEN for a couple minutes, then it goes back to GRAY.
The same happens to bluetooth. The only difference is that bluetooth takes less time to go back to GRAY.
The Android version installed was 4.2.2.
There was an offer to update Android, so I thought that could solve the problem, so I updated Android to 5.0 over mobile network (no wifi, remember?).
After the update, wifi still didn't work. By dialing *#1234#, I noticed this:
Code:
AP: G900MUBU1BOC4
CP: G900MUBU1BOC3
CSC: G900MZTO1BOC4
AP and CP are different. Shouldn't they be equal?
Anyway, after seeing the update didn't solve the problem, I did a downgrade, again with no success. The *#1234# now shows this:
Code:
AP: G900MUBU1ANCE
CP: G900MUBU1ANCE
CSC: G900MZTO1ANCE
Wifi still don't go on.
I also tried to flash two Android 5.0 (Lollipop) versions available to my country (got them from sammobile dot com):
Code:
/firmwares/download/45787/G900MUBU1BOC4_G900MZTO1BOC4_ZTO/
Code:
/firmwares/download/44412/G900MUBU1BOC1_G900MZTO1BOC1_ZTO/
None worked.
I used ODIN for all updates. Some background on how to use ODIN can be found here:
www dot droidforums dot net threads guide-complete-samsung-odin-v3-xx-options-and-reference.278159
While inspecting the phone's dumpstate, I found this:
Code:
01-01 10:56:42.519 732 967 E WifiHW : ##################### set firmware type 0 #####################
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_fw_path(): fwpath = /system/etc/wifi/bcmdhd_sta.bin
01-01 10:56:42.519 252 914 E WifiHW : Cannot open "/data/.cid.info": No such file or directory
01-01 10:56:42.519 252 914 I WifiHW : wifi_change_nvram_path() = /system/etc/wifi/nvram_net.txt
01-01 10:56:42.519 252 914 E WifiHW : TEMP_FAILURE_RETRY complete
.
.
.
01-01 10:56:42.529 732 967 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '16
01-01 10:56:42.529 732 967 E WifiHW : supplicant_name : p2p_supplicant
01-01 10:56:42.529 732 967 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
The following also appears from time to time along the log:
Code:
01-01 10:56:53.549 732 967 E WifiHW : Supplicant not running, cannot connect
I read a lot about wifi connections dropping, but none about not being able to turn on wifi on Samsung Galaxy S5. Got to some similar threads on S4 and previous versions, but none about S5, so I decided to post here.
Some questions arises:
1. Am I the only one having this issue?
2. Can it be hardware-related? And if yes, is there any way to check this?
3. Could the Factory Reset have done something nasty to wifi config files? I read some suggestions to erase wpa_supplicant config files.
4. When flashing a new rom, is any data kept inside the phone or everything is erased?
5. Is there a way to reset the wifi only or updating its firmware?
Thanks for helping!
Click to expand...
Click to collapse
I believe, (Don't quote me on this), if the EFS partition was corrupted or lost, the phone would not have any radio functionality including voice and text etc
Also I 'think' the IMEI is also included on that partition, so *#06# should come up blank if it was the EFS partition causing the problem
But again, this is just what I've also picked up in the short time I've been with my S5 so could be missing something
[Solved], but the hard way
I took the device to Samsung and they said there was a problem on the main board (?), so they replaced it for a new one. I don't think I'm going to complain about it. Although I think that could be fixed somehow, replacing was probably easier. I said "the hard way" on the title, meaning it was a "brute force" fix. It is a pity I wasn't able to keep the old board for experimentation...
Thanks for your replies, guys. I didn't even expect replies and got yours and so complete! Thanks a lot!