yashsingh1/xdaforums huggingface dataset:
[Samsung Infuse 4G] bradbusa:
technically it never actually existed in the first place, but you can download that in version 1.8
[Samsung Infuse 4G] Dani897:
it was nothing but a problem with the math. with Samsungs timing setup 200mhz jumps are optimal, smaller jumps need changes, change too many clocks and sometimes yoy get reporting problems. 1800 is probably too much for almost all of us. 1700 it reachable but if you notice bedwa took out the 900,1100,1300,1500,&1700 steps. he wants to maintain the proper timing setup for maximum stability and his cpu probably won't run at 1800 givving him no way to test the kernel fully for a release.
[Samsung Infuse 4G] Entropy512:
There's also the fact that the sysclock divider is limited to 8 - So to keep the system clock below 200 MHz, CPU can't exceed 1600.

The sysclock does NOT like to be overclocked - even a few MHz over 200 and stability goes down the tubes.
[Samsung Infuse 4G] Dani897:
ahh. seems like for a faster clock you'd have to rewrite the cpu driver then. that makes sense. why it was never done on xda for the sgs or nexus.
[Samsung Infuse 4G] Entropy512:
No - it's a fundamental hardware limitation. The clock divider maxes out at 8.

http://xdaforums.com/showthread.php?t=1111866 has the known documentation for our CPU and a few other things - if you read the Clocks section in the processor datasheet you learn a lot about what's possible and what's not. 1600 is the limit without sysclk going over 200. And you're always going to be limited to a CPU speed of 8*sysclk. Since sysclk doesn't like going beyond 204-206 or so, this puts pretty significant limits on the CPU.
[Samsung Infuse 4G] JordanElliott:
O. So well never oc past 1600 u mean to say? :(
[Samsung Infuse 4G] Dani897:
that's what he's saying. we have reached the limitation.

I do remember unhelpful saying that the theoretical limit was 1.6 long before there were kernels that went over 1.2. I didn't know he meant hardware limited to, just thought that was some rating Samsung gave it. now it makes sense.
[Samsung Infuse 4G] ookba:
So are we the only ones not seeing any use above 1200 Mhz? Any ideas why? Bedwa?
[Samsung Infuse 4G] drowningchild:
in voltage setting make sure the other freqs are checked

forgot about this :P
[Samsung Infuse 4G] ookba:
They are...
[Samsung Infuse 4G] drowningchild:
i have no clue?

i did uncheck 1.2 though
[Samsung Infuse 4G] ookba:
What freq do you have enabled? And what UV?
[Samsung Infuse 4G] drowningchild:
no uv(at the moment) 100,200,400,600,1000,1400,1600

it jumps right to 1600

might change it around
[Samsung Infuse 4G] a3plew:
Is there some way to disable bln. Or can we get a version without it. It seems that even if I disable bln the button lights can be activated by touching them with the screen off.
[Samsung Infuse 4G] a3plew:
After some quick testing the buttons lights can be activated with the screen off when using the charger. If unplugged they can still be activated right after you lock the screen.
[Samsung Infuse 4G] TheNetwork:
No one replied D:
[Samsung Infuse 4G] cpunchin:
That did the job!... thanks.

Is there a place in VC to specify that the init.d filename is different?. Now I have to manually rename the init file everytime I change it
[Samsung Infuse 4G] scoppola:
Both kernels not stable for me even with no UV. Phone reboots several times a day. Also, BLN only comes on for about a second when a message comes in.

No problems for me with v1.8, even with near max UV.
[Samsung Infuse 4G] Entropy512:
It sounds like BLN may need a revert.

My current build is identical to Core-A except I synced my fork BEFORE BLN was put in. That's the only difference, and I've been rock solid.
[Samsung Infuse 4G] tight686:
While I hope you all with BLN get the help for your problems I gotta ask.

PLEASE Bedwa don't drop bln. It's been nothing short of a blessing for me and this phone.
[Samsung Infuse 4G] bedwa:
I'll pull my core A and B that were pre BLN and post later today....

On the frequencies sticking, I'm not sure.... it seems to hit 1200 on mine. Not as frequently as some of the others, but it does. I'm running 16, 12, 8, 4, 2. With either core.
[Samsung Infuse 4G] MikeyMike01:
I have A with BLN. I can't undervolt as much as before. Otherwise has been perfectly stable.

Sent from my Infuse 4G
[Samsung Infuse 4G] entropism:
My undervolts (completely stable) with 1.8 went like this:

100-1000: -150mv

1200: -100mv

1400: -75mv

1600-1800: -50mv

Now, I'm unstable if I drop below these values:

200, 400, 600, 800: -75mv

1000, 1200: -50mv

1400, 1600: -25mv
[Samsung Infuse 4G] stuartmc:
Superb work Bedwa! I'm running core B, full OC and mild UV. Bln is working perfectly with the bln pro app. Don't lose the bln in any future additions- it's just what I neded...none of the other notification apps worked for me.
[Samsung Infuse 4G] MikeyMike01:
Almost identical to my settings.

Sent from my Infuse 4G
[Samsung Infuse 4G] entropism:
Looks like I tried to UV a little too much (dropped 200-800 to -100mv) and now my phone freezes before it fully loads the OS. Let's see if I can fix this without a wipe. oh well.

Edit: Flashed 1.8, got into SetCPU, disabled everything. Rebooted to install 2.0, works fine now (with the much milder UVs)
[Samsung Infuse 4G] jhego:
Im having the same issue.
[Samsung Infuse 4G] SiL3nTKiLL:
downloading now!
[Samsung Infuse 4G] JordanElliott:
Wait. So core a doesn't have nani?
[Samsung Infuse 4G] bori1030:
ok so i flashed the 1.8 some time ago and phone just turns off by it self when sceen goes off after reboot it will not stay on.. no big deal just went back to 1.5 its been flawless so now i see the 2.0 with BLN so flashed that....and the same problem phone will NOT stay on at all just keeps turning off on its own I so just reflashed the 1.5 and everything is A OK.... any help..
[Samsung Infuse 4G] JordanElliott:
Are u undervolting at all?
[Samsung Infuse 4G] Ltilt2:
Core B

Using Core B/ at 1664/1664/ cfq/ conservative

1664-75

1248-75

1040-75

624-50

416-50

208-50

104-50

I have been using these settings. it works perfectly for me. no SODS or Freezes. Good Battery life.

disable wife & GPS.

Thanks Bedwa for this great kernel
[Samsung Infuse 4G] bori1030:
yes i am have settings saved for undervolting that have not given me any problems great battery life with 1.5 ..but like i said after flashing 1.8 or 2.0 phone just dies...
[Samsung Infuse 4G] JordanElliott:
Reflash using odin and start over
[Samsung Infuse 4G] bedwa:
Don't Odin, remove voltage script and flash, then setup your phone again.
[Samsung Infuse 4G] indymx:
I spoke too soon. After running for a while, cfq/conservative and no other changes to OC or UV, I get audio skip & stutter quite a bit.

I haven't tested yet on wired headset, this is happening on my bluetooth stereo headset.

Could it be a bluetooth issue?
[Samsung Infuse 4G] bedwa:
Unfortunately I do think it is.... I have a Motorola roadster and it always seems tinny through it rather than my standard earbuds. Supercurio has made me an audio snob....
[Samsung Infuse 4G] indymx:
Can anything be done? or should I just wait for GB?

Just a note, I don't have these problems with audio when running the Community Kernel from gtg..
[Samsung Infuse 4G] Entropy512:
Try Core-A. Bus overclocking could be hosing up the Bluetooth subsystem a bit.
[Samsung Infuse 4G] bedwa:
That too..... I am going to tweak core B a bit in the next few days... I've noticed a few other goofy things as well.....
[Samsung Infuse 4G] JordanElliott:
When I place a call it sounded very staticy. Then I reflashed to community kernel and it was gone. I had it on core b
[Samsung Infuse 4G] bori1030:
thanks weezy and bedwa will try what bedwa said first thanks!!

edit. ok had to reinstall rom then flash kernal but i mainly did this for BLN and it has not worked for one notification. I'm i missing something?
[Samsung Infuse 4G] JordanElliott:
Sorry. I tried :/
[Samsung Infuse 4G] Entropy512:
Run Core A.

Everyone should be starting with Core A - if you have issues with Core A, then there's no way you'll not have issues with Core B.

If you have issues with Core B, go back to Core A. Bus overclocking is highly experimental and is notorious throughout history for causing all sorts of weird stuff to happen since the early days of overclocking.
[Samsung Infuse 4G] trouzzermouse:
On my old iphone 3g i always got a skip when playing music through bluetooth.
[Samsung Infuse 4G] Ltilt2:
What if I have no issues with Core B? LOL I keed!!! :D
[Samsung Infuse 4G] slyguy2000:
I am totally loving Core A, its nice to have BLN again, loved that feature when I was running my Captivate.

I am not, overclocking, just trying to massivly undervolt to extend battery and still be solid and stable.

this is what I am running now and it is rock solid!

YMMV...
[Samsung Infuse 4G] bori1030:
how did you get BLN working I've been at it for about two hrs nothing blinks or turns on after notifications
[Samsung Infuse 4G] slyguy2000:
have you downloaded Blinky from market?

Blinky will allow you to turn the feature on, and config the frequency of the blinks.

update on BLN feature:

I found that, at least with Blinky, using 5 second checks, with 1 second on, 1 second off works well, changing them to something else is hit-or-miss on if it will work...
[Samsung Infuse 4G] bori1030:
seems to work now with Blinky thanks
[Samsung Infuse 4G] slyguy2000:
no prob, glad I could help.
[Samsung Infuse 4G] nelomen:
I flashed core B and it waz working fine and all of a sudden my phone went to reboot and would not stop rebooting. I could not flash any roms for some reason so I had to odin back to stock. After a day of rerooting and getting cwm back on the phone I flashed Refuse 1.7, then core B and have been having no issues for a full day. And it has awesome battery life now. All day checking for updates on Xda(like 100 times or more) listening to audio book for 2 hours or so and still have 46% left. Loving this phone.
[Samsung Infuse 4G] Dani897:
bedwa what do you think of this ?

xdaforums.com/showthread.php?t=1171948

has he made mistakes and having a frequsency reporting error or has he overclocked the buss alot? and what do you think about his voltage mods? he has different kernels for cpus that don't clock well and claims to be able to ger more fro them. is this all just an unstable experiment gone wrong? is there hope foe more speed? if the timing structure is a problem maybe his voltage mods work and could mean more speed for users that can't hit 1.6 ghz yet. who knows.
[Samsung Infuse 4G] Entropy512:
He's cranked the bus a LOT. I'm actually surprised he was able to crank it that much on any device. Bookmarking for reference.
[Samsung Infuse 4G] P1 Wookie:
Yeah sometimes it helps to disable the wife. lol
[Samsung Infuse 4G] bedwa:
Hadn't looked at glitch in the last few days.... bookmarking git.
[Samsung Infuse 4G] slider2828:
Core B is pretty awesome... nenamark and linpack scores are very good compared to old kernel at 1800mhz.....

Does anyone have a flickering bln sometimes? Its weird. Sometimes it just flickers on and off....
[Samsung Infuse 4G] Ltilt2:
Very true, lol
[Samsung Infuse 4G] AiyoX:
Yeah, it tends to do that. Sometimes, if you touch the capacitive buttons without waking the device, they'll turn on as well. BLN is still a bit glitchy, but overall it generally works well.
[Samsung Infuse 4G] Ltilt2:
1800mhz wasnt really 1.8 and yes it flickers but as long as my phone runs great, i dont care.
[Samsung Infuse 4G] The Jack of Clubs:
i am getting alot better performance now with this βcore kernel than the 1.8 one. what are your overvolts? tried to do all -150 from the old kernel but that caused a freeze. -100 on all is working fine though.
[Samsung Infuse 4G] Ltilt2:
If you uv too much, your device will freeze. The 1.8 kernel was actually like 15** instead of 1800
[Samsung Infuse 4G] The Jack of Clubs:
well i know that, doesnt mean i dont want to uv as much as possible.
[Samsung Infuse 4G] Dani897:
i have found the 2.0 kernels to act funny when you initially uv, after removing all the ocuv scripts and running a couple reboots i was able to get my previous levels of uv and more with core a. i got rid of core b because i got sleep death after messing with uv and my quickest solution was to flash core a, but now that i think about it the sleep death may have been too much clock or voltage differential on wake as i removed the 200 mhx seeing and it was jumping directly to 400 mhz.

right now on core a i am running -200mv across the board but on first boot i couldnt go more than -100 because after putting it on performance governor and trying a quick linpack benchmark the settings would revert or the phone would freeze, latter i was able to add more uv with total stability. this is the same behavior i noticed with core b initially but on core b i left it where it was and didnt try further experimenting.

my core a settings

100 -200

400 -200

800 -200

1200 -200

1600 -200
[Samsung Infuse 4G] bori1030:
so thought it was working but after reboot and you let stand til the screen goes off it does not go to sleep it just turns off after every reboot. ill have to open the phone after reboot so it wont do that but some times after doing something and leaving the phone alone until it goes to sleep boom again its off while on phone calls the screen goes out but never turns back on, after hanging up the phone is off again i finally did a clean install reflashed ROM infused latest and then kernal it seemed like it was working but then it started doing it again if i let the phone go to sleep on its own it just turns off. so i just flashed 1.5 again and everything back to normal no problems no shutdowns this has been happening on the 1.8 and the 2.0.... and man i want some BLN but with these shutoffs cant run that 2.0..any ideas?
[Samsung Infuse 4G] indymx:
Ok.. I installed Core-A right after reading this.. It worked fine last night, and I thought today we had something. But no..

It's doing it with this kernel too. And I did confirm that it's only doing the stutter on bluetooth. I plug in the headphones and it's flawless. I'd just go with that, however, I really don't want to be wearing headphones in my truck. I really need bluetooth to work. I also use it at work, and like to leave my phone on my desk while I move around doing my work.

I see that your GIT tree for the bluetooth drivers don't seem to be different from the gtg's tree Bedwa, but for some reason I don't experience the issues with bluetooth when I'm running his kernel.

I would have to guess that it's not something with the bluetooth driver itself then, but something with the memory management or voodoo sound driver that's causing bluetooth to skip.

Also, just an aside, I was wondering if something could be done about notification sounds to be set to not interrupt the audio played from either music player or video players? It's rather annoying to have a notification come thru while watching a movie.

Thanks again guys, you're doing excellent work!
[Samsung Infuse 4G] theoracle09:
Edit: resolved
[Samsung Infuse 4G] Dani897:
2480 in quadrant on core a! will try on core b soon,
[Samsung Infuse 4G] Dani897:
core b results.

and yes those are my voltage results, it runs like that just fine.
[Samsung Infuse 4G] bradbusa:
wow thats pretty impressive, both the UV and the benchmark score
[Samsung Infuse 4G] Markiddo:
Hi, i'm looking for the best rom to use with this, which do you guy's recommend ? I've been on infused and it's gone amazing :D and thanks bedwa for you're awesome development!
[Samsung Infuse 4G] VinnyCh4se:
To be honest they are all amazing in there own way but for right now your better off saving your battery life and your sanity and sticking with stock rooted because gingerbread roms are being baked up right now and are well worth the couple extra days of waiting

Sent from my Samsung Infuse with Infused 1.5.3
[Samsung Infuse 4G] Entropy512:
Try Defuse - It's 90% identical to Infusion with the difference being undervolt/overclock.

If Defuse is also problematic then we can work from there. I don't have easy access to any A2DP device any more - the car with my A2DP radio was given to a good friend.
[Samsung Infuse 4G] Dani897:
Hint, airplane mode helps, it keeps ads from running.

Also the uv did turn out to be too aggressive. It froze a while later.
[Samsung Infuse 4G] Ltilt2:
I cant wait for a oc kernel for GB
[Samsung Infuse 4G] bedwa:
Workin on it. ;)
[Samsung Infuse 4G] nelomen:
Bedwa you are awesome! Loving your kernel, can't wait to try your gb kernel when your done.

