Database Info

EaglesBlood ROM Complaint

First of all, I know this is in the wrong section but that's because I have not made 10 posts yet.
Now onto the complaints and recommendations.
1. Lock screen is tedious. There is no way for the lock screen to activate. Even when I reboot, the phone just completely bypasses the lock screen. I don't even know how the developers have missed that. It is such a fundamental function and I can't even use it.
2. Home button loses functionality. My home button doesn't work. So every time I want to go to my home screen, I need to press "back" a million times. Fix it?
3. Create on-screen buttons. Like what the Genesis ROM has. You can choose to have Galaxy Nexus's digital buttons.
4. Quad-circle lock screen is cut off. You never fully see the circles when you selected one of the four. Do what Hellfire ROM did and make it a semicircle.
The first two are just deal breakers for me at times. But the only reason I have this ROM is that it is the only one that can call, and that's why EaglesBlood is pretty good. I hope the above recommendations/criticisms will be seen by the developers because it will greatly benefit many people. Thanks.

Your lock screen may be disabled under security settings. Have you checked that?
The lock screen issue, and particularly the home button, indicate that you likely have a bad flash. Redownload the rom and wipe, wipe, wipe, reflash. If this were a ROM related issue it would be expected that there would be at least one other mention of the first two issues in the ROM's thread. Bad flashes or downloads are not uncommon. Try again, see if they persist. And be careful restoring things through Titanium Backup.
Why would you want the digital buttons taking up space on the screen when we have perfectly functional ones?
I agree completely about the quad-lock.

