Hi there,
I'm still using our beautiful Galaxy phone. But as the new year has started some strange things happened to my phone.
It will no longer notify me when the screen is locked. So no reminder and no alarm clocks(!).
Every time I reboot, the year is set back to 2010. But the time is unchanged. (Time would reset too if internal battery clock is dead)
I can "fix" above bugs, when I change the current date to something before the year 2016.
For me (as a programmer and hacker) it looks like the internal hardware clock is not sending interrupts to the CPU when the year is greater than 2015. This means: No alarms/notifications and not even screen locking after screen timeout. And if some alarm is pending and I wave my hand just above the proximity sensor (above the screen) it will trigger some "wake-up" event and the notification/alarm will pop up.
Is anybody else experiencing these issues? And on which ROM are you running?
I'm currently on CM7.2 alpha MTD. I'm still hoping this is software related...
I can confirm the behavior. After reboot it's set to 2010 and the alarm is ringing too late or not at all... Everyone was afraid of the '2k bug' (the older ones will remember) and nothing happened... Now obviously planned obsolescence by Samsung - it's not a bug, it's a feature. My next Phone won't be made by SAMSUNG...
Thank you for the confirmation.
What I tried so far: (As the hardware seems to have a problem with the year '2016' I searched for ways to fake this date for the system and set the hardware clock back to 2010)
Privacy tools like XPosed/XPrivacy don't have the option to fake date or time for apps.
There is a library (libfaketime) that can fake the timestamp for linux processes (like the android system, which is just a process on the underlying linux). I failed to cross-compile this application because of missing library functionality (librt, libpthread, ..) on our phones. Or maybe I'm just missing something here.
I checked the kernel source for our CM7.2 MTD version on github. Maybe we can ask @marcellusbe to point us to the lines that read the timestamp from the hardware and mess around with this value. Or maybe, because he coded a lot of things, he knows better whats wrong with the year 2016 on our phones.
To have a working alarm clock I set the date back to 2015 before I go to bed. But for the notifications while the phone is locked we need something different ...
I also tried different years while testing if the screen would lock after the timeout:
Code:
1970: yes
1980: yes
1990: yes
2000: yes
2010: yes
2015: yes
2016: no [since 2016-01-01 00:00 UTC]
2020: no
2030: no
2033: no
2034: yes [since 2034-01-01 11:00 UTC]
2035: yes
So if we have enough patience we'll be able to use the phone without problems again. .. well maybe we've got other problems then
tried to switch to 1960 - didn't work
I thought its only my device having this bug, I am on stock Froyo. Its really irritating.
Just a quick update here... You can find the development related questions here.
I compiled the (CM7.2 MTD) kernel with a fix that changes the communication with the hardware clock. It's now running on my phone without problems, alarms and notifications are working again. BUT: the graphics driver screw up somehow while compiling. That still needs to be fixed ... So stay tuned
Here is the updated kernel for the CM7.2 MTD ROM. That was some pain in the ... So, have fun with this one.
Since the hardware clock "thinks" it's the year 2008 (subtract 8 years from true time), this should work until 2023-12-31.
clock
Hello, i have stock JPU(2.2 Froyo) rom and it worked fine till 1.1.2016. I flashed JK1(2.1 Eclair) and clocks working fine.. Can someone experienced look at it and compare, if its posible, and make a fix for stock JPU? im total noob, so if its not posible then tell me please. btw is that "feature" made on purpose by samsung or its just a bug? and please can someone explain to me more what is actually wrong? once more, i dont know anything about programing or android but im curious. thanks for reply, and sorry for my english and hijacking this thread.
Wade23 said:
Hello, i have stock JPU(2.2 Froyo) rom and it worked fine till 1.1.2016. I flashed JK1(2.1 Eclair) and clocks working fine.. [...]
Click to expand...
Click to collapse
That is some interesting behavior. While I was working with the source code of the kernel, I was 99% sure that this is a hardware bug.
So, I try to explain it more noob-safe for you: You have this phone. This phone has a processor. That's the one that runs at 667Mhz (not overclocked) and is your main processor. But that is not the only one inside your phone. But it's the only one that runs Android with the underlying kernel. Your phone has some more processors, like the camera, the USB connector, your baseband chip and of course the clock. These "processors" (or simply "chips") cannot be modified. So they can only do the job they are designed to do. (You cannot get your camera processing chip to calculate prime numbers. This chip can only pre-process camera signals)
Your main processor can interact with these chips. This is obvious, your phone depends on this. Because everything in your phone is connected to the main processor somehow, you can access all chips and tell them to do something. In your source code, you write something like: "Hey processor, write these bytes to this chip, please, and tell me what it replies" or "Hey processor, please read this information from that chip". That happens when you write or read from the internal hardware clock. ("Write that time" or "Read that time"). But because this is some low level stuff, we read each time component individually. So second, minute, hour, day of month, month and year.
This hardware clock has also the task of notifying the main processor at a certain time. That's what developers call "interrupt". Imagine you lock your phone and it goes to sleep. The processor calls the clock: "Hey mate, wake me up tomorrow at 08:00 AM" - clock: "Alright!". The processor then goes to sleep, because processors like to sleep. At 08:00 AM, Clock: "Hey processor, it's the clock. Wake up". Processor: "Yo, nice. I'm gonna check what tasks are due and do some work...".
But here lays the problem: Whenever the kernel updates the time on the hardware clock (Only happens when you change the time in the Android settings) the hardware clock does not save the year "2016" properly. So when the kernel reads the time it ends up with the year "2010". The Android system itself keeps track of its clock, so it will never be a problem showing you the correct time. But it gets a problem when your phone is sleeping and it should notify you at some point. The point is: It won't notify you.
And here is why I'm sure it is a hardware bug:
There is nothing magic about this clock driver. The source code for this driver was initially developed by Samsung, but is now online and part of the linux source code. It simply reads and writes the time components to their corresponding place. And because it is only the year that gets messed up, there must be something wrong with the way the chip handles the year.
What you can try:
Set up an alarm to ring in 5 minutes. Put phone in flight mode, disconnect USB, disconnect WiFi. Lock phone and put it somewhere you won't touch it. Wait. If it won't ring, leave it there for 2 more minutes.
Can someone experienced look at it and compare, if its possible, and make a fix for stock JPU?
Click to expand...
Click to collapse
I looked at the Froyo source and the driver is the same. I patched the source for the Froyo kernel. The *.tar file is attached. Use at your own risk. I have not tested this one! If phone won't boot, flash back the original ROM/Kernel! Flash the tar file only if you're sure the original ROM contains a kernel. If you're not sure, don't flash!
I also attached the patch if someone is interested.
and sorry for my english and hijacking this thread.
Click to expand...
Click to collapse
No worries.
wow, really long reply.. really thanks for explanation.. ill try that on weekend..
another question arised in my noob head.. .. what is in that zimage? can i use zimage from 2.1 rom where clock working fine for 2.2?
Wade23 said:
wow, really long reply.. really thanks for explanation.. ill try that on weekend..
another question arised in my noob head.. .. what is in that zimage? can i use zimage from 2.1 rom where clock working fine for 2.2?
Click to expand...
Click to collapse
I think you mixed something up. A fully-packed ROM normally contains a Kernel and the platform (the Android system). The kernel is either provided as a zImage or as a boot.img file. A kernel can only work with certain platforms and platforms can only work with certain kernels. The zImage I posted some weeks ago only works with the CyanogenMod MTD version.
The zImage I posted today is build from the original source downloaded from the Samsung homepage. This kernel will only work with Android 2.2 (Froyo). Well, I don't know if the kernel runs, I couldn't test it. So zImages should only be used with the ROM they are shiped with.
Maybe tell us what files you use to flash your 2.1 (Eclair) and 2.2 (Froyo) ROM. And maybe what files are inside the archived (*.zip or *.tar) file. I'm asking because if the zImage I uploaded is not working, you need to reflash a working kernel. Some ROMs don't have a kernel included (only the Android platform) so there would be no way to get the phone working again (with Froyo). You can of course flash a CyanogenMod version (or any other ROM) at any time, so your phone won't be broken forever
And: Did you tested the alarm thing. Because I'm still quite sure this is a hardware fault that should be present in all ROMs.
i was using I5800XXJPU (2.2) till problem apear, then after testing another 2.2 and many factory resets and wipes still doesnt work, then i flashed I5800XXJK1 (2.1) and alarm working like a charm.
all firmwares i tryed are from this thread, flashed with odin as single image.
Wade23 said:
i was using I5800XXJPU (2.2) till problem apear, then after testing another 2.2 and many factory resets and wipes still doesnt work, then i flashed I5800XXJK1 (2.1) and alarm working like a charm.
all firmwares i tryed are from this thread, flashed with odin as single image.
Click to expand...
Click to collapse
I just checked these two ROMs and they both contain a kernel. So, you're safe
Do the following:
Flash the 2.2 ROM (I5800XXJPU) with Odin
Let it start. Then turn phone off again.
Just like your ROM, flash my zImage_froyo_fix.tar as "One Packge" in Odin. This is only a kernel, build from the original source but with a fixed clock driver that works with 2016.
Because this kernel is quiet a bit smaller than those in the ROM-files, don't expect too much. Most likely your phone will get stuck in the boot process. If nothing happens after 5 minutes:
Flash the 2.2 ROM (I5800XXJPU) with Odin again. (Only when my kernel fails to start)
I'm still curious what they did in the Eclair (2.1) kernel. But there is no source available, so we will never know :silly:
Related
EVOLUTIONX2
UPDATE-EVOX2
Alright this is just an updated X. i had alot of ideas in mind but i cant get them to function properly. Just as many updates in the V series were small, they led to bigger things. with source and everything this week it has been hard to stay focused on one rom. X3 will be a completely new beast. so for now pick V or X series. they work the same
END----------------------------------------------
EVOlutionX-This is a DroidX themed Froyo. its as reliable as V8 but now it has alot of motorola elements. i started Seem editing moto razrs so im going back to the beggining .
i recommend wiping everything then Flashing. IF you have V8 or Hero_overs rom, you might not HAVE to wipe because its froyo over froyo but if you experience problems, wipe then flash
This is a very visual rom. i love it so far. If you dont like it just restore your V8 or w/e. This is a new series of froyo roms so i will continue updating this with the V series.
New-Wifi-tether
sprint tv
all red
new bootscreen
new launcher
new live wallpaper
new market
new icons**
new froyo leak
wireless N
Ability to flash OC kernels
lots more!
EVOlutionX2
So enjoy it.
New Series Changlog
-EVOlutionX-Droid theme. million extras.
-EVOlutionX2- Revamped everything. much faster, smoother.
============================================================
EVOLUTION V9
Alright EVOV9 is based on FRF85B and has the Evo update applied. it fixed alot of little problems. Much more stable and smooth. This is considered very beta as the new updates kill alot of things, it was hard to get it right. 35+ test roms actually. I will be updating as problems are found. but the only things that are not fixed are mms, BTmono, cameras. everything else should work. I recommend a wipe coming from anything, but as always it may not be 100% needed coming from another froyo rom.
Please enjoy EVOlutionV9
EVOlutionV9
Quirk- some people may get no sim card inserted at google login. just click back and it will fix it. this is one of the issues i have fixed but i will address them at a later time.
I will be adding patches, one for MMS fix and another with a white taskbar incase you dont like the black one.
You must flash coming from any rom. Go to market and download TITANIUM BACKUP. click (problems?) and install busybox. after that push menu and select batch. BACKUP ALL USER APPS. when its done you will then have all your apps backed up. then install rom, rinse, repeat.
for people who dont want use this because of cameras, i posted this up and i guess people dont think about it. Nandroid backup your 2.1. after its done wipe everything, flash this rom, set up the 2.2 rom to your liking, titanium backup works on froyo, and nandroid backup this rom. nandroids are sorted by date so just remember the earlier one is 2.1. you can rename but people say it messes up sometimes. then use froyo when you dont need cameras, and just wipe dalvik and restore 2.1 when you do. thats what i do and i love it.
Working-A2dp BT
Some mono headsets.
Wifi
GPS
Phone
SMS
MMS-Handscent
Video player
Lights
JIT
Market
Not Working-
Cameras i am still in testing but i have not done all the tests yet so theres still hope
Changelog-
Froyo test 2-toasts current release.
Froyo test 3-Changed around xmls for mag sensors(accident) Fixed Bluetooth HW issue so now it starts and pairs. Fixed wifi reconnect issue.
Froyo test 4-Fixed all sensors. lights stay on for right now. Wifi works, Gps works, Bt works, no a2dp. 4G now works but no app to use.
Froyo test 5-Based on different froyo leak. many many changes. new boot.img. fixed bluetooth 100%. should fix bootloop
Froyo test 6-Completely Deodexed. more refined. no cameras same things apply from before but its more stable now. and now we can customize.
Froyo test 7-Cleaned up everything. Fixed lights and sensors. fixed market. added more BT. fixed roaming. fixed launcher lag. Overall much much faster. Haptic is still low to keep other fixes.
New changelog-
EVOlutionV8-Went back to V5 framework and apks. Fixed led, estrong file manager<jackedfromflipz>,fixed wifi issues, 3G issues, Better memory managment, added sense clock<fancy widget>, 100% FULLMARKET, fixed roaming, decreased JIT threshold for faster waketimes, improved stock audioEQ, Fixed news widget refresh, fixed GPS lock-on, fixed mag sensors.
EVOlutionV8RevA+B-added newer froyo, and oc ability
EVOlutionV9- Fixed all the little issues. Now based on newest leaks and added the evo updated files. Theme by nexus devs. The only things that dont work now are cameras, mono BT, and mms. mms should be fixed this week.
enjoy!
Recommendations- i want to include this as i know how it is just starting android rooting. when your start flashing roms, the first thing you do is look for flaws. now these little things kept me from going to roms. the biggest problem i forget is that there are apps out there that can replace the small ones.
Handcent-Ultimate msging app. i suggest you download this, go into the stock msg app and disable notifications. this will help with Voicemail issues.
Rootexplorer- you must have this. it is one amazing app
Better keyboard- the stock skin on this beats anything i have used. i recommend this app also.
Titanium backup- USE THIS AND BACKUP ALL APPS WEEKLY!!!
i will add to this as i continue. and one very very important thing, i got my htc hero in november. i didnt join XDA until january but i downloaded roms from day1. leave comments!!!! as a developer the most important thing is not how many people use your rom or how much money you make. its all about you all telling us you love our rom. theres no greater feeling than sitting down for 6 hours at a time and fixing issues and hearing thanks. so this is just something to think about thanks for the support everyone
Credits-Toast for first build!!! Without that i would be working on something else
Credits go to the the nexus forum where i got the icons
-thanks to the dev who found wireless N
-anyone i forget, i do not in any way shape or form want to take away from other developers. if i forgot you please pm me and i will include you and get you the credit you deserve.
great work, I downloading , will report back when done.
looks like fun, hopefully froyo is ported over before its official evo release
Running well.
Good work.
as stated above. please list in detail EVERY problem you find i will go threw and try to fix what can be fixed.
starting with BT. tell me what profiles do and dont work. i know a2dp doesnt but lets see about the others
thanks!
Not able to download from link.
Testing right now. I have to root with Toast. I'll report.
Nice work, getting closer to a stable froyo, will try when a get out work and report back with problems that I find.
yea.. 4shared isnt letting any browser download it.. I wait 90 seconds.. then the link comes up and then it re-counts down 90 seconds..
tyrnight said:
yea.. 4shared isnt letting any browser download it.. I wait 90 seconds.. then the link comes up and then it re-counts down 90 seconds..
Click to expand...
Click to collapse
1+
10chars
OP, thank you so much, i've been waiting for test 3 and didn't think it was ever going to come. if everything besides mms and camera works, you're about to get the biggest donation today. thanks once again man and i will post back results.
can someone mirror this? the link on 4shared is not working.
edit: i got it, nevermind.
p-slim said:
can someone mirror this? the link on 4shared is not working.
edit: i got it, nevermind.
Click to expand...
Click to collapse
Still not working for me, did you do anything different?
If not do you think you could mirror it somewhere, 4shared is being a pecker head.
theoottesen said:
Still not working for me, did you do anything different?
Click to expand...
Click to collapse
after the countdown, i waited about 30 seconds before clicking the download link. I'm stuck in the infinite boot loop, and i factory reset, wiped cached, and wiped davlik cache.
p-slim said:
after the countdown, i waited about 30 seconds before clicking the download link. I'm stuck in the infinite boot loop, and i factory reset, wiped cached, and wiped davlik cache.
Click to expand...
Click to collapse
Ok I'll try that, let you know what happens.
Link is still not working...ugh
Confirmed.. dont know why.. but waiting 30 seconds worked
can anybody get this rom to load? i'm trying to give some money away but i've done everything and am stuck in this infinite boot loop. I can flash another rom but i want this one.
p-slim said:
can anybody get this rom to load? i'm trying to give some money away but i've done everything and am stuck in this infinite boot loop. I can flash another rom but i want this one.
Click to expand...
Click to collapse
Damn me and my impatience, tried it again and bam, it worked.
Thanks for the ROM. Here are 3 problems I am incurring:
1. Can't pair with bluetooth device.
"There was a problem pairing with LG HBM-570 because the PIN or Passkey was incorrect." The problem is, android doesn't pop up a keypad for me to type in any PIN. Then when I hit the back key, I get an error message:
"Sorry! The application Settings (process com.android.settings) has stopped unexpectedly. Please try again."
2. Screen auto-rotate to landscape doesn't work at all. I tried in Messaging and the Browser. The setting Auto-rotate screen is checked under Display setting.
3. Proximity sensor doesn't work. When I'm on the phone the screen doesn't turn off automatically.
Other than that everything else seems to be running fine. The LED light goes away when I unplug, finally! I also updated the eri.xml to get rid of the roaming indicator. I will post updates as needed. Thanks
theoottesen said:
Damn me and my impatience, tried it again and bam, it worked.
Click to expand...
Click to collapse
have you gotten the rom to actually load? i get stuck in this infinite boot loop. I flashed another rom and it booted up right away. i flash back to this and i'm stuck. I tried wiping everything including dalvik cache. any ideas?
I wanted to post this in the development section as feedback for garyd9's revised kernel for the P6210, but since I am new with fewer than 10 posts, I cannot do so. I PM'd Gary, he suggested I post it here. So here it is:
I have a P6210 and installed your custom kernel_20120101 and it worked beautifully. The tab was very stable, and battery life is better, as you indicated. I then installed kernel_20120105, and the tab immediately started having sleep of death problems. I would shut off the screen, set it down, and next time I came back to it, I had to do a hard reset by holding the power button ~20 seconds and reboot it. This happened consistently. I then tried kernel_20120107, and had charging issues. The tab got very warm while charging from the AC adapter. Uncomfortably warm. I have no idea if this was related to the kernel update, or just a one-time fluke. I am just relaying my experience. Anyway, the heat freaked me out, so I immediately downgraded back to kernel_20120101, and my tab is completely stable again.
Thanks for the work you do on this.... They are cool devices, and it's nice to be able to play with them.
Thanks.
Click to expand...
Click to collapse
I want to add that I am not running setcpu...
I'm willing to try the newer kernel updates again, or provide any other info Gary may need.
Thx
Can you check which version of the samsung firmware you are using? Does it end with "KL1" or something else?
I'm wondering if it might have been a bad flash or some other fluke. Here are the differences (with comments) between the 1st and 5th:
android ram_console support - this could do something unpredictable, but shouldn't. Basically, what this does is on boot up, it asks the kernel to reserve a VERY specific location and size of memory, and writes kernel messages here. On the next reboot, the kernel will check that exact chunk of memory and if certain headers are in place, it will stick a copy in /proc/last_kmsg. In this way, I might be able to see the kernel messages (including any panic) from the previous boot. Of course, the memory often gets trashed between the two boots, so this doesn't always work. Anyway, if something else is trying to use the exact same memory, it could cause problems (but it would cause the same problems for everyone with the same model tablet...)
bootanimation: This isn't actually a kernel change, but a modification to the init script that checks to see if a bootanimation file is present and if so it'll run samsung's own "bootanimation" binary instead of samsung's "samsungani" binary. In either case, the process is killed when the lock screen is first presented.
conservative governor stuff: As you aren't using setCPU, you are still using 'ondemand' so this stuff would have NO impact.
---
Honestly, the issue reported kind of surprises me. The kernel I'd expect to give people problems would be the 0101 one, as I mess with clock speeds and voltages in there. Since then, the changes have been very light. Can you try to delete any copies of Jan07 you might have sitting around, completely redownload it, and reflash it? Let me know if you have the same (or different) issues.
If you do have issues, use the market app called "OS Monitor" to export the dmesg log (while you are having the issue or immediately afterwards, but before rebooting.) Upload the exported log here (or somehow get it to me) with a full description of what was happening, if it was occuring during the time you exported the log (or how long previous to exported it occured), etc.
At that point, go ahead and revert to whichever kernel you are comfortable with and I'll study the log and try to see whats going on over the weekend.
Take care
Gary
Gary,
I flashed "GT-P6210 for US RETAIL" from this thread:
http://forum.xda-developers.com/showthread.php?t=1367478
Here's a screencap.
http://woodsware.aciwebs.com/galaxy_capture_01.png
I'll try the 20120107 kernel again, and let you know. It may be tonight....
Thanks!
i flashed the new kernel last night, and i haven't really had a chance to test it, but i did do some reading on the SOD deal, and i have my wifi set to "sleep when screen off" and i left home an hour ago, just pulled out my tab plus and BAM, fired right up.
I did want to ask you one request, any chance of implementing "smartassv2"? i'm gotten so lazy and spoiled with it...i never got around learning how to set profiles and junk, so this always helped me out...
rswoods said:
Gary,
I flashed "GT-P6210 for US RETAIL" from this thread:
http://forum.xda-developers.com/showthread.php?t=1367478
I'll try the 20120107 kernel again, and let you know. It may be tonight....
Click to expand...
Click to collapse
Okay, that's the older KK3 firmware. Here's what I'd like for you to do (if you could):
1. reflash that from the ODIN thread. That should revert recovery, the kernel, etc. Then attach your tablet to your PC and let Kies run to update the firmware to KL1. It would really be best if your firmware was updated BEFORE changing kernels. There are a couple reasons for this, but most importantly so that we are talking about the same thing (I've only ever tested these kernels with KL1.)
2. Make sure Kies has updated your firmware... settings->about->build number should show something like HTJ85B.UEKL1.P6210UEKL1. If Kies updates the firmware to something beyond "KL1" (if the number is greater than 1 or the last letter is beyond "L") then STOP, reply to this post letting me know the build number. (I'll want to revert my own tablet to stock and get it on the latest build for testing.)
3. Then go ahead and start playing with kernels - you will hopefully be good to go. if not, let me know.
Take care
Gary
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
Thedonk13 said:
i flashed the new kernel last night....
Click to expand...
Click to collapse
Please post this in the proper thread (in the DEV subforum.) I asked rswoods to post his question here in general as he can't post in DEV yet (doesn't yet have 10 posts), but I wanted the "public" to see the troubleshooting steps in case others have similar issues, etc. (I can't complain that people aren't searching for answers if the answers are hidden in PM's.)
Oh, and probably not. The same can be accomplished with SetCPU profiles, and I'm working hard to REDUCE the kernel footprint.
Take care
Gary
Gary,
OK... I reflashed the stock ROM, updated to KL1 through Kies, installed p6210_CWMR_20120107.zip, then flashed your 20120107 kernel. So far so good.
I'll see how it goes the next few days and report back.
Thanks for the help!
Gary,
Things are mostly good, but I'm still getting infrequent SOD's. I never know when it will happen... It will wake successfully several times in a row, but every once in awhile require the long press reboot.
rswoods said:
Things are mostly good, but I'm still getting infrequent SOD's. I never know when it will happen... It will wake successfully several times in a row, but every once in awhile require the long press reboot.
Click to expand...
Click to collapse
SOD's are unsolved. The majority of people having them are using the stock firmware and kernel (and replacing the kernel with mine doesn't seem to help whatsoever.) There's a thread dedicated to the subject here - you might find it interesting reading.
I'm glad the other issues you were experiencing have gone away...
Take care
Gary
Things are running great for me.
I would post this in the Developer forum, in reply to a poster who has the same problem, but I just registered and therefore do not meet the requirements to post there.
I'm wondering if anyone else has observed this behavior. In short, I installed TriForceROM 3.0 (after performing a "Wipe User Data" operation in TWRP 2.6.0.0) and all was well for about 12 hours. During the ROM installation, I chose the "Standard" option, as I believe it's called. (I didn't elect to customize anything.)
After 12-18 hours of having the ROM installed, I noticed that my phone was simply powered-off. I hit the power button and nothing. Then I held-down the power button, which is how I normally power-on the device, and then realized that the device was, in fact, powered-off when I came back to it after a few hours of being in the other room.
After powering-on the device, the same thing happened a few hours later, and the issue seems to be occurring more and more frequently as time passes.
I have not changed any of the ROMs settings, and I haven't installed any type of third-party "tweaking" app.
Another individual has the same problem:
http://forum.xda-developers.com/showpost.php?p=43942167&postcount=1466
Could this be due to kernel, power, or CPU settings? I noticed that when I opened KTweaker for the first time, the application warned me:
"Your KThermal values do not match current, Apply values?"
and
"Your vibration Strength does not match current, Apply Vibration Strength value?" (this one seems unrelated)
The CPU temperature seems to hover around 45 degrees Celsius. (Is this a normal range?)
Another observation is that when I long-press the Home button (to bring-up the app-switcher), I see a little Android icon with the title "MIPErrorActivi...". If I click on it, I'm simply dumped to the Home Screen. I don't know if this is at all related.
Thoughts or suggestions, anyone?
My phone is model SPH-L720.
Thanks in advance!
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
DrRichardQuack said:
I went into KTweaker and clicked "Load Defaults" and rebooted, and everything seems to be stable. No reboots in 18 hours or so.
Also, the ROM author has mentioned this issue, as well as an interim fix (related to the KT kernel), and says that he will release v 3.1 within a few days, which should fix the issue entirely.
Good stuff!
UPDATE:
Well, the phone rebooted itself, eventually, so setting KTweaker settings to defaults was not the solution.
However, I downloaded the kernel update that the ROM author suggested ( http://forum.xda-developers.com/showthread.php?t=2288309 ) and that does seem to have fixed the problem. No reboots in over two days. Yay!
An interesting aside is that with the new kernel and accompanying KTweaker app, the warnings that I was receiving with the old kernel when launching KTweaker disappeared. All is well!
Click to expand...
Click to collapse
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Lsd-Pulsar said:
Thanks for noting this. I actually started my account for the same reason, but haven't had enough useful input to get the posts to leave feedback in the dev forums. I sure don't want to spam useless posts :angel:
Click to expand...
Click to collapse
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
DrRichardQuack said:
Haha. Well, glad I could be of help and that we both garner a couple of "useful posts" out of it.
I'm pretty sure that the reboots continued for me (although, less frequently with the kernel patch in place), but upgrading to TriForceROM 3.1 seems to have fixed the issue altogether. It's worth noting that I chose a different kernel this time (I forget what it's called; the name is four letters, all capitals). No reboots in the first 24 hours.
I doubt it makes a difference, but I also upgraded to the MF9 firmware from Samsung. Happy to answer any questions in that regard, too.
Click to expand...
Click to collapse
I would wager that you moved over to AGAT's. Several users reported lag with that kernel, so I stuck with KT.
After more reboots and a lot of tweaking, I've got my issue nailed down. Raising the voltages on the low end cpu frequencies (where a phone would normally be with screen off) has corrected the stability issues. I also had to up the voltages at the high side. That helped Antutu to run for a while, but now that's crashing back to desktop for me. When it does run, I usually hit around 25,000 with the Triforce 3.0 + Ktoons kernel with overclock enabled. I have not overclocked the GPU (yet). Running KTmod, but not crossbreeder.
I may back this all up tonight and reflash with Triforce 3.1. I've been fighting battery issues: Google Location Services and Android Widgets Pro seem to be behaving badly.
I feel like I'm very close to a fast, stable rom install with good battery life. Once I get there, I'll wait a couple months until the existing ROM's and kernels are polished a little more. And now I'm one post closer to being productive in the Dev forum.
That's the one; AGAT's kernel. I haven't noticed any sluggishness with the ROM's (and or kernel's) default settings. So, I'm happy!
No random power-downs or any other abnormal behavior since upgrading to 3.1 and switching to AGAT's three days ago.
I don't know if it was upgrading from 3.0 to 3.1 or switching kernels that fixed the random power-downs; I'm just glad I have a very fast and stable ROM at this point.
My battery life has been good. Moderate usage throughout an 8-10-hour work-day leaves me with about 70% battery when I get home.
My hat's off to the developer. I think I'll kick him a few bucks.
Hello World,
I recently purchased a SGN 12.2 Pro - Model Number SM-P900.
I flashed CyanogenMod onto it, and now its Android Version is 5.1.1
The CyanogenMod version is 12.1-20151104-Unofficial-v1aWIFI
The kernel version is 3.4.104-gd233b3f
Now for the most part the system runs smooth and w/o problems, but 7 or 8 times out of 10 when it goes asleep (screen is off and no program is actively running in the foreground, but the system was not shut down), I can not wake the tablet back up again.
Matter of fact, I end up having to perform a hard reboot on the tablet (pressing the power button until I force a reset) to get it to respond again.
I ran a logcat session in the background to catch any error, but the recorded log did not any error when this happened. It just suddenly stopped recording.
For me it seems like the system is going into some sort of hibernation mode, from which it only awakes after a hard reset.
But I don't see any such setting as "hibernation" in my system panel, and I certainly didn't install any such program on my tablet.
Now I am getting afraid that I might end up corrupting the filesystem or some important database by forcing these hard resets all the time.
That is why I need to find out what's going on here - anyone got some constructive ideas about it?
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
ShadowLea said:
To rule out any potential hardware issues, you might want to try seeing if the problem occurs on stock as well.
Click to expand...
Click to collapse
Nice idea, but I need the functionallity of CM, and I also rely on my tablet for work - so I can't play "flashaholic" here.
But I have upgraded my CM Firmware three times in a row by now, and if this is CM related, then all those firmware packages would have to cause the same problem - with me being the only one who suffers from it (because I didn't read anyone else having this problem in the CM comment threads).
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Osama chohan said:
Really? Cwm for functionality? Even Snote doesn't work in cwm thus for a note device cwm is waste of space although for devices without spen i recommend cwm as well and do you want your problem to be fixed or not if yes then flash stock firmware to check if it's software or hardware related.
Click to expand...
Click to collapse
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Masinissa said:
Those are pretty brazen and broadband condemnations of a custom ROM that has won many distinctions and is even considered by industry groups as a replacement for STOCK ROMs.
And since SNOTE is part of Samsung's most crappy Software Suite, I truly would not regard *that app* as a benchmark of quality.
Now do you have any links to confirm your loudmouthed dismissal of CM, or does that fall into the same category as urban myths such as "openSUSE isn't real Linux" and "Virus Scanners are useless"?
And by the way: CM = Cyanogen Mod (Custom Firmware); CWM = Clockwork Mod (Custom Recovery).
Not the same by a longshot - and I use TW for recovery anyway.
PS: I found a solution by now in installing an app which prevents the tablet from going into deep sleep mode (-> CPU_WAKE_LOCK). As it seems at times the tablet would come back online after some seconds, *if* I let go of the power button in time. But since I have the tablet hooked up to a power source most of the time anyway, I don't need deep sleep mode, and I was never good at counting seconds when pressing the power button.
That app resolved the "sleep of death" issue for me.
PS#2: As a systems admin I generally refuse advise of the kind of "just reinstall (flash) from scratch and see if it fixes the problem", for that is *not* debugging, its just being too lazy to perform root cause analysis.
Click to expand...
Click to collapse
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Osama chohan said:
You may be right but generally in samsung firmwares there are problems with the firmware itself...anyway...if you do find the root cause let me know although when I installed the cyanogen mod 12 this didn't happen I think it was a problem of wake lock in some early builds of rom. Have you experienced this after updating to latest builds?
Click to expand...
Click to collapse
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Masinissa said:
Hi Osama,
the problem startetd after I had installed some software tools for power management and activated CM's own CPU governor.
That is why I suspected this not be a case of a software loop caused by a program or Firmware bug, but a problem with the system waking back up from deep sleep mode.
Now I could have just uninstalled everything and disengaged the CPU governor altogether, but as I wrote earlier on, I don't think highly of such "let's reset it all to zero and see if at fixes things" approaches.
Also, I liked the battery savings options, I just needed a way to prevent the CPU from going all the way down into deep sleep mode.
I found that solution in the form of a small APK on the market place, which does exactly that - and only that.
It prevents the CPU from being turned off (CPU_WAKE_LOCK), whilst still allowing for the screen, bluetooth, WiFi and so on to be turned off, to save battery power.
That fixed my problem almost completely, and now it happens only when the app (I use RedEye) for some reason isn't auto-activated at boot.
Click to expand...
Click to collapse
I'm glad that you fixed the problem and sorry that i couldn't be of any help.
hello,
I'm having a problem with my G925F
it randomly freezes (sometimes) on any screen, mostly while playing games, until i force reboot it (vol down+power for 7sec)
ROM: the global elite 4.1
Kernel: ROM stock.
any help would be appreciated, i tried different kernels but still problem, is it a ROM problem or hardware?
UPDATE: I tried different Roms too, same problem..
when im with headphones and it freezes, it starts a loud sharp noise that'll rape your ear (that's how it really feels)
and some glitchy lines appear on the screen..
it stays frozen for like 5 or 6secs then it reboots itself with a white solid LED light...
pleas guys what's this problem???
anyone??? ☹
zinou111 said:
hello,
I'm having a problem with my G925F
it randomly freezes (sometimes) on any screen, mostly while playing games, until i force reboot it (vol down+power for 7sec)
ROM: the global elite 4.1
Kernel: ROM stock.
any help would be appreciated, i tried different kernels but still problem, is it a ROM problem or hardware?
UPDATE: I tried different Roms too, same problem..
when im with headphones and it freezes, it starts a loud sharp noise that'll rape your ear (that's how it really feels)
and some glitchy lines appear on the screen..
it stays frozen for like 5 or 6secs then it reboots itself with a white solid LED light...
pleas guys what's this problem???
Click to expand...
Click to collapse
Those glitchy lines are signs of hardware problems. Try flashing stock rom, if the problem persists, you'll know it's the hardware.
tiktakt0w said:
Those glitchy lines are signs of hardware problems. Try flashing stock rom, if the problem persists, you'll know it's the hardware.
Click to expand...
Click to collapse
I'm pretty sure its hardware too, but idk which part is exactly damaged?
i didn't drop my phone, water or dust didn't touch it in anyway..
the problem happens while playing PUBG Mobile or similar heavy games.
btw.. can battery cause such problems like this?
tiktakt0w said:
Those glitchy lines are signs of hardware problems. Try flashing stock rom, if the problem persists, you'll know it's the hardware.
Click to expand...
Click to collapse
It happened again, this time the device wasn't hot, no apps on background, no gaming, nothing. i was just on home screen swiping looking for an app, it suddenly froze. with those glitchy lines, rebooted itself with white solid LED light. i didn't use it for like 10min.. i came back again, unlocked it, swiped up for apps menu.. BOOM, froze again with those glitchy lines. this time it didn't reboot, it blacked out after 5sec.. i tried different button combinations to turn it on again, no luck. i plugged in the charger and waited for 2min, nothing. then i got into download mode [warning screen] (while plugged). i pressed the vol- button to restart, it booted up normally. now I can't really use it cause i don't want it to get worst. btw, sometimes when it freezes & reboot itslef, All settings are reset to default.
Any suggestions on what to do?
zinou111 said:
I'm pretty sure its hardware too, but idk which part is exactly damaged?
i didn't drop my phone, water or dust didn't touch it in anyway..
the problem happens while playing PUBG Mobile or similar heavy games.
btw.. can battery cause such problems like this?
Click to expand...
Click to collapse
I doubt it's the battery, but you'll never know unless you try. Glitchy lines or artifacts are usually the sign of a failing gpu.
tiktakt0w said:
I doubt it's the battery, but you'll never know unless you try. Glitchy lines or artifacts are usually the sign of a failing gpu.
Click to expand...
Click to collapse
okay.. but why it sometimes happens while doing nothing... and sometimes it doesn't freeze at all even while gaming for hours...
one more thing, when i shake thr phone near my ear, i hear something like (tick tick tick...). i taught that maybe that's it. but i asked my friend who has an s6e too (G925T) he said that he has that sound too when he shakes it, but doesn't encounter any problems with his phine... soo??
What I most associate with that sound, and the phone freezing... is CPU hotplugging. Are there any apps that affect these? /sys/class/devices/system/cpu/cpu./online
sys/class/devices/system/cpu/ whichever one isn't cpu 0-7 or cpuidle.
Bryan48765 said:
What I most associate with that sound, and the phone freezing... is CPU hotplugging. Are there any apps that affect these? /sys/class/devices/system/cpu/cpu./online
sys/class/devices/system/cpu/ whichever one isn't cpu 0-7 or cpuidle.
Click to expand...
Click to collapse
i have no idea.. how can I know which apps do this?
and what is CPU hotplugging??
zinou111 said:
i have no idea.. how can I know which apps do this?
and what is CPU hotplugging??
Click to expand...
Click to collapse
Which apps... maybe something related to "editing kernel settings", viewing CPU info (root), etc.
CPU hotplugging is the stopping (and returning when needed) of CPU cores (big cluster, etc), to save power, etc. When it fails, it does... that (maybe not the artifacts?).
/sys/devices/system/cpu/cpu[0-7]/online.
others related to CPU hotplugging...
/sys/devices/system/cpu/... ?
/sys/power/... ?
GPU hotplugging is /sys/devices/14ac0000.mali/power_policy (/sys/class/misc/mali0/device/power_policy). Writing "always_on" disables it, "coarse_demand" enables it, "demand" enables it. I haven't had any problems with this, only temperature reading.
Bryan48765 said:
Which apps... maybe something related to "editing kernel settings", viewing CPU info (root), etc.
CPU hotplugging is the stopping (and returning when needed) of CPU cores (big cluster, etc), to save power, etc. When it fails, it does... that (maybe not the artifacts?).
/sys/devices/system/cpu/cpu[0-7]/online.
others related to CPU hotplugging...
/sys/devices/system/cpu/... ?
/sys/power/... ?
GPU hotplugging is /sys/devices/14ac0000.mali/power_policy (/sys/class/misc/mali0/device/power_policy). Writing "always_on" disables it, "coarse_demand" enables it, "demand" enables it. I haven't had any problems with this, only temperature reading.
Click to expand...
Click to collapse
i don't have any apps of this kind, i used to have Kernel Auditor & Synapse in the past Roms cuz i was using custom kernels.. but now, im on stock kernel.
how can clear all kernel settings and start fresh?
however, it didn't reboot today. i was expecting it every time i use it. but no freezes or reboots.
zinou111 said:
i don't have any apps of this kind, i used to have Kernel Auditor & Synapse in the past Roms cuz i was using custom kernels.. but now, im on stock kernel.
how can clear all kernel settings and start fresh?
however, it didn't reboot today. i was expecting it every time i use it. but no freezes or reboots.
Click to expand...
Click to collapse
Kernel 'settings' are reset to the default (defaults may change after flashing a kernel) on reboot, unless there's a script (init.d, etc) that changes the settings on boot, or later. If it happens again, maybe the error messages are in /proc/last_kmsg.
Bryan48765 said:
Kernel 'settings' are reset to the default (defaults may change after flashing a kernel) on reboot, unless there's a script (init.d, etc) that changes the settings on boot, or later. If it happens again, maybe the error messages are in /proc/last_kmsg.
Click to expand...
Click to collapse
okay.. i flashed Aldeon this afternoon.
after booting, i installed Synapse. after opening it and granting superuser access.. it showed me the screen saying that kernel settings are reset ti default cuz system wasn't stable for 2mins after booting... this usually appear after it really happens...
its weird that it appeared after flashing the kernel directly...
no reboots or freezes so far, since yesterday.
zinou111 said:
okay.. i flashed Aldeon this afternoon.
after booting, i installed Synapse. after opening it and granting superuser access.. it showed me the screen saying that kernel settings are reset ti default cuz system wasn't stable for 2mins after booting... this usually appear after it really happens...
its weird that it appeared after flashing the kernel directly...
no reboots or freezes so far, since yesterday.
Click to expand...
Click to collapse
Hello @zinou111 how has your phone behaved after what you did? I am currently having the same issues you had and I'm looking for a solution.
Yours is the only hope after a couple hours of searching.
really? same symptoms as mine?
well... i didn't do anything at all... I turned it off and threw it for like 4 days... and last few days, i was bored, so i got it back and turned it on.. i faced this problem only 4 times within this week... i didn't do anything..
it used to be +10 times a day... now its just gone i think & i hope... it didn't freeze last 3 days & it works flawlessly!
i hope this can help you
Solution! And Cause!
I am not pretty sure uf it is a software or a hardware damage! But It can be :
1. After years of using your phone the battery power decreases and the voltage needed for cpus to work is not given anymore..
2. A permission file!
FIX for 1.:
- Install custom kernel(pos45) where you can change voltage
- Install Synapse or MTweaks
- Upvolt all values under 1000mHz to 800mAh in both big and small cores
- And youre done!
FIX for 2.:
- Install rom Ultimate Nougat S8+ Port v3.1
- This rom contains a fix for this issue!(I tested it it works!)
I recommend: Try FIX for 2. FIRST its more secure and dont blame me if you destroy your device!
ArkPly said:
I am not pretty sure uf it is a software or a hardware damage! But It can be :
1. After years of using your phone the battery power decreases and the voltage needed for cpus to work is not given anymore..
2. A permission file!
FIX for 1.:
- Install custom kernel(pos45) where you can change voltage
- Upvolt all values under 1000mHz to 800mAh in both big and small cores
- And youre done!
FIX for 2.:
- Install rom Ultimate Nougat S8+ Port v3.1
- This rom contains a fix for this issue!(I tested it it works!)
I recommend: Try FIX for 2. FIRST its more secure and dont blame me if you destroy your device!
Click to expand...
Click to collapse
thanks bro! but i don't think its a software problem, cuz i had it completely fresh & new last week, i mean the guy flashed it using those things called BOXs.. like.. i'm even getting OTA updates lol... still same problem..
but i left it like i said turned off for about 3 days & i can tell that it got better.... probably the CPU is failing i guess
i'll try the 1st solution when i face the problem again
Yes I can safely say...
zinou111 said:
thanks bro! but i don't think its a software problem, cuz i had it completely fresh & new last week, i mean the guy flashed it using those things called BOXs.. like.. i'm even getting OTA updates lol... still same problem..
but i left it like i said turned off for about 3 days & i can tell that it got better.... probably the CPU is failing i guess
i'll try the 1st solution when i face the problem again
Click to expand...
Click to collapse
Ok but I can tell you that for me both ways 1 and 2 worked! (S6 Flat by the way)
I installed the rom(Way2) and no crashes anymore without changing the voltages... On stock rom(odin clean installed) I still had random reboots and freezes!:victory:
But when you flash a custom kernel and changes voltages (Way1) also on stock no more random reboots!
So both ways worked try it out!
ArkPly said:
Ok but I can tell you that for me both ways 1 and 2 worked! (S6 Flat by the way)
I installed the rom(Way2) and no crashes anymore without changing the voltages... On stock rom(odin clean installed) I still had random reboots and freezes!:victory:
But when you flash a custom kernel and changes voltages (Way1) also on stock no more random reboots!
So both ways worked try it out!
Click to expand...
Click to collapse
okay man! that was really helpful! ill try it and keep u up to date!
thanks alot bro!
ArkPly said:
I am not pretty sure uf it is a software or a hardware damage! But It can be :
1. After years of using your phone the battery power decreases and the voltage needed for cpus to work is not given anymore..
2. A permission file!
FIX for 1.:
- Install custom kernel(pos45) where you can change voltage
- Install Synapse or MTweaks
- Upvolt all values under 1000mHz to 800mAh in both big and small cores
- And youre done!
FIX for 2.:
- Install rom Ultimate Nougat S8+ Port v3.1
- This rom contains a fix for this issue!(I tested it it works!)
I recommend: Try FIX for 2. FIRST its more secure and dont blame me if you destroy your device!
Click to expand...
Click to collapse
Hello
I dont understand this : Upvolt all values under 1000mHz to 800mAh in both big and small cores
Maybe have you a screenshot ????
thx