yashsingh1/xdaforums huggingface dataset:
[Nexus S 4G Android Development] sigaiser:
Which would you suggest using with Pete's ROM...stock or cm7, since his is a hybrid of both?
[Nexus S 4G Android Development] snandlal:
Reddv1 tought me that the cm versions just flash the zImage and the stock versions flash the complete boot.img

So....

zImage + ramdisk= boot.img

Stock zips flash boot.img which is the complete kernel (zImage+ramdisk)

Cm any kernels flash just the zImage on top of your existing ramdisk

I would just flash cm any kernel
[Nexus S 4G Android Development] info[]box1:
Thanks for the Dev
[Nexus S 4G Android Development] fergie716:
Like it so far.. Using post-2.3.3 colors on Oxygen 2.2.2

Thanks!
[Nexus S 4G Android Development] trevtt600:
Wifi does not seem to work. Getting a error when trying to turn on.
[Nexus S 4G Android Development] dazednconfused:
which one did you flash? I've flashed both CM7 kernels and my wifi worked just fine.
[Nexus S 4G Android Development] trevtt600:
Flashed the stock yellow. Just flashed the stock blue and all is well. Not sure why my phone Dosent like the yellow, but blue is working well. Thanks for the quick response.
[Nexus S 4G Android Development] merlthecruel:
downloaded. backing up. soon too flash. i will def post feedback. im not expecting anything other than amazing. wonderful work
[Nexus S 4G Android Development] snandlal:
Reddv1 is an up and coming super-dev
[Nexus S 4G Android Development] baldwin69:
my wifi doesn't work with the yellow kernel either. i'm using stock rom
[Nexus S 4G Android Development] reddv1:
I'll fix the wifi, sorry about that.

Sent from my Nexus S
[Nexus S 4G Android Development] blacknet101:
any update on the wifi issues concerning the yellow version. i too installed it and got the wifi error while trying to turn on. Hopefully it works soon cuz i miss messing with the voodoo colors :D
[Nexus S 4G Android Development] reddv1:
Fixed wifi, Update link in OP. Let me know if it's working.

Sent from my Nexus S
[Nexus S 4G Android Development] blacknet101:
woohoo its working! :D thanks a lot!
[Nexus S 4G Android Development] funcrusher:
Giving it a try today. Thank you.
[Nexus S 4G Android Development] reddv1:
Version 2.1

Updated kernel to version 2.1,

-Fixed the problem of the touch controls misbehaving after the proximity sensor has blanked the screen during a call.

-Touch Wake time out changed from 45 seconds to 30 seconds.

-BLD: i9023, fix (this time for real) the touchkey backlights not being re-enabled on touchkey press

-BLD, SLD & TW: Code clean-up

--------------------------------------

New Lucid Experimental 2.1.11: http://goo.gl/idvJQ

-Lucid Blue

-1.1Ghz

-BLD enabled, 30 seconds

-Touch Wake enabled, 30 seconds

-SD card read ahead increased to 1024

-2.1 bugfixes
[Nexus S 4G Android Development] funcrusher:
Lucid yellow was working great for me -- didn't run into any issues and battery seemed great.

Just flashed the experimental -- will let you know.

---------- Post added at 10:46 AM ---------- Previous post was at 10:07 AM ----------

Experimental definitely feels snapppppy.

I was texting while charging my phone when my phone froze for about 5 seconds, then restarted.
[Nexus S 4G Android Development] reddv1:
Try raising the voltage by 25mV for the 1100 MHz frequency to 1275.

Sent from my Nexus S
[Nexus S 4G Android Development] baldwin69:
2.1 yellow seems good so far (not that i expect to find any problems. lol). thanks for fixing the wifi btw
[Nexus S 4G Android Development] funcrusher:
Done.

