Related
Hi, a few days ago my phone camera fault, I get a notice saying "error connecting to camera", so I did a logcat to see what happened but I honestly don't know how to read it and thus can not understand where is the reason for the problem so that's why I put this here so that any experienced user help me and tell me what is the problem... Here is the log http://pastebin.com/print.php?i=rXU9DwAc
Thanks for your time guys!
PS: the front camera and flashlight also don't work, I try flashing another rom but didn't work (CyanogenMod 10.1)
Well at face value, e.g. taking the error literally.. a bug caused a java error keeping the camera app from loading properly. Specifically an empty string value that throws an exception.
Now you have to place that in a context. If it was a one time error.. don't worry about it. If it is repeatable, it could be a bug, conflict, corrupted install, et cetera. A logcat is just a detailed log of what the OS and drivers were doing to provide clues for troubleshooting. Do a search for the CM build you have and see if anyone else is having issues. If so, that suggests a bug. Otherwise you can try disabling other apps that may be conflicting.
You implied that this is a recent problem.. so corruption or a conflict seem more likely. Did this happen after a recent flash or installing a new app? If you flashed a new CM build, did you wipe the cache? If not, I'd suggest that you If not, consider reflashing your ROM, ensuring that you wipe the cache data to see if that resolves the issue. It seems odd if you had a stable configuration and reflashing doesn't resolve the issue.. at least temporarily. Look for a pattern or missed step, like not wiping the cache.
HTH
fffft said:
Well at face value, e.g. taking the error literally.. a bug caused a java error keeping the camera app from loading properly. Specifically an empty string value that throws an exception.
Now you have to place that in a context. If it was a one time error.. don't worry about it. If it is repeatable, it could be a bug, conflict, corrupted install, et cetera. A logcat is just a detailed log of what the OS and drivers were doing to provide clues for troubleshooting. Do a search for the CM build you have and see if anyone else is having issues. If so, that suggests a bug. Otherwise you can try disabling other apps that may be conflicting.
You implied that this is a recent problem.. so corruption or a conflict seem more likely. Did this happen after a recent flash or installing a new app? If you flashed a new CM build, did you wipe the cache? If not, I'd suggest that you If not, consider reflashing your ROM, ensuring that you wipe the cache data to see if that resolves the issue. It seems odd if you had a stable configuration and reflashing doesn't resolve the issue.. at least temporarily. Look for a pattern or missed step, like not wiping the cache.
HTH
Click to expand...
Click to collapse
Well none of those, I was on a stock rom (I flash a few tweaks for improve the net speed and things like that) and suddenly the camera error starts so I flash a cm rom for try to solve the problem but seems to not work ( I make all the wipes correctly)
martin_carpio17 said:
Well none of those, I was on a stock rom (I flash a few tweaks for improve the net speed and things like that) and suddenly the camera error starts so I flash a cm rom for try to solve the problem but seems to not work ( I make all the wipes correctly)
Click to expand...
Click to collapse
The essence of troubleshooting is looking for patterns.. which point us towards the ultimate cause of a problem. If I had a java error, the first thing I would try is simply rebooting the phone. If it continued, I would suspect a conflict (if I had recently installed an app or changed some settings). So.. try reversing those tweaks and see if that clears that error. Less common would be corruption.. and you might test that by flashing back to the same stock ROM if it was working fine before you saw the issue.
Flashing to a different CM ROM wouldn't be a first step. It might work. But you don't gain much knowledge if it doesn't as a new ROM introduces a host of new variables as well. If the cause of the issue is unclear, you want to confront the most obvious suspects first and try to change only one variable at a time. In your place, i'd go back to the stock ROM.. confirm that the camera works properly again. Then restore your tweaks one by one watching to see when the problem recurs.
Good luck
.
Intro
I don't mean this to be a thread for any specific ROM or problem, but rather a general guide that essentially eliminates all doubt of machine or user error (we all make mistakes). This is generally geared towards the issues users are experiencing when flashing an AOSP ROM, but can also apply to Sense, and even other devices. This covers from downloading a ROM forward, and also making sure that everything gets properly installed with no corners cut, so that everybody can be on the same page when a problem arises. I'm not trying to say anybody's way of doing things is wrong, but I've see a lot of people asking different questions that end up getting solved with the same few answers. This isn't a "how to flash" thread, but rather how to ensure you're getting your device in a clean, fresh state so that everybody can be on the same page when it comes to bugs, otherwise nobody is going to want to help you if you don't try to help yourself first.
I know this is on the longer side, so key points are underlined, with a TL;DR at the bottom
Downloading
Checksums or hashes are a great way to make sure that the *.zip or any other file you're downloading is not only the right one, but that it hasn't been corrupted or tampered in transfer (uploads or downloads). You'll probably need to install something to work with chescksums- personally I like the open-source HashCheck for Windows. It adds a "Checksums" tab to the right-click > Properties dialog that automatically calculates MD5 (most common) and SHA-1 (more advanced) hashes. I encourage anyone posting a file to also post the MD5 with it, for everybody's sake, since it only takes a few extra seconds to eliminate all doubt of a bad upload or download. HashCheck even gives an option to create a *.MD5 file, just like the ones you might get from goo.im. If you're on Linux, Android, or presumably Mac you can check a file's md5 by opening terminal and simply typing "md5sum <filename>" without the quotes. If a file is posted without an MD5, you can download it twice and check it against itself, but just keep in mind you're going to be hitting somebody's server twice as hard, so only do it if necessary. Now that you're sure you have the right files...
Wiping/Flashing
Most people know dirty flashing is at your own risk, and if you have a problem, the first thing anybody's going to tell you is to do a clean flash. No really, just clean flash- that's what backups are for, but that's a whole different topic. Unfortunately, most people consider a clean flash to be just a factory reset, but that only wipes dalvik, cache, and data (except your sdcard), while leaving the system partition intact. To do a proper clean flash you want to go into advanced and make sure that system gets wiped in addition to dalvik, cache, and data. I can't say exactly what (sorry), but there's lots of miscellaneous things that can persist between flashes, especially when you're going to a different ROM. For us DNA owners, there's still a lot of activity in our CM device tree, meaning that even on the same ROM, some of our device files may change between versions which will necessitate a wipe of system. Maybe it's just me, but it seems things go out of line more often on 4.3 so I just always wipe system now.
If you're here, you probably know how to flash a ROM, but always double check the OP or first few posts and see what gapps/settings/etc are recommended. I'm also going to remind you that it takes just a few extra seconds to create a *.md5 file with HashCheck that you can push to your device along with the *.zip and TWRP (probably CWM too) will check the file against it's MD5 before flashing it. After using the Setup Wizard to log in to your Google account, make sure that you uncheck the box to restore settings and data to your phone, otherwise those can cause problems. Now you can be sure that whatever is on your device is clean as can be and as the developer intended, otherwise you're probably not going to get much help.
Narrowing down the problem
Now that you've got a brand spanking new and clean ROM is the best time to try and narrow down a problem, but before you post anything, try the golden rule of IT- "Have you tried rebooting it yet?" Also, you can try booting to recovery to clear just dalvik and cache and/or repair permissions. This is the first time you should consider making a post about your problem, but please, please, please don't make a post that just says something like "Settings FCs." Posts like that don't tell anybody anything- the best thing you can do is pull a log (more on that in a second), and create a post in the appropriate thread which you can determine as follows: Start by seeing if the problem occurs with nothing installed besides the ROM and recommended gapps- do not restore any backups, install any apps, or flash any kernels, even if the OP recommends it. If you're having problems with Settings or any Google app, there's likely a conflict with the gapps package that should go away if you reflash only the ROM, otherwise it's a bug in the ROM itself. Either way, if you can reproduce a problem at this point you should post in the ROM thread. If you want to flash a custom kernel, only do so after you've verified the problem isn't with the ROM or gapps. Flash only the kernel, and if there's any problems after that, post them in thread you got the kernel from, not the ROM thread.
If you're having a problem with an app, once you've completed the above steps, install only that app without restoring any data. If you can't replicate the problem, there's likely an incompatibility any corresponding data you may have restored, and sorry, but there's not really anything you can do about that. If the problem occurs with a freshly installed app, first check the Play Store to see if other users are experiencing the same problem- there may just be something wrong with the app. If it only seems to be you having this problem with a clean install, the ROM thread is the best place to post, although keep in mind other users may not be familiar with app.
Pulling and posting logs
Even now, nobody is obligated to help you (you flashed that ROM at your own risk, remember?), but once you're at this point, you'll have a better chance at getting help. Try to include as much information as possible like what else you were doing, what screen you were on, what button you tried to press, etc. and if you can, try to see if you can replicate it. Like I mentioned above, posting a log is the best way to get help, and they're really easy to get. Not everybody is going to understand every line, but if you know what you're looking for, occasionally the log can tell the developer exactly what the problem is, and bam- easy fix.
First make sure USB Debugging is enabled in Developer Options (if you don't see Developer Options, go into About Phone and tap on the Build Number line 7 times), and make sure that Root Access is set to both Apps and ADB. Now as far as gathering these logs, SysLog is by far one of the easiest ways- download it, open it, and press "Take Log." It pop up a toast message saying that your logs are in /sdcard/SysLog/<DATE_TIME>.zip and it'll even give you the option to share it via email, Dropbox, or anything else you might use. Post that and you'll have even better chances of getting help. For simplicity, I'm not going to details on manually pulling logs, however if you're stuck in a bootloop or something like that and can't run the app, use "adb pull /proc/last_kmsg" and post a link to that file.
TL;DR
Sh*t happens, learn to deal with it or go back to stock
Verify your download with an MD5 Checksum
Wipe system in addition to factory reset (dalvik, cache, & data)
Flash ROM and gapps without installing anything else or restoring any data
Pull a log, it's really easy
Now is the best time to make a post about your problem
Radio/Reception Problems on the DNA?
First things first- Double check your settings in Settings > More > Mobile networks. They should be as follows:
Data Enabled: Yes
Data Roaming: No (unless you're actually roaming)
National Data Roaming: Yes (otherwise you'll probably lose data; this won't get you any roaming fees)
Network Mode (Verizon): LTE/CDMA/EvDO (or Global, which is everything, I've never noticed any difference between the two)
Network Mode (GSM): GSM/WCDMA preferred (depending on the ROM, you may also need to flash the GSM patch courtesy of Flyhalf205 from the 2nd post in the original CM10.1 thread.)
System Select/CDMA Roaming: Automatic
CDMA Subscription: RUIM/SIM
GSM users may also need to manually enter APN settings for your carrier to get things like MMS functioning properly. I'm not going to compile a worldwide list, but if Google fails you, your carrier should have support documentation with these settings. Recently, I noticed this file in the android source lists tons of APNs, so try finding your carrier in there too.
Why do I have 0-1 bars? I got a lot more on Sense
Don't be alarmed if your reception looks low/non-existent. Sense "pads" the signal bar to get it to show bars more "accurately," but AOSP does not, so expect a drop in bars. To get an accurate assessment, you want to be looking at your actual signal in dB before trying to diagnose anything by going to Settings > Interface > Status Bar and changing Signal Status Style to Text, and your signal bars will be replaced with a negative number, therefore a value closer to zero indicates a stronger signal. If you don't like negative numbers, another way of thinking about this is as if the phone was telling you how far you are away from the nearest tower. What would normally be 5 bars on Sense equates to -70dB, and 1 bar equates to -115, but these are approximate values and depending on your location and environment, you might bee numbers outside this range.
I'm still having problems
Unfortunately, our phone is known to have problems with reading the SIM card. Some say it's purely software, some say its purely hardware, but I believe it can be either. I'd first suggest giving your SIM card a cleaning by popping it out and gently rubbing the contacts with a clean rubber eraser, another more risky option is a just drop of isopropyl alcohol on a cotton swab. If you have compressed air, you can give that a small blast into the SIM slot from a few inches away. If the phone is still having issues with reading the SIM after that, it might need to be replaced.
Another possibility is issues with the radio firmware. You can try updating the firmware by following the instructions in this post. Personally, I recommend the most recent version, 2.06.605.1. Some users, myself included, have reported that sometimes a full RUU back to 100% stock is necessary to restore proper radio function. Instructions for that can be found here, but be aware that this can be a lengthy, tedious process. You'll end up having to re-unlock and root your phone before you'll be able to flash anything else again, so I only recommend this as a last resort, but is nonetheless something to bear in mind.
Stickie this?
Sent from my HTC6435LVW using Tapatalk 4
I'm going to stick it for now, it's actually good basic info. But I am moving it to the Q&A forum.
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
pyroguysf said:
Thank you. I debated where to post this, but since this mainly applies to those of us who are flashing away from Sense, I thought it would get more attention with the development section, but I respect your decision to move it.
Click to expand...
Click to collapse
Yeah that makes sense, and I was hoping this would also cut down on unnecessary thread starts.
I think what I'll do is have this in both development forums as a sticky, hopefully this will help out some of the chefs.
If you edit one thread, be sure to edit the clone in the other forum.
I am going to let you clean this up as much as possible over the weekend, then maybe move it to the dev threads Monday as a polished product, see if you can get as much info as possible about GSM to include about the signal issues etc.
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
orangekid said:
Part of the issue is that a lot of the users who are guilty of saying "this is broken, fix it" with no logcat and not having wiped or installing some app that is causing the issue don't read stickies, but it's a good resource to have.
Click to expand...
Click to collapse
I've noticed this, but I made this in hopes of giving people a place to link back to rather than having to waste time typing out the same things over and over, which is why I also put the link in my sig.
orangekid said:
You might add something about restoring apps from TI or MyBackup and apps causing issues, or installing some root app and then having issues, a solution might be to wipe, then boot, then try to reproduce the issue, or uninstalling the app.
Also if you flash a different kernel, do not then go into the ROM thread and start saying something doesn't work, having installed a kernel that did not even come with the ROM and confusing the chef.
Click to expand...
Click to collapse
Good ideas. I'll try to add a section for apps when I get a chance. I tried to briefly touch on the kernel situation by saying to read the OP for recommended settings, but I'll definitely expand on that.
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
pyroguysf said:
OP edited for clarity/grammar and updated with information for apps and determining where to submit your post (e.g. ROM vs kernel thread). Second post updated with GSM info.
Click to expand...
Click to collapse
Sounds good.
Moved to dev forum.
If you want to go ahead and create the same thread and copy / paste the first 2 posts, I can sticky it.
I don't know if others are facing the similar problem but it has turned my life into hell after the new update. I will list down the issues on ALL ROMS after the new OOS 3 update with bootloader in my device.
I had issue in accessing storage, which means gallery, file explorer or literally any app crashes when I try to access from the storage, be it internal or external sd card.
Couldn't use the latest snapchat at all, can't post in story, can't save any snap, can't upload from camera roll. It was just a dead end. However I could only post into story with a older Snapchat version, still due to storage access issue, I couldn't save or upload from Camera Roll
Facebook picture upload would ocassionally crash the app.
Couldn't take more than 1 picture in latest youcam app, storage issue would crash the app.
Gallery apps fail to generate thumbnail previews.
All these above problems caused permanent storage access unavailability until I rebooted device.
Need to charge my device twice as Battery runs faster than Usain Bolt.
So finally after a lot of tingling, I finally downgraded my device to OOS 2.1.3 with TWRP 2.8.7. Trust me it's very stable, bug free and battery friendly. Though I miss the new security patches features and snappy feel from Android 6 & 7.
The above problems are not happening in 2.1.3. I can use latest snapchat, youcam & facebook without any issue at all. Is there any way to prevent these issues on new Android OS in my device ? I believe it's not a device issue as 2.1.3 is running very stable and bug less.
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Exodusche said:
Never had any of those issues on OOS 3 update. Think you might of gone wrong somewhere maybe.
Click to expand...
Click to collapse
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
arafat_mw said:
I am really eager to find that out. I have almost tried every ROM on the new bootloader. Except MOOS 2.0 or something, each and every ROM had this bug, even official OOS 3.1.4. Any idea what might went wrong ? The bugs are not reproducing in OOS 2.1.3 though. Which makes me believe that my device is ok.
Click to expand...
Click to collapse
Think I figured it out for you. You are on really old OOS2 build you need to flash 2.2.3 before you update to OOS3. It was made for the update to MM.
Are you sure you gave the good permission. On MM, when you first launch an app, it should ask you for it. Maybe a bug appear at one point.
You should go to menu settings / app / 3 dots menu at the top right an reset app prefs.
Then re open app one by one.
You can try first without your SD inside to see if it happens again.
PpPmod for Realme UI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
About PpPmod
PpPmod is a port of the excellent xXx NoLimits magisk ROM for Oxygen OS. It's a systemless modification to the default Realme UI that allows the user to get much more out of his device than the default configuration allows.
But why a magisk ROM?
For two reasons:
1. Realme devices offer good price to performance ratio, but in many cases they lack a developer community around them to build those ROMs the users want.
2. Realme UI is not that bad honestly. It offers good performance, it's not too crazy aesthetically and its bloatware isn't baked deep into the system.
It's also a much safer way to modify Mediatek devices. As long as you've managed to root your phone, you are good to go. If something goes wrong, just wipe data and no harm, no foul.
Supported devices
While in theory, any Realme device with Realme UI v1, Android 10 and a full HD screen resolution should be compatible, the only two devices this has been tested on are a Realme 6 and a Realme 6 Pro. For the curious, i own the later.
Ok, but what does it do?
- Port of xXx NoLimits for Oxygen OS
- Fully systemless Realme UI ROM mod for magisk
- Designed to work with all phones that run RealmeUI v1, Android 10 on full HD screens, including MTK ones
- Fully configurable installation, every component is optional
- Includes comprehensive debloating options
- Optional build.prop tweaks
- Many kernel tweaks that can be adjusted and combined, in order to target different degrees of performance and battery life
- 90hz/120hz for ALL apps when the display is set to its high refresh rate
- GMS Doze included
- Ability to disable analytics
- Ability to disable wakelocks
- Can enable full screen gestures (swipe up) for 3rd party launchers
- Ability to set custom bootanimations from a built in list, or as a user selected bootanimation.zip
- Includes extra launchers, sounds and icons from popular device brands like Pixel and OnePlus
- Gcams for both Qualcomm and Mediatek devices are included (by Urnyx and onFire)
- Youtube Vanced, detached from the playstore so no pesky updates can override it
- Google Dialer and Contacts, both old and new versions
- Custom density modes
- Ability to systemize apps
In order to set your own bootanimation, place a bootanimation.zip inside /sdcard/PpPmod. You can also place a shutdown/restart animation named rbootanimation.zip there. Make sure that your bootanimations are 1080 pixels in width, or they won't work as you'd expect. If you set option CustomBootAnimation to 1 in PpP.profile, your animations will be used during start up and/or reboot, instead of the default ones. For more information about the PpPmod folder and the PpP.profile file go to Installation Instructions.
If you want to systemize an app for whatever reason, just place the apk inside /sdcard/PpPmod/apps., before flashing.
Concerning debloating there is a master switch you should toggle if you want your individual options to work. Set IndividualDebloatSelection to 1.
Installation Instructions
You will find detailed installation instructions along with download links on post #3
Screenshots
For screenshots, press here
Thanks to:
xXx
ahmed_radaideh
dustintinsley
gloeyisk
k1ks
andip71
linuxct
Mostafa Wael
mrRobinson
osm0sis
rufus.wilson
snowwolf725
topjohnwu
Zackptg5
ZaneZam
Kevin Saiza
Tytydraco
XDA:DevDB Information
PpPmod, ROM for the Realme 6
Contributors
FatherJony
ROM OS Version: Android 10
ROM Firmware Required: RealmeUI
Version Information
Status: Stable
Current Stable Version: 1.1
Stable Release Date: 2020-09-14
Created 2020-09-03
Last Updated 2020-09-14
Changelog
Version 1.1
Fixed a bug where enabling HighRefreshRate had no effect on the first boot after installation.
Updated Google Dialer to the latest version.
Updated sqlite to the latest version.
Reworked kernel tweaks, with some inspiration from Ktweak by tytydraco.
New ReadAhead option added. This allows the user to disable, or set the readahead cache to a percentage of the device's memory. Default is 1 (cache disabled).
New CPUGovernorTweaks option added. When this is enabled, schedutil and interactive governor tunables are tweaked in order to increase performance. The default governor will also switch to schedutil or interactive depending on availability. Default is 1 (enabled).
Reworked CPUInputBoost option to make it more granular. You can now select from small, medium, high and max presets. For more info about them read the profile description.
Reworked CPUStuneBoost option to make it more granular. You can now select from small, medium, high and extreme presets. For more info about them read the profile description.
Installation
PpPmod allows for a fully customizable installation. The way this works is via a configuration file called PpP.profile. You will always be able to find the latest version of this file on this post. Make sure you edit this file on Notepad++ if you are opening it on Windows in order to preserve the Unix EOL format.
Requirements:
Realme UI v1 on Android 10 and display width of 1080 pixels
A working Magisk installation of v20.4 or higher
PpPmod should only be flashed via Magisk Manager
First time installation:
Place PpP.profile in /sdcard/PpPmod/ and edit it to personalize the installation to your liking
Flash the PpPmod zip via Magisk Manager
Reboot. Wait for at least a minute to let all installation options take effect.
Done
The first time you install, chances are that the PpPmod folder will not be in /sdcard, so you have to create it yourself. If you don't place PpP.profile there, the mod will be installed with the default options when you flash it and place the default PpP.profile inside /sdcard/PpPmod/.
Update to a newer version:
Open Magisk Manager and uninstall the previous version
Reboot
Wait for a couple of minutes after reboot as the uninstallation process can take some time
Install the newer version via Magisk Manager. Don't worry about changes to PpP.profile, they will be merged to your older version profile
Reboot. Wait for at least a minute to let all installation options take effect
Done
Uninstallation:
Press the waste bin icon next to the mod's name on the Magisk Manager
Reboot. Wait for a couple of minutes after reboot as the uninstallation process can take some time
Done
Downloads:
PpPmod v1.1
PpP.profile v2
PpPmod v1.0
PpP.profile v1
FAQ
Q: I just installed PpPmod and my phone has heated up and stutters, is this normal?
A: Yes, the installation process is fairly intense, and during the first boot following the installation, a lot of stuff happens in the background. Just let your phone settle for 10 minutes and it should be fine.
Q: I did all that and my phone still heats up, you liar!
A: Well, check your settings. PpPmod offers many options for tweaking, but not every one of them is suitable for all phones, or all usage patterns. In general, the higher performance settings may be fine for general usage and offer you a flagship like experience along with a high refresh rate, but will cause excessive heat and throttling during gaming.
For example, maybe a 12nm chipset shouldn't be pushed aggressively by enabling CPU boost options, especially if you game alot. You may gain a brief performance boost that will sooner or later be the cause of intense overheating, which will cause throttling, which will cause stutters. In short, try to be reasonable with your settings and expectations, PpPmod will not magically turn your mid range chipset into an SD865.
PpPmod is also not designed to work along with other magisk mods that adjust performance by altering kernel behavior. If you want to use such mods with it, try disabling every PpPmod performance setting, like:
KernelTweaks
LMK_RAM_Management
ReadAhead
DisablePeWq
DisableHotplugging
IncreaseMinGPUFreq
CPUGovernorTweaks
CPUStuneBoost
CPUInputBoost
The result may still not be ideal, but this is your best bet.
Q: My debloating options aren't working!
A: You forgot to set option IndividualDebloatSelection to 1.
Q: I think i found a bug, what is the best way to report it?
A: You should always include a detailed description of what triggers the bug, its effects, your specific phone model (including hardware characteristics like RAM and storage), firmware version, your PpP.profile and preferably a logcat from when the bug occurred.
Q: Can i be a beta tester? I swear i am awesome!
A: As long as you meet certain conditions, sure! The conditions are:
First and foremost, you must understand that beta testing doesn't mean early access. Most of the time you will have to do things that may be inconvenience you, or lead to loss of time and data (factory resets)
You should know at the very least how to setup and use adb
You should have A realme device with Android 10 and Realme UI v1
Q: Can i ask for a feature?
A: Sure, but keep in mind that PpPmod isn't primarily geared towards a specific device. So while device specific features are not out of the question, priority will be given to features that affect a range of devices.
Q: My phone isn't listed in supported devices, but it's a Realme device with Realme UI v1, Android 10 and a full HD resolution, should i give this a try?
A: Yes, as long as you don't mind resetting your data if something goes wrong, you should. That's exactly what i am trying to achieve with this mod. Normally, a new phone like for example the Realme X7 Pro would not have any options for customization on release, and may never get much due to the Mediatek soc. But PpPmod should work immediately, at least in theory. Even if there are some device specific issues i will do my best to fix them, and in the worst case scenario the phone is still safe from any permanent harm. Just reboot to recovery and reset data.
Q: PpPmod sucks and i wanna uninstall it. Must i also remove magisk?
A: NO, you don't have to and in fact you shouldn't if you don't have a reason unrelated to PpPmod, as magisk resides in your boot partition and thus unlike PpPmod, can mess with your device if you aren't careful.
Q: What does PpP mean?
A: No one knows fo sure. Some thik that it means Pro Plus Prime. Some other, less charitable persons claim it means PapaPowah instead. We may never know the truth.
Q: What do you plan for your next project?
A: Rewriting Android in Objective Cobol
Q: Is it true that you are actually a boomer?
A: Ok, that's enough. You guys have crossed the line and now i am forced to conclude this QA session.
FatherJony said:
Reserve
Click to expand...
Click to collapse
Good job dude
Does it work for RMX2001 Realme 6(india). I would assume it does as mentioned in OP. however, i would just like to confirm. don't want to brick my new phone.
PapaSid26.12 said:
Does it work for RMX2001 Realme 6(india). I would assume it does as mentioned in OP. however, i would just like to confirm. don't want to brick my new phone.
Click to expand...
Click to collapse
Yes, it works. But the whole point of a systemless mod is that you CAN'T brick your phone. Worst case you will just have to wipe data via recovery.
great job but will it work for eu version to (rmx2001)
we are unable to unlock bootloader with deeptesting.apk and nobody seems to care..
marvinvvh said:
great job but will it work for eu version to (rmx2001)
we are unable to unlock bootloader with deeptesting.apk and nobody seems to care..
Click to expand...
Click to collapse
I am sorry to hear that about the EU version. I thought that this would have been resolved by now. Unfortunately this is a magisk mod, thus it doesn't work without magisk.
Even after making changes in PpP.profile I'm getting default settings
Shanpatil said:
Even after making changes in PpP.profile I'm getting default settings
Click to expand...
Click to collapse
You have to make the changes and save them before flashing the mod. Meaning that if the mod is already flashed and you make changes to PpP.profile, you have to remove the mod and reinstall it in order to get the new settings.
FatherJony said:
You have to make the changes and save them before flashing the mod. Meaning that if the mod is already flashed and you make changes to PpP.profile, you have to remove the mod and reinstall it in order to get the new settings.
Click to expand...
Click to collapse
Can u give some SS??
I bricked my phone...
Yep, title says it all.
It was supposed to be systemless though right?
So what happened was, I successfully rooted the phone, installed magisk using the manager, download both the profile and the mod itself. 1st installed the mod using magisk without the profile installed, got some bugs like green screen on viewfinder, default camera app though so i thought the problem lies within the profile settings so... uninstalled then installed 2nd with the profile on. Still got green screens, videos goes green as well, and UI restarts when I try to access stock launcher widgets. So i decided I'd uninstall the mod and magisk as well, and so i did. Restarted on each uninstall, and gave time as instructed. After magisk I got stuck on boot. Only access is to recovery and I can't seem to find any SP flash tool options like other mediatek devices have. 1st time on a realme phone as well. Any thoughts on where I actually fd up?
Edit: Tried wiping data but to no avail. (wipe and format)
fraillesgeon said:
Yep, title says it all.
It was supposed to be systemless though right?
So what happened was, I successfully rooted the phone, installed magisk using the manager, download both the profile and the mod itself. 1st installed the mod using magisk without the profile installed, got some bugs like green screen on viewfinder, default camera app though so i thought the problem lies within the profile settings so... uninstalled then installed 2nd with the profile on. Still got green screens, videos goes green as well, and UI restarts when I try to access stock launcher widgets. So i decided I'd uninstall the mod and magisk as well, and so i did. Restarted on each uninstall, and gave time as instructed. After magisk I got stuck on boot. Only access is to recovery and I can't seem to find any SP flash tool options like other mediatek devices have. 1st time on a realme phone as well. Any thoughts on where I actually fd up?
Edit: Tried wiping data but to no avail. (wipe and format)
Click to expand...
Click to collapse
The mod is indeed systemless, but magisk isn't. If you'd asked for help before attempting to uninstall magisk (for no reason i might add), i would have explained that the module files can be found in /data/adb/modules/RealmeUI_PpP_mod and you can remove them manually if you have issues. But removing magisk on mediatek does mess with boot partition so it can brick your phone. Fortunately for you, if you can enter fastboot mode you are not truly bricked yet. What i am assuming happened is that your boot.img was restored to the factory one but vbmeta (which i am assuming you also replaced with a patched one in order to root your device) wasn't. Be extra careful with what you do from now on as you can really brick your device. I would suggest downloading the exact rom version you have installed on your phone, extracting the boot and vbmeta images and flashing them via fastboot. If you are not experienced with this kind of stuff you should download telegram and seek help in the Realme 6 community there.
FatherJony said:
The mod is indeed systemless, but magisk isn't. If you'd asked for help before attempting to uninstall magisk (for no reason i might add), i would have explained that the module files can be found in /data/adb/modules/RealmeUI_PpP_mod and you can remove them manually if you have issues. But removing magisk on mediatek does mess with boot partition so it can brick your phone. Fortunately for you, if you can enter fastboot mode you are not truly bricked yet. What i am assuming happened is that your boot.img was restored to the factory one but vbmeta (which i am assuming you also replaced with a patched one in order to root your device) wasn't. Be extra careful with what you do from now on as you can really brick your device. I would suggest downloading the exact rom version you have installed on your phone, extracting the boot and vbmeta images and flashing them via fastboot. If you are not experienced with this kind of stuff you should download telegram and seek help in the Realme 6 community there.
Click to expand...
Click to collapse
First of all, thanks a lot for replying. Really cleared everything out.
HAHAHA YEAH there was no reason to uninstall magisk at all, wonder why i actually did that. For science I guess?
And so I have the vbmeta and boot img from the B.45 patch, i can get to recovery and i connected my phone to my pc the only problem is i can't seem to authorize my phone for adb. (RSA Key prompt doesnt happen on recovery), any other way to get to fastboot?
EDIT: THERE WAS! (assuming that download mode is fastboot) I kept pressing the version at the bottom of the screen on recovery and it showed a prompt to go to download mode. Unfortunately though, can't seem to access it. It just automatically restarts on REALME boot.
fraillesgeon said:
First of all, thanks a lot for replying. Really cleared everything out.
HAHAHA YEAH there was no reason to uninstall magisk at all, wonder why i actually did that. For science I guess?
And so I have the vbmeta and boot img from the B.45 patch, i can get to recovery and i connected my phone to my pc the only problem is i can't seem to authorize my phone for adb. (RSA Key prompt doesnt happen on recovery), any other way to get to fastboot?
EDIT: THERE WAS! (assuming that download mode is fastboot) I kept pressing the version at the bottom of the screen on recovery and it showed a prompt to go to download mode. Unfortunately though, can't seem to access it. It just automatically restarts on REALME boot.
Click to expand...
Click to collapse
I did the same mistak. Howevre here is a solution.
If you have sd card, download latest ozip file from realme wessbite and place in root of sd card. Then insert it into your realme 6 and boot into recovery using power and vol down. After that install zip from total storage and install from sd card. Hopefullt it will be back.
On an another note there shall be some key combo for booting into fastboot mode
Yes, you can install via recovery if you can push the ozip to /sdcard. But when the boot or vbmeta imgs are modified sometimes the installation fails. Hopefully it will work for @fraillesgeon.
As for PpPmod, i would appreciate if you guys could report the specific bugs you encountered and provide me with your PpP.profile settings. I cannot improve this for Realme 6 without your help as i don't own the device. I do have a few beta testers but sometimes they will miss stuff, it's only natural.
I'm back!
FatherJony said:
Yes, you can install via recovery if you can push the ozip to /sdcard. But when the boot or vbmeta imgs are modified sometimes the installation fails. Hopefully it will work for @fraillesgeon.
As for PpPmod, i would appreciate if you guys could report the specific bugs you encountered and provide me with your PpP.profile settings. I cannot improve this for Realme 6 without your help as i don't own the device. I do have a few beta testers but sometimes they will miss stuff, it's only natural.
Click to expand...
Click to collapse
Well I've been doing it for days, it seems I was just using a broken sdcard and when it patches it fails, I thought that the phone was totally broken though lols. Well I'm back and installing PpPMod now.
And during my desperate attempt to fix the phone, I was searching for solutions, and found out that the camera problem and reboots was from a buggy boot and vbmeta img in the flash tool I used (the one posted and is now updated with a new one).
well that's that, I'll check the mod up for bugs and hope it helps as much as you helped me fatherjony, Thanks alot!
Can you do the step by step process on how to flash it using magisk?
fraillesgeon said:
Well I've been doing it for days, it seems I was just using a broken sdcard and when it patches it fails, I thought that the phone was totally broken though lols. Well I'm back and installing PpPMod now.
And during my desperate attempt to fix the phone, I was searching for solutions, and found out that the camera problem and reboots was from a buggy boot and vbmeta img in the flash tool I used (the one posted and is now updated with a new one).
well that's that, I'll check the mod up for bugs and hope it helps as much as you helped me fatherjony, Thanks alot!
Click to expand...
Click to collapse
Great news! I am really glad you were able to save your phone. As a rule, only use internal storage (/sdcard) for important operations.
I am looking forward to your impressions!
PLEASE BEFORE YOU decide to try this rom, you MUST read all of post 1, 2, 3 and 4 (about 10 minute read). If you think this is an unreasonable request, then stop reading now and find another rom. Thank you.
NOTE: There is no S-pen support. If you need S-pen, DO NOT USE THIS ROM.
I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this rom.
BACKUP YOUR DATA AND OLD rom BEFORE trying my rom.
If you are NOT an expert in using fastboot, adb, odin, heimdall, twrp, DO NOT use this rom. You must know how to use these tools to revert back to your old rom. If you are new to flashing custom roms, do NOT attempt this. If you need your tablet for work and something important, do NOT flash this rom. This rom could result in a bricked device or boot loop or non booting device or you not being able to revert back to your old rom.
What works
1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. audio over bluetooth
8. camera (selfie photo preview doesn't work), a bit slow to switch from front to back camera and vice versa
9. selinux enforcing
10. DRM level 3
11. deep sleep
What doesn't work/What isn't tested
1. gapps. Some of you require gapps for whatever reason. I use Aurora Store for my purposes and thus have NO KNOWLEDGE of the current state of gapps.
There are various gapps projects (at least 5 in 2022). Each has pros and cons. It's your job to do the research and find a suitable gapps project. I suggest you allocate at least a couple of hours/days doing your own research. My rom works by itself fine without gapps. DO NOT talk about gapps in this thread.
2. full disk encryption has been deprecated in Android 13 (LineageOS 20).
3. S-pen doesn't work and I have no plans to even try to make it work.
Source Code
The build instructions, source code and manifest are listed in post #2 FAQ #1. The kernel source code is at
https://github.com/retiredtab/android_kernel_samsung_msm8916/tree/lineage-20.0
Thanks
1. LineageOS team for source code.
2. LineageOS-UL team for merging, maintaining the legacy patches needed for old devices into one common repository so everyone can benefit.
https://github.com/orgs/LineageOS-UL/people
3. @lpedia for helping test a msm8916 tablet device.
FAQ - I spent hundreds of hours building this rom. If you think it's unreasonable to read this FAQ, then don't use this rom. Thank you.
Q1. Where are the source and kernel source files?
A1. The kernel source files are at
https://github.com/retiredtab/android_kernel_samsung_msm8916/tree/lineage-20.0
The device tree files are at
https://github.com/retiredtab/android_device_samsung_msm8916-common/tree/lineage-20.0
https://github.com/retiredtab/android_device_samsung_gt5note10wifi/tree/lineage-20.0
https://github.com/retiredtab/device_samsung_gte-common/tree/lineage-20
The vendor tree files are at
https://github.com/retiredtab/vendor-samsung-gt5note10wifi/tree/lineage-19.1
https://github.com/retiredtab/vendor_samsung_msm8916-common/tree/lineage-20
The manifest.xml (or roomservice.xml) and build instructions for 20 are at
https://github.com/retiredtab/LineageOS-build-manifests/tree/main/20/msm8916
Q2. Is this ALPHA rom suitable as a daily driver?
A2. It can be depending on your requirements. I can't test every app so you try it yourself to see if it's suitable. I've been using this rom myself since mid Jan 2023 with no major issues. I suggest you do a clean install, see FAQ 11, and flash this 20 ROM BY ITSELF (no gapps, magisk, etc) and see if you like it.
Q3. What if my app, xyz, doesn't work?
A3. If your app doesn't work, then go back to your old rom.
Q4. Your rom is laggy and buggy.
A4. If you find the above, then go back to your old rom. There's only so much software can do on a 2015 budget level tablet. Remember a budget tablet will have the slower SoC/CPU and less DRAM than a top of the line model. Your tablet will also run slower when you use gapps. You can run a lot of software without using gapps. Research fdroid, newpipe, Aurora store etc.
Q5. What TWRP should I use?
A5. You MUST use TWRP 3.5.2_9. Get it from
https://sourceforge.net/projects/retiredtab/files/SM-P550/TWRP/
Q6. Why should I use this rom?
A6. If you don't like this rom, then don't use it.
Q7. Will you offer monthly updates with security patches?
A7. I will try to offer monthly security patches, but that all depends on if I continue to have high speed Internet in the future.
Q8. Can you help me? I'm a newbie. Can you provide step by step instructions?
A8. I don't have the time to help newbies, so please do your own research. There are lots of tutorials, videos, etc on how to flash roms. Newbie questions must be posted in the Questions and Answers forum, not here.
Q9. Can I report a bug with respect to the rom?
A9. Yes, but you need to supply the following information. If you don't, I won't look at it.
You must provide an adb logcat of the problem and tell me how to reproduce it. Note I will not be downloading any apps that require money or an userid/password. For example, if you have problems with Netflix, I cannot help you since I don't have a paid subscription. If you use some app that requires an userid/password, I cannot help you as I'm not willing to create another userid/password even if it's free.
To get a logcat, open up a terminal window.
Code:
# clear the logcat first
adb logcat -c
# start logcat trace
adb logcat > problem.txt
# reproduce problem
# wait until problem has occured, then stop trace by hitting ctrl-c
# attach the problem.txt ZIPPED as text files don't seem to get attached properly
Q10. Do I need to erase everything and format my data?
A10. Yes, you MUST erase all the partitions (system, data, dalvik/art cache, cache) using TWRP and MUST format your data before installing 19.1 when you are coming from stock or an earlier version of LineageOS or from another custom rom. If you get stuck at the boot animation for more than 5 minutes, it's likely because you didn't follow the instructions I just wrote. Dirty flashes from stock, other custom roms or older LineageOS versions are not supported and not likely to work.
Q11. What gapps should I use?
A11. I don't use gapps anymore. I use Aurora Store. As of Nov 6, 2021, I no longer make recommendations on which gapps to use as your mileage may vary.
Let me by crystal clear. YOU NEED TO DO YOUR OWN HOMEWORK selecting between the various gapps offered. There are 5: opengapps, nikgapps, mindthegapps, flamegapps and bitgapps. Each one will have it's own installation instructions. The only recommendation I will offer to use the SMALLEST version of gapps.
Don't be surprised that whatever gapps you use might have problems like "Just a sec", voice not working, updating google play store please wait, etc. These are NOT problems of the OS as the OS will run fine without gapps. These are gapps problems and you must ask in the gapps forum why it doesn't work.
Q12. I'm having problems with gapps, can you answer why it's not working?
A12. I WILL NOT answer any questions regarding gapps. This thread is about the rom, not gapps. Android does not depend on gapps in order to work.
Q13. Why isn't my post answered or ignored?
A13. Questions already answered in the FAQ will be completely ignored. Again, I do not use Windows OS or gapps.
Q14. What speed up/optimization tips do you suggest?
A14.
1. Turn off animations. Go into developer settings, scroll down to the drawing section, and set window, transition and animator scale all to "off".
2. If you don't have a google account, don't install gapps. Use Aurora Store to get your apps as you can get all the same apps from the play store using an anonymous login.
3. Dont' run more than 2 apps at the same time. You can probably listen to music in the background and use a web browser at the same time, but don't expect great performance from a 2015 entry level tablet.
4. Use a web browser like Brave that has built in adblock and privacy features.
5. Use newpipe to watch your streaming content. It has built in adblock so you don't have to watch forced ads.
6. Look for apps that are open source, ad free and lightweight.
7. Remove all unused quick setting "bubbles" from the quick pull down menu. I only need and have 6.
Q15. Does this rom support Magisk for root?
A15. I don't use Magisk myself so I don't know and Magisk is always being updated to fool Google's certification process. Others have reported Magisk as working, but I won't answer any questions regarding it.
Q16. Will this rom ever become official?
A16. Starting with 19.1, legacy devices like ours will NEVER be official due to lack of ebpf support. See https://lineageos.org/Changelog-26/
Also, I don't want the responsibilities that come with being an official maintainer.
Q17. What is the difference between this rom and others?
A17. This rom tries to be pure LineageOS with little to no modifications.
Q18. Will there be any major 20 code modifications in the future?
A18. I don't anticipate any major modifications. There may be some small bug fixes and minor code cleanup, but all the hard work in getting the rom up and running and fixing all the major bugs have been done completed. This doesn't mean the code is perfect or well organized, but I won't be doing any major changes now that 20 is working.
Q19. Why did you fork the device and vendor trees for 20?
A19. The msm8916 repos seem geared towards phones and sometimes do not work or cause boot animation loops for tablets so I decided to fork their repos. In other words, what's deemed as msm8916-common code isn't common to all devices.
In addition, since I'm building SM-T350, SM-T357W, SM-T550, SM-P550 and SM-T560NU (all use the same msm8916 code), it seems easier to maintain all of them if I can control my own code repos and not worry if my changes affects the phones or not.
I have completely decommonized and rearranged the 20 msm8916-common tree so it's easier for me to maintain and build.
Q20. Can you build a variant of this device? For example, a LTE or S-pen version.
A20. If I don't physically have the device, I cannot and will not build it unless I can boot and test it myself. Even then, there's no guarantee that I can get those variant features working.
Q21. Can I load this rom on a variant devivce like LTE or S-pen version?
A21. The rom is built for the device explicitly listed. If you are an advanced user and understand TWRP, adb, odin, heimdall, you can try loading it on a LTE or S-pen variant by modifying the updater-script, but it may cause a bricked device, bootloops or non functionality of LTE/S-pen. You have been informed and warned!
Q22. I don't like the taskbar, how do I turn it off?
A22. Choose settings, type task into the search bar. Choose enable taskbar and disable taskbar. This will leave the on screen nav bar. If you want to disable that, go to settings, system, gestures, system navigation, gesture navigation.
Q23. Okay, I understand the consequences and that this is ALPHA rom and willing to take the risks outlined, now where can I find the rom?
A23. You can download it from https://sourceforge.net/projects/retiredtab/files/SM-P550/20/
Release notes
NOTE: All builds that I upload have been personally tested on my device to boot and function as described in post #1. Having said that, there's still a chance it won't work on your device due to human error, your configuration, your apps, etc. If it won't boot, always start with a complete wipe of everything and format your data in TWRP. This is known has a clean install. Backup your data before a clean install.
June 23, 2023
1. Initial 20 ALPHA public release.
2. Incorporates June 5th security patches as per https://review.lineageos.org/q/topic:"T_asb_2023-06"
Reserved.