yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] fragargon:
no i didnt change anything... flashed as it is. :rolleyes:

(i will correct the sig)
[Desire Android Development] mrkaehler:
OK. I will try that - later ...

But why works the "dirty" second boot? What is the difference? It's the same script.

Desire on slim ics v0.9
[Desire Android Development] suiller:
I think that the 1st clean boot is unable to mount correctly

I don't know what is the cause but could also hardware dependent... pheraps the card despite its speed class needs those more ms to initialize correctly

I'm just inventing but probably is something related
[Desire Android Development] suiller:
Can I have your df output plus du -hcs of your system?

Ps: Run du inside system folder
[Desire Android Development] suiller:
UPDATE, gained some precious Mb for /system partition by revisiting xbin & bin folders

for ex I removed bash & sshd setup (left instead ssh client) plus other not used binary, cleaned a bit /etc compartment (smaller unused files but better than nothing)

now /system takes just 139Mb, so "we" left about 7Mb for eventually cover damaged/unusable nand sectors, this to prevent bootloop on full /system after fresh installation

as usual published under repository or dropbox mirror :cool:
[Desire Android Development] marcocsh:
The governor always jump back to conservative and cpu speed always jump back to min 960 max 1075 automatically. No reboot before jumping back.

Am I the only one who have this issue?
[Desire Android Development] mrkaehler:
My?

app_86@android: /system # du -hcs
137.9M .
137.9M total

For "df" see above:

Filesystem Size Used Free Blksize
/dev 202M 32K 202M 4096
/mnt/asec 202M 0K 202M 4096
/mnt/obb 202M 0K 202M 4096
/system 145M 141M 3M 4096
/sd-ext 287M 158M 128M 4096
/cache 5M 840K 4M 4096
/data 1G 278M 752M 4096

---------- Post added at 11:06 AM ---------- Previous post was at 10:27 AM ----------

Now:

- I took the new v0.9(25 May 2012 @ 10:05) pushed your patched 40ad2sdx into

- reflashed via Ext4-Control incl. wipe dalvik cache

Booted! :D

df:

Filesystem Size Used Free Blksize
/dev 202M 32K 202M 4096
/mnt/asec 202M 0K 202M 4096
/mnt/obb 202M 0K 202M 4096
/system 145M 139M 5M 4096
/sd-ext 287M 163M 124M 4096
/cache 5M 836K 4M 4096
/data 1G 288M 743M 4096

du:

app_86@android: /system # du -hcs
135.3M .
135.3M total
[Desire Android Development] suiller:
all seems right

I've just published a "new" version with modded 40xxx a2sd script, if you have time can you try to flash over & see if fails again on your 1st boot? thank you

EDIT: you were faster than me :D
[Desire Android Development] suiller:
there is no issue, is that we want... different states between display on/off

on 3rd post all is well explained: http://xdaforums.com/showpost.php?p=25000098&postcount=3

you can't change freq or governor trough setcpu or evervolv toolbox, it's controlled by mycpu sub-script ;)
[Desire Android Development] efattal:
About home button

Hi suiller,

I can finally post here and first I can say thanks (tante grazie) for your work. Sandvold and the whole team made a fantastic job. Your version and mods makes it even nicer from my experience.

However, since 0.9 version, even with your today's latest version, after full wipes, my home button doesn't behave normally. Sometimes it's unresponsive and I have to press at least twice. With long pression it doesn't even display running apps anymore.

Thanks for your advices.
[Desire Android Development] mrkaehler:
:D :D

:eek: I had your new script replaced by an older one ... compared ... it is only the first "sleep" - but I am happy that my device now is clean booting
[Desire Android Development] marcocsh:
Dear Suiller,

Ooops I don't aware it is caused by the script. I will just stay with it and have a test on the battery life. Thanks for your explanation anyway.
[Desire Android Development] suiller:
trust conservative governor & you wont get BSOD ;)
[Desire Android Development] suiller:
you are not alone but I think it could be also hw related... simply because 99% didn't report this kind of issue

have you noticed the same behavior with previous rom (also different rom) or you are noticing it also because actually you are focusing on it?

but of course could be software dependent, I mean 3rd software app

as you saw few posts back we discovered that some sd-cards are a bit "reluctant" to mount within 1 second upon 1st boot, so it couldn't be a strict rom issue
[Desire Android Development] efattal:
I'm quite sure I didn't have the problem with the original 0.9 version. And I am sure I didn't have it with previous versions.
[Desire Android Development] suiller:
hmmm... strange, I think isn't a cpu-timing issue also because they are very high when display is on, in fact for ex sliding is very smooth

