yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] roalex:
Its not only about what you install but also about what you are running if you leave 2 browser windows open (exit with HOME) its likely that the task killer will start shooting left and right.
[G1 Android Development] dillalade:
ahahahaha, you just killed with "What's funny, is you think you know what I have installed on my phone."

hahahah, too fkin funny!

Great work with Ghostly SMS - I'm comin back to Ginger - BUT is it faster then Laszlo (cos that sh!t fliessss)

Great work
[G1 Android Development] dillalade:
Before coming back to gingerbread - can anyone set me straight:

1. has the notification power widget bar returned?

2. has the lockscreen music controls come in to this build?

Thanks in advance
[G1 Android Development] ZilverZurfarn:
No on both accounts. At least in AnDiSa's build.
[G1 Android Development] Poppu:
Nope. These are not Gingerbread stock features, but CM features.

So if you really want them you need to use a CM-based ROM.
[G1 Android Development] dillalade:
Thanks for confirming guys.

And has anyone officially stated the comparison in terms of speed/usage with Laszlo & this ezginger rom.

(If not, then I'll give it a go I guess)

Thanks
[G1 Android Development] ibraheeemz:
I have used most of froyo roms, but gingerbread is a hell stable, fast, smoth and a lot features!! so just go for it, EZTERRY is working to prepare an even mature kernal and will publish soon as he can!! so far you can use any ezginger based roms, like ADS_magpie, or others too.
[G1 Android Development] roalex:
The widget and such are pretty trial to "insert" for terry, im sure they will be here sooner rather then later ;)
[G1 Android Development] Poppu:
Not so trivial : check the thread on GingerYoshi, you will see that they can be included "as is" but to be fully integrated on our devices, they need to be modify (e.g. no "auto mode" for brightness as we don't have any luminosity sensor...).
[G1 Android Development] roalex:
don't compare yoshi with this....

this is made from sources, Yoshi is made from mixing binaries ...you can do anything with the sources, like modifying how the auto brightness works
[G1 Android Development] AndDiSa:
I agree, I was already looking for this, but it's not as easy as it seems at the first look. The PowerWidget functionality is very mixed with code from Cyanogenmod, so either you have to change the framework/base to Cyanogenmod or you have to touch many files ... :(
[G1 Android Development] roalex:
its a commit if you search in the cm framework history and the conflicts can be fixed (this has been done on a lot of other open sources roms)
[G1 Android Development] hrk:
Hehehe... if you want to see the source, I can release it. No problem in doing it. :) However, if you think my app messes with SMS... how can i "make up" messages for people I don't even know or speak their language? :)

BTW, I have 3 widgets (Google Search + 2 * Smooth Calendar) and I limit my installed apps ('cause I don't have time to play games or such stuff). It's true that I have Titanium Backup installed and that I exit the browser with the HOME key... I will remember to close the window (even if it seems stupid to me that an unused page in the unused browser makes the system kill an actively running process which is receiving messages...)

Now, as a sidenote: I've just been in Belgium for around 24 hours and I lost around 90% of the messages I received. Wow, that's really something! :eek: It's very likely I had a (single) page in the browser (mobile check-in@airport) which I "HOME-d" at the airport... then I didn't even have data turned on (no roaming). Gonna wait some hours before installing 0413, just to see if I receive messages in Italy.

EDIT: Ok, I sent a message from another phone and... it got lost. :) ddms shows just a bunch of applications running (no browser). I can confirm that I have multiple receivers for SMSs: the stock app, a widget for my mobile operator, prey, xbmc, a second sms app, my own ghostly. Quite a bunch, yep... I'm gonna move to 0413 now. :)
[G1 Android Development] AndDiSa:
Yes, I know. It this one:

https://github.com/Pedlar/android_frameworks_base/commit/eb0e39732842151e947f27cf64a00480d75e5631

But this is from october last year.

1) This patch is not (fully) compatible, i.e. you have to do some additional changes

2) in the meantime there were several other changes related to the PowerWidget, so those changes should be merged, too ...

I wouldn't say that it is impossible, but one has to find some spare time to do that work.
[G1 Android Development] jdb78:
I use Ghost SMS, too. I'm glad I do because I lose messages every time they arrive while using the browser or Google Maps (I used to use Maps a lot recently because I will move to another town). I don't use widgets a lot, only dazzle as a temp power thing control bar you were talking about and business calender to show the next three appointments. I have a lot of stuff installed but autostart prevents the apps from starting automatically.

