Fingerprint problem with G900t on cm13 - Galaxy S 5 Q&A, Help & Troubleshooting

Hi Guy's,
I've got a problem with my fingerprint after reflashing. I flashed the phone to cm13 and the fingerprint works well. All my phones are encrypted, so wanted it to on my S5. But that was a miss decision! After the was rebooted and typed in my pin, it hang on boot screen. I gave it another try by removing the batterie. Than it comes up, but with a full wipe. Strange was, that my internal storage shows only 3gb free, on an empty phone. I tried to flash it back with the original firmware, but it won't except my encryption pin. At least I flashed it back to cm13. But now my fingerprint won't work! What a mess! The setup for the fingerprint shows:
{
"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 got an terminal error, but I don't know if it regards to the fingerprint error:
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
CM Version: '13.0-20160820-SNAPSHOT-ZNH5YAO0J4-klte'
Build fingerprint: 'samsung/kltetmo/kltetmo:6.0.1/MMB29M/G900TUVU1GPE1:user/release-keys'
Revision: '0'
ABI: 'arm'
pid: 26949, tid: 26975, name: Terminal 0 >>> com.android.terminal <<<
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0
r0 a8d9e69c r1 00000010 r2 00000000 r3 00000000
r4 0000efff r5 00000010 r6 a86c5138 r7 ffffffff
r8 00000000 r9 0000003c sl a86c50e0 fp 00009fff
ip aee8efdc sp aec9e448 lr aee86b7d pc aee86bc2 cpsr 600f0030
backtrace:
#00 pc 00005bc2 /system/lib/libjni_terminal.so
#01 pc 00005503 /system/lib/libjni_terminal.so
#02 pc 00007239 /system/lib/libjni_terminal.so
#03 pc 00003d3d /system/lib/libjni_terminal.so
#04 pc 000039c7 /system/lib/libjni_terminal.so (vterm_push_bytes+410)
#05 pc 00002545 /system/lib/libjni_terminal.so (_ZN7android8Terminal3runEv+452)
#06 pc 0029330d /data/dalvik-cache/arm/[email protected]@[email protected]@classes.dex (offset 0x17d000)
I'm not a developer and can't analyse this message. That's why I wrote to the XDA developer forum. I got a post for that issue at the cm forum, but no replies.
Can somebody please give my a hint!
Best
Schlombie
Sent from my SM-G900T using XDA-Developers mobile app

Related

[Q] Storage space running out - but what's using it?

I realize there's plenty of threads with more or less the exact same topic. But I haven't found an answer in any of them that helps my situation.
Alright here's the deal:
I'm getting the "Storage space running out"-notification. And apps are starting to FC.. My phone is a i9505 and I'm currently running Carbon. But this was a problem with CM 10.2 too.
Here's what confuses me:
Code:
[email protected]:/data # busybox df -m
Filesystem 1M-blocks Used Available Use% Mounted on
...
/dev/block/platform/msm_sdcc.1/by-name/userdata
9351 9300 50 99% /data
...
/dev/fuse 9351 9300 50 99% /mnt/shell/emulated
...
/dev/block/vold/179:33
30688 25851 4837 84% /storage/sdcard1
Those should be the interesting bits (I'm showing off my 32GB external card here as well). Right, so I'm using 99%, or 9300MB.
Now here's how I check what's taking up the space:
Code:
[email protected]:/ # du -d1 -m /data
1 /data/dontpanic
3404 /data/media
1 /data/misc
1 /data/local
252 /data/data
1 /data/app-private
176 /data/app-asec
203 /data/app-lib
939 /data/app
1 /data/property
1 /data/ssh
1 /data/radio
321 /data/dalvik-cache
1 /data/resource-cache
1 /data/lost+found
1 /data/drm
1 /data/mediadrm
1 /data/security
4 /data/system
1 /data/wpstiles
1 /data/wiper
1 /data/shared
1 /data/fota
1 /data/time
1 /data/bluetooth
1 /data/audio
1 /data/.ssh
1 /data/tombstones
1 /data/nfc
1 /data/user
6 /data/qcks
1 /data/backup
1 /data/anr
5302 /data
du sums it up for us: 5302MB on /data
DiskUsage is showing me "System data" is taking up the space, but it doesn't tell me what or where:
{
"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've checked solutions mentioned in related threads (all over the internets):
* The "/datadata" issue - I don't have this directory
* The "lost + found" - It's 1MB as you can see
* The "/data/log" issue - I don't have this directory
So what am I missing?
Well wouldn't you know. After a reboot the usage is down and df reports the same as du. I'm still confused as to what took up the space though.. I even got Java exceptions (from DiskUsage) saying the disk was full.

Install Winxp on Note 3 N900

i have install " BOCHS APP" on my device and i make Image for windows xp using virtual machine
after i copy file " XP " and run BOCHS win xp not working i make all change on file bochsrc.txt
and still not working
Code:
###############################################################
# bochsrc.txt file for DLX Linux disk image.
###############################################################
# how much memory the emulated machine will have
megs: 384
cpu: count=2, ips=6000000, reset_on_triple_fault=1, ignore_bad_msrs=1
# filename of ROM images
romimage: file=BIOS-bochs-latest
vgaromimage: file=VGABIOS-lgpl-latest
vga: extension=cirrus, update_freq=50
pci: enabled=1, chipset=i440fx, slot1=cirrus
# what disk images will be used
#floppya: 1_44=W98RUS.img, status=inserted
#floppyb: 1_44=floppyb.img, status=inserted
# hard disk
ata0: enabled=1, ioaddr1=0x1f0, ioaddr2=0x3f0, irq=14
ata1: enabled=1, ioaddr1=0x170, ioaddr2=0x370, irq=15
ata0-master: type=disk, path="xp"
#ata0-slave: type=disk, path="d.img"
ata1-master: type=disk, mode=vvfat, path=/sdcard/hdd, journal=vvfat.redolog
#type=cdrom, path="RUSW95B_USB.ISO", status=inserted
# choose the boot disk.
boot: c
# default config interface is textconfig.
config_interface: textconfig
#config_interface: wx
#display_library: x
# other choices: win32 sdl wx carbon amigaos beos macintosh nogui rfb term svga
# where do we send log messages?
log: bochsout.txt
sb16: enabled=1
# disable the mouse, since DLX is text only
mouse: enabled=1
# enable key mapping, using US layout as default.
#
# NOTE: In Bochs 1.4, keyboard mapping is only 100% implemented on X windows.
# However, the key mapping tables are used in the paste function, so
# in the DLX Linux example I'm enabling keyboard_mapping so that paste
# will work. Cut&Paste is currently implemented on win32 and X windows only.
#keyboard_mapping: enabled=1, map=$BXSHARE/keymaps/x11-pc-us.map
#keyboard_mapping: enabled=1, map=$BXSHARE/keymaps/x11-pc-fr.map
#keyboard_mapping: enabled=1, map=$BXSHARE/keymaps/x11-pc-de.map
#keyboard_mapping: enabled=1, map=$BXSHARE/keymaps/x11-pc-es.map
there any help how i can make config for note 3
sorry for my bad english
you renamed c.img to xp here
ata0-master: type=disk, path="xp"
#ata0-slave: type=disk, path="d.img"
ata1-master: type=disk, mode=vvfat, path=/sdcard/hdd, journal=vvfat.redolog
#type=cdrom, path="RUSW95B_USB.ISO", status=inserted
# choose the boot disk.
boot: c
Click to expand...
Click to collapse
... why ?
U should rename it back to c.img
ata0-master: type=disk, path="c.img"
#ata0-slave: type=disk, path="d.img"
ata1-master: type=disk, mode=vvfat, path=/sdcard/hdd, journal=vvfat.redolog
#type=cdrom, path="RUSW95B_USB.ISO", status=inserted
# choose the boot disk.
boot: c
Click to expand...
Click to collapse
and rename xp img you made to c.img and put it on SDcard/SDL/ (device storage not external) like this :
{
"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"
}
and you should be able to run it
tips :
Change ram to 512 or 1024 or even 1536
# how much memory the emulated machine will have
megs: 512
Click to expand...
Click to collapse
U can add files and folders to drive d:/ on win xp by copying them to sdcard/HDD
Reply if it worked or not
....
If its possible , can you uploud xp img cuz i tried w98 and it worked but it's very old

Heart Rate Sensor Problem

Hi guys, my heart rate monitor sensor is not working and the sensor doesn't even light up, which means it's not working AT ALL! And recently I even noticed Antutu and CPU-Z(Sensor Section) doesn't even detect it! (Screenshot below) What may be the cause of this?
Here is the logcat output of the BioSensor:
Code:
E/EnterpriseSharedDevicePolicy( 1132): isSharedDeviceEnabled
E/SensorService( 1132): Error activating sensor 18 (Operation not permitted)
E/SensorService( 1132): Error activating sensor 18 (Operation not permitted)
E/MaximBio( 1132): File Open Failed : /sys/class/sensors/hrm_sensor/led_current
E/MaximBio( 1132): File Open Failed : /sys/class/sensors/hrm_sensor/led_current2
E/MaximBio( 1132): File Open Failed : /sys/class/sensors/hrm_sensor/lib_ver
E/audio_hw_primary( 338): [MAXIM] setDSM_tx_Control()....dsm_enable : 0, dsm_opened : 1, adev->mode : 0
E/LocSvc_libulp( 1132): I/int ulp_msg_process_system_update(UlpSystemEvent): systemEvent:5
E/LocSvc_libulp( 1132): I/int ulp_msg_process_start_req(), at ulp state = 1
E/LocSvc_ApiV02( 1132): I/<--- void globalRespCb(locClientHandleType, uint32_t, locClientRespIndUnionType, void*) line 125 QMI_LOC_GET_BEST_AVAILABLE_POSITION_REQ_V02
E/LocSvc_libulp( 1132): I/int ulp_brain_process_zpp_position_report(loc_sess_status, LocPosTechMask, const UlpLocation*), report ZPP position to providers,report_position = 1
{
"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"
}
Was your heart rate monitor working before? Have you tried doing a hard factory reset to see if it will help?
DarkGuyver said:
Was your heart rate monitor working before? Have you tried doing a hard factory reset to see if it will help?
Click to expand...
Click to collapse
I didn't try the heart sensor before, never really gave it much thought...
Yes, I've tried to do a Hard Reset, I even flashed new firmware via Kies and made the Soft Reset (Take of the battery, press power btn for 1 min, yadayada) and it still doesn't work... I've uploaded a logcat check 1st post.
I'd take your phone to a Samsung Service Center and ask them to fix it for you. Or take it back to the retailer for repairs as it maybe faulty.
Btw did u get the solution b/c I have same problem

FTDI USB Serial Device converter now disconnected from ttyUSB2

{
"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"
}
---Setup---
1) We are evaluating using Raspberry Pi Compute Module CM3.
2) USB-HUB and USB-UART are boarded on the IO board.
3) USB-HUB is working in Self-power mode.
4) VBUS-detect of USB-HUB uses the same 3.3V power supply as CM3.
5) Two LTE modules are connected to USB-HUB via USB-SERIAL and each LTE module takes 2A
---Protocol---
AT commands
---Problem----
The LTE modules which are connected to USB-HUB are disconnecting.This problem occurs only sometimes not always
Following are kernel Logs.
Kerenl log:
19:47:58 raspberrypi kernel: [ 9301.001438] usb usb1-port1: disabled by hub (EMI?), re-enabling...
19:47:58 raspberrypi kernel: [ 9301.001457] usb 1-1: USB disconnect, device number 11
19:47:58 raspberrypi kernel: [ 9301.001463] usb 1-1.1: USB disconnect, device number 12
19:47:58 raspberrypi kernel: [ 9301.001668] ftdi_sio ttyUSB2: error from flowcontrol urb
19:47:58 raspberrypi kernel: [ 9301.001872] ftdi_sio ttyUSB2: FTDI USB Serial Device converter now disconnected from ttyUSB2
19:47:58 raspberrypi kernel: [ 9301.001906] ftdi_sio 1-1.1:1.0: device disconnected
19:47:58 raspberrypi kernel: [ 9301.002107] ftdi_sio ttyUSB3: error from flowcontrol urb
19:47:58 raspberrypi kernel: [ 9301.003371] ftdi_sio ttyUSB3: FTDI USB Serial Device converter now disconnected from ttyUSB3
19:47:58 raspberrypi kernel: [ 9301.003429] ftdi_sio 1-1.1:1.1: device disconnected
19:47:58 raspberrypi kernel: [ 9301.010150] ftdi_sio ttyUSB4: FTDI USB Serial Device converter now disconnected from ttyUSB4
19:47:58 raspberrypi kernel: [ 9301.010212] ftdi_sio 1-1.1:1.2: device disconnected
19:47:58 raspberrypi kernel: [ 9301.010430] ftdi_sio ttyUSB5: error from flowcontrol urb
19:47:58 raspberrypi kernel: [ 9301.018012] ftdi_sio ttyUSB5: FTDI USB Serial Device converter now disconnected from ttyUSB5
---Question---
Any investigation method and solution?

