yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] Ezekeel:
No that is not a silly question at all. I actually have not tested that.

I still do not understand how these interrupt wakeups really work. One can block/unblock 13 different interrupt wake sources. One of them is external interrupt EINT. For this external interrupt 32 individual external interrupt wake sources can be blocked/unblocked.

Currently I have blocked all interrupt wake sources including EINT and blocked all external interrupt sources except XEINT[30]. If I also block XEINT[30], there are problems with Touch Wake (pressing touchkeys lights up the keys, but does not wake the device). That is puzzling because I have blocked EINT, so the configuration of the individual external interrupt sources should not matter - but it does. The configuration in the original source code files I found was blocking all interrupts except RTC tick and I2S and blocking all external interrupts except XEINT[22] and XEINT[29].

Since I could not find any documentation on the meaning of the 32 individual external interrupt sources XEINT[0]-XEINT[31], I guess a lot of trial and error work will be necessary to optimize this.

There are only 12 different interrupt sources; EINT should never be touched, so one can configure the external interrupts only by using XEINT[n].

This was a bug in the original code. I am doing some more tests.
[Nexus S Android Development] KalimochoAz:
This is set on kernel v2

I'm checking what could happend since I have no issue with the last version I pushed.
[Nexus S Android Development] from1989:
miui 1.10.7 i9023 not work
[Nexus S Android Development] Jonathon Grigg:
I don't think I ever got anything in a PDF from you? Maybe you did but I didn't see it on my phone. I will check anyway.

@Ezekeel Maybe there needs to be like a Google docs public spreadsheet or form (something anyway) for people to fill out so you can more easily see the results. I tested this in my mostly stock kernel yesterday and had no issues during the hour or two of music playback and other use. I have an i9020T SAMOLED which could make a difference (between 20 and 23, seeing as there were other differences between them for other changes you have made).

Sent from my Nexus S
[Nexus S Android Development] formula84:
I also installed it, I have issues with Bluetooth headphones when paired and connected music playing if the phone sleeps the headphones stop playing and sound stops although the app says its still playing when I wake...I have to disable bluetooth to get sound back. Tested with wired headphones without problems.

I did get a issue after 30 min of screen off music playing through wired, when I woke the device to check something the unlock screen was present...used pause from lockscreen, unlocked and DSP manager FC and screen went black with buttons lit at the bottom, had to pull the batt.
[Nexus S Android Development] Ezekeel:
I have found a way to decode what the different external interrupt values are used for and that XEINT[30] I did unblock belongs to the headphone jack and wakes the system from DEEP-IDLE every 800µs or so. That is not good since it means that the DEEP-IDLE state is essentially not used at all.

So I went back to the configuration of the original code I found. Also I noticed that in the original code some values were changed which are reserved and should remain untouched which I did correct. As said above with this configuration there are problems with Touch Wake and the touchkeys not waking the device; I will look into it.

Bugfix: http://www.pastie.org/2692199

Try and see if the problem still persists with the latest patch.
[Nexus S Android Development] dsellers2:
Great work EZ! I almost loving this patch.
[Nexus S Android Development] thoth77:
Independent thread

I recommend independent thread

[KERNEL] CyanogenMod
[Nexus S Android Development] iceandfire:
Thanks! You gave me my answer.. :D Will implement it asap!
[Nexus S Android Development] Realtyem:
Maybe an app

Perhaps ezekeel you should piece together a simple app to help control all these awesome things you work on. Amazing stuff to witness. Good job and thanks for all you do.
[Nexus S Android Development] KalimochoAz:
on post #36 there is a new updated kernel with Ezekeel last change to be tested
[Nexus S Android Development] from1989:
i still can not download it~~can you give me a hand email me? pdzbyg@gmail.com
[Nexus S Android Development] _bryan_:
you can use securityKiss, it's a free vpn.

get it here, then you can download the kernel at #36

http://downloader.brothersoft.com/b...ecurityKISSsetup.exe&name=SecurityKISS+Tunnel
[Nexus S Android Development] martinsjt:
Same issue with v2.4 go off and do not wake up.

I tried Trinity kernel and works fine but CPU Spy reports Deep Sleep state not Deep Idle.

