yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] AnnihilatorSC:
I'm indeed observing a decrease in battery use. Whereas I used to lose about 20% of charge overnight prior to the change, I'm now gulping thru about 10%.

I recommend more testing on a larger number of devices. Suggestion: a new version of SpeedMod with altered mount options (noatime,commit=60; data=ordered is the default anyway).
[Galaxy S I9000 Android Development] bilboa1:
by the way.. comiting every 60s does not mean that the journal is useless. it means you will lose between 0 and 60 last seconds of work if it crashes, instead of 0-5s.

In most cases, that's very much ok. Although i'm a bit surprised if it makes such a diff in battery use. Mine's at default setting and with radio off I lose barely a % overnight.
[Galaxy S I9000 Android Development] hardcore:
Yes actually, maybe ext4 doesn't use as much battery as initially feared. It seems to be okay for me too (with no journal), but even with the journal I think battery use felt about the same. All subjective though.
[Galaxy S I9000 Android Development] HazzBazz:
I swear android requires journalising for stability/consistency!? Isn't that the point of ext4? It only has quadrant scores low because the journalising, and the raw performance can be increased by safely avoiding disk I/O wait?

http://upload.wikimedia.org/wikipedia/commons/6/63/E2fsck-uninit.svg

Performance improvement (love the wiki).

Anyone care to shed light on this? I'm not pooping a party I just remember supercurio's various reasons for choosing ext4, and also quandrant scores are VERY limited.
[Galaxy S I9000 Android Development] danzgrace:
@hardcore,

Could you cook kernel and modify ext4 support with no-journal already so we don't need to go to do this kind of modification, its somewhat tedious to other non-tech people.

TIA.
[Galaxy S I9000 Android Development] hardcore:
Finally getting around to doing that. I'm modifying the lagfix options in the ULF to add ext4-no journal mode.

And also some other changes like removing JFS (too unstable, no real benefit over ext4) and some of the most of crazy/useless lagfix schemes.
[Galaxy S I9000 Android Development] spline1:
all Partitions with ext4 without Journaling, i have no problems and the battery is a little more better.

It works !
[Galaxy S I9000 Android Development] danzgrace:
Awesome man. Grateful thanks!
[Galaxy S I9000 Android Development] hardcore:
Working on that. I've got a new version almost ready with several options including no-journal.

I also wanted to keep the ext4 mount options standard, BUT... one thing that struck me is this mount option: noauto_da_alloc

If I don't include it, the Quadrant scores are only about 1000 with or without journaling. But once I add that in, the Quadrant scores jump to 1500 to 1700.

Now I'm wondering, we're not after the highest Quadrant scores here. We want SPEED and STABILITY, and Quadrant scores don't really represent speed.

Should we really put the option noauto_da_alloc? It seems to be more risky.
[Galaxy S I9000 Android Development] AnnihilatorSC:
My vote is - no. Remove barrier=0 as well, which is also unsafe.
[Galaxy S I9000 Android Development] xcreatir:
noauto_da_alloc

[...] in the default data=ordered mode, the data blocks of the new file are forced

to disk before the rename() operation is committed. [...]

Seems like the option is only important if you have (bad programmed) applications doing renames on files. I do not really know how often this is happening, but my guess is: not really often.
[Galaxy S I9000 Android Development] hardcore:
Yes but, why does it make such a HUGE difference in benchmarks? It makes the single biggest difference in Quadrant scores among all the other settings (including turning off journaling).
[Galaxy S I9000 Android Development] hardcore:
But then all the Quadrant-watchers will go "oh no my Quadrant dropped to 1000 after flashing this kernel!".... Haha

If I'm not wrong, supercurio also uses noauto_da_alloc in Voodoo. I'm gonna test it without noauto_da_alloc for a while and see if there is any difference in battery life and usability.
[Galaxy S I9000 Android Development] AnnihilatorSC:
I've been running without noauto_da_alloc and barrier=0 for a day and a half and can say that there's no difference in the _feel_ of performance of the phone. I never look at benchmark numbers as they can be utterly misleading.

Well, in the end the choice is yours: to cater to the Quadrantoid masses or to create the most stable and safest possible replacement for the stock kernel. ;)
[Galaxy S I9000 Android Development] GwynBleidd:
Ghm, seems that the only thing that auto_da_alloc does is fix the behaviour (to make it more ext3ish) if it detects 'incorrectly' written programs which use rename or truncate instead of sync when writing a file. I guess that, in doing so (detecting and additionally monitoring each write) it also becomes slower and drains more battery.

No clue at all whether there is a slightest possibility to meet such poorly written apps on our device, but my personal opinion is that its safe to use noauto_da_alloc - and it should really give perfomance gains, maybe not as much as Quadrant wants them to be.

Side note: why don't we include nodiratime together with noatime by the way? Just noticed that there is such an option.

EDIT: Wow, just thought about an explanation to Quadrant's difference between auto_da_alloc and noauto_da_alloc (a mere assumption though):

Quadrant ACTUALLY IS a 'poorly written program', so it either renames or truncates instead of syncing in its write tests. That's why with auto_da_alloc ext4 detects that AND turns off delayed allocation for these writes, making it much much slower. At the same time, most/all system programs use the 'correct' sync behaviour, that's why there's no noticeable difference.

How does that sound? :)
[Galaxy S I9000 Android Development] CommanderROR:
Whatever the reason, I would like to at least have the option of using the faster and more energy efficient system...

Also, quadrant might not be all that reliable but it does give an indication of what is faster an slower, so let us not discount the quarant scores completely.
[Galaxy S I9000 Android Development] hardcore:
noatime implies nodiratime - you don't need to specify both. Now I'm beginning to get interested to try ext3 as well, and if there's ext3 why not ext2? Hmm...
[Galaxy S I9000 Android Development] GwynBleidd:
From what I remember, ext3 with journaling is much slower than ext4 because of absense of delayed allocation (it basically does what auto_da_alloc does for ext4, but all the time), thus it wouldn't be of any advantage.

On the other hand, ext3 without journaling (I think you can apply ^has_journal to ext3 as well) is generally a plain ext2; but so is ext4 (or almost is at least) - so I don't think there would be any advantages.
[Galaxy S I9000 Android Development] hardcore:
I just build a new test kernel with ext2, ext3, ext4, ext4 no-journal support.

Quadrant Benchmarks:

ext2: 1700-1800

ext3: 1000

ext4/ext4nj: 1000

ext4/ext4nj noauto_da_alloc: 1600-1700
[Galaxy S I9000 Android Development] CommanderROR:
Ver cool!

Can I have it please... cwm package would be nice... :)
[Galaxy S I9000 Android Development] hardcore:
Here's my current snapshot. This is like an alpha preview of SpeedMod K10. Have fun!

P.S. This is really experimental. I'm still deciding which ext4/ext3 parameters to use. Journaling is tricky.

EDIT: Removed download. Moved to a new post.
[Galaxy S I9000 Android Development] CommanderROR:
Thanks.

I'll give it a try.
[Galaxy S I9000 Android Development] GwynBleidd:
Awesome! Thanks for the kernel, going to try it out.

You might want to check these benchmarks, or we need to say that synthetic tests suck - because noauto_da_alloc should have any effect on ext4 only in case there is a journal.

EDIT: Question, are you actually using 256Hz yourself?
[Galaxy S I9000 Android Development] CommanderROR:
I tried the ext4 no journal and ext2 briefly and I think ext2 really rocks performancewise... sadly, I can't compare to the auto alloc ext4 sice I could not find that option in the kernel you provided. I'll testdrive the ext2 for a bit and see how consistent the performance is and whether battery life changes. Right now it feels perfect, all reactions are immediate, with ext4 I had occasional stutters, so far I have none on ext2.
[Galaxy S I9000 Android Development] dupel:
I think its high time to move to another letter =)

So, is ext2 faster (in your experience) than ext4 no journaling?

And do you plan to add [RFC/RFT PATCH v3], new complier and options. Maybe even some changes from jfs kernel (security and stuff) as they look tasty.

Not to mention than we all really want some uv, to save even more battery =))
[Galaxy S I9000 Android Development] hardcore:
Thanks for trying it guys. I'm most interested in any differences in battery life there may be. Frankly they all seem to be fast enough.

BTW just realized the codesourcery 2010.09 is out!
[Galaxy S I9000 Android Development] mengsuan:
I just tried ext2. The first run seems to conclude that ext2 is not as smooth as ext4nj. I need more time to observe though.

K10 alpha1 does not have noauto_da_alloc option
[Galaxy S I9000 Android Development] hardcore:
Yup. It's easy for me to add it, but I'm thinking where in the cwm ui to add it. Maybe under tweaks.
[Galaxy S I9000 Android Development] mengsuan:
Or ULK advanced options?
[Galaxy S I9000 Android Development] CommanderROR:
I am worries... ext2 feels pretty good an smooth here, better than ext4 with journals in any case... however, my battery is draining like mad. I haedly touched the phone today and am already down to 76% although lunchtime is just arriving. Spare parts shows "running" (translated from ausführen) as the culprit. Screen on time is 10% and this running whater it means appeara to have swallowed 80% of the used battery amount...

