yashsingh1/xdaforums huggingface dataset:
[Desire Android Development] malso:
I don't know why, but logcat doesn't give me an appropriate output. However,

dmesg does. I hope this can help to. For me it is just jibberish :)

So, I wiped:

data / factory reset -> /data /cache /sd-ext /sd-ext.something

cache & dalvic

formatted /system (but when flashing the ROM, system seems to be formatted again anyway)

plus created new partitions on the sd-card, first ext as ext4, skipped 2nd ext, wipe, an so on, as stated before.

I'm a bit scared of wiping /boot. Is it save? On which partition does the recovery

exist?

I'm sorry, I think I created some confusion.

So, before I flashed the first version from your ROM, 0.7 without a2sd script,

I was on MIUI with darktremor script.

I later tried, after following your tip and deleting the amarullz script from the

zip, to install darktremor again. My desire did boot, but as I said before,

a2sd was not working and the ROM was kind of laggy. So yeah, I wasn't either

able to have a complete running darktremor script with the slim ROM.

:confused:
[Desire Android Development] suiller:
no I mean /system not /boot, anyway was my fault because I forgot to mention that re-installing a rom always format /system so the problem is not here

Ok now I understand... hmm... just took a look at your log and ext4 is correctly mounted:

EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode.

just for curiosity... which brand & model is your sd-card? because I read somewhere about a2sd issues on certain cards, I hope isn't your case

you should push 40xxxx script under /etc/init.d & run manually & look what happens, at least for errors
[Desire Android Development] malso:
I just tried again, this time with fixing the permissions in recovery,

as it was mentioned somewhere in a troubleshoot.

But no change..I had to pull the battery after waiting for 30 minutes.

I did flash the amarullz script manually before, but there was

not notable difference.

I really appreciate your help. A lot!

But I think I will use your slim version without a2sd now for some time,

as this keeps distracting me from work more and more with every new

failed flash :D

Edit:

I've got a Toshiba, 16GB, class 4.
[Desire Android Development] suiller:
OK, I'll search for similarity and eventually will report... :cool:
[Desire Android Development] suiller:
updated 98myscriptI, I modded some priority & and I need your feedback

, here all seems to work but I need some more reports. thank you

for lazing people just redownload & flash over but I suggest to use the mini-sdk provided... it's faster :cool:
[Desire Android Development] suiller:
I told you... :cool: I made some benchmark tests and this is what I got (tested with Quadrant standard)

1st run

enabled ksm & zRam: 1786

disabled ksm & zRam: 1811

disabled ksm & zRam but enabled forcing 2D: 1828

then 2nd run

enabled ksm & zRam: 1705

disabled ksm & zRam: 1704

disabled ksm & zRam but enabled forcing 2D: 1798

both tests were made under same circumstances

so what is the response? the response is that ksm plus zRam don't produce any effect but if you insist you can enable them & give a chance to your "placebo" :D
[Desire Android Development] marcocsh:
Thanks for your work Suiller :)

Flashed your latest version over the old one with only cache wipe. Used it for 6 hours. Had 1 reboot when I use the facebook app just after flashing. No other problem spotted.

Cheers!
[Desire Android Development] suiller:
thank you for testing :cool:

I don't use facebook but many reported some issues with facebook app, so I suppose it's app fault... I read somewhere that there is an app that prevents facebook app to drain battery (I suppose by calming down its crazy polling)

anyway if you flash over a same version you don't need to wipe anything, just flash over ;)
[Desire Android Development] mrkaehler:
hi suiller, installed v0.8 after full wipe.

1GB ext4, 4ext touch, cm7r2 hboot.

looks great, everything I need is working (nothing around video tested).

But ... after regular shutdown my desire stay in the android-startscreen (for hours), after battery-pull it starts normal. I tryed this three times, one for 4ext-backup and two times after playing with fm spirit light (bluetooth died in indifferent state).

Regards Robert
[Desire Android Development] suiller:
publishing 0.8.1 with latest shaky kernel (don't remove from zip file the kernel folder or you wont appreciate new adreno libs)

as always if coming from an old slim release is enough to flash over

remember that latest amarullz script is included so

if you used a different a2sd script/setup remove, before flash and directly from zip file, the script 40xxx located under /etc/init.d

ps: under

dropbox mirror

is 100% uploaded, under official repository will take about 20 minutes to finish upload
[Desire Android Development] suiller:
hmm... seems related to a2sd, which one you use?

and for shutdown you mean completely turn-off not standby right?

I'll try both things (shutdown + spirit) & I'll report eventually ;)
[Desire Android Development] suiller:
just published 3 videos showing our old but brave desire running ics... search for "slim ics desire" :cool:
[Desire Android Development] mrkaehler:
just v0.8 installed with 1GB-ext4 on SD. I think amarullz managed this. I see over 760MB avail. on internal. And yes: this happens here only after complete turn-off.
[Desire Android Development] mrkaehler:
Add: spirit-bt-crash was my fault, used audio method "htc" instead of "qsd8250" and Bt=off.

