I/Netd (14447): Netd 1.0 starting
I//system/bin/iptables(14447): Flushing chain `INPUT'
I//system/bin/iptables(14447): Flushing chain `OUTPUT'
I//system/bin/iptables(14447): Flushing chain `FORWARD'
I//system/bin/iptables(14447): Flushing chain `PREROUTING'
I//system/bin/iptables(14447): Flushing chain `OUTPUT'
I//system/bin/iptables(14447): Flushing chain `POSTROUTING'
I/Netd (14468): Netd 1.0 starting
I//system/bin/iptables(14468): Flushing chain `INPUT'
I//system/bin/iptables(14468): Flushing chain `OUTPUT'
I//system/bin/iptables(14468): Flushing chain `FORWARD'
I//system/bin/iptables(14468): Flushing chain `PREROUTING'
I//system/bin/iptables(14468): Flushing chain `OUTPUT'
I//system/bin/iptables(14468): Flushing chain `POSTROUTING'
I/Netd (14489): Netd 1.0 starting
I//system/bin/iptables(14489): Flushing chain `INPUT'
I//system/bin/iptables(14489): Flushing chain `OUTPUT'
I//system/bin/iptables(14489): Flushing chain `FORWARD'
I//system/bin/iptables(14489): Flushing chain `PREROUTING'
I//system/bin/iptables(14489): Flushing chain `OUTPUT'
I//system/bin/iptables(14489): Flushing chain `POSTROUTING'
I get this in logcat when i try to boot. It just repeats that forever..
Did you root? That is an odd error if not, since the byte code layer and framework are pretty good at avoiding corruption of protected files. If not a root related issue, seems a hardware related flash corruption is possible.
Have you tried a hard reset? Not the best option, but might be the only one.
well I just flashed a rom i've been working on porting and that's what i get in logcat (it's just stuck at a blank screen). i tried deleting the ipcofig file from /system/bin/ to see what it says and it tells me it's missing or something like that (obvious i know ). From what research i've done it seems to be kernel related but i can't really find any specific info on it lol.
That does seem a lower level failure. I rooted my Droid 3, but will leave my Flyer at stock.
Netflix plays great, good battery life and already faster than my rooted D3 and Thrive. I see no gain to root and plan on leaving Gingerbread on it. A 7" display is small enough without having a navigator bar take up more space.
Related
Hi all,
I have a t-mobile phone and tried to install android 2.2. there. I used mdeejay's and darkStone's builds, but wifi didn't work at any of them. I've found a person who uses T-mobile hd2 too and installed the same versions of rom and radio. It didn't helped. In windows mobile wifi works well.
Could you please advice how to hande it? Did anyone face the same problem?
Thank you in advance.
#did some debug via adb:
I suppose that the red line below tells about reason.. But I haven't dealt with WPA on android before.. Any help is appreciated.
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
I/WifiHW ( 1916): wifi_load_driver enter
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
I/WifiHW ( 1916): wifi_load_driver end right 3
I/WifiHW ( 1916): wifi_start_supplicant enter
I/WifiHW ( 1916): wifi_start_supplicant end right 2
D/WifiService( 1916): ACTION_BATTERY_CHANGED pluggedType: 2
I/wpa_supplicant( 2771): CTRL-EVENT-STATE-CHANGE id=-1 state=0 BSSID=00:00:00:00
:00:00
E/wpa_supplicant( 2771): Failed to disable WPA in the driver.
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/PowerManagerService( 1916): New lightsensor value:40, lcdValue:90
D/lights ( 1916): set_light_buttons
D/lights ( 1916): set_light_keyboard
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x6257a8), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x6257a8), index=0, pid=2298,
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
E/SettingsWifiLayer( 2298): Unable to scan for networks
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::setBuffers(this=0x4ca268), pid=2298, w=1, h=1
D/SurfaceFlinger( 1916): Layer::requestBuffer(this=0x4ca268), index=0, pid=2298
w=350, h=85 success
E/WifiHW ( 1916): Supplicant not running, cannot connect
V/WifiStateTracker( 1916): Supplicant died unexpectedly
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/WifiStateTracker( 1916): Disabling interface
D/WifiService( 1916): setWifiEnabled( mAirplaneModeOverwridden=)false
D/WifiStateTracker( 1916): Reset connections and stopping DHCP
D/NetUtils( 1916): ifc_get_info addr=0 !
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = true
D/WifiStateTracker( 1916): Disabling interface
I/WifiHW ( 1916): wifi_stop_supplicant enter
I/WifiHW ( 1916): wifi_stop_supplicant end right 1
I/WifiHW ( 1916): wifi_unload_driver enter
I/WifiHW ( 1916): wifi_unload_driver end right 2
D/NetSharing_NSReceiver( 2298): onReceive : android.net.wifi.WIFI_STATE_CHANGED
D/NetSharing( 2298): wifi enabled change, state = false
how to set up MAC address for android builds (except startup.txt)?
Hi again,
I did some search and found that the core of the problem is in getting MAC address for wifi. (as dmsg says). Exactly the same problem was for Touch2, Tilt and other devices (http://forum.xda-developers.com/showthread.php?p=9211659) and it was resolved after they corrected wifi-nvram.txt. This file is responsible for setting up MAC address there, but I couldn't find it at builds for hd2.
if anybody knows what file is used to set up MAC address for wifi, I would be very appreciated.
Thanks!
I believe they just checked for their WiFi mac address from one of the following locations:
Settings->About phone->Status
Wireless & Networks -> WiFi Settings -> Menu Button -> Advanced
Then they edited the nvram.txt file @ /system/lib/hw/wifi/nvram.txt to include the proper MAC address.
Thanks for the answer!
Unfortunatelly wireless settings are not available until wifi is turned on.
I investigated the problem deeper and found that the reason could be in wifi hardware initialization. I did dmesg and saw the following:
wlan: wifi_set_power = 1
htcleo_wifi_power: 1
wlan: wifi_set_carddetect = 1
htcleo_wifi_set_carddetect: 1
mmc0: card_present 1
mmc0: Slot status change detected (0 -> 1)
wlan: Dongle Host Driver, version 4.218.204.2
mmc0: queuing CIS tuple 0x91 length 3
mmc0: new high speed SDIO card at address 0001
wlan: DHD: dongle ram size is set to 294912(orig 294912)
wlan: dhd_bus_rxctl: resumed on timeout
wlan: firmware version: ver
wlan: Return_dpc value is : 0
wlan: stop poll
wlan: dhd_bus_rxctl: resumed on timeout
wlan: dhd_preinit_ioctls: can't get MAC address , error=-110
wlan: dhdsdio_probe: failed
Since in windows mobile wifi does work I used the firmware files from WM: nvram.txt and rtecdc1.bin. As it turned out nvram in android is located in /proc/calibraion. But unfortunatelly it didn't help. So, I think that the problem is in bcm4329.ko driver. I'm not sure why other people with the same hd2 (t-mobile US) and the same ROM/RADIO/Android have no such issue. Perhaps my broadcomm hardware has a problem which is bypassed in windows, but not in Android.
I wonder if there is a way to get more detailed info than dmesg and logcat give (except building andoid sources of course ).
I don't know if it can help, but still, I'll say it anyway.
I think i had the same problem some times ago.
Wifi in android wouln't work, but was perfectly working in winmo.
it seems that if wifi is on in winmo when you boot on android, the wifi device seems to be blocked in some way.
Do you have wifi enabled in winmo? if yes, try to disable it, and boot on android to see if it works.
Hi kushulain,
Thanks for the advice! (I've almost started to build andriod by myself to find out the reason..) Unfortunatelly wifi was turned off when android was booting.
But this is another point to play around. I haven't tried to boot andriod with wifi turned on.
Thanks!
Just tried to boot andriod with wifi turned on. The device hangs at the beginning of the booting (even before screen with 'htc' appears). I think it is connected to my problem.
Did someone have similar problems?
Hey, I have the same problem, did you find any solution ?
Guys have you tried to change the radio part of the phone with a suitable one?
canavaro said:
Hey, I have the same problem, did you find any solution ?
Click to expand...
Click to collapse
hi, I didn't fix it actually due to lack of time. I tried to use wm hw init files in Android, but it didn't help. There is a score of my posts on this forum regarding this topic so you can find exactly what I tried. The funny thing is that WiFi works in wp7.
To stealth21
yes, that was the first thing I tried.
when I use OTG cable plug the ZTE MF820 LTE Dongle, android can detect its model but the 3g/4g not work .
I checked there is a file
/etc/usb_modeswitch.d/19d2_0166
###########################
ZTE MF820 4G LTE
DefaultVendor= 0x19d2
DefaultProduct=0x0166
TargetVendor= 0x19d2
TargetProduct=0x0167
MessageEndpoint=0x01
MessageContent=55534243123456782400000080000685000000240000000000000000000000
CheckSuccess=20
here is a part of the message from the logcat:
D/MountService( 146): sendStorageIntent Intent { act=unmounted dat=file:///mnt/usbhost1 (has extras) }
D/MountService( 146): volume state changed for /mnt/usbhost1 (unmounted -> removed)
D/MountService( 146): sendStorageIntent Intent { act=android.intent.action.MEDIA_REMOVED dat=file:///mnt/usbhost1 (has extras) }
D/[CORE_SERVICE]( 2057): Receive media broadcast
D/[NOTIFICATION]( 2057): ignore a notification because of not accepted
I/StorageNotification( 213): Media {/mnt/usbhost1} state changed from {unmountable} -> {unmounted}
D/VoldCmdListener( 82): volume shared /mnt/sdcard ums
I/StorageNotification( 213): Media {/mnt/usbhost1} state changed from {unmounted} -> {removed}
.
.
.
D/APPTrafficLogic( 1867): 10053--android.process.acore--0--0--
I/USB3G ( 92): event { 'add', '/devices/platform/sw_hcd_host0/usb1/1-1', 'usb', '', 189, 9 }
I/USB3G ( 92): path : '/sys/devices/platform/sw_hcd_host0/usb1/1-1'
I/USB3G ( 92): VID :size 5,vid_path '/sys/devices/platform/sw_hcd_host0/usb1/1-1/idVendor',VID '19d2
I/USB3G ( 92): '.
I/USB3G ( 92): PID :size 5,Pid_path '/sys/devices/platform/sw_hcd_host0/usb1/1-1/idProduct',PID '0167
I/USB3G ( 92): '.
I/USB3G ( 92): cmd=/system/etc/usb_modeswitch.sh /system/etc/usb_modeswitch.d/19d2_0167 &,
I/USB3G ( 92): excute ret : 0,err:No such file or directory
what is the problem? thank you for any advice.
I rename the 19d2_0166 to 19d2_0167
and run
/# system//etc/usb_modeswitch.sh system/etc/usb_modeswitch.d/19d2_0167
Reading config file: /etc/usb_modeswitch.d/19d2_0167
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.0 (C) Josua Dietze 2011
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0x0166
TargetVendor= 0x19d2
TargetProduct= 0x0167
TargetClass= not set
TargetProductList=""
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="55534243123456782400000080000685000000240000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode disabled
usb_set_debug: Setting debugging level to 15 (on)
usb_os_find_busses: Found 003
usb_os_find_busses: Found 002
usb_os_find_busses: Found 001
usb_os_find_devices: Found 001 on 003
usb_os_find_devices: Found 002 on 002
usb_os_find_devices: Found 001 on 002
error obtaining child information: Inappropriate ioctl for device
usb_os_find_devices: Found 019 on 001
usb_os_find_devices: Found 001 on 001
error obtaining child information: Inappropriate ioctl for device
Looking for target devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 19d2:0167
found matching vendor ID
found matching product ID
adding device
searching devices, found USB ID 1d6b:0001
Found devices in target mode or class (1)
Looking for default devices ...
searching devices, found USB ID 1d6b:0001
searching devices, found USB ID 0bda:8176
searching devices, found USB ID 1d6b:0002
searching devices, found USB ID 19d2:0167
found matching vendor ID
searching devices, found USB ID 1d6b:0001
No devices in default mode found. Nothing to do. Bye.
is that miss something ?
Hi folks...
My contribution by to the community...
Over the weekend, I figured out how to get a HID Mouse to connect to the Nexus Q.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I wrote about it here..
goto : droidcloudshare.blogspot.com
*DISCLAIMER: PROCEED AT YOUR OWN RISK.
This is really pre-beta...
I am not responsible for any damage that your device that may result from doing this. Specifically, DON'T COME COMPLAINING TO ME IF YOU BRICK YOUR NEXUS Q. At this moment, the ability to unbrick a Nexus Q maybe very limited....
SO ONCE AGAIN, PROCEED AT YOUR OWN RISK.
Let me know if you have trouble and I'll try to fix.
Next thing will be to get HID Keyboard and Headset working too.
could you github NexusQTools Source Code
You can also use a usb OTG cable and hook up a usb keyboard / mouse. The cable I use for my XOOM worked just fine.
I couldn't make the Q boot into clockworkmod recovery, it boots to the normal UI with this img, so I used another one, if you are having problem with this step, just reply here and I will give you the link, I'm not sure if I can put links from another forum...
auad, I'd love that link, and if you could also perhaps toss some backups of your Q my way, that'd help me bring it out of a bricked state... thanks!
Followed all the steps, but the Nexus Q Tools baffles me. Attaching a screenshot and some logs.
07-11 17:01:55.968: D/OpenGLRenderer(483): Flushing caches (mode 1)
07-11 17:01:55.984: D/OpenGLRenderer(483): Flushing caches (mode 0)
07-11 17:01:56.007: D/HidConnectActivity(2065): Remote BDADDR = 58:1F:AA:EA:FBC
07-11 17:01:56.015: D/HidConnectActivity(2065): Turning on Bluetooth...
07-11 17:01:56.015: D/BluetoothAdapterStateMachine(163): PowerOff process message: 1
07-11 17:01:56.015: D/BluetoothAdapterStateMachine(163): Bluetooth state 10 -> 11
07-11 17:01:56.015: I/bluedroid(163): Starting hciattach daemon
07-11 17:01:56.023: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.039: D/HidConnectActivity(2065): BT state change: STATE_TURNING_ON
07-11 17:01:56.117: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.171: I/ActivityManager(163): Displayed com.droidcloudshare.bt/.HidConnectActivity: +249ms
07-11 17:01:56.218: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.320: I/bluedroid(163): bt_enable: ret: -1, errno: 19
07-11 17:01:56.421: E/brcm_patchram_plus(2078): Done setting line discpline
07-11 17:01:56.507: I/bluedroid(163): bt_enable: ret: -1, errno: 114
07-11 17:01:56.507: W/bluedroid(163): Bluetoothd already started, unexpectedly!
07-11 17:01:56.507: I/bluedroid(163): Starting bluetoothd deamon
07-11 17:01:56.515: E/BluetoothEventLoop.cpp(163): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
07-11 17:01:56.531: E/BluetoothEventLoop.cpp(163): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
07-11 17:01:56.546: E/BluetoothEventLoop.cpp(163): get_adapter_path: D-Bus error: org.freedesktop.DBus.Error.ServiceUnknown (The name org.bluez was not provided by any .service files)
07-11 17:01:56.578: I/BluetoothEventLoop.cpp(163): agent_event_filter: Received method org.bluez.Agent:Release
07-11 17:01:56.687: D/BluetoothAdapterStateMachine(163): WarmUp process message: 101
07-11 17:01:56.710: D/OpenGLRenderer(483): Flushing caches (mode 1)
07-11 17:02:06.687: D/BluetoothAdapterStateMachine(163): WarmUp process message: 104
07-11 17:02:06.687: E/BluetoothAdapterStateMachine(163): Bluetooth adapter SDP failed to load
07-11 17:02:06.695: E/BluetoothService.cpp(163): setBluetoothTetheringNative false
07-11 17:02:06.734: I/bluedroid(163): Stopping bluetoothd deamon
07-11 17:02:07.234: I/bluedroid(163): Stopping hciattach deamon
07-11 17:02:07.234: D/BluetoothAdapterStateMachine(163): Bluetooth state 11 -> 10
07-11 17:02:07.234: D/BluetoothAdapterStateMachine(163): PowerOff process message: 101
07-11 17:02:07.242: D/HidConnectActivity(2065): BT state change: STATE_OFF
07-11 17:02:07.273: D/DockEventReceiver(427): finishStartingService: stopping service
07-11 17:02:11.289: D/OpenGLRenderer(483): Flushing caches (mode 1)
07-11 17:02:11.390: D/dalvikvm(637): GC_CONCURRENT freed 464K, 5% free 12609K/13191K, paused 4ms+4ms
07-11 17:04:14.281: D/dalvikvm(163): GC_CONCURRENT freed 513K, 6% free 15453K/16327K, paused 5ms+4ms
07-11 17:05:35.359: D/OpenGLRenderer(483): Flushing caches (mode 2)
07-11 17:05:35.367: I/EventLogService(444): Aggregate from 1342038935272 (log), 1342038935272 (data)
07-11 17:05:35.421: I/ServiceDumpSys(444): dumping service [account]
07-11 17:05:35.453: D/dalvikvm(444): GC_CONCURRENT freed 331K, 4% free 12860K/13319K, paused 5ms+3ms
07-11 17:07:00.187: D/PermissionCache(99): checking android.permission.READ_FRAME_BUFFER for uid=2000 => granted (244 us)
07-11 17:07:02.804: D/dalvikvm(163): GC_CONCURRENT freed 578K, 5% free 15513K/16327K, paused 5ms+5ms
fredc888 said:
Hi folks...
My contribution by to the community...
Over the weekend, I figured out how to get a HID Mouse to connect to the Nexus Q.
I wrote about it here..
goto : droidcloudshare.blogspot.com
*DISCLAIMER: PROCEED AT YOUR OWN RISK.
This is really pre-beta...
I am not responsible for any damage that your device that may result from doing this. Specifically, DON'T COME COMPLAINING TO ME IF YOU BRICK YOUR NEXUS Q. At this moment, the ability to unbrick a Nexus Q maybe very limited....
SO ONCE AGAIN, PROCEED AT YOUR OWN RISK.
Let me know if you have trouble and I'll try to fix.
Next thing will be to get HID Keyboard and Headset working too.
Click to expand...
Click to collapse
This works well, a small revision in the directions that may help a few people are:
Step #5 item 7 should read:
Update the main.conf ownership and permissions
adb shell chown bluetooth /system/etc/bluetooth/main.conf
adb shell chmod 440 /system/etc/bluetooth/main.conf
I also had a question regarding connecting a second input device such as a wireless keyboard, would I just repeat the Stpe #6 item 4 with the Bluetooth address for the device I wish to input? Also would you happen to know why an on screen keyboard doesn't appear? I can't type anything nor can I open any application that has keyboard input such as Google Play & Gmail (to sign in)
mrjaymillz said:
This works well, a small revision in the directions that may help a few people are:
Step #5 item 7 should read:
Update the main.conf ownership and permissions
adb shell chown bluetooth /system/etc/bluetooth/main.conf
adb shell chmod 440 /system/etc/bluetooth/main.conf
I also had a question regarding connecting a second input device such as a wireless keyboard, would I just repeat the Stpe #6 item 4 with the Bluetooth address for the device I wish to input? Also would you happen to know why an on screen keyboard doesn't appear? I can't type anything nor can I open any application that has keyboard input such as Google Play & Gmail (to sign in)
Click to expand...
Click to collapse
To put it back exactly like it was, you'd issue
chown bluetooth.bluetooth main.conf
note the period, as help for chown on android shows USER[.GROUP] for setting the permissions.
Either way, this worked great for pairing a magic trackpad. Interestingly if i multitouch all 10 fingers on the pad, there's representations for each finger that show up on the display output on the Q
Scrambling my brain!
Hey all, just giving a bump to see if anyone is still watching. I'm sort of novice, but trying hard to wrap my head around this. My Q is rooted properly I believe. Been able to sideload and get the launcher to work, so I'm now onto the bluetooth mouse.
1. I noticed when I ADB SHELL MOUNT, where it should say "rootfs on / type rootfs (rw)" it says "rootfs / rootfs ro,realtime 0 0". If that is not read/wright will it cause me issues down the road?
2. When I fastboot the recovery image I downloaded, it doesn't go into CWM recovery, just boots normally. EDIT: Solved this by using the steelhead boot img.
3. What string would I use to list the main.conf so that I could confirm that my chmod worked?
4. When I get to the step "adb shell am start -a android.intent.action.MAIN -n com.droidcloudshare.bt/.HidConnectActivity --es 00:07:61:EB:1DD", I am returned with a list of am usage commands followed by "Error: Argument expected after "00:07:61:EB:1DD"". EDIT: So I didn't realize that {HID Mouse Bluetooth Address} was part of the string. So this time I entered adb shell am start -a android.intent.action.MAIN -n com.droidcloudshare.bt/.HidConnectActivity --es 00:07:61:EB:1DD {HID Mouse Bluetooth Address} and was returned with this:
Starting: Intent { act=android.intent.action.MAIN pkg=Mouse cmp.droidcloudshare.bt/.HidConnectActivity (has extras) }
Error type 3
Error: Activity Class {com.droidcloudshare.bt/com.droidcloudshare.bt.HidConnectActivity} does not exist.
5. I've been retracing my steps, and when I perform adb install -r NexusQTools.apk I get the amount of data transferred and how fast, but then adb just hangs, no "Success". Originally I just closed the command window and restarted and moved on assuming it installed. If Success isn't confirmed is it safe to say it didn't properly install? Is this apk essential to get the mouse to pair on the Q?
So for now I'm kinda stuck, if anyone has a bit of advice I'll gladly take it and push on.
Cheers
can this be used to connect a keyboard and mouse at the same time?
I think they only reason it won't work for a keyboard right now is because there needs to be a driver present for the keyboard
Hello there,
My Samsusng Galaxy S2 (i9100) has recently stopped working as it is supposed to. While I tried debugging the issue in any way I could, I figured out I might get some help over here.
At any time that the device itself isn't connected to a power source (USB cable [adb] or the charger), it randomly crashes (the screen turns black and I have to turn the phone on again). I also must say that this problem doesn't happen while on the recovery screen (CWM based recovery).
At first I thought this may happen because I've installed a pretty old version of Cyanogenmod (the cm11 installer version), so I installed the recent monthly build, but the issue still persists. I've tried debugging the device wirelessly (because when it was connected to a power source it never crashed), so I played a game which makes the CPU work abit, and I thought I'll get a crash log - which I didn't get. The last radio signal I got from the phone was this:
I/LibraryLoader( 2817): Expected native library version number "",actual native
library version number ""
I/chromium( 2817): [INFO:library_loader_hooks.cc(116)] Chromium logging enabled:
level = 0, default verbosity = 0
I/BrowserStartupController( 2817): Initializing chromium process, renderers=0
D/TinyALSA-Audio Hardware( 1855): audio_hw_get_mic_mute(0x4003e938, 0x4126daeb)
D/BluetoothManagerService( 2205): Message: 20
D/BluetoothManagerService( 2205): Added callback: android.bluetooth.IBluetoothMa
[email protected]:true
D/BluetoothAdapter( 2817): 1112752792: getState() : mService = null. Returning
STATE_OFF
D/libEGL ( 2817): loaded /system/lib/egl/libEGL_mali.so
D/libEGL ( 2817): loaded /system/lib/egl/libGLESv1_CM_mali.so
D/libEGL ( 2817): loaded /system/lib/egl/libGLESv2_mali.so
E/ ( 2817): Device driver API match
E/ ( 2817): Device driver API version: 23
E/ ( 2817): User space API version: 23
E/ ( 2817): mali: REVISION=Linux-r3p2-01rel3 BUILD_DATE=Wed Oct 9 21:05:
57 KST 2013
W/chromium( 2817): [WARNINGroxy_service.cc(890)] PAC support disabled because
there is no system implementation
I/chromium( 2817): [INFO:CONSOLE(0)] "Document was loaded from Application Cache
with manifest {URL}
k-core-v40.appcache", source: {URL}
d/sdk/native/sdk-core-v40.html (0)
I/chromium( 2817): [INFO:CONSOLE(0)] "Application Cache Checking event", source:
{URL}
l (0)
I/chromium( 2817): [INFO:CONSOLE(0)] "Application Cache NoUpdate event", source:
{URL}
l (0)
W/chromium( 6284): [WARNINGroxy_service.cc(890)] PAC support disabled because
there is no system implementation
I/chromium( 6284): [INFO:simple_index_file.cc(437)] Simple Cache Index is being
restored from disk.
D/Yamaha-MC1N2-Audio( 1855): yamaha_mc1n2_audio_output_stop()
D/Yamaha-MC1N2-Audio( 1855): yamaha_mc1n2_audio_route_start()
Click to expand...
Click to collapse
I've tried tracing the log files the system automatically creates in the ./system folder, but I couldn't find any useful information except from some deamon crash logs.
I tried resetting the dalvik cache, reinstalling my ROM manually (adb sideload), preforming a complete factory reset and wiping cache partition, and yet it didn't work.
I'm quite sure the issue relates to my phone's battery (which overheated a bit when I used it for a long time), but I'm still not completely sure this is the issue, so I would like to hear your suggestions.
Thanks in advance,
Eden
Eden Campo said:
Hello there,
....
I've tried tracing the log files the system automatically creates in the ./system folder, but I couldn't find any useful information except from some deamon crash logs.
I tried resetting the dalvik cache, reinstalling my ROM manually (adb sideload), preforming a complete factory reset and wiping cache partition, and yet it didn't work.
I'm quite sure the issue relates to my phone's battery (which overheated a bit when I used it for a long time), but I'm still not completely sure this is the issue, so I would like to hear your suggestions.
Thanks in advance,
Eden
Click to expand...
Click to collapse
I also read your logcat or yeah the part of it and it seems all to be fine, normal lines.
I don't own the S2 anymore and I didn't had the issue. But I suggest to try somethings first before buying a new battery.
Try another rom instead of cyanogenmod, Cyanogenmod is supporting Alot of devices and it's not really good specific for devices so I suggest to try one of the roms from the development forums.(Cyanogenmod always have bugs.)
Try to flash back to stock with odin
Try to borrow a battery from a friend and see or you still have the same problem
Remove the battery out of the phone and leave your phone without a battery for like 1-5 minutes.
It could be maybe the battery that it got issues cause the S2 is not the newest phone anymore and hardware also has a lifetime sadly. But your screen goes black and your device goes off right?
Hi,
I am currently building a CM 12.1 ROM for the Redmi Note 3, and most of the stuff works, but I have problems getting the device encryption to work, and was hoping somebody could help me figure this out.
Device encryption is built-in, but enabling it leads to an error. Specifically, when telling Android to encrypt the device (i.e., selecting "Encrypt phone" in the settings), it starts the process, but after less than one minute shows a screen saying that the encryption failed, and that the phone needs to be factory reset.
The logcat shows the following output:
Code:
05-15 19:47:49.694 I/Cryptfs ( 254): Using scrypt for cryptfs KDF
05-15 19:47:50.680 I/Cryptfs ( 254): Enabling support for allow_discards in dmcrypt.
05-15 19:47:50.680 I/Cryptfs ( 254): load_crypto_mapping_table: target_type = crypt
05-15 19:47:50.680 I/Cryptfs ( 254): load_crypto_mapping_table: real_blk_name = /dev/block/platform/mtk-msdc.0/by-name/userdata, extra_params = 1 allow_discards
05-15 19:47:55.706 E/Cryptfs ( 254): Cannot load dm-crypt mapping table.
05-15 19:47:55.707 I/Cryptfs ( 254): Encrypting ext4 filesystem in place...
05-15 19:47:55.707 I/Cryptfs ( 254): Encrypting group 0
05-15 19:47:55.710 E/Cryptfs ( 254): Error writing crypto_blkdev /dev/block/dm-0 for inplace encrypt
05-15 19:47:55.710 I/Cryptfs ( 254): Encrypted to sector 0
05-15 19:47:55.710 E/Cryptfs ( 254): Error encrypting groups
05-15 19:47:55.710 D/Cryptfs ( 254): cryptfs_enable_inplace_ext4()=-1
05-15 19:47:55.710 E/Cryptfs ( 254): Failed to encrypt f2fs filesystem on /dev/block/platform/mtk-msdc.0/by-name/userdata
05-15 19:47:55.710 I/Cryptfs ( 254): Encrypted to block -1
05-15 19:47:55.710 D/Cryptfs ( 254): cryptfs_enable_inplace_f2fs()=-1
05-15 19:47:55.710 E/Cryptfs ( 254): Encrypting filesystem in place...
05-15 19:47:55.710 E/Cryptfs ( 254): Cannot seek to previously encrypted point on /dev/block/dm-0
05-15 19:47:55.710 D/Cryptfs ( 254): cryptfs_enable_inplace_full()=-1
with the most pertinent line probably this one:
Code:
05-15 19:47:55.706 E/Cryptfs ( 254): Cannot load dm-crypt mapping table.
At the same time, the kernel log prints the following:
Code:
<3>[ 1196.971648] (3)[324:vold]device-mapper: table: 253:0: crypt: Device lookup failed
<4>[ 1196.971659] (3)[324:vold]device-mapper: ioctl: error adding target to table
I have traced this problem through the source code, and I suspect it is somewhere in dm-crypt.c of the Linux kernel, in the crypt_ctr() function:
Code:
if (dm_get_device(ti, argv[3], dm_table_get_mode(ti->table), &cc->dev)) {
ti->error = "Device lookup failed";
goto bad;
}
Presumably, dm_get_device() fails for some reason (of course, I might be mistaken and the problem is somewhere else, but tracing the function calls in the source code seems to suggest that this is where the error comes from).
Unfortunately, the kernel sources for the device in question are not available, so I cannot perform any more detailed testing on the kernel.
An additional piece of the puzzle is that there is an AOSP 5.0 ROM for the same device, which uses exactly the same kernel (as in, the same binary), and there the phone encryption works. Unfortunately, I am not familiar enough with dm-crypt, the device mapper and other related things around it to figure out what the difference is, and why it fails on CM-12.1 (e.g., whether there is for example any device mapper configuration somewhere that could be different, etc.).
Even more strangely, if I encrypt the user partition on the AOSP ROM, then use TWRP recovery to flash my CM-12.1 ROM, wipe the data partition (which does not remove encryption, as TWRP can correctly decrypt and mount the data partition), then my CM-12.1 ROM boots normally and decrypts the data partition (presumably then not having a problem with the device-mapper).
I have been banging my head against this problem for a bit too long, so if anybody has any ideas or knows that the problem could be and how to solve it, that would be very much appreciated.
for kernel maybe you can refer to this : http://forum.xda-developers.com/mei...elio-x10-kernel-source-code-released-t3225886, i saw that meizu mx was shared the same processor with ours.
Whyv
galuh said:
for kernel maybe you can refer to this : http://forum.xda-developers.com/mei...elio-x10-kernel-source-code-released-t3225886, i saw that meizu mx was shared the same processor with ours.
Click to expand...
Click to collapse
Why you digged up this old thread? Not that it would help other devs 'cause we already have CM13 ROMs.
AtomR said:
Whyv
Why you digged up this old thread? Not that it would help other devs 'cause we already have CM13 ROMs.
Click to expand...
Click to collapse
Yes if you had snapdragon version you were having cm 13 but if you were holding the mtk version you will stuck in lolipop i bet till now. Cm 13 only available for snapdragon bersion not mtk.