yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] jhr5474:
I

guess that is why it was constant reboots with continuum today? what does bigmem at the end of the kernel name mean compared to the other kernels available?
[Captivate Android Development] existz:
Bigmem has more "free" memory... normal version has 341mb, (debug version is 339) but the bigmem is 353mb (352 with logcat)...but it breaks 720p video recording...it just gives more free memory
[Captivate Android Development] existz:
Continuum 5.4.1 is up for those on JVH...the kernel in the release should fix most issues
[Captivate Android Development] jhr5474:
You

Said you changed the OC in it though? For the 5.4.1?
[Captivate Android Development] neubauej:
Damn!

I loaded continuum 1.5 this am, have been fiddling with it all day wondering why i couldnt get anything over 1.2 stable, killed the battery, and while letting it charge finally think to check here, and find you have already fixed it!

Here is looking very much forward to 1.3-1.5 oc stable!

Thanks!!!

:D
[Captivate Android Development] existz:
Yea for now its back to 1.2ghz, the oc code for 1.3/1.5ghz was the cause for the usb charger rebooting issue/tw4 reboot issue...so its removed for now until i can figure out what the problem is..But the kernel in 5.4.1 seems to fix all the issues reported in Continuum thread for 5.4 (the kernel issues)

But for right now, the JVH kernel will stay for Continuum only... Once i get 0.1.7-final finished, for jvb and jvh, ill post a release here...until then, only JVH kernel will be in Continuum
[Captivate Android Development] golfslicer:
Anybody got a link to just the 1.7 kernel, I tried to reflash one I extracted from Continuum 5.4, but managed to not work. The reason I was trying to reflash the kernel was the external sd was not mounting to computer and I found that reflashing earlier kernels on 5.3 would make it work.
[Captivate Android Development] existz:
Theres no standalone versions of the kernel for JVH, its only available in Continuum, icezar just released 5.4.1, which includes an updated kernel that fixes most of the issues reported..(ie. usb charger causing reboot/touchwiz 4 reboots..etc)..I recommend flashing 5.4.1 if you havent
[Captivate Android Development] jhr5474:
yeah

I am really looking forward to the 1.3 to 1.5 oc to try on the mosaic. Of course it will probably be mosaic 2 when that comes out. Your kernel is ridiculously fast on mosaic with ext 4 enabled via chainfires app. I appreciate your work, I was starting to give up hope on the captivate ever getting above a 2200 quadrant but I scored a 2650 last night with it and I have decided to keep the captivate for now I was actually about ready to move on to a different phone. Tired of the froyo and slow ass GB. NOT NO MORE THOUGH:D
[Captivate Android Development] golfslicer:
Thanks just downloaded 5.4 this morning and installed, I didn't realize that 5.4.1 was already posted. It did solve the issue of the external sd mounting.

How come I can't make a tar file that works from Continuum of the 1.7 - 10 kernel with 7 zip.
[Captivate Android Development] MarlowXim:
1.3 ghz

I actually tested 1.3 ghz it works fine for me, I did have that issue with charging reset bug, but swapping out the initramfs to fugu's worked well for me. More likely its something to do with his Efs implementation is on dbdata, but that also has it's own problems.

Also I'd like to know which lines do you edit for maximum voltage 1350 was abit to high for me on that stepping. Since I can see in the code where you added but I'm not sure if there is any divisors I have to edit.
[Captivate Android Development] existz:
Im not sure if it was setting max clock when usb was plugged in, or setting arm volt max when it was inserted or what, causing reboot for some ...but its def something with the code I think, once removing 1.3ghz and the upped voltages, it works fine... ill have to dig into it..but im just using cfs initramfs as a placeholder for now, ill either make up my own or use hardcores once he's done with his..ive always had good results with his (plus ill modify it some of course) ...

But to lower voltage for 1300, edit lines 68 and 94...then change the arm volt max on line 89 as seen in this commit https://github.com/existz/linux_gt-i9000-gb/commit/7da17655d26580aaa0277c54bb94df386ecbfc86

If your wanting to contribute any im always looking for collaboraters, just jump on my irc channel whenever (weblink in the OP) and ill add you as a collaborter on my github...the more devs working on it the better :) currently me, kodos96 and ytt3r work on this kernel..always room for more ..and I can always need to learn a thing or two ..;)
[Captivate Android Development] GGXtreme:
I'm a bit curious about CPU governers in Android kernels. I accidentally left my Captivate playing music with PowerAMP while the screen was off for 10 hours, and when I checked on it afterward my battery had gone from 85% to 34%. I assumed that might be normal for music playback, but when I checked CPU Spy, it seemed that the phone spent most of that time running at 1.2GHz. But why is this? When I used to use SetCPU (I stopped because of sleep death issues), I found that my phone could play music just fine with the screen off while capped at 200MHz or 400MHz, and still respond quickly to headset button commands. Wouldn't it save battery to run at 400MHz while the screen is off?

Another thing I noticed (although I'm less sure of this) is that my phone drains ~10% per 30 minute video I watch, pretty much regardless of screen brightness (I've tried at 14%, 50% and 75%). This time, CPU Spy indicates the phone was running at 800MHz the entire time. But for hardware-accelerated video playback, is that even necessary?

Just some thoughts. Also, if anyone happens to know a better way of setting up profiles for conditions like "screen off" than SetCPU, please let me know.
[Captivate Android Development] existz:
With gingerbread/2.6.35 we use the ondemand/interactive/smartass governor, they scale from 100 to max clock, instead of scaling from 100 to 400 to 800 to max clock..etc..so going from 100 to max clock makes things smoother and faster, it gets to full speed quicker.. so when theres load it scales to max clock, thats just how the governors are. Same goes for scaling down, it goes from max clock to 100mhz, instead of 800 to 400 to 200 to 100..etc..getting to 100mhz faster..giving better battery life.. The 2.6.35 kernel is completly different than 2.6.32 that was used on froyo, with it, the only governor we could use was conservative...but with 2.6.35 the conserverative governor does not play well, its extremely , extermely laggy.. and i highly recommend NOT using it.. You can set a screen off profile with SetCPU, limiting max clock to 400 or whatever.. Again, the 2.6.35 kernel is completley different than 2.6.32, the sleep/charge death issue does not seem to be present..or atleast not nearly as bad.. so its worth a try. But thats why, the governor does not scale through the other frequencies like with froyo, it goes 0 to max..and from max to 0.. its way bettery on speed and battery.. but try a sleep profile (you can actually use SetCPU, unlike with froyo) ...

Take all your habits/knowledge..etc.. you have of froyo and completley forget about them...things work 10x different with gingerbread, and what use to work on froyo does not on gb
[Captivate Android Development] GGXtreme:
Thanks for the info. I'll give SetCPU a try then and see if I still run into sleep death issues. Too bad there aren't profiles for things like, "fullscreen video playback", because other apps like PowerAMP can detect those states.
[Captivate Android Development] H3llstorm:
Has anyone tried the JVB wifi driver patch? It's supposed to fix battery drain issues.

http://xdaforums.com/showpost.php?p=13434007&postcount=2024
[Captivate Android Development] existz:
Yea, I've been using it for awhile, works fine...but havebt noticed any difference in battery life... That wifi module is actually compiled from google source instead of samsung source, so it should be better
[Captivate Android Development] froli13:
It's weird because I feel my battery drains verry slowly when on wifi and verry fast when on 3G/HSPA and I am not using this fix.

By the way, what modems are best on battery with GB roms? Tried JVE and JVK so far and it's terrible...
[Captivate Android Development] existz:
It varies region to region...but I've always had good luck with KC1 or JK4
[Captivate Android Development] maerlim:
Does anybody have TW3 for jvh? I'm still getting lag when i have more than 16 objects on the home screens. I'm convinced it's tw, but I need to test.

Thanks!
[Captivate Android Development] froli13:
Well, do you consider that 25% cell standby of ~10 hours total is too much considering that the phone was on standby (screen off) most of that time?

With the same apps, modem and same usage routine with froyo the battery would be at 70-75% after ~10 hours (when I get back home from work) and with GB it is at 55-60%
[Captivate Android Development] H3llstorm:
I've recently become a fan of JVO.
[Captivate Android Development] MarlowXim:
I'll try to contribute but I didn't learn kernel development in school. I just learn primarily tinkering with linux boxes. Although I have to say tiny_preempt_rcu is quite smooth @ 1.3ghz. Very sg2 like kind of smoothness. Is your model stable at 1.4 ghz, my current unit had some instability with gpu related tests. Just wondering if the sensitivity is different from froyo.

Also with efs on dbdata there are modem related crashes, for instance switching to airplane mode will cause a reboot. It seems to be independent of whatever rcu system you are using.

Don't know if it's symlink related. Maybe converting the efs partition to ext4 might be a possible work around. I don't know the conversion command unfortunately.
[Captivate Android Development] kodos96:
Well I'm using CIFSmanager too... the only things I can think of that are different between your setup and mine is that I'm mounting mine under /mnt/sdcard/cifs , and I'm mounting a linux samba server rather than a windows machine... not sure if either of those have anything to do with it.

If you open up a terminal and do 'ls /mnt/cifs/' do you see your files?
[Captivate Android Development] goob1284:
Does anyone else get freezes? Sometimes my phone locks up, then a 15 seconds later its done. It is very annoying.
[Captivate Android Development] rajendra82:
Existz:

I have a little bit of information that may be helpful to all this random lag discussion. I was playing around with the CPU Tuner app a while ago, and ran into a period of extreme lag. When I opened the app to see what was going on, I noticed that the CPU clock was locked in at 100 MHz. Thinking that the profiles set by the app were the cause, I uninstalled it. I then had SetCPU installed to check current clock speed (didn't set any profiles in it), and in the time of lag, the CPU was again locked in at 100 Mhz, instead of scaling up to max speed like the interactive governor would dictate. I think there is something in code for the new governor that makes the state get stuck at 100 MHz, and the phone becomes very unresponsive.

I'd like to test this further by using on demand governor instead of interactive for a little while. What is the best way to change governors? Is there a setting to hand edit or app to use to set it to ondemand on boot?
[Captivate Android Development] neubauej:
I have noticed it locking in on 100 at times also..
[Captivate Android Development] Vivified:
My phone continues to have locking up issues while listening to music. Happened twice in a 3 hour period today while in my pocket. Had to 2-button recovery and reboot both times. I have no idea why Dark Core 2.1 doesn't do this, and it's really annoying.
[Captivate Android Development] pizz0wn3d:
yeah I've got this issue as well. It probably has something to do with the fact that poweramp with the eq enabled can eat up a good bit of resources.

Herp derp XDA premium app.
[Captivate Android Development] jerkysh:
my phone freezes for a minute, then it reboots

talon 1.6.0 , 1000mhz in voltage control, sio
[Captivate Android Development] H3llstorm:
Did you install it using CWM? When I did, it automatically rebooted, which I'm not used to (and spooked me a little :eek:).

FYI: When you select Wipe Dalvik Cache from CWM, I see the following error:

"E:unknown volume for path [sd-ext]"

Is this a problem?
[Captivate Android Development] LNJ:
Nope. It's normal.

Samsung Galaxy S i896 on Cezar's Continuum v5 GingerBread
[Captivate Android Development] Dino.:
Im getting lock ups too, not too often, but enough to be annoying.

Mine have happened in the gallery, and I think a couple other areas but mostly when sending texts, it freezes while typing with the gingerbread keyboard with PII beta 3 with 1.6.

Had something in the "Android OS" that was draining the battery bad, (Was more drain than 12hrs standby) but I think thats more rom related and a restart has fixed the prob so far. Whatever this was caused straight 1000GHz frequency. No UV yet either.
[Captivate Android Development] rahlquist:
Not to drag another chef into this, but Designgears has told me when I have had hang issues on Cognition to remove the 100Mhz clock speed and its seemed to me to clear up the hangs and random reboots. I havent tried that on this rom yet but will now if I can figure out how to disable it(looks like the voltage app I used on cog doesnt allow clock removal on this).
[Captivate Android Development] trekie86:
The Android OS taking all of the battery is a firmware issue. Hoping JVH fixes the problem. The best suggestions so far have been to reboot, if that doesn't work, shutdown and pull the battery for about 5 minutes and boot it up again. I know you said the restart fixed but I wanted to give you another option in case it continued.
[Captivate Android Development] rajendra82:
I

Replace Voltage Control with Voltage Control EX, and you will be able to see the states tab to do what you suggest. I don't buy the logic of the fix though. I like the 100 MHz speed for when the phone is idling, and wish for a bug free governor that does not keep it stuck there. Disabling it is just band-aid, and will hurt your battery life.
[Captivate Android Development] rahlquist:
Just a matter of preference at this point. Getting 14+ hours of battery life doesnt mean a lot if I cant answer the bloody phone LOL.
[Captivate Android Development] goob1284:
I just want to get rid of the buggy governor. I hate how it freezes up.
[Captivate Android Development] existz:
You can change the governor with SetCPU or Pimp My Cpu to ondemand, but to be honest i dont think the governor is the cause for it freezing mostly during txt..im going to try a few things, i might know whats causing it...if i can prove it, ill hopefully get an update soon (I think its related to the pvr_power_latency adjustments)
[Captivate Android Development] goob1284:
Thanks! I just don't like using those appear cause they make my phone very hot and drain the scrap out of my battery
[Captivate Android Development] shane87:
For anyone looking for a way to change governors, I am almost finished with Control Freak. It will have the ability to change governors, along with the standard features of VCEX. Hopefully I will have a release sometime today. I will post in here, and in DG's Perception thread, with the link to the download.
[Captivate Android Development] existz:
For those on Continuum 5.4/5.4.1 JVH, I posted 0.1.7-TEST11-JVH over in icezars thread, should fix the minor lockup issue

Once 0.1.7 is final ill release a JVB version
[Captivate Android Development] Vivified:
You think this will fix my lockups while listening to music?
[Captivate Android Development] abee_13:
What does the touchscreen sensitivity tweak do ?? been kind of curious
[Captivate Android Development] kodos96:
I'm not sure what icezar is talking about with a permissions issue - he was probably just guessing... the actual problem is that the version of busybox installed with perception, as well as the 1.18 version downloadable via stericsons installer, doesn't include the 'run-parts' command for some reason.... one quick fix is to use the stericson installer to dowgrade to 1.17.... not because 1.17 is better than 1.18 (it isn't) but just because for some reason the 1.18 build from the stericson installer (which is probably what's also included in perception) was built with a very minimal set of builtin commands, while the 1.17 build is more standard.

Downgrading, though it will solve this problem, might introduce other problems, since perception is expecting 1.18. The real solution is to get a version of 1.18 built with all the standard builtins included, and submit it to DG to include in his next release. I'm working on that, but it's a PITA.
[Captivate Android Development] Spidious:
OOps wrong forum sub section..
[Captivate Android Development] H3llstorm:
I listened to all of Pantera's Cowboys From Hell with Mixzing and didn't have one skip/stutter/pop/lock-up/etc.
[Captivate Android Development] Vivified:
Had a lockup while listening to music with PlayerPro. Phone was in my pocket. I'm trying now with PowerAMP to see if it happens with another player.
[Captivate Android Development] pizz0wn3d:
I've had this issue as well. Just had to pull the battery when the phone locked up while I was using poweramp.

Herp derp XDA premium app.
[Captivate Android Development] GGXtreme:
I accidentally left my phone playing music with PowerAMP with the screen off for 10 hours and it never froze, music was still playing fine when I checked on it. I've also never had the phone freeze/lag while listening to music. But this was on 0.1.6, I'll test 0.1.7 test 11 some more.
[Captivate Android Development] shane87:
Control Freak is live!

Check it out at http://xdaforums.com/showthread.php?p=13672621

It will allow you to do (almost) everything that VCEX did, plus it supports Governor switching.
[Captivate Android Development] Vivified:
It appears as if aknegow playerpro was causing the issue. Have not had it since switching players to poweramp.
[Captivate Android Development] mgfjd:
I have been using Talon with Continuum.. I noticed running touchwiz sorter would crash my rom (always) I thought it was a normal ROM problem... switched to the JVH re-oriented kernel.. run touchwiz sorter no crashing... dont know if you can reproduce the problem...

Thanks..
[Captivate Android Development] existz:
Works fine for me, been using tw4 since 5.4 dropped with no issues or lag
[Captivate Android Development] dbord_n:
Download links not working from captivate. Keeps saying connection failed.
[Captivate Android Development] Juan Bond:
Hi and thanks for your kernel I find it works well but I'm interested to give overclock. You're going to get another kernel soon?
[Captivate Android Development] cnigro1279:
It is oc'able to 1.2.....open voltage control app and enable it. Higher clocks maybe in the future.

Sent from my couch on my phone.
[Captivate Android Development] Vivified:
This is an issue with your browser, not the download links.
[Captivate Android Development] existz:
Try using astro file manager to allow downloading of all file types, its under menu->more->preference ...or try a different browser, or dload it from a computer
[Captivate Android Development] rockosifraldi:
existz,

Not to hijack..:) but with the latest release from xCal do you see any changes flowing into Talon for Continuum...
[Captivate Android Development] Spidious:
I don't see voltage control ? Does it have to be installed separately from this kernel ?
[Captivate Android Development] trekie86:
Yes Voltage Control is a separate app from the market.
[Captivate Android Development] Spidious:
Just installed Voltage Control and my score jumped to 2016...Running stability test right now..

Any base setting I should use ?
[Captivate Android Development] trekie86:
You can leave it how it is or tweak with the voltages. I undervolt 1000Mhz & 12000Mhz by 50 mV. Been super stable.
[Captivate Android Development] rockosifraldi:
Mine is -50 all the way .. on 100 it is -100.. runs great.
[Captivate Android Development] existz:
The only change was voodoo lagfix,... with my initramfs, both are ext4 just with minor changes to mount options..I see no reason to change, both are very similar. I actually used voodoo at first before releasing, I just like chainfires better ...for now anyways.. im working on something else right now that should help with memory management.. so might be another day or two before I release ..still testing/tweaking a few things
[Captivate Android Development] rockosifraldi:
You don't let the excitement die, do you.. :)
[Captivate Android Development] rockosifraldi:
A small donation....to keep you going..for those long nights:)

34K54219HS135062D
[Captivate Android Development] cbalt:
I went to ext4 with chainfires manager a couple kernel releases back and since then have done a complete wipe and then updated to the newest kernel and c5.4.1 and when I open ext4 manager I see convert to ext4 and i tap it, it reboots and does its thing as far as I can tell then reboots and the option to convert to ext4 is still there.
[Captivate Android Development] Will of fire:
Im currently using continuum v5.4.1 and i keep losing my apps and the phone keeps freezing i was told i need to instal the latest Talon Kernal can anyone comfirm if this is true?
[Captivate Android Development] krufttangoud:
I would agree

Other than battery life...I have had good results from this kernel. Battery life isn't terrible though.

Still tweaking OC/UC to achieve best results.

using Control Freak: Scheduler set to NOOP, governor on interactive OC to 1.2.
[Captivate Android Development] Will of fire:
So you dont know about the apps being removed i wonder if its becuase i used to have froyo. would this be a problem if the apps are being deleted because the app data is from froyo
[Captivate Android Development] krufttangoud:
apps

When I restored the apps, just to be safe I did app only no data.

some of those apps are not compatible with GB. They will install, but won't work right.

However, this is the best kernel, IMHO, once it is out of DEV it should be rock solid. Enable the tweaks and convert to EXT 4. \

I haven't had an App disappear yet.
[Captivate Android Development] Will of fire:
i will test this out a post back after, i hope that fixes it becuase i was installing with data. Thanks again i hope it works.
[Captivate Android Development] rlorange:
@exitz

Are you still planning to implement the smartass governor?

**Simply Honey 3.1, Talon i9000 test kernel OC/1.2Ghz, JVK modem**
[Captivate Android Development] neubauej:
I have zero lag on continuum 5.4.1 with Talon 1.7 t11 until ram dips below 70mb free or so. Also, it keeps closing the stock GB launcher. It doesnt seem to matter what tweaks are enabled. Default, min-free enabled or not, swappiness enabled or not. Etc.

Just reporting.

Carry on.
[Captivate Android Development] rivtre:
Same here,that's why i've been waiting for BIGMEM version.;)

In JVH even if you kill all running apps the system still says there's 80-90 MB left and in JVB 140M or more can be freed.

Edit:I am with Mosaic II and Talon 0.1.6 BIGMEM ,just an FYI.OCed to 1.2G and -75mv on each state,pretty smooth and stable with ext4.
[Captivate Android Development] jlsesler:
Issue with 1000mhz setting

There seems to be an issue with my speed at the 1000mhz setting. Look at the data below:

Linpack scores (each setting run 3 times with highest score recorded below):

1200mhz - 17.025

1000mhz - 11.525

800mhz - 11.66

400mhz - 5.97

Notice that the scores for 800 and 1000 are similar (yes, i made sure to "apply for now" when setting the speed each time). I get about a 14.5 score with Xcal's kernel (set to 1000mhz) on the same ROM. I am currently running Cont 5.4.1 (JVH) with 0.1.7 test 11 kernel, but I have seen the same results with earlier versions of the Talon kernel on JVB.

Is there something that I am missing that could be governing my cpu to the 800mhz level even though it is set at 1000mhz? Anyone else get the same results?
[Captivate Android Development] neubauej:
Odd, but I get the same results...