yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] ezterry:
The logcat tells me maybe try fix permissions..

genie widget is better than it used to be .. currently it defaults at a 6h refresh. As it serves various other applications news+weather info (such as the weather icon on the DeskClock app) it will refresh even if not actively run or set to a widget.

That said previous version used to attempt to stay memory resident; at least that seems to no longer be the case.

I believe the above reasons are why you do not find the apk in the MT3G froyo OTAs.

I can't say it won't eat some battery but given the above it really ought not be a major drain. (delete it from system if you don't want it)
[G1 Android Development] hrk:
As a sidenote regarding USB draining, I have something weird here. I experience drain when I unplug from a Mac, a Windows laptop and a Linux server, but not when I disconnect from a (different) Linux desktop. Yesterday the standard battery went on for 19+ hours (with standard usage!) and I charged it from the mentioned desktop, no rebooting after disconnect.

I'll try to figure out the difference, maybe it can help pinpoint the bug.
[G1 Android Development] greenkabbage:
Hi ezTerry,

I followed your instructions in the op to set up a repository on my ubuntu machine, but when I try to make, I get an error.

make -j3 otapackage
============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=2.3.2-ez
TARGET_PRODUCT=full_sapphire
TARGET_BUILD_VARIANT=userdebug
TARGET_SIMULATOR=false
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=GINGERBREAD
============================================
build/core/binary.mk:25: *** external/stlport: Invalid LOCAL_NDK_VERSION '4' Choices are . Stop.

Googling lead me to a patch for x86 builds, but it logically didn't fix my issue. Any ideas?

Thanks!
[G1 Android Development] AndDiSa:
ro.compcache.default defines only the default value, the current value is defined in /data/property/persist.service.compcache

If you want to change the value you should modify / remove that property
[G1 Android Development] ezterry:
It must be something wrong in your enviroment:

All that the validation in question checks the requested NDK version is in TARGET_AVAILABLE_NDK_VERSIONS, in turn populated based on the prebuilt NDK directories.

You ought to see version 4 when you run

ls -d prebuilt/ndk/android-ndk-r[0-9]*

in the root directory

---

Edit: on a completely different note.. how is bluetooth working for people.. I tried to make an internet call with a chepo bluetooth headset ... it worked for about 5 seconds before audio stopped sending/receiving.
[G1 Android Development] ximmox:
It was one SMS at the beginning of my ezGB-test (latest nightly) that went missing.

Afterwards I had no problems, at least none I know of ... so it doesn't seem anywhere as severe as it was the case before the fix in CM6.1 (where I received only half of the sms).

In my case I really lost the one in question, my girlfriend gets a report from the provider that it was delivered, but it never shows up on my phone.

I'm sorry for the confusion, it's doesn't really seem to be a problem anymore,

I'll report back once/if that happens again.
[G1 Android Development] greenkabbage:
Yup, looks like the initial repo sync messed up while setting up the prebuilt stuff, even though I reran it a couple of times. After starting over from scratch, it worked out.

Thanks!
[G1 Android Development] greenkabbage:
So far BT has been working well for me. I used my sony ericsson MW600 for stereo audio and a couple of voice calls without a hitch.

Edit: Doh, should have put this into my post above, sorry...
[G1 Android Development] guitargler:
I lose nearly all. Once in a while, one comes through, but it'll be while I'm literally not using my phone at all, no tasks running, probably not been using it for a while. And I don't know if the few texts I have gotten are current or delayed. I suspect delayed.
[G1 Android Development] jdb78:
I apologize in advance for asking this here since I know there is no support for binaries so far. But I don't know where to ask else.

I tried to install an app from market.android.com, it would not start downloading on my device due to no connection to GTalk (provider related). At home the device connected to WLAN, started downloading the app. I decided not to want it any longer and canceled the download in the market app. Since then I don't see any apps any more in my download list within the market app any longer. I did the following to resolve the issue:

delete cache of Market app

delete cache and data of Package-Installer

restartet phone

wiped dalvik-cache and cache in recovery

downloaded new apps

The new downloaded apps appear in the downloaded apps list within the market but are not marked as installed. They are installed though. All my installed apps are not marked as installed in the market app.

I still can see all the apps within the http://market.android.com profile. I read somewhere that one has to set the device from "hidden" to "show" within the settings of that profile, which I did. Since then the site claims that no device is associated with my account.

The last thing I did NOT do is to delete DATA of the market app because the button is grayed so I can't push it.

Does anybody know, why this is grayed and how I can delete data manually?

I use the phone mentioned in my signature with ADS_magpie-20110202-signed ROM.

I apologize again for off topic and hope for help.
[G1 Android Development] wrsg:
i don't know where else to ask this but i want to use this -> cm_dream_sapphire_full-307.zip

with the latest 28.25 radio and the .13d spl that t-mobile released recently. is it enough to just the flash ezterrys latest g1 kernel for froyo over this? is there a version of that already has the relevant kernel? some help here would be nice.
[G1 Android Development] jdb78:
Maybe here?

I used to use terry's last kernel with the 285 build and it worked fine for me. AFAIK the 307 is very similar to the 285. I use This SPL though.
[G1 Android Development] wrsg:
thanks

it seems from that thread that i can just slot in any kernel as long as its froyo-compatible? i did already see that rom thread, but i was hoping for a more froyo-froyo if you know what i mean, i.e. without the added ginger. i think i'm on the same spl as you.

i know this gets asked all the time, but any idea as to the best kernel for froyo roms?
[G1 Android Development] jdb78:
This is not a Froyo thread, this is eZTerry's and all the other dev's thread for AOSP Gingerbread so please ask at least within a Froyo thread. I assume there is no "best" kernel. I experienced that ezterry's and pershot's kernel are both very good in any manner so just chose one of those.
[G1 Android Development] kwapiu:
BLUETOOTH

Mine case exactly.

Thou am not using BT on regular, lately been bored and tried to connect to various bluetooth available devices.

Each time connection failed even before pairing was done.

On the other side I am still on previous version, will upgrade to 02.08 now.

Keep up the good work :)
[G1 Android Development] crypticc:
You might wish to search cyanogen forum for my posts with audio.conf mentioned. It could be same issue.
[G1 Android Development] Krypt:
My phone crashed last night and I noticed that the 3-finger handshake doesn't work anymore. I tried to reset with Phone-Menu-Hangup combo, but that doesn't work anymore.

