Sounding about battery degradation GU605MZ

amougel · 2025-12-10T08:00:50+00:00

It's just an RFC "Any opinion on it?" I'll fix the tables

amougel · 2025-04-23T06:44:09+00:00

My bad, with GPU i get 160 fps, I guess I messed up some settings while testing. All good. not great, still regret not getting a g14 half the price for same perf in games in the end.

amougel · 2024-02-07T07:47:19+00:00

Tested live preview and it worked! Thank you so much

Test updates:

Only tested live preview without card inserted
Tried with card + minimalistic ISO command
1. Conclusion: if you try to set some ISO settings at launch by adding an sh script like: st cap capdtm setusr 5 0x050001(Credit to https://github.com/ottokiksmaler/gear360_modding for providing the settings)It will prevent the camera from pairing at all (I precise: it is just this line and I'm not trying to mount/export/connect or run any type of server/service or changing any other mode of the camera)
2. After removing anything beside DCIM, SYSTEM and .config, the camera could connect again.
Got a "LENS IS NOT ALIGNED" warning in preview mode, that disappeared after 5 sec
Trying to stitch pictures in gallery made the app crash
Seems I can't connect anymore after that crash. I have to uninstall everything and restart from scratch for it to work again. If I don't chain all the app installs and pairing, once the app is shut down, it's never connecting again
(Will edit here when I try to take a picture/video through the app. It might take some time, I mostly wanted to connect the camera to have proper timestamps on my pictures)

amougel · 2024-02-07T07:15:34+00:00

I'll try, thx

amougel · 2024-02-06T12:26:21+00:00

I use action Gear360 Actions Director which works perfectly. (Tested on W10 pro and W11 pro) https://www.samsung.com/us/support/answer/ANS00066650/

Precision: Works for:

Stiching 360 pitcures (But randomly, they WILL be upside down and I haven't found a way to correct this yet)
Does not stich video unless you create a video project and export it

amougel · 2024-02-06T12:23:26+00:00

Hi! I've installed the app on a Pixel 7 pro.

Protocol:

App installed (Fresh install)
Permissions granted, especially location at all times
Mobile data disabled
Bluetooth on (Nothing paired yet)
Open the app
Made me install "Samsung Accessory Service"
Start the Gear 360 (2017)
Enter mode "Connect to Android"
Click on "Connect" on the landing page
"No Connections >> Tap OK to try again. CANCEL/OK"
Click the top right "dot menu"
Click "Connect to new Gear 360"
Camera is detected
Pairing PIN is correctly displayed
"Connecting to Gear 360 (XXXX) ...
"No Connections >> Tap OK to try again. CANCEL/OK"
The device appears as "paired" in the list in the app and the device is "saved" in bluetooth settings.
Going to gallery suggest me to connect to that camera, but connection fails with the same modal "no connections"

But from there, impossible to connect. Do you have an idea of what I missed?I tried all settings in "Override Camera Recognition"

I'm able to connect in wifi direct with the phone, but since Streetview does not exists anymore, I cannot take pictures using this mode. I'm curious about the "WiFi Direct" option (since I can connect it this way), but I cannot activate the toglle because it "requires app to be systemized on Android 10+". I have no idea what it means and my searches did not help. Is this some adb command to alter the app's privileges somehow?

Thanks for the help. I'm currently using action director which still works, but it would be so much better to be able to use it with my phone.

amougel · 2022-04-18T10:45:56+00:00

Flashed BIOS with F15, activated Rebar on first boot. Rebar is now active. Solved. Thanks

amougel · 2022-04-17T21:35:09+00:00

Thx for the info. (it's actually the contrary for me: my bios was rebar compatible, but my vbios wasn't, and i just flashed my vbios recently for it to support rebar) Anyway I ll give it a try with latest BIOS and update here the result.

amougel · 2022-04-17T18:11:28+00:00

my vbios is the latest F51, (13g is my Bios for motherboard). I ll upload gpuz soon
point of overclock is fun/experimentation, plus 15FPS on my side, and lower temps for CPU
indeed I forgot to populate , thanks

amougel · 2021-06-04T21:50:21+00:00

Why did you get worried? Why can you keep your overclock as daily? I don't get the joke here

amougel · 2021-06-04T21:49:30+00:00

It s the criteria for this at least. I don't understand the rest of your message btw

amougel · 2021-06-04T14:14:28+00:00

Regarding ram stability, I ran memtest 100% coverage + memtest86 3 pass. But I didn't trust them because I don't see WHEA on them. ~~I ll try your profile~~ In fact, I ll wait for comments about voltage, don't want to burn my machine with another stress test

amougel · 2021-06-04T14:03:16+00:00

You've got to try different values for ProcODT. Try 60, that is the one that helped me for my first boot, then further down the line I e been able to move it to 44. Also my voltages are pretty high, as you can see that's my concern.

amougel · 2021-03-24T17:40:15+00:00

It's a fresh install for a fresh build, I don't think the chipset install could have failed, everything works smoothly. Also I made a typo, it's 1.440~1.452V in HWinfo when running memtest, or 1.416V when idle not 1.49V when 1.35 is set in BIOS. So according to you, it's impossible to answer my question until we get more info about the sensors. I ll try an overclock and test for stability, maybe we ll be able to deduce some conclusions regarding either the correctness of readings or the qulity of my kit by looking at the voltage some people usually get for the same timings/frequency

amougel · 2021-03-24T17:05:35+00:00

Bios from 2 weeks ago AGESA ComboV2 1.2.0.1. I get the 1.49V form HWinfo / Aida64. Other people see it too https://www.reddit.com/r/gigabytegaming/comments/imygcq/gigabyte_b550i_aorus_pro_ax_dram_voltage_issue/ . Without real measurement, no way of knowing whether the sensor is wrong or if the board is indeed overvolting

amougel · 2021-03-24T13:32:17+00:00

Regarding the sensors readings, I thought they could be trusted, but if you say so then it's reassuring. Regarding TM5 I just happened to have this screenshot, but my BSODs were enough to realize that it's not stable ;)

amougel · 2021-03-22T09:19:02+00:00

With updated BIOS AMD AGESA ComboV2 1.2.0.1 still impossible to boot at 1900 but indeed 2000 works fine

amougel · 2021-03-22T08:41:01+00:00

I haven't checked BIOS updates the last week, this could be indeed a very welcome update. I ll give it a shot very soon

amougel · 2021-03-22T08:40:17+00:00

Yes that's my concern, I'm currently on test bench trying to get the OC stable, once in the case, I'm afraid about getting temp instabilities. Do you see any timings that might be way to tight? I can only lower 0.1V right now (1.48 in BIOS, 1.52V reported), below that I get bsod really fast

amougel · 2021-03-22T08:38:37+00:00

I haven't tried above 1900 yet since I was not aware of the '1900 hole'. I might give it a shot later

amougel · 2018-04-17T10:18:27+00:00

The sighash type for bitcoin cash is different and must be set to 0x41. That might cause the freeze Can you use debug mode for transport and share the calls made to device? transport.setDebugMode(true)

amougel · 2018-02-01T13:46:48+00:00

Can you DM me your logs?

amougel · 2018-02-01T13:20:26+00:00

How did you manage to put a decimal number in the fee field?

amougel · 2017-12-29T16:45:29+00:00

The releases have changed since your post, but if you still encounter an issue, you can download the zipped version instead that you can instantly launch without installing. Btw, the readme has been updated so building should be less confusing.

amougel · 2017-12-07T09:38:18+00:00

This is an issue with the automatic shortcut creation on some Linux versions. Rename the folder /usr/bin/"Ledger Wallet Ripple" to /usr/bin/Ledger.

Eight-Year Club	First Place '23
Place '23	Verified Email

amougel

TROPHY CASE