try also to focus your attention to latest installed/upgraded 3rd part software, if it would a general issue it will touch mine device too

just to be sure post your logcat here & I'll give it a look ;)
[Desire Android Development] suiller:
Please... we are looking for BSOD, remember that shaky kernel (included) is still in beta stage
[Desire Android Development] vlaya:
Updated to 0.9, very nice. Battery life significantly improved. Or I didn't use my phone that much today :)

Maybe it's the new kernel, I don't know, but I do not complain :D
[Desire Android Development] satamateur:
+1
[Desire Android Development] gie62001:
i think thats the way he set up 98mydesireI script as its governing CPU clock speed and governor, but yes it jumps back to me too, so i just leave it as it is (the only reason i wanted to check how people get BSODs as the only time i used to have was maybe 0.6 version but its been quite long so i leave the CPU clock speed as it is).
[Desire Android Development] marcocsh:
Yes mate you are right. Suiller has explained to me in the last page that it is normal!:thumbup:
[Desire Android Development] efattal:
I looked in my logcat and I saw that apps displaying ads (like MX player free) generate lots of exceptions because unable to reach ad servers. As in your version hosts are modified, can this explain my home button issue as the phone continues trying to reach the server? I still have to confirm but it looks like until I start such an app everything is fine.
[Desire Android Development] efattal:
Exceptions from Dropbox service too? Which app use it?

My logcat is available here http://pastebin.com/Da1sjtz8

Thanks for your time
[Desire Android Development] suiller:
yep, I must admit... I hate ads, I know they are useful to app developers but they stress continuously precious 3g band, take resources and sometime post personal/private info

so I prefer to limit them ;)

dropbox service is an internal android service to collect crash dumps, it is needed only by app developers who can take a look inside in case of a specific app failure

general issues/errors are anyway collected by main log, that isn't locked

we need access just to the general issue log file... the rest produce just traffic/space/resources waste

so it's normal that you see dropbox service locked and unable to record any request... is that we want :cool:

anyway I don't understand when you say: I still have to confirm but it looks like until I start such an app everything is fine.

a specific app or generally speaking?
[Desire Android Development] suiller:
no absolutely

on the contrary your device will use less resources because ads request are deviated to localhost (127.0.0.1)

for ex I blocked also this kind of things:

W/UsageStats( 331): Failed writing stats to file:/data/system/usagestats/usage-20120525

I don't want that apps will collect usage stats... personal usage stats... ask me before doing it :rolleyes:

or this:

E/DropBoxManagerService( 331): Can't write: system_server_wtf

E/DropBoxManagerService( 331): java.io.IOException: Can't mkdir: /data/system/dropbox

yeah you don't have to write anything that I don't want/need

in case of issues main log file is more than enough ;)
[Desire Android Development] efattal:
Sorry I was referring to apps with ads.

I know that ads are blocked on purpose. I was just wondering why this causes some apps to generate logs and if this could be an issue. I guess my idea is wrong.

However, after wipe cache/dalvik and fix permissions, it looks like the home button behaves normally.
[Desire Android Development] suiller:
perfect, keep me informed if it works

now that I think about... I read somewhere issues related to button reaction till dalvik flush... I'll give a look but I'm almost sure that it's just 3rd app dependent/related issue, perhaps freeing up caches keeps in order some stuffs :rolleyes:

here similar case:

http://xdaforums.com/showthread.php?t=1504501

so at least you're not alone :D
[Desire Android Development] suiller:
UPDATED to Sandvold 0.10

as usual download from repository (in signature) or from dropbox mirror (link in repository website) and flash over, only cache+dalvik wipe is needed ;)
[Desire Android Development] mrkaehler:
v0.10 installed (cache+dalvik wiped), normal booted, seems fine

any special points for testing?

Desire on slim ics v0.10
[Desire Android Development] suiller:
Only pain here :D

Thx for testing :cool:
[Desire Android Development] marcocsh:
used the latest version for 4 hours. Battery life is excellent. No BSOD. No problem in installing apps in market.

Another excellent work by Sandvold and Suiller! Thanks!
[Desire Android Development] suiller:
I'm experimenting some different combination for managing our vm cache

