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
Related
I have currently developed 90% of my app, and i need help at the last part.
I want to thange the default database path to another user spezified path.
i get an error when i try this:
Code:
String myPath = "/data/data/com.android.providers.settings/databases/settings";
SQLiteDatabase myDB = SQLiteDatabase.openDatabase(myPath, null,SQLiteDatabase.OPEN_READWRITE);
The Debug monitor shows:
Code:
FATAL EXCEPTION: main
android.database.sqlite.SQLiteException: unable to open database file
i hope someone here can help me
It can't open it because it's not there.
You need to create the DB in that "settings" subdirectory. Or you can just use adb shell and copy the DB to .../settings.
the database exists, found with root explorer
when i want to acces the database with:
SQLiteDatabase myDB = set.this.openOrCreateDatabase("/data/data/com.android.providers.settings/databases/settings.db", MODE_PRIVATE, null);
it says, unable to open file, that means that the database not exists, but there is one, please, thats the last part, i need help
ilendemli said:
Code:
String myPath = "/data/data/com.android.providers.settings/databases/settings";
SQLiteDatabase myDB = SQLiteDatabase.openDatabase(myPath, null,SQLiteDatabase.OPEN_READWRITE);
Click to expand...
Click to collapse
Didn't you forget the ".db" at the end of /data/data/com.android.providers.settings/databases/settings ?
tryed with db and without db, the same problem:
Code:
SQLiteDatabase myDB = set.this.openOrCreateDatabase("/data/data/com.android.providers.settings/databases/settings.db", MODE_PRIVATE, null);
What does the Debug monitor shows when you do openOrCreateDatabase ? (can't be "unable to open database", if it were it would create it)
I am catching the Exception and showing the error as toast message,
at the debugger there is this error:
Database: sqlite3_open_v2("/data/data/com.android.providers.settings/settings.db", &handle, 6, NULL) failed
According to this link :http://www.sqlite.org/c3ref/open.html, you should be able to execute sqlite3_errmsg to have a description of the error.
But I have to admit that I don't know if you can do that easily with the SDK :/ I don't really know how it handles errors in this case (cause "failed" isn't really speaking to me ^^)
Edit : Hey, I just spotted something ! You missed your shot in writing the path to settings.db !
You wrote : /data/data/com.android.providers.settings/settings.db
It is : /data/data/com.android.providers.settings/databases/settings.db
I tryed it.. annd.... the same error..
if i try:
Code:
SQLiteDatabase myDB = set.this.openOrCreateDatabase("/data/data/com.android.providers.settings/databases/settings.db", MODE_PRIVATE, null);
it should normally create a new database at the dir.
when i type /data/data/.file/settings.db
there will be created the database, but at com.android.providers.settings/databases/ or all other com.* folders, it haves no permission.. :/
Try to add WRITE_SECURE_SETTINGS permission to your manifest then. Perhaps it will unlock it
Code:
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE"/>
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.CHANGE_WIFI_STATE" />
<uses-permission android:name="android.permission.WRITE_SETTINGS" />
<uses-permission android:name="android.permission.WRITE_SECURE_SETTINGS"/>
alot of permissions xD i will try it
€: nope, no permission.
Well, I think I've reached my limit ^^
I'll go with the "If you don't have and can't have the permission to touch it, then don't" and try to find an API that do the things you want.
BTW, can you explain what you want to do with this DB ?
i want to change "wifi_http_proxy" and "wifi_http_port"
Are you sure that these fields even exist ?
I can find http_proxy, but no wifi_http_proxy nor wifi_http_port :/
which android do you have? 2.1? or 2.2?
2.2, but I'm using the official SDK website as a reference (and Google, obviously ^^)
can you change proxy settings manually?
Virtual Device:
{
"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"
}
My Phone:
Yes, I have the same screen as yours (2nd one).
hmm.. have you ever tryed to change the settings? try it to change, and then open the database /data/data/com.android.providers.settings/databases/settings.db -> system and then look for "wifi_http_proxy" and "wifi_http_port"
I'll try it once I get home. I'm at work now, and they locked the possibility to connect something with USB :/
I'll tell you what I'll see.
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.
Hello everyone,
I have start my first app, with this app, can you count your small change. And It works fine.
But, the fields must have a number, otherwise will my app cras.
Is there a solution to fix this? I mean if the user no number set on a row, that the app see this as a zero?
This looks my app:
{
"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"
}
this is the code what i use, it is maby not perfect but I am a beginner.
Code:
Button btn_optellen = (Button) findViewById(R.id.btn_optellen);
btn_optellen.setOnClickListener(new OnClickListener() {
@Override
public void onClick(View v) {
double een = Double.valueOf(txt_001.getText().toString());
double twee = Double.valueOf(txt_002.getText().toString());
double total_een = een * 0.01 ;
double total_twee = twee * 0.02 ;
double totaal = total_een + total_twee;
tt_001.setText(String.format("= €%.2f", total_een ));
tt_002.setText(String.format("= €%.2f", total_twee ));
tt_totaal.setText(String.format("= €%.2f", totaal));
After you write the values to een and twee, you should do a check if they are null. And if that check is true, then set the value to 0.
So to be precise: do this check just before the line
double total_een = een * 0.01;
Click to expand...
Click to collapse
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
Recovery: TWRP 2.8.2.0
Thanxs for your answer.
I hope I don't ask to muts. But I am ana beginner. Can your show how I must write it?
Ok so i just researched a bit and found out that if the string to parse is invalid, then there is an exception thrown immediately. I thought that just null would be returned, so we need a different approach. But here os how to do it:
Code:
Button btn_optellen = (Button) findViewById(R.id.btn_optellen);
btn_optellen.setOnClickListener(new OnClickListener() {
@Override
public void onClick(View v) {
//we should initialize the two doubles to 0, so that we can just leave it like this in case of an error
double een = 0;
double twee = 0;
try {
een = Double.valueOf(txt_001.getText()); //btw, you dont need to call toString() after getText(). That method already returns a string so doing this would be redundant
} catch (Exception e) {} //nothing has to be done here, because the double has already been initialised to be 0
//same here
try {
twee = Double.valueOf(txt_002.getText());
} catch (Exception e) {}
//so now the two doubles are either set to 0 or to the value entered by the user, if it was a correct number
double total_een = een * 0.01 ;
double total_twee = twee * 0.02 ;
double totaal = total_een + total_twee;
tt_001.setText(String.format("= €%.2f", total_een ));
tt_002.setText(String.format("= €%.2f", total_twee ));
tt_totaal.setText(String.format("= €%.2f", totaal));
--------------------
Phone: Nexus 4
OS: rooted Lollipop LRX21T
Bootloader: unlocked
Recovery: TWRP 2.8.2.0
Very muth thanx, I am going try it out.
I was wondering if someone could help me with settings to use in the Dose Config Settings in the OmniGears menu to replace the Forcedoze app.
Is it possible to force Omni to doze by using some more agressive settings in the Dose Config, so Omni would go into deep sleep after switching the screen off and not looking to the sensors?
And when the answer is yes, what settings are preferabele then?
You have to use another kernel then default for this because you have to block the wakelock sensor_SMD for this with EX kernel manager (or another kernel manager ofcourse).
Unfortunately it is not possible to block wakelocks with the default Omnirom kernel so I am using Mady's Xtended Kernel for this in combination with the following doze settings in the OmniGears doze menu:
light_after_inactive_to = 0
light_pre_idle_to = 0
light_idle_to = 0
inactive_to = 10
sensing_to = 0
locating_to = 0
motion_inactive_to = 0
idle_after_inactive_to = 0
idle_pending_to = 30
idle_to = 1800
{
"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"
}
Jan_L said:
You have to use another kernel then default for this because you have to block the wakelock sensor_SMD for this with EX kernel manager (or another kernel manager ofcourse).
Unfortunately it is not possible to block wakelocks with the default Omnirom kernel so I am using Mady's Xtended Kernel for this in combination with the following doze settings in the OmniGears doze menu:
light_after_inactive_to = 0
light_pre_idle_to = 0
light_idle_to = 0
inactive_to = 10
sensing_to = 0
locating_to = 0
motion_inactive_to = 0
idle_after_inactive_to = 0
idle_pending_to = 30
idle_to = 1800
Click to expand...
Click to collapse
so I can change the values, but it has no effect, if i use the offical omni with his own kernel?
Master_TC said:
so I can change the values, but it has no effect, if i use the offical omni with his own kernel?
Click to expand...
Click to collapse
When the motion sensor is active, the device will come out of deep sleep.
Because in the mean time I have switched a lot in ROM's and kernels, I am using Forcedoze now again, but indeed, another kernel with wakelock blocking would do the job.
I would suggest HolyDragon kernel or Luiskernel, both are very good. Drain of Luiskernel is the lowest I could find until now (even better then Mady's).
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?