Related
Hi, I'm new to this so I hope I'm posting in the right place. I have an HTC Desire running AdamG's Oxygen v1.0.4, but I'd like to put some of the old HTC apps back on the phone, like the music player/widget, news and weather app/widget, etc..
So what I've done so far is extracted the system.img file from my Nandroid backup with unyaffs to get the apk files. I then put the app folder back onto my SD Card and tried to use Root Explorer to copy the apks I wanted back into the system/app folder on my phone, but when I try this, nothing is copied across. I have it in R/W mode and it flashes pasting quickly on the screen but when that disappears, there is no copied app and no less space in the folder.
Is it even possible to install HTC's system apps onto a different version of android? If so, what am I doing wrong? Also, if I do manage to copy the apks into the system/apps folder, do they need the corresponding odex files to work?
Thank you.
I've been trying to do the same thing. I unyaff'd the image, then tried 'adb install HTCAlbum.apk'
This fails with "Failure [INSTALL_FAILED_INSUFFICIENT_STORAGE]"
Googling around says this is to do with it not being signed. However checking this with "jarsigner -verify -verbose -certs HTCAlbum.apk" shows it is signed OK. Have tried re-signing it too, but that made no difference.
logcat output from the install:
Code:
D/AndroidRuntime( 1943): >>>>>> Booting Oxygen by AdamG <<<<<<
D/AndroidRuntime( 1943):
D/AndroidRuntime( 1943): >>>>>> AndroidRuntime START com.android.internal.os.RuntimeInit <<<<<<
D/AndroidRuntime( 1943): CheckJNI is OFF
D/dalvikvm( 1943): creating instr width table
D/AndroidRuntime( 1943): Calling main entry com.android.commands.pm.Pm
D/dalvikvm( 1485): GC_EXPLICIT freed 5K, 54% free 2558K/5511K, external 1625K/2137K, paused 24ms
W/ActivityManager( 147): No content provider found for:
D/dalvikvm( 147): GC_EXPLICIT freed 120K, 44% free 6780K/11911K, external 4453K/5026K, paused 75ms
D/AndroidRuntime( 1943): Shutting down VM
D/dalvikvm( 1943): GC_CONCURRENT freed 212K, 71% free 301K/1024K, external 0K/0K, paused 0ms+0ms
D/jdwp ( 1943): adbd disconnected
There are several different provider apk's but they don't seem to install either...
Posting this in the hope this gives you a pointer and you get further.
Hi guys,
I'm using R22 since a week and i never find particular issues. Now is happening a bad thing...
Suddenly, I have that wifi is not working anymore and frequently phone reboots.
Wifi UI Settings is still on "Turning on.."
- switch button is gray
Hi tried to restore old backup as R21 or TrickDroidV3, but nothing is still changed.
I reflashed Radio, I used and I'm using PD98IMG_12.69.60.29_26.17.14.11_M.zip
I don't know what i have to do to solve this issue, any ideas?:crying:
Thanks for every helps :good:
I changed regional setting on wifi advanced setting with "Europe", now if I try to change it again, it still on the same value... I don't understand
Sent from my Desire HD using xda premium
In the image are figured as wifi setting ui is hang..
Sent from my Desire HD using xda premium
A similar issue when I try to start tethering
Sent from my Desire HD using xda premium
other information:
Sent from my Desire HD using xda premium
lillox said:
Hi guys,
I'm using R22 since a week and i never find particular issues. Now is happening a bad thing...
Suddenly, I have that wifi is not working anymore and frequently phone reboots.
Wifi UI Settings is still on "Turning on.."
- switch button is gray
Hi tried to restore old backup as R21 or TrickDroidV3, but nothing is still changed.
I reflashed Radio, I used and I'm using PD98IMG_12.69.60.29_26.17.14.11_M.zip
I don't know what i have to do to solve this issue, any ideas?:crying:
Thanks for every helps :good:
Click to expand...
Click to collapse
lillox said:
I changed regional setting on wifi advanced setting with "Europe", now if I try to change it again, it still on the same value... I don't understand
Click to expand...
Click to collapse
lillox said:
In the image are figured as wifi setting ui is hang..
Click to expand...
Click to collapse
lillox said:
A similar issue when I try to start tethering
Click to expand...
Click to collapse
1. You might want to consider using the edit button.
2. Just to clarify, I'm assuming that wifi still doesn't work and you still get frequent reboots on both R21 and TrickDroid?
3. Did you change anything on your phone just before it started exhibiting those problems?
4. Just for troubleshooting you could try flashing a rooted stock and see if the problem still exists. Make sure you do a full wipe.
5. Since it's a problem across multiple ROMs it could very well be a hardware problem. Unfortunately, I don't know which hardware problem.
bananagranola said:
1. You might want to consider using the edit button.
Click to expand...
Click to collapse
You have absolutely right!
2. Just to clarify, I'm assuming that wifi still doesn't work and you still get frequent reboots on both R21 and TrickDroid?
Click to expand...
Click to collapse
I have frequent reboots on R22, now i'm trying to restore an old TrickTroid to verify if reboots happens.
3. Did you change anything on your phone just before it started exhibiting those problems?
Click to expand...
Click to collapse
I don't want make a mistake, but the last thing that i did is set the regional setting.
4. Just for troubleshooting you could try flashing a rooted stock and see if the problem still exists. Make sure you do a full wipe.
Click to expand...
Click to collapse
I will do and report everything.
5. Since it's a problem across multiple ROMs it could very well be a hardware problem. Unfortunately, I don't know which hardware problem.
Click to expand...
Click to collapse
I think so, but i don't find a way to list devices(like "lspci" or similar *nix commands) to verify if the wifi module is "switched off" or "died".
Thanks for your answer.:good:
lillox said:
I think so, but i don't find a way to list devices(like "lspci" or similar *nix commands) to verify if the wifi module is "switched off" or "died".
Click to expand...
Click to collapse
3 options:
1. netcfg.
2. Look in your logcat. There's often stuff about wpa_supplicant and other fun stuff there.
3. Dial *#*#INFO#*#*. There's wifi debugging info in there.
bananagranola said:
3 options:
1. netcfg.
2. Look in your logcat. There's often stuff about wpa_supplicant and other fun stuff there.
3. Dial *#*#INFO#*#*. There's wifi debugging info in there.
Click to expand...
Click to collapse
Ok, I did many tries:
1.
3.
Something isn't working...
Now, I have to know something about logcat to create an useful log. I'll looking for information in the forum, I remember that there was something about it in the random blame's thread.
I'll update this thread with other info soon.
Thanks again for your tips.
3. This is my logcat: http://db.tt/aoWeqV94
EDIT: I extracted wifi information:
E/WifiStateMachine( 1657): Failed to disable IPv6: java.lang.IllegalStateException: command '1 interface ipv6 wlan0 disable' failed with '400 1 Failed to change IPv6 state (No such file or directory)'
I/WifiService( 1657): WifiService starting up with Wi-Fi enabled
D/WifiService( 1657): setWifiEnabled: true pid=1657, uid=1000
D/WifiWatchdogStateMachine( 1657): Disabling poor network avoidance for wi-fi only device
I/PowerWidget( 1865): Button list: toggleWifi|toggleMobileData|toggleBluetooth|toggleBrightness|toggleGPS|toggleAirplane|toggleSound|toggleFlashlight
I/PowerWidget( 1865): Button list: toggleWifi|toggleMobileData|toggleBluetooth|toggleBrightness|toggleGPS|toggleAirplane|toggleSound|toggleFlashlight
D/WifiService( 1657): New client listening to asynchronous messages
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '7 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 7 Failed to set address (No such device)'
I/WifiService( 1657): WifiService trying to set country code to it with persist set to true
W/WifiNormalizer( 2112): No specific device detected. Offset set to -7.
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '10 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 10 Failed to set address (No such device)'
E/WifiHW ( 1657): Unable to open connection to supplicant on "wlan0": No such file or directory
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '13 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 13 Failed to set address (No such device)'
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '16 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 16 Failed to set address (No such device)'
E/WifiHW ( 1657): Unable to open connection to supplicant on "wlan0": No such file or directory
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '19 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 19 Failed to set address (No such device)'
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '22 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 22 Failed to set address (No such device)'
E/WifiHW ( 1657): Unable to open connection to supplicant on "wlan0": No such file or directory
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed 6 times to start supplicant, unload driver
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '25 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 25 Failed to set address (No such device)'
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '28 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 28 Failed to set address (No such device)'
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '31 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 31 Failed to set address (No such device)'
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '34 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 34 Failed to set address (No such device)'
E/WifiHW ( 1657): Unable to open connection to supplicant on "wlan0": No such file or directory
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '37 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 37 Failed to set address (No such device)'
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '40 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 40 Failed to set address (No such device)'
I/ActivityManager( 1657): START {act=android.settings.WIFI_SETTINGS cat=[android.intent.category.DEFAULT] flg=0x10000000 cmp=com.android.settings/.Settings$WifiSettingsActivity u=0} from pid 1865
I/ActivityManager( 1657): Start proc com.android.settings for activity com.android.settings/.Settings$WifiSettingsActivity: pid=3600 uid=1000 gids={1015, 3002, 3001, 3003, 1028, 3007}
I/ActivityManager( 1657): Displayed com.android.settings/.Settings$WifiSettingsActivity: +1s485ms
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed 6 times to start supplicant, unload driver
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '43 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 43 Failed to set address (No such device)'
I/WifiService( 1657): WifiService trying to set country code to US with persist set to true
I/WifiService( 1657): WifiService trying to set frequency band to 2 with persist set to true
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '46 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 46 Failed to set address (No such device)'
I/WifiService( 1657): WifiService trying to set country code to GB with persist set to true
I/WifiService( 1657): WifiService trying to set country code to CA with persist set to true
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '49 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 49 Failed to set address (No such device)'
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '52 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 52 Failed to set address (No such device)'
D/WifiService( 1657): setWifiEnabled: false pid=3600, uid=1000
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '55 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 55 Failed to set address (No such device)'
E/WifiHW ( 1657): Unable to open connection to supplicant on "wlan0": No such file or directory
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiHW ( 1657): Supplicant not running, cannot connect
E/WifiStateMachine( 1657): Failed to setup control channel, restart supplicant
E/WifiStateMachine( 1657): Unable to change interface settings: java.lang.IllegalStateException: command '58 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 58 Failed to set address (No such device)'
Click to expand...
Click to collapse
Sent from my Desire HD using xda premium
Ok, I think that it is an hardware fault. I'll try to return back to stock and I will go to assistance
Sent from my Desire HD using xda premium
Verticle lines after screen off
Hie guys, can any one help me am having verticle lines after not using my phone for a while. wen it stays for 5 minites and i unlock the screen there vertical lines and the screen glitches. i ha had this since r19 now on r23 but still happening
Ok, now I'm on stock.
Just for the record I contacted the phone assistance and I received three tips:
1. Unplug the battery for 5 minutes and check if the problem persist
2. Boot in Recovery mode ("stock" recovery) switch on the phone and press vol- until a vibration. Check the problem
3. Factory reset from hboot (this wipe everything on your phone) and check the problem
Nothing has solved my wifi problem, now I have to contact newly the assistance for an assistance center.
PS: sorry for my English...
Sent from my HTC Desire HD A9191 using xda premium
EDIT: 11/15/2012 Wifi Still Not Working, I'll go to assistance.
After going back to stock wifi is now working
I believe that "stock" airplane mode fixed the problem. Yes, it is a strange conclusion.
For now I am enjoying the wifi, but I'll go back to jellytime soon.
I hope that this thread helps someone.
Good luck!
Lillox
Sent from my HTC Desire HD A9191 using xda premium
I followed all the instructions for adb and successfully installed twrp, and the firefirefire bootloader, I then went on to make a backup and flash the smoothrom rom and g apps. Everything was fine except that I noticed when the screen would turn off with the 30-second timer, it wouldn't "suspend" the kindle, but completely turn it off; in addition it sometimes happened when clicking the power button. I also encountered that whilst using the stock wall charger either letting it lock, or using the button the screen would go gray and not suspend, which sometimes followed by turning off completely.
I've done a clean install 5 times, and even installed the CM10 Hellfire rom to see if that one was free from the grasp of this bug, but it also shares the same fate. Does anyone have a solution to this, because I've searched the forum, and the threads themselves and it seems like I'm the only one suffering from this.
In also turns off after 30 minutes of not using it?
Do you know how to get a logcat? Get one and put it in pastebin or something similar, and post a link here. Don't post your entire logcat here.
Also, what is your governor set to?
http://pastebin.com/ihqRfzWz
Bowsa2511 said:
http://pastebin.com/ihqRfzWz
Click to expand...
Click to collapse
That's interesting.
As far as your device is concerned, it goes to sleep and wakes up just fine:
Code:
[B]03-12 21:38:50.643 I/PowerManagerService(378): Going to sleep by user request...[/B]
[COLOR=Gray]03-12 21:38:51.073 D/SurfaceFlinger(107): Screen released, type=0 flinger=0x4164f318[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): GC_CONCURRENT freed 1128K, 24% free 6551K/8540K, paused 5ms+7ms, total 86ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 61ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.198 D/Sensors (378): newState = 2[/COLOR]
[COLOR=Gray]03-12 21:38:51.283 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 I/qtaguid (378): Failed write_ctrl(s 0 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 0) failed with errno -1[/COLOR]
[COLOR=Gray]03-12 21:38:51.401 D/dalvikvm(378): GC_CONCURRENT freed 843K, 21% free 6769K/8540K, paused 7ms+6ms, total 87ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.408 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 56ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.432 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info back home RECENT* clock search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.455 V/TAG (378): bug 7643792: fitSystemWindows([0,25][0,0])[/COLOR]
[COLOR=Gray]03-12 21:38:51.502 D/Sensors (378): newState = 0[/COLOR]
[B]03-12 21:38:51.502 I/PowerManagerService(378): Waking up from sleep...[/B]
[B]03-12 21:38:51.510 D/SurfaceFlinger(107): Screen acquired, type=0 flinger=0x4164f318[/B]
[COLOR=Gray]03-12 21:38:51.510 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): GC_CONCURRENT freed 1154K, 22% free 6734K/8540K, paused 1ms+6ms, total 109ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 95ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 65ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 68ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.713 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 0[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 I/qtaguid (378): Failed write_ctrl(s 1 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 1) failed with errno -1[/COLOR]
[B]03-12 21:38:51.815 I/WindowManager(378): Lock screen displayed![/B]
Do you know what your CPU governor is set to? Also, you say this happens to you on all the ROMs you've tried?...is that correct?
soupmagnet said:
That's interesting.
As far as your device is concerned, it goes to sleep and wakes up just fine:
Code:
[B]03-12 21:38:50.643 I/PowerManagerService(378): Going to sleep by user request...[/B]
[COLOR=Gray]03-12 21:38:51.073 D/SurfaceFlinger(107): Screen released, type=0 flinger=0x4164f318[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): GC_CONCURRENT freed 1128K, 24% free 6551K/8540K, paused 5ms+7ms, total 86ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 61ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.198 D/Sensors (378): newState = 2[/COLOR]
[COLOR=Gray]03-12 21:38:51.283 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 I/qtaguid (378): Failed write_ctrl(s 0 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 0) failed with errno -1[/COLOR]
[COLOR=Gray]03-12 21:38:51.401 D/dalvikvm(378): GC_CONCURRENT freed 843K, 21% free 6769K/8540K, paused 7ms+6ms, total 87ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.408 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 56ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.432 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info back home RECENT* clock search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.455 V/TAG (378): bug 7643792: fitSystemWindows([0,25][0,0])[/COLOR]
[COLOR=Gray]03-12 21:38:51.502 D/Sensors (378): newState = 0[/COLOR]
[B]03-12 21:38:51.502 I/PowerManagerService(378): Waking up from sleep...[/B]
[B]03-12 21:38:51.510 D/SurfaceFlinger(107): Screen acquired, type=0 flinger=0x4164f318[/B]
[COLOR=Gray]03-12 21:38:51.510 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): GC_CONCURRENT freed 1154K, 22% free 6734K/8540K, paused 1ms+6ms, total 109ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 95ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 65ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 68ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.713 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 0[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 I/qtaguid (378): Failed write_ctrl(s 1 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 1) failed with errno -1[/COLOR]
[B]03-12 21:38:51.815 I/WindowManager(378): Lock screen displayed![/B]
Do you know what your CPU governor is set to? Also, you say this happens to you on all the ROMs you've tried?...is that correct?
Click to expand...
Click to collapse
This has happened on all the roms I've tried, the governor is "interactive-cfq", the minimum is 300 and max 1200. The problem doesn't occur when it's plugged in, but occurs when it's not; what I mean by this is that when the 30 second screen-off timer sets off, instead of just locking the device, it turns off completely and I have to boot the kindle once more. Pressing the lock button on the bottom also triggers this and I've tried clicking "fix permissions" in twrp to see if that does anything, but it doesn't.
soupmagnet said:
That's interesting.
As far as your device is concerned, it goes to sleep and wakes up just fine:
Code:
[B]03-12 21:38:50.643 I/PowerManagerService(378): Going to sleep by user request...[/B]
[COLOR=Gray]03-12 21:38:51.073 D/SurfaceFlinger(107): Screen released, type=0 flinger=0x4164f318[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): GC_CONCURRENT freed 1128K, 24% free 6551K/8540K, paused 5ms+7ms, total 86ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.182 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 61ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.198 D/Sensors (378): newState = 2[/COLOR]
[COLOR=Gray]03-12 21:38:51.283 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 I/qtaguid (378): Failed write_ctrl(s 0 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.291 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 0) failed with errno -1[/COLOR]
[COLOR=Gray]03-12 21:38:51.401 D/dalvikvm(378): GC_CONCURRENT freed 843K, 21% free 6769K/8540K, paused 7ms+6ms, total 87ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.408 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 56ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.432 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info back home RECENT* clock search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.455 V/TAG (378): bug 7643792: fitSystemWindows([0,25][0,0])[/COLOR]
[COLOR=Gray]03-12 21:38:51.502 D/Sensors (378): newState = 0[/COLOR]
[B]03-12 21:38:51.502 I/PowerManagerService(378): Waking up from sleep...[/B]
[B]03-12 21:38:51.510 D/SurfaceFlinger(107): Screen acquired, type=0 flinger=0x4164f318[/B]
[COLOR=Gray]03-12 21:38:51.510 D/PhoneStatusBar(458): disable: < expand icons alerts ticker system_info BACK* HOME* RECENT CLOCK* search >[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): GC_CONCURRENT freed 1154K, 22% free 6734K/8540K, paused 1ms+6ms, total 109ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 95ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 65ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.698 D/dalvikvm(378): WAIT_FOR_CONCURRENT_GC blocked 68ms[/COLOR]
[COLOR=Gray]03-12 21:38:51.713 E/wpa_supplicant(533): Unsupported command: SETSUSPENDMODE 0[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 I/qtaguid (378): Failed write_ctrl(s 1 10062) res=-1 errno=1[/COLOR]
[COLOR=Gray]03-12 21:38:51.721 W/NetworkManagementSocketTagger(378): setKernelCountSet(10062, 1) failed with errno -1[/COLOR]
[B]03-12 21:38:51.815 I/WindowManager(378): Lock screen displayed![/B]
Do you know what your CPU governor is set to? Also, you say this happens to you on all the ROMs you've tried?...is that correct?
Click to expand...
Click to collapse
Also ... when exactly did you grab this logcat?
I would also try this: when your device entered the "sleep of death", meaning pressing the power button doesn't do anything, try to connect it to your computer and see if adb still works (probably not, but i'd try it). If it does grab a logcat and /proc/kmsg or dmesg.
If adb doesn't see the device then get a last_kmsg right after you reboot:
adb shell "cat /proc/last_kmsg" > last_kmsg.txt
What gapps do you have installed? You said you didn't install any other apps, right? Did you make any changes to the performance settings (governor, io scheduler ...)?
Bowsa2511 said:
This has happened on all the roms I've tried, the governor is "interactive-cfq", the minimum is 300 and max 1200. The problem doesn't occur when it's plugged in, but occurs when it's not; what I mean by this is that when the 30 second screen-off timer sets off, instead of just locking the device, it turns off completely and I have to boot the kindle once more. Pressing the lock button on the bottom also triggers this and I've tried clicking "fix permissions" in twrp to see if that does anything, but it doesn't.
Click to expand...
Click to collapse
From what I see your device isn't completely shutting down...only going into a Sleep of Death. If the device doesn't display the same type of behavior while plugged in, try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
If, after running that script the device stops displaying the same symptoms, then it's probably just a hardware issue and you may need to boost you governor a bit...something like 600/1200
twa_priv said:
Also ... when exactly did you grab this logcat?
I would also try this: when your device entered the "sleep of death", meaning pressing the power button doesn't do anything, try to connect it to your computer and see if adb still works (probably not, but i'd try it). If it does grab a logcat and /proc/kmsg or dmesg.
If adb doesn't see the device then get a last_kmsg right after you reboot:
adb shell "cat /proc/last_kmsg" > last_kmsg.txt
What gapps do you have installed? You said you didn't install any other apps, right? Did you make any changes to the performance settings (governor, io scheduler ...)?
Click to expand...
Click to collapse
The computer doesn't even detect the kindle via adb, or any types of mounting anymore; I only followed the instructions, wiped what needed to be wiped, installed the rom, then gapps and rebooted. Even in it's pristine state it still suffers from the problem.
soupmagnet said:
From what I see your device isn't completely shutting down...only going into a Sleep of Death. If the device doesn't display the same type of behavior while plugged in, try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
If, after running that script the device stops displaying the same symptoms, then it's probably just a hardware issue and you may need to boost you governor a bit...something like 600/1200
Click to expand...
Click to collapse
I've also tried doing that with SetCPU to see if it was the slowness of 300mhz causing the SoD, but the same symptoms occured
Edit: I'm going to download today's build, with the latest g apps then do the following:
•1. Wipe factory reset.
•2. Wipe cache.
•3. Wipe dalvik.
•4. Wipe system.
•5. Flash Rom zip.
•6. Flash gapps zip.
•7. Select reboot, then system if prompted.
Doing that would technically be doing everything in the pristine manner (Unless I have to change a frequency or governor?)
Just in case you missed it...
soupmagnet said:
...try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
Click to expand...
Click to collapse
soupmagnet said:
From what I see your device isn't completely shutting down...only going into a Sleep of Death. If the device doesn't display the same type of behavior while plugged in, try the following to get a logcat while unplugged:
http://forum.xda-developers.com/showthread.php?t=2044930
If, after running that script the device stops displaying the same symptoms, then it's probably just a hardware issue and you may need to boost you governor a bit...something like 600/1200
Click to expand...
Click to collapse
soupmagnet said:
Just in case you missed it...
Click to expand...
Click to collapse
Here's the log
twa_priv said:
Also ... when exactly did you grab this logcat?
I would also try this: when your device entered the "sleep of death", meaning pressing the power button doesn't do anything, try to connect it to your computer and see if adb still works (probably not, but i'd try it). If it does grab a logcat and /proc/kmsg or dmesg.
If adb doesn't see the device then get a last_kmsg right after you reboot:
adb shell "cat /proc/last_kmsg" > last_kmsg.txt
What gapps do you have installed? You said you didn't install any other apps, right? Did you make any changes to the performance settings (governor, io scheduler ...)?
Click to expand...
Click to collapse
Did you grab a last_kmsg ? Get it right after reboot after you had to do a hard shutdown because of a SOD.
Don't know if you've done/tried that - but I would also revert completely back to the stock OS and see if the same issues occurs as there as well.
twa_priv said:
Did you grab a last_kmsg ? Get it right after reboot after you had to do a hard shutdown because of a SOD.
Don't know if you've done/tried that - but I would also revert completely back to the stock OS and see if the same issues occurs as there as well.
Click to expand...
Click to collapse
I occasionally get a sleep of death as well. I have had it happen with the CyanogenMod Nightly dated cm-10.1-20130311-NIGHTLY-otter.zip. It did not happen when my kindle was running the stock rom. I'm still working to get fully up to speed on how to chase this sort of thing, and all of you guys posting helpful info is appreciated.
twa_priv said:
Did you grab a last_kmsg ? Get it right after reboot after you had to do a hard shutdown because of a SOD.
Don't know if you've done/tried that - but I would also revert completely back to the stock OS and see if the same issues occurs as there as well.
Click to expand...
Click to collapse
I flashed the stock rom, and the modaco gr9 rom and the problem doesn't persist on either, i'm going to flash CM10 once more and do that
Interestingly enough, this 4.1 build doesn't have the sleep of death, wonder what the difference is
http://goo.im/devs/loosethisskin/otter-cm10/cm-10-20121211-1416-otter-sgt7.zip
Interesting, I may try that one if bumping up the governor to 600 does not solve the problem.
Sent from my Amazon Kindle Fire using XDA Premium HD app
muiriddin said:
Interesting, I may try that one if bumping up the governor to 600 does not solve the problem.
Sent from my Amazon Kindle Fire using XDA Premium HD app
Click to expand...
Click to collapse
Yeah i tried everything from trying out kindle roms, 4 different roms , gapps, permission fixing, dreamscape settings; inactivity settings, governors and clock frequencies, they all have the same problem. That test build i posted has been running perfectly all day now! No bugs with or without charger and no sleep of death! Its 4.1.2, but that is worth not having an unusable kindle
Don't forget to flash the CM10 (4.1) gapps
After one and a half days of testing I have not gotten a SOD with twa_priv's rom from this forum here:
http://forum.xda-developers.com/showthread.php?t=2051331
To be specific, I'm using 20130323-2135-otter-sgt7.zip with gapps-jb-20130301-signed.zip
This is running 4.2.2 instead of 4.1.2. If I do get one I will probably start running soupkits logcat script to chase the issue further.
Okay this morning before work the device appears to be in a SOD. Hopefully I have time to look at it tonight when I get home. It did go for around four days before this happened.
This one was different from the past my battery was down to 0% even though it was on a charger?
I managed to get it recharged only by plugging it into a computer for a while.
Sent from my KFTT using Tapatalk HD
I have a phone Sony Xperia S LT26i (Android version 4.1.2, Build number 6.2.B.0.211). I do not know the history of this phone. It has problems with WiFi. When I want to connect WiFi (Setting-> Wireless & networks -> Turn on WiFi), I get a message Wi-Fi Error. It can not turn on WiFi. When I check the MAC-address WiFi (Setting-> About phone -> Status -> WiFi MAC-address) I always see it Unavailable. I check the file /data/ets/wifi/fw and I can see that there is written MAC-address 30:39:26:0B:C8:73. When I check MAC-address Bluetooth, I can see 90:C1:15:FC:6E:18. I know that usually MAC-address Bluetooth is slightly less, than the MAC-address WiFi, but numbers are relatives and similar. But I see that in my phone, they differ greatly!
Probably the problem with WiFi is what the hardware MAC-address Wi-fi and MAC-address WiFi in the file /data/ets/wifi/fw differ?
Help me please restore operability of WiFi.
Help me please...:crying:
porcelana said:
Help me please...:crying:
Click to expand...
Click to collapse
Try reset to factory settings.
AlinTheron said:
Try reset to factory settings.
Click to expand...
Click to collapse
I've done it already several times. It doesn't solve a problem.
There are still ideas?
porcelana said:
I've done it already several times. It doesn't solve a problem.
There are still ideas?
Click to expand...
Click to collapse
Click Here -> TRY THIS
Error log of Dalvik Debug Monitor
AlinTheron said:
Click Here -> TRY THIS
Click to expand...
Click to collapse
When I start Dalvik Debug Monitor in Android SDK, I see the error log (at phone start), with reports about WiFi. This is shown below, but it is not complete logs, and only a few selected lines:
Code:
Log Startup (error)
01-12 15:03:54.409: E/EventHub(369): could not get driver version for /dev/input/mice, Not a typewriter
01-12 15:03:54.759: E/CommandListener(150): Failed to open /proc/sys/net/ipv6/conf/wlan0/disable_ipv6: No such file or directory
01-12 15:03:54.759: E/WifiStateMachine(369): Failed to disable IPv6: java.lang.IllegalStateException: command '1 interface ipv6 wlan0 disable' failed with '400 1 Failed to change IPv6 state (No such file or directory)'
01-12 15:03:54.779: E/MobileDataStateTracker(369): default: Ignoring feature request because could not acquire PhoneService
01-12 15:03:54.779: E/MobileDataStateTracker(369): default: Could not enable APN type "default"
01-12 15:03:54.789: E/WifiHW(150): Failed to open wlan fw path param (No such file or directory)
01-12 15:03:54.789: E/SoftapController(150): Softap fwReload - failed: -1
01-12 15:03:54.789: E/WifiStateMachine(369): Failed to reload STA firmware java.lang.IllegalStateException: command '2 softap fwreload wlan0 STA' failed with '400 2 Softap operation failed (No such file or directory)'
01-12 15:03:54.799: E/WifiStateMachine(369): Unable to change interface settings: java.lang.IllegalStateException: command '4 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 4 Failed to set address (No such device)'
01-12 15:03:54.839: E/wpa_supplicant(585): Could not read interface wlan0 flags: No such device
01-12 15:03:54.889: E/AudioHardwareMSM8660(156): unknown stream
01-12 15:03:54.939: E/wpa_supplicant(585): Could not read interface wlan0 flags: No such device
01-12 15:03:55.419: E/SQLiteLog(369): (5) statement aborts at 1: [PRAGMA journal_mode=TRUNCATE;]
01-12 15:03:55.449: E/wpa_supplicant(585): Could not read interface wlan0 flags: No such device
01-12 15:03:55.549: E/wpa_supplicant(585): Could not read interface wlan0 flags: No such device
01-12 15:03:55.559: E/Trace(610): error opening trace file: No such file or directory (2)
01-12 15:03:55.649: E/wpa_supplicant(585): Could not read interface wlan0 flags: No such device
01-12 15:03:55.859: E/wpa_supplicant(585): nl80211: Could not set interface 'wlan0' UP
01-12 15:03:55.859: E/wpa_supplicant(585): wlan0: Failed to initialize driver interface
01-12 15:03:56.189: E/Trace(664): error opening trace file: No such file or directory (2)
01-12 15:03:57.629: E/SocketMonitor(735): The socket server maybe not started.
01-12 15:03:57.629: E/SocketMonitor(735): Error in SocketMonitor.
01-12 15:04:05.919: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:04:05.959: E/(156): [ACDB RTC]->rtc init done!->result [0]
01-12 15:04:05.959: E/Diag_Lib(156): actp_diag_init: call diag init function with 418A0959
01-12 15:04:05.959: E/(156): [ACDB ACPH]->actp diag init done!
01-12 15:04:05.959: E/ACDB-LOADER(156): Error reading MBHC general config returned = fffffff3
01-12 15:04:06.929: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:04:09.929: E/WifiStateMachine(369): Failed to setup control channel, restart supplicant
01-12 15:04:12.629: E/SocketMonitor(735): The socket server maybe not started.
01-12 15:04:12.629: E/SocketMonitor(735): Error in SocketMonitor.
01-12 15:04:12.839: E/Trace(2073): error opening trace file: No such file or directory (2)
01-12 15:04:13.189: E/MM_OSAL(156): ValidateAACFile failed
01-12 15:04:13.249: E/Trace(2131): error opening trace file: No such file or directory (2)
01-12 15:04:14.779: E/MM_OSAL(156): ValidateAACFile failed
01-12 15:04:14.799: E/Trace(2250): error opening trace file: No such file or directory (2)
01-12 15:04:14.939: E/WifiHW(150): Failed to open wlan fw path param (No such file or directory)
01-12 15:04:14.939: E/SoftapController(150): Softap fwReload - failed: -1
01-12 15:04:14.939: E/WifiStateMachine(369): Failed to reload STA firmware java.lang.IllegalStateException: command '8 softap fwreload wlan0 STA' failed with '400 8 Softap operation failed (No such file or directory)'
01-12 15:04:14.949: E/WifiStateMachine(369): Unable to change interface settings: java.lang.IllegalStateException: command '10 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 10 Failed to set address (No such device)'
01-12 15:04:14.959: E/WifiHW(369): Unable to open connection to supplicant on "wlan0": No such file or directory
01-12 15:04:14.979: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.019: E/Trace(2299): error opening trace file: No such file or directory (2)
01-12 15:04:15.079: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.159: E/Trace(2319): error opening trace file: No such file or directory (2)
01-12 15:04:15.189: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.189: E/(2262): vnd.android.cursor.dir/event
01-12 15:04:15.289: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.309: E/ThermalDaemon(1152): Fusion modem thermal mitigation not available.
01-12 15:04:15.309: E/ThermalDaemon(1152): Sensor setup:[tsens_tz_sensor0]
01-12 15:04:15.389: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.399: E/Trace(2348): error opening trace file: No such file or directory (2)
01-12 15:04:15.499: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.569: E/Trace(2379): error opening trace file: No such file or directory (2)
01-12 15:04:15.609: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.849: E/Trace(2400): error opening trace file: No such file or directory (2)
01-12 15:04:15.919: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:15.989: E/Trace(2421): error opening trace file: No such file or directory (2)
01-12 15:04:16.019: E/wpa_supplicant(2295): Could not read interface wlan0 flags: No such device
01-12 15:04:16.019: E/wpa_supplicant(2295): nl80211: Could not set interface 'wlan0' UP
01-12 15:04:16.019: E/wpa_supplicant(2295): wlan0: Failed to initialize driver interface
01-12 15:04:16.069: E/Trace(2438): error opening trace file: No such file or directory (2)
01-12 15:04:17.239: E/MM_OSAL(156): ValidateAACFile failed
01-12 15:04:17.319: E/Trace(2509): error opening trace file: No such file or directory (2)
01-12 15:04:17.509: E/Trace(2523): error opening trace file: No such file or directory (2)
01-12 15:04:17.629: E/ThermalDaemon(1152): Thermald Server: accept[fd=31]
01-12 15:04:17.629: E/ThermalDaemon(1152): Thermald Server: write success [data=600][0x58 0x02]
01-12 15:04:17.639: E/Trace(2543): error opening trace file: No such file or directory (2)
01-12 15:04:17.819: E/SQLiteLog(2523): (5) statement aborts at 1: [PRAGMA journal_mode=TRUNCATE;]
01-12 15:04:18.119: E/Trace(2606): error opening trace file: No such file or directory (2)
01-12 15:04:26.969: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:04:29.779: E/Trace(2847): error opening trace file: No such file or directory (2)
01-12 15:04:29.969: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:04:29.969: E/WifiStateMachine(369): Failed to setup control channel, restart supplicant
01-12 15:04:34.979: E/WifiHW(150): Failed to open wlan fw path param (No such file or directory)
01-12 15:04:34.979: E/SoftapController(150): Softap fwReload - failed: -1
01-12 15:04:34.989: E/WifiStateMachine(369): Failed to reload STA firmware java.lang.IllegalStateException: command '11 softap fwreload wlan0 STA' failed with '400 11 Softap operation failed (No such file or directory)'
01-12 15:04:35.089: E/WifiStateMachine(369): Unable to change interface settings: java.lang.IllegalStateException: command '13 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 13 Failed to set address (No such device)'
01-12 15:04:35.159: E/wpa_supplicant(2894): Could not read interface wlan0 flags: No such device
01-12 15:04:36.169: E/wpa_supplicant(2894): nl80211: Could not set interface 'wlan0' UP
01-12 15:04:36.169: E/wpa_supplicant(2894): wlan0: Failed to initialize driver interface
01-12 15:04:46.109: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:04:50.110: E/WifiStateMachine(369): Failed to setup control channel, restart supplicant
01-12 15:04:55.120: E/WifiHW(150): Failed to open wlan fw path param (No such file or directory)
01-12 15:04:55.120: E/SoftapController(150): Softap fwReload - failed: -1
01-12 15:04:55.130: E/WifiStateMachine(369): Failed to reload STA firmware java.lang.IllegalStateException: command '14 softap fwreload wlan0 STA' failed with '400 14 Softap operation failed (No such file or directory)'
01-12 15:04:55.150: E/WifiStateMachine(369): Unable to change interface settings: java.lang.IllegalStateException: command '16 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 16 Failed to set address (No such device)'
01-12 15:04:55.160: E/WifiHW(369): Unable to open connection to supplicant on "wlan0": No such file or directory
01-12 15:04:55.189: E/wpa_supplicant(2948): Could not read interface wlan0 flags: No such device
01-12 15:04:56.189: E/wpa_supplicant(2948): nl80211: Could not set interface 'wlan0' UP
01-12 15:04:56.189: E/wpa_supplicant(2948): wlan0: Failed to initialize driver interface
01-12 15:05:07.179: E/WifiHW(369): Supplicant not running, cannot connect
01-12 15:05:10.180: E/WifiStateMachine(369): Failed to setup control channel, restart supplicant
Run logcat:
E/WifiHW ( 369): Unable to open connection to supplicant on "wlan0": No such file or directory
I/wpa_supplicant( 3043): rfkill: Cannot open RFKILL control device
E/wpa_supplicant( 3043): Could not read interface wlan0 flags: No such device
E/wpa_supplicant( 3043): nl80211: Could not set interface 'wlan0' UP
E/wpa_supplicant( 3043): wlan0: Failed to initialize driver interface
E/WifiHW ( 369): Supplicant not running, cannot connect
D/StateMachine( 369): handleMessage: E msg.what=147458
D/StateMachine( 369): processMsg: SupplicantStartingState
D/WifiStateMachine( 369): SupplicantStartingState{ what=147458 when=-3ms }
E/WifiStateMachine( 369): Failed 6 times to start supplicant, unload driver
..
porcelana said:
[/CODE]
Click to expand...
Click to collapse
Read THIS TUTORIAL Maybe you can fix it.
AlinTheron said:
Read THIS TUTORIAL Maybe you can fix it.
Click to expand...
Click to collapse
Thank you, but is not work for my case
This works fine on my other phone SAMSUNG S2. But my main phone is other. This is the Sony Xperia S model number is LT26i. Code * # * # 526 # * # * does not work for him. I think that for Sony Xperia S other code is necessary. Somebody knows the correct code for Sony Xperia S? My WiFi is not turning on. When i dial *#*#526#*#* there is no message. I stopped on a Step 1. Please help me.
porcelana said:
Thank you, but is not work for my case
My phone name is Sony Xperia S, model number is LT26i. My WiFi is not turning on. When i dial *#*#526#*#* there is no message. I stopped on a Step 1. Please help me.
Click to expand...
Click to collapse
Do you have JellyBean .211 ? WIFI is one of the many bugs in this ROM, you'll have to wait for an update.
---------- Post added at 08:42 PM ---------- Previous post was at 08:38 PM ----------
Try this, leave it on Airplane mode for 5 minutes, if that doesn't work, remove the sim card for 10 minutes and then insert it back in. Try you're WIFI after those tweaks.
---------- Post added at 08:53 PM ---------- Previous post was at 08:42 PM ----------
Or, repair your phone with Pc Companion. Back up first, because it will erase everything.
AlinTheron said:
Do you have JellyBean .211 ? WIFI is one of the many bugs in this ROM, you'll have to wait for an update.
---------- Post added at 08:42 PM ---------- Previous post was at 08:38 PM ----------
Try this, leave it on Airplane mode for 5 minutes, if that doesn't work, remove the sim card for 10 minutes and then insert it back in. Try you're WIFI after those tweaks.
---------- Post added at 08:53 PM ---------- Previous post was at 08:42 PM ----------
Or, repair your phone with Pc Companion. Back up first, because it will erase everything.
Click to expand...
Click to collapse
Yes i have now JellyBean .211. But before I had version 2.73 and WIFI is not working on it. Then I updated to JB .211 by PC Companion . So this is an old problem. Now I'm waiting for help to solve it.
porcelana said:
Yes i have now JellyBean .211. But before I had version 2.73 and WIFI is not working on it. Then I updated to JB .211 by PC Companion . So this is an old problem. Now I'm waiting for help to solve it.
Click to expand...
Click to collapse
Do a repair with Pc Companion or SUS
AlinTheron said:
Do a repair with Pc Companion or SUS
Click to expand...
Click to collapse
I have PC Companion version 2.10.165 and I do not see her features Repair.
I do not have the SUS. I will search and install it and do the repair, then come back here again.
Thank you for your help.
porcelana said:
I have PC Companion version 2.10.165 and I do not see her features Repair.
I do not have the SUS. I will search and install it and do the repair, then come back here again.
Thank you for your help.
Click to expand...
Click to collapse
Ok, try to press UPDATE on Pc Companion and even if it says that you have the latest software installed it will give you the option to repair your phone. Or press Support Zone.
AlinTheron said:
Ok, try to press UPDATE on Pc Companion and even if it says that you have the latest software installed it will give you the option to repair your phone. Or press Support Zone.
Click to expand...
Click to collapse
I did this and PC Companion tells me that I have the last Update, and no others. Repair function is not available.
porcelana said:
I did this and PC Companion tells me that I have the last Update, and no others. Repair function is not available.
Click to expand...
Click to collapse
READ THIS
Worst case scenario : Hardware problem.
AlinTheron said:
READ THIS
Click to expand...
Click to collapse
I took all steps from this manual, but WiFi wasn't restored. Any ideas? .
AlinTheron said:
Worst case scenario : Hardware problem.
Click to expand...
Click to collapse
In the error log (in the message #6) reports that there is a problem with the driver and with wlan0. I want to check that all configuration files for WiFi and MAC are available in phone. Somebody can tell me what configuration files for WiFi and MAC have SXS? It is possible that in my SXS missing necessary files.
Definitely a hardware problem.
Hey,
i got the same issue as mention here --> https://forum.xda-developers.com/galaxy-tab-s/help/wifi-bluetooth-t3725452
i checked /efs/wifi/.mac.info which contains the right MAC. Anyway i was not able to activate WiFi or BT. There are a lot file inside the efs folder so i dont think the partition is corrupted.
I got lineage-microg flashed, but i also tried lineage build 07.09.2019 with same result.
Any suggestions how to fix this issue?
I reflashed original Firmware, which shows the correct MAC under Systemstatus, but i cannot enable WiFi or BT anyways ...
Could someone be nice and check which file are in your /efs folder? Maybe i'm missing some ...
mine is:
/efs/
/efs/lost+found
/efs/drm
/efs/drm/sdrm
/efs/drm/sdrm/data_agent
/efs/drm/playready
/efs/drm/playready/00003.PRV
/efs/.files
/efs/.files/.dx1
/efs/.files/.dm33
/efs/.files/.mp301
/efs/wifi
/efs/wifi/.mac.info
/efs/wifi/.mac.cob
/efs/bluetooth
/efs/bluetooth/bt_addr
/efs/prov
/efs/prov/ffffffff00000000000000000000000c.tlbin
/efs/prov/libdevkm.lock
/efs/imei
/efs/imei/mps_code.dat
/efs/FactoryApp
/efs/FactoryApp/hist_nv
/efs/FactoryApp/fdata
/efs/FactoryApp/test_nv
/efs/FactoryApp/earjack_count
/efs/FactoryApp/factorymode
/efs/FactoryApp/keystr
/efs/FactoryApp/serial_no
/efs/FactoryApp/hw_ver
/efs/FactoryApp/prepay
/efs/FactoryApp/baro_delta
/efs/FactoryApp/asoc
/efs/FactoryApp/batt_cable_count
/efs/FactoryApp/max_temp
/efs/FactoryApp/batt_discharge_level
/efs/FactoryApp/max_current
/efs/FactoryApp/control_no
/efs/ss_data
/efs/nv.log
/efs/nv_data.bin
/efs/.nv_state
/efs/.nv_core.bak
/efs/.nv_core.bak.md5
/efs/.nv_data.bak
/efs/.nv_data.bak.md5
/efs/gyro_calibration_data
/efs/nv_data.bin.md5
/efs/00000000.authtokcont
/efs/grip_cal_data
/efs/prov_data
/efs/prov_data/dev_root
/efs/prov_data/dev_root/dev_root.dat
/efs/prov_data/dev_root/sym_key.dat
/efs/prov_data/knox
/efs/prov_data/knox/knox.dat
/efs/prov_data/ccm
/efs/prov_data/ccm/ccm.dat
/efs/sec_efs
/efs/sec_efs/ucm_ca_cert
/efs/wv.keys
/efs/h2k.dat
/efs/mc
/efs/cpk
/efs/TEE
/efs/SMS
/efs/pfw_data
/efs/Battery
/efs/Battery/batt_capacity_max
/efs/recovery
/efs/recovery/postrecovery
/efs/umc
/efs/umc/BulkEnrollmentProfile
/efs/edk_p_sd
logact gives me:
09-13 13:29:27.920 2795 7794 E WifiMonitor: startMonitoring(wlan0) failed!
09-13 13:29:32.935 2315 2956 W CommandListener: Failed to retrieve HW addr for wlan0 (No such device)
09-13 13:29:32.935 2795 7794 E WifiStateMachine: Unable to change interface settings: java.lang.IllegalStateException: command '54 interface setcfg wlan0 0.0.0.0 0 down' failed with '400 54 Failed to set address (No such device)'
09-13 13:29:32.940 2795 7794 E wifi : Could not read interface wlan0 flags: 19
09-13 13:29:32.945 2795 7794 D WifiMonitor: startMonitoring(wlan0) with mConnected = false
09-13 13:29:33.310 15395 15395 I wpa_supplicant: set_csc_config : ifname(wlan0), certi_flags(0x0), autoconnect_flags(0x0), opbranding_flags(0x0), boolean_flags(0x20008), vendorssid_list()
09-13 13:29:33.495 15395 15395 E wpa_supplicant: Could not read interface wlan0 flags: No such device
09-13 13:29:33.495 15395 15395 I wpa_supplicant: nl80211: deinit ifname=wlan0 disabled_11b_rates=0
09-13 13:29:33.495 15395 15395 E wpa_supplicant: Could not read interface wlan0 flags: No such device
09-13 13:29:33.495 15395 15395 E wpa_supplicant: wlan0: Failed to initialize driver interface
and yes, thats true. There is no WiFi device unde /dev. Where is it gone?
You need to post more info on what caused this?
ashyx said:
You need to post more info on what caused this?
Click to expand...
Click to collapse
What info do you need?
I got the device from a friend because it refuses to charge. Because of this fault he put it inside a locker in his Bathroom for about a year.
I got it charging by holding down power and volume down for 30 seconds, plug in charger while holding down these buttons and hold it for again 30 seconds. After that it started to charge.
After first boot WiFi turned on but toogled of randomly. By toogling on BT it got better but not much. After i flashed lineage MAC was shown as 02:00:00:00:00 and WiFi wont turn on. So i reverted to Stock ROM. Here MAC was shown correctly but WiFi wont turn on. Same for BT. This is the current state.
Because my friend stored the device in his Bathroom (why people do sh*t like this???) i think maybe some steam found its way inside the device and maybe under/inside the Chip. But i want to be sure before i'll try to replace it.