I'm using the Rom only for test purposes, cause
android auto is still not working.
android auto is still not working.
I still using this rom daily for my 2nd phone. And if there's any improvement in the future, I'll be happy. so far it's quite reliableHi all,
in the short period I'll be very tight on schedule so I was wondering which project maintain and which pause. So I'll be very glad to know how much people actually use this ROM and in which capacity (daily, tried and waiting for improvement, not interested) so that I can focus my very little time on a specific project and not wasting it.
Let me know!
Thanks
I haven't used it for a while now.. Tested it but as soon as the number of installed apps increases, random reboots become more frequent.Hi all,
in the short period I'll be very tight on schedule so I was wondering which project maintain and which pause. So I'll be very glad to know how much people actually use this ROM and in which capacity (daily, tried and waiting for improvement, not interested) so that I can focus my very little time on a specific project and not wasting it.
Let me know!
Thanks
Hey, so I've been testing this for almost 23 hours now, and that trick seems to be working. I have had no reboots, almost 70 apps installed, and its working great. It does stutter here and there once in a while (I noticed this when installing my apps after logging into my google account), but the battery life is the same, no overheating, pretty much everything works. Great work dude..Hi all,
thank you for partecipating to the poll. I've decided to continue to work on this and, thanks also to @dslul that have pointed me in the right direction, I think I've found a way to fix (hopefully) the random reboots.
I've uploaded a new build, that I'm also testing on my device, and with 50+ app installed and same old usage I'm at 40+ hours uptime without a single reboot. The room happened to hang a couple of time but it recover nicely after just a couple of seconds.
Now if someone else would test I would remember that is an experimental fix that relies of a little overvoltage for the big core in the latest frequency; that been said it's pretty stable here and also I've far less overheating that with the last build without fix.
Happy testing and let me know!
Thanks for the feedback. Quick question: are you using the default launcher? Here I use the Nexus launcher, installed directly with gapps, and the stutter is way better. Quickstep is a little funky in this build and I think is the patch for the removal of the search bar.Hey, so I've been testing this for almost 23 hours now, and that trick seems to be working. I have had no reboots, almost 70 apps installed, and its working great. It does stutter here and there once in a while (I noticed this when installing my apps after logging into my google account), but the battery life is the same, no overheating, pretty much everything works. Great work dude..
I was actually using quickstep. I just switched to Pixel Launcher R (using Quickstep), seems like its gone for now. Will report if this one does that too.Thanks for the feedback. Quick question: are you using the default launcher? Here I use the Nexus launcher, installed directly with gapps, and the stutter is way better. Quickstep is a little funky in this build and I think is the patch for the removal of the search bar.
Ok thanks. For me quickstep was a continuous crash but maybe the problem was on my side than. Other small question: have you flashed gapps? Which version if I may ask?I was actually using quickstep. I just switched to Pixel Launcher R (using Quickstep), seems like its gone for now. Will report if this one does that too.
Yep. Gapps are from September of 2019, nano package.Ok thanks. For me quickstep was a continuous crash but maybe the problem was on my side than. Other small question: have you flashed gapps? Which version if I may ask?
The undervolt patch was already in the default kernel tree but seems to not work with aosp. The overvolt one does instead.I compiled grapheneos with the undervolt patch and the system seems stable finally (for now)
Sorry, I meant underclock. Originally it was set to 1.9 instead of 1.8 for BIG cores. In 48h I didn't have a reboot (but my usage is really light, few apps and no gapps).The undervolt patch was already in the default kernel tree but seems to not work with aosp. The overvolt one does instead.
Also, I was thinking of start porting aex, have you a public repo for grapheneos or have you all only local?
Tethering and hotspot are always a source spot, o well we will see about that. I'd understood that you where talking about the underclock and that's the patch that I already add in my tree but that didn't do anything on my aosp build. This one seems a bit more stable. I actually had a reboot today during a call but passing from 2/3 a day to one every 72h (maybe less) it's a great improvement I think.Sorry, I meant underclock. Originally it was set to 1.9 instead of 1.8 for BIG cores. In 48h I didn't have a reboot (but my usage is really light, few apps and no gapps).
I went back to aosp since the SIM card sometimes is not detected with graphene, however I just added this file to the local_manifests folder (plus some adjustments in the build folder). It's not a complete port of course, partly because Sony doesn't allow to simply replace they avb keys.
The only issue I have ATM is that tethering and hotspot are broken (but weren't on omnirom).
What are you trying to boot into recovery? Because here boot into recovery works without problem. The first things that come to mind is reflash recovery using fastboot but that should not be necessary. Trying cannot hurt anyway.Can not boot into recovery mode to install Gapps " Because location not working in bitapps "
Any Fixes !?
![]()
TWRP Not working ..What are you trying to boot into recovery? Because here boot into recovery works without problem. The first things that come to mind is reflash recovery using fastboot but that should not be necessary. Trying cannot hurt anyway.
Okay so apart from hotspot, media cuts off until a reboot, like you won't be able to play any kind of media from the speakers or headphones(although BT may work). This has been a bug since kernel 4.4, so I don't know how fixable it is, but it's kind of an annoying bug.Tethering and hotspot are always a source spot, o well we will see about that.
Yep, the reboots are still present, but nowhere near as much as they were. Even I get a reboot once every two or three days, first one was when I was trying out different versions of gcam, second one was when I was shuffling between 5 or 6 apps (RAM management is great in this ROM), so they were open in the background. Other than that, this works pretty well. So basically heavy usage can result in a reboot. Also I don't know if this is a system or RAM issue or a kernel thing, but when using gcam with enhanced HDR or night sight or astrophotography, background apps just close. Just shows the age of the phone.I actually had a reboot today during a call but passing from 2/3 a day to one every 72h (maybe less) it's a great improvement I think
Thanks for the detailed review. Yes the phone is old and thing start to not work as well. I didn't use gcam so I cannot compare but overall the situation is better. Which version of gcam are you using?. I'm trying some other tweak to the kernel to see if I can remove reboots altogether. No promises thoOkay so apart from hotspot, media cuts off until a reboot, like you won't be able to play any kind of media from the speakers or headphones(although BT may work). This has been a bug since kernel 4.4, so I don't know how fixable it is, but it's kind of an annoying bug.
Yep, the reboots are still present, but nowhere near as much as they were. Even I get a reboot once every two or three days, first one was when I was trying out different versions of gcam, second one was when I was shuffling between 5 or 6 apps (RAM management is great in this ROM), so they were open in the background. Other than that, this works pretty well. So basically heavy usage can result in a reboot. Also I don't know if this is a system or RAM issue or a kernel thing, but when using gcam with enhanced HDR or night sight or astrophotography, background apps just close. Just shows the age of the phone.
Battery life is great once I set the minimum core frequencies to 400 MHz, even better than LOS 16, and I have set the max frequencies to 1401 and 1958 MHz respectively, but there's pretty much no difference in performance from the stock settings. Deep sleep is 93% for a discharge from 100 to 30% on an average according to Franco kernel manager. I also use Universal GMS doze in magisk, so that might be another reason for the good battery life. Anyways, Thanks for keeping working on this phone. Because to this ROM, I can skip buying a phone for another year.
What you mean with "twrp not working"? Which version? I'm using it and no problems (and I flash a lot because I'm testing new fixes". Also I'm using opengapps (mini or nano or Pico) and all of them works without any issue. Not even heard of anx camera so I don't know about that. Using stock here and other user have reported that gcam worksTWRP Not working ..
i switch to another recovery and install GApps Stock but location not working .. is any recommend fix ?
&
i try install anx camera more than 10 times but every time stuck at boot too .. ?
Gcam is DMGC 4.5 (based on 7.3). Arnova's 6.2 version used to work perfectly (with buffer fix) in previous builds (even shutter key), but for some reason 60 FPS videos now have green lines all over in that version. Shutter key doesn't work in version 7, other than that everything works.Thanks for the detailed review. Yes the phone is old and thing start to not work as well. I didn't use gcam so I cannot compare but overall the situation is better. Which version of gcam are you using?.
That's great! Also can the media bug be possibly fixed?I'm trying some other tweak to the kernel to see if I can remove reboots altogether. No promises tho![]()