yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] ezterry:
1) market: before any complaints make sure it works on other 2.3.3 roms first.. market uses various filters to make sure you only see certain apps.. also use the market webpage to try and instasll the items it won't let you if you can't see it on the phone but might tell us why.

2.3.3 is api level 10, 2.3.2 was api level 9.. some apps seem to allow 9 but not 10..

2) The touch issue is already on the issue tracker.. (and indicates the bottom of the screen as well in the description text.) Any Idea of how android gets the numbers and how its diffrent w/o the multi-touch permission are welcome.

When the permission is removed the phone shows the correct multi touch events (or at least more correct).. but apps will think there is no mt.. thus in many cases will ignore mt events. But for the life of me I can't see anywhere in the code where the event reading code checks the mt permision. So I'm missing something..
[G1 Android Development] crypticc:
edit:reflashed gapps and google sync re-established links to sd mnt I guess.

Rom is all good - thanks
[G1 Android Development] roccoadam32:
found a bug if you disable or uninstall latinime and go to settings about phone it force closes
[G1 Android Development] crypticc:
Tell you what.

Ezterry your summary change log doesn't do the improvement over 2.3.2 justice. This rom is a keeper.

I might even reinstall my swype beta I uninstalled for performance reasons when I left cm6. :D
[G1 Android Development] tnpapadakos:
so, if you mess with the rom, and change it, it creates a bug, you mean
[G1 Android Development] roccoadam32:
no one asked you sir how is taking the on screen keyboard which is a waste of ram for the g1 messing with the rom lol get a life dude
[G1 Android Development] tvall:
using things in ways they were not intended can have unexpected side effects
[G1 Android Development] roccoadam32:
lol your supposed to be able to disable it thats y there is a option u guys are nutts im not even going to discuss this further rom runs great
[G1 Android Development] androidcues:
Well its simple. I let the latest rest and settle in overnight. Then I take it to work and just leave it on alll day long using it to organize some files on the sdcard and delete pics. Nothing heavy but when I started playing with it after work oy vey..the battery was still at the highest level I've ever seen any android phone after a whole day...much less the G1.

ezGingerbread may be better than the dreams intended firmware.... and that's two years ago!

Able to download like a champ. No problem! No market issues...nothing! I might as well swapout sim cards and drive dream to work tmw.
[G1 Android Development] tnpapadakos:
i wasnt insulting you, i was just differentiating between a rom having a bug as it was released, and creating a bug after changing something

why you gotta get all nasty?

you better check yourself before you wreck yourself

no big deal
[G1 Android Development] AndDiSa:
You can download it from their website and install it manually, then it works fine.
[G1 Android Development] yokonunz:
Thanks terry!! 2.3.3 run much smoother!!!
[G1 Android Development] SubVert:
Hmm, looks like something may still be amiss.

I just did a wipe in recovery, followed by a SuperWipe, then installed the 309 version.

In Settings - Application Settings - Preferred install location, I have three options:

Internal device storage

Removable SD card

Let the system decide

No sd-ext option.

I just tried again with the 304 and 306 versions, wiping first each time, same thing, no sd-ext option.

I have the move to sd-ext button available for the individual apps under Manage Applications, just the install location option missing.

I went back to the earliest version I have, from 0224 and the option is present there :

Internal device storage

Removable SD card

SD Extension partition

Let the system decide

Anyone else have this with the latest version, or is it just me?
[G1 Android Development] :
Same here too, no option for SD Extension Partition.
[G1 Android Development] psilofx:
Yes, but after installation of the app in to internal memory or SD card you can move it to sd-ext via Settings - Applications - Manage Apps - click on aplication in the list - Move to sd-ext button.

As it's possible to move an app after installation it's not a showstopper for me anymore...
[G1 Android Development] roccoadam32:
latest magpie works fine for me install location is on the manage applications menu and i can move my apps to sd ext fine
[G1 Android Development] AndDiSa:
I cannot verify at the moment, because I am just running a yet unpublished version of ADS_magpie ... here the sd-ext option does exist, so be sure the next releases will have that option built it.
[G1 Android Development] jdb78:
I run the 20110309 version and I do have the option "sd-ext" within "Settings - Application Settings - Preferred install location". I do not use MTD.
[G1 Android Development] AndDiSa:
... so then there must be something else preventing the option to appear.
[G1 Android Development] ZilverZurfarn:
So do I.

Internal device storage, Removable SD card, SD Extension partition and Let the system decide. <edit>I have an ext4 sd-ext partition</edit>
[G1 Android Development] :
Well erm thanks but I'm not a noob and am well aware of this, my issue is with 212 apps using that method is just the worlds biggest pain in the arse and have no intention of wasting the time doing it but thanks again anyway.