Thankkkkks.
[Nexus S 4G Android Development] jta462:
Experimental is getting some random reboots. Great bat life and response though. On cm7 nightly 96. If you need logcat or anything let me know.
[Nexus S 4G Android Development] baldwin69:
out of curiousity, sometimes my 'home' button gets stuck - either my phone will freeze or the recent apps list will come up, the home button will black out while the rest of the lights are still on, and i can't do anything for maybe about 5 seconds. had this problem with one of the netarchy kernels too. i didn't have it happen on the lucid 2.0 but i'm having it on the 2.1 (yellow). is it maybe just a bad install? a kernel problem?
[Nexus S 4G Android Development] onigiri1692:
Anyone have any idea why the CPU frequency can't be changed with the 'CPU Settings' utility included in Pete's rom? the CPU toolkit force closes when I boot up my phone. I'm able to change the CPU frequency with setcpu but not the included utility yet this wasn't a problem with any of the other kernels I have tried out. I'm using the Luicd yellow 2.1 cm7/anyrom version of the kernel, should I try flashing the stock version of the kernel or would that cause problems?
[Nexus S 4G Android Development] reddv1:
I'll look into this issue. Don't flash stock version on non stock, it's the same kernel you'll just be messing your rom's ramdisk.

Sent from my Nexus S
[Nexus S 4G Android Development] onigiri1692:
I appreciate the feedback, aside from that one issue this kernel is running very smoothly, thanks for all your efforts.
[Nexus S 4G Android Development] funcrusher:
Haven't had any reboots since raising the voltage. I'm using Pete's ROM too and noticed that none of the other frequencies show with this kernel.
[Nexus S 4G Android Development] funcrusher:
Did flashing the experimental touch my ramdick?
[Nexus S 4G Android Development] funcrusher:
ramdisk* lol :/
[Nexus S 4G Android Development] SA-07:
Haha was that intentional :P
[Nexus S 4G Android Development] funcrusher:
no, it actually wasn't. ;P
[Nexus S 4G Android Development] reddv1:
No. But lets refer to the ramdisk as initramfs from now on, lol.

Sent from my Nexus S
[Nexus S 4G Android Development] reddv1:
Something is seriously wrong with your Nexus S dictionary

Sent from my Nexus S
[Nexus S 4G Android Development] funcrusher:
Lol. Goodnight guys.
[Nexus S 4G Android Development] reddv1:
Never had that problem, it could be caused by bld, cause I updated the code. Were you on netarchy 1.4.0 when it happened, that version has bld?

If you want/possible try running logcat and try to reproduce the problem while logcat is running and send me the log. That probably the only way to catch it.

Sent from my Nexus S
[Nexus S 4G Android Development] FAFS:
Great kernel I like the amazing colors using on miui
[Nexus S 4G Android Development] reddv1:
2.2 update

Update kernel to 2.2

Changlog:

2.2

-Removed Screen Dimmer

-Raised FPS to 65

-Raised SDcard read-ahead to 1024

-Bugfixes for BLD and Touch Wake

-Added Lazy Governor

-TUN support

Lucid Nexus 2.3 eXXperimental:

Blue: http://goo.gl/wpmgn

Yellow: http://goo.gl/rAzwe

-Everything in 2.2

-Deep Idle added and enabled by default

-BLD enabled at 30 seconds

-Touch Wake enabled at 30 seconds

-Runs at 1144Mhz
[Nexus S 4G Android Development] snandlal:
Glad to see this quality over here now. Thanks Reddv1
[Nexus S 4G Android Development] brokentoaster24:
I feel the color profiles in the experiments aren't right. Flashed both yellow and blue and tried changing settings in voodoo control and they both look the same

Sent from my Nexus S 4G
[Nexus S 4G Android Development] grifforama:
Goddamn it. Why do you devs have to keep churning out quality kernels ?

Don't you realize I've got work to do ?

;-)
[Nexus S 4G Android Development] reddv1:
Yeah, I noticed the same thing about the colors looking different. I thought it was my imagination, thanks for confirming the problem. One of the mods I added must've changed something, I'll look into it.

Sent from my Nexus S
[Nexus S 4G Android Development] Igotsanevo4g:
Can deep idle be enabled in the non experimental version? I'm assuming is just off by default, right?
[Nexus S 4G Android Development] reddv1:
No you can't. I wanted to test it out first before. I'll probably add it soon.

