yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] Effdee:
I'll have to remember how to do the sums, but I don't think the oc makes all that much difference to power

besides stock is terrible with battery

I've flashed some of the old school roms like king and cannon

but I didn't really pay all that much attention to battery drain

from my reading it all started around cm5 and cm6

so something happened between 2.6.34 and 2.6.35

maybe I will reflash 1.33.2005 and use an old rom as a benchmark

however it does raise a question

is it directly related to the kernel?
[G1 Android Development] AndDiSa:
Yes, that's true ADS_magpie is based on Terry's ezGingerbread and if I am requested by Terry to open a different thread to discuss ADS_magpie, I will do so. I am not sure if such a split up into different threads would be really a good idea, because this rom is very closely related to ezGingerbread. There are principally only three extensions which I integrated, into Terry's rom:

- a2sdext (in my opinion a must for G1, otherwise it's alsmost unuseable), here I integrated Firerat's magpie, who already did the work to integrate a2sdext into ezGingerbread

- e2fsck, because it was missing and is needed when you want to mount securely ext2/ext3/ext4 filesystems

- compcache support (which in my opinion is a must have, too, because of the big number of background services starting up on Gingerbread)

All these modifications can be found on Github.
[G1 Android Development] sb56637:
I've been running ADS_Magpie for quite a while now, and I really like it. However, I just got hit bad by the battery drain bug on the 20110319 build. I charged it to about 93%, and disconnected it while it was still booted up. I don't even use it as a cellphone, so it was in airplane mode with all transceivers turned off. And it was in standby. About 12 hours later it shut off, completely dead battery. Normally this phone with ADS_Magpie will sit for a week in standby without even using much battery at all.

Just wanted to report this. Thanks again for the nice ROM!
[G1 Android Development] AndDiSa:
I noticed a high battery drain some days ago, too, especially when using 3G networks. Almost at the same time I noticed that there were exceptions related to this gralloc / out of recources error in the logcat, too. I am wondering if there might be a relation ...
[G1 Android Development] muldy:
Aparently reverting this:

http://android.git.kernel.org/?p=pl...ff;h=68d3478860fecc9b8fbf256796a832a037434555

"fixes" the

"out of memory error on surface flinger"

Anyone tried this?
[G1 Android Development] AndDiSa:
These patches are already included in the sources, but nevertheless thank you for the hint.

I tried also to merge the patches from 15/17 March. I noticed a little improvement in that way, that sometimes I got the black screen, the exceptions were thrown in the logcat, but using for example the back-button I could continue to use the phone.
[G1 Android Development] hrk:
I'm not a kernel developer, but the patch doesn't look like a culprit to me. it looks like there's a missing "free" (not the function itself) somewhere, so the enforcement of "no more references" of the patch doesn't allow layers to be removed and in the end the memory is never recalled.

BTW, a couple of days ago I could "successfully" trigger the /dev/pmem exaustion in around three hours (!) from a reboot, by switching between GMail and Calendar doing copy/paste of some texts. Not the only thing that I did, but I never do it and... three hours?!?! :)
[G1 Android Development] AndDiSa:
It's not in the kernel, but the OS ;)

I am thinking, too, that a reference is not freed correctly, but problem is to find where. The patches from the 15/17 of March corrected some bugs in accessing / freeing wrong elements within the list of allocated resources / caches, but it seems that it was not the root of the cause ...
[G1 Android Development] d3vilskid:
So using farm kernel for a lil bit now, here is my batt usage. 9 hrs and 27 min batt is at 94 %. No cc, jit and did not reboot when unplugging usb.
[G1 Android Development] muldy:
Yes the source has this patch...

But the suggestion is to revert the patch :)

I think the bug is from a aggressive garbage collection on surfaces? or something :)

And yes, using you phone more, will make it happen sooner.
[G1 Android Development] hrk:
LOL I got one of these.

I know it's a needle in a big haystack but... I'd check the new copy/paste markers introduced in GB.

True, friend, true, but I didn't use it like crazy, I just switched back and forth w/ gmail and calendar doing copy/paste around.... 10 times? I'd hardly call it "using your phone more". :-) Indeed, I used my phone way less than I normally do.
[G1 Android Development] Effdee:
Awesome!

lets call it 10hrs and 90% battery left and we can extrapolate that to 90hrs

just to make sure we are not being too silly , half that to get 45hrs

are you certain your numbers are right?
[G1 Android Development] bi0hzr:
with the first andisa odex rom i get 42 hours w/o charging, and i have a 1150mhA batery

better than ever, but i still prefere froyo for many reasons.

ginger its being exelent, just a few things to inprove and it will be done!

