yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] crypticc:
I did with mixed results. It works but streaming doesn't work, which isn't unusual. What is, is that local files are "streamed" via jumper service which is as big as apk and gets kicked out sometimes. Search my posts
[G1 Android Development] Nico013:
ADS_MAGPIE

Hello,

Sorry for my bad English, but I'm french.

So, I would like to try the last MAGPIE rom's but when I install this, I can't use it because my screen are freeze on boot-animation.

I post logcat View attachment ADS_magpie-20110316.zip

If anyone can help me please...

Thanks

My phone is :

HTC SAPPHIRE 32b

Radio: 2.22.28.25

SPL: 1.33.0013d
[G1 Android Development] ZilverZurfarn:
Did you wipe thoroughly before flashing? I recommend SuperWipe.
[G1 Android Development] AndDiSa:
Looks to me that your cache partition is not bind mounted to /sd-ext, but dex files are written to /cache

you can try to add the following line to build.prop

dalvik.vm.dexopt-data-only=1

or you can try to use the version from 20110313.

Edit: and please check, that there are no additional scripts in /data/userinit.d or /sd-ext/userint.d
[G1 Android Development] Nico013:
For ZilverZurfarn, yes I use superwipe by OSAKA.

For AndDiSa I forget to tell you: I use swap partition 96Mb an ext4 512Mb

If I use adb shell, can I try this: dalvik.vm.dexopt-data-only=1?

And tks a lot for your help:)
[G1 Android Development] dillalade:
Yo Peeps,

I was here a long time ago - seems like your all making progress.

However has SMS send/retrieve issue been resolved yet?

I need this to function before I think to return here to test.

Cheers
[G1 Android Development] hrk:
After the latest changes from Terry and AnDiSa I haven't lost an SMS. Today, though, it looked liked I lost one (... and one I shouldn't have lost...) so I got pretty "F-Google!" "F-Android!" but when I rebooted, the SMS notification appeared and the SMS was there, so... I dunno.

Anyway, I made this quick-hackish-workaround: the app will listen for SMS messages and save them in a db (stored in data). In the activity you get a list of saved message, touch one and you can choose between "Move to INBOX" and "Delete". Guess what happens then? ;-)

Gonna call it "No-frills Hack For Lost SMS in Gingerbread"...

EDIT: published on the market. XDA thread here
[G1 Android Development] jdb78:
Just curious:how can your app receive SMS when the mms app can't? What does your app do? BTW I lose a whole bunch of messages...
[G1 Android Development] hrk:
From what I've witnessed with my phone, the MMS app does indeed receive the messages, but it dies before writing them in its database.

As I wrote, my app simply reacts on incoming messages, stores them "quickly" in its database, then shows the notification (so that you can know that something was received). Nothing more, nothing less. Let me know if you use it and it helps you.
[G1 Android Development] jdb78:
Already installed it and this morning I had a notification - but the mms app did receive the message as well. So I'll test and report my experience :)

My wife was kind of pissed because she wrote three messages a couple days ago asking me stuff to do and I just did not receive them... "Yeah great phone you got, are not able to make calls and receive sms but are online 24/7- go buy yourself a good phone without that crappy internet stuff" ;-)
[G1 Android Development] ggonsalv:
and I thought I was alone in my misery!
[G1 Android Development] Nico013:
ADS

Hello,

I tried this code but I have the same probleme with rom 03-13-2011 to 03-16-2011.

dalvik.vm.dexopt-data-only=1

But tonight I tried the last rom and she run very well, so???

Many thks for anybody work on the rom, very good work and good luck...
[G1 Android Development] AndDiSa:
There is no difference in functionality / configuration, but todays build is odexed, i.e. you need no/less memory in dalvik-cache for system apps.

In your log I could see, that on your phone dalivik-cache will be written to /cache, but it should go to /data. It seems, that your /cache partition is too small to hold the system odex files and that leads to your boot problems. The odexed version for you is working, because there are no odex files written to /cache and so your phone boots. :)
[G1 Android Development] AndDiSa:
You could try pershoots 2.6.35.11 kernel. I was playing around with it the last days and my impression was that I had always 3-4MB more memory free compared to ezTerry's standard kernel.
[G1 Android Development] jdb78:
Thx! I'll try tomorrow, no access to a PC today.
[G1 Android Development] d3vilskid:
odex