Either my battery meter is suddenly out of sync or something is gravely wrong. Can somebod double check this?
[Galaxy S I9000 Android Development] s88:
ext4 without journal is very fast. much faster than ext4, even though quadrant is only ~1k.
[Galaxy S I9000 Android Development] Mitiko78:
Where can I find this:

K10 alpha1
[Galaxy S I9000 Android Development] mengsuan:
http://xdaforums.com/showpost.php?p=9454832&postcount=60
[Galaxy S I9000 Android Development] danzgrace:
http://en.wikipedia.org/wiki/Ext4

From this document I think we can benefit with the "noauto_da_alloc" mount option on battery usage but not data safety.
[Galaxy S I9000 Android Development] hardcore:
Interestingly, the Linux laptop-mode tools sets the commit to 600 seconds!

http://www.linuxjournal.com/article/7539

http://samwel.tk/laptop_mode/laptop_mode

The intention was to save battery life. No wonder ext4 seemed to suck up more battery.
[Galaxy S I9000 Android Development] danzgrace:
and the reason why we get more high score on quadrant with "noauto_da_alloc" setting.
[Galaxy S I9000 Android Development] AnnihilatorSC:
Now why doesn't that surprise me? :P

In any case, my opinion is that commit=X should be the only mount option, leaving everything else to ext4 defaults (journal enabled, data ordered).
[Galaxy S I9000 Android Development] danzgrace:
so its safe to say, we should use that noauto_da_alloc mount option for better SGS performance and longer battery life.
[Galaxy S I9000 Android Development] hardcore:
SpeedMod K10 is up on the main thread and also here: http://touristinparadise.blogspot.com/2010/11/samsung-galaxy-s-download-speedmod.html

By default now it uses the fast ext4 mount options. If you want to go to the safest/slowest/standard one, u can toggle it from the recovery menu also under ext4/3 mount options.
[Galaxy S I9000 Android Development] mengsuan:
I assume the slow/fast mode is about noauto_da_alloc? :)

Previously I was on K10 alpha1 which uses ext4nj without noauto_da_alloc. I just had to select ext4nj again in CWM, then the quadrant boosted up to 1.6k again without having to go through all the backup, format and restore. Good job!
[Galaxy S I9000 Android Development] cnn888:
seems to me, the ext4 no journaling is FAST, ... BUT... i lost data for so many times.

tried your k10 with ext2 for all, feels very solid. update later.

thanks hardcore.
[Galaxy S I9000 Android Development] hardcore:
Glad to hear that. Yup the "slow" mode is the default mount options which should be the safest. Normally I'd recommend the safest but I think default mount options also uses more battery life, which is why I recommend the "fast" mode.
[Galaxy S I9000 Android Development] tonymy01:
Interesting you mention this... I had tweaked my ext4 with tune2fs as per the other thread, and made an init.d script to remount tweak, but since speedmod V10 introduced these tweaks natively, I figured I would upgrade with the no journalling option, and I noticed on 2 reboots I had lost recent changes to my upgraded/download apps (and a double vibrate regularly happening with no crashing app log on screen, adb logcat showed it was gmail spitting the dummy, so I cleared the gmail email data and it all came good).

I do type "sync" and then "reboot recovery" from time to time, I wonder if this is still prone to losing data rebooting this way??

Also noticed in one or two bootups when I had this issue that fsck was finding errors and creating lost+found files.. but the past 24hours after doing the conversion, it has stabilised (also as I have been more paranoid and doing proper power button type shutdowns, rather than from console).
[Galaxy S I9000 Android Development] hardcore:
Just in case anyone's wondering... looks like ext4 barriers don't work with our phones:

<4>[ 8.278209] JBD: barrier-based sync failed on stl11-8 - disabling barriers

<4>[ 8.278621] JBD: barrier-based sync failed on stl10-8 - disabling barriers

So better to just mount them with barrier=0.
[Galaxy S I9000 Android Development] haroonasla:
How to convert back to journaling mode ?

Hi guys. can anyone tell how I can convert from non-journaling mode to journaling mode ? Is there any safe procedure / set of commands or do i have to convert back to rfs and then back to ext4 standard.
[Galaxy S I9000 Android Development] supercurio:
tune2fs -j /dev/block/mmcblk0p2 (for data, adjust the device name for other partitions where you removed the journal)
[Galaxy S I9000 Android Development] haroonasla:
Thanks ! that was a quick response :) will try this now. should i do a fsck on each partition after this ?
[Galaxy S I9000 Android Development] supercurio:
No need, but the journal will be active only after a reboot.