Now on v0.8.1 :-)

... and the same procedure works :

backup via 4ext-control-app.
[Desire Android Development] abc001:
Is it possible to add theme manager/chooser in next version?
[Desire Android Development] suiller:
do you know apk name?
[Desire Android Development] suiller:
just tried to turn off completely & my device boot perfectly, have you tried again with your current setup? (I mean now that you use amarullz a2sd script)
[Desire Android Development] suiller:
found a issue in amarullz script, or better the script doesn't take care if ext partition exists or not

so if not exists any ext partition the script will continue its procedure but of course it badly fails (causing bootloop)

I implemented the script by adding a simple check at the beginning, if no ext partition is found the script will exit before messing up all things :D

as always is enough to reflash over (or pushing corrected script from adb), updated dropbox mirror is almost instantaneous for diaduit.bounceme.net just wait 20 minutes
[Desire Android Development] suiller:
some batt stat, during night consumption is very low
[Desire Android Development] marcocsh:
hey suiller,

Thanks for your work! Used your latest version for 8 hours now and no issue spotted. The rom is fast and stable. Just 1 reboot during Antutu bench marking.

p.s. got 2900 score in Antutu with a class 4 sdcard :)
[Desire Android Development] suiller:
oh very nice, in theory is possible to go little faster in benchmark but we will compromise stability, anyway on everyday usage difference isn't noticeable

ps: this morning I corrected an error in the 98mydesireI script
[Desire Android Development] suiller:
added on 1st page 3 videos... from fresh installation to game test, just sample videos

videos here 1/3 (installing) - 2/3 (average usage test) - 3/3 (game test)
[Desire Android Development] mikes69:
Hi All,

Thanks for a great ROM!

I installed the 0.8.1 dated today (21st) and get a bootloop. I installed the two other script updates mentioned above to check but they didn't seem to make a difference...

adb -d logcat during first boot gives me :-

D/dalvikvm( 755): Unable to process classpath element '/system/framework/framework.jar'
E/dalvikvm( 755): Could not stat dex cache directory '/data/dalvik-cache': No such file or directory
I/dalvikvm( 755): Unable to open or create cache for /system/framework/android.policy.jar (/data/dalvik-cache/system@framework@an
droid.policy.jar@classes.dex)

...repeated lots of times with 'VM aborting' as a result...

adb shell mount gives me :-

rootfs / rootfs rw,noatime,nodiratime 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,noatime,nodiratime 0 0
sysfs /sys sysfs rw,noatime,nodiratime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mtdblock3 /system yaffs2 rw,noatime,nodiratime 0 0
/dev/block/mtdblock5 /sd-ext yaffs2 rw,noatime,nodiratime 0 0
/dev/block/mtdblock4 /cache yaffs2 rw,noatime,nodiratime 0 0
/sys/kernel/debug /sys/kernel/debug debugfs rw,relatime 0 0

and also :-

adb shell ls -ld /data
drwxrwx--x system system 2012-05-21 15:14 data

adb shell ls -l /data
lrwxrwxrwx root root 2012-05-21 15:14 tombstones -> /dev/null
drwxr-xr-x system system 2012-05-21 15:14 user

adb shell ls -l /sd-ext
drwxrwx--x system system 2012-05-21 14:46 app
drwxrwx--x system system 2012-05-21 14:46 app-private
lrwxrwxrwx root root 2012-05-21 14:46 app_s -> /data/app_s
drwxrwx--x system system 2012-05-21 14:46 dalvik-cache
drwxrwx--x system system 2012-05-21 14:46 data
drwxrwxrwx root root 2012-05-21 14:46 data_s
drwxr-x--- root log 2012-05-21 14:46 dontpanic
drwxrwx--- drm drm 2012-05-21 14:46 drm
lrwxrwxrwx root root 2012-05-21 14:46 framework_s -> /data/framework_s
lrwxrwxrwx root root 2012-05-21 14:46 lib_s -> /data/lib_s
drwxr-x--x root root 2012-05-21 14:46 local
drwxrwx--- root root 2012-05-21 14:46 lost+found
drwxrwx--t system misc 2012-05-21 14:46 misc
drwx------ root root 2012-05-21 14:46 property
drwxrwx--x system system 2012-05-21 14:46 resource-cache