in particular I'm trying to gain best balanced performance by tuning vm virty ratios... here explanation:

http://hep.kbfi.ee/index.php/IT/KernelTuning

hard to find a definitive setup, also because values aren't perfect for all uses and above they should be adapted on kernel type

keep in mind also we don't have any physical disk (no spin disk) and we have a limited amount of ram

I'll make some bench runs to establish which values could fit better our "common" setup
[Desire Android Development] suiller:
experiment finished, these are results:

====================================================================
| dirty ratio | dirty background ratio | 1st run | 2nd run | average |
|-------------|------------------------|---------|---------|---------|
| 65 | 5 | 1737 | 1712 | 1724 |
| 95 | 5 | 1554 | 1724 | 1639 |
| 95 | 55 | 1728 | 1740 | 1734 |
| 60 | 10 | 1753 | 1716 | 1734 |
| 55 | 5 | 1778 | 1797 | 1787 |
| 60 | 40 | 1771 | 1724 | 1747 |
| 55 | 35 | 1673 | 1743 | 1708 |
| 45 | 5 | 1759 | 1779 | 1769 |
--------------------------------------------------------------------

so it's clear, at least on short run, that dirty background ratio should stay between 5 and 10 (%), while dirty ratio has sense for a value near 50 (always in %)

benchmarks were taken in same conditions (on my office desk :D ) and waiting 5 clock minutes between 1st & 2nd run
[Desire Android Development] suiller:
published 0.10.1

framework isn't changed, so as usual a flash over is enough ;)

