Hello,
I recently bought on Internet a cheap tablet (REF : LAZER MD1005). Since, it was used, I did a factory reset in order to clean all the data of the previous owner. However, when it rebooted, the screen stopped working. I don't think it's an hardware problem, since it worked fine before. I'm not very aware of how android works, but I thought some drivers could have been deleted, is that possible ?
Here you'll find all the info I grabbed :
Brand : Lazer
Model : MD1005
Android Version : 4.1.1
Kernel Version : 3.0.8
Build number : JRO03C.20130412.v008
Touch Screen Controller : CHIPONE ICN8305M
> When I type 'logcat | grep EventHub' it tells me that there is on event6 a device named 'chipone-ts', but that it has no configuration file.
> Here is what I get with getevent -p
Code:
add device 2: /dev/input/event6
name: "chipone-ts"
events:
KEY (0001): 0066 008b 009e 00d9
ABS (0003): 002f : value 0, min 0, max 254, fuzz 0, flat 0, resolution 0
0030 : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
0032 : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
0035 : value 0, min 0, max 1024, fuzz 0, flat 0, resolution 0
0036 : value 0, min 0, max 600, fuzz 0, flat 0, resolution 0
0039 : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
input props:
INPUT_PROP_DIRECT
Do you think there is any way to fix this ? Thanks for your help !
You can try to flash your original rom !!!
Sent from my XT1022 using Tapatalk
androidrocks23 said:
You can try to flash your original rom !!!
Sent from my XT1022 using Tapatalk
Click to expand...
Click to collapse
Thank you for your reply.
Indeed, that would be a good idea.
However this tablet is so rare that I did not manager to find any original rom.
Related
hi everyone, i've made a port of sense 3.5 on evo 3D GSM and some bug persist like sound first and in logcat this is what i got :
W/AudioHardwareMSM8660( 2507): written 0, check if route has been changed..
any ideas about that ??
Hi Guys,
So i've been trying to flash modules from within the phone without having to boot into the recovery,
and i found that i can just extract the update-binary and execute it through shell and it will do the trick!!
however,
know im trying to do that through my app,
i successfully got root access using Chainfire's libsuperuser,
however, whenever i send the commands to run update-binary i get "segmentation fault(core dumped)" Error.
the command i using in both shell and from within the app is "./update-binary 3 stdout ./modules.zip".
P.S. this might be irrelevent but when ever i add a number before stdout (e.g 7stdout) i get segmentation fault during shell as well,
other than that, i can't find the problem
This is a logcat of the process through strace, if we have a linux debugger here
Code:
08-24 17:06:43.568 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] execve("./update-binary", ["./update-binary", "3", "recovery", "./KernelLighter.zip"], [/* 24 vars */]) = 0
08-24 17:06:43.573 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] gettid() = 9202
08-24 17:06:43.573 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] syscall_983045(0x39a10, 0x399d4, 0, 0x40, 0x399d4, 0xbea729c0, 0xd8ec, 0xf0005, 0, 0, 0, 0, 0, 0xbea72960, 0x28dcf, 0x8c9c, 0x60000010, 0x39a10, 0, 0, 0xc764, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0) = 0
08-24 17:06:43.588 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] mmap2(NULL, 131072, PROT_READ, MAP_SHARED, 8, 0) = 0x4007e000
08-24 17:06:43.588 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] open("/dev/urandom", O_RDONLY|O_LARGEFILE) = 4
08-24 17:06:43.588 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] read(4, "B\300>7", 4) = 4
08-24 17:06:43.593 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] close(4) = 0
08-24 17:06:43.598 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40119000
08-24 17:06:43.598 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] mprotect(0x40119000, 4096, PROT_READ) = 0
08-24 17:06:43.603 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] fcntl64(0, F_GETFL) = 0 (flags O_RDONLY)
08-24 17:06:43.603 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
08-24 17:06:43.693 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] +++ killed by SIGSEGV (core dumped) +++
08-24 17:06:43.693 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] Process 9202 detached
08-24 17:06:53.368 8703-8756/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU%] END
08-24 17:06:43.603 8703-9188/com.thunder.kernel.lighter D/libsuperuser: [libsuperuser][SU*] fcntl64(0, F_GETFL) = 0 (flags O_RDONLY)
Click to expand...
Click to collapse
I think this line is the important one. I think fcntl stands for flag control, also there is something about read only. Hope this helps somehow, I am not an android expert, but I do know a few things about linux...
I've read some man pages. Combined with what I know from Android I suppose the following: When you execute the command in the shell, there is nothing between it and the kernel / memory. If you execute it from within the app, you have to bypass some securit system put around Android apps which is checking the permissions of the apps. The app itself will not be able to write to the memory, therefore the process is generating a SIGSEV signal, which just says the process trying to write is not allowed to write. Without this, executed from the shell directly, you are allowed as you already have full access
You get a segmentation fault (I suppose SIGSEV as well) when you write something before stdout, because stdout is specifying a system device; the standard output. When the system can't find this device, it is missing an address to write to, that's why you get the segmentation fault as well.
Hope this hellps, I am not entirely sure.
I figured it was due to stdout but is there a way around it?
Sent from my HTC One X
As I already said, I am not an Android expert. But what you have to try is: I don't know if this is possible, but try to start a new shell instance form within the app, gain root access and execute the command there rather than directly processing the command from the app. That's what I do in a Linux GUI when trying to run particular commands.
EDIT: Another question: What does the command update-binary do exactly? Does it need stdout as parameter definitely? Also, as stdout is a virtual system device, that's likely the cause why it won't work from within the app. Is there an Android access right for virtual system devices like stdout which you need to sepcify for the app?
dansou901 said:
As I already said, I am not an Android expert. But what you have to try is: I don't know if this is possible, but try to start a new shell instance form within the app, gain root access and execute the command there rather than directly processing the command from the app. That's what I do in a Linux GUI when trying to run particular commands.
EDIT: Another question: What does the command update-binary do exactly? Does it need stdout as parameter definitely? Also, as stdout is a virtual system device, that's likely the cause why it won't work from within the app. Is there an Android access right for virtual system devices like stdout which you need to sepcify for the app?
Click to expand...
Click to collapse
You might have missed it,
But I'm running the command as root,
Thus it would already be in a different shell, the su.
I thought it could be permission but root only needs root permission and I have that.
The update-binary is found in all flashable zips,
It's what process the update scripts and flashes the zip,
I'm trying for a recovery less flashing technic.
Also the stdout parameter can be anything and it will still cause the error,
But from within a shell it will also work with anything.
Sent from my HTC One X
RAZR XT710 EU
I've had spotty GPS functionality ever since I've switched to the CM10.1 roms which means I had to sometimes restart the phone to get the blinking status icon. But once it was blinking I knew it took a few seconds to lock and I would get some satellites even indoors.
Two weeks ago the GPS stopped working completely, ever since I removed the SIM card. I've tried reinstalling the same ROM, installing other ROMs, doing a clean install on another slot (4.1.2. SPREM) but it just does not want to find any satellites.
I've used GPS Toolbox, Faster GPS and NMEA Decoder to see what it's outputting. On one ROM I was getting some strings with $PMOTO but no NMEA position strings.
The libgps shows an error code which could be either 9 on one ROM or 12 on another:
Code:
D/libgps_GpsMgr( 444): schedGps() mode: 3, tbf: 0, accuracy: 0, perf: 0, pAgps: null
D/libgps ( 444): GpsInterface_stop()
E/libgps ( 444): recv_command_status() : fix returned error code 9
D/libgps_GpsMgr( 444): sched() set mode: 3, tbf: 0
D/libgps ( 444): status_cb: GPS_STATUS_SESSION_END (2)
D/libgps_GpsMgr( 444): schedGps() mode: 0, tbf: 1, accuracy: 0, perf: 0, pAgps: null
D/libgps ( 444): GpsInterface_set_position_mode( 0, 1, 100, 0 )
D/libgps ( 444): GpsInterface_start()
D/libgps_GpsMgr( 444): sched() set mode: 0, tbf: 1
D/GpsLocationProvider( 444): NTP server returned: 1382386872254 (Mon Oct 21 22:21:12 CEST 2013) reference: 36370 certainty: 18 sy
stem time offset: -326353
D/libgps ( 444): GpsInterface_inject_time( 1382386872254, 36370, 18 )
D/libgps ( 444): status_cb: GPS_STATUS_SESSION_BEGIN (1)
V/PhoneStatusBar( 576): setLightsOn(true)
D/libgps ( 444): GpsXtraInterface_inject_xtra_data( 0x41FC6370, 60862 )
......
E/libgps ( 444): recv_command_status() : fix returned error code 12
AFAIK the GPS functionality is on the same chip with WiFi and Bluetooth, both of which work perfectly. Is there any antenna connector that might have come loose? I didn't see any in the ifixit teardown.
Can Matt's utility be used to reset a phone that's non-Verizon? Or should I use RSD?
Fixed by flashing the factory firmware with RSD Lite.
Hi,
I also had a problem with GPS in Russia,
Here is a solution what helped me.
http://forum.xda-developers.com/showthread.php?p=43910953
If you don'thave the gps.omap4.so file, just placed the attached file on system/lib/hw, fix permissions (RWX / R-- / R--) via any root file explorer and reboot.
Click to expand...
Click to collapse
Hi.
I am using xt912 gsm prepaid sim India.
I am facing problem with ussd code for checking my balance and other think.
Like *111# not working.
I tried CM12.1 and AOKP
But same problem.
Can any one fix this ?
Or give me any other rom 4.4 or 4.1
Thanks .
Use ES File Manager or any other file manager that supports root and navigate to /system and open your build.prop, scroll to the last line and leave about two spaces(that is hit enter twice) and paste this..
Code:
# General GSM Settings
telephony.lteOnGsmDevice = 1
telephony.lteOnCdmaDevice = 0
telephony.rilV7NeedCDMALTEPhone = false
persist.ril.mux.noofchannels = 10
persist.ril.modem.mode = 2
persist.ril.features = 0x102
persist.radio.vzw.cdma.mdn = deleted
persist.radio.ap.phonetype = 1
persist.radio.lte.mm.disable = 1
ro.telephony.default_network = 3
ro.telephony.gsm-routes-us-smsc = 0
ro.telephony.ril.v3 = writeaidonly, signalstrength
ro.cdma.data_retry_config = default_randomization=2000, 0, 0, 120000, 180000, 540000, 960000
ro.gsm.data_retry_config = max_retries=infinite, default_randomization=2000, 0, 0, 80000, 125000, 485000, 905000
ro.cdma.subscribe_on_ruim_ready = false
# Motorola GSM Settings
ro.mot.eri = 0
ro.mot.phonemode.vzwglobalphone = 0
ro.mot.phonemode.vzw4gphone = 0
ro.mot.lte_on_cdma = 0
ro.mot.ds.fastdormancy.disable = true
Now save it, close the build.prop and reboot your device.
Thanks, it's work for me. I'm using Droid Razr in Bangladesh. I'd also tried lots of Customs Rom including CM 12.1 but none works about ussd problem.
I have been having Wifi problems with my Z2 for a while and decided to try and flash this.
I'm not 100% sure if this is the culprit or not but I have been having worse issues since.
Wifi seems to be stable but;
Bluetooth disconnects and reconnects intermittently, noticeable as Sleep for Android loses sync with my Garmin midway through the night
If Wifi has been connected for a while and I head out and lose Wifi connection, my mobile data stays off and won't come back on until I hard reset my phone.
I'm currently running Resurrection Remix N for Xperia Z2.
I'm guessing I'll need to do a logcat for both instances?
logcat
I believe it's around line 133;
Code:
09-02 12:29:41.496 D/ConnectivityService(1305): handleLingerComplete for NetworkAgentInfo [MOBILE (LTE) - 104]
09-02 12:29:41.500 D/DcNetworkAgent(2931): NetworkAgent: NetworkAgent channel lost
09-02 12:29:41.500 D/DcNetworkAgent(2931): NetworkAgent: DcNetworkAgent: [unwanted]: disconnect apnContext={mApnType=default mState=CONNECTED mWaitingApns={[[ApnSettingV3] Telstra Internet, 2937, 50501, telstra.wap, , , , , , -1, default | supl, IP, IP, true, 0, 0, 0, false, 0, 0, 0, 0, , , false]} mApnSetting={[ApnSettingV3] Telstra Internet, 2937, 50501, telstra.wap, , , , , , -1, default | supl, IP, IP, true, 0, 0, 0, false, 0, 0, 0, 0, , , false} mReason=dataDisabled mDataEnabled=false mDependencyMet=true}
09-02 12:29:41.511 D/ConnectivityService(1305): NetworkAgentInfo [MOBILE (LTE) - 104] got DISCONNECTED, was satisfying 9
09-02 12:29:41.554 I/libmdmdetect(334): ESOC framework not supported
09-02 12:29:41.555 E/libmdmdetect(334): Found internal modem: modem
09-02 12:29:41.556 I/libmdmdetect(334): ESOC framework not supported
09-02 12:29:41.556 E/libmdmdetect(334): Found internal modem: modem
09-02 12:29:41.591 I/libmdmdetect(334): ESOC framework not supported
09-02 12:29:41.592 E/libmdmdetect(334): Found internal modem: modem
09-02 12:29:41.613 W/ConnectivityExtension(1305): ConnectivityExt jar file not present