Anyway, no stress, don't need quick answer or anything - just FYI!

Let me know if there's anything else I can do. Was from a full Wipe, previously ran 0.6 without problems. No Ext partition on the SDCard.

Kind Regards,

Mike.
[Desire Android Development] suiller:
you don't need to flash separately amarullz script... the one included is corrected to avoid boot loops in absence of ext partition

if I understand well you flashed amarullz script from its thread?
[Desire Android Development] marcocsh:
I flashed over with your latest upload. I feel that the 3g data connection is not quite stable because I lost the data twice within 1 hour. Don't know what the problem is.:(

I will test again tomorrow. Gotta sleep now;)
[Desire Android Development] gie62001:
Same here :( 3g/HSDPA dropping quite frequently especially when opening maps, or sending receiving messages with Whatsapp and when changing wifi on/off.

followed Suillers advice in other thread as i thought maybe there's the same problem that other few people are experiencing with "parent" rom:

"from adb shell:

# setprop ro.ril.disable.power.collapse 1

plus

# setprop pm.sleep_mode 2

ps: ril power collapse carried troubles with GB rom too, so it's not an ics or this rom fault, in..."

but this didnt seem to help, at least for me,

Suiller what are default values as i would like to change them back just to see what difference do i get in connection drops. also tried looking maybe adb or shell commands could log radio or data connection but couldnt find.

also do these values affect battery usage? or its just new Shaky's kernel. (can achieve almost 100% deep sleep for hours but still drainage is about 1-2% evey 5 mins.

let me know if i could test anything (Fresh install after full wife including System partition).

worst case will try to reinstall again just to see what else can go wrong.

thank you and
[Desire Android Development] suiller:
about drop 3g connection issue it could depend by ril collapse method but it doesn't affect every user at the same way, so it should be also isp dependent

anyway setting ro.ril.disable.power.collapse as 1 could not solve issue, or better sometimes is not possible to change the value (even if you change it the value turn back as 0)

pm.sleep_mode instead means:

pm.sleep_mode=0 => Power Collapse Suspend

pm.sleep_mode=1 => Power Collapse (Provides best power savings)

pm.sleep_mode=2 => Apps Sleep

pm.sleep_mode=3 => Slow Clock and Wait for Interrupt

pm.sleep_mode=4 => Wait for Interrupt

pm.sleep_mode 2 will affect battery more than 0 or 1 but much much less than having a device looking constantly for active network :cool:
[Desire Android Development] suiller:
due to some issues reported about loop boot in absence of ext partition I'm testing all the stuff from scratch (wiping and without any ext partition)
[Desire Android Development] suiller:
corrected issue giving boot loop in absence of ext partition

ps: tried twice after full wipe, so it works! :cool:

as always re-download & reflash, or if you are brave enough extract amarullz script from current rom & push into yours ;)

DON'T FLASH .ZIP FROM AMARULLZ THREAD... IT'S NOT CORRECTED!!
[Desire Android Development] albertronic:
Installed with no ext partition and it worked ok so I guess you solved it (as usual :))

Thanks for your work!
[Desire Android Development] suiller:
perfect... thank you for testing :cool:
[Desire Android Development] deviantus:
I have 3g connection issue also :(

I'm waiting for the fix.
[Desire Android Development] marcocsh:
I re-flashed (over) and used for 8 hours. The data connection problem just vanish. Strange but it is working really.:rolleyes:
[Desire Android Development] suiller:
I forced sleep mode as 2 in latest ver published yesterday evening at 23.00, I want test how battery is influenced
[Desire Android Development] suiller:
did you installed ver published yesterday evening at 23.00?

if not try to flash latest ver than report data drop issues
[Desire Android Development] ShiftyBloke:
Just installed, so far so good. Really great work.

The only issue I had was when I messed something up :D
[Desire Android Development] marcocsh:
I unplug the phone for 1hr 30mins Listen music for 1hr and idle for 15mins.

Battery is now 77% left.
[Desire Android Development] marcocsh:
Hey suiller, after the last report, i stand by for 2 hrs and had a phone call using the speaker for 20mins. Now 60% battery left.

Governor: conservative

Min CPU 960

Max CPU 1075
[Desire Android Development] suiller:
UPDATED beta (from Sandvold 0.9)

as always download from official repository or dropbox mirror...

repository => http://diaduit.bounceme.net

dropbox mirror => http://www.dropbox.com/sh/8zl76aoewhgmcga/kcGljZD1vA/diaduit.bounceme.net (updated almost instantaneously)
[Desire Android Development] aardappel12:
Could I install this again without wiping? Sorry if it's a dumb question, but it appears to be quite important to wipe in Sandvold's own 'fat' version :p

Again sorry if it's a dumb question!
[Desire Android Development] suiller:
yep sure, mainly because framework isn't changed and because /system will be formatted (/data instead will be preserved without loosing personal settings) :cool:
[Desire Android Development] aardappel12:
Alrighty then! Flashing over as we speak :)