thx for this exelent work.

sry if i spell something wrong
[G1 Android Development] d3vilskid:
Effdee: haha yea all this with no use or minimal usage, really testing it on standby. Been using the phone quite a bit in the last couple hrs and finally got down to red or 7%.

So the good news for me now is that if I lose my phone around the house, I don't have to worry bout it dying in like an hr or 2.
[G1 Android Development] {davros}:
Nice write up gonna start building on my g1 also. I've been doing Moto Droid custom froyo and gb roms for awhile now.
[G1 Android Development] crypticc:
Confirmed working on magic 32b. Including wifi which previously wouldn't start. will update on battery life later after a quick cal. Cheers.

Update: Sorry would've said the frankenstein kernel
[G1 Android Development] AndDiSa:
I've reverted the patch in the latest ADS_magpie build, so you can test. Actually it's running fine, probably we need to do some stress tests ... (should become the word of the year ;))
[G1 Android Development] muldy:
I'm running reverted too

no more:

"out of memory error on surface flinger"

but in less than 20h got a soft reset to android animation... :(

For me its better than blanck screens... but still a no go

PS: Got no black screens...
[G1 Android Development] muldy:
It appears there is a upstream fix from google:

http://code.google.com/p/android/issues/detail?id=15135#c39

-- testing --
[G1 Android Development] roalex:
It looks like the commit its already on the CM tree.
[G1 Android Development] AndDiSa:
ezTerry merged it, too. We will see, wether it was really the reason for these out of memory errors.
[G1 Android Development] roalex:
Yup, so anybody noticing any improvements ?:D
[G1 Android Development] AndDiSa:
It's running fine ... at least I was not able to provocate the error up to now, but I am running the ROM only for half a day now.
[G1 Android Development] roccoadam32:
anyone try out swap on this?
[G1 Android Development] AndDiSa:
Why do you want to use swap? Swap in my eyes is worse than compcache. Either use compcache with a very low swappiness, or run without anything.

At the first moment swap might help you, but when it comes to swaping, the performance is going down rapidly. Just my 2 cents.
[G1 Android Development] roccoadam32:
there is not enough free ram on this and compache slows down over time swap has been running very good for me on foyo did not slow down a bit usually i disable to onscreen keyboard for more ram but on this i get force closes if i do that
[G1 Android Development] AndDiSa:
With the +14MB hack and compcache set to 20% it runs very smoothly. If you want to use swap, you could try to use Firerat's AIO script. It should work, but I did not use it up to now. But be sure to switch off compcache.
[G1 Android Development] dekans:
I did a couple of builds of ezGingerBread.

But 90% of the time (and 100% of my today tries) I get a n"o rule for otapackage" error.

How to resolve this ? The repo is synchronized.
[G1 Android Development] ezterry:
Um.. quite sure you missed a step or are running make from the wrong location.. but we will need more information to help
[G1 Android Development] dekans:
I'm in the right folder.

I cleaned the all directory, and refetched the source to get sure.

But even this way, with a fresh project, i get the same error "no target found for 'otapackage'".

Do you think it can be caused by the use of OpenJDK 6 instead of sun JDK 6 ?
[G1 Android Development] AndDiSa:
I don't think, that it's the JDK, because the error message says something different. Normally you should do (always from the same directory):

- repo sync

- . build/envsetup.sh

- lunch (you should select the option 3 there)

- make -j2 otapackage

Then you should be able to build everything.
[G1 Android Development] dekans:
it's exactly what I do, but the 'otapackage' rule is still not found.

I will try again later.

PS : With the Cyanogenmod or AOSP source I don't have this issue.
[G1 Android Development] :
apps 2 sd can be added by flashing this: http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip

(tested and working)

and options can be controlled with this: http://xdaforums.com/showthread.php?p=12069632#post12069632
[G1 Android Development] AndDiSa:
For what is it needed? The ADS_Magpie-builds do have included a fully functional a2sdext implementation (plus options to move them to internal storage or sdcard).
[G1 Android Development] azrash:
is it possible to choose which app to be moved to ext or forcing certain apps to be in internal? thanks!
[G1 Android Development] AndDiSa:
You can define the default location for installation, but for each application in addition you can move it around between the three differen locations, as you want (certainly only within certain limits, i.e. private / non-private, etc. as defined by the application itself).
[G1 Android Development] hrk:
Latest ADS build

Plugged and unplugged numerous times after first flash of the latest ADS (Apr 2nd).

It never lasted this long on me! (Well, maybe it did once... this is the second time!)

2G only, GPS ON

WiFi OFF, BT OFF.

interactive@128/614 w/ NoFrills.

Normal usage (except that the first 12 hours I didn't use it very much).

L.
[G1 Android Development] bestofrhcp:
hey ezterry, can you make a flashable zip for the kernel used for the latest build, its that awesome! can you please?
[G1 Android Development] ezterry:
Um.. all of my recent builds are still using exp20110109:

If you are intending to use it on a froyo build.. the bugs in this CM nightly based kernel may make the biff testing 20110222 kernel (link on op of kernel corner) more interesting..

I'm currently working on a 2.6.36.4 build merging most of the bug fixes out there.. (see my github for progress) .. once I make this bug free ish I can look into moving to 2.6.27 and beyond.
[G1 Android Development] bestofrhcp:
oh ok thanks alot, i guess i skipped it, for a second i thought it was a .11 build so i was impressed, but then i found out it was .10 build, makes sense haha. thanks for the link, and im looking foward to the 2.6.36.4 build :D
[G1 Android Development] Effdee:
:confused: why would you add another busybox when the one built in is better anyway?

and bash :confused: 2.5 mb just to make some symlinks?

and why not just use fr aio a2sd ? it lets you decide if you want app on internal or sd-ext

10s of kb instead of several mb and you only need to run it once not flash it every install

if you ask me that dtapps2d is a poor way to add apps2sd

and like AndDiSa says just use his magpie version
[G1 Android Development] :
Omfg, do you really have to troll my every post... I know there are other options, I didn't read the entire thread, but I like using darktremor a2sd method (although you may disagree). I've used the fr a2sd script before, but I just used dark tremor to test out the new A2SD GUI app.
[G1 Android Development] Effdee:
seeing as ADS_Magpie is better, I thought I would point it out

I have had a closer look at this dark tremor and it is even worse than I thought it was at first glance

many of the scripts are just copies of the same script

My advice is use ADS Magpie if you want a2sd

use fr a2sd if you can't or don't want to use ADS Magpie

seriously it's less than half the size of one of the duplicate scripts in darktremor

but if you want to add dark tremor to your rom fine, you do that I'll just facepalm and wonder if you will make a better rom some day
[G1 Android Development] :
Don't worry, I will. Sorry for overreacting a bit, I will look into ADS_Magpie..

One thing why I used DarkTremor was to use the A2SD GUI app that allowed to change swapinness and jit, on a stock rom.
[G1 Android Development] Effdee:
well jit control is in CMParts doubt it would take much to port that

adding swappiness should also be trivial

myself I don't find swap works very well and prefer not to use it

but setting up swap and swappiness is easily done with a script, and a rooted rom without busybox is like a Swiss Soldier without their famous pocket knife. So I don't see the point in adding a duplicate.

And bash is a little ott I'm sure sh is more than capable of setting up symlinks

besides the completely different scripting styles (at least we know they don't just copy each other) the distinct difference between fr and dt scripts is fr uses mount -o bind and dt uses symlinks

in dt if a symlink is dangling it will just bootloop, but because fr tests and makes the bind mounts it won't bootloop

even if it didn't have this safety feature imo fr's is far superior due to its size. After all, we want to use a2sd because of the lack of space, having all of those duplicate scripts, an extra busybox and bash is a poor show.

but like I said the choice of 5mb :eek: of wasted space is yours to make.
[G1 Android Development] creezalird:
Andisa, I just started using your ADS_gingerbread the 02042011 ones.

So far I can say it is very much working although sometimes it is quite hard to do multitasking, but I can live with that.

My question is what is this file "ADS_gb_patches-signed.zip" ? Do I need to flash that one too? And in future if u release new version, do I need to do full wipe or just flash over?

Danke schön :)
[G1 Android Development] AndDiSa:
There is not need to flash the ADS_gb_patches.zip. When there is a new version, a non wiping update should be fine, until I state different.
[G1 Android Development] creezalird:
okay..thank you so much..:D
[G1 Android Development] tcorless:
ADS_Magpie on TMobile MyTouch 3G orig 32b

I have been running ADS_Magpie on a G1 for awhile now and it is great! I just inherited a MyTouch 3G orig 32b and rooted it. I install the odexed version and it ran fine. I just tried the latest version 0402 and it stops at the boot animation screen. Looking at the logcat I see a permission denied error during DexInv, any idea how to fix it?

SAPPHIRE PVT 32B SHIP S-ON G

HBOOT: 1.33.0013D (SAPP30000)

CLPD-10

RADIO: 2.22.28.25

pastebin.com/mYf4CMbd

(Sorry, I can't post outside links yet.)

Edit: I did do a wipe of everything, here are the directory outputs, I also included df output:

C:\Program Files\Android\android-sdk\platform-tools>adb shell ls -l /
drwxr-xr-x 3 root root 0 Apr 5 19:26 acct
drwxrwx--- 1 system cache 2048 Apr 5 19:26 cache
dr-x------ 2 root root 0 Apr 5 19:26 config
lrwxrwxrwx 1 root root 17 Apr 5 19:26 d -> /sys/kernel/debug
drwxrwx--x 1 system system 2048 Apr 5 19:28 data
-rw-r--r-- 1 root root 118 Jan 1 1970 default.prop
drwxr-xr-x 13 root root 1200 Apr 5 19:26 dev
lrwxrwxrwx 1 root root 11 Apr 5 19:26 etc -> /system/etc
-rwxr-x--- 1 root root 94172 Jan 1 1970 init
-rwxr-x--- 1 root root 1677 Jan 1 1970 init.goldfish.rc
-rwxr-x--- 1 root root 14426 Jan 1 1970 init.rc
-rwxr-x--- 1 root root 2967 Jan 1 1970 init.sapphire.rc
-rwxr-x--- 1 root root 2967 Jan 1 1970 init.trout.rc
drwxrwxr-x 6 root system 0 Apr 5 19:26 mnt
dr-xr-xr-x 83 root root 0 Jan 1 1970 proc
drwx------ 2 root root 0 Jan 9 13:30 root
drwxr-x--- 2 root root 0 Jan 1 1970 sbin
drwxrwx--x 6 system system 4096 Apr 5 19:26 sd-ext
lrwxrwxrwx 1 root root 11 Apr 5 19:26 sdcard -> /mnt/sdcard
drwxr-xr-x 13 root root 0 Apr 5 19:26 sys
drwxr-xr-x 1 root root 2048 Apr 5 19:26 system
-rw-r--r-- 1 root root 0 Jan 1 1970 ueventd.goldfish.rc
-rw-r--r-- 1 root root 3764 Jan 1 1970 ueventd.rc
lrwxrwxrwx 1 root root 14 Apr 5 19:26 vendor -> /system/vendor

C:\Program Files\Android\android-sdk\platform-tools>adb shell ls -l /cache
drwxrwx--x 1 system system 2048 Apr 5 19:28 dalvik-cache
drwxrwx--- 1 root root 2048 Apr 5 19:26 lost+found
drwxrwx--- 1 system cache 2048 Apr 5 19:21 recovery

C:\Program Files\Android\android-sdk\platform-tools>adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 56416 32 56384 0% /dev
tmpfs 56416 0 56416 0% /mnt/asec
tmpfs 56416 0 56416 0% /mnt/obb
/dev/block/mtdblock3 92160 71268 20892 77% /system
/dev/block/mtdblock5 302848 3480 299368 1% /data
/dev/block/mtdblock4 81920 17148 64772 21% /cache
/dev/block/loop0 896 896 0 100% /system/lib/modules
/dev/block/loop1 2560 2560 0 100% /system/fonts
/dev/block/mmcblk0p2 516040 16780 473048 3% /sd-ext
[G1 Android Development] AndDiSa:
I am not completely sure, what's the reason. It is a problem with /cache/dalvik-cache, which seems not mounted correctly resp. where isn't enough space available to hold the dex-files. Somebody (I do not remember exactly who it was), reported already the same problem.

The odexed versions are running, because no additional space is needed, while the non-odexed versions create new dex files. I would expect, that those dex files go to on /data/dalvik-cache on first boot, but in your log I can see, that they are written to /cache/dalvik-cache :confused:

If there is not enough space available for the dex-files, you will get those errors. I don't know, if you cleaned dalvik-caches / did a wipe before installation. If not, you could try that. Unfortunately I don't have a MT3G here, so it's only hypotheses. Probably someone else with an MT3G running ADS_Magpie can support here ...

Edit: can you pls check persissions of /cache and /cache/dalvik-cache? Even if stuck on boot screen you can connect to the phone by adb. So you can do an

adb shell ls -l /

and

adb shell ls -l /cache
[G1 Android Development] AndDiSa:
On ADS_Magpie JIT-, vm-heap-size- and compcache-size-controls actually are located in SpareParts. Swappiness actually is set to 10, fixed, but as Effdee already stated, it's very easy to add also a control for that.
[G1 Android Development] AndDiSa:
Unfortunately it's not fixed completely ...

Today I've got the gralloc / out of memory error again. There is an improvement, because I could continue to use the phone for a while, but now I am stuck on on lockscreen and I have to reboot :(
[G1 Android Development] muldy:
:(

Sad to ear that.

That's a show stopper for me.

I'll just wait for a fix. I'm using ezterry's amazing AOSP 2.2 OTA ROM meanwhile, and it runs like a baby :) - Good stable ROM.

I'll wait for a real fix.

Btw. I have the same problem with your roms AndDiSa, i get stuck on the boot animation... Haven't checked the logcat yet...
[G1 Android Development] creezalird:
How can I triggered the gralloc thingy? Or it is just happened after a day or two of usages? Because so far I've still not encountered it. Maybe tomorrow..:(:(
[G1 Android Development] muldy:
I think apps using a log of graphic resources can lead to gralloc fails.

I would say gallery 3d? Maps?

I can't reproduce it.

For me it's usually after 20h uptime.
[G1 Android Development] creezalird:
I see..then I shall wait till about 16hours more..and maybe playing around with gallery3d and maps..thanks for the info
[G1 Android Development] hrk:
LOL I wanted to post it this morning, when I found out. :) I guess I had around 36 hours of uptime when it occurred, but I was affected in a minimal way: XDA app would keep on the spinning screen, but everything else worked (especially aLogcat) and I rebooted. Looks like I could use some copy/paste between gmail and calendar to check if it goes off sooner...
[G1 Android Development] muldy:
Usually when it happens it affects all apps includding launcher. And in my experience once it happens the only solution is to reboot.

I think the millage before it happens may vary.
[G1 Android Development] AndDiSa:
For me now it was after about 60h uptime. I'll try redo the modifications you suggested about one week ago. Probably this will help, I would like to test it a bit more, because I removed the modifications from the sources when the "official" patch came up.

Edit: new versions (odexed and non-odexed) uploaded and can be tested ;)
[G1 Android Development] muldy:
I just flashed (clean wipe)

ADS_magpie-20110405

and got stuck on the boot animation

here's the bug report :)

odexed booted ok, but the googlesign app force closed... and could not get out of the loop
[G1 Android Development] creezalird:
I think I just got bootlooped too..right now trying to reflash evryhing
[G1 Android Development] Effdee:
try making /cache/dalvik-cache with adb shell

adb shell install -o 1000 -g 2001 -m 770 -d /cache/dalvik-cache
[G1 Android Development] AndDiSa:
Probably I should integrate this into the 06BindCache - script for the case, that people are not using MTD and cache size is >= 27MB.
[G1 Android Development] creezalird:
I'm using customMTD with mtd 90 2

About few hours ago, I tried upgrading to your latest 0504 version.

First boot I have the lockscreen, but after unlocked, only black screen. So i decided to reboot, and then got caught in the bootloop.

Right now I've nandroided back to previous version
[G1 Android Development] muldy:
I'm not using mtd :)
[G1 Android Development] AndDiSa:
Thanks for the directory listings. I think I've found the reason: /cache has 770 permissions and is owned by system/cache. For me it should be 771, because otherwise applications other than system cannot write into / read from that directory.

To resolve that problem, the following should help:

Boot into recovery mode and connect the phone by USB. Then type on the PC

adb shell mount -o rw /system
adb shell chmod 771 /cache
adb shell reboot

Edit: I am wondering why this is happening only on HTC Magic and not on G1 :confused:

Edit2: The first line should mount /, but nevertheless it will not work ...
[G1 Android Development] AndDiSa:
... without logcat it's a bit difficult to understand what's happening, but probably its the same reason as for tcorless.
[G1 Android Development] wjsturgis3:
Works like a champ, Thanks Firerat.
[G1 Android Development] Firerat:
ok, kewl

so in the short term need a fisrtboot.sh script to make sure dir are setup

been looking at some of the code, and it _should_ be creating the required

but , tbh I was looking at something else, so it might be broken , idk

anyway, I've just compiled with a chunk of Magpie

will play around for a couple of hours and see what needs putting into the build

ooops , typos

kin ;s, I always manage to miss one somewhere :)

Edit:

wouldn't it be great if when the compiler expects something to be some place it sticks it in for you

after all it wasn't wrong
[G1 Android Development] sparksco:
Do you have a github yet? lol, I'm compiling this right after I finish syncing to cyanogenmods repo. Not sure how much help I can be but I'll do my best :D
[G1 Android Development] tnpapadakos:
http://review.cyanogenmod.com/#change,1765

wtf does this really mean...
[G1 Android Development] Firerat:
errm

yeah

but I havn't push anything gb to it yet

well, I did create an initial repo for GB stuff, but will probably drop that and add more ( to keep the names uniform )

https://github.com/Firerat