sent from my Infuse with Refuse 1.7
[Samsung Infuse 4G] Markiddo:
Will this Kernel be compatible with the expected release of infused v2 beta "2" ?
[Samsung Infuse 4G] JordanElliott:
No. No 2.2.x kernels will work on gingerbread.

I'm On One
[Samsung Infuse 4G] Ltilt2:
I can read your mind, as I read GTG's mind about Gingerbread. I know you are already working on an oc kernel and for that, I thank you my friend.
[Samsung Infuse 4G] Entropy512:
FYI LinuxBozo made a TON of build/compile fixes last night that don't seem to be in your fork. :)

Also Netarchy has a lot of good stuff in his repo, I'm considering pulling some of it in. Gotta chat with LB when I get time on IRC.

A bit of chatting - pulled jhash3, not pulling in the rest until the "extraversion vs. RFS modules" issue is resolved.
[Samsung Infuse 4G] JordanElliott:
Your amazing

I'm On One
[Samsung Infuse 4G] JordanElliott:
Nice. Keep it up!

I'm On One
[Samsung Infuse 4G] ookba:
bedwa, you might wanna change the title of this thread to reflect Froyo or 2.2 kernel. May be a lot of bricks once we get a working CWM kernel for GB.
[Samsung Infuse 4G] Ltilt2:
Even if Bedwa changes the title, you will still see people flahsing the wrong kernel. that's a given.
[Samsung Infuse 4G] MikeyMike01:
You can very easily flash the appropriate gingerbread kernel again if that happens.