Is this a ROM, SPL or kernel issue?
[G1 Android Development] smashman42:
I think it is new for Gingerbread, the 3 finger salute still works in Froyo with a .0013d/.28.25 config Sapphire so that eliminates the SPL/Radio
[G1 Android Development] Firerat:
it works, but it is not immediate, hold for 5+ sec
[G1 Android Development] hrk:
Does this mean you're still alive and kicking on this forum? :)
[G1 Android Development] bypass23:
Well thanks for the input it's my fault... If it doesn't go farther the splash screen it kinda means the kernel doesn't boot properly :eek:

I forgot to update the ramdisk I think, well since few other people did send me private messages after your post I tried to fix it.

I updated the download link from original post

Thank you for trying ;)
[G1 Android Development] ForTehWolf:
Got SU to work,

after turning off animations and clocking to 595, this ROM is pretty usable
[G1 Android Development] lolmensch:
not working :S

doesnt proceed after first bootsplash. no bootloop just freezing. tried to install by default and with pershoots latest kernel 2.6.35.10. (dunnow which one you are including)

dream 32b with dspl and 2.23 radio :S
[G1 Android Development] irisiris:
how did u wipe phone?

did u do superwipe then shutoff phone? then reboot to recovery and Flash ROM. reboot normally till u reach homescreen. then shutoff phone.reboot to recovery to flash the modded gapps the reboot normally to use phone.
[G1 Android Development] lolmensch:
i wiped as i always wipe.

clockwork recovery:

wipe everything (data, cache, dalvik-cache, system, boot, sd-ext, .androidsecure)

then reboot into recovery and flash the rom. reboot and it sticks at 1st bootsplash
[G1 Android Development] ForTehWolf:
All I did was flash the su over ezterry's alpha, when I tried using the other ROM and kernel is failed for me too