Sent from my Nexus S
[Nexus S 4G Android Development] brokentoaster24:
I think both kernels have old color drivers. Neither blue and yellow have gamma or screen hack sliders

Sent from my Nexus S 4G
[Nexus S 4G Android Development] Braneless:
Anyone using this with a 2.3.7 rom?

NS4G NSCollab Sprint 1.0.51, Matr1x 8.0+, Caelum Theme
[Nexus S 4G Android Development] snandlal:
Yes we are. And they work great
[Nexus S 4G Android Development] Braneless:
Awesome. Thanks!

NS4G NSCollab Sprint 1.0.51, Matr1x 8.0+, Caelum Theme
[Nexus S 4G Android Development] Braneless:
Bootloop after flashing on 2.3.7 rom. Bad zip download maybe?

NS4G NSCollab Sprint 1.0.51, Matr1x 8.0+, Caelum Theme
[Nexus S 4G Android Development] reddv1:
Maybe, I'm using a 2.3.7 rom. Which version did you flash? So it didn't even boot once?

Sent from my Nexus S
[Nexus S 4G Android Development] Braneless:
Blue for cm7. After splash screen it just went black and wouldn't respond until I pulled the battery.

Running NScollab 2.3.7.

NS4G NSCollab Sprint 1.0.51, Matr1x 8.0+, Caelum Theme
[Nexus S 4G Android Development] reddv1:
Try downloading and flashing again and see what happens. The kernel runs on stock speeds and uv is slight so you shouldn't have trouble running it.

Sent from my Nexus S
[Nexus S 4G Android Development] Braneless:
Damn. Dl'ed and flashed again with the same result. The only kernels I can get to run on my phone are matr1x and Tiger Stripes.

Tried Lucid, Trinity, or Apocalypse ... No luck :( Guess I'll just stick with matr1x 8.5 (phone won't wake up after overnight sleep with 9.0).

NS4G NSCollab Sprint 1.0.51, Matr1x 8.0+, Caelum Theme
[Nexus S 4G Android Development] reddv1:
Updated Kernel with the following

-Source updated to 2.3.7

-Rebuilt source

-Deep Idle

-Custom Voltage

-Live OC

-Wifi Tweak

-Freed about 12mb memory by disabling Android_PMEM

-All bugfixes up to 11/21

-Ramdisk update to latest version

-Misc check github
[Nexus S 4G Android Development] snandlal:
Lovin it. Thanks!
[Nexus S 4G Android Development] jeffreynothing43:
I had good luck with your earlier versions...I'm really hoping the updated ones provide the same. With Franco's and GladO everything starts Force Closing after like 24 hours. Do you have any suggestions to prevent that from happening on this kernel?
[Nexus S 4G Android Development] reddv1:
I can only suggest to not run to many apps at the same time, reboot every few days and use cfs, bfs starts giving me trouble after awhile. Everything starts hanging, especially incoming calls screen.
[Nexus S 4G Android Development] reddv1:
Lucid blue 4.0 is here for Ice Cream Sandwich!

http://goo.gl/L9rsD
[Nexus S 4G Android Development] reddv1:
Update Lucid blue to 4.0.1 for Ice Cream Sandwich.

Fixed Multi-Touch.

Link in OP.
[Nexus S 4G Android Development] reddv1:
Update Lucid Nexus to 4.0.3 for Ice Cream Sandwich.

Add Lucid yellow support

Fixed USB mass storage support.

Link in OP.
[Nexus S 4G Android Development] jeffreynothing43:
Just a request...but is there anyway you can make it so that I can charge to 100%? Right now its stopping at 94... Just wondering. :)
[Nexus S 4G Android Development] zeeraf:
i tried Lucid Blue 4.0 for the ICS rom .... now the USB options are there in the pull down menu but any choice i make causes my phone to reboot
[Nexus S 4G Android Development] jeffreynothing43:
Awesome sauce?!