Sent from my Captivate
[Samsung Infuse 4G] Ltilt2:
for you and I but for those who tried installing a froyo kernel onto a GB rom?
[Samsung Infuse 4G] Entropy512:
That's exactly what he meant. heimdall/odin a GB kernel.
[Samsung Infuse 4G] bedwa:
I'm working on some of the same on the back end.... lolz... I've been looking over at existz's i9000 kernel work.

I'm on it... Though I do agree with everyone else through. ;)
[Samsung Infuse 4G] crispy1805:
Does anyone else experiencing hot infuses with the screen off profile in setcpu? I have my max cpu speed at 400 with the standard settings in alpha.
[Samsung Infuse 4G] mfpearson:
setcpu does not work properly with infused rom/infusion kernel. i found this out through lots of experimentation of my own + reading others' stories.

use voltage control - the free version works flawlessly (minus the profiles that setcpu has), and if you like it when you test it, you can donate later.

i do miss that "screen off" setcpu profile... but the overall results i get from voltage control are very comparable to the results i got from setcpu before i flashed the incompatible rom/kernel. you won't be disappointed with voltage control!
[Samsung Infuse 4G] bradbusa:
just installed core b. right off the bat, i noticed that im not able to UV quite as much. but performance is significantly better than before(coming from 1.6)
[Samsung Infuse 4G] squall_x2x:
I'm on your Infused 1.53 ROM... which kernel version is it on now? I disable VooDoo Lagfix and should I disable the /system conversion too while update to new ROM?