Is there anyway to keep Launcher2 in memory btw?
[G1 Android Development] irisiris:
i did wipe first time from recovery and got stuck too on sapphire..but then i flashed superwipe, rebooted to recovery.flashed rom and it worked.
[G1 Android Development] lolmensch:
didnt work. are you on new radio/spl?
[G1 Android Development] irisiris:
ofcos.. 14MB RAM with new radio and SPL is a blessing for 32B ;)
[G1 Android Development] lolmensch:
k thx thats the difference. only had bad luck with it.

edit: tried new radio and hboot and it's booting

edit2: bootloop at the very end. seems kernel related. not sure.
[G1 Android Development] irisiris:
try the 22nd dec ROM.. it doesnt loop

i tried 27 dec one..it loops
[G1 Android Development] lolmensch:
already tried it myself. anyway thanks =) it boots ^^
[G1 Android Development] midget_3111:
Just flashed Ezterry's latest radio + kernel on my G1 tonight, I must say that it and this ROM are pretty amazing considering stock updates to the G1 stopped at 1.6, the things the community can do eh?
[G1 Android Development] ForTehWolf:
and this is just the Alpha :D
[G1 Android Development] CBATESY:
there shouldnt really be any different with the roms. the 27th is just colorized, unless im missing something....?
[G1 Android Development] tnpapadakos:
pretty much, yup
[G1 Android Development] fineguy1:
It loops for me. I left it going crazy for about 30 mins, and went back to that of the 22nd. Battery life is pretty good. With the extended battery, it's lasted almost 48hrs and I still have 30% left. The same battery used to last me about 12 hrs.

Thanks for the good job.
[G1 Android Development] CBATESY:
usually if It loops to a long period of time I just remove the battery at that point and reboot. usually boots pretty quick while in a couple of minutes. Usually with any new rom installed the first boot is the longest, at least for me. With this GB ive had great battery life, I just ended up trying out Yoshi 1.7 untill the gps is working.

Back to GB. yay got bored. Ive been wondering why this thread isnt in the mt3g section?? seeing that ezterry i thought had a mt3g. ....huh
[G1 Android Development] mzmo:
You guys are just simply geniuses. They said the G1 would never be able to go past 2.1 & it did. Now they're saying it can't go past 2.2 & it can & it will! Just showing my appreciation.

Much love to the devs!

Sent From My Awesome White HTC Dream
[G1 Android Development] MrFrankfromCM:
So, I tried flashing GB and getting this error:

BY-GINGERBREAD-32A-Alpha mount() expects 4 args, got 3. E:Error in /sdcard/BY-GINGERBREAD-32A-Alpha-signed.zip (Status 7)

My info is:

2.22.23.02

2.6.34.7

1.33.2005

Thanks for any advice.

Frank
[G1 Android Development] xela92:
waiting for updates/new nightlies :D
[G1 Android Development] ezterry:
I'd build nighties more often if I received more patches.

But I've not really made any changes since the build on the 8th myself. (Well a new tool for CustomMTD.. but I've not integrated it with the otapackage build yet)

Part of it is temporal problems.. been busy on projects that pay me significantly more than this one.
[G1 Android Development] s14evil:
Using ez gingerbread 0129, is the a patch for Gingerbread Keyboar
[G1 Android Development] jdb78:
Hi s1evil,

What kind of patch do you need?

@thread: I installed AnDiSa's last build recently. Had to re-install anyway due to my market issue. I had the build before the last one on my Dream up to then. In my opinion the build before the last build (still talking about AnDiSa's Magpie build-sorry for my English) was more reactive, acted smoother. I had not one single reload of ADW. With the last build I have a reloading ADW every other day. And in my opinion the touchscreen does not react instantly anymore, it takes a few ms to react. It feels like you gotta press the screen harder-sounds funny,huh?

EDIT: I switched back to AnDiSa's build from 20110202 without wiping (only cache and Dalvik) and the phone is much more responsive, working better again.
[G1 Android Development] strages:
does anybody know something about the battery drain on using native sip in gingerbread? what should it be and what does it cost atm ;)

i am using it, but i think i am experiencing bat drain from it.... (still it works like a charm ! :D )
[G1 Android Development] MrShides:
Well EzT,

I've been watching development here and since I hadn't seen much changes I gave this a shot and have been running it since monday.

It runs great, if not just as good as your tmobile 2.2 update for the mytouch.