Ok man...I will hafta say...your kernel is first with live OC and deep idle not to make my phone force close every single application after 24 hours. I really hope this keeps up because so far I am very happy with its performance and longevity of battery life. Just make it go to 100 and I will be very very happy. Good work man. Not sure what the other guys did wrong but this rules.
[Nexus S 4G Android Development] reddv1:
Update Lucid Nexus to 4.0.4 for Ice Cream Sandwich.

4.0.4

-EXT4 optimization

-init.d script support (requires busybox)

-USB storage/adb bootup Bug fix

-Wireless tethering support (patch from Koush, doesn't work on kwiboo's ICS)

Can someone confirm if wireless and usb tethering are working on Koush's ICS rom, thanks.

Link in OP
[Nexus S 4G Android Development] jeffreynothing43:
Am I missing something...? How do you get 'deep idle' to kick in... It seems like sometimes it works and sometimes it doesn't. Any help would be appreciated.
[Nexus S 4G Android Development] Mecid8:
please realese update with slqb for gingerbread.
[Nexus S 4G Android Development] GeezyAF:
Open Camera.
[Nexus S 4G Android Development] jeffreynothing43:
Thanks for the reply, but I found that opening the camera was only working sometimes...it is not a SURE thing that it kicks deep idle in. I actually ended up removing Gtalk with video and replacing it with the version that doesn't have video so I don't have to worry about it anymore. I don't use video chat anyhow. If anyone wants this Zip file, please PM me.
[Nexus S 4G Android Development] JohnCorleone:
oh man, all these goodies to test tonight! Thanks. Question: should this work on kwiboo and Koush builds? I was just about to flash Koush's latest...edit...is Lucid blue the one with the richer colors?
[Nexus S 4G Android Development] reddv1:
Yes Lucid blue has the richer colors, more bluish than yellow.

Yes Lucid 4.0.4 works with both roms, but tethering doesn't work on kwiboo's rom.
[Nexus S 4G Android Development] reddv1:
Updated Lucid Nexus to 4.0.5 for Ice Cream Sandwish

4.0.5

-Data stats and limits fixed

-Wifi tethering works on all ICS roms

-USB tethering works on Kwiboo's ICS rom

-Tweaked Lucid Yellow colors a bit

Link in OP
[Nexus S 4G Android Development] GeezyAF:
It's the only way to activate actually. reddv1 also agrees.

I use Trinity and every time I open Camera after a reboot, DI kicks in.

I know by letting my phone sleep for a little then checking idle stats.
[Nexus S 4G Android Development] derekwilkinson:
I keep getting random reboots on this with ICS... which is a shame because i liked bln. I guess i'll switch to matrix for stability.
[Nexus S 4G Android Development] jeffreynothing43:
This is straight from Ezekeel's Deep Idle thread...and I will add I can reboot my phone and check deep idle stats and confirm that I do not need to open the camera.

CAM bug

There is a bug in the Google Talk app with video-chat which causes the CAM submodule to be activated on boot. As a consequence the DEEP IDLE state will not be used. Opening the camera app once and then closing it, shuts down the CAM module so after that the DEEP IDLE state will be used properly. The Talk version without video-chat does not have this issue. Unfortunately both version are shown as Version 1.3 in the application info, however the app size differs (740KB with video-chat, 500KB without video-chat) as well as the permissions (with video-chat additionally has the permission 'Hardware controls').

Link:

http://xdaforums.com/newreply.php?do=newreply&p=19688393
[Nexus S 4G Android Development] reddv1:
SLQB

Here are kernels with the addition of SLQB nothing else is added.

Lucid-Blue-3.1-slqb

http://goo.gl/HaA2L

Lucid-Yellow-3.1-slqb

http://goo.gl/abaxU

Lucid-Blue--ICS-4.0.6-slqb

http://goo.gl/WfGFJ

Lucid-Yellow-ICS-4.0.6-slqb

http://goo.gl/3i7b5
[Nexus S 4G Android Development] reddv1:
No More Updates

I won't be updating this kernel anymore, all feature and bugfixes are up to date for both Gingerbread and ICS.

When the official ICS kernel sources for the Nexus S comes out I might make Lucid-Nexus kernel for that.

