yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] shoman94:
Does this overwrite the FuguTweaks?
[Captivate Android Development] di11igaf:
no if you have them it won't. It contains no bin files. I was using the tweak with a test kernel and didn't notice a difference with the tweak though. Now If we could get the libdvm.so from 2.3 to work with 2.2 that would probably make a difference but the phone won't boot with it . I'm gonna try to compile one from source and see if I can get it to work.
[Captivate Android Development] diablo009:
I shouldn't have bought up this tweaks things at all :o
[Captivate Android Development] shoman94:
Cool... I was just checking to be sure.... I suppose I could have just looked without asking.... so I'm sorry.

You didn't bring it up. I saw it in the i9000 forums. I'm sure others did as well.... plus with Phoenix7 and Serendipity including it. Also I think Darky's rom thread people have been adding it as well. I waited because people were having issues installing it with SP kernels....

Anyways... nothing wrong with enhancements. We can't know if we don't try.
[Captivate Android Development] momulah:
Is there a way to revert back if I installed tweak and I'm having issues? Without full wipe?
[Captivate Android Development] di11igaf:
You can

A- flash a new kernel that supports them (mine will when I get around to compiling a new one)

B- push the original files back, or put them in the zip to replace the 2.3 ones and flash it
[Captivate Android Development] shoman94:
diablo009 posted a revert flash back here: http://xdaforums.com/showpost.php?p=12054227&postcount=4397
[Captivate Android Development] diablo009:
Go back a page or two or three. I posted one last night to replace the tweak files to those from dilli's 7.0.
[Captivate Android Development] garringm:
I installed 7.0.2 this morning, I had a couple small issues in the pulldown when I would select wifi It would show real quick that I was low on memory which memory is it referring too still had over 100mb of ram available, 1.71 gb of internal memory 11gb int sd and 7gb ext sd

also when in the pull down I had a % p% or something like that, I assume this is a battery percentage and since I have that removed from my top bar maybe it is jacking with that but Im not sure,

overall I really liked 6.0 so I had to give it a shot but I really didn't like most of the theming even though I incorporated the theme to my choice there was still a few things that werent appealing to my eyes so I have reverted back to 6.0 Maybe I'll work on 7.1 theming it. Still a good job really like your work.
[Captivate Android Development] di11igaf:
What do you mean have that removed from my top bar? if you got rid of the circle hart and replaced it with something else it must not be compatible as it sounds like your getting text string errors. this ONLY happens with incompatible framework files

Those errors are not Rom related, it has to do with whatever you did with the theme.
[Captivate Android Development] koreancanuck:
I didnt have that issue with the wifi and I noticed the weird symbol when I was messing around with i9000 themes but its fine with di11is stock look.
[Captivate Android Development] garringm:
No I just got rid of them, replaced with nothing else, well I didn't do it someone else did on another thread from somewhere else. It really isnt a big deal to me I assumed that battery part was my doings but the low memory warnings I assume are not from me
[Captivate Android Development] slayp00n:
Is their no more green version? :(

Also still on 6.0 and my swype expired?????????
[Captivate Android Development] ProBoner:
Once again, here is the themed swype I use. Only this time I posted the "so" file since I had to use it after having switched to the beta version for half a day.

libswypecore.so file goes in system/lib folder

swype.apk goes in the system/app folder (with permissions set to match the other files in that folder)

There are a couple of issues with this latest version that I won't be able to fix until more themed versions are released. 1 - the swype line is green and 2- french and dutch are green keyboards (actually the dutch language file was removed altogether)

Everything else looks good to me :D

edit: If you're currently on the beta, this won't work until you remove that version and re-start the phone.

ALSO, THIS IS NOT A CWM FLASHABLE FILE, UNCOMPRESS THE FILES THEN PUSH THEM (using root explorer, etc) INTO THEIR APPROPRIATE FOLDERS
[Captivate Android Development] WillyWonka23:
Hey pro, your swype file didn't get attached to your post. Just letting you know if you hadn't noticed.
[Captivate Android Development] di11igaf:
well, there both related, the low memory is just a text string error, along with the % signs you are seeing. you dont have a low memory error, thats supposed to say something else, but the ids are messed up now, which is why its saying low memory. so whatever someone else from another thread did, that you eventually did, changed something in the framework. thats the only way to get either one of those messed up strings. i know its not a big deal to you, but when things like that are posted as bugs, other users see that, and this thread is FULL of bugs that are not bugs, but user error problems. not trying to be harsh, just trying to explain that whatever you did to remove the battery is the culprit of both of those problems, cause thats the only possible explanation. i know theres no text string errors in stock form of my rom, so unless something is changed in the framework its impossible to get those errors in this rom.

im guessing whatever you did to remove the battery involved framework-res.apk, andriod.policy.jar or services.jar, cause thats some of the files that would cause those text errors.
[Captivate Android Development] ProBoner:
Yeah it was too large of a file to post so I had to remove Dutch language files to get it under 8meg (otherwise I would need to register on megauploads or something to post it).

If it doesn't work for any reason, somebody let me know and I'll post the full 9meg file one way or another.
[Captivate Android Development] rjblack11:
replaced lib and apk works like a charm (just used it) thank you sir
[Captivate Android Development] di11igaf:
If that a confirmed working version, ill theme it and include in next update. what a pain in the add swype.
[Captivate Android Development] rjblack11:
you're saying if it doesn't expire in 40 days right?
[Captivate Android Development] ProBoner:
That's probably beta and they expire every 4 months I believe... but that's plenty of time to flash to a new ROM with another swype :D

Di11, you can use that version and overwrite my blue/white with the all-white theme PNG files and you'll have your old setup again already fixed for the dark text as long as you don't overwrite those PNGs ;)
[Captivate Android Development] WillyWonka23:
Should I match the permissions on the libswypecore.so with the other files in its folder as well?