loving the odex, seems more reliable. hope to be seeing more of them in later builds.
[G1 Android Development] SubVert:
Using the odexed version and it seems to have broken Speech.

I have espeak installed, and have a task in Tasker that speaks a phrase. It worked fine until I installed the odex version. Now I get a tts failed to initialize message, and going to Settings - Voice input & output - Text-to-speech settings just brings a force close.

Not a big deal for me, just for information.

Also, I still have no Sd-ext in Preferred Install Location.

I ran a boot logcat, didn't seem to show any problems, I can repeat it and post if it might help.

SubVert
[G1 Android Development] jdb78:
See the changelog:
[G1 Android Development] konnspiracy:
About how much free ram do yall have after its all set up?
[G1 Android Development] AndDiSa:
Did you clean the dalvik-caches? Is your /sd-ext partition mounted?
[G1 Android Development] Effdee:
flashed ADS and can confirm the sd-ext option is missing, at least until I switch language

Trouble is I only do English .. hehe

I see why

https://github.com/AndDiSa/GB_packages_apps_Settings/tree/adsMagpie/res

the ones without "added sd-ext to arrays.xmls (default install lo... [Firerat]" will be broken

e.g.

https://github.com/AndDiSa/GB_packages_apps_Settings/blob/adsMagpie/res/values-en-rGB/arrays.xml

<string-array name="app_install_location_entries">
<item msgid="8151497958991952759">"Internal device storage"</item>
<item msgid="3738430123799803530">"Removable SD card"</item>
<item msgid="4498124044785815005">"Let the system decide"</item>
</string-array>

looking at it Firerat just cheated

https://github.com/AndDiSa/GB_packages_apps_Settings/blob/adsMagpie/res/values-es/arrays.xml

<string-array name="app_install_location_entries">
<item msgid="8151497958991952759">"Almacenamiento de dispositivo interno"</item>
<item msgid="3738430123799803530">"Tarjeta SD extraíble"</item>
<item msgid="8651707593222110014">"sd-ext"</item>
<item msgid="4498124044785815005">"Selección del sistema"</item>

and used a generic sd-ext for all langs

in Settings

for i in $(ls res/values*/arrays.xml); do grep -q 'msgid="8651707593222110014' $i; if test $? -ne 0 ; then sed '/3738430123799803530/ a \ \ \ \ <item msgid="8651707593222110014">"sd-ext"</item>' $i;fi;done

if your happy that that works, then add -i to the sed command

a little easier to read

for i in $(ls res/values*/arrays.xml);do
grep -q 'msgid="8651707593222110014' $i
if test $? -ne 0;
then
sed '/3738430123799803530/ a \ \ \ \ <item msgid="8651707593222110014">"sd-ext"</item>' $i
fi
done
[G1 Android Development] roccoadam32:
less than froyo
[G1 Android Development] SubVert:
Oh yeah, I did read that, but it didn't register :) Ignore me!

Yup, all fine.

I can confirm it's the language thing. I'm on English-GB, if I change to English-US, SD-ext is there :)

SubVert
[G1 Android Development] jdb78:
In my subjective impression the odexed version seems to be less snappy and lags more than ADS_magpie-20110309-signed for instance. I can't give you anything proofing that, just MHO.

Since I deleted swype (which was very hungry for memory) and installed hrk's ghost sms both - the ghost sms and the mms app notified me about new messages. So if one assumes that ghost sms receives messages more reliable I guess I did not miss any message since then. :] Ghost sms did not notify me alone up to now.

I'll keep on testing the odexed released for another day or two and will return to the latest non-odexed ADS Magpie to be able to compare the two versions.
[G1 Android Development] AndDiSa:
I had a similar impression after installing the odexed version. Especially reaction on touch / swipe seems to be a bit slower. For the rest I do not notice much differences. Benchmark values are more or less the same (even if I never reached Quadrant score of 400 as EffDee with the latest FR_magpie build).
[G1 Android Development] hrk:
Install swype again and see if you get ghostly notifications... ;-)
[G1 Android Development] ggonsalv:
I think the older version of Quadrant gives a higer score. With Standard I get in the lower 300's and with Advanced 1.1.something I get 360+. Both are with no Gapps, with Enhanced email installed.

Also I think odexed is a slower that original
[G1 Android Development] jdb78:
+1 exactly what I meant. :)
[G1 Android Development] AndDiSa:
You can try yesterday's build, it seems to me better.