BTT: I use the latest AndDiSa Magpie and I am really happy with the snappyness (does this word exist?) Runs like a charm!

--

Sent using my HTC Dream
[G1 Android Development] roalex:
not that one, its one in the GB framework, in Jan i think it was, search deeper ;)
[G1 Android Development] AndDiSa:
When I am able to find it ... and find some spare time, I will try to integrate it. I know, there are several people waiting for it.
[G1 Android Development] roalex:
https://github.com/CyanogenMod/andr...mmit/bc8cf55a953bac719f97b7d4b34c6a7d716587a0

ofc there are more commits to fix some of its features but you can follow up from there !
[G1 Android Development] AndDiSa:
Yesterday I found some time to analyze / to merge it into the current ADS Magpie. Some modifications were missing, but I was able to kang them from the cyanogen sources. Seems to me, that it's working fine now. Thanks again for your hint, roalex.
[G1 Android Development] creezalird:
Is this for real..looks cool..gonna try this tonight..:D
[G1 Android Development] roalex:
I think you also need to rip the settings from CMParts for the widget, aint really hard either.
[G1 Android Development] AndDiSa:
Step by step ..., but it's already on my list. ;)
[G1 Android Development] aneto:
Thanks a lot AndDiSa!

ADS 20110416-1 works very, very well.
[G1 Android Development] bi0hzr:
that's good to know i love it, but, how much memory does it use that?

im about to test las ads build, and give feedback, ty so much
[G1 Android Development] ggonsalv:
I don't see any difference when adding the widget to the desktop??

Do you need to do superwipe before installing it?

Love it all the same, been my daily driver for atleast a month+..

Fast and no mysterious reboots or freezes..

Only things I miss are unlock with menu key, and battery %age in status bar.
[G1 Android Development] creezalird:
It is not the widget on desktop, it is widget on the notification bar. Slide down yours, you will see it there. :D
[G1 Android Development] ggonsalv:
Duh... I see it now..

This is the most stable ROM imho...
[G1 Android Development] dillalade:
wOwzers, I'm glad I popped back a few days back to bring this Power Bar back to surface.... fkin sick Research by Roalex & great work with implementing ADS.

Im coming gingerbread, Im coming to youuuuuu, ahahahah

erm - so from reading that commmit - we can have more then 6 widgets in the bar (scrollable?) - and music controls applicable here tooo? Really?

Cant wait to flash this badboy again, when I left this months back when helping discover the sms fails I wasn't sure if I'd come back (great work to the Ghostly SMS dude too, props!)

Thanks to everyone for all the brainstorming/digging/implementations.
[G1 Android Development] dekans:
Do wa have to activate anything to get these widgets in the notification zone ?