Edit: Nevermind, I got it working. I like the green.
[Captivate Android Development] v1nsai:
1571 in Quadrant, 862 in smartbench and 13.797 megaflops.

Liking it so far, market is almost impossible to use because of black on black, unthemed version of the rom would be nice :-D
[Captivate Android Development] rjblack11:
more black=less batt
[Captivate Android Development] bclark:
This is why there is a theme thread. Check it out I'm sure you'll find something you like
[Captivate Android Development] koreancanuck:
http://xdaforums.com/showthread.php?t=957331

Choose what market you like, download the zip file, thank the dev and flash.

Yes but I don't see any point of having most of it black if you can't read texts in some of the parts..
[Captivate Android Development] diablo009:
+1,000,000

Having display down to minimum has a lot of battery savings compared to higher brightness and auto brightness.

Having black or black background hardly makes noticeable battery life difference, atleast as far as I have observed. On 7.0, I was on dilli's black theme, and now on blue theme, and my battery life is still the same. Plus 90% of time I am not on home screen, so I have a colorful wallpaper set too since I changed theme to blue (colorful as in not white shades, but yes, lots of colors).
[Captivate Android Development] rjblack11:
ha I changed my xda app to dark b/c I thought I might save me batt. maybe a little :)
[Captivate Android Development] diablo009:
Yes. I am with u on this, darker colors reduce glare compared to light colors.
[Captivate Android Development] d1g1talphyre:
by nature the screens uses no power to display black. so the darker the better.
[Captivate Android Development] diablo009:
Couple of interesting facts about AMOLED in this presentation (attached presentation to this post):

Page 15

•TFT display has constant current as backlight which must be on no matter what

picture is displayed.

• Conclusion – use Black background on OLED to minimise power

(I stand corrected on my earlier statements.)

Page 17

AMOLED power consumption depends on image content & application.

• Black background can save more power.

• Moving image is a good application. (Does this apply to live wallpaper too?)

Slide 18

AMOLED power consumption can be

decreased by:

• 1. Black background. ( 50%~80% ) ↓

• 2. Lower full white brightness. ( 20% ) ↓

• 3. Auto current limit driving method. (20% ) ↓ (Seems to indicate "Power Savings Mode" under display settings reduces power usage.)

• 4. OLED material & device efficiency increase. (30% ) ↓

Slide 30

has some interesting guidelines on designing themes/icons.
[Captivate Android Development] charlier1977:
the above links do not seem to be working. the first downloads a blank file and the udate to v7.1 takes you to a 404 error on the eschnet site
[Captivate Android Development] diablo009:
Try this link: link