But be carefull: /system is on it's limits. You need at least 90MB (probably more), otherwise you will get problems with flashing / restoring gapps.
[G1 Android Development] jdb78:
/system is 91.0M - I ain't use custom MTD. ATM df -h shows 6.4M available but I assume that flashing a ROM will erase everything? You kind of irritated me :]
[G1 Android Development] AndDiSa:
Flashing only the ROM (after wiping) will fit on a /system with about 85MB, so there is no problem. But there is the backup.sh script which will copy gapps on installing and this might fail if there is not enough memory available. Try to flash it, if you have only a few 100 kB free on /system there is a big risk that your /system partition was too small ...

Edit: it's more a warning to those people using CustomMTD, like me ;)
[G1 Android Development] jdb78:
I see, thank you for explaining. (: Well tonight I won't flash anything, phone has to work reliable. I'll try tomorrow if the non-odexed runs smoother and give feedback.

I love this thread with all the contributers, thank you guys!

EDIT: Oh it was an odexed version, too. O.k., give it another try right away :]
[G1 Android Development] jdb78:
Today I was updating apps from the market. In the meanwhile I received a phone call which I couldn't answer so it has been diverted to the mailbox. After that I got a notification from Ghost SMS - but there was no message in the Inbox. So, Ghost SMS seems to do what it is supposed to do! :) Great stuff, thank you!
[G1 Android Development] roccoadam32:
latest ads is running super smooth even with jit on still cant disable to the on screen keyboard though but thanks great work!
[G1 Android Development] farmatito:
New 2.6.35.11 ds 32b kernel for 2708 radio with bfs

for ezGingerbread.

I'm working to fix the usb battery drain bug but need more

testing, so please report if you see any improvements.

NO WARRANTY. USE AT YOUR OWN RISK.

Enjoy.

PS: This kernel is tested only on HTC Dream.
[G1 Android Development] Effdee:
Any source code?
[G1 Android Development] d3vilskid:
cant get it to boot past the g1 logo, not sure if its because im running andisa roms.
[G1 Android Development] farmatito:
Cannot test it on ezGinger as I'm running enomther now.

Will check If my build scripts are messed up.
[G1 Android Development] ThdDude:
Would not boot my G1 on Ginger Yoshi RC6.1, Hangs at G1 screen
[G1 Android Development] Effdee:
guys

if this has nothing to do with the ezGingerbread repo then consider creating your own thread for it
[G1 Android Development] farmatito:
New 2.6.35.11 ds 32b kernel for 2708 radio with bfs

for

ezGingerbread

based on pershoot git.

I'm working to fix the usb battery drain bug but need more

testing, so please report if you see any improvements.

NO WARRANTY. USE AT YOUR OWN RISK.

Enjoy.

PS: This kernel is tested only on HTC Dream.

Fixed boot problems: squashfs was not compiled in.
[G1 Android Development] Effdee:
interesting

what makes it specific to ezGingerbread?

any chance of seeing the source code as per the GPL?
[G1 Android Development] d3vilskid:
andisa post on this source repo thread, if you care to look. and if you didnt know andisa rom is based off of ezgingerbread rom with the addition of firerat magpie, and with some of his mods to it.
[G1 Android Development] Effdee:
yes I figured that out

still

I have no idea what that has to do with posting a kernel in every rom thread

along with not providing source code for it, and getting awkward when someone asks for it

It would be nice to have a kernel without the drain bug, but that guy is just going about it in totally the wrong way.

start reading here http://xdaforums.com/showpost.php?p=12403099&postcount=713

and look at his posting history here http://xdaforums.com/search.php?searchid=64602817

he needs his own thread, and in that thread he needs to set out a testing procedure.

the purpose of the test procedure is to limit the variables he is dealing with

and he spat his dummy out when I suggested he approach nailing the bug via regression testing, claiming he didn't have time.

No time? but has plenty of time to be compiling random kernels from random source bases.

I have said my bit, if he chooses to ignore then more fool him.

I will be ignoring his spamming of kernels compiled from secret source

I might make some time to fix it properly, or at least get the ball rolling with a proper plan
[G1 Android Development] d3vilskid:
effdee: all i can say about that is to his there own i guess, seems like he doesnt really want help.