How can we check if the Deep Idle mode is really used.

Best
[Nexus S Android Development] morfic:
Implemented the 2nd bugfix, all seems well.

I didn't get to try my bluetooth headset on bugfix#1 alone, but i am playing via tunein radio for a while now.

Cool my usual work 5am alarm went off, so that also works. was wondering if it would impede on alarms, at least while streaming it's working....

There are a couple other use cases that we will have to explore maybe.

Thanks,

Daniel
[Nexus S Android Development] FloHimself:
Latest kernel is without BLN... Is BLN also affected?
[Nexus S Android Development] morfic:
BLN is blinking and working on my build.
[Nexus S Android Development] FloHimself:
Not on KalimochoAz's build... seems just to be disabled. @KalimochoAz can you provide one with BLN enabled?
[Nexus S Android Development] chickelnoodensoup:
The new Trinity TEUV kernel with deep idle seems to be working well after a few hours of testing.

Has anyone else noticed vibration alerts (for texts, emails, etc.) being insanely weak on kernels with the deep idle added? It's so weak that you almost can't feel it in your pocket.
[Nexus S Android Development] :
keep looking my signature i always use altervative link always updated with new version.
[Nexus S Android Development] Black Coffee:
Any improvement in the battery backup ?
[Nexus S Android Development] chickelnoodensoup:
What do you mean by battery backup? If you mean battery life, I haven't really tested it for long enough yet to notice any differences.
[Nexus S Android Development] JimmieMaul:
Haven't noticed any weak vibrate personally on Oxygen 2.3.1 on a Nexus S 3G
[Nexus S Android Development] from1989:
ok thanks alot
[Nexus S Android Development] from1989:
i use the trinity teuv kernel now it sames better?and why my diverse always not good with bfs kernel in any way ~~~
[Nexus S Android Development] :
I use Cm7 kernel sorry.
[Nexus S Android Development] from1989:
ok~~~~
[Nexus S Android Development] morfic:
This is from use of DIDLE in TEUV:

I can now safely say i see no battery savings with CONFIG_CPU_DIDLE=y

Which leads me to ask what rom you are using, what build.prop modifications (if any) you are using.

In a working CM7 environment, the savings are nil.

Food for thought: letting my phone idle with all apps running, i can get through about 24 hours on a charge.

With SIM removed, but WIFI enabled, i can get twitter updates, emails and gtalk messages for 6-7 days.

Let's use a 1:6 ratio, that makes the proposed savings in airplane mode a theoretical savings of 4%?

That is if the cpu does no work with the radios.

I think testing must be done in a real world environment.

As saving battery with cpu UV and chipset UV is extremely hard as most our power is eaten up by the radio.

I could blame KF1 radio, but even people who have since flashed back from KF1 still see no real world benefit.

If anyone does see real world benefits from Deep Idle, i would like to know more about your configuration, build.prop tweaks, settings changes, anything of relevance.

For my real world usage: I don't play flacs for hours on end, i use my phone to use gtalk, tapatalk,gmail, perhaps browser, tweetcaster, sms all with the screen on, or it is in my pocket, with screen off, where it should sleep, not idle.

That too could be factoring in, unless someone can chime in and that confirm they do use it as media player and still don't see savings.

Just letting you know what i see here.
[Nexus S Android Development] steve.garon:
Been playing with deepidle on my kernel too and my phone refused to turn the screen back on after a phone call while deepidle is on.

Flashed the same kernel but with deepidle off and phone calls are fine.
[Nexus S Android Development] intheb0x:
Did u post your latest build?

I don't see it.

Thanks

Edit,

Found it here

http://www.derkernel.com/

But having issues with it and the usb storage on the nexus not being found, same issue i had with bfs kernel, what gives?

Thanks
[Nexus S Android Development] Ezekeel:
There still is a problem with Deep Idle since it seems to prevent the phone from going to sleep. I will see if I can fix this.
[Nexus S Android Development] dsellers2:
Sorry that use use that Kernel. :)

Jk
[Nexus S Android Development] formula84:
Anyone else have Data Issues? I am on Morfics from today and I have lost 3g twice today...3g icon is lit up and my sync arrows are lit but I do not get internet. Browser never gets anywhere email does not work, etc. If I toggle airplane mode and let it sit for a minute and toggle back on it works without a reboot.

