@Encrypted11
to be really honest, this phone is really not targeted at users who just want to purchase and use the phone out of the box.(my 2 cents) Running Cyanogen already "staple" the "more technical" tag to the device.
So users shld understand that some bugs around are inevitable.
Even apps have bugs less OS..
I'm actually running stock root and I have not faced any random shut down for the half year i'm using the device. What is the logic to reboot everyday? I only do so when modules updates requires to. My current uptime is 160+ hours.. No idea when the longest was, never cared.
on screen keys not working is largely due to the touchscreen drivers.
i believe it has been rectified..
Hi. I'm not new to Cyanogenmod. Been using it on various devices and just the experience on the OPO breaks it. Been using it since the S3 days and also used one of the most upvoted budget phones on Amazon (and I'm the top reviewer). Milestone builds, nightlies, used them all.
Never had long standing issues like random reboots that were carried over from build to build, milestone to milestone. Ever. Yes, updates tend to fix something and break something at the same time but I've never experienced anything this bad.
If you'd look at
CM's JIRA bug tracker, the issue's been pretty upvoted and rampant on devices of a number of users and tagged with many event logs till date. If it doesn't affect you, doesn't mean it doesn't affect others. XDA, OPO Forums, CM JIRA, you name it, they all have traces of this issue.
Worst of all for mine, it only started random reboots after 44S. On the rebooting point, I never had to do so on 38R fyi.
On the touchscreen, its fixed. No ghost swipes at all.. Its just the on screen AOSP style navigational keys are used, the hold back key to quit app feature is not working at least.