farm: so far using the kernel, unplugged it from usb and no reboot. been using it for like 30 min to an hr and so far that crazy android os on that battery stat havent increase or show up. but will be testing it more down the road and giving more feedback.
[G1 Android Development] Effdee:
from his post history he has been at it for weeks

he may not want help but he needs it

he also needs to link the source or have his kernels treated as warez
[G1 Android Development] roalex:
Im not sure whats the big deal in releasing the sources or patches or commit history. Its like no public work on kernels for ds GB, which surely isn't going to do anybody any good.
[G1 Android Development] Effdee:
agreed

look at the great things that have happened here because of Ezterry

we have a few forks to play with, and all the code is in the open

I'm seriously thinking of building a snapshot ROM and organising an effort to squash this usb drain thing

no skipping back and forth between different source bases

no spamming every rom thread to get random users to test hidden fix attempts on their random roms with random apps and usage patterns

maybe in a couple of weeks I can draft up a plan of action
[G1 Android Development] studjuice:
I have a suggestion for an edit to the first post.

In the first post where it says

repo sync

to be changed to

repo sync -j16

I found this difference from the cyanogenmod building from source page, and it was that little difference that has made me finally able to do the repo sync without hanging!

Perhaps someone could explain why adding "-j16" gets further?
[G1 Android Development] roalex:
How many jobs to do i think, -j16 gets it done faster for sure.
[G1 Android Development] ezterry:
Yes... well I think I've been actually using -j10 myself (never used to but needed with the stalling) ... 'repo help sync' tells you about the -j option.. I think the CM update is new.
[G1 Android Development] d3vilskid:
Yea it would be a lot helpful if he posted up the source patch or whatever he did to the kernels. But all I could right now is hey he is on the right path with this new kernel. Battery drain is at a minimum, that damn android os doesn't run like it used to.
[G1 Android Development] d3vilskid:
So this android os still runs but it cuts on and off for a long while. Not as constant as it used to be. Which is keeping the drain to a minimum.
[G1 Android Development] farmatito:
What I did:

1)About posting kernels in threads: each rom uses slightly modified kernels with little differences in config so if you want people to test and report about a change you have to supply kernels that are flashable and actually boot with their roms.

2)I've always stated what the source base was (peshoot, cm-kernel, kernel.org, whatever)

3)If you had taken the time to look at the posts you claim to have read you would have seen zipped patches attached to some of them.

4)Some of the patches were applied on the trees of other devs (ezterry if i recall correctly and pershoot).

5)I will of course release the relevant patch about the usb drain bug if it is confirmed that it fixes or reduces the bug.

6) About suggesting the correct approach of fixing the bug I can only say that talk is cheap and that rather than suggest things to others that try to do their best to fix a long standing bug nobody cares about you can take action in your hands and fix the bug with the methods and approaches you feel to be fit for the purpose, on the other hand you could also give me the help I asked you for and test this kernel. Costs nothing, is fast and could contribute to create better roms in the end.

7) I'm working on this for weeks, maybe months and I can assure you that I've tried all ways "to limit the variables"

8) About the testing procedure: there is no need for a testing procedure as it is very simple: boot, plug in usb, start an adb session, unplug usb, battery drain.

What i will do:

1) Now i presume to have fixed it in the sense that for the last week I was not able to trigger the bug so I'm happy that I can use my phone without risking to run out of battery but I want to be sure that others see the same results as I do before publishing the patch to avoid you could say that I falsely claim to have fixed the bug. So more positive reports sooner the patch will be published.

What i will not do:

1) I will not set up a git repo as there are far to many polluting the web already.
[G1 Android Development] roalex:
Or your hiding your key logger.
[G1 Android Development] farmatito:
this is a problem you have with most cooked roms, even

ezterry's ezGinger has precompiled kernels, also the apps

that you download from the market do bad things sometimes........
[G1 Android Development] ezterry:
precompiled kernel.. in the repo yes.. but not without source:

http://forum.cyanogenmod.com/topic/...ghtlies/page__st__5660__p__117678#entry117678

And *ALL* cooks are supposed to provide the source of their kernel (yes if you use say the kerenl above you can point at that post.. as is done in a few places including the second post of this thread) but the kernel is GPL and sources must be provided.

Most of the Android system is Apache2 and under different requirements.

1) the point of a git repo is to maintain *YOUR* changes so if you are not actually using git locally you are going to have a much more pain in the long term..