NS4G
[Nexus S Android Development] simms22:
my phone sleeps just fine using teuv lazy with the deep idle. on usb/charger, off the usb/charger, and i have 0 issues while using it. but i am reading about many whos phones arent sleeping properly. my only thing with deep idle is that its not doing anything for battery life. i get the same battery life with teuv/lazy as with teuv/lazy/deep idle. the only significant thing ive noticed is more people having more problems when deep idle gets thrown into the mix. now, in theory, deep idle sounds wonderful. but in practice, it doesnt seem to be very useful. so my question is, is it worth the time?
[Nexus S Android Development] Black Coffee:
Been using Deep idle v2.4 & the battery life seems to have improved a lot, no other issues till now except a single reboot !
[Nexus S Android Development] Ezekeel:
If you rarely use any background processes with screen off like music player you will see almost no change in the battery runtime. I use my device for 2-3 hours music each day, so for me the savings are substantial.

To be more precise: the phone goes to sleep and wakes up directly after due to some external interrupt. This does not happen all the time. I checked and I get the same behavior without DEEP IDLE, so this must be something with the ROM or some tweak installed. So, false alarm here.

I made some changes, so for DEEP IDLE the same wakeup interrupts are used as for sleep. This should fix this and possibly other issues.

Bugfix: http://www.pastie.org/2697909
[Nexus S Android Development] thoth77:
Next Nightly Kernel

http://cm-nightlies.appspot.com/?device=crespo

Thanks for CM-DeepIdle Kernel :)

Next Nightly Kernel will be changed much.

Are CM-original-kernel.zip and CM-DeepIdle-kernel.zip for flash changed too accordingly?
[Nexus S Android Development] steve.garon:
Thats cool. I'll give it another shot!
[Nexus S Android Development] franciscofranco:
Going to test it and provide feedback tomorrow.
[Nexus S Android Development] steve.garon:
Bugfix #3 still wouldnt wake up screen. Had to pull the battery... I'm pretty sure I have all patches installed. You can verify my github if you want.
[Nexus S Android Development] morfic:
Do you have the coolbho3k SoD fix in?

Not sure how it relates, but perhaps deep-idle gets entered at any frequency, and sleep from there?

It is obvious that the kernels with this patch in, wake up normal.
[Nexus S Android Development] steve.garon:
Never heard of that SoD fix. Can you give me a link that describes it please?
[Nexus S Android Development] morfic:
It saves your current policy min max, suspends at SLEEP_FREQ and restores min max policy after resume.

Send me an email, I don't have the link to his patch, but recreated one from my git commit. Should work for you.

[MyUsernameatxda]@gmail.com
[Nexus S Android Development] :
deep idle doesn't like -30 mV also -25 too with 100/1000 conservative. i revert it back to the 7.1.0 kernel with -25 mV.With undervolt got more than 4 crush bsod.
[Nexus S Android Development] steve.garon:
My custom kernel does run a -25 mv across the bands so that might be why I'm getting SoD.
[Nexus S Android Development] :
probably. until i try to uv i never get bsod with 2.4 or 2.3 deep idle kernel.
[Nexus S Android Development] Serious_Beans:
Is anyone else having a problem with losing data on any custom kernel with deep idle? I'm using morfics teuv with deep idle and me and some other people are having a problem with wi-fi/data going out randomly and the only way to fix it is with a reboot, it's not the radio because there are 3 different radios mentioned that I know of that have the problem.
[Nexus S Android Development] dsellers2:
I was. I changes from kf1 to kd1 and thought that fixes it but it did not. Now its just much less when. It cuts out. I'm running morfics teuv-mcpb. I'm not sure what it could be. Maybe one of these interrupts are causing the data network to take a dump until reboot?
[Nexus S Android Development] morfic:
I guess radio does not get woken up.
[Nexus S Android Development] Ezekeel:
I am not having any trouble with the data connection. I tried Edge, 3G and WiFi and everything is working fine. My baseband is I9020XXJK8 and I am running CM7.03. What ROM are you using?
[Nexus S Android Development] simms22:
im not having any trouble with the radio or any other data connections either. i wonder what the variable is. teuv-mcpb and the last cm kang by FuZZ_.
[Nexus S Android Development] dsellers2:
Latest kang by fuzz. Never had issues until this latest (awesome) mod. Its not constant though. Only after my phone has been in a deep sleep for 30 minutes or more. After waking up no data. Any less its usually fine.
[Nexus S Android Development] dsellers2:
If it matters Ezekeel, I'm sure I'm not the only kme with the issue. But not everyone is having the issue either. So I'm not to sure.
[Nexus S Android Development] dsellers2:
I'm on the same rom, radio, and kernel as you simms. Very odd indeed. Maybe a setting that I have enabled and you don't?
[Nexus S Android Development] steve.garon:
I'm running uckf1 radio with CM7.1 stable and not that I lost 3G at any time but I always and up with at least 10 radio dumps when ever I use a deepidle enabled kernel o_O
[Nexus S Android Development] franciscofranco:
After a full day of testing this mod works perfectly fine for me. Oxygen rom + my modified CM kernel
[Nexus S Android Development] Serious_Beans:
Running the same baseband as you and running the latest CM7 Kang with TEUV-MCPb and I get data issues, it's odd, some people get it and others don't, maybe our chips can't handle the deep idle? Or is this mod suppose to work on every single cpu regardless of build unlike overclocking/undervolting?
[Nexus S Android Development] dsellers2:
I tryed a different kernel, Tuv-mcpB instead of teuv thinking it would solve the wierd data disconnect issue. It worked great all night until I woke up and then.....no data until a reboot. :/
[Nexus S Android Development] red_skittles:
I am curious as to the reasoning behind this. Is this because clocking at say 1.2GHz will cause the CPU to reach the idling state faster than clocking at 880Mhz so the phone stays idling for longer. Is the decrease in battery drain from being in idle for longer really enough to offset the battery drain from running at a higher frequency. If ive got this all wrong someone please correct me. None the less, this mod looks very promising!
[Nexus S Android Development] franciscofranco:
In theory that's what should happen, the faster the clock the faster it enters IDLE, and what we want is faster entering in IDLE mode for the best battery savings.
[Nexus S Android Development] morfic:
Ezekeel, food for thought: why not let it reach deep idle while we stare at the screen, reading something?

Why only let it reach deep idle with screen off?

When we read a message, web page, forum post, not much is really needed.

Is it possible to enter a deeper idle state with screen on?
[Nexus S Android Development] dsellers2:
How would one know the difference. What if a page had flash ....although I like your reasoning.
[Nexus S Android Development] joebarkho:
How would I put the patch ONTO a kernel? Do i flash something?

As for the Deep Idle State, should I put the cpu on a certain governor?
[Nexus S Android Development] morfic:
You need to flash a kernel that was built with the kernel changes in it.
[Nexus S Android Development] Ezekeel:
I tried that before in the initial implementation with TOP=ON, but I was causing laggy animations. Maybe I can think of something.

I implemented a sysfs interface (/sys/class/misc/deepidle) for enabling/disabling the use of the DEEP IDLE state. This should make debugging more convenient since people can compare the behavior without changing the kernel.

Bugfix: http://www.pastie.org/2709212

I also made some further tests and receiving calls, SMS and emails while the phone is in the SLEEP or the DEEP IDLE state is all working flawlessly.
[Nexus S Android Development] franciscofranco:
I don't have your kind of knowledge, but since your mod needs CPU_IDLE to be enabled I thought that maybe using a newer CPU_IDLE code it could help on the weird BSOD problems that some users have. If that's any reasonable by a long shot here it is my commit of the 3.1 cpu idle backport: https://github.com/franciscofranco/...mmit/0c304350fcc71722be00df4993cf09afef6ca765
[Nexus S Android Development] joebarkho:
So which kernels for ns4g implement these things? which governor should I use?
[Nexus S Android Development] steve.garon:
I was just reading throught all your mods. There is some pretty interresting stuff. I might pull a couple of those changes.

That said, since I rebuilt my defconfig using morfic's I havent had any SoD. One option I had that to me might have been conflicting with deepidle was APM emulation. I believe it's for power management right? Well removing this + all the debugging stuff seems to have fixed it for me. I'm close to 10h without SoD. With the previous defconfig I never managed to pass an hour...
[Verizon Droid Incredible 2] CyanogenMod:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Instructions:

First time flashing CyanogenMod 7 to the HTC Incredible 2, or coming from another ROM?

Root the device and install ClockworkMod Recovery. Instructions are available here.

Perform a NANDroid backup of your current ROM.

Format the system, data & cache partitions of your device.

Perform a factory reset.

Flash CyanogenMod.

Optional: Install the Google Apps addon package.

Upgrading from earlier version of CyanogenMod 7?

Perform a NANDroid backup of your current ROM.

Flash CyanogenMod (your Google Apps will be backed up & restored automatically).

Issues?

Experience issues? Please provide the following info:

If the device was hard reboot, please provide the file "/proc/last_kmsg".

If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.

Please use Pastebin when possible.

Download Links:

Official post​

CyanogenMod:

Latest version: update-cm-7.1.0.1-Inc2

Download: link

Mirror: link

MD5sum: 178fb833abff50ddc86f980617030d53​

Google Apps addon:

Version: gapps-gb-20110828

Mirror: link

Mirror: link

Version: Google Talk with video addon

Mirror: link

Mirror: link​

The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
[Verizon Droid Incredible 2] iceman99393:
Hmm. Were experiencing data, wifi, issues on the stable. Wifi breaks radio, data arrows still dont animate.Do you guys know this? I'm sure others will chime in.
[Verizon Droid Incredible 2] shoman24v:
I'd definitely flash, if there weren't serious issues :(
[Verizon Droid Incredible 2] Droidel:
Both nightly and stable is broken! Enabling then disabling wifi kills the voice and data. Airplane mode messes up everything.

Please read the comments

http://xdaforums.com/showthread.php?t=1296842

http://xdaforums.com/showthread.php?t=1156343

Quote the following and add to it on bottom if you find other bugs

************** Stable release issues ****************************

- Enabling wifi kills the ability to send/receive text messages via verizon towers

- Disabling wifi does not fix the issue

- Airplane mode renders phone useless and can't get it out of airplane mode

- Restarting phone fixes the airplane mode issue

- Compass doesn't work

- Data arrows don't animate when 3g is downloading/uploading

**********************************************************

anything else?
[Verizon Droid Incredible 2] dnoyeb:
if i remember correctly the compass doesn't work right either.
[Verizon Droid Incredible 2] seejoshplay:
did the wired headset get fixed yet?
[Verizon Droid Incredible 2] Droidel:
What is the issue? What build did you have this issue with?
[Verizon Droid Incredible 2] jaypr9:
If your taking about the mic working with the headset, then yes.
[Verizon Droid Incredible 2] cac2us:
WiFi Breaks Radio??

OK I tried to "Break the Radio" by turning WiFi ON, connecting to my home network, placing a voice call, open a browser on the phone and leave a voicemail at the same time,

The ONLY real issue I can find is the Airplane mode issue and I get around that by de-selecting Data enabled in Mobile network settings.

I am running the stock radio (havent updated).

Currently running Tiamat 1.1.3 (battery issues reported with 1.1.4).

Oh, and when I first booted from flash, I had to enable International data roaming.:eek:

Did "Everyone" that seems to have this WiFi Breaking the Radio issue,

Check the MD5 of the .zip on the phone?

I have had data cable issues leaving me with a bad file on the phone.

Fully wipe data Factory Reset in CW Recovery NOT RM?

Try to use WiFi BEFORE restoring ANY apps...?

Use Titanium Backup to restore app only for those apps that might alter the core OS?

I have not flashed without wiping at least cache and davlik between nightlies and FULL data wipe "Factory Reset" when changing base ROM.
[Verizon Droid Incredible 2] Droidel:
I wonder if latest radio is causing the broken data and voice.

Cac2us

What version of radio do u show in your about phone?
[Verizon Droid Incredible 2] cac2us:
Stock radio

I just noticed that the build shows "Nightlly"

Just remember if your gona flash a radio, make sure to check the MD5 on the phone. Stuf happens...