Hi,
My M30s started randomly restarting after a software update. I could not find solutions here when I searched but it appears a lot of people on the internet having been facing similar issues for quite a few months now. The Samsung community forums are full of multiple messages and Samsung is pushing people to get to their phones to the service centers and are getting the motherboards replaced for free if the warranty is valid (or at a cost of INR 9,000 otherwise).
In any case, I found another poster on the Samsung forums who seems much more tech savvy than I am. And he seems to have solved the problem on his phone by changing 2 lines of code in the Linux kernel wand rebuilding the OS afterward.
Like I said, I am not tech savvy enough for this, but I thought I would post the link here because I could not find this particular fix here.
Re: READ THIS IF YOUR SAMSUNG GALAXY M30S KEEPS RANDOMLY FREEZING AND RESTARTING AUTOMATICALLY
To add a bit of my research into this problem: My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the...
r2.community.samsung.com
(Here is the text from the post in case you are not able to open it)
-----------------------------------------------------------------------
To add a bit of my research into this problem:
My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the OS Samsung has released on their open-source portal. I can use this source code to fix and rebuild the OS to prevent the issue from happening.
The issue and the fix is well known among the Samsung M30s community. It's two lines of code that need to be changed to prevent at least one of the common reasons for frequent reboots.
It takes a lot of work for a private user to fix those two lines of code, because Samsung releases source code that's non-trivial to compile and actually run on your device afterwards.
Samsung's Android 11 still ships with the same old kernel version (4.14.62) as their Android 9 (4.14.62), released back in 2018. There might have been some fixes between 4.14.62-19694174 and 4.14.62-20748039 introduced by Samsung in the meantime.
Regardless, this fix is not part of the source code for M307FNXXU2BTC6 (linked above) that's been released by Samsung in June 2020. Therefore, it doesn't seem like Samsung is actually applying all fixes to their kernels.
The kernel itself should have been upgraded to a higher version - at least to 4.19 - to fix bugs that's been plaguing users of Exynos 9611 chips running on Linux v4.14 for a long time.
Samsung: Please apply this fix to your Android kernels and push the update to your customers. Thank you!
References about the "fix NULL pointer deref in smaps_pte_range()":
Mainline Linux kernel fix:
[4.19,248/361] mm: /proc/pid/smaps_rollup: fix NULL pointer deref in smaps_pte_range()
https://lore.kernel.org/patchwork/patch/1010971/
Google Android Linux kernel backported this change in 2019 :
https://android.googlesource.com/kernel/common/+/043c92bd0517e0018cb6307390eb9c36b864fb9f
--------------------------------------------------------------------------------------
EDIT: After more hours of experimenting I have managed to compile a kernel with the patch mentioned in this post. I can confirm that I faced no reboots since I flashed my phone with this new kernel. Hence, I can confirm this fix really prevents frequent reboots.
superstarksa said:
Hi,
My M30s started randomly restarting after a software update. I could not find solutions here when I searched but it appears a lot of people on the internet having been facing similar issues for quite a few months now. The Samsung community forums are full of multiple messages and Samsung is pushing people to get to their phones to the service centers and are getting the motherboards replaced for free if the warranty is valid (or at a cost of INR 9,000 otherwise).
In any case, I found another poster on the Samsung forums who seems much more tech savvy than I am. And he seems to have solved the problem on his phone by changing 2 lines of code in the Linux kernel wand rebuilding the OS afterward.
Like I said, I am not tech savvy enough for this, but I thought I would post the link here because I could not find this particular fix here.
Re: READ THIS IF YOUR SAMSUNG GALAXY M30S KEEPS RANDOMLY FREEZING AND RESTARTING AUTOMATICALLY
To add a bit of my research into this problem: My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the...
r2.community.samsung.com
(Here is the text from the post in case you are not able to open it)
-----------------------------------------------------------------------
To add a bit of my research into this problem:
My phone (SM-M307FN) is rebooting many times every single day due to a Linux kernel issue which has been already fixed a long time ago in the mainline version. I am still running Android 10, because that's the latest version (M307FNXXU2BTC6) of the OS Samsung has released on their open-source portal. I can use this source code to fix and rebuild the OS to prevent the issue from happening.
The issue and the fix is well known among the Samsung M30s community. It's two lines of code that need to be changed to prevent at least one of the common reasons for frequent reboots.
It takes a lot of work for a private user to fix those two lines of code, because Samsung releases source code that's non-trivial to compile and actually run on your device afterwards.
Samsung's Android 11 still ships with the same old kernel version (4.14.62) as their Android 9 (4.14.62), released back in 2018. There might have been some fixes between 4.14.62-19694174 and 4.14.62-20748039 introduced by Samsung in the meantime.
Regardless, this fix is not part of the source code for M307FNXXU2BTC6 (linked above) that's been released by Samsung in June 2020. Therefore, it doesn't seem like Samsung is actually applying all fixes to their kernels.
The kernel itself should have been upgraded to a higher version - at least to 4.19 - to fix bugs that's been plaguing users of Exynos 9611 chips running on Linux v4.14 for a long time.
Samsung: Please apply this fix to your Android kernels and push the update to your customers. Thank you!
References about the "fix NULL pointer deref in smaps_pte_range()":
Mainline Linux kernel fix:
[4.19,248/361] mm: /proc/pid/smaps_rollup: fix NULL pointer deref in smaps_pte_range()
https://lore.kernel.org/patchwork/patch/1010971/
Google Android Linux kernel backported this change in 2019 :
https://android.googlesource.com/kernel/common/+/043c92bd0517e0018cb6307390eb9c36b864fb9f
--------------------------------------------------------------------------------------
EDIT: After more hours of experimenting I have managed to compile a kernel with the patch mentioned in this post. I can confirm that I faced no reboots since I flashed my phone with this new kernel. Hence, I can confirm this fix really prevents frequent reboots.
Click to expand...
Click to collapse
Amazing work brother, everyone is facing this restart problem but you can help
Can you compile the latest kernal(4.14.113) and share it with our M30s community.
razs.originals said:
Amazing work brother, everyone is facing this restart problem but you can help
Can you compile the latest kernal(4.14.113) and share it with our M30s community.
Click to expand...
Click to collapse
Like I said in my post, I am not tech savvy enough to do this. And I am wondering if this problem has been widely reported even. This is the place I expected to find lot of buzz but i dont see any
Everyone is upset with this Samsung's reboot problem. Anyways we users will find a solution.
I am a M30s owner. I have done this on my phone and it's a temporary fix. Atleast try this and wait for the official fix. It's better to have something than nothing.
How To Fix Restart Issue On Galaxy M30s, M31, M31s, A50, A50s? (Updated) - SamsungSFour.Com
How To Fix Restart Issue On Galaxy M30s, M31, M31s, A50, A50s? (Latest Method)
www.samsungsfour.com
Related
Gents,
I need your help about "kernel", as I know when installing Android I need the folder named Android and the data.img.
But the kernel what is that?
Thanks for reading and more for helping.
The kernel is the core of the Android OS. Windows too runs on a kernel. Every build already includes one, and usually the most up-to-date or stable version, so you shouldn't have to worry about it, unless you want to update your kernel some time in the future.
I've been running Android for several months now and I've not updated the kernel once.
Still there is somthing to say
First I want to thank you for giving me some of your time.
The answer is clear, but why there is update always (now is 8.6)?
and what the kernel is including, is it the same of Android folder?
I hope I will find some more time.
Check out here for a bunch of explanations of terms that are commonly used around here
http://forum.xda-developers.com/showthread.php?t=852660&highlight=glossary
The reason that the kernels are updated alot is that the people who build the kernels find flaws in them through testing them, and through the feedback they recieve here on XDA.
Then they work to try and find ways to fix those flaws. Sometimes in fixing one flaw, a new one emerges. Generally it is a good idea to use the latest version of whatever kernel came with the build.
Hello, I'm trying to build an app called Commotion Wireless from its source code - I didn't make this app myself, so it should be a simple case of following the instructions in the README, importing into Eclipse and exporting as a .apk. However, upon attempting to build, there are 3 errors: two saying "isIBSS cannot be resolved or is not a field" and the third with "frequency cannot be resolved or is not a field". The offending pieces of code are here:
github.com/opentechinstitute/commotion-android/blob/cm/src/net/commotionwireless/profiles/Profile.java - lines 201 and 202
github.com/opentechinstitute/commotion-android/blob/cm/src/net/commotionwireless/meshtether/NetworkStateChangeReceiver.java - line 92
Now as many of you know, stock versions of android don't seem to support ad-hoc networks, this is functionality that other custom firmware such as Cyanogenmod adds. As far as I can tell, this app is intended for cyanogenmod (as the devs state in URL1 below). Therefore I think that the definitions of "isIBSS" and "frequency" are not in the stock versions of andriod (URL2 is a patch somebody wrote that adds them), and the root of my problem is that I'm trying to build the app based upon the stock version of android that doesn't understand what "isIBSS" and "frequency" mean. I have never tried to build an android app before so have little experience, but my first instinct was that I needed to install a custom version of the android SDK for Cyanogenmod that would have the needed definitions in - however as far as I can tell, no such thing exists.
Does anyone here have any idea how I may resolve this issue? Your help is much appreciated
URL1: commotionwireless.net/developer/resources/commotion-android/
URL2: thinktube.com/files/android-ibss/patches/frameworks-base-0001-Wifi-Enable-Ad-Hoc-IBSS-network-configuration.patch
When Moto X Play is getting official CyanogenMod 13? Any updates?
Nitish247 said:
When Moto X Play is getting official CyanogenMod 13? Any updates?
Click to expand...
Click to collapse
Probably never. Does it matter? No, not at all. What is better about an official version compared to the unofficial? Nothing at all.
But why? Any specific reason? All Moto phones till date have official CM.
It's my understanding cm13 will turn official some day.
Nitish247 said:
But why? Any specific reason? All Moto phones till date have official CM.
Click to expand...
Click to collapse
If you are following the cm13 thread then you would know that squid has told that he would push for the cm13 build to become official but there is no estimated time.
Sent from my XT1562 using Tapatalk
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
Great news. Laud your hard work have a great year ahead squid2
Sent from my XT1563 using Tapatalk
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
Thanks! Thats' awesome! :good:
We expect lux on official CyanogenMod list soon
squid2 said:
It's a matter of fixing bugs. My intention has always been to make CM13 official once it is ready. There are three bugs blocking this:
Use of WiFi assisted location causes soft reboots if you don't add additional bounds checking. I am not sure if this bounds checking should really be there or if it is a symptom of some other problem.
A mysterious issue with the new camera drivers is causing memory corruption in the audio HAL. I'm not sure of the cause (other than the crash only happening when liboemcamera is updated to the Marshmallow version). I have a crude hack to work around this, but it is not suitable for merging into official CM. This will be tricky to debug and fix properly.
The RIL needs fixing on XT1562. I don't have an XT1562, so that makes it more difficult for me to troubleshoot, but @scritch007 will be looking into this in the coming days.
Click to expand...
Click to collapse
I tried the version from the 25th of December, and I don't have any issue with it (I own a dual sim xt1562) and only have one sim inserted, but just after the boot I was prompted for the pin code. So I won't be of any help...
I'm running the 24.11.18.lux_retasia_ds.retasiaall.en.03 retfr version as my main version, so all my partitions were updated to 6.0
Hey guys,
I'm just looking for someone to point me in the right direction. Basically, my school has this web portal logon thing called Cloudpath (formerly xpressconnect) that requires you to log on to the portal's network in order to follow the instructions in your web browser for your specific OS. The problem arises with Android. It requires you to download an app, which does all the nitty gritty certificate installation and configuration for you. However, whenever I try this on a CUSTOM ROM (LOS-based and DU), I end up in a connecting loop. I never get connected to the secured network even though the certs appear to be installed correctly. I've tried using the app and doing it manually by downloading the certs myself. This only occurs on custom nougat roms, but works on stock MM (I haven't tried MM roms, because I want nougat).
As far as I know this problem only affects this phone after I install the rom and OpenGapps. Some of my peers have LOS and have gotten it to work, so I'm the only one, and the tech staff have no idea what to do. I don't have the log file on me, but if you need it, I can post it (they're pretty long, but seem to be detailed up until the connection part which just flops between CONNECTED and DISCONNECTED).
Is this a problem with the modem or the roms themselves? I was going to wait until the nougat kernel blobs got integrated to LOS, before trying again as I don't want to use the experimental build because it's a month old now. This problem has been around since at least January of this year. If there is a non-los based nougat rom, I would be glad to try that too. otherwise, I'm at a loss and I need some direction.
Any help is appreciated!
Seeings as how all of our Nougat ROMs are a mixed bag of partial MM and part Nougat still, and all custom ROM's for the MXPE use LoS's device tree, I am thinking this is a ROM issue, probably with some binary blob we don't have yet. The kernel source just released a few weeks ago, give it time and custom ROM's will get better (we think), and if the MXPE ever gets official Nougat, we will probably have better binary blobs too.
If it works on stock Marshmallow, it obviously isn't a radio thing, because your Nougat ROM's use the same radio firmware.
I don't have much else to say, but I would try a custom Marshmallow ROM and see if it works... if it fails as well, the problem is something in the LoS core device tree and it will need some developer's special attention (good luck with that, since we are considered to have a stable device tree it takes some work to get it changed), but if it works, chances are good that once custom Nougat ROMs get updated more it will likely work.
In a last ditch effort. I tried flashing the experimental build after posting this article, and it actually works! Now, this isn't the ideal situation given that there are some bugs (that I haven't run into yet) and that this build is a month old now. But for now, I'm satisfied. I just hope these blobs get integrated to official LOS soon.
Progress on that is here: https://review.lineageos.org/#/q/project:LineageOS/android_device_motorola_clark
If there are any roms out there that are considered stable and have these implemented now, I would appreciate it, otherwise, I think I'll be set for a little while. Thanks for your help!
Dear fellow developers and users of this great device,
I'm working on mainline support for the p4note device family, I started with the N8010 but this is usable on all the other N80XX devices as well as they are technically all the same aside from the modem.
The current status is that an initial device tree will land in 5.11 with some components still missing but its a good start. I'm working on the rest and also I'm working on Android 11 on top of that.
This post will not be updated any longer, you can find my mainline progress here.
There is also a blog which I'll probably woefully neglect as I'm way too busy with everything in life.
Cheers
An update for my mainline progress, there is kernel logs on the display now! I'm currently working on the touch screen config.
Oh Nice to see.
But i think not many people read the General forum anymore ^^
You might want to mention this in the Dev thread.
Do you have a git repository anywhere? I found a Note 10 8000 hidden in a box and wanted to get a working small working terminal up on the wall at my 3D-Printer/Soldering-workstation, I would be happy to be tinkering around som with the code.
Nevermind, found it.
fldc said:
Do you have a git repository anywhere? I found a Note 10 8000 hidden in a box and wanted to get a working small working terminal up on the wall at my 3D-Printer/Soldering-workstation, I would be happy to be tinkering around som with the code.
Nevermind, found it.
Click to expand...
Click to collapse
Hey, great to hear that you want to tinker with it. Remember that I currently work on rev 6 of the hardware, the version info can be found in the atags of the kernel log. You may run into issues with other revisions but it should be fine.
For the wifi settings, you need the correct nvram file. I'm not yet sure whether you can determine it by the version of the hardware, the current way is a macloader in the current hardware repo.
I extracted the touchscreen firmware from the sources and put them in my buildroot repo. The driver will look for a file called maxtouch.fw on boot.
I hope this helps.
Thank you very much for the pointers, I haven't t really been into kernel development since Samsung Galaxy S2 (9100), but getting a proper Linux installation on this device would fit me perfectly so I would happily try things on my side, keep us posted.