ps: I maintained shaky kernel because I feel it smoother anyway if you want test latest drewis (tiamat based one) flash from recovery as usual (a copy is available in repository)
[Desire Android Development] marcocsh:
Just flashed v0.10.1 (cache+dalvik wiped) but stuck in the boot screen. Tried twice and the device never boot up. Need to go back to v0.10 now.
[Desire Android Development] suiller:
Really strange it's almost identical to previous version... I'll give a fresh flash thia morning & see what happens ;)
[Desire Android Development] gie62001:
not sure what happened here but mine flashed (cache+dalvik wiped) and working properly. try redownloading the rom and flashing again maybe the .zip got corrupted somewhere? or skipped some sectors while flashing (maybe bad sectors on NAND or SD card?
[Desire Android Development] efattal:
Hi suiller,

With every version since 0.6, and even after full wipes, every (not just first) boot takes a very long time: 1:55 on splash screen then 0:55 on boot animation.

How long is it for you?

Config:

Cm7r2

Amarullz

Sdcard: SanDisk 8gb class 10
[Desire Android Development] suiller:
it's an usual behavior, if you wipe dalvik cache it will take some minutes on a fresh start-up to rebuild basic dalvik cache

rarely I wipe dalvik so I don't realize differences, then if something wrong I proceed with a full cache wipe + rom reflash, 90% of times 1st flash works perfectly ;)
[Desire Android Development] suiller:
yep probably, in this cases is better to give a look at the recovery log, first lines show eventually bad sectors during /system format: # adb shell cat /cache/recovery/last* >recovery.txt
[Desire Android Development] efattal:
That's the point : by first boot I meant after cache/dalvik wipe. But the long boot is on every boot! :confused:
[Desire Android Development] suiller:
just tried here... a complete reboot takes only 3 minutes

anyway my98scriptI has to wait 90 seconds before apply mods/tricks, because it needs to wait some OS services to start :cool:
[Desire Android Development] marcocsh:
Guys, after re-downloading and another flash attempt I now get it working. Thanks! I will test and report if there is any issue!
[Desire Android Development] efattal:
Sorry it looks like we have the same time and behavior. I just have to be more patient. :o

Thanks for your time.
[Desire Android Development] suiller:
never mind I though you had to wait many minutes... 3 minutes is normal :D
[Desire Android Development] suiller:
oh very well, perhaps is better I add the MD5 check-sum, in this way is easier to detect broken downloads :cool:
[Desire Android Development] mad_tom:
hello,

i followed this version/build/rom/whatever from beginning but i didnt used it so far.

i hope it's not posted already but i can not see it.

i wonder why talk.apk isn't in that rom, because there is space left on /system.

it's an system app and it cant be installed on internal memory (for example email.apk can be) - i know it's your choice, but i still wonder why do not integrate it if space is left, also it cannot be downloaded easily from google play, ok easy just root explore it and move it there after new install.

second thing is, there is something missing to use the the speech recognition in maps for example, start maps-> "destination with speech" (sorry i got german version, maybe it's also important to know)

google text-to-speech is installed, german pack installed.

(not the pico tts)

maybe it's not needed, is it?

ofc i want to say thanks for that rom!

it's very smooth and i like it - if it was not - i would not post anything^^

if i do wrong and/or i got wrong suggestion of this rom, just tell me.

thx for your answer/help

i'm on 0.10(not the actual version)
[Desire Android Development] suiller:
you're right but 1st not everyone needs it and as you confirmed is possible to re-insert it after full installation, and 2nd but more important is that we need a sort of free/security margin of free space under /system

this because as happened recently some users reported bad sectors under they /system folder, when you have many bad sectors in reality you'll miss some space that isn't reported into allocation table... so even if you see for ex 145Mb of free space under /system partition in case of damaged nand it's not so rare to have up to -5/-6Mb less than reported

to avoid this it's necessary to keep at least 5Mb of free space maring

if you are sure that your /system partition has enough & good free space you can simply inject talk.apk directly into the .zip under /system/app folder

I didn't included any language pack of both pico & true tts because they are downloadable from market and above all they are required & installed automatically by OS into /sdcard (you wont loose after a wipe for ex)

I don't remember well (because I done it just one time) but the OS itself will ask in case it needs lang pack, mine has asked to download tts lang pack when I enabled voice into CoPilot nav software

perhaps is it software dependent? dunno but it should work for all at the same manner

please report if you have any issues, I'll give it a look ;)
[Desire Android Development] junjihoon:
Thank for great work!! I'll try it!
[Desire Android Development] Yannn:
about camera and usb tethering ???
[Desire Android Development] suiller:
it's the same version provided by Sandvold, I just removed/replaced some stuffs & integrated some tricks/patch available here around, plus some personal mods to satisfy "slim" people :cool:
[Desire Android Development] sempi601:
Hello suiller!

Thanks for this awesome ROM, I've just downloaded it. It feels really responsive and snappy. But I really miss the adhoc support. At the moment I cannot connect to a normal wifi network, only through adhoc. Have you got a solution to that?

Because I've tried replacing wpa_supplicant that usually solved it, but here it won't work. :(
[Desire Android Development] suiller:
sorry but it's not clear... 1st you say that you miss ad-hoc support then you say that you can't connect to normal (no-adhoc) wlan... :confused:

from this afternoon I switched trough 3 wlan with based on 3 different router/providers and I got connection without trouble

anyway wlan class is the same provided in original full ICS Sandvold rom, so if you was able to connect before you must able to connect now :rolleyes:
[Desire Android Development] sempi601:
I can connect to normal wifi without a problem, but now where I am there's no wifi router. But I have a computer with wired connection and I shared the computer's connection. This is adhoc that I cannot connect to. Anyway I'm trying to get a solution.
[Desire Android Development] suiller:
ok now I understood... sorry ;)

I'll try soon I'll be at home :)

excuse me but I really use seldom ad-hoc connection :rolleyes:
[Desire Android Development] Klausi:
Hi suiller,

atm I'm using a stripped down version of CM7.2 RC1 so it fits into the old cm7 hboot (130mb /system, 5mb /cache, 300mb /data).

I'd like to try sandvolds rom - do you see any chance of removing some more stuff like recorder, search or something else, so that the rom will fit into my hboot?

Thanks, Klaus
[Desire Android Development] fragargon:
hi Suiller,

I just installed the slim rom with your desire tweak...

well i can say that is running really fast, smooth and fine.

Installed full stock as i m not used to :D

as a bit lazy, i used Titanium to restore paas i used to play with.

well i hit the button:rolleyes:

thanks mate
[Desire Android Development] suiller:
dear Klaus let me think... actually the rom takes about 137Mb under /system

soundrecorder takes few Kb

most "fat" apk are:

android.playmusic = 5.3Mb

GoogleTTS = 4.1Mb

Gallery = 1.6Mb

you should remove at least first mentioned 2 apks to be sure

Listen to me, it's just a chess mate game... dowload & install winrar, then extract from original .zip under /system/app: android.playmusic.apk + GoogleTTS.apk to whatever you want (for ex your desktop)

then remove (delete them from zip itself, always from winrar)

then re-inject those 2 apks under /data/app folder

it should work because you moved about 10Mb from /system to /data ;)