You can do this in normal mode even when the partition is mounted ;)
[Galaxy S I9000 Android Development] haroonasla:
nicee. also sent u a pm about voodoo. see if you can figure out something from the log. No complaints whatsoever since voodoo magic just rocks !
[Galaxy S I9000 Android Development] dupel:
Strange, error chech doent work on latests doc (JPY + voodoo), as well as removing journal (asks to check before that).
[Galaxy S I9000 Android Development] carfield:
If I run umount and get error message, is that mean I don't have ro.debuggable enabled?
[Galaxy S I9000 Android Development] cba1986:
I cannot execute e2fsck. not found.

Any ideas?
[Galaxy S I9000 Android Development] oswade:
Sorry to bump an old topic, but I used this guide on gingerbread and my phone is rockin!!! :D Living on the edge :cool:
[Galaxy S I9000 Android Development] gsw5700:
FYI... Speedmod ext4 mount options

$ mount | grep ext4

/dev/block/mmcblk0p2 /data ext4 rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered 0 0

/dev/block/stl10 /dbdata ext4 rw,noatime,commit=20,barrier=1,nodelalloc,data=ordered 0 0

/dev/block/stl11 /cache ext4 rw,noatime,commit=20,barrier=1,nodelalloc,data=writeback 0 0
[Omnia 7 General] saldawop:
I did a search of this forum before posting this so here goes.

I have synced my google calendar with my Omnia 7. Is it possible to increase the amount of time it looks for an appointment to show on the homescreen?

My next appointment is Saturday (two days) but it doesnt show up on the tile on the homescreen.
[Omnia 7 General] sergioiacobucci:
Hi

Seeing as noone has replied to your question I thought I would, as far as i am aware I cannot find a way to increase the amount of days shown on the live tile and mine is synced with windows live.....so i am going to say no you cant sorry

serg
[myTouch 4G Q&A, Help & Troubleshooting] stdafx:
i formatted my touch4g's SD on PC. (all data on SD are lost)

and now i can't run the recovery any more.

i searched google and it says that there're important system data located on SD and cannot be erased. is that the reason i failed to recovery my phone ?

what can i do now ?

thx for help !!
[myTouch 4G Q&A, Help & Troubleshooting] sicdroid:
Open ROM Manager and reflash Clockwork .
[Streak 5 General] Umaycry:
Helllo this is my first post here and i hope you can help me cause this is realy getting on my nerves now.

I live in sweden and we got the official update this thusday and ever since my dell streak lockscreen dosent respond while i have a fullscreen app running.

The scenario: I fiddle some with the phone read my RSS feeds and turn on spotify, ready for a walk to work. Suddenly this song that i dont like comes up and i want to change it...or maybe i just want to send an SMS. But no, i cant open the lockscreen. For some reason it just dosent work so il have to pull the battery out and reboot the phone while my fingers freeze to ice. After that it works flawless until i run spotify again and the screen locks.

Is there anyone that have the slightest clue or have experienced this themself? I've tried to calibrate the screen without any success.

I have no custom rom or anything, the only thing is that i use ADW.Launcher.
[Desire HD Android Development] exidler:
I don't like quite speaker of DHD, and don't want use non sense rom.

After small research i have found working solution :)

DSP manager needs customized libaudioflinger.so, but if just replace it, all sound gone on sense rom. :(

I have taken libaudioflinger.so and libaudio.so from CyanogenMod 6.1.0 Beta 3, and replaced. DSP Manager WORKS fine! :)

But then i have found another problem, DSP Manager disables it's eq when phone in call (also when it's ringing), so i have modified manager source and added new page for speaker settings when phone ringing.

All what you do, you doing on own risk, I'm not responsible for any damage!

Backup libaudioflinger.so and libaudio.so from /system/lib/ before continue

This patch will break dolby and srs features of preinstalled music player

2010.11.29 This patch also breaks working of stereo bluetooth headset, but in in call bluetooth headset works well

- Install patch using Recovery

Download DSPManager-DHD-update.zip

Copy it to phones sdcard

Reboot to recovery and apply this update.

- Install manually (using adb) * you need to know what is adb and how use it, and have S-OFF with ENG HBOOT

Download DSPManager-DHD-files.zip

Unpack files to temporary directory

Remount /system on phone as rw (run 'adb shell', then rund command in shell 'mount -o remount,rw /dev/block/mmcblk0p25 /system')

Run commands from computer

#adb push libaudio.so /system/lib/

#adb push libaudioflinger.so /system/lib/

#adb push DSPManager-DHD.apk /system/app/

and then reboot your phone.

