It seems to be working alright without gapps and the recovery is non-functional in this build but otherwise is cpu hotplug is enabled on the Android 10 build because i'm getting much better battery life than on pie. I am currently using it on my phone and it's fine for light usage.
Maybe there is something to do with the CPU governor, it is using PegasusQ. CPU Hotplug is disabled.
Hi Lee
Recently a friend of mine flashed your ROM on his GT-N7000 he was using the stock ROM and the ROM installed perfectly fine but then after the phone booted a lot of apps kept crashing so he decided to go back to stock ROM with Odin and in the stock ROM it exhibited the same issue and now it is unusable every second apps keep crashing and then the phone freezes and automatically reboots and gets stuck on Samsung logo for about 20 minutes. Is there a way to fix this.
Sent from my LG Nexus 5x using XDA-Developers Legacy app
Recently a friend of mine flashed your ROM on his GT-N7000 he was using the stock ROM and the ROM installed perfectly fine but then after the phone booted a lot of apps kept crashing so he decided to go back to stock ROM with Odin and in the stock ROM it exhibited the same issue and now it is unusable every second apps keep crashing and then the phone freezes and automatically reboots and gets stuck on Samsung logo for about 20 minutes. Is there a way to fix this.
Sent from my LG Nexus 5x using XDA-Developers Legacy app
Even Q runs on Note 1!
Hi Argood. Just wanted you to know... Android 10 runs on Note 1.
Hi Argood. Just wanted you to know... Android 10 runs on Note 1.
Attachments
Tested POSP ROM is not stable. To many crashes.
How can I start the recovery mode because this ROM doesn't support it?
Via ADB shell or Buttons it's not more possible.
Last edited:
I know that I posted this a few days ago. Also it is extremely unstable and has broken recovery, Ril, GPS and abnormal standby battery drain. So , I think Pie will the last custom rom our beloved galaxynote wI'll be getting.
---------- Post added at 02:31 PM ---------- Previous post was at 02:29 PM ----------
You will need to flash a recovery using odin and you will be able to go to recovery. It will make this ROM unbootable if you do so.
Last edited:
Recovery
I use TWRP and it works. ROM boots and I can go into recovery using buttons.....
This doesn't work on my phone. If I try to go to recovery it will boot into OS instead of it.
Thx for your help. I flashed TWRP via ODIN and Lee's ROM via TWRP and it works stable again.
This is interesting! I was still running an old version (some time 2019) and having random reboots since August and since a few days also RIL is crashing. I came back here to see if a new version fixes these problems. I am also running microG setup (without Magisk). So maybe there was some update in the Google Apps (even via PlayStore) which causes these issues? Or just my eMMC giving up...
So you are running a 2019 build and the RIL is crashing too?
And did you turn off low_ram config? Because it actually makes the reboot more frequent on my side. It have been 3 days without reboot on my side compared to last time where it will reboot at least once everyday.
Really hope it's a problem with the ROM so that I can fix it...
At least it shows an "x" near the reception. I did not change low_ram config. Further I can't see notifications any more since a few days.
So memory corruptions are likely, I guess? Maybe I should reinstall. Is it enough to boot to TWRP, wipe system and install lineageos zip to do so?
Yeah, you may try so. Or maybe there's something up with the microg.. we don't know too.
Normally for the RIL, if it shows no service then definitely is the RIL crashed. If it shows X then it should be no data or no internet.. isn't it?
Yeah data is deactivated. But when I enable it, it disables itself immediately. So I expect some crash to be happening...
One more clarification: Does the lineageos zip include the boot image as well or do I need to flash it separately?
That is interesting..... indeed looks like a crash.
Yes, every zip already includes a boot image. Just that the additional boot image is for those who perfers to have magisk patched kernel.
Hello folks.
Here is another bootimage that I hope could have fixed the RIL crashing issue.
Basically, what I did is that I revert the kernel back to lineage-16.0 branch from rinando and apply my changes on top of it. So this kernel has no lineage-17.1 commits (which I have been cherrypicking los17 commits to our los16 sources all the while). the cpu governor was configured to ondemand, so you should experience better battery life at the cost of having slower performance.
I just consulted rinando and seems like kernel shouldn't be a cause of the RIL issue unless there's upstream source changes related to binder (which imo is unlikely since it's already android 11 now). However who knows if the unrelated is related. So I just go ahead and rework the kernel from a fresh lineage-16.0 branch from i9100.
I seriously don't know what went wrong since I almost reverted all lineage-17.1 changes on my side
Sorry folks, my capability is not enough ._. but I will try my best to resolve this.
So far it's already 9 hours on my side. If the RIL is up for 3 days, we are good to go. This kernel is magisk-patched and there's only magisk patched. You are fine to use even if you don't use magisk.
Here is another bootimage that I hope could have fixed the RIL crashing issue.
Basically, what I did is that I revert the kernel back to lineage-16.0 branch from rinando and apply my changes on top of it. So this kernel has no lineage-17.1 commits (which I have been cherrypicking los17 commits to our los16 sources all the while). the cpu governor was configured to ondemand, so you should experience better battery life at the cost of having slower performance.
I just consulted rinando and seems like kernel shouldn't be a cause of the RIL issue unless there's upstream source changes related to binder (which imo is unlikely since it's already android 11 now). However who knows if the unrelated is related. So I just go ahead and rework the kernel from a fresh lineage-16.0 branch from i9100.
I seriously don't know what went wrong since I almost reverted all lineage-17.1 changes on my side
Sorry folks, my capability is not enough ._. but I will try my best to resolve this. So far it's already 9 hours on my side. If the RIL is up for 3 days, we are good to go. This kernel is magisk-patched and there's only magisk patched. You are fine to use even if you don't use magisk.
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone