yashsingh1/xdaforums huggingface dataset:
[Nexus S Android Development] simms22:
easier work arounds..

1. in the terminal emulator type..

su(press enter)

reboot recovery(press enter)

2. use the rootbooter app(i use this because my power button is broken, and its faster than the power menu).

3. use gscripts. type in the reboot recovery script, save it, make a shortcut on your homescreen to it. one press and youre in your recovery.
[Nexus S Android Development] roshga:
Been there, fixed that.

Turn on flight mode

Reboot

Turn off flight mode

Good luck :)
[Nexus S Android Development] dario3040:
My power button works fine :P

I think the volume keys might die if I keep it up like this (have around 40 kernels to scroll through D: . )
[Nexus S Android Development] sinik420:
Kd1

sent from my nexus s on a kang from simms
[Nexus S Android Development] belair56:
Wish O I wish

Wish it was that EZ

1. tried - no go phone goes dead have to do a battery pull just as if I tried to go to recovery from the power button menu.

2. did not try. But I have tried Quick Boot - no go same as above.

3. no reason to try after #1 failed.

All TEUV dated after 9-28 I Fail

Simms I do appreciate your help with everything :) anything else you think of let me know.
[Nexus S Android Development] simms22:
what recovery/version are you using?
[Nexus S Android Development] belair56:
twrp-1.1.1
[Nexus S Android Development] Serious_Beans:
Permanent fix or temporary?

---------- Post added at 04:44 PM ---------- Previous post was at 04:44 PM ----------

Try using CWM
[Nexus S Android Development] belair56:
Thanks

I'll flash in a flash :p

downloaded a euroskank branded recovery by fitsnugly this week

No go

Tried power button menu and term.

Thanks guys for suggestions.
[Nexus S Android Development] skinniezinho:
Miui-pt (Portuguese translation of the official MIUI) + MCP kernels (Either MCP or MCPb give me network and wifi problems, it says error on the wifi toggle and no network (must switch to airplane mode on and then off to have network).

With stable kernel all works.

With english miui I have wifi on mcpb but no network (Even with the airplane mode tweak) edit: I have network, it took a while.

Hope it helps you on deving..
[Nexus S Android Development] brainmaster:
Needed to catch up with the thread, reading the last 30 pages in one hour. Allot of changes, including the new Ezekeel's stuff.

morfic, I'm open for suggestions about the RAM script. The trouble with your settings for the RAM is that it often kills widgets on my MIUI ROM or they freeze (weather or clock not updating).

If you have better settings, or can adjust mine - please post it, and if it works fine (no killed widgets) I will integrate it.
[Nexus S Android Development] eduke:
no, I have KD1 and I have the problem ...
[Nexus S Android Development] dsellers2:
Well I guess I spoke to soon. Although it ls not happening as much after flashing KD1 from KF1 I'm still losing something wifi and data. What could I do to troubleshoot this and get some dev's some actual feedback to use. Other than me saying I'm losing data. Lol. Logcats or something? If so, it may be hard to catch since it"s so intermitenent.
[Nexus S Android Development] Serious_Beans:
Download a really large file and when it stops downloading and you have 0kbp/s then you will know when it happened. I don't know how log cats work so I'm guessing you have to generate it at the time of the problem? or know when it happens so yeah if that's how it's done then you can try my suggestion.
[Nexus S Android Development] dsellers2:
Well I don't lose data until my screen turns off. When I'm Messinger g around with the phone. All us fine. But an hour later I pick my phone up and data is gone and needs a reboot. Althought I will try your suggestion with logcat running.
[Nexus S Android Development] skinniezinho:
Donated, next month will donate more =) (student life always on the budget lol).

Will be testing TUV MCPb on English MIUI from http://miuiandroid.com/ :D
[Nexus S Android Development] Babydollll:
Just some MORE proof of the awesomeness of this kernel. :D

(latest TEUVmuadib)

Pipsqueak approved this message.
[Nexus S Android Development] simms22:
:eek:

to bad it doesnt go further than this before freezing.. yet!

---------- Post added at 06:55 PM ---------- Previous post was at 06:53 PM ----------

thats not the latest version. there have been bugfixes since, try this one TUV-MCPb.zip http://morfic.euroskank.com/simka/TUV-MCPb.zip
[Nexus S Android Development] skinniezinho:
I may be wrong, but at least it seems to me that MCB is snappier than MCPb.

Both using fresh instalation of 10.1.14 english MIUI (all wipes dones).
[Nexus S Android Development] simms22:
or..

you may be right.

whats important is that youre happy with it :)
[Nexus S Android Development] skinniezinho:
Both are quite fast, the MCB seems to be snappier,maybe because it "switches" to higher freq faster (Don't know, just saying) although I think that if everyone tests,shares opinions and donates, it is easier for the dev to make a better kernel =) so I'll do that =)

If I have time I will see with cpu spy how much is the difference (with cpuspy) between mcp and mcpb =)
[Nexus S Android Development] Babydollll:
Okay, thank you. I'll report back later. :)

Pipsqueak approved this message.
[Nexus S Android Development] melvinchng:
I never get to 100... the most just 98. The mod doesn't require bump charge as many users said. "Those battery was at 96. Now it is 100%."

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] noobiekins:
:eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek::eek: Crazy speeds :eek:
[Nexus S Android Development] from1989:
o my god !!!who can tell me why this kernel on miui will cause the wifi not work???help~~~help~~~
[Nexus S Android Development] simms22:
try turning off youre wifi, reboot, then turn your wifi back on.
[Nexus S Android Development] from1989:
i try it many times it do not works ~~~the problems will get back at next time when i reboot my diverse with wifi on
[Nexus S Android Development] skinniezinho:
What MIUI?

On miui from here it works.
[Nexus S Android Development] from1989:
the chinese stock one
[Nexus S Android Development] kid1da:
I just wipe cache and dalvik when that occurs.

if the skies the limit, where's the urgency?
[Nexus S Android Development] supercluver:
I'm having the same issue. Anyone know how to fix this? Flashing a different kernel does fix it...
[Nexus S Android Development] from1989:
i do that too but it will breakout another time
[Nexus S Android Development] morfic:
stop flashing when it works
[Nexus S Android Development] simms22:
and it runs.. mostly :eek:
[Nexus S Android Development] FuZZ__:
dont wanna see your Nexus S got fried!:eek:
[Nexus S Android Development] simms22:
dont worry.. youre just smelling the bacon inside, frying ;)
[Nexus S Android Development] melvinchng:
They are waiting outside :)

Accidentally sent from my Google Nexus S using XDA Premium
[Nexus S Android Development] simms22:
lol!

i can see them outside :eek:
[Nexus S Android Development] SS2006:
the 1.54 ghz kernel isnt downloading, neone else
[Nexus S Android Development] tehgeekguy:
http://morfic.euroskank.com/NS/T1544-S22-05102011.zip

You have to change "simka" in the link to "NS" for that one. It was mentioned quite a few pages back.
[Nexus S Android Development] SS2006:
flashed this over CM 7.1

the screen color is changed now, its bluish, normal??

also it hangs alot and reboots, i dont think this is meant for cm 7.1 yet.
[Nexus S Android Development] morfic:
Are you on a 1.544ghz kernel?

And the cooler whitebalance is intentional, better than the google yellow.

Don't eat the snow.
[Nexus S Android Development] SS2006:
yup the 1.544 .. ? is that why?

i figured the color is intentional, some sort of enhancement, i suppose my eyes didnt adjust
[Nexus S Android Development] morfic:
1.544 is for few phones.

Run T144 or TEUV, my 2 favorites.
[Nexus S Android Development] Tzorg:
Right, after running majority of yesterday on MCPb without issues, when I tried to use the phone this morning the following 2 things happened:

1. I did have wifi but not mobile signal. Is this the radio issue other users are reporting with DIDLE? Or is that only affecting their 3g data? I'm on kd1

2. I set the airplane mode, through right button menu, to see whether switching it on and off would sort out the radio. Once in airplane mode the right button menu would show the airplane mode and the reboot options greyed out, so I had to use the power off option, which was enabled. After restart all is ok again. I wonder whether that could be related to some of the interrupt tweaks done to the DIDLE bit in MCPb. Or it could be the voltages, I've had weird interface issues in the past when undervolting too much in other kernels, how much undervolted is teuv?
[Nexus S Android Development] SS2006:
Is lazy gvrnr better than smartass v2?

Perfoemance wise and battery
[Nexus S Android Development] saranyan:
Which Trinity kernel is stable for CM7.1(stable), I tried the TEUV muadib and got the black screen of death.

Dunno which one to flash TUV 10 or TEUV normal.

Any suggestions?:)
[Nexus S Android Development] roshga:
The deep idle is better then I thought it'll be.. 0_o
[Nexus S Android Development] benrees21:
Is deep sleep the same as deep idle?

I noticed worse battery life with deep idle mod but maybe it was my fault and I should of gave it more time to settle in. I've just flashed it again and will give it a few days this time. Does anyone know if using autokiller memory optimizer is a good idea? I'm using it now but I keep getting these microlags and I'm wondering if it's interfering with the kernel. Thanks for your help.

Sent from my Nexus S running NSCollab ROM and Trinity T144 Beast Kernel.
[Nexus S Android Development] Roscopcoletrain:
it for sure going into deep sleep more, but I cant say for sure if the battery life has improved much. Maybe just a touch.

One quick question, would it be better to run the 1ghz kernel or 1.44 but underclock it to say 1.1/1.2 or whatever it allows? I like a slight OC, but not sure if the 1.44 is meant to be run at 1.44 only.
[Nexus S Android Development] Rooster85:
I have been getting the wifi and data connection bug, it will connect fine for awhile then just randomly lose connection to anything at all. Only a reboot will let me connect back to data.

Sent from my Kushed Nexus S 4G
[Nexus S Android Development] benrees21:
It boots at 1.1 but if you change it you can only select 1.0 and 1.4

Sent from my Nexus S running NSCollab ROM and Trinity T144 Beast Kernel.
[Nexus S Android Development] Roscopcoletrain:
Perfect, thanks!
[Nexus S Android Development] skinniezinho:
I may be wrong but I have the same thought as you...

In miui battery stats it says

cell standby 48%

Phone idle 20%

Android system 11%

Display 9%

Voice Calls 5%

Android os 4%

...

Cpu spy:

deep sleep 96%

100mhz 1%

(the phone has been sitting here doing nothing)
[Nexus S Android Development] k4str0:
I have too on the latest TEUV experimental with Deep Idle. Just flashed TUV experimental to see if I still run into this problem.
[Nexus S Android Development] noobiekins:
It seems that if I'm playing music, it stays at 100 mhz

edit: To anyone that lags with teuv in gaming such as drag racing, try turn off purging of assets.
[Nexus S Android Development] dsellers2:
I tryed Tuv-mcpB last night instead of teuv hoping 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] kecinzer:
I'm using TEUV-NS-05102011 and sometimes I have graphics artefacts. I can see strange lines on lock screen and sometimes in launcher.

Is there anyone who has this issues too?
[Nexus S Android Development] Rooster85:
I did the same and all seems well so far

Sent from my Kushed Nexus S 4G
[Nexus S Android Development] italia0101:
Everything's good for me with ythe latest .. haven't used phone loads but am on 17% now and its been going for 31 hours! With 3 with screen on
[Nexus S Android Development] eduke:
data lost big problem...:mad:

back to stable 05102011... is not usable, I can not reboot the phone when I need ... I will continue testing everything ...:rolleyes:
[Nexus S Android Development] dsellers2:
It will get fixed. Just give it time. You are on a beta test kernel which at times has bugs which I'm sure you know.

I can't wait until its fixed because it will be the perfect combination of speed stability and efficiency from Morfic's kernel. I want to do whatever I can to do so, but not all people are having the issue which makes it even longer to get solved typically.
[Nexus S Android Development] eduke:
of course, I've tried and I will continue trying ...

I appreciate the work and effort of morfic ...:)
[Nexus S Android Development] Kraenesk:
Teuv no didle 100/880 lazy. CM7.1

uninstalled maps because I don't use it and got a couple hundred points jump.
[Nexus S Android Development] benrees21:
Well lets try and get down to the root of these connectivity issues. I don't have a problem, my model is I9020 and I'm on NSCollab.42 with T144 and KF1 Radio. Think it would be an idea if people put down details of phone model, rom, kernel and radio. Might see a pattern emerge or you might not, worth a try though.

Sent from my Nexus S running NSCollab ROM and Trinity T144 Beast Kernel.
[Nexus S Android Development] Kraenesk:
Same settings t144
[Nexus S Android Development] thedudejdog:
I've had this happen once. Reboot fixed it and I haven't had that issue since
[Nexus S Android Development] dsellers2:
I'm on latest fuzz kang...teuvmcpb, 9020a
[Nexus S Android Development] khartaras:
Morfic, when ICS comes out, can the existing tweaks be ported to Linux 3.0?
[Nexus S Android Development] kenvan19:
To test the experimental TEUV kernel installed it in my phone and the regular teuv on my wife's. Our phones get a similar amount of usage with hers being mostly games and mine being mostly news feeds. Over the course of three days her phone had massively better performance in games and battery life.

Sent from my Nexus S MV from the XDA Premium app.
[Nexus S Android Development] ZiggSVO:
Oxygen 2.3

TEUV 0510
[Nexus S Android Development] morfic:
As per Ezekeel, main use/benefit of DEEP_IDLE would be for screen off media playing.

Seems neither of the two of you plays with the screen off or reads news with screen off.

Makes the difference interesting for me.
[Nexus S Android Development] morfic:
I haven't seen the source, i suspect a lot can be moved easily, some with time.

Has a lot to do with how the cpu-freq stuff is layed out for the cpu used in the device.
[Nexus S Android Development] scumm_boy:
Hi Morfic

I have been bitten with the Deep Idle data bug as well, and I just thought I'd share my findings.

When the issue occurs I get the 3G or H icon, but it stays white never going the 'connected to google' green. Wifi connects after this bug, but again it never goes green and no data enabled app connects.

Flipping Aircraft Mode on and off didn't change anything, but the weird thing is that from a terminal I was able to ping google.ca.

I didn't try #*#*info*#*# to see if anything in that menu would fix the issue.

Hopefully something in this wall of text will help!

Sent from my Nexus S
[Nexus S Android Development] Ezekeel:
The CPU in the Nexus S will not change with ICS. Or are you already fantasizing about your new shiny Nexus Prime?

If others can confirm that the data connection still works from terminal, this probably means that the problem is not with the kernel and DEEP IDLE, but something in the ROM is not properly reinitializing the data connection. To confirm, get Fast Reboot (https://market.android.com/details?id=com.greatbytes.fastreboot&feature=search_result) and see if restarting the systems processes reenables the data connection.
[Nexus S Android Development] dsellers2:
+1. Same here. Exact same symptoms.
[Nexus S Android Development] scumm_boy:
It very well could be something in the ROM (Fuzz's latest CM 7.1 nightly Lang WOC) but as soon as I flip to the last non deep idle kernel (5/10 I believe) I don't have a reconnect issue coming back from an extended period of the screen off. Would any other feedback help track down the issue?

Sent from my Nexus S
[Nexus S Android Development] Rooster85:
I thought my issues may lie with decks rom so I flashed cm stable and had the same issues using the deep idle kernel. Right now I'm running decks stable release with the 10/5 tuv kernel with zero issues

Sent from my Kushed Nexus S 4G
[Nexus S Android Development] simms22:
im using the same rom, and not having any issues. but i am realizing that the teuv w/out deep idle is slightly quicker overall, especially when it comes to 3d intense gaming(tested with asteroid 2012).
[Nexus S Android Development] scumm_boy:
That is strange, as I think we have the same version of the Nexus... I'm on an AWS provider in Canada, and I think you had said that you are on T-Mobile who is on the same band.

I find that the problem only happens after extended time with the screen off (presumably in deep idle)

Sent from my Nexus S
[Nexus S Android Development] morfic:
I have seen eclair source look different from froyo source different again in gingerbread.

Why should I expect samsung to not yet again have moved stuff around for Ics?

Samsung will be samsung. Thanks for playing.

EDIT: and yes, I can't say much about the source for the phone that has it first.
[Nexus S Android Development] kenvan19:
I ran it for 3 days and never once had a data loss on nexus mv. I frequently switch from wifi to data and let me phone sleep for hours in between while working or doing other things at home. I did however, as I mentioned earlier, have significantly worse battery life than my wife (though neither of us use much media on our phones) even after installing the kernels on fresh roms and calibrating both batteries. At the end of the day with similar amounts of use (hers less but more gaming mine more but heavier news reading) her phone was around 70% (which is spectacular considering previously it would be around 1%) whereas mine would be > 10% (whereas before on the Oct 5th teuv id be around 60%). Sadly I forgot to use batterystat on either device so I don't have concrete data.

Sent from my Nexus S MV from the XDA Premium app.
[Nexus S Android Development] HelloH:
I had an 94%-on-the-charger SOD with teuv 05102011 stable this night, perhaps it is undervolted too aggressively?
[Nexus S Android Development] mikemike23:
I am using MIUI 1.10.7, and my kernel is Trinity T12-NS-05102011. Everything seems good before. Nowaday, I flash the kernel into T144-NS-14102011b .....My phone become laggy.....and Hang.........the situation keep the same even I change back into T12.........Finally, I need to flash MIUI ROM again. But now, my phone will become laggy even I flash with T12, Does anything can tell me why my situation like that? What should I do now? I really want to use T12 or T144...............
[Nexus S Android Development] bringonblink:
Hey morning all,

Just a quick question, can someone help me navigate morfics git?

Basically i want to check what the voltages are on some of these kernels, where exactly do i have to go to check that out?
[Nexus S Android Development] coloxim:
I'm using the teuv without idle..and the battery is infinity..very good...I'm using it with kang..no issue..everythings are perfect..

Thanks mor..

Inviato dal mio Nexus S usando Tapatalk
[Nexus S Android Development] noobiekins:
I have recently been through the data loss problem, restarting the phone works. CM7.1 with tuev mcpb
[Nexus S Android Development] dsellers2:
Those of you having data disconnects on MCPB. I was reading in another kernel thread about people getting that bsod an the way they solved it in their was to raise their min frequency to 200.

I thought that maybe the data disconnect was the related with this kernel. So, I raised my min to 200 last night on the teuv-mcpb version and I woke up this morning without data disconnect issue. That's 8 hours with screen off time and didn't see the problem. I typically can't go more than an hour it two. I'll continue testing but figured I'd pass this on to hopefully helps others as well.

Edit: after 12 hours it finally happened. Not sure what was different but I did lose data. Its definitely happening much less at this point.
[Nexus S Android Development] scumm_boy:
@dsellers2

I had 8 hours without a problem last night as well. My min freq is still 100 MHz. I haven't run into a data disconnect since I reflashed mcpb last night. Interesting.

Sent from my Nexus S
[Nexus S Android Development] nadiros:
Dudes! Deep sleep is NOT deep idle....okay!
[Nexus S Android Development] droidance:
I'm also having frequent data disconnections and the only way to find out is if I do something with the data so I think this is pretty bad especially if I'm waiting for an e-mail or SMS (via data, not text message).
[Nexus S Android Development] dsellers2:
Dude. There's not a feqiency step called "deep idle"

Okay! And that's Mr. Dude to you.
[Nexus S Android Development] scumm_boy:
Or El Duderino, if you aren't into the whole berevity thing.

Sent from my Nexus S
[Nexus S Android Development] nadiros:
LoL, funny you took this one on....

Anyways, no there isn't such a step thank you ;) My point is the

confusion with posting CPU Spy screens to back up claims, or show as proof of the effectiveness of deep idle.

Cheers Mr. Dude ;p
[Nexus S Android Development] simms22:
Dude, youre probably right, i just cant say that im 100% sure. because my phone sleeps well(deep sleep) with and without deep idle. i pretty much get the same results in cpu spy with the teuv kernel with deep idle and the teuv kernel without deep idle.
[Nexus S Android Development] dsellers2:
I like it. Lol.
[Nexus S Android Development] dsellers2:
Dude, I've noticed the same thing. On a side note, has anyone seen my car? :P
[Nexus S Android Development] nadiros:
Love the pic! Made my day ty :)
[Nexus S Android Development] simms22:
here you go, i spotted it outside. its kinda hard to lose this one, you must have been distracted :p

ps. sorry, the organic cold medicine is making me loopy
[Nexus S Android Development] noobiekins:
Hey morfic, are you planning to release a T11 anytime soon? I miss the old TUV11 since it gave me great performance with better than stock battery life. If the answer is no then I'll stick with what you got right now. Your kernels are very snappy :D
[Nexus S Android Development] simms22:
there will be a 1.1ghz kernel, but it wont be like the old tuv11. thats what tuv is. for a long time that we were running tuv11, but later found out that it was 1ghz and not really 1.1ghz. so it was just remade into tuv.
[Nexus S Android Development] morfic:
As simms22 already pointed out, yes, T11 will come, just not getting to it yet.

aside from catching up with maintenance builds on the deep idle tests, i worked on Iconia, am working on sensation in a limited trial, poking the G2x and then try to get simms22 some fun kernels.

with the current crop being so close in performance, T11 won't be missed for a few days longer

but i won't sell you a TEUV > T11, but yes i'll sell you a TEUV > TUV ;)

just hang in there, it'll come
[Nexus S Android Development] dsellers2:
Haha.
[Nexus S Android Development] morfic:
Test builds with Ezekeels bld, sd, tw fixes and deep-idle sysfs interface are available at Der Kernel

From Ezekeel: "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."
[Nexus S Android Development] simms22:
NOT INCLUDED IN THE TEST KERNELS ABOVE..

:eek:
[Nexus S Android Development] tylercarter:
Lol. We want what we want and we want it now. Lol.
[Nexus S Android Development] dsellers2:
Do I have to run a script to enable the deep idle state Morfic?
[Nexus S Android Development] simms22:
it just started its testing phase. and morfic just let me know that he accidentally lowered the voltage too much for 99% of the phones.