@ AndDiSa - Only thing I can think of is maybe because my Ext partition is ext3? I will try doing an ext upgrade and seeing if it reappears.
[G1 Android Development] AndDiSa:
I cannot imagine, that this could be a reason, because a2sd is working it's only the menu item which is missing.

If sd-ext is not working for you, please provide me with a logcat, especially the first part may be interesting, when /sd-ext is mounted.

Edit: my partition is ext2
[G1 Android Development] :
Its wasn't the problem but welcome to the world of error tracking, we have to eliminate all options ;)

The sd-ext is present doing the df command but it is NOT working corrctly as even with moving Dalvik to ext I still can't install all my apps without the wonderful 'Out of memoery' errors as my /data partition is obliterated and this has always been a problem for me with Magpie and one of the reasons I have rarely tried the rom from you. I have never had the desire to work out what the problem is as I just skip back to Froyo and have never really taken the time to understand Magpies implementaion which is my bad on that one.

I'm gonna run some tests tonight as need my phone for tethering at the moment, gonna run Terrys release in post 2 and see how FR's AIO works with it and also if it can help the problems I'm experiencing with your build. I just need some inspiration to get me moving as I've never really liked Gingerbread, even the taste of the stuff gives me indigestion :D
[G1 Android Development] sb56637:
20110309 is working well for me, with the SD-EXT option in the app install location. I'm using a 500MB EXT4 partition.

However, I did notice that two manually installed APK were installed to the internal memory despite me setting the SD-EXT option in app install location. But at least it let me manually move them. The market apps seem to be mostly going to the SD-EXT by default.
[G1 Android Development] jdb78:
I use ext3 for sd-ext so ext2, ext3 and ext4 seem to work. I just wonder why some ppl see the menu item and some do not. Maybe device related?

EDIT: Maybe not. Shadow runs the same hardware, radio and SPL as I do. We even use similar SD cards... So.. I'd better shut up, can't contribute any useful :]
[G1 Android Development] AndDiSa:
Normally there should be both /data/dalvik-cache *and* /sd-ext/dalvik cache. /data/dalvik-cache contains all the dex of ROM installed applications, while /sd-ext/dalvik-cache contains dex files which are on /sd-ext. Probably it's a mess up with the dalvik-caches, specially when switching between different ROMs. You could try to go to recovery, mount /data and /sd-ext and clear all caches and then reboot.
[G1 Android Development] BibleBelt:
I just gave this another try. I'm one of the guys with a Magic, not getting wifi to work with this kernel. Unfortunately your new release didn't change this.

After booting I still get following dmesg output

<6>[ 95.935699] TIWLAN: Driver loading
<4>[ 95.936431] wifi_probe
<7>[ 95.936645] sapphire_wifi_power: 1
<7>[ 96.147796] sapphire_wifi_reset: 0
<7>[ 96.197753] sapphire_wifi_set_carddetect: 1
<7>[ 96.198211] mmc0: card_present 1
<6>[ 96.198425] mmc0: Slot status change detected (0 -> 1)
<6>[ 96.221038] snd_set_volume 256 0 2
<6>[ 96.755218] request_suspend_state: wakeup (3->0) at 91211991476 (2011-03-11 15:50:16.446951220 UTC)
<3>[ 98.735931] mmc0: Command CRC error
<3>[ 98.784118] mmc0: Command CRC error
<3>[ 98.803985] mmc0: Command CRC error
<3>[ 98.839752] mmc0: Command CRC error
<3>[ 98.848815] mmc0: Command CRC error
<4>[ 98.896209] mmc0: card claims to support voltages below the defined range. These will be ignored.
<3>[ 98.949218] mmc0: error -110 whilst initialising MMC card
<3>[ 106.205963] tiwlan_module_init: Timed out waiting for device detect
<4>[ 106.206848] wifi_remove
<7>[ 106.207092] sapphire_wifi_set_carddetect: 0
<7>[ 106.207458] mmc0: card_present 0
<6>[ 106.207672] mmc0: Slot status change detected (1 -> 0)
<7>[ 106.207946] sapphire_wifi_reset: 1
<3>[ 106.324554] mmc0: Error setting clock rate (-22)
<3>[ 106.402893] mmc0: Error setting clock rate (-22)
<3>[ 106.404815] mmc0: Error setting clock rate (-22)
<7>[ 106.431671] sapphire_wifi_power: 0
<3>[ 106.463012] mmc0: Error setting clock rate (-22)
<3>[ 106.482879] mmc0: Error setting clock rate (-22)
<3>[ 106.484954] mmc0: Error setting clock rate (-22)
<4>[ 107.081787] WiFi disable vreg_wifi_osc.