2) as for a public repo.. well I'm not sure really why you are adverse to it.. its simple to clone pershoots tree on github .. then use it as your own.. push a tag with the public release of a kernel and you are a step ahead of many developers here... but if you really don't want to bother I accept the output of format-patch see: 'git help format-patch' for details .. you may find the output looks familiar.

Problem is given your track record ...

1) I won't believe it until I see it..

2) I won't test it until I see the code

And thus I have ignored all kernels since patches stopped appearing and will continue that rule

There is some exception here.. but it involves a more dedicated group of testers not a kernel published to the public.
[G1 Android Development] farmatito:
I know that maintaining the changes is a pain, nonetheless

that is how I'm used to do it. I'm adverse to a public repo 'cause i will make my patch public as soon as there are more positive feedbacks that it does what is expected and does not break anything else. That way there is no need for another repo as the patch could be committed to the existing ones.

I'm all for sharing the sources and license compliance

but to tell the truth most of the roms on xda include proprietary binaries (libs, perfected spls, radios, fixed apks ) , or link to gapps to be downloaded or come with precompiled kernels pointing to sources that don't even compile, so calling just my kernel warez is ridicolous, nonetheless if there is a request from a forum moderator I can remove them all.
[G1 Android Development] farmatito:
I really don't see the difference....thought people on xda already was a dedicated group but if there is a more dedicated group of testers how can i send them the kernel to test? So it is ok to do it in private but not in public?
[G1 Android Development] Effdee:
instead of posting your kernels in every rom thread just make your own

[THINK-TANK] lets nail the usb drain bug

and I don't see why you need specific kernels for each ROM

Anykernel solved that by making it quick and easy to pack your zImage along with the rom's ramdisk and kernel command line

and as for your point on polluting github, it is bs

you are quite happy to pollute xda rom threads with your 3mb attachments, bandwidth xda pays for

get yourself a free uploading account , like mediafire , rapidshare , or dropbox

your own thread just makes much more sense

no pollution of rom threads

central discussion of your work, which has to make your life easier in tracking feedback

wake up dude !
[G1 Android Development] farmatito:
I did not post in every rom thread i posted just in 2 (the one i'm using now and the one i used before) plus a link in the kernel thread.

So please stop telling things that are not true.

If you don't see why specific kernels are needed for different roms than just take a look at the differences between lets say enomther's and ezGinger's and try to boot one rom with the others kernel.
[G1 Android Development] d3vilskid:
farm: since unplug from usb and no reboot, phone lasted for ten hours. the android os that was killing that battery is at 10. odd thing is

Display eats 37% of battery on sleep mode.

cell standby at 32%

and phone idle at 17%
[G1 Android Development] Effdee:
so in your think tank thread have

Froyo version

gingerbread version

honestly you are digging yourself a hole

just make your own thread and stop spamming enomther's , ezGinger's and kernel corner

or at least limit yourself to kernel corner

but as you are specifically trying to fix the usb drain I think your own thread is warranted

central

easier to maintain updates

better version control ( no need to dig around the forum )

specific discussion on usb drain

as I have said before, you can choose to ignore my advice

BUT I think many will see that what I have said here makes sense and you would be foolish to ignore it.

It is your call
[G1 Android Development] Effdee:
I get around 10 hours with ezterry's kernel

the 2.6.35.10-cyanogenmod ezterry@zack

so nothing new
[G1 Android Development] d3vilskid:
yea but when i use ezterry kernel and forget to reboot, my phone will die in a matter of mins well really like 30min to an hour. but i know what your saying.
[G1 Android Development] Effdee:
this *is* without reboot !

I used to get around 15hrs with stock 1.5 so for me 10hrs is bad

but you think 10hrs is good?
[G1 Android Development] d3vilskid:
wow hmm... for some reason im always plagued by this usb drain bug.

10hrs on gingerbread for me is ok, and i guess i forgot to mention i recalibrated the battery also, so after a couple recharge the batt life will be back to normal hopefully around 15hrs
[G1 Android Development] farmatito:
Stock was not overclocked nor had it the usb drain bug.

So you can confirm that the android os entry in battery stats

disappears/stops after unplugging usb and battery doesn't drain fast (less than an hour sometimes). That is exactly

what I'm seeing on my phone. I would dare to call that a improvement over the previous state of things.