I just did a repo sync & build. But there is no such notification bar widgets in this rom :(
[G1 Android Development] creezalird:
I'm not really acquinted with "repo sync&buld" , but I've just updated mines with the ROM link from Andisa for ADS_ezGingerbred. No need to activate anything.
[G1 Android Development] AndDiSa:
If you want to build from the sources, you have to checkout my modifications from Github.
[G1 Android Development] newellj79:
Would appreciate some help. I'm currently running roalex version of gb and loving it. I'm a flashaholic thoughand looking to try some other versions of gb for fun. Stumbled upon this thread. Alot of people who post in here have the ads magpie gb in there sig. I'm thinking of trying it. My question is, is that the rom that this thread is for? I see it says based on ezterrys code. Compiling the rom myself is over my head. Sure wish it wasn't. :(
[G1 Android Development] creezalird:
ads magpie ezGingerbread is kind of modded/added feat of ezGingerbread(ezterry).

U can try the original flavor of ezGingerbread from the first page link download

or you can try the added magpie version from dropbox link in Andisa's signature ( or anyone else, even mine)

I'm not really the wise-guy here about magpie, but it is some kind of script that give you the ability to move/install app into your specified location such as sd-ext partition.

So far..My phone is running quite well, especially with the latest version, added the most-wanted widget on notification bar, I couldn't ask for more ..:D
[G1 Android Development] geokuttan:
Is it possible to implement the app2sd method used by super in superAosp http://xdaforums.com/showthread.php?t=1036283

For some reason while using ADS magpie the app2sd doesnt actually move the entire app to sd/ext or something i tried the super aosp and i got like 20 apps and still no changes in the internal memory storage(60 mb left vs 14 mb on ADS). Is this a good idea? just wondering.
[G1 Android Development] AndDiSa:
What did you try? What is your preferred installation location? Do you have an ext2/ext3/ext4 partition?

For sure Firerat's magpie implementation is the best I know so far. It offers you the possibility to select the place where to install the apps and to *move* them arround (internal, fat, ext): Go to settings /application management and first select your preferred installation location. Now all new apps will be installed there. If you want to move an app, then select the app in application management and move it by pressing the appropriate button.
[G1 Android Development] creezalird:
An extra question : I have the ext4 partition but if i check through terminal. The partition is mounted as ext2. I've googled about this and found out that this is due some mount script in the ROM.

http://forum.cyanogenmod.com/topic/16476-ext4-mounted-as-ext2/

It looked like has something to do with the mount command.
[G1 Android Development] AndDiSa:
ext2/ext3/ext4 are almost the same (at least as it it used on the phone), ext3 / ext4 have journaling which is slower, but which guarantees you a consistent file system, even when OS crashes. On our phones imho journaling is superflouus ...

Mounting of sd-ext is normally done with the "auto" flag, and as it seems, auto is mounting as ext2, even if a journal exists. I personally would not change anything here, because it's the most compatible behaviour, otherwise you need different mount options for different filesystems which will lead to more complex code and more error prone behaviour

...
[G1 Android Development] jdb78:
They changed a mountscript for Dark Tremor A2SD. But I read somewhere on XDA the other day that we suppose to use ext2 only because ext3/4 is wearing out the SDCard a whole lot faster due to the journal written on the card. I guess the next SDCard I'll buy I will use ext2 only for sd-ext. What is your opinion about this?

EDIT: AndDiSa was faster... :)
[G1 Android Development] creezalird:
Thank you for the explaination. Just asking out of curiousity. :D
[G1 Android Development] geokuttan:
I tried both the Sdext and SD card . I have ext4. First i tried using the "Let system Decide" and then i tried SDext. I like the ability to move and app back forth from internal to external. But my memory keeps getting lower. :) Maybe its because of the data being stored internally or something. I wish I could get the app2sd script from superaosp and put it in ADS cuz magpie is the fastest gingerbread i have ever seen...
[G1 Android Development] AndDiSa:
... probably it's the data and dex-files, because system dex-files are going to /data, too, which will need already around 40MB.

One hint: clean /data/local/downloads

A second hint: try to use customMTD, so you can get some additional space for /data.
[G1 Android Development] billquinn1:
This is off the subject a little bit.

I updated from 4/2 to 4/16-1. I remember reading somewhere to wipe cache so I wiped all the caches I saw in clockwork. When everything was done loading, the app drawer in launcher 2 would not open but instead give a acore crash message and reload the desktop. I reinstalled ADW and everything works perfect.

My question is, what caches do I need to wipe to do a no wipe update ... or better yet is it possible for you to include the code to do it in the updater script? It is all good with ADW so no big deal.

EDIT. I don't have the power controls bar in the notifications so I guess I will need to wipe.

Thanks,
[G1 Android Development] jdb78:
AndDiSa posted which caches to delete already. I'll quote it here:

When I switched from odexed to non-odexed I deleted all caches mentioned above using terminal emulation in advance before rebooting to recovery to install the ROM.
[G1 Android Development] newellj79:
Thanks for the info. Ill probablly try the magpie version tonight to see how it stacks up against roalex's.
[G1 Android Development] ThdDude:
Roalex is using magpie now
[G1 Android Development] billquinn1:
Clearing the caches did fix the app drawer issue but not the "no power control in the task bar" issue. I wonder if it is in 4/16 but not 4/16-1?
[G1 Android Development] creezalird:
Nope, it is still in 1604-1

Currently running it flawlessly
[G1 Android Development] AndDiSa:
It's in both versions, but there may be issues when you have already an "old" power widget configuration, for example from a different rom. I noticed this yesterday when I was playing around with COSSettings from roalex. To verify this, you can look at the logfile, there should be some errors regarding the power buttons. At the moment the only chance is to wipe data ... :(
[G1 Android Development] billquinn1:
Just flashed 4/16 and it is not working for me there either. Your theory is probably correct since I used Titanium backup when I flashed 4/2. Whatever settings were in the last rom are probably still there. I don't have time to wipe and retry right now but I will give it a go tonight.
[G1 Android Development] hrk:
I guess the settings should be here: /data/data/com.android.settings/shared_prefs/com.android.settings_preferences.xml