Thanks to you, sandvold and shaky for all the hard work you've put into this awesome rom! Works great & lovin' it! :)
[Desire Android Development] papa-luigi:
Hi!

How can i avoid running the amarullz script while installing?

I have a ext4 partition - but i don't want to extend the datastore with that partition...

i simply want the "slim" version!

tnx for your help!

luigi
[Desire Android Development] suiller:
open rom .zip (with 7z for ex) and remove under /system/etc/init.d the amarullz script (40xxx) then close & flash as usual ;)
[Desire Android Development] ivanoscar:
I try to install your rom but after the installation don't run I have only write on the screen android.

Could you help me.

Thanks

ivan
[Desire Android Development] suiller:
probably you got & bootloop but I need some more info... almost impossible helping you with no info...

for ex you could tell me:

1. if use ext partition, if yes specify with which mode (3 or 4) and if was previously populated with another data2sd script

2. recovery version (this rom is tested by myself with latest clockwork notouch 2.3.1 & touch version 1.0.53)

3. did you manipulated .zip rom file? (I mean if you have removed or added something else)

4. did you flash something after rom (I mean another kernel different from the one included or whatever)

5. have you tried also, just to be sure, after a full wipe (data + cache + dalvik + ext partition)
[Desire Android Development] ivanoscar:
I have revolutionary and then I use clockworkmod recovery v5.0.2.0.

Now i made wipe dalvik cashe, than pardition sd card 512mb.

Rebut recovery and than I install your rom.

After done this nothing change. what can i do ? Now don't work.

thanks
[Desire Android Development] suiller:
try with another recovery, try with a simple one like this:

http://diaduit.bounceme.net/recovery-4EXTRecovery_v2.1.3_bravo.zip

if it works than you can also upgrade

anyway I never used clockwork (just 4ext), perhaps it doesn't align correctly the ext partition (I imagine of course... I'm not sure)

EDIT: just in case re-download completely the .zip rom file
[Desire Android Development] ivanoscar:
I try to install recovery-4EXTRecovery_v2.1.3_bravo but say installation aborted.

I use button on/off and the volume down and the open revolutionary tha I used revovery and after I use install zip from sdcard. is it possible to in other mode ?

Thanks

ivan
[Desire Android Development] suiller:
You have to install from adb... download always from repository the mini-sdk... it will do it for you ;)
[Desire Android Development] rafiek:
My WiFi is not working.

In the setting where I turn it on it says Wi-Fi enabling (inschakelen), then nothing happens. I do not get a list of SSID

Am I doing something wrong?

tnx

Rafiek
[Desire Android Development] fragargon:
hi,

got the same issue, check system partition... almost full, make room

df -h from recovery (only system mounted)

df -h

Filesystem Size Used Available Use% Mounted on

tmpfs 203.2M 32.0K 203.2M 0% /dev

/dev/block/mtdblock4 5.0M 1.6M 3.4M 31% /cache

/dev/block/mtdblock3 145.0M 144.9M 68.0K 100% /system

removed music2.apk (5mb) and replace by appolon (376 Ko)

http://www.seeingpixels.org/2012/05/apollo.html

reflashed rom this should fix the wifi problem (failed load driver)

hope this help

:)
[Desire Android Development] suiller:
Strange I started from scratch and I have still 4mb free under /system
[Desire Android Development] mrkaehler:
Same here. I installed over the slim v0.8.1 without wipe.

Pulling the battery and start again solve this for me.

hboot: cm7r2, 1Gb ext4

Desire on slim ics v0.9
[Desire Android Development] suiller:
please can you confirm your setup? did you modded /system inside .zip file? because I tried twice & all work correctly, also because the kernel dump image instruction is equal (literary speaking) to the old one (0.8.1)

EDIT:

this is mine df output... after fresh installation

~ # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 203.2M 32.0K 203.2M 0% /dev
/dev/block/mtdblock4 5.0M 800.0K 4.2M 16% /cache
/dev/block/mtdblock3 145.0M 141.9M 3.1M 98% /system

which recovery are you using?

EDIT2: hmm... could it happen due to some bad sectors (skipped by OS) in mtdblock3?
[Desire Android Development] fragargon:
Wells, i start from scratch, did not changed anything.