everything besides the quad lock screen being cut off sounds like user error, and if you don't like it then use another rom... not trying to be rude as you will take this, but how many people report that the roms "home" button doesn't work? How many people post that there is no lock screen (and how did you see the lock screen being cut off if you can not see the lock screen? You can use any rom to make calls if you go to Owain's thread and get the "new_baseband" zip he created
all you need to do is properly install the rom or maybe redownload as it may have been corrupted during the download.

Just like ladygagadisco, I realize that this is the wrong section, but I don't have 10 posts yet... And just like her (I am assuming gender based on name), I have all the same troubles. And this is now the third time I have downloaded the ROM and installed it. So, I guess this question is directed towards her... did you ever get this fixed?
I will try one more time and hope like it hell that it works.
---------- Post added at 03:23 PM ---------- Previous post was at 03:13 PM ----------
Well it seems that the fourth time was the charm. The home button now works.

I'm running the GB EB 2.3.7 ROM and I think it's the best for my phone so far.
Being in Canada with Videotron I had issues with some other ROM's. I tried EB's ICS 4.0.4 ROM but for me not to be able to record Video (known issue due to NVIDIA not releasing drivers for Tegra2 for ICS) and not getting voicemail notification were a big deal for me so I downgraded to EB GB ROM.
I have not used or verified your option 3 & 4 but 1 & 2 worked in both EB ROM's I installed.

Do a full wipe. EB is the most stable former. No problems aside from the known bugs
Sent from my LG-P999 using xda app-developers app

T.O.S.
ladygagadisco said:
...(edit)... Do what Hellfire ROM did and make it a semicircle.
Click to expand...
Click to collapse
Creating secondary false userID's to flame others will get you banned from this community. I suggest you take this strongly into consideration and use better judgement.

[Q] Synergy r373 on vz i535

Haven't seen this topic covered in the Synergy forum, so I was hoping to hear if anyone knows of this issue and knows how to fix.
I have flashed the r373 ROM from Synergy a few times. I have a Verizon i535 phone. The ROM works great overall.
Did a Superwipe and using Ziggy Kernle and stock, i.e. non-selected, keyboard during install.
I find that during typing on the keyboard, in either Mail or Message, that once in a while the phone freezes for about 20-30 seconds. I cannon do anything in the mean time but wait. It seems to hold the cue of clicks, so that once it finally gets going, after 20-30 seconds, it flushes out the cue of clicks.
I have loaded this ROM (r373) twice and have the same issue. I tried one of the other keyboard options during the install, but same result.
Any ideas or help?
Otherwise, I love this ROM. Phenomenal battery life.
Thanks.

dgrigg said:
Haven't seen this topic covered in the Synergy forum, so I was hoping to hear if anyone knows of this issue and knows how to fix.
I have flashed the r373 ROM from Synergy a few times. I have a Verizon i535 phone. The ROM works great overall.
Did a Superwipe and using Ziggy Kernle and stock, i.e. non-selected, keyboard during install.
I find that during typing on the keyboard, in either Mail or Message, that once in a while the phone freezes for about 20-30 seconds. I cannon do anything in the mean time but wait. It seems to hold the cue of clicks, so that once it finally gets going, after 20-30 seconds, it flushes out the cue of clicks.
I have loaded this ROM (r373) twice and have the same issue. I tried one of the other keyboard options during the install, but same result.
Any ideas or help?
Otherwise, I love this ROM. Phenomenal battery life.
Thanks.
Click to expand...
Click to collapse
It's a known issue. Probably kernel related. No fix yet. Some have suggested changing the govenor from ondemand to somthing else like smartassv2. That seems to work but its more of a workaround.

corbn89 said:
It's a known issue. Probably kernel related. No fix yet. Some have suggested changing the govenor from ondemand to somthing else like smartassv2. That seems to work but its more of a workaround.
Click to expand...
Click to collapse
Thanks for the reply. I'm glad to hear that it is a known issue and not just some problem in the way I am flashing.
I'm not sure I follow you on how to attempt the work around with what you describe about changing the govenor. Where do I change these settings?
Where, or how, do I learn more about this?
Thanks again.

Also fyi, the lag isn't just in email and message. You could be doing anything and it'll just freeze for a bit. I get like 2 instances a day. I would switch the kernel if Ziggy's kernel wasn't so awesome otherwise.
Basically to get rid of the freezes, you could flash a new kernel - either stock or another 3rd party kernel like LeanKernel
OR (not sure if this second method works 100%)
you can change your kernel governor
Description of various kernel governors
Synergy's default gov. for the ziggy kernel is ondemand. To change it you can use an app like SetCPU or ROM Toolbox or you can use the synergy's toolbox feature. If you want to use the synergy toolbox, go into you recovery, flash the rom to start aroma installer but do not hit install rom. Instead, select the toolbox, change the governor, apply changes, then hit menu and exit. Then you can reboot your phone. You wont have to actually re-flash anything.

r443
corbn89 said:
Also fyi, the lag isn't just in email and message. You could be doing anything and it'll just freeze for a bit. I get like 2 instances a day. I would switch the kernel if Ziggy's kernel wasn't so awesome otherwise.
Basically to get rid of the freezes, you could flash a new kernel - either stock or another 3rd party kernel like LeanKernel
Click to expand...
Click to collapse
Updated to r443 reciently, with the Copy/Paste fix also, and this issue seems to be not occurring anymore. Just thought you might want to know.

[Q] Random power-downs in TriForceROM 3.0 on Samsung Galaxy s4

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.

Event0 wakelocks

Hey guys, lately I've been having the eventx-xxxx wakelocks that *seem* to keep my phone awake and drain my battery. These wakelocks are usually event0 ones and followed by a four digit number which I believe to be the Process ID.
The current wake lock I am having is event0-2012 shown by BBS. It changes on every so the PIDs are rarely the same. It also happens that the 4 digit number happens to be the process ID of system_server. So there's something that's keeping it awake.
Lastly, the event0 is the synaptics touchscreen. So I'm guessing that this event0 wakelock keeps track of all the touches you make on the screen. This problem only appeared after the new touchscreen firmware updates so that may be the cause. Anyone have any thoughts on this matter?
Screenshots for proof below
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

Alright guys I'm back to share what I have found after doing some research.
Right now I'm using ark kernel with liquid smooth 3.2 milestone
So back to these wakelocks, as it turns out, even though event0 was the most prevalent, most of the time it was on was while the screen was on, so basically you can ignore it.
However, there were two other events that I still had to investigate, event2 and event3. For me event2 is gpio_keys which are the button inputs. event3 is s2w_pwrkey.
First I deleted the event2 file under /dev/input. These files are restored on boot but I would still make a backup before trying this. After deleting this, my volume buttons stopped working, as expected. But my power button still worked. I used it for a couple hours but there was something that was keeping my phone awake still.
Then I rebooted and deleted event3. This is related to the sweep2wake that's implemented in alucard's kernel. I never use it anyway so I went ahead and deleted it. And what do you know, now my phone is sleeping like a baby and even the other events have gone down as well. But the problem is you have to delete the file on every boot. The solution? An init.d script with the following line. Where X is the number of the event you want to remove. You can also just add it to any existing scripts you might have in /system/etc/init.d
rm /dev/input/eventX
How to find out what's causing yours?
1.Download wake lock detector from the
play store and use it for a day
2.check under kernel wakelocks to see if
your phone is being kept awake by an
alarmingly high number of event
wakelocks, if so proceed.
3. Open terminal emulator and type the
following: "su" press enter after each
line
"ps | grep xxxx" where xxxx
is the number
following the event
wakelocks.
4. If system_server doesn't show up,
another app is causing it. Find it and
manage it. Otherwise, proceed.
5. Go back in terminal and type "su" enter
"getevent -c 1" this will give you all
of you events and and what they
are bound to.
6. Make a backup in recovery.
7. Delete one of the problem events and
see if your phone is kept awake, if it.
isn't then congrats! You found the
drain! Else keep testing.
8. Once your are certain which one it is.
Create an init.d or use an existing
one and add the line "rm /dev/input/
eventX" replace X with the event
you want to remove.
You're done.
If you have any problems or questions, I'll be happy to help.
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

Thanks alot for this thread, very helpful. :good:

i don't have wakelocks (using @ak kernel and enabled only dt2w) but very useful thread
5 star rated :good:

ak said:
Thanks alot for this thread, very helpful. :good:
Click to expand...
Click to collapse
Cool that means alot coming from you
wizyy said:
i don't have wakelocks (using @ak kernel and enabled only dt2w) but very useful thread
5 star rated :good:
Click to expand...
Click to collapse
Thanks! I've never had a 5 star thread before
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

I am on cm11s and have these same wake locks but all are less than 10 on so far a days worth of battery time. I don't think it's much of a problem for me and probably more for cm12? Anyways thanks for the info now I know where to look if it ever becomes an issue
Cheers

i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.

tracerit said:
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
Click to expand...
Click to collapse
Agreed, it only started happening recently and I haven't installed any new apps, but newer Roms and kernels. So I really don't know whats causing it
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

tracerit said:
i've been getting these crazy same wakelocks the last week as well, which is weird because i didn't get them the two weeks before that when i got my phone. And I've been flashing ROMs (Mahdi, SlimKat, Lollipop) and kernels (stock and AK) back and forth. Even after settling on Mahdi with a clean flash, they're still showing up. THanks for your investigation, I'm going to check things out when I get home tonight.
Click to expand...
Click to collapse
Update: I flashed AK v30 kernel and the wakelocks seem to be gone now! Prior to this I was on Mahdi with stock kernel which had the wakelocks, and prior to that I was on Mahdi with AK v11 kernel which also had the wakelocks. This is only after an hour of "testing" though, so hopefully no apps I'm going to use will trigger them back :/
Edit: jk, wakelocks returned after a while. Screenshot attached. I rebooted the phone then left it alone for almost two hours.

Getting event0 1585 wakelocks, quite alot , more than 30k wakelocks in 3 hours.
It seems to be related to the synaptics driver, which to my knowledge is the touchscreen so i better not turn that off
Running AK 030 with Paranoid Saber Droid 4.4.4

mumaster20 said:
Getting event0 1585 wakelocks, quite alot , more than 30k wakelocks in 3 hours.
It seems to be related to the synaptics driver, which to my knowledge is the touchscreen so i better not turn that off
Running AK 030 with Paranoid Saber Droid 4.4.4
Click to expand...
Click to collapse
No just ignore that one. Most of the the 30k happens when the screen is on l
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

abhi08638 said:
No just ignore that one. Most of the the 30k happens when the screen is on l
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.

mumaster20 said:
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
Click to expand...
Click to collapse
I'll look into it
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

Nice investigating and bug hunting OP.

mumaster20 said:
I am getting another quite massive wakelock, ipc0000007b_sensors.qcom, this one hits 143k wakelocks in 6 hours.
Tried searching for it on google but didnt really find any answerd or solutions. Do you know maybe what this wakelock is?
Most likely its a sensor, as seen in the name.
Click to expand...
Click to collapse
Alright, unfortunately I couldn't find any information about it. Are you running any auto brightness apps? Autorotation? Accelerator gaming? Magnetic case?
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

Flashed the most recent boeffla kernel this morning (had ak 030 yesterday) and this whole day I haven't had any disruptive event wakelocks. Instead of minutes of those wakelocks, they're just St seconds now. Didn't change anything else.

tracerit said:
Flashed the most recent boeffla kernel this morning (had ak 030 yesterday) and this whole day I haven't had any disruptive event wakelocks. Instead of minutes of those wakelocks, they're just St seconds now. Didn't change anything else.
Click to expand...
Click to collapse
That's curious. It might be because of new commits that might have been reverted in the kernels. Right now I'm using Ark kernel
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!

abhi08638 said:
Alright guys I'm back to share what I have found after doing some research.
Right now I'm using ark kernel with liquid smooth 3.2 milestone
So back to these wakelocks, as it turns out, even though event0 was the most prevalent, most of the time it was on was while the screen was on, so basically you can ignore it.
However, there were two other events that I still had to investigate, event2 and event3. For me event2 is gpio_keys which are the button inputs. event3 is s2w_pwrkey.
First I deleted the event2 file under /dev/input. These files are restored on boot but I would still make a backup before trying this. After deleting this, my volume buttons stopped working, as expected. But my power button still worked. I used it for a couple hours but there was something that was keeping my phone awake still.
Then I rebooted and deleted event3. This is related to the sweep2wake that's implemented in alucard's kernel. I never use it anyway so I went ahead and deleted it. And what do you know, now my phone is sleeping like a baby and even the other events have gone down as well. But the problem is you have to delete the file on every boot. The solution? An init.d script with the following line. Where X is the number of the event you want to remove. You can also just add it to any existing scripts you might have in /system/etc/init.d
rm /dev/input/eventX
How to find out what's causing yours?
1.Download wake lock detector from the
play store and use it for a day
2.check under kernel wakelocks to see if
your phone is being kept awake by an
alarmingly high number of event
wakelocks, if so proceed.
3. Open terminal emulator and type the
following: "su" press enter after each
line
"ps | grep xxxx" where xxxx
is the number
following the event
wakelocks.
4. If system_server doesn't show up,
another app is causing it. Find it and
manage it. Otherwise, proceed.
5. Go back in terminal and type "su" enter
"getevent -c 1" this will give you all
of you events and and what they
are bound to.
6. Make a backup in recovery.
7. Delete one of the problem events and
see if your phone is kept awake, if it.
isn't then congrats! You found the
drain! Else keep testing.
8. Once your are certain which one it is.
Create an init.d or use an existing
one and add the line "rm /dev/input/
eventX" replace X with the event
you want to remove.
You're done.
If you have any problems or questions, I'll be happy to help.
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
Really a different way to deal with the problem than any other threads I have gone through. I am facing the same issue. Phone being awake when connected to WIFI only. The problem does not persist with Data connection and WIFI Off. Its very strange. I was working around for the solution but different things seemed liked working at different times.
Though I was having Event wakelocks and not wlan wakelocks I followed some solutions from this thread http://forum.xda-developers.com/galaxy-s2/help/puzzle-wlanrxwake-wakelock-sgsii-t2133176
Disabling netbios worked for me and again after an update the problem came back. Next time I tried changing frequency to 2.4Ghz and it worked. Now again after dalvik cache wipe the problem came back. No solution left to try.
I shall try the methodology u hav provided. Finger crossed. Really frustrated with this issue. Unable to keep the phone connected to WIFI.
But what can be the real issue. How can the volume keys or sweepwake issues persist only on WIFI and not on data connection. Should I ask for am exchange from OPO?

abhi08638 said:
Alright, unfortunately I couldn't find any information about it. Are you running any auto brightness apps? Autorotation? Accelerator gaming? Magnetic case?
sent from my amazingly awesome OnePlus One
Don't forget to hit thanks!
Click to expand...
Click to collapse
Non of that, next to the standard autorotation and auto brightness of android itself. I did see that all the screen off gestures were turned on in synapse so I turned that off but it didn't seem to help. Its not that big of a deal though, probably some necessary stuff happening in the background. Still getting rock solid battery life! 6+ hours sot over 2 days so you don't hear me complain thanks anyways for sharing your info!
Sent from my One using XDA Free mobile app

kandalamv said:
Really a different way to deal with the problem than any other threads I have gone through. I am facing the same issue. Phone being awake when connected to WIFI only. The problem does not persist with Data connection and WIFI Off. Its very strange. I was working around for the solution but different things seemed liked working at different times.
Though I was having Event wakelocks and not wlan wakelocks I followed some solutions from this thread http://forum.xda-developers.com/galaxy-s2/help/puzzle-wlanrxwake-wakelock-sgsii-t2133176
Disabling netbios worked for me and again after an update the problem came back. Next time I tried changing frequency to 2.4Ghz and it worked. Now again after dalvik cache wipe the problem came back. No solution left to try.
I shall try the methodology u hav provided. Finger crossed. Really frustrated with this issue. Unable to keep the phone connected to WIFI.
But what can be the real issue. How can the volume keys or sweepwake issues persist only on WIFI and not on data connection. Should I ask for am exchange from OPO?
Click to expand...
Click to collapse
Yeah I have noticed this wifi issue as well. Iight be related to the new drivers that were implemented but I haven't been keeping up with that so I don't know if it was reverted or not. I usually keep the wifi sleep policy to never. As I said before, I don't really know why they show up, but this "solution" is very dirty. The best way would be to find the cause of it.
I removes the s2w event because whatever triggered it actually uses power by keeping the capacitive keys on. So stopping that process ultimately saved me some battery.
Sent from my LG-P880 using XDA Free mobile app

[Solved for CM7.2-MTD] No alarms since 01-01-2016 and strange date related bugs

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: