yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] redjersey:
can i flash this using cwm on top of my talondev 0.2.1?
[Captivate Android Development] TonyStark R.I.P.:
existz I am looking for an image of that screen. is the .h a convertible image? I would like to use it in my sig.
[Captivate Android Development] Loftus:
Try rebooting with packet data disabled. This allows BT to activate for me. You can reactivate packet data after booting.
[Captivate Android Development] zacharias.maladroit:
there were some serious lags in the beginning so I switched from deadline to cfq

but it seems I kinda fixed it - if they (lags) don't occur - go ahead and use sio, deadline, noop, etc.

conservative: because it offers the best trade-off between power preservation and performance

besides that: it (conservative) doesn't lag so much & has less regressions

I've a battery of apps & games that I run on the phone & kernel before I view it as consumption-ready

smartass is fine but tends to consume more energy (while idle @600 / 400 MHz afaik),

interactive: tends to get somewhat sluggish overtime so the experience isn't consistent

ok, thanks,

the update jvb -> jvh doesn't seem to cause any changes in wifi-code

so maybe it's framework and/or ROM related

perhaps some stabilizing compiler-flags might help, dunno ...

this shouldn't normally happen,

anything special you did while calling ?

could you try to disable the proximity sensor if that helps (I know it's convenient) ?

to find out whether it's caused by that

I had that in the past with CM7/MIUI kernels

should - if you don't get lags or anything

there might be still some micro-lags (which I reduced from several seconds-long lags to half or less seconds lags) while it swaps out stuff to the swap (zram)

backlight softkeys - it's probably because I've lowered the timeout from 1600 to 700 ms

see description above

thanks !
[Captivate Android Development] manny05:
i can support that the wifi problem does happen to me as well.

i turned off wifi, turned it back on, turned it off, and turned it back on. thats when my cappy just rebooted.

i am not sure if this happens only when i turn it on and off twice consecutively or just once a in while. ill keep an eye on it though.

aside from that, this kernel is running GREAT. quick and stable.
[Captivate Android Development] kodos96:
I've been away from the forums for a few days working on getting the new initram working, so let me reply en masse to some of what's been discussed in my absence:

You do not want to use Darky's ramhack or Juwe11's ram tweak on Talon

These are both scripts which tweak android's LMK settings using a deprecated method which conflicts with Talon's built in LMK setting scripts.

I'm not saying you have to use my LMK settings - in fact I strongly encourage you all to experiment with tweaking your LMK settings, and give me feedback on what works best for you... I'm just saying that you should be doing your tweaking via Talon's LMK configuration file, in order to ensure that the settings you choose get applied correctly. If you use one of these external scripts, you're actually only setting HALF of the relevant settings, and you end up with a situation where one part of the system is using one set of settings and another part is using another.

The location of the file you want to be looking at is either /system/etc/lmk.conf or /system/etc/ram.conf , depending on what version of Talon you're on. If you want, you can try just plugging the values from Juwe11's script or whatever into that conf file, although its highly unlikely that settings optimized for a different kernel will end up being optimal on Talon, since Talon uses ZRAM, which has a major impact on how the system uses ram. But at least that way, all parts of your system will be in agreement about what LMK settings they're supposed to be using, instead of fighting against each other.

If you're interested in some more in-depth technical detail about how the various settings work, here's a link to a reply I wrote last week explaining some of it. And please, feel free to ask questions if there's anything you don't understand about how this works, or want to run an idea by me for some new settings, or drop by #suckerpunch on irc.freenode.net...... but please don't just go dropping random scripts in your init.d
[Captivate Android Development] shane87:
Hey kodos, I have a (slightly) related question. Is it "safe" to write a script to modify governor-specific tweaks, i.e. up-thresh in ondemand governor? I am working on adding some of these tweaks to Control Freak, but I was wondering if modifying these values via scripts, either through a script like I use for now that just adjusts an individual setting, or through adding it to s volt scheduler.

Any feedback would be appreciated!

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Android Development] mkr14:
Voltage Control Boot Settings Do Not Stick- Zach's Talon Mod

Is anyone else having issues saving boot settings in Voltage Control using Zach's Talon mod? I have tried everything I can think of as far as deleting the boot files, reinstalling, etc. Am I missing something? I am guessing it is the scripts but I do not know.

If no one else is having this issue, at least I know it is just me.
[Captivate Android Development] timn2bama:
I just rebooted 2 or 3rd times and finally BT kicked in.
[Captivate Android Development] shane87:
I am unsure of the issue in Zach's kernel, however, I do know that some people have had trouble getting boot settings to stick with certain roms due to a problem with busybox. Busybox 1.18, that comes installed on several roms, does not have run-parts installed. That prevents all /etc/init.d scripts from being run at boot. Stericson has a busybox installer in the market, and I can confirm that using stericon's busybox installer to install busybox v1.17 will fix the run-parts issue.

If the script is getting run, but the settings are still not sticking, it may be a VC specific problem, which you would have to address to xan. Control Freak does work, however, and provides the same functionality, plus cf has time in state info and offers governor switching. CF works with both busybox 1.17 and 1.19, so if all else fails you may try it out.

Hope this helps!

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Android Development] mkr14:
Thank you for this reply! This is probably exactly it. I ignorantly updated busybox to 1.18. I will give this a shot and update with results.

EDIT: OK this was the problem! Apparently my phone was in a state far from optimized. Thanks again Shane!
[Captivate Android Development] zerkai:
For some reason, I can't get a data connection with zach's kernel. It says its ON (as in, "Use packet data" is checked, and long press on power button says data is activated), but nothing works -- no internet, MMS fails then when I switch back to 0.2.1, presto, H/3G on.
[Captivate Android Development] Rrryan2:
Workaround 'hack' to get BT working that has worked for me with 100% reliability: disable WiFi, reboot. Turn on BT *BEFORE* re-enabling WiFi. That's it.

It's a little bit of a kludge and still well short of ideal, but it'll get your BT running at least.
[Captivate Android Development] kodos96:
That would be a question for eXistZ or ytt3r - I actually haven't been involved in any development related to the cpu governors, and I'm not up to speed on how that stuff works.
[Captivate Android Development] zacharias.maladroit:
for me packet data works like with the previous kernel (for SGS)

maybe your APN data got changed or something

I don't have an captivate so can't tell whether there might be any difference or issues with it compared to the SGS

generally it should work

does wifi work ?

are you trying to connect via VPN or something ?

if yes you need to disable the rp_filter part in the S98system_tweak script
[Captivate Android Development] irishvandal:
->Blue Banshee< - >IV-Remix<-

After 36hrs of running this set-up on a dirty phone, I decided it was time to run a clean install with formatting and all.

The entire set-up of my very current and very Beastly Rig of a i897 is listed below. This set-up is glossy blue themed and not for the absolute amateurs.

In other words, if you don't understand what set-up I am running, SIT DOWN. This is not for the faint of heart. I am a noob and understand it, some techy tricks are involved working this magic. So that is why for the direct angle there.

I have fixed the BT bug that was eluding me, it was somewhere in the garbage on the phone. Cleared and solid so far. Extensive testing the off/on toggle trouble that have been plaguing the many. This also goes for WIFI, tested under various conditions and was solid each and every time. Honestly, if you know of any one way to BRING THE PAIN to this bug ppl are having I will try it.

I am going to try and keep a as-close-as-possible 24hr update schedule on this set-up. If anyone has any questions or feedback feel free to PM. I just want to share this set-up for other to try and maybe bring some devz together on a solid beast of a package. It is that sick.
[Captivate Android Development] zerkai:
WiFi works. APN shouldn't have gotten changed because as soon as I flash back to 0.2.1, data works again. And I'm not using the 2 scripts you provided. No changes when I do use them anyways.

Like seriously, i can literally flash your kernel and have data fail then flash to 0.2.1 and have it working again.

Interesting...
[Captivate Android Development] shane87:
Alright man, thanks for the reply anyway! I am not seeing any negative impacts while running my script, but then again, I don't have time to do the in-depth testing I should between work and my family. Again, thanks for getting back to me!

ROM: Continuum v5.5

Kernel: TalonDEV 0.2.1, Voodoo Sound, Voodoo Color, CFRoot ext4

Modem: I9000 tdvjp9

HW Build Number: 1101
[Captivate Android Development] zacharias.maladroit:
take a look what my screenstate_scaling script does

it seems to do the things that you mentioned

so there should be no problem to switch between governors and adjust settings ...
[Captivate Android Development] steph2:
existz you going to do any work on the new JVP kernel ??

I would love to use some of your oc uv magic on JVP ROMs.

Thanks for the reply in advance
[Captivate Android Development] existz:
Already have a JVP kernel testing :)
[Captivate Android Development] RichMD:
The bootanimation in your signature is my new favorite - Awesome! :D - http://api.viglink.com/api/click?fo...a-developers&txt=Andro zapping Apple to ashes
[Captivate Android Development] watsa:
So far its looking good, no wifi or BT issues.
[Captivate Android Development] zacharias.maladroit:
yeah :)

where can I download it ? :p

hidden in the text ^^
[Captivate Android Development] jesus_c:
deleted

sorry
[Captivate Android Development] existz:
1) Both work fine for me...

2) Please quit posting Talon TEST builds on other forums (if its not you, then its someone with your same screen name..and i apologize) ..

Incase anyone doesnt know by now... I DO NOT want test builds posted to the public. Its pretty sad its gotten to the point to where im going to have to password protect them.. Ive asked numerous times and have had to change download locations 2x-3x.. I know theres ways to find the links, but if I wanted it posted, I would have done it myself, so if its not posted, thats for a reason...
[Captivate Android Development] jesus_c:
sorry

edited my msg
[Captivate Android Development] zelendel:
I should not have to say how much this is not tolerated. If the Dev does not want it posted then dont post it. If I find someone is releasing something the Dev does not think is ready for release (Means He didnt post it himself) then a Ban will be soon coming. I hope I am understood. These Work hard on this and deserve some respect.
[Captivate Android Development] TonyStark R.I.P.:
Unfortunately we live in a society of children, everybody wants to act special and show off. It's always the immature that ruin it for all. Welcome to the "it's all about me" generation!
[Captivate Android Development] existz:
Im not trying to be an ass, far from it... sometimes test builds are just that, tests...for example, take 0.2.2-T3, 1.3ghz was introduced again, but some of the cpu code was missing by accident, and it caused the screen to flicker/show black lines.. it seemed to only happen with cpu and/or gpu intensive task.. So I don't know what damage it could have done, for all I know it could have burnt the cpu out or screen (pretty extreme, but u never know) .. luckily I was able to catch it and removed it with a fixed version..But sometimes there's times I don't catch it.. And for those that don't know about it, it could have done some damage... So that's why I ask don't post test builds.. Not because I don't want you guys using it, its just because we do alot of things that are experimental and could damage your phone for good (again, pretty extreme, but u never know with these things) .. Also, we are working on a new initramfs, the first test build would corrupt the filesystem under certain conditions..so for those that don't know about it, it could mean losing everything .. if its stable enough for use, ill post it or give it to rom devs to use in their roms (ie. Continuum 5.6 uses 0.2.2-T2, its fully stable)..

So please don't take me as an ass, not trying to be...just trying to protect those that do not know about the issues from losing all their data or something worst

This is completely different than other devs building from our git with stuff not in latest public builds... I don't push anything to git unless its fully tested and stable.. the latest git might be different than latest public build, but TEST builds are things not in public builds or on github yet..If its stable ill push it to github or put out public builds with it

/end of topic
[Captivate Android Development] stojkov.matt@gmail.com:
Can i test the jvp kernel?
[Captivate Android Development] existz:
I might release 0.2.2 today/tomorrow .. It wont include the new initramfs yet, still working on it, but should include a few new features/fixes.. Right now custom bootanimation does not work, to be able to get it to work on JVP i had to disable custom bootanimation, and im trying to only release just one kernel for all builds (JVH/JVO+/JVP).. so more than likely 0.2.2 will not support custom bootanimation .. But who knows, by then i might decide to release 2 different builds, (one for jvh/jvo+ and one for jvp)..and JVP would only have broken bootanimation..but i dont know yet what ill do..
[Captivate Android Development] Sqb:
Patiently waiting for your next release. Thank you for the hard work. Kernel on 5.6 is awesome!