Thanks!
[Samsung Infuse 4G] Dani897:
looks like you got the wrong thread. disabling voodoo disables everything. that option is to have rfs on /system while voodoo still effects the cache, and data partitions.

you can safely flash now that voodoo is disabled. make sure you let it reboot and do the conversion before flashing. you should here robot voices.
[Samsung Infuse 4G] slyguy2000:
absolutly loving the battery life with CoreA!

this is with wifi on, gps on, 2 gmail accounts, 1 exchange, 1 hotmail...the one little charge session, was using copilot w/gps, and streaming Pandora in the car via the car dock... this is the best I have ever seen while using this phone!
[Samsung Infuse 4G] Markiddo:
Is there any way to measure my cpu speed because this is what's happening w/ cpu spy.

Sent from my Infuse 4g

Running Infused 1.53

Bedwa's Infusion 2.0 Beta Core
[Samsung Infuse 4G] slyguy2000:
mine works fine
[Samsung Infuse 4G] bradbusa:
bedwa stated in a previous post that cpuspy does not work with core B.
[Samsung Infuse 4G] Markiddo:
Thanks! I haven't been reading the full thread. I'm I switched to core A and I'm using set cpu to uv and I'm stable so far, but I heard some proper say that voltage control is better . What do you think?

Sent from my Infuse 4g