HELP!!!!! Android 11 fingerprint issue (beer bounty awarded)

Hi guys, I guess I'll keep it short and sweet, but I got my OP8 Pro back from repair and it came back wiped so naturally I yeeted OOS11 off it and flashed Pixel Experience, long story short I got to fingerprint enrollment, and whilst it doesn't say enrollment failed, it will just flash when I scan my finger but it won't build my fingerprint on screen.. I flashed using the instructions provided and reflashed using the same instructions...
It doesn't look like the typical persist.img failure where it'll usually tell you the enrollment failed, has anyone run into this issue too? My bootloader is also unlocked, I've tried to flash the OOS vendor image however fastboot will respond with "fastboot: cannot find partition"
Ideas? Will send a beer over to anyone that can get to the bottom of this, cheers!
Edit: attached a screenshot, the sensor activates and I can touch it but it does nothing..
{
"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 took a look in logcat whilst opening the enrollment page - got this:
Code:
03-18 17:51:30.655 1208 1251 D [GF_HAL][FingerprintCore]: [enroll] Enroll.
03-18 17:51:30.655 1208 1251 I [GF_HAL][DelmarHalUtils]: [checkModuleVerions] modules(3) version match passed: 38fcd06_db26a93_caeef16_2020.05.20_11:40:00
03-18 17:51:30.655 1208 1251 E [GF_HAL][DelmarFingerprintCore]: [checkEnrollAuthReady] cali data not ready caliState=0x00000010
03-18 17:51:30.655 1208 1251 E [GF_HAL][FingerprintCore]: [enroll] exit. err=GF_ERROR_CALIBRATION_NOT_READY, errno=1094
03-18 17:51:30.656 1208 1251 E [email protected]: An unknown error returned from fingerprint vendor library: 1094
03-18 17:51:30.656 1250 1250 W FingerprintService: startEnroll failed, result=1
03-18 17:51:30.656 1250 1250 V BiometricStats: Enroll latency: 18
03-18 17:51:30.656 1250 1250 V BiometricStats: Error latency: -1
03-18 17:51:30.656 1250 1250 W BiometricStats: found a negative latency : -1
03-18 17:51:30.656 1250 1250 V BiometricStats: Enroll latency: 18
03-18 17:51:30.656 1250 1250 V BiometricStats: Error latency: -1
03-18 17:51:30.656 1250 1250 W BiometricStats: found a negative latency : -1
To be fair, it looks like a /persist issue. That being said my WiFi MAC addr and 5G work fine, I guess I may just need to calibrate the FP sensor within OOS.
Backup persist and modem files than try to go back to OOS. Let's see is it permanent or not? Are you flashed ready to use magisk boot images or as I remember that PixelExperience rom was supporting locking bootloader at custom rom. Did you tried to lock? Or attempt(flashed) anything to lock bootloader?

Categories

Resources