I’m also in brax.me-who would I contact there about a replacement? That is how I got the log files to Plamen.
Email [email protected]
ok-I will look into this!
I will backup my settings to my other BraX3 phone and then reset this one and see if it continues to restart. If it does then I will put in for a replacement. That could be 9 months again to wait?!
Ask in the email, probably not as they should have devices ready and there is more experience with shipping.
1 Like
Last night I started working on my old Sony Xperia and reset that one to iode 6.11. Then I started moving my first BraX3 settings over to it. I plan on doing a seedvault backup on my second BraX3 while on iode 6.9 so that if updates mess it up I have a restore point.
So back to my first rebooting BraX3. Why do u think I may have hardware issues-was there something in those log files to indicate that?
I am hoping that it will get stable again by resetting the OS!
Lazarus
Since you have 2 phones you can know whether they behave differently.
Android is even more stable than regular Linux because the apps run into virtual machines, so having reboots is very concerning, probably the dmesg could show more but it’s not your business doing the debugging except if keep this unstable device for this reason.
Also nobody has reported this behaviour, I had 2 spontaneous reboots but nothing else.
Ok-no reboots today. Uptime on my first rebooting BraX3 is 23 1/2 hours. I will do the same 2 diagnoses on my other BraX3.
BTW, I used to always root my phones and rooted iodé a couple years ago with magisk. I had to flash in their recovery. I found directions in the iodé forums. Since then I have heard rooted phones are a security vulnerability so I stick to no root. But that is a way to see dmesg!
Rooting is done either for development purposes or to flash an OS, then you unroot it again else the OS can be modified by apps or other attacks.
1 Like
Wow-apps can even modify your phone if it is rooted? I liked it because I ran a firewall that used iptables and didn’t need to reside in the 1 VPN slot that Android gives u. That is why I stuck with iode’ because they have their firewall blocker that doesn’t need your VPN slot.
Also, iode’ didn’t used to use the lineage OS recovery. I’m not sure rooting is possible now with the lineage OS recovery.
I’ve seen this happen a couple times myself, so I’ll be watching to see what comes of this. Not super important to me, but I still look forward to a fix.
I’m not going to root the BraX3.
FWIW not trying to talk you into it but mine is rooted and it’s super easy with the brax3 and the spflash tool to root, unroot, and install OS updates without losing data.
1 Like
So it is still possible!
Since updating to iode 7.1 I’ve noticed random reboots. The last one happened yesterday around 2:30 pm. I went a little over 3 days since the former reboot. For me it is totally random. Never had random reboots with the previous versions of iode.
1 Like
Just to clarify, you don’t need to root the device to update the OS via spflash without using user data.
Right. My point was that rooting and unrooting are easy, and rooting doesn’t make updating hard. I didn’t state it as precisely as I could have.
Back on topic, yesterday my phone got super bogged down for some reason to where it would become unresponsive for 10-15 seconds, respond to a couple gestures, go unresponsive again, and on and on for like 10 minutes. I tried killing things like System UI since it said it wasn’t responding but it never cleared up. I eventually held the power button to force reboot it. I wonder if whatever was happening with my phone is what leads to the random reboots.
1 Like
It is starting to look like I am not alone with spontaneous reboots and strange behavior in iode’ 7.1! What I’m hoping clears it up is a reset of the OS which is what I did almost 2 days ago after backing up my information with seed vault.
So I didn’t restore my information yet as I want my refreshed phone to go for a week without rebooting before doing that. Maybe going from 6.x to 7.x needed a fresh start?
What I also did was transfer all my settings to an old phone so I will use that for a week before making BraX 3 my daily again!
2 Likes
Not to rub salt into anyone’s wounds, but I’m still running iodeOS 6.9, waiting for the dust to settle. Hopefully, others will, in the future, not be so quick to jump on new iodeOS updates that are initiated by updates to LineageOS, initiated by updates to Android. In my opinion, there are just too many parties involved to ensure that a new iodeOS fork of a new LineageOS fork of a new release of Android will not suffer unexpected issues.
Call me selfish, but I’d rather wait for the next update of iodeOS, or perhaps a later update still. That said, my hat’s off to the LineageOS and iodeOS teams for all that has been accomplished with getting iodeOS to do what it is intended to do on the Brax3, having cleared so many hurdles. I have confidence that they will continue to fix reported bugs despite the complexities. We just have to WAIT for stable updates. 
There are no stable versions in that respect. The device plays a major role in unexpected bugs and not all problems appear to all users, every update has some inherent risk to break something. What you could do is to wait the release of iodéOS 8(Android 17) and choose the less problematic 7.x version to install.
1 Like