Running Infused 1.53

Bedwa's Infusion 2.0 Beta Core
[Samsung Infuse 4G] slyguy2000:
voltage control works very well, simple interface, and can set temp settings that hold till reboot, or set semi permanent boot settings...
[Samsung Infuse 4G] crispy1805:
Thanks for the response. Everytime I try to save voltage states now it freezes and I have to pull the battery. I'm using a few examples from the thread here that works well for others. I've tried setcpu and voltage control.
[Samsung Infuse 4G] JordanElliott:
Btw. What works well for others. Might wont work for you. Its hard to explain. I found out the hard way.
[Samsung Infuse 4G] crispy1805:
What is deep sleep? Is it when the processor isn't being used at all? Mine only has about an hour of deep sleep over the last day. That can't be good at all.
[Samsung Infuse 4G] jgeezy24:
re you using cfq conservative? what is everyones experience with CoreA and B in this regard?
[Nexus S Q&A, Help & Troubleshooting] nixguy:
I installed oxygen rom and I can't seem to be able to install car home..any one had this issue?
[Nexus S Q&A, Help & Troubleshooting] crucio:
yeah i have the same problem. i can't install earth neither.
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
Car home i am unsure if I've ever been able to install on Gingerbread. Earth however should work. If it's showing as a non compatible device in the market then it's likely the build fingerprint/signature in build.prop
[Nexus S Q&A, Help & Troubleshooting] MarkVis:
I had that issue also in oxygen so i just flashed a different rom and its all working now.

Sent from my Nexus S c",)
[Nexus S Q&A, Help & Troubleshooting] JGAGNON10:
i have the same problem on oxygen...i'd switch roms but i like oxygens simple speed....any other roms that are similar anyone can suggest?
[Nexus S Q&A, Help & Troubleshooting] krohnjw:
You could just edit /system/build.prop and match a known build fingerprint:

I changed a few things enumerated below on a compiled AOSP 2.3.5 rom to get protected apps visible again (needed Touchdown key). Earth is also available again.

ro.build.id=GRJ22
ro.build.display.id=GRJ22
ro.product.model=Nexus S
ro.product.brand=google
ro.product.name=soju

ro.build.fingerprint=google/soju/crespo:2.3.4/GRJ22/121341:user/release-keys

Compare with your values in /system/build.prop. Back up the original, make your desired changes, reboot and check.
[Nexus S Q&A, Help & Troubleshooting] MarkVis:
There you go. But I recommend infinity rom if you'd like to try another rom. It's almost like oxygen but it has transparent pull down notification.

Sent from my Nexus S c",)
[Nexus S Q&A, Help & Troubleshooting] nixguy:
It works on infinity......now I'm on carbon beta rom it works on it also
[Nexus S Q&A, Help & Troubleshooting] crucio:
can you share a link for infinity rom. i searched but couldn't find anything
[Nexus S Q&A, Help & Troubleshooting] MarkVis:
Infinity is I believe discontinued. Jonathon Grigg the dev behind infinity has a new rom. It's called carbon. Go check it out in the android dev forums.

Sent from my Nexus S c",)
[Windows Mobile] illi:
The threaded e-mail have been discussed in a number of forums. I have read them all. However, none addressed the issue with COM2 and it seems it is not possible at all.

I tried cooking (using OS Builder) with various combination.

Have anyone successfully cooked the threaded e-mail, especially for COM2 (21916) and willing to share their experiences?

Thank you