Great work as always. I'm officially an EzT fan!
[G1 Android Development] jdb78:
+1
[G1 Android Development] xela92:
I know, you're totally right... But I'll tell you: this is really an awesome project, and it's great that you did all this for us, and if you'll keep doing, I'll really appreciate (and maybe, who knows, make a donation? ;))

Anyway, THANK YOU :)
[G1 Android Development] crypticc:
What you waiting for? lol
[G1 Android Development] bestofrhcp:
is it me, or the latest build's Android system and OS taking up a chunk of battery life??
[G1 Android Development] jdb78:
The opposite is the case. Batterylife improved. Like I mentioned before I experienced a huge drain, too - but only the first two days of using it. I also use autostarts to avoid having apps running without using them. My battery life is wonderful. I still use the original battery that came with the Dream.

According to donating: +1, what are you waiting for?
[G1 Android Development] Firerat:
it is the kernel

and before you ask, no there is no current kernel without the bug ( blame everyone for running with the pack ) , if you want a kernel with better battery then use a 2.6.34 kernel ( but I'm not sure that will play well with gingerbread )
[G1 Android Development] id242:
For anyone asking for a link to that, here is one...

Pershoot's Kernel - http://droidbasement.com/db-blog/?p=1096

EzTerry's Kernel - http://xdaforums.com/showpost.php?p=8797419&postcount=442

Since the "2708 Radio" came out around the end of November and the "2.6.34 Kernel" was replaced by the "2.6.35 Kernel" in mid-September sometime, as Firerat mentioned, you may have difficulties finding one since everyone was basically doing the same thing at building the latest kernel. ("running with the pack")

So basically, if you are running Radio 2.22.27.08 or 2.22.28.25 with a 1.33.0013 version of SPL (for the 14mb RAM "hack"), you are just about SOL for finding a "2708 Radio 2624 Kernel". Everyone else is good :)
[G1 Android Development] ezterry:
Your timeline is off.. 2708 I released just after Biffmod 2.1 on November 6th; and used the bifftesting 2.6.34.7 kernel (derived from pershoots 2.6.34 tree)

The 2.6.35.* CM and Pershoot ports came after that.. but 2.6.34.7 trees have the old mass storage drivers that don't play nice with gingerbreads updated vold.. so either you downgrade vold and hope for the best.. or need the newer kernel drivers. (Or just never use USB mass storage) It also won't indicate debugging access is available however adb appears to work anyway.

My back porting of mass storage attempts to 2.6.34 have thus far failed miserably.. Some of the CM patches needed are mixed into large patches for other kernel components and cause problems in the back port.
[G1 Android Development] Firerat:
I'm currently using NameLessJedi's xVold , its base is CM Froyo branch, ums seems to work fine

I have Kanged NLJ's xVold into AOSP's gb branch, it compiled but I've not tested it yet ( not got round to adding in the data binds yet )

Couple of drawbacks with xVold,

one is that scripts on sd-ext don't run, as vold is started as an init service and these all start after the run-parts is exec'd

Second is a2sdext can be a little hit and miss, vold doesn't always mount sd-ext soon enough , seems to be ok on my G1 but others report that a2sd is not working, I suspect that if we start the vold service sooner ( around the same time as the other mounts ) it *might* have a better chance of working, but it could be the async detection of mmc devices that is the bottleneck , idk it might be difficulty for me to test as my g1 didn't suffer as much as others did

Anyway, should have a cleaner Magpie with proper sd-ext accounting one way or the other