Sent from a rock on fire in the middle of the sea
[Captivate Android Development] TonyStark R.I.P.:
This statement might be suited well in the OP, bold-faced;)
[Captivate Android Development] mrhaley30705:
I've noticed that by turning Samsung Apps to off, the wifi problem isn't as bad. Not saying it's a cure, just makes it better.
[Captivate Android Development] squishy5:
how do u switch kernels i am currently on the rom mosiac and would like to change the talon kernel ???
[Captivate Android Development] nrgaway:
Is there anything special I need to do to load Talon kernel from stock mosaic IV? I have seen some things that need to be removed in /etc/init.d in other roms but not sure with this one since its just hot off the press.

Also does the bln framework.jar need to be applied to mosaic IV or is it already compatible?

Thanks in advance!
[Captivate Android Development] Loftus:
Yeah but those that NEED to read it are usually the ones that don't look at the OP :-(
[Captivate Android Development] baghera1979:
Flash kernel's thru Odin3 in the PDA slot
[Captivate Android Development] alexige:
with auto-reboot unchecked
[Captivate Android Development] baghera1979:
Forgot that...sorry and thanks
[Captivate Android Development] TonyStark R.I.P.:
The file attached is a cwm flashable. download the file and put it in your sd card. Then flash it.

http://xdaforums.com/attachment.php?attachmentid=618740&d=1307482596
[Captivate Android Development] jdsatyr:
Is the auto-reboot actually needed after the first time? I have flashed several versions of talon without unchecking auto-reboot without any problems
[Captivate Android Development] alexige:
Well yes you have to reboot the phone but it has to be done through a battery pull and power on. Devs on here have recommended this and I know from personal experience that leaving auto reboot on will cause the kernel flash to fail and get a soft brick.
[Captivate Android Development] mrhaley30705:
Unchecking reboot is only needed when installing certain roms, not on every kernel flash. Unless you are going from a cwm 2 to cwm3 , out vice versa, kernel. Thats why you uncheck it, to gain the version of cwm you need to actually flash the rom from recovery.
[Captivate Android Development] jesus_c:
unchecking auto-reboot is not needed but recommended!

it is needed to go to CWM to wipe cache and dalvik after flashing new kernel
[Captivate Android Development] Taderich:
I don't see you as being as ass but rather being considerate. You've mentioned it multiple times and given us fair warning. I'd just like to say thank you.
[Captivate Android Development] irishvandal:
I glanced over this the other night and honestly did not give it the respect it deserves. Thank you existz. TY for all your hard work and even loving compassion during a time of scolding, lol. You did well and stated your point fairly clear. The open nature of your feelings only showed your overall knowledge of what we are dealing with and the seriousness in which we deal with it. I know I will take a more cautious approach on new "MixBuilds". NA!!!! Who am I kidding, lol. I cant stay in a seat like that, gotta find something to get into, lol. Bring it.

Existz - personal opinion, is the TalonDev version I am running safe? If not could you point me to a solid Talon version with this much juice. Honestly, if this kernel is doing something, it would have to be on the side and background. Minus any lags/sluggish issues(mostly during sleep/wake), I have NOT seen ANY issues. I am going to "finally" post my >>>Blue Banshee<<< Forum Update 1 next. Would of last night/this morning but XDA servers didnt respond.

TNX,

IV

PS existz - Is my Sig link to Talon appropriate? Let me know, I am just wanting to share the wealth. BEAST !!!!!!
[Captivate Android Development] irishvandal:
BLUE BANSHEE Update01

Update on POST 1997 of my I897 Custom build in my Sig

I am currently on the 24hr of this run and everything has worked flawlessly minus a device test at 9%. Incurred a deadlock with a soft-boot. everything came back up fine. The app I am using for scores is DeviceMark from the market. I was able to achieve a Score of 1539 and Rank 3 for I897. Not sure if this app is entirely accurate. If someone has an app that seems more on the money please let me know.

I have also been hard on the phone today. Here are some of the conditions i provided for my Beast to plow thru:

MS Exchange( 3 accounts) sync every 4 hours

Facebook signed in for all 11hrs - sync once every hour

MSNMercury signed into my Hotmail IM account for 4hrs.

Weather & Toggle Widgets sync Location weather every hour

Bluetooth transfer of jpg, png, mp3 - i will test out vid transfer tomm

Over 150 outbound SMS with approx 100 inbound

30 MMS messages outbound

3-5 10+minute phone calls

2 30+minute phone calls

30-60 minutes of streaming YouTube video

4 DeviceMark tests - Best of Four was 1539

Open/Read 3 Email account approx 3 sessions

1 15min Navigation with On-point GPS locations

Off/On toggles of BT/WIFI/GPS under various Off/On toggle combinations

30+ minutes of Gallery

30+ minutes of PowerAMP

15+ minutes of Market

20+ App Updates

plus misc function and mad Display use.

The first run on training this battery is lasting 13hrs with 5% remaining during this writing. This is under a CPU clock by SetCPU of 1300MHz the whole day. I have noticed the Video Call button still remains despite my attempts on installing this package in the manner I first had installed it. Also to note is the stock Music Player provided by "Serendipity7 Build2 Full ROM" does not provide the function of being able to share directly in any manner, messaging, BT. Nothing. I did find one of my already preferred apps picking up for the slack of sharing my media via BT. Root Explorer. Its not the method I prefer but it does get the job done.

Overall, I am very happy with the current custom build I have mix together. It has been stable and is VERY quick. I do notice some sluggish nature from Blue Banshee when she wakes up, but I accept that minor inconvenience right now.

I will be waiting for this battery to completely die tonight and throw it on for a FULL charge in the morning and put this baby to the test once again. That will be the first full charge under cleared stats and day 2 of this build.

I look forward to any questions or input. Feel free to PM.

TNX -- As stated on YouTube, "Animation credit goes to

saintmichaelsarmoury

"

Yep, lol. Good to see a Big dawg nodding. TNX alot for Talon brotha. It rokz sockz. Keep up the GREAT work.

!!!!! USE EXTREME CAUTION USING THIS KERNEL, UNDER DEVELOPMENT !!!!!
[Captivate Android Development] existz:
Yea 99.9% of builds are safe.. Usually when this discussion pops up, im usually referring to my private TEST builds (not the same as whats on Github), I know theres ways to find the link, but if you find it on your own and use it, then its all on you...I just dont want them posted in forums, so people think that they are safe and stable.. But most of the time I usually catch serious bugs right off the bat (given theres been times I havent).. like lastnite, I put a test build up with 1.6ghz..but later on we found out that when charging with USB, it was locked at 1.4ghz, no matter what you had set for max clock, even 1ghz.. So while charging, it was constantly running 1.4ghz, and got verry hot really quick... I dont have to explain the danger in that..

So after finding the issue, it was fixed and that build was removed and replaced with a fixed version.. But for example, if that test was posted on a public forum, most of them would have not known about it and if someone just throwed it on usb charger and left it over night, it could have done some serious damage.. But it seems the USB clock bug has been there since we introduced 1.2ghz (setting it to 400mhz) then with 1.3ghz (it idels at 800mhz),, but ive since fixed it and now should be charging at 200mhz when using usb (stock setting).. But seems 1.6ghz is holding up pretty good, theres been multiple testers running 1.5ghz pretty stable (using oc/uv code from TKGlitch) for you benchmark lovers, was geting 22.6 in linpack and 3400-3500 in quadrant.. I planned on releasing yeserday/today, but since 1.6ghz is running so good, im going to test it just a little bit more and next build will/should include it (1.3ghz, 1.4ghz, 1.44ghz, 1.5ghz and 1.6ghz)