yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] cj chitwood:
Not that anyone cares, but I've restored from a NAND backup to COS-DS-Full-04122011. It was pretty stable for me before. However, while I've not noticed any major issues yet, the phone DID lock up for a good minute or so before becoming responsive again, and ADB isn't working like it should, but these were not problems before. It speaks to the inconsistencies I've noticed.

For half of us to be using the same exact hardware, and the other half to mostly be using the same exact other hardware, it seems odd to me that so many different configurations are both best and worst for the phone. I believed it to be personal preference before, but at the moment I wonder if the hardware itself isn't suspect. I'm wondering if our internal flash memory is wearing out for some of us, causing wipes to seem to only partially work (I'm sorry, one wipe should do it -- if you have to wipe three times to erase your phone, SOMETHING IS NOT WORKING CORRECTLY).

Anyway, I've had good results before with this version, and I'm going back to it. I'll post if it stays rock stable for a while. I'll reboot tonight before bed, and we'll see how long it takes for the phone to crap itself, if it ever does.
[G1 Android Development] bmtdan:
the setup wizard keeps force closing when i get to the end of the phone setup on the latest release

edit nevermind reboot fixed the issue
[G1 Android Development] vion77:
Yes but this method dot work for me! I asked to find how to modify some files to add a town in the weather app town list.
[G1 Android Development] luminoso:
Is the new security bug already fixed in this version?

Link: Critical Android Vulnerability: Use Precaution on Public WiFi
[G1 Android Development] cplusplus:
need help

someone can upload rom to mediafire for me??

because in china, i can't download rom anymore, i can't connect to anywhere:mad::mad::mad:
[G1 Android Development] Effdee:
Plenty of people in China have worked out how to get round your dictatorship's Firewall

time you did the same
[G1 Android Development] WongHokZau:
Thanks for replying.I have pressed the button "Mount R/W", when i locate on sd card or someplace else it works,means can be switched.But when locating on System/font/...,nothing change when pressing the "Mount R/W".If i succeed to switch it.everything would be done.But i just wonder why it change nothing when pressing the button mentioned above.

i think i have had my phone root, i use 16/05 rom.and when i install BusyBox(to verify whether i have rooted),it show "your phone is rooted".i'm still working on it,your help is appreciated......
[G1 Android Development] Effdee:
every Android file manager I have tried is crap

Honestly terminal is much faster

su
mount -o rw,remount /system
cp /sdcard/myuberfont.ttf /system/fonts/

Honestly learn to use a shell, way better than stupid file managers
[G1 Android Development] WongHokZau:
My font file names "DroidSans.ttf"

when i try

su

mount -o rw,remount /system

cp /sdcard/DroidSans.ttf /system/fonts/

it shows

cp: can't creat systm/fonts/DroidSans.ttf ':file exists
[G1 Android Development] Poppu:
So it means your file already exist.

try :

ls /system/fonts/DroidSans.*

if you have a result, it means your font is already installed.

If really you want to replace the existing file, you can try

su
mount -o rw,remount /system
cp -f /sdcard/DroidSans.ttf /system/fonts/
[G1 Android Development] WongHokZau:
Two ways you mentioned above i had tried.Same problem exists.

when i tried

ls /system/fonts/DroidSans.ttf

showed

/system/fonts/DroidSans.ttf

when trying

su
mount -o rw,remount /system
cp -f /sdcard/DroidSans.ttf /system/fonts/

showed

cp: can't creat '/system/fonts/DroidSans.ttf': file exists

i really don't know what to do now...
[G1 Android Development] b1czu:
so try to remove it first by rm and then copy

rm /system/fonts/DroidSans.ttf
cp /sdcard/DroidSans.ttf /system/fonts

post back what u get
[G1 Android Development] Poppu:
OK, this means that there is already a font with that name on your system.

<STRIKE>One more possibility : the file can not be copied because it is already used.

In this case, you can try to do the following :

- reboot on Recovery using ClockWork Recovery

- plug the phone on you're computer with your USB Cable

- connect to the phone from your computer with adb using "adb shell" command.

- from the recovery (on your phone) select "Mounts and storage"

- select "Mount /system"

- select "Mount /sdcard"

- try again the "cp -f" operation (you may skip the "su" command).

- go back to previous menu on the phone and choose "reboot"

But I did not try it, so I'm not sure this will work.</STRIKE>

Ok, I tried it on my phone but it seems there is only one big file called fonts.sqf in the /system/fonts/ directory instead of all the usual *.ttf files when I'm in Recovery, so it will not work... So You will need someone with better skills than me, sorry.
[G1 Android Development] ezterry:
Its a squashfs disk image. A readonly compressed filesystem mounted on boot. (Cuts the fonts size by 40%)

To change the fonts you either need to update the fonts.sqf or remove it and restore all the font files (but loose the system space needed for the uncompressed fonts)
[G1 Android Development] Effdee:
:D

lol

.sqf is read only

so learn about Linux and squashfs

this will help in the short term

su
cp /sdcard/DroidSans.ttf /data/
mount -o rw,remount /system
echo "\#\!/system/bin/sh" > /etc/init.d/07newfonts
echo "mount -o bind /data/DroidSans.ttf /system/fonts/DroidSans.ttf" >> /etc/init.d/07newfonts
chmod 700 /etc/init.d/07newfonts
./etc/init.d/07newfonts

only reason I put the file on data is I have no idea how much space you have left on system
[G1 Android Development] xploit:
wow this ROM is the fastest ....thanks roalex!! is working great here on my touch 3G classic ...just to let everyone know there was an update to this rom 5-17-2011
[G1 Android Development] WongHokZau:
first i tried

rm /system/fonts/DroidSans.ttf

showed

rm: remove '/system/fonts/DroidSans.ttf'?

a symbol"?" appeared

but when trying

cp /sdcard/DroidSans.ttf /system/fonts

still

cp: can't creat systm/fonts/DroidSans.ttf ':file exists

thank for that.....
[G1 Android Development] WongHokZau:
:)thank your so much.Let's work it out together.i will keep going........
[G1 Android Development] Effdee:
like I said above