Thanks for the support.
[Nexus S 4G Android Development] info[]box1:
Thanks for your Energy and Persistence
[Nexus S 4G Android Development] svghost:
I am having problems with usb storage. It says usb connected as installer. I try to switch it to mtp or camera and it either restarts or turns the mode on and off quickly.

Odd problem...
[Nexus S 4G Android Development] ftwaynejuggalo16:
Anyone gotta link for blue 3.0? For gb

Edit: Nevermind found one!
[Galaxy S II General] jr866gooner:
It does, unfortunately I noticed this too but it uses little resource. It is annoying to see the open applications count as "one" when you have finished!
[Galaxy S II General] siddardhab:
Apps like messaging and internet stay in the background even after you close it,because these apps are frequently used and they load faster the next time you use it,but dont worry the android OS will kill them eventually
[Galaxy S II General] DeHann:
I waited a long time and the Messaging application never actually closed.

I suspect it is a similar bug to the Contacts issue I had with Froyo where the application remained open. This was later fixed in Gingerbread...

Does anyone else see Messaging remain open in the Program Monitor widget?
[Galaxy S II General] jhernand1102:
It stays open for me also, If and when the resources get low enough it should close but since we have so much ram i don't think it will ever close. It doesn't really bother me.
[Galaxy S II General] devilkin:
Stop using task killers. The android os does not work like windows that relies on free memory. It keeps apps in memory so that they can be instantly opened later. Some system processes will even be started again after you close them.

If a program is in memory but not used for a while it will be flagged to be removed if another app needs more memory. Just because an app is in memory does not mean it is using your CPU.

You are wasting more battery by killing things that you will use again or that the system will restart anyway. This phone has a lot of memory, let the phone use it!
[Galaxy S II General] DeHann:
Thsnks for your reply; but, I am not using a task killer...

I am just wondering why the stock messaging application is displayed in the Program Monitor once exiting via the back button. Is it a known bug? Also, is there any way to fix it besides killing it or using another messaging app like Handcent?
[Galaxy S II General] BrandoHD:
Known bug, it's not a bug, it's a feature,

Your phone has almost 1 Gig of ram, why would you want to micro manage what apps use the ram, has your phone ever run out of ram, has your phone slowed down, does it lag, do you attribute this lag (if there is any) to the messaging app running in the background???
[Galaxy S II General] kryptoner:
when I replaced my messaging app using stock sms app, then the bug/feature went away
[Galaxy S II General] DeHann:
I am not sure why, really. All I am looking for is to have the Program Monitor display 0 instead of a 1...

I am famous for leaving unused tasks open and like to monitor for them using that widget. If I understand correctly running tasks consume CPU which, in turn, drains the battery.

I have noticed that the messaging app is not in the Battery usage list; so, at this point it is an annoyance more than anything...
[Galaxy S II General] DeHann:
Interesting. Can you explain this in more detail?
[Galaxy S II General] kryptoner:
I downloaded messaging Google stock app from here - http://xdaforums.com/showpost.php?p=16699746&postcount=1

then I put it in system/app folder using root explorer and installed it, i deleted old messaging app...

now whenever I exit messaging using back button and open task manager, I don't see messaging app in active tasks...
[Galaxy S II General] DeHann:
Thanks. I tried it and you are right. I ended up reverting though. Going to look into it more if/when I find time.

Hopefully it is not the same in the next firmware release; but, for now, it is only an annoyance.
[Galaxy S II General] bruflot:
Advanced task killer :)
[Galaxy S II General] xeq544:
No, dont use task killers. If anything, it only eats more resources. Android keeps those apps open for a reason, when you open it next time its quicker and actually needs to use

less

resources. Free memory= useless memory, If there is an app which needs more memory (like a game) android will automatically kill "suspended" apps on background to free up memory. And when you finish playing it will restore those apps again. Killing it with force only causes the app to restart again and again and again and again.... Even windows does it (a little bit differently though).

And if you

really