please if it works report here it could be useful for future development :cool:
[Desire Android Development] suiller:
so titanium worked? this is a good new :D

I'm one from old school, so not familiar with 3rd part restoring tool

from which version are you coming from? I suppose regular Sandvold ICS, if different please refer here. thank you
[Desire Android Development] fragargon:
latest ics sandvold on cmr2 hboot with amarullz script as i am not heavy app consumer... i do this

i used to have around 50 apps so it fits well into your slim rom and yes i just restore about 49 apps + data with TB without problem. I dont advice to do such with system app or system data...

m2c
[Desire Android Development] junjihoon:
Very fast!! I love it! Thank you again
[Desire Android Development] suiller:
yep the goal is to make our nand sufficient... and it is... I have 117 app installed and still 60mb free, of course all games are moved in sd (with regular method) so I don't need anymore sd script

don't use any a2sd script if really not needed. for how much can be fast your sd card it can't compete with nand speed :rolleyes:
[Desire Android Development] trinity1:
For those who are asking whether Titanium Backup works when restoring apps from gb roms to ICS and vice versa I can tell you what I have experienced.

As far as I've seen, the problem isn't the rom but available space for apps (especially “where” this space is available), and whether you have apps onto ext or not, because:

- 99% apps are compatible with both gb and ICS roms (if not the app's dev will for sure work on new version of app, if he wants to have the app downloaded from play store…); all my apps restored with TB always worked, apart from the rom I had on my phone

- TB uses to restore apps only onto (internal) /data partition (I could be wrong but that seems its normal behavior).

So, when you have cm7r2 hboot, data partition is 287MB (according to alpharev), against the 147MB /data partition of stock hboot. Furthermore some of this /data partition can be used by some system apps, which reduces the available space for you.

CASE STUDY: you come from a gb rom/cm7r2 hboot, you have more than 147MB of apps backupd with TB, and want to give a try to an ICS rom which requires hboot stock. What you can do is:

- OPTION 1: restore only some of the backupd apps. PROS: it doesn’t take too much to restore apps. The rom itself together with restored apps is fast and fluid. You are forced to evaluate whether keep a specific app or not (I consider it a benefit since I had some apps which I didn’t actually use… So I decided to “kill” them; which helped also in reorganize my phone). CONS: if you really want/need to have all apps back then you are in trouble.

- OPTION 2: create (if not already available) an ext partition onto the microSD, then restore some of the apps, use some a2sd script to move apps to ext partition (which will free the internal /data partition), and continue restoring apps from TB. PROS: you have all your favourite apps back. CONS: it takes time to restore all the apps, since you have to apply a2sd, reboot the phone etc.. The rom/restored apps can be laggy (as Suiller already explained): even if the ext partition is considered (by the OS) an “extension” of /data partition, widgets (just an example) are not as fast as when the app is onto /data partition. The same for games. It depends on sd class (read/write timings), and can be very annoying.

Sorry for the OP, but I've seen a lot of people to have a struggle to restore apps and to affirm that a ROM doesn't work, when it's just a TB issue

Cheers

P.S. - when I talk about “apps” I mean ONLY downloaded apps, and NOT system apps.

P.S. 2 - should anybody know how to tell TB to restore apps onto the original apps location (ext or /data partition) and not only to /data by default, pls let me know!!!
[Desire Android Development] suiller:
excellent Trinity :cool:
[Desire Android Development] trinity1:
thanks, buddy.

Listen, is the 0.6 in the repository the LATEST rel of your rom?

---------- Post added at 01:49 PM ---------- Previous post was at 01:05 PM ----------

I noticed that the media folder is structured as you can see here

the yellow folders are duplications and (as far as I can see) empty. Is there a reason to keep them?
[Desire Android Development] suiller:
1. I corrected some small things, pushing right now, available in 10 minutes

2. no I think we can remove safely, also because empty folders aren't replicated in /system
[Desire Android Development] trinity1:
BTW I successfully flashed your first release. everything fine. fast and fluid.

Having an ext4 still ready, I installed a2sd to see how it works. I'll give a feedback for those interested.

Like multiLing keyboard as well as the lite launcher, but I really miss T9 dialer...
[Desire Android Development] suiller:
1. well done, thank you for testing :cool:

2. about a2sd I suggest to don't move dalvik, move only app

3. multiling keyboard should have T9 (keep pressed 123 then choose a different layout)