read about linux and squashfs

or just use the script I gave you
[G1 Android Development] WongHokZau:
i've tried that,it shows

./etc/init.d/07newfonts: #!/system/bin/sh: not found

i don't have many ideas on linux or squashfs,so i just try the code your gave.that's what it shows.....thanks......
[G1 Android Development] Effdee:
in recovery?

instructions were intended for use in the ROM not recovery

just boot it will work

make sure that 07newfonts script is in /system/etc/init.d/

and that data was mounted before you copied the fint to it

confirm by looking at the output of df command
[G1 Android Development] xploit:
guys just a quick question... im trying to install the Honeybread Theme which is an .apk file ...how are you guys installing it? using ADB? whats the command?

reason I ask if because I get the message saying NOT ENOUGH SPACE.

Using

> hboot-1.33.0013d

> radio-2.22.28.25
[G1 Android Development] Effdee:
ok

time to ask obvious questions

do you have ext partition (sd-ext)?

have you set default install location?

have you used cMTD?

do you have space free?

adb install

but I don't even bother with that

I just adb push the apk where I want it
[G1 Android Development] xploit:
thanks for the help effdee

time to ask obvious questions

do you have ext partition (sd-ext)? No Im looking for fastest performance

have you set default install location? No... will this be set at Settings-applications- install preff internal device storage? then yes

have you used cMTD? not with this rom... I have used it before with previous rom... what will the recomended mtdpartmap.txt be?

do you have space free? Internal 296MB available 276MB
[G1 Android Development] psychosonic:
Ugh, rebooted again. Couple minutes after deleting the battery stats too. Some incompatibility here we don't know of?

Here's the last_kmsg

http://pastebin.com/6gJW7fbf
[G1 Android Development] roalex:
just use the stock kernel, is stock for a reason.
[G1 Android Development] psychosonic:
Oh, you mean the one that I posted about on page 211 with a catlog, where there's massive battery drain, and it caused me to not be able to boot past splash?

That one?

Even if that stuck-at-splash issue doesn't come up again, it still has that huge battery drain problem, which is unacceptable.
[G1 Android Development] hrk:
"performance" governor will not scale CPU frequencies, so it will keep the CPU at 576 MHz forever and ever. It doesn't matter what min frequency you choose. :)
[G1 Android Development] dw9906:
I have great battery life with stock kernel. And I use wifi all day long.
[G1 Android Development] chris122380:
Why so many different kernels? What is best for the mytouch 3g 32B 2708 radio? I have been using the default ROM kernel would using a different one make a deference?
[G1 Android Development] ezterry:
What is wrong with the one that is autoinstalled?