want to have control over your processes in background, use watchdog which will warn you if theres an app eating resources in the background.
[Galaxy S II General] DeHann:
I am running Watchdog app now & previously monitored the Battery Usage app and show no messaging application displayed. So, it is just an annoyance for me...
[Galaxy S II General] lupixxx:
copied the sms app in the system/app folder, but when i try to install it, it says couldn`t install application
[General Questions and Answers] Parth_goklani:
hey guys is there any live tv app for android for in india r u using if yes then which:confused::confused::confused::confused::confused:
[General Questions and Answers] cdesai:
Yea

Try Mobiletv in samsung app store
[Epic 4G General] andrewt328:
whats the best modem...best signal and speeds? im currently using ee03
[Epic 4G General] Robalboa:
i found that ef10 worked best
[Epic 4G General] KennyG123:
Personal choice. EC05 is still molst people's choice. EE03 is another popular choice. I have tried them all and found the best speeds on EE03 and EH17. You have to try them for yourself and test for your unique phone and area.
[Epic 4G General] jdelano:
I've found that EH17 has worked best for me; indoors 8/8 lock and GPS 2.6m accuracy. I can even connect to 4G; which I haven't been able to do since EB13 modem and finally cell strength has improved by a bar.

As with anything .. YMMV
[Epic 4G General] Gavisann:
I am using EG22 currently, the only problem is with the cell strength indicator. I am thinking about trying EH17.

Send from my SPH-D700 (Samsung Epic 4G)
[Epic 4G General] JohnCorleone:
See, this is what I don't understand. I have repeatedly been told that modem has no effect on 4G. Can anyone definitavely tell me if this is true or not please? Does the modem change signal strength? Does it effect 4G,Wifi?
[Epic 4G General] ugothakd:
It definitely has an effect on your 4g. Try flashing a modem in odin, and pull the cable. Thatll screw up ur baseband (modem). WiFi will work, 4g won't (or a 3g or SMS or calls). WiFi is a module in the rom (or kernel) if I remember right.

sent from my uncyanogen modded epic 4g. with the key skips.
[Epic 4G General] JohnCorleone:
Well, when people run Speedtest and post results I feel its necessary to run it at least 15 or 20 times and average it out. I am still using EC05 modem and I average 5-6Mbps download speeds but I get bursts on some runs of 8+Mbps. I know that I personally haven't seen any marked improvement in average speed or signal strength myself. I like EC05 and EE03 the best because GPS works the best for me on those
[Epic 4G General] digiblur:
Check your 4g modem version in wimax info in the wimax dm screen. It doesn't always match nor is it upgraded with every modem upgrade.
[Epic 4G General] malcolmXman:
Back on DK28, yep, no joke.
[Epic 4G General] a2tz:
Went from ec05 to eh17. Noticeable increase in speeds and signal for me....used to get max 300k downloads in speedtest...now I can get max a meg or so. Haven't tested it all over but it seems faster all around.

Gps does seem a little....slower maybe? I can still get good locks on 7 or more and it is usually very quick....but sometimes it seems to take a little longer then it used to on ec05. Just my opinion.

Running bonsai 4.1.3
[Epic 4G General] JohnCorleone:
Thanks for that digiblur.
[General Questions and Answers] karsten1990:
what is the best root for my phone and i want to get paid apps for free ??
[HTC EVO 3D] johnequickiii:
About a day ago I got a PRL update to 21081 and decided to go back to the original proxy settings because my internet speeds and signal were still really slow. My speeds are back up to about where they belong I think.

Yall should try it and see what happens. I know I'm very happy with it. Far more than I was with the proxies out.
[HTC EVO 3D] johnequickiii:
Seriously. I had such connection and signal strength issues when I took out the proxy info, but when I put it back in, it bumped the speeds back to where they should've been in the first place. I recommend at least trying it.
[HTC EVO 3D] thizzlemania91:
What did you put into your proxy I messed up I didn't save the original settings like I should have :(
[HTC EVO 3D] GooseEye:
Default settings are:

RTSP proxy IP = rtsp.vog.sprintpcs.com

RTSP proxy port = 554

HTTP proxy IP = pd.vog.sprintpcs.com

HTTP proxy port = 8085