Taken from this post: http://xdaforums.com/showpost.php?p=11886858&postcount=4038
[Captivate Android Development] di11igaf:
Ill have to fix them when I get home, might be something up with the server. I didn't upload to multi as a backup for 7.0.1 cause I didn't have time yesterday.
[Captivate Android Development] WillyWonka23:
I'm not sure if the green swype trace is suppose to be there or not with the blue but keep it. I love it. It is nice and bright for my colorblindness. Using Pro's version.
[Captivate Android Development] bamjoe:
Isn't that 7.0 and not 7.1?
[Captivate Android Development] diablo009:
It is 7.0, but hardly noticeable changes between 7.0 and 7.1. 7.1 no wipe update can be got from one of the posts here. So instead of waiting, one could go ahead with 7.0.
[Captivate Android Development] tehsam:
theme is looking great- has themed swype been incorporated yet?

also- does anyone know what the deal is with js5 wifi? is it a battery drain like JPX/do we need to apply any wifi fixes?

i have been a long time user of 6.0 but I am thinking I will move to 7.0 and flash fugu tweaks this week.
[Captivate Android Development] kimchi0400:
Just flashed the mms fix, as well as replacing the animations with another theme's.

This thing is a sexy beast. :)
[Captivate Android Development] francous:
Getting a file server error for the 7.1 no flash update.. Is there an alternate link?
[Captivate Android Development] WillyWonka23:
What is the difference between the 7.1 full rom and the 7.1 update from 7.x? I am already on JK4. I could flash the speedmod kernel at the bottom of the OP to replace voodoo. Is there more to the full 7.1?
[Captivate Android Development] shoman94:
In case people wanna know.... Battery life is great so far.

72% remaining.... on for 12hrs.....Display on for 1Hr 7min and on auto brightness...5min voice call... one hour of internet usage...