If nothing is wrong its the best that is why its included

(and if there is an unknown problem if you don't report it .. it will remain unknown)

roalex: Maybe the other kernels ought to be removed from the op.. I know they where added when there was some issues such as green screen.. but now a historical kernels link to a new post with them listed really ought to do.. for historical reference.
[G1 Android Development] cabrerachaparro:
Gtalk

Hi,

I have an issue with Gtalk. I have to be checking Gtalk because it disconnect for nothing. I don't know why it happens that.

Any ideas?
[G1 Android Development] blackcuzz:
Need help with this also because some apk do the same...they says i have insufficient space when i have well over 170 mb now but that doesn't matter at all they do it on a fresh install with wipe.

I have same setup without ext partition and default install is set to device
[G1 Android Development] chris122380:
Nothing is wrong, I was just wondering what the difference was. I'll just stay with the default then.
[G1 Android Development] ldrifta:
sorry if this has been asked already but can i flash this with RA dream 1.7.0 recovery? and do i need a kernel bcuz i have 2.22.28.25 and 0013d
[G1 Android Development] creezalird:
yes u can with amon-ra, no extra kernel needed coz autokernel is included,

maybe u need custommtd
[G1 Android Development] Effdee:
in that case we are going to need a logcat so we can see what the real error is
[G1 Android Development] Effdee:
yes I know

phone is more responsive and it makes very little difference to battery :)
[G1 Android Development] ringochan:
I had a similar issue in the past with different roms. Have you tried other install locations (i.e. 'let the system decide' or 'removable sd card')? In my experience, if an app can be installed on any location, then I could move it to internal storage afterwards. For the same token, you can create a small ext partition for apps like those, then move them to internal afeter installation. Your won't loose performance that way.
[G1 Android Development] psychosonic:
Alright, I decided to try the stock and just leave Wifi on. And surprisingly, you're right. It actually doesn't drain much battery at all, the effect seems pretty minimal. I've been afraid to try this since in the past I've left it on and my battery was dead in around 4 hours. Although it's likely that I tried this with a much older OS or kernel. Either way, this workaround seems completely feasible for the time being.

EDIT:

Alright, I've hit a snag here with the deskclock. Earlier today, my alarm (via Deskclock) went off while the phone was sleeping/suspended/idling (whatever the term is). However, the screen wouldn't react at all when I tried to tap "dismiss" for a couple minutes, and it kept beeping. After a minute or two, it said that the system wasn't responding, I hit "Wait", and then was able to hit "dismiss" for the alarm. However, now when I try to add a new alarm to the clock, or edit an existing alarm, deskclock forcecloses. I've tried rebooting, clearing the clock's data, wiping the dalvik-cache, extracting the deskclock apk from the COS 5/18 zip and pushing it to system/app, and also re-flashed the COS 5/18 zip. Still force closes. I'd prefer to not have to wipe everything again...

What do?

http://pastebin.com/RSapKmWi
[G1 Android Development] roalex:
you can delete the cache of that app alone, settings/applications/manage/all...
[G1 Android Development] psychosonic:
Was originally going to try that, but the clear cache button is grayed out. I also tried to uninstall it then reinstall (via adb), but I get "Failure" when trying to uninstall, presumably because it's in system/app.
[G1 Android Development] roalex:
that means nothing is saved ><
[G1 Android Development] psychosonic:
Sooooooo... what does that mean? Wipe is the only solution? I mean, I can just use some app-store alarm, but it's really bugging me that this one isn't working.
[G1 Android Development] tom0769:
Maybe try uninstall/reinstall the DeskClock.apk via adb:

adb remount

adb pull /system/app/DeskClock.apk ./DeskClock.apk

adb rm -f /system/app/DeskClock.apk

...