By removing the offending lines (or deleting the whole file), you could get clean settings to start without wiping everything.
[G1 Android Development] billquinn1:
Those settings didn't contain anything other that you standard settings.

<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<boolean name="sound_effects" value="true" />
<boolean name="com.android.inputmethod.latin/.LatinIME" value="true" />
<boolean name="jp.co.omronsoft.openwnn/.OpenWnnJAJP" value="true" />
<boolean name="auto_time" value="true" />
<boolean name="com.android.inputmethod.pinyin/.PinyinIME" value="true" />
<boolean name="adb_notify" value="true" />
<boolean name="allow_mock_location" value="true" />
<boolean name="haptic_feedback" value="true" />
<boolean name="location_gps" value="false" />
<string name="date_format"></string>
<boolean name="lock_sounds" value="true" />
<string name="vibrate">always</string>
<boolean name="com.swype.android.inputmethod/.SwypeInputMethod" value="true" />
<boolean name="enable_adb" value="true" />
<boolean name="dtmf_tone" value="true" />
<boolean name="location_network" value="true" />
</map>

I'm thinking there must be another file. I will look around.
[G1 Android Development] Effdee:
sqlite3 /data/data/com.android.providers.settings/databases/settings.db 'select * from system where name="expanded_widget_buttons";'

:D

you should get something like:

1481|expanded_widget_buttons|toggleWifi|toggleGPS|toggleSound|toggleNetworkMode|toggleMobileData

try deleting /data/data/com.android.providers.settings and rebooting
[G1 Android Development] AndDiSa:
The settings can be found here:

/data/data/com.android.providers.settings/databases/settings.db

Edit: Effdee was faster ... ;)
[G1 Android Development] billquinn1:
That was it. :) I did:

#mv /data/data/com.android.providers.settings/databases/settings.db /data/data/com.android.providers.settings/databases/settings.bak

#reboot

Works like a charm.
[G1 Android Development] Effdee:
doubt it will work

the problem is the settings.db already exists so it doesn't get updated

you would either need to inject a new record or just sledgehammer it into recreating the whole db

like above by deleting it
[G1 Android Development] AndDiSa:
if it's not working on the phone directly, it should work by copying locally, changing and uploading again, doesn't it?
[G1 Android Development] Effdee:
I think to do it properly you would need to mess with

frameworks/base/packages/SettingsProvider/src/com/android/providers/settings/DatabaseHelper.java

and bump the version up

private static final int DATABASE_VERSION = 57;

that way it sees that Settings.db needs to be updated

BUT I haven't looked closely enough at that to see if it *is* the way it should be done

call me lazy but tbh I would be tempted to just test and inject the required records with a script at install time

eventually the script will be redundant

thinking about it

did CM need a wipe for it to work properly?

because looking quickly at CM code I can't see an update/insert in it.
[G1 Android Development] roalex:
what about something "like" this (don't mind the commands but the process)
[G1 Android Development] Effdee:
:eek:

did I open a can of worms and now everyone will be h4x1ng dbs with sqlite3 scripts :D

I haven't looked at sms I seldom use it myself which is ironic as I bought my first mobile because of the txt ability
[G1 Android Development] roalex:
Just a script i borrowed in case the sqlite f_sync hack im using on the rom messes up >< But the idea should work for this too.
[G1 Android Development] azrash:
AndDiSa, is it possible for us to send application data to sd-ext?:) i came from ezterry's froyo AOSP and this option saves internal memory and because the apks are in internal, opening applications is much faster, for me i guess :p

great ROM! very stable and fast
[G1 Android Development] Effdee:
seems you want the ddb option of firerat aio script
[G1 Android Development] mejorguille:
Hey! I'm not sure of a better place to post this so I might as well do it here:

http://r.cyanogenmod.com/#change,4677