- Uninstall manually (using adb) * you must have S-OFF with ENG HBOOT

Connect phone to computer using usb

Open adb shell (run adb shell)

Remount system as read write (run in shell 'mount -o remount,rw /dev/block/mmcblk0p25 /system')

Then you need copy to /system/lib/ on phone backuped files libaudioflinger.so and libaudio.so.

If you backuped it on computer, then locate they and in backup folder run

#adb push libaudio.so /system/lib/

#adb push libaudioflinger.so /system/lib/

if you backuped files on sdcard, then from adb shell run commands

cp libaudio.so /system/lib/

cp libaudioflinger.so /system/lib/

rm /system/app/DSPManager-DHD.apk

then reboot your phone

- Uninstall with recovery, rollback libs to stock v 1.32.405.6

Download DSPManager-DHD-uninstall.zip

Place it on sdcard, and install this update from recovery.

How it's works (amplify about +6db):

[YOUTUBE]AzAfyZEQbpg[/YOUTUBE]

to moderators: i'm posting in

'Desire HD Android Development' because using this patch required changing /system/ partition
[Desire HD Android Development] broncogr:
So is it a lot louder with DSP manager installed?

I am especially interested in ring volume and notification volume as i am finding that I tend to miss some calls and SMS's because i dont hear them
[Desire HD Android Development] exidler:
Speaker it self not so good.

But overal volume can be increased. Is it will be enough for you - don't know.

All changes made by 5band equalized, in range +/- 10db (as drawn in configuration utility)
[Desire HD Android Development] bigtin:
Works great, thanks!

I find the trick with the DHD is to make sure you put it in your pocket with the screen facing your leg since the back speaker is much more powerful than the front one.
[Desire HD Android Development] broncogr:
Ok I have installed it.

What settings are you using for gain in the 5 bands? I have tried +6 in all five.

Will this also work for notifications and sms notifications?

I posted about this app on the LeeDroid Rom thread. Maybe Lee could add the app to his Rom if enough people are interested...
[Desire HD Android Development] SkilletDesire:
Just to inform you all this knocks out dolby and srs. Restoring the system lib files should restore them though.
[Desire HD Android Development] exidler:
i have using 5.0, 6.7, 6.5, 6.0, 4.3 (i'm don't like high pich of speaker)
[Desire HD Android Development] exidler:
thanks, i will write about it in first post.
[Desire HD Android Development] psych0t1c:
Would it be possible to hack the Dolby / SRS feature in a way that you can globally enable it so that every music player and even system sounds/notifications can benefit from it?

That would be pretty awesome, I kinda like the sound of those features, but I dislike the music player. I think this would be a cool thing to explore / include on custom ROMs.
[Desire HD Android Development] LeeDroid:
Nice job! Was getting round to this one, its already an add-on for my Desire ROM

Swyped from my LeeDrOiD loaded HTC Desire HD using my thumb....
[Desire HD Android Development] Software Guru:
Excellent work
[Desire HD Android Development] lukesky:
maybe some one would be so kind to make a before and after video so that we can all see how great this patch works? :D
[Desire HD Android Development] exidler:
I have uploaded video, look in first post.
[Desire HD Android Development] Rixsta:
Noticed the difference...great work ! :D
[Desire HD Android Development] Kimi123:
Doesn't work on Legend/FroYo

I am using an unofficial froyo build for the legend. http://xdaforums.com/showthread.php?t=841517

Unfortunately the DSPManager doesn't work with that rom
[Desire HD Android Development] Rixsta:
Just a quick side note...

Couldn't get the CWM.zip to work so I pushed the files using root explorer...worked fine :)
[Desire HD Android Development] nandihno:
Excellent job I can hear now lol
[Desire HD Android Development] exidler:
This *.so libraries only for Desire HD hardware.

Look for original DSP Manger package
[Desire HD Android Development] xdaman85:
@exidler

I have written a little guide for your DSPManager patch on our website, hope you don't mind.

http://hemorrdroids.net/do-you-wish-your-desire-hd-speaker-could-be-louder/#more-2424

:)
[Desire HD Android Development] eozen81:
Thanks a lot for this development. At least we know this low speaker issue can be developed or fixed via software update, I hope HTC engineers will see and integrate it this into new batches with a few developments so that new users al least will not suffer :)
[Desire HD Android Development] brolee93:
I have bug , my speaker work and other work etc ok , but my bluetooth ear samsung sbh-650 didn't work with this i don't hear music or video but i can use phone lol i listen my friend with phone
[Desire HD Android Development] silashack:
This is what I love about these forums, you have an issue and some one takes the time and effort and fixes it

Many many thanks my friend