maybe reboot to recovery and wipe cache/dalvic cache (don't know if necessary)

...

adb install ./DeskClock.apk

Had some fc problems with Opera Mini and could get it to work in that way.
[G1 Android Development] Paul Shirley:
Have the same clock problem. Pushing DeskClock.apk from COS-DS-full-05112011-signed.zip fixed it (the most recent previous version I have), nothing else did - fix-permissions, wipe cache, reinstall, repush apk etc..

05-19 13:44:40.551: ERROR/AndroidRuntime(9855): FATAL EXCEPTION: main
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.android.deskclock/com.android.deskclock.SetAlarm}: java.lang.NullPointerException
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1768)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:1784)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at android.app.ActivityThread.access$1500(ActivityThread.java:123)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:939)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at android.os.Handler.dispatchMessage(Handler.java:99)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at android.os.Looper.loop(Looper.java:130)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at android.app.ActivityThread.main(ActivityThread.java:3835)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at java.lang.reflect.Method.invokeNative(Native Method)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at java.lang.reflect.Method.invoke(Method.java:507)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:841)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:599)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at dalvik.system.NativeStart.main(Native Method)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): Caused by: java.lang.NullPointerException
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at android.content.Intent.parseUri(Intent.java:2793)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at com.android.deskclock.IntentPreferenceScreen.updateIntent(IntentPreferenceScreen.java:97)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at com.android.deskclock.SetAlarm.updatePrefs(SetAlarm.java:222)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at com.android.deskclock.SetAlarm.onCreate(SetAlarm.java:145)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1047)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:1722)
05-19 13:44:40.551: ERROR/AndroidRuntime(9855): ... 11 more
05-19 13:44:40.571: WARN/ActivityManager(180): Force finishing activity com.android.deskclock/.SetAlarm
05-19 13:44:40.581: WARN/ActivityManager(180): Force finishing activity com.android.deskclock/.AlarmClock
05-19 13:44:41.081: WARN/ActivityManager(180): Activity pause timeout for HistoryRecord{40986ee8 com.android.deskclock/.SetAlarm}
[G1 Android Development] Paul Shirley:
Damn, other apps started misbehaving until I rebooted... so reboot after pushing.

With the broken DeskClock the launcher seemed extremely sluggish responding to clicks on the clock and to some extent other app icons. Replacing it seems to have fixed that. Bizarre, is the apk corrupted and confusing adw?
[G1 Android Development] roalex:
seams to be resolved guys. check the change log of the pack here

this fix was included in the 19 build and tbh i can't reproduce this event.
[G1 Android Development] kapsidi:
Hi guys and roalex. I am building an app for android and testing it on my HTC Magic.

My phone reboots but it's not always when I am in the app. Sometimes I have closed the app hours ago.

So I tried to find something but don't know what should I search for.

Could this be because of the app or a kernel problem?

In "adb baugreport" I find these lines:

[13328.994964] Kernel panic - not syncing: Fatal exception

[13328.995300] Rebooting in 5 seconds..

[13332.996337] Restarting Linux version 2.6.36.4-cos (alex@buildbox) (gcc version 4.4.3 (GCC) ) #1 PREEMPT Mon May 9 07:30:26 EEST 2011

and I can't find anything suspicious about my app when searching for it's package name.

Off-course I am writing here because I use this ROM and want to see if it's my app or the kernel!

thanks!
[G1 Android Development] roalex:
more details are needed imo :)
[G1 Android Development] kapsidi:
What exactly could I do to help you help me?

And in general is it possible for an app to make a phone reboot?
[G1 Android Development] ezterry:
Somewhere above the last three lines of kernel log created while the system rebooted its self was a stack trace telling what the kernel was doing/did to make the system think it needed to reboot.

Above that still was some context as to what the system was doing (wakeing from slleep? are you underclocked?, trying and failing to free some ram? was a large amount of ram in use.. or a large web page open)

Between that context and the stack trace .. and an informal collection of such information gathered by others and my self using the 2.6.36.4 codebase I can see if its new random or just feels like a bigger problem is the above.

An app ought not be rebooting the system .. and if nothing goes wrong the kernel on request.. but if something goes wrong your kernel and phone is configured to reboot rather than lock up where possible
[G1 Android Development] WongHokZau:
wow,wow,Talented guy,exciting result...finally i succeeded after rebooting like you said.finally solved this program.thanks....

after finishing the steps,it showed

./etc/init.d/07newfonts: #!/system/bin/sh: not found

just ignored it,reboot then work...

grateful

----------------