If you look, that is the version bump for 7.0.1. One of the many devices listed are the G1 and MT3G!! The release was postponed for a few days to sort out some issues with other devices, but this means that the G1 will get official support again from CM! I will definately be flashing that to my old G1 lol.
[G1 Android Development] kingjehu:
On the Android Guys stream last week, Cyanogen said there will never be official CM support for the HD2 (Leo) but it's listed there. There will be CM7 on the G1 eventually (he told me on twitter) but I wouldn't count this as evidence. Right now, unofficial builds can be made by anyone and they work well for the G1, but it's just not supported yet. There are a few things left to work out before that happens.
[G1 Android Development] mejorguille:
Yeah, but if you look at the 7.0.0 bump, the dream_sapphire branch is not mentioned. So this is definitely a step forward. I follow his twitter too so I've heard him say that the G1 is not off the table, just not high priority either. And I didn't see the podcast, but are you sure that the HD2 is off the table? It's very active in gerrit.
[G1 Android Development] Poppu:
If you click on the "Dream - Sapphire" change, you will see that it was mentioned. The change is :

from "ro.modversion=CyanogenMod-7.0.0-RC0-DS" to "ro.modversion=CyanogenMod-7.0.1-RC0-DS"

and from "ro.modversion=CyanogenMod-7.0.0-RC0-DS-KANG" to "ro.modversion=CyanogenMod-7.0.1-RC0-DS-KANG"

So I believe they keep it only for KANG versions right now.
[G1 Android Development] jdb78:
Sorry guys, but this ain't a CM7 thread. It's about Terry's AOSP and (I assume) what Firerat, AndDiSa and the other contributers made out of it.

If you want to chat about CM7 why don't you use a CM7 thread instead? Thank you!
[G1 Android Development] Poppu:
You' re right. Sorry.
[G1 Android Development] geokuttan:
I second that....it would be awesome to use the app2sd format ezterry used in his froyo AOSP. this will give almost unlimited app space. :)
[G1 Android Development] AndDiSa:
As Effdee already stated: you can try to use AIO from Firerat and use the ddb option, so data will be moved to /sd-ext and you will get more space on /data.

At the moment I do not exactly know, what's the a2sd implementation in ezTerry's froyo AOSP, but principially there cannot be much differences to Firerat's a2sdext implememtation. Probably the main difference is the following: Firerat's implementation locates the dex-files "near" to the location of the application (/system/ -> /data/dalvik-cache, /sd-ext/ -> /sd-ext/dalvik-cache), while the "old" implementation is moving all dex-files to /sd-ext/dalvik-cache.
[G1 Android Development] ezterry:
Just a slight varient of the old apps2sd script method..

Gui to select dex2sd, app2sd, data2sd

Then on boot an init scrip made the bind mounts to match the users choice (with some logic to move the data .. no space checks so backups recomended)... but I never recommend all three it slows down the phone.

Thus on a mostly odexed version of this rom using the sd-ext for most apps it ought to be almost the same as checking dex2sd and app2sd leaving plenty of room for data on MTD.. or a user that needs to consider uninstalling un-used apps from time to time.

(Really it was a way to hack a type of apps2sd on an otherwise mostly un-modified OTA rom.. intended to be very simple to use but firerats aio has more features if you really can't stand magpie)
[G1 Android Development] AndDiSa:
... there is another topic to consider: if we want to go for xVold Firerat's magpie solution will work like a charm. If you in contrary use AIO and move dex and/or data to sd-ext, there is no need for xVold any longer, because /sd-ext need to be mounted always, otherwise you will get FCs.
[G1 Android Development] geokuttan:
If using AIO slows down the phone...Firerat's method would be the best...I love the speed of magpie...there is no lag wat so ever...even home in memory is the best compared to other gingerbread roms...It would be awesome if we got more space for apps...but if it slows down the phone...then i would so not go for it..A cool feature would be an option to select which app2sd method you want when you flash the rom..hehe :D
[G1 Android Development] azrash:
i think it will only slow things down when all the stuffs are in sd, like ezterry said. because the phone is trying to access the sd card which has its own limitation. i think it is best to stick to either one. either send apk to sd-ext or send apks' data to sd-ext.

I used the datatosd back in ezterry froyo's, and appstoext(magpie) in gb. it is just that i have this weird of thought in my mind that keep on telling me that apk in internal and data on sd will load faster than the other way around coz data size of app is not that big. LOL, idk :p

one question though, is it safe to run firerat's aio ddb script side by side with the built in magpie (as in magpie set to internal only) :)

thanks!:D