This app was mentioned in 60 comments, with an average of 2.83 upvotes
Not sure if its what he is using, but its a great app. The Dev, does top notch work.
https://play.google.com/store/apps/details?id=flar2.devcheck&hl=en_US
>...I have the latest version of lineage for S5 and I would like to know if there is any way to use the split screen without one of them freezing while I use the other one...
I see in your screenshot that you are trying to run two sessions of Pokémon at the same time on the antique & limited RAM S5.
I just ran in split screen YouTube playing a video & DevCheck > Dashboard for CPU monitoring & it worked fine.
That's on a Galaxy S5 G900M LineageOS 16.0 klte build 2019-07-07 + Open GApps Pico + LineageOS AddonSU, no custom kernel or system mods of any kind.
BTW "latest" will not mean a thing for future readers after the next update so including the build date & LineageOS version is good practice IMO. ;)
And what is your exact S5 model?
Well. I checked using this app: https://play.google.com/store/apps/details?id=flar2.devcheck and this aplication is telling me that i have LPDDR5... But someone gave me an adb command, and that says that i have LPDDR4X... The adb command is: getprop ro.boot.ddr_type It will give you a number. 0 is for LPDDR4X or 1 for LPDDR5.
Same issue on my Pixel 3. I can use a utility to test the proximity sensor and it won't toggle like it should. After a reboot everything works normally until the issue returns. Using DevCheck https://play.google.com/store/apps/details?id=flar2.devcheck
Not sure. Most likely the filesystem drivers are provided through FUSE.
In my device, when I checked it using DevCheck, the filesystem information for the removable storage is completely absent (filesystems for /data
and /system
both show as "ext4"). The SD card inserted in that device is a 32 GB one, formatted with FAT32.
There's an free app called Devcheck that XDA put out. It will tell you everything you ever wanted to know about your phone.
Here's a link
Available on Google Play: https://play.google.com/store/apps/details?id=flar2.devcheck
Yikes, yeah, they didn't tell you the truth, but better finding out now than when you order the wrong battery.
The Force has the "shatterproof" display panel, a larger battery (making the Force slightly thicker at 7mm vs 5mm), and a 21MP camera vs the 13MP on the normal Z. The battery difference is 2600mAh for the Z vs 3500mAh for the Z Force. I wished they had used a different primary model number, instead of just including it as a dash-XX notation that usually just identifies between carrier or unlocked model variations. They made the Force just a variant of the same model number, even though it's different enough it should have gotten its own model number like xt1655 or something.
Just to be sure, you're looking at the numbers right next to the charging port? I'm just trying to be sure in case someone flashed a ROM from an -03 on it (not likely, but should be possible) onto a Force for some reason, so the system is reporting the wrong model.
You can verify by installing any of the various system information apps like this one from highly respected Android kernel developer flar2 (there's many others, I just know for sure that one is 100% safe), the hardware will speak for itself, regardless of what it says in settings>system>about. Check the camera for 13 vs 21MP, and the battery size of 2600mAh vs 3500mAh. That should give you positive confirmation enough which model you have.
/r/Xiaomi/wiki/specs/redminote5
Codename: - WHYRED
The Pro version naming scheme is only for India, where the Redmi 5 Plus is labeled RN5.
Although the Global Version has the Pro extension in DevCheck app.
https://play.google.com/store/apps/details?id=flar2.devcheck&hl=en
https://play.google.com/store/apps/details?id=flar2.devcheck&hl=en
What I use and its great. Aaron keeps it pretty updated also. Tons of monitoring solutions. Just enable "snap to status bar" & go to town.
Edit : wording
Only some people get the red tint. It's something to do with the panel manufactorer. Tianma is supposedly the good one, and Sharp the "bad" one. You can check which panel you have with this app: https://play.google.com/store/apps/details?id=flar2.devcheck (under the hardware tab)
Check if just your OS is outdated or if your device is running on 32-Bit SoC.
Go to i.e. Settings > System > About phone to check the OS version, and Settings > System > Software updates to see if there's any update available. There may be also an App named Update or similar in your App drawer.
Or you can use DevCheck to get the information easily.
Depending on manufacturer and model, there's still a small chance to get a official system upgrade, i.e. Android 6 > 7 or 8+, but it makes only sense for a 64-Bit device.
Check
If it's 64-Bit but there's no update available, you could try to find a inofficial update or alternative ROM for your device (*requires probably Root access and unlocked Boot Loader definitively). It'll require some technical knowledge though.
>u/ActionFamous8431 - S9+ screen wont turn on after being locked...I replaced the screen since the original was broken...
Maybe changing the screen affected the proximity sensor?
Check the proximity sensor with a sensor test app like Sensors Sandbox on F-Droid or DevCheck in Play Store.
The best troubleshooting step to confirm or rule out a hardware problem is to flash the most recent stock manufacturer's OS for your device & test thoroughly before installing LineageOS. That will also update the vendor's firmware if you did not do that yourself already.
Their paywall policies vary apparently randomly depending on the device & age of the OS but I used both sammobile.com & updato.com to download stock Samsung OS. Some users recommend samfw.com.
They all have flashing instructions using Odin3 in their respective download pages.
DevCheck](https://play.google.com/store/apps/details?id=flar2.devcheck) does this and more.
So does BetterBatteryStats aka BBS, which is much better for the purpose of saving battery; since it also shows detailed information about wakelocks, alarms, etc. which impacts battery life, even down to which apps are doing it and why. Truly a fantastic app, and it's even free on XDA (or the mirror I linked).
I try to avoid ancient apps when there's good up to date alternatives.
It's probably your Android version, the hardware is fine. Do you still run on 7.0 (Nougat) or did you upgrade to 8.1 (Oreo) already?
You can simply use DevCheck from Google Play Store to your device.
It's possible that you didn't got the update via OTA for this or another reasons, but there are ways to install the update manually.
I'm using DevCheck, but CPU Monitor seems to be the more popular one on this sub.
In official LineageOS 18.1 > Settings > About device > Model.
Try DevCheck or Droid Examiner > Build.
I would say it swaps to zram which is a portion of memory dedicated to compressing processes to free up memory.
If it needs to modify the freed up process, then it needs to expand and move it back to ram (which seems convoluted)
To me it seems that the storage has expanded read only pages that it keeps on there then moves it back to ram when it needs it. Actually it can't be read only. Seems like the unmodified file can be deleted from ram but the dirty modified can't be.
> This portion of RAM grows or shrinks in size as pages are moved into or taken out of zRAM. Device manufacturers can set the maximum size.
Maybe OP selected a really low value here. According to Dev Check my 7T has 2GB of zram allocated to it
So it seems like it tries ram first. When it can't fit everything it compresses a portion putting it in zram. When zram gets low it removes things contained on storage and references it when it needs it again.
Check the proximity sensor with a sensor test app like Sensors Sandbox on F-Droid or DevCheck in Play Store.
The modem baseband doesn't define the processor. Could be using a different baseband that was based on the older modem, and just didn't change the version naming.
Install DevCheck and see what the second tab says. Should tell you the CPU that is actually inside.
YMMV depending on the device but you can check the proximity sensor with an app like DevCheck > Sensor panel or Sensor Box for Android for example.
I upgraded to Android 10/OneUI 2.0 this morning and DevCheck only registers "Status: Far" from the proximity sensor. In other words, it doesn't appear to be fixed.
> G900FXXU1CQK3
That is recent enough & should work.
Was your S5's modem updated via a stock Samsung firmware or did you flash only the modem?
I am asking because the packages linked in S5 Odin Flashable Modem & Bootloader includes much more than just the modem.
With an app like DevCheck > System where you can see your current Bootloader which is named aboot in the S5. Which one do you have?
Ohhh the FTP plugin is to make your phone an ftp server! That's pretty neat.
Also worth noting, I use this app called Dev Check to monitor cpu sensors etc. The pro version is an in app purchase one time, and it enables on screen monitoring that can snap to the status bar, I use the "Battery current monitor" which gives a quick glance view of how hard the apps are hitting the cpu, helps identifying any shady app making the phone too hot etc! https://play.google.com/store/apps/details?id=flar2.devcheck
Yes, I have it running on my Pixel, I'm also rooted but I don't I think it requires it. Here's the link: https://play.google.com/store/apps/details?id=flar2.devcheck&hl=en&referrer=utm_source%3Dgoogle%26utm_medium%3Dorganic%26utm_term%3Ddevcheck&pcampaignid=APPU_1_CuX9WKmWDMLqjwS__oToBg
*Link is a mess. Just type in DevCheck on Play Store.
https://play.google.com/store/apps/details?id=flar2.devcheck (you can check which panel you have with this app) I'm from Europe and I'm ready to be disappointed. AT LEAST WE GET THE EARBUDS AM I RIGHT
edit: i checked this thread and some eu customers got the tianma version http://forum.xda-developers.com/htc-10/how-to/poll-panel-htc-10-main-s820-variant-t3370972/page2
From what I remember offhead (based on articles and discussions that I've read), Android 9/Pie's many regressions (moreso for notchless phones) include:
Neutered navigation bar with an increased focus on gestures rather than buttons (wit the bar using up the same amount of space with decidedly half-baked gestures). Some companies at least maintained the options of buttons or gestures, but I think the Google Pixel 3 prevents users from having the option of using the classic navigation buttons.
Horizontal Recents/Overview screen instead of a vertical variant - this "feature" is more subjective, I guess.
Enforced 3-icon limit for notifications in the status bar, all thanks to notches - for certain phones, this change completely removed the option to have as many icons in the status bar as you have space for.
The Digital-Clock/Time's position was enforced on the left instead of the classic right-side position - again, all thanks to notches..
The Volume Slider got changed to a "vertical" variant if I recall correctly, and I think that certain volume sliders can only be changed by actually diving into Settings, whereas the Android 8/Oreo implementation gave a simple quick drop-down to change all 4 at once, and Samsung even added the option to switch the controlled volume default from Ringtone to Media.
Removal of easy access to viewing System Uptime in Android Info (WHY? It's a useful metric that just sits there harmlessly!).
The DevCheck application thankfully still indicates System Uptime, although the read-out isn't as "fluid" (doesn't refresh as much) from what I've seen.
Neutering of the "Quick Toggles" pop-up thing, where you can adjust certain quick-toggles' settings quickly without actually diving into the Settings screen.
certain "Do Not Disturb" mode capabilities/workflows that were possible in Android 8/Oreo are apparently harder, if not impossible, to achieve in Android 9/Pie.
I think that the Android 8/Oreo Easter Egg got removed..? (if one counts that as a feature).
Call Recording got heavily hampered.. I'm not sure of Screen Recording... Custom theming on Samsung devices also seems like it will be harder to achieve in the near future (going by a recent changelog entry for the "Theme Galaxy" application), although "One User Interface (One UI)" seems to be softening the blow.
as others have mentioned, the method to access Android-native "Split-screen/Multi-Window view" has been altered a bit...
The annoying thing is that a good chunk of these changes were done by actively worsening what Android 8/Oreo had practically perfected (especially the Volume Sliders and Quick-Toggles), and a lot of user frustration could have been alleviated if there were more toggles for things (especially regarding buttons vs. gestures, positioning of the time/clock on notchless devices, horizontal vs. vertical Recents screen, horizontal vs. vertical Volume Slider, and the method for accessing Multi-Window view). At least some manufacturers are trying to rectify some Android Pie issues, like the recent updates to Samsung's Good Lock application and modules.
Also, if that mention of "E-mail being removed soon as a form of technical support" is true, then I agree with the sentiment of that being a stupid decision, considering that snail mail / written correspondence has the disadvantage of usually taking extra time for message exchange to occur, and things like phone calls and "online customer-support chat-rooms" can be very hit or miss for a given consumer and are not nearly as easy to "auto-archive for reference" as an e-mail message is.
It has more features and isn't just a cash grab.
Can someone with Devcheck if the devices can deep sleep?
Complete information about your CPU, GPU, battery, camera, network and OS.
Available on Google Play: https://play.google.com/store/apps/details?id=flar2.devcheck
>I've got G900FXXU1CRH1_G900FXXU1CQK3_Baseband_Firmware.tar.md5 for my G900F...
Why not include a link to where you got it from for the benefit of other S5 users? I suspect it's from haggertk's SM-G900F folder here
I described here with screenshots how I updated my S5 G900M LineageOS 16.0 klte using haggertk's Odin flashable bootloader & modem combos and what the packages include: S5 Odin Flashable Modem & Bootloader.
Haggertk is the S5 klte + variants LineageOS maintainer & one of the 9 LineageOS project directors.
>...before burning these files I'd feel more comfortable downloading the existing partitions to my laptop in such a format that I could use heimdall to restore the phone back to where it started from....
What is your current bootloader & modem?
You could use DevCheck or Phone INFO Samsung for example to get that info.
Then get that older package from haggertk's folder linked above or in his older modem folder instead of backing up all the partitions updated by his packages.
See my other post in this thread about the S5's partitions if you still want to do a backup.
Sorry I don't use Heimdall so can't help with that.
>u/w2vy - So far the wiki documentation on getting started looks good and clean, the one thing I see missing is the steps to revert back to Stock FW.
You are linking to the Samsung Galaxy S9 (starlte) installation wiki.
It's easy to return to stock Samsung OS.
Their paywall policies varies apparently randomly depending on the device & age of the OS but I used both sammobile.com & updato.com to download stock Samsung OS. Some users recommend samfw.com.
They all have flashing instructions using Odin3 in their respective download pages.
On XDA [Tool] Frija - Samsung firmware downloader/checker to download directly from the Samsung servers.
In Frija the CSC is required info. You can check if the original one for your device is shown in About phone or using an app like DevCheck > System > Product code's last 3 digits or check sammobile.com for example to find other CSC's then use Frija for fast & free downloads.
See also Samsung support Moving contents using Samsung Smart Switch PC and Google Backup which you can restore on first boot after installing LineageOS.
Thanks for the screen, I was near to ask what app anyone use to obtain this information. I'll give a try to DevCheck.
DevCheck by flar2
DevCheck has floating monitors you can dock to the status bar. It requires the in-app pro upgrade to unlock that feature.
>u/Traditional-Top-4708 - X00P (Zenfone Max M1) ...I finished the installation instructions from recovery, got script succeeded: result was [1.000000] when i hit the back arrow to return to the main menu, it adds: Install completed with status 0. Then i hit reboot system now. But it keeps rebooting until the Asus logo and repeats over and over. I can enter recovery again to retry the process but it never boots into lineage... i followed these instructions. Its about the ASUS Zenfone Max M1 (X00PS). Without the "pro", but with an additional "S", while the instructions are about the "X00P". Is that the issue?
If you really followed all the steps of the installation wiki maybe that's the issue.
What is your exact device model number?
Sadly the dev did not include a list of supported model in the wiki ASUS Zenfone Max M1 (X00P).
Searching the web with X00PS I found the model ZB555KL.
Comparing Asus Zenfone Max (M1) ZB555KL vs. Asus Zenfone Max (M1) ZB556KL on gsmarena they have different network bands, screens& possibly chipset, CPU & GPU depending on the variant.
Maybe you could ask in this XDA forum thread created by the LineageOS maintainer of your device & where you can find actual users: [ROM][11.0][OFFICIAL] LineageOS-18.1[X00P][MSM8937].
Note that in the title of his tread he mentions chipset MSM8937.
Try DevCheck or Droid Examiner to get hardware & other infos about your device.
Install DevCheck. It has the nosel in the system tab.
https://play.google.com/store/apps/details?id=flar2.devcheck
you could use this app:
https://play.google.com/store/apps/details?id=flar2.devcheck
>u/Wiktor090 - Samsung Phone ...Where i can find ( or how ) the CSC
Try DevCheck > System.
For ois download https://play.google.com/store/apps/details?id=flar2.devcheck
Download devcheck app
Hey can you run Dev Check and tell us the zram total and usage.
Was using this the other day to upscale some of my older digital photos!! Your device needs a Vulkan capable GPU (most modern phones do, https://play.google.com/store/apps/details?id=flar2.devcheck can help ID if so)
Literally, git clone the repository; git clone https://github.com/tanyiok1234/waifu2x_srmd-ncnn-vulkan-termux-binary.git
Using the waifu2x-ncnn-vulkan option, cd into it's folder and find yourself a low resolution image.
And then issue a command like so;
./waifu2x-ncnn-vulkan -i /sdcard/Pictures/Pixlr/1627474982066.jpg -o /sdcard/Pictures/upscaled.jpg -t 32 -j 1:1:1
I did a reduction of the top image, bringing it to 400/500 resolution, after running through this, it's made a noticeable improvement on upscaling https://imgur.com/a/9yDeoi3
I use an app called Dev Check with the fps overlay enabled (pro unlock required), and it fluctuates between 89.1 and 89.5 fps in every app I test.
I even used the refresh rate test at testufo with Chrome, Brave, Samsung, and Edge browsers, which also gives very similar results. They never drop down to 60 fps
Note, I do not have any Developer Options enabled. Not even the menu itself unlocked.
Edit: I JUST found this out, but when battery saver is enabled, the refresh rate drops down to 60 fps everywhere, even in web browsers.
You are welcome but the problem is not solved yet. :/
With an app like DevCheck > System > could you tell me what is your bootloader & baseband?
Or use Phone INFO Samsung > Firmware or AIDA64 > Android panel to see Baseband & Bootloader. Also neat is it's > 3-dots > Send Report in E-Mail to yourself so you can copy/paste the data w/o having to type everything.
Does this happen after a restart? You can check sensors with an app like DevCheck (https://play.google.com/store/apps/details?id=flar2.devcheck)
Good question. Honestly, I don't know. Can you try https://play.google.com/store/apps/details?id=flar2.devcheck&hl=en_US ?
>Restore of EFS partition after flashing Lineage OS helped a little. SIM card is detected now, but at most there is no signal (with stock android signal strength is very strong here)...
>
>...There was no progress at all with suggested TWRP flashable modems. SIM card was not detected again.
I am following that XDA thread linked above since November 2017 & while I saw a handful of cases with no SIM error after flashing LineageOS 14.1 coming from stock Samsung, none where not fixed with a EFS partition restored from a backup made with TWRP while running stock Samsung & SIM working.
The only options I can think of are:
​
Can you install https://play.google.com/store/apps/details?id=flar2.devcheck&hl=en_US and let me know the panel type under graphics section?