Yep this could be due to bad sectors skip by system...

Since removed music apk and reinstalled everything, it s running fine... amarulz a2sd.

More detail o. My setup see sig except kernel... shaky: )
[Desire Android Development] suiller:
so you have substituted kernel folder in the .zip?

ps: shaky kernel is yet included...
[Desire Android Development] suiller:
updated latest 0.9, I re-introduced latest beta adreno libs from Shaky, I (again) tested them for a whole day without a single issue... I think they are mature enough for everyday usage :cool:

as always download from repository or dropbox mirror
[Desire Android Development] mrkaehler:
updatet act. v0.9 (over v0.9) without wipe.

same frozen "android" screen ... try to add logcat ...

Edit: As always - solved by taking out battery ...
[Desire Android Development] suiller:
thank you for providing log... I found the issue, at least in your device, but I don't understand why it acts in this way...

java.io.IOException: Couldn't create directory /data/system

at then end it crashes here (as expected):

W/InputManagerService( 7008): Couldn't create dir.: /data/system/inputmethod

but it's really strange, just to be sure I need your df output... it isn't an out of space issue, seems a permission issue

sorry but I don't remember if you use data2sd script & if yes which one, thank you
[Desire Android Development] suiller:
IMPORTANT, who has troubles upon fresh install (bootloop) is pleased to post here his recovery logcat...

from adb (or mini-sdk): adb pull /cache/recovery/last_log

zip it & post here, so I can understand the reason why you get a bootloop, thank you :cool:
[Desire Android Development] rafiek:
WiFi not working

I don't know how to check my df -h

but this is the info from 4ext (1.0.0.3 beta 6)

-------------------------------------------------

Partition | fs | size | free

sd-ext ext4 1025 MiB 971.1 MB

sd-card fat32 6307 MiB 6.1 GB

swap swap 257 MiB

current rom : Desire Beta 0.9

--------------------------------------------------

I installed from scratch and did not modified the zip file.

thanks rafiek
[Desire Android Development] suiller:
some for sure had many bad sectors, so effectively free space is less than reported, look for ex my recovery log:

1_5 formatting system
mtd: not erasing bad block at 0x00960000
mtd: not erasing bad block at 0x08140000

our /system has a margin of few Mb (about 3) so for heavily damaged nand these 3 poor Mb could be not enough

let me make some experiments perhaps I can solve...
[Desire Android Development] suiller:
:eek:

you don't need at all a swap partition... we don't have any "spin" drive but just nand, save those 257Mb!! :D
[Desire Android Development] suiller:
UPDATE: removed kernel folder, now shaky is the default one, also because the original isn't used anymore by Sandvold too :rolleyes:

we saved a couple of Mb during flashing process :cool:
[Desire Android Development] mrkaehler:
Hm "df -h" is not right for my phone:

Filesystem Size Used Free Blksize
-h: No such file or directory

But "df" says:

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
/mnt/sdcard 28G 15G 13G 32768
/mnt/secure/asec 28G 15G 13G 32768
/mnt/asec/com.aldiko.android-2 16M 14M 1M 4096
/mnt/asec/com.svox.classic.langpack.deu_deu_fem-1 2M 264K 1M 4096

Remember: Started with empty (full wiped) phone + Kingston-32GB-card (31GB fat32 + 1GB ext4(wiped))

-installed your v0.8

-installed your v0.8.1 without any wipe

-installed your v0.9 with dalvik cache wipe only

Never called or installed any script "by hand" but I have 1GB "internal memory" Apps=363MB Free=753MB, this is done by amarullz automatically - right?

With v0.8 and v0.9 it don't boot after real shutdown (verry cold boot), battery pull solved this. (With v0.8.1 I can't reproduce this)

One point: during shutdown I see "You can now remove the SD-card" (in german) just before switch off.

I think there is something with mounting the ext4-partition (timing or so?)...

Regards

Robert from Berlin
[Desire Android Development] suiller:
yep sorry... without -h (busybox is busybox :D )

all seems OK here

yep

this is normal... to avoid data corruption OS umount sd-ext before shutdown (nand isn't reported also because is faster)

could be... let me think... I added this line in amarullz script to avoid starting /data copying procedure without an active (& ready) ext4:

busybox mount -t ext4 -o errors=continue,noatime,nodiratime,nosuid,nodev /dev/block/mmcblk0p2 /sd-ext || exit 69;

then soon

#-- Unmount /sd-ext if it already mounted
busybox umount /sd-ext;

I can try to retard 1 sec before dismount & then remount...

EDIT: try with attached zip, open it and push in your .rom zip under /system/etc/init.d, then reflash... let's see what happens