and i met another issue after doing all the steps you gave me. at first i replaced DroidSans.ttf, and then i tried to replace DroidSansFallback.ttf. of course it worked.but the font file "DroidSans.ttf" became default which meant i can replace one font file only,any one file changed,the others would back to default.
[G1 Android Development] kapsidi:
Here is a link for my bugreport (it's some time after the reboot) http://dl.dropbox.com/u/1254600/bugreport.txt

It would be perfect if you could help me...I cant see anything understandable by me.

I just started to be suspicious with my USB port, cause it only happened while plugged on and now an external drive made some weird things on my PC!

Anyway the only thing I am really concerned about is if this thing caused by my app. My experience with the ROM is good and I don't think this is a problem in kernel!
[G1 Android Development] Effdee:
it is a dirty hack

but it works, and for most is much easier than repacking the fonts.sqf (which is the correct way to do it)

if you want to replace more than one font file, you need more lines

su
cp /sdcard/DroidSans.ttf /data/
mount -o rw,remount /system
echo "\#\!/system/bin/sh" > /etc/init.d/07newfonts
echo "mount -o bind /data/DroidSans.ttf /system/fonts/DroidSans.ttf" >> /system/etc/init.d/07newfonts
echo "mount -o bind /data/DroidSansFallback.ttf /system/fonts/DroidSansFallback.ttf" >> /system/etc/init.d/07newfonts
chmod 700 /system/etc/init.d/07newfonts
./etc/init.d/07newfonts

if you are going to be replacing many, it may make more sense to use a for loop

e.g.

for font in DroidSans.ttf DroidSansFallback.ttf;do
mount -o bind /data/$font /system/fonts/$font
done

no *real* advantage here but if you have 3 or 4 fonts you can see how it saves repeating lines

taking it even further, put your replacement fonts in a folder on data (data/fonts)

for font in $(ls /data/fonts/*ttf);do
mount -o bind /data/fonts/$font /system/fonts/$font
done

makes it even easier as you don't need to edit the script if you want to add/remove fonts

btw,

like I said this is a dirty hack in the long run it is best to do it properly by repacking the .sqf

but I think it serves as a practical example of useful scripting
[G1 Android Development] kingjehu:
Is the issue with menu-unlock happening despite it being disabled fixed with the latest?
[G1 Android Development] gtavo:
:( I´ve been looking in the post, but I didn´t find what is the "system partition" is a swap partition in the sd¿?

Thanks and sorry for my ignorance.

PS I´ve tried the search too.... :confused:
[G1 Android Development] ringochan:
/system, /data, /cache are all on the phone itself.

System partition is where the ROM gets stored.

Swap partition is something we create on the sd card.
[G1 Android Development] cabrerachaparro:
Hi,

I use Tasker and Shake to call apps. These apps have services that are shown on the notification bar. It supposed that when they service are active it should stay on but some reasons the services restarts frecuently and sometimes they disappear form the notification bar.

Do you know why it happens? I didn't have this issue using Android 2.2

Thanks
[G1 Android Development] dw9906:
WooHoo!!! Effdee has finally been banned from XDA!! About time!
[G1 Android Development] Maxamillion:
What? he has??? why?

Guys i think im gonna downgrade to froyo and try out froyo bylazlo, cuz im looking for a daily driver and gingerbread is just not ready yet, its almost there. I will keep my eyes on this rom though to see when its ready.
[G1 Android Development] dw9906:
Look around the forums and you'll see why. He treats people like crap. He was a horrible person and he deserved it. And I use this rom as a daily driver with no issues. I don't understand why people have so many issues. This is by far the best rom I've ever used. And I mean that. Sorry you have so many problems. But I doubt it will get any better for you being this rom is already great and I personally don't see how it could get much better. Good luck with froyo by lazslo. :)
[G1 Android Development] Maxamillion:
yea he was a jerk to me twice and i did notice how mean he was to people. MAy i ask what are your settings? I have no swap, overclock at default, cc at 10%, vm heap size 16M, no purging of assets, lock home in memory checked, lock messaging app in memory checked, no jit,no surface dithering, i have launcher pro as home.

Have you done anything particular to this ROM, like bareboned, deleted stock apps, configuration, etc.?

I actually havent had that many problems, its just that, sometimes after a few days without a reboot, like 2 or 3, it becomes REALLY slow, and almost unusable.

Besides that, everything else is ok.

Have you tried fryobylazlo by the way?