( I've currently got SdExtIsMounted() logic in andriod.os.Environment, so I can easily switch it between vold or prop based without needing to change things in Setting.apk and the various other places in the framework , mind you, may make more sense to have that in MountService early days yet )

one day I might get round to looking at the kernel, but that will be no small task , bringing a bugless 2.6.34 upto .35 without the bat drain will likely take a long time, I've looked at usb related commits ( as it does seem tobe linked with usb ) but can't see anything that would trigger it, so patch --> make --> test until the bug appears seems to be the most foolproof way of finding it
[G1 Android Development] AndDiSa:
In my opinion your magpie-extension is running very well. I haven't understood yet, what's really the advantage to integrate /sd-ext mounting into vold. Can you help me?
[G1 Android Development] ezterry:
The reason I see is if you have magpie properly integrated with vold such as froyo/gingerbread apps2fat implementation is you can then unmount your SD card as long as you have no swap/data binds.

While some apps will be missing this may let you say put in the SDCard from a camera; copy off some photos; then return your primary dream/sapphire card.

Also it makes mounting the sdcard on your computer for a bulk transfer of files w/o using adb possible.

Without this end to end functionality I see little problem with using a script to mount the card on boot and just forcing the user to keep the card in the phone.. like a hard disk on a linux desktop. So I find the current version a point in the progress to the goal but not strictly something the average end user will see benefit from.

xVold will always be hard for init scripts on the sdcard..best keeping them in system or data.. if you really want it on ext.. I think safest is to leave the init.d script to mount/run them even if xVold is also installed so after boot the other functionality I mentioned can still be done.
[G1 Android Development] carz12:
You can't mount usb ? or am I not reading enough of the thread lol, some things got renamed in vold, I just updated the usb

The reason I went back to 34.2 kernel was a severe lag when I used the 35, I used my 34 sources and ported all the updates to usb that are in the froyo stable tree.

CM froyo stable is much more similar to my CM .34 / htc .29 mash for 6.35 radios because of all the htc imports he did, I was shocked, it's how I got GB running so quick on our radio. I also merged steelbytes camera source for hero into mine.

The reason I didn't update to 34.9 from 34.2 is all the pm updates, they don't play well with 6.35, I already have all of htc's updates for 2.1 in there.

I think with a few usb pulls from the 35 kernel you can use the 34 kernel just fine.

I really think it's the 6.35 radios time now though.
[G1 Android Development] ezterry:
Gingerbread changed the API between the kernel and vold (its a different message type not just a rename).

If you use the AOSP stock vold you need a kerenl supporting the newer messaging. (CM did sorta add it into 2.6.34.* as the kernel code has been known for a while; pershoot however did other things to USB mass storage and undoing it without other aspects of the kernel changing has proven annoying)

CM7's Vold on the other hand has a support layer for older kernels added since some of the CM supported devices are using much older kernels.

The CM version of vold actually introduces another bug (related to why pershoot says his latest kernels are not for gingerbread) is if you have a kernel that supports the new style with a backwards compatibility layer for the old Vold (such as all 2.6.35.* CM6.1 kernels including exp20110109 from ezGingerbread) the vold that also supports both the new/old USB mass storage messages gets duplicate messages (causing the USB tether issue you may have seen on other roms.. it seems to be working more on ezGingerbread)
[G1 Android Development] NLJ:
I've fixed this on Friday. It wasn't even xVold fault. PackagaManager service is considered critical and started at the very begining (it's like 4th service started by SystemServer). MountService is not critical and gets started way down the boottime.

During initial scan of apps made by PackagaManager MountService stuff is simply not there yet. The only reasonable way I found

for now

is to communicate with xVold via properties (this commit [1]). As soon as MountService starts it is perfectly safe to use getSdExtState() (this commit).

Logic of Vold will also pick up that /sd-ext was mounted before it started and keep that if somebody asks (like Settings or whatever).

That too but there is also a benefit of system knowing about additional storage and it's state. /data/data binds are more of a problem as currently it's not properly handled (system simply doesn't get info on bindings). The sole reason for this is that this should be handled using vold.fstab. So far I couldn't come up with syntax that would easily fit with current vold.fstab syntax.

At this moment one can check ro.vold.data2sdext and sys.vold.sdext. If they are both true than data is on sd-ext and unmounting sd card is dangerous (I realy can't think of situation when mount bind will fail and sd-ext will be mounted at the same time).

I don't think I get this. In my sources I disabled sharing sd-ext on purpose (so people won't mess there without knowing what they do). Now I think it can be made configurable.

No, it won't. To use scripts on sdcard it has to be mounted first. The only problem I see is that script mounting SdExt needs to take care of needed dirs (app, app-private, dalvik-cache at the very least). Also I kinda got lost: what other functionality you have in mind?

[1] - This trick with waiting is used in some other places of AOSP too (tbh most of the time while unmounting). 20sec is overkill and I don't expect this to last longer than 5-10 secs max. This also allows booting the ROM if there is no SdExt at all (previously it would crash on scaning SdExt)
[G1 Android Development] hrk:
Have you read this? [EHCI hint]

Is the hint useful?