Last weekend I played with CM7, which has a 2.6.37.1 kernel and there wifi worked. Is there anything I can do comparing a working and a non working setup that would help you?
[G1 Android Development] :
Definitely no sd-ext dalvik hence why I used the AIO, and after fastboot wiping and running Superwipe twice I can pretty much rule out your suggestion of mounting them to clear them. As I said I will test further when I have the time and the inclination. Thanks for the explanation though, I'm sure someone will find it useful.
[G1 Android Development] farmatito:
I'll take a look at it myself as soon as I have some spare time.
[G1 Android Development] AndDiSa:
Most likely you know, but AIO provides almost the same init-scripts as included within the ROM. There is no need for them, I am almost sure, that the AIO-scripts are overwriting / interfering with the built in scripts and are the root cause for your problems.
[G1 Android Development] :
Sorry again to burst that bubble too.

I ran this clean without gapps or even touching the AIO and I know the scripts are included but for whatever reason are not mounting correctly hence why I thought to have a play with it. So the AIO is not to blame either unfortunately :(

I feel your frustration with this fella trust me but hopefully I can find the problem tonight, just a ball ache I need my phone as a tether today.

Edit: I'll post a logcat of first boot to pastebin when I reflash, two pairs of eyes are always better than one and hopefully together we can get this resolved :)
[G1 Android Development] hrk:
(regarding Nexus Live Revamped & other live wallpapers)

Seeing that you have a Dream: does it really work for you? [ed: I am talking of FrooByLazlo ROM, see below]When I choose it from the list, I get the "set wallpaper - options..." activity but nothing appears on screen. If I go to the options, and then press BACK, the wallpaper appears. In a similar way, sometimes I don't see the wallpaper. I press MENU -> SETTINGS -> BACK and... there it is. It started happening w/ the first OpenGL release, so I thought it was an app issue... but if you say it's working fine for you, I am puzzled.

Ok, today I had some time to tinker a bit.

ADS 309 (2.3.3):

Market (phone): a search does not return any result.

Market (web/pc): it asks for a different phone, as this one is not supported

Manual: didn't try it, sorry.

COS GB "310" (2.3.3):

Market (phone): a search does return the app and I can install it.

Market (web/pc): it sends the app to the phone and installs it

FroyoBylazlo (2.2.?)

Market (phone): a search does return the app and I can install it.

Market (web/pc): it sends the app to the phone and installs it

So I guess it's related to ADS. i didn't try a plain Terry's build, I may do it later to see if it changes anything.

Hmmm... I am sorry, but I think my report here and the bug description are different. The problem is not related to simple "taps". If you move your finger out of the edge and came back, it will not be recognized as long as you keep your finger on the screen. it doesn't "feel" the finger anymore, unless you exit from left/top or raise your finger.

Anyway...

ADS: right+bottom edge bug.

COS: right+bottom edge bug.

FroyoByLazlo: works fine.

If you hold the first finger on the screen and use the second one to try and trigger the bug, it doesn't get triggered (but when you exit/enter, the dot runs to the x/y line of the other finger).

Multitouch Visible test is an open source app, can its source code be useful to guess what's happening?

EDIT: source code just draws circles centered on MotionEvent.getX()/getY(), so it really doesn't do much. :)
[G1 Android Development] hrk:
Ok, I don't think it's a bad RAM/NAND here, because when this morning I rebooted your ROM and it self-rebooted once a few seconds after the home screen appeared. But then... when I installed COS to see if a different 2.3.3 would allow me to install Nexus Revamped, I choose the FULL 88MB version and it installed, booted and run fine with no hiccups.

The same goes for FroyoByLazlo: install, boot, run without any issue or reboot.

Every single installation (and COS was done twice because of my mistake activating my google account before enabling sdext storage) has been done after Ohkasa's full wipe.

This doesn't add anything useful to debug the issue, but I guess it clears my poor RAM/NAND. :-)
[G1 Android Development] farmatito:
Yes a link to this kernel so that i can download it.

While running this kernel do:

adb pull /proc/config.gz .

and post config.gz

One more test you can do is:

unzip my kernel

extract modules.sqf

unsquashfs modules.sqf

copy wlan.ko to your sdcard

insmod /sdcard/wlan.ko
[G1 Android Development] hrk:
ril settings to enable higher speed for 2G/3G

I have changed two ro.ril settings in build.prop to enable higher data speeds. They come from a post in CyanogenMod forums which was posted here on XDA too.

I use Speedtest.net app to check my network speed and I've seen a 3x change for 3G, both upload and download, as per attached image.

I haven't yet reached the top speeds of CM6.1, but I still haven't tinkered with all the available settings.

The ones I have changed are:

ro.ril.hsxpa -> 2

ro.ril.gprsclass -> 12

I am wondering why ROMs don't come with these settings enabled by default: could it be that they don't work well in the USA? (Or could it be that USA carriers don't want people to get higher speed?)

EDIT: these are the settings found on a stock HTC DESIRE/BRAVO sold in Italy.

[ro.ril.ecc.HTC-ELL]: [92,93,94]

[ro.ril.ecc.HTC-WWE]: [999]

[ro.ril.enable.a52.HTC-ITA]: [1]

[ro.ril.enable.a53.HTC-ITA]: [1]

[ro.ril.enable.a52]: [0]

[ro.ril.enable.a53]: [1]

[ro.ril.hsdpa.category]: [8]

[ro.ril.hsupa.category]: [5]

[ro.ril.hsxpa]: [2]

[ro.ril.disable.fd.plmn.prefix]: [23402,23410,23411]

[ro.ril.enable.sdr]: [0]

[ro.ril.vmail.23415]: [1571,BT]

[ro.ril.vmail.27203]: [171]

[rild.libpath]: [/system/lib/libhtc_ril.so]

[ro.ril.enable.dtm]: [1]

[ro.ril.gprsclass]: [12]

[ro.ril.def.agps.mode]: [2]

[ro.ril.disable.power.collapse]: [1]

[ro.ril.avoid.pdp.overlap]: [1]

[ro.ril.enable.prl.recognition]: [1]

[init.svc.ril-daemon]: [running]

[ril.reload.count]: [1]

[ro.ril.nv.compare.result]: [128]

[ril.preferred.language]: [3:it,en,de,fr,sv]

[ro.ril.ecclist]: [112,911]

[ril.ecclist]: [112,911]

[gsm.version.ril-impl]: [HTC-RIL 2.2.0028HM (Sep 20 2010,22:33:44)]

[ro.ril.current.ip.address]: [109.119.250.160]
[G1 Android Development] AndDiSa:
I had this changes in my old Superfly-ROMs included and there were some people (if I remember well they were from US) complaining that they had problems with data connection. Here in Europe it should work fine.
[G1 Android Development] yokonunz:
Why android settings is always running and eats 10mb of ram constantly?
[G1 Android Development] ezterry:
Um.. probably because you are checking what is running from the settings.apk thus it must be running to show you what is running....
[G1 Android Development] hrk:
A true and pure case of Heisenberg principle of uncertainty indeed...
[G1 Android Development] yokonunz:
Ahahhhaa. I will verify this with a third part task manager.
[G1 Android Development] BibleBelt:
Ok, for point 1 and 2 see attached zip file. It contains the boot.img I extracted from the update-cm-7.0.0-RC0-DS-KANG-signed.zip and the config.gz. Is that enough information for you?

Trying to put your wlan.ko into the kernel gives

localhost ~ # insmod -f wlan.ko
insmod: can't insert 'wlan.ko': invalid module format

and the corresponding dmesg output

[ 1519.882812] wlan: version magic '2.6.37.3-cyanogenmod preempt mod_unload ARMv6 ' should be '2.6.37.1-cyanogenmod+ preempt mod_unload ARMv6 '

I thought the -f option to insmod would have that test to be skipped, but apparently it didn't.
[G1 Android Development] hrk:
Lil' bugs...

This is the third time it happens on me, but this time I have adb/ddms near me. :-)

Screen is off, hit anything which should wake it up, the wallpaper appears but the lock screen is invisible. If I slide my finger where the "lock" is, vibration starts and I guess that it unlocks. The menubar can be seen and I can draw the notification bar down.

I can hold POWER and, if I know where to touch, I can reboot the device.

While I was writing...: change! The lock screen is appearing, but after I unlock, the hom does not appear. The notification bar "works", in that I opened Gmail, read a mail, but when I pressed HOME, I could only see the wallpaper.

Touching where the app drawer is made the home visible but unresponsive (the app grid button is highlighted).

Logcat attached...
[G1 Android Development] AndDiSa:
Yes, it's out of memory ... I had a similar error at the beginning of February. I remember well, because later I increased vm heap-size to 24m for some time. I never got it again, so I returned to 16m. Might be a problem when compcache is already used fully but additional memory is needed. Did you run live-wallpaper or other memory consuming applications?
[G1 Android Development] muldy:
I have exactly the same problem, already posted a logat on this thread.

It normally happens after a 24h+ uptime.

Tried other launchers, tried to reduce memory consuming apps, and tried using sdcard swap.

Only got insignificant uptime extensions :(

I use ezGingerbread stock. (no addons, no mods)
[G1 Android Development] hrk:
No, I am not using any live wallpapers (I can't install them from the market with this ROM, don't you remember? ;-)...) and during the whole day I often looked at the memory usage to see 21/25 MB free thinking "Man, this ROM rocks... COS-DS had my memory used at 100% and lagged badly... this one lacks the power notification and the (super)power widget but it's so smooth I can't use anything else..."

So... it happened with the phone idling. Unfortunately I have rebooted :|... but if/when it'll happen again, how can I dump a useful memory map/usage? I could enter the settings, so next time I'll start by reading those values.
[G1 Android Development] muldy:
I've got a bug report of it happening:

could it be this: http://code.google.com/p/android/issues/detail?id=15135 ?
[G1 Android Development] Poppu:
I had some different bug but similar in some points :

- when entering in a textbox, keyboard dos not appear on-screen. However the main application is reorganized, and if I click on the space where keyboard is supposed to be, it acts as if keyboard was there.

- on other occasions, keyboard appears normally and I can type my text nothing appears in the textbox. But text is here : dictionnary is working and proposing me some words, and if there is a dynamic drop list (e.g. google search box) the list is giving me some propositions. And if I click OK, the application is using the text I just entered.

So in both cases the problem is purely graphics. And it happens only with the latter ROM (latest from ezTerry, no magpie or kernel change).
[G1 Android Development] hrk:
Now that I think about it, I had some strange moments where I thought the keyboard was supposed to appear and it wasn't... maybe it was the same issue!

For the record, I'm using AnDiSa's build.
[G1 Android Development] muldy:
Yes, had the same problem, changed to symbol keyboard...

It dind't update the layout... but when I pressed a key a symbol was printed.

Weird stuff
[G1 Android Development] AndDiSa:
Looks to me very similar, most likely the same, especially because of the exceptions which were thrown at the same place in the code (android.view.Surface.lockCanvas(Surface.java:314)
[G1 Android Development] AndDiSa:
Same problem today for me: I noticed a difference since three days. First compcache was almost not used, then yesterday it started to get more and more filled up. Today now the problem with the empty screen. Looks to me like a memory leak within surface_flinger(?), or at least a component which is related to it.
[G1 Android Development] ggonsalv:
Silly question but how do you check comp cache usage?

I know you can use free on either adb shell or terminal

for RAM & swap partition.
[G1 Android Development] guitargler:
I'm impressed. I was running AnDiSa's magpie, but then decided to play round with Honeycomb and then Cos-DS. I used Cos-DS for a couple of days and it was slow and horrible; I'm now on AnDiSa's latest magpie build and it's probably the best rom I've ever used. All of the glory of Gingerbread on my G1, and now Messaging finally works again without crippling the entire phone's usefulness (my experience on Cos-DS). Good work, can't wait to see this completely finished. I can sense some donations flying around once I have a job. :)
[G1 Android Development] AndDiSa:
Either on the shell you can use

compcache stats

or you can use SetCPU. Here on the info page you can see the different types of memory and their usage.
[G1 Android Development] Poppu:
Or you can use the "meminfo" app which is quite convenient to see all memory details.
[G1 Android Development] AndDiSa:
Little update to that problem: yesterday I merged some bugfixes from gingerbread/master. This didn't solve the problem completely, but it improved the situation in the following way:

- an exception is thrown to logcat when an out of memory error on gralloc occurs

- the phone continues to work, i.e. there is no longer the problem with the black screen / only the wallpaper is shown
[G1 Android Development] jdb78:
SMS problem

I still suffer from the missing sms problem. Yesterday my wife sent a couple of messages to me but they never showed up. I did not get any notification nor any message in my inbox. Unfortunately my logcat stopped working (I was saving logs every hour but I tried the new swype beta, 9MB big so I guess alogcat just got killed) so I can't provide logs.

This is getting serious for me so is there anything I can do to help finding the source of the problem?
[G1 Android Development] AndDiSa:
This might be the problem for receiving sms, too. What kind of services are running? How much memory do you have "free" normally (SetCPU: MemFree + Cached)?
[G1 Android Development] jdb78:
With Swype installed:

MemFree: 2616KB

Cached: 22724KB

swype not installed (values varied from 2260 to 3784):

MemFree:3784KB

Cached:21932

EDIT: BTW I don't really need swype due to the hardware keyboard. I just wanted to try. :] But I had that missed sms issue before I installed swype as well. I do not use live wallpapers as well. I use autostarts to reduce the amount of running apps.