Choice dialer used a bit more then I'd like.... so I just got rid of it. Auto rotate-on and gps-on. BT off and Wifi off.
[Captivate Android Development] francous:
nice to know.. wish i could download it .. :(

Update: found it here! http://eschnet.dlinkddns.com/Dilligaf/

Scroll down to 7.1 no wipe

:D
[Captivate Android Development] WillyWonka23:
Try right clicking the link and select "open link in new window or tab"
[Captivate Android Development] WillyWonka23:
There is a newer SGS Tools app available. Would it be a good idea to include that one with your rom instead of the older one?
[Captivate Android Development] di11igaf:
i dont include that with my rom,

i used to include a bunch of stuff like that, but then decided to try and cut out as much as possible, especially all the completely unnecessary apks. so while i did that, figured id only include the more necessary stuff, not stuff that half the people are gonna uninstall.
[Captivate Android Development] shoman94:
Makes sense because we can easily grab it from the market.
[Captivate Android Development] di11igaf:
Exactly. Id rather let users decide on stuff like that
[Captivate Android Development] shoman94:
What do I see in your sig? Are you gonna be taking a time out and concentrating on the I-4g? :(

EDIT: I have something I think your ROM may benifit from. I notice that when my WIFI is on that it scans every 5 seconds for networks. My last couple of ROMS I haven't liked the WIFI drain on the battery.... The JPA fix doesn't helps THAT much IMO since it takes 15min of screen off time to take advantage of the JPA drivers. Now I remember it was either Torch or Precision that Ryude changed the scanning time to happen every 90 seconds instead of the standard time. It made a huge difference on WIFI drain. Do you think its something that you could look into?
[Captivate Android Development] steph2:
This ROM and GB,s oc kernel is stable fun and fastest ROM kernel

Combo I can find, even better then today's CM7 I flashed 2play with. I even used cm Oc kernel, and this is smoother faster scores in the 2k,s on quadrant. Its also better looking. Thanks for all your hard work keep the updates comeing. Btw flashing back when charged. Battery life is amazing.
[Captivate Android Development] IRONMAN-NC:
No green theme for 7.x? :-(
[Captivate Android Development] WillyWonka23:
Makes sense. I was just curious is all. A lot of people probably don't know what it even is.

Sent from my SAMSUNG-SGH-I897
[Captivate Android Development] francous:
would AUTO FOCUS be possible with 2.2.1??
[Captivate Android Development] di11igaf:
ask and ye shall receive.

i actually just checked out what you just posted with those roms, and it looks like he tried to set this from the build.prop, just like a lot of other roms do. this does NOT work,(look at 7.1, its supposed to scan every 240 seconds, obviously thats not right cause its scanning every 6 seconds), so other roms are still scanning at the default time, cause having that in the build.prop affects nothing. so i just went through a **** load of code, found the method and changed the hex time from 6 to 32 seconds. i tried with 100 seconds and it wont compile, along with a few lower numbers. so it seems like its only possible to go right around this 32 second scan time, maybe a LITTLE higher, but not much. 32 seconds is a lot better than 6 though.

http://www.multiupload.com/IBBW34HX1P

this is 7.1.1 -only change is the extended wifi scan time.
[Captivate Android Development] bigbooty:
No biggy but I came back tonite to 7.1 and then loaded 7.1.1 but my version says 7.0.1. Lol.
[Captivate Android Development] bigbooty:
Wifi tweak rocks. Works fine.
[Captivate Android Development] Eschmacher:
Just to check, it looks like the server is fine, was it a link issue dilli?
[Captivate Android Development] WillyWonka23:
Well after updating to 7.1.1 I lost my swype functionality again. I was using pros themed version. Hmm...
[Captivate Android Development] shoman94:
All I can say is you are the man. Thank you very much....

Sent from my Captivate on the XDA-App
[Captivate Android Development] Eschmacher:
Hey dilli, I noticed a really obscure bug in 6.0 yesterday, didn't know if had caught and fixed it in 7.1. When I went to select text on a webpage, I clicked the.copy button and it popped up and said, "charged" and not "copied".
[Captivate Android Development] diablo009:
That's "cute". In other apps I used that feature it always said copied.
[Captivate Android Development] ap1618:
forgive my ignorance... can I just update from 5.6 to 7.1? (without wipe)?
[Captivate Android Development] diablo009:
In short, No.

Thumb rule: When moving between major versions, it is recommended to go with a wipe. 6.x has too many changes compared to 5.x, and same applies between 7.x and 6.x.
[Captivate Android Development] ap1618:
oh ok... but I dont have to do back to stock or anything right? just back up, and flash in recovery?
[Captivate Android Development] godzulu:
Me too - anyone have a fix or working swype they can upload
[Captivate Android Development] double RL:
This always seems to be very controversial, but I never flash back to stock. Unless I'm changing between really different releases. Although 7.1 is jsm instead of jpy, I flashed from 6.0 to 7.1 with zero problems. I figure its a lot closer than flashing from stock which is a much different version. Really confusing for people who have bought a captivate recently because they are shipping with froyo now.
[Captivate Android Development] diablo009:
I would recommend stock. It adds like 10 extra mins to the whole process, but will save from any potential issues.
[Captivate Android Development] rjblack11:
having trouble with swype and sending pic message after 7.1.1. the latter issue may be my current location.
[Captivate Android Development] double RL:
My question is why do people recommend it? I don't know and have just never seen a good argument for it. I know di11i and some other devs usually say to do it. I get that. But if I weren't the type to wanna know why, I probably would have a bone stock iphone and not a badass di11ivated Galaxy S.

My deal with it is that stock is jf6 or ji6 or whatever and Android 2.1 Eclair while everything we flash to is 2.2 or 2.2.1. I admit that I have zero idea why we should or get told to flash stock but I never do and have flashed a bunch of roms without much if any issue. And no issues that have been related to not flashing stock.

I do know that it only adds ten minutes most of the time, but when you have a phone that hates odin and flashing stock, then it just becomes more of a time saver to just put the rom together the way I like it, zip it, and flash. If I get a problem, then I can go back and flash stock. Seriously though, never having problems, I've saved a couple hours now by not going to stock over the last several months.

Anyway, seriously not trying start **** at all. I love this entire group that contributes in this thread. di11i's roms are the best for sure and the people itt are the best community I've seen on xda.
[Captivate Android Development] diablo009:
I think the whole thing stemmed when people were moving between 2.1, 2.2 and 2.2.1 based ROMs. Since the base was different, there was a chance of mess up. So it was/is considered safest to load a custom over a phone that is how it was when released from factory. This is all I can think of.

Personally, I do recommend people to do this (esp if they are in newbie state), 'cos when they are stuck it would be easier to debug their steps instead of asking what they had on earlier and trying to trace that out.
[Captivate Android Development] shoman94:
Interesting....as I didn't have any issues at all. I'm anxious to get home to see how wifi battery fix works out.

Sent from my Captivate on the XDA-App
[Captivate Android Development] double RL:
For noobs, I definitely agree. Anyway, thanks diablo.

Did anyone else have the issue from a few pages back with the rom showing up as 7.1.1 and then mysteriously switching to 7.0.1? I flashed the updated 7.1.1 last night and then checked and it showed as 7.1.1. This morning, it is showing as 7.0.1 after a reboot.

Don't care too much since the battery is badass on this thing with the di11i5v2 kernel and jl2 modem.
[Captivate Android Development] rjblack11:
not yet. +100000 on batt life.

btw can someone please send pic message on 7.1.1 jl2 dilli rom/kernel to see if it works?
[Captivate Android Development] shoman94:
It works fine.... I'm not on JL2 though.

di11i...I have a auestion about MMS pictures. I've been meaning to ask you. Every rom I flash it always sends a 640x480 picture. But when I use an AT&T rom it sends out a 1280x960. I haven't tried the AT&T froyo mms.apk though. I would imagine I should try that first? But maybe that would be a good feature for you rom also? IDK but 640x480 just sucks....lol
[Captivate Android Development] krips2003:
In layman's term 'Best Practices'.

This might come handy when someone keeps flashing roms without going to stock and one fine day feel like installing CM7 gingerbread. And guess what? Well everyone already knows the answer.

Remember windows 7 people upgrading on vista and didn't see much difference in speed and reliability. Solution, perform clean install.

Moreover, every user's experience completely different from one another.

On the other hand, now I flash roms without going to stock. I have also reflashed if I had bad flash without going to stock.

But this is not the recommended method if you are new and don't know how to flash a Tom. Till then use the recommended method.
[Captivate Android Development] rjblack11:
update: pic msg working after 20+ attempts. must be data coverage(im in a white-no data- zone on verizon's version of att 3g map) i have H iiiI bars- i represents fill, always wondered why this happens. santa rosa beach, fl
[Captivate Android Development] diablo009:
Nice explanation :)
[Captivate Android Development] francous:
im on JL2.. mms works fine.. so far
[Captivate Android Development] shoman94:
I don't get it...
[Captivate Android Development] francous:
i thought all pic messages had to be thru the data network??
[Captivate Android Development] di11igaf:
this really was a bigger issue back when not all roms/kernels were lagfix compatible and/or ext4 compatible. so there might have been a rom with an OC kernel, with no lagfix, and a rom with a voodoo kernel when it first came out. when you flash a rom without flashing stock with ODIN, your filesystem will stay as ext4, unless you specfically convert it back to rfs. a factory data reset will leave the filesystem as ext4, and the update script for the rom, even though it formats, still leaves the filesystem as ext4. ODIN on click, which repartitions will take whatever lagfix you have applied and and completely wipe it and THEN youll be back to RFS, and this is a guarantee with one click.

and then when not all kernels supported ext4, if you filesystem was still that when you flashed a non-voodoo kernel, the phone wouldnt boot.

so the thing here is, its not really flashing stock to prevent problems, its using odin one click which leaves no possibilities or corrupt/left over data/metadata and is more a complete wipe than the factory reset, as that only formats /data. and the update script also only formats, not repartitions.

ill look into this when i get a chance. if its possible ill get it working. might be an xml or something limiting the pic size that the att version is allowing a bigger size.
[Captivate Android Development] godzulu:
Does anyone no how to fix swype
[Captivate Android Development] francous:
https://beta.swype.com/

sign up.. download.. certify.. good 2 go.
[Captivate Android Development] godzulu:
Thanks francous , I had just done what you suggested theN I saw your post.
[Captivate Android Development] Phoenix-Lead:
Yeah, but then you have an ugly Swype. I know how to bring back our old looking swypes
[Captivate Android Development] godzulu:
Cmon adam, do tell. Sent via ugly swype.