yashsingh1/xdaforums huggingface dataset:
[G1 Android Development] cj chitwood:
Search this thread for posts containing the term "init.d" (I tried a few different terms before this one actually provided the answer -- I hate "search this thread" -- it brings me everything EXCEPT the search terms, usually).

http://xdaforums.com/showthread.php?t=950765&highlight=init.d

http://xdaforums.com/showthread.php?t=950765&highlight=init.d

Basically, for some time now init.d has been a SquashFS. Just need to unsquash it to add stuff and resquash it when you're done, from what I gathered. Of course, I've never done that myself, so IDK how well that works, but just from actually reading this thread instead of skimming the last three posts like most people seem to do, I've picked up on that much.

HIH... Let us know how it goes for you.
[G1 Android Development] roalex:
um, why over complicate things, if you don't wanna have it read only, pull the current init.d scripts then reboot to recovery and delete the sqf file...add the scripts you want in there, chown the files to 755 but as i said before, you won't make it run any better :)
[G1 Android Development] belrin:
Thank You :)
[G1 Android Development] roalex:
I made a new recovery build now it seams proper, as in those odd reboots are gone, also v4.0.0.5 now ;)

/later edit

Removed misc from fstab as you cant really be sure something unexpected isn't going to happen, those who had the chance to flash the new one should update.
[G1 Android Development] roalex:
If you have issues mounting ext after a wipe:

reboot in recovery:

adb shell

parted /dev/block/mmcblk0

print

rm ext (2) for instance

mkpartfs (input primary,ext2,start (where the FAT partition ends), end (where the SDCARD ends)

now use the format sd-ext from the recovery menu, and your done :)
[G1 Android Development] dw9906:
Thanks, I'll give it a shot.
[G1 Android Development] roalex:
Well it was ok but the format sd-ext was still buggy, but NOW! its ok ;)
[G1 Android Development] dw9906:
Edit/ NM. I reflashed anyways. :) just in case.

I should reflash again?
[G1 Android Development] roalex:
Yup, its needed :)
[G1 Android Development] dw9906:
Well crap, it wont let me do a backup. I get the same recovery reboot as soon as it tries to backup system. :(
[G1 Android Development] Sheist!:
So what conditions would blow away this customization effort?

1. new COS-DS flash? (straight ROM-over-ROM, without wipe)

2. new kernel update with or without ROM update?

Since the files there are so small anyway, what is the benefit of squashfs in the first place, I wonder?

Thanks.
[G1 Android Development] robuser007:
What has changed from ClockworkMod Recovery v3.0.2.4

to v4.0.0.5 ?
[G1 Android Development] darkguy2008:
Ask in CM's thread? you know, this thread is kinda unrelated to it :/
[G1 Android Development] robuser007:
which one?
[G1 Android Development] roalex:
gotta sort out sd-ext before that, make sure it works first :)
[G1 Android Development] dw9906:
Looking forward to new version. :) Glad to finally see someone working on this new recovery for our D/S's
[G1 Android Development] roalex:
try the new build but this time, before trying to backup or wipe sd-ext run this flashable.
[G1 Android Development] almostthere:
Hi Roalex, tried to flash that using Amon-RA, error came out. Message was:

E:Wrong digest:

tmp/alignment/mkfs.ext4

E:Verification failed
[G1 Android Development] dw9906:
It wont wipe sdext will it?
[G1 Android Development] dw9906:
Im pretty sure he meant to flash the new recovery then flash the .zip.
[G1 Android Development] almostthere:
Thanks for clarifying. If that's the case I'll pass as I'd prefer to keep Amon RA due to it's sd-ext creation and formatting abillity
[G1 Android Development] innerspace:
USB bug status in stock COS kernel

Hi roalex, I'm wondering what the status of the USB power drain bug is in your stock kernel.

I'm seeing random reboots (really, really random) and am definitely seeing the Wifi/USB power drain bug. It's so random I'm uncertain as to the chain of events (ie: Wifi on, plub USB, unplug USB Wifi off etc).

Have the patches in the related thread here at xda been applied to your stock kernel or should I flash a new kernel? If the answer is flash a new one could you explain the process to me? Long time G1 user, long time xda user, never flashed a kernel and don't know what you've done already to address the issue.

Thanks.
[G1 Android Development] ringochan:
Flashing a kernel is as simple as making a nandroid backup and flashing the zip file in recovery on top of whatever rom you have installed. I don't think you need to clear anything or do fix_permissions, but I usually do it as a precaution.

I have a G1 too and my setup is very similar to yours (except mine is not black:p). To me, roalex's kernel works the best on cos-ds overall. I have 2 spare batteris, so can't really comment on the battery drain, though.

Those hard reboots occur once in a while and really can't do anything because they are so random I don't know how to diagnose the cause. But hey, it even happens to new phones with stock roms, too. Soft reboots, on the other hand, seem to be caused by low-memory situations.

In any case, if you try all the kernels out there and find a good one, let us know.
[G1 Android Development] roalex:
Ok, finally managed to fix the recovery, have fun, everything should be working, also as a "feature" our build will wipe/format sd-ext as ext4 :) the soruces are on github.
[G1 Android Development] dw9906:
SWEET!! THANKS
[G1 Android Development] cj chitwood:
[TL-DNR]

I recommend backup, full wipe, upgrade to 06082011.

[/TL-DNR]

Full Version:

I'm running 06082011 and my uptime is 6.95 days. I have not noticed the drain bug and I sometimes have wifi on and sometimes off, so I can't say as there is a wifi drain bug anymore. However, I don't charge via usb to computer very often so I can't provide feedback there.

I have not had any random reboots in quite a few versions. For that matter, having uptime of a week is saying something for this phone.

I have noticed recently that my quadrant score dropped into the 290s and I don't know why, since it was up in the 370s not long ago. I did, however, enable long-back-to-kill-app because of it to test, and it doesn't seem to have helped (indicating only that the cause is not resource related, though not definitively proving it).

All of this on the stock kernel, cpu set to max/next to lowest, and jit disabled with everything else default.

And I did do as full a wipe as recovery and fastboot would allow before flashing this one... which I hate doing but now that a2sdext is pretty much standard, it's not so big a deal anymore for me.

HIH...

[Edit: by the way, my drain rate is close to -- but not equal to -- the best I've seen. About 1% per hour. Mind you, I shut off wifi, 3g, gps, sync, and all that any time I'm not using them. Sometimes I still forget to though, and while the phone does still drain quicker with stuff enabled, it's far better than a month or two ago. Minorly inconvenient when I have to enable them but at least now I can have my phone on my hip all day and not need to charge it constantly. Also, if I am at the office where brick and concrete walls prevent having signal, my battery does still drain far more quickly than when I have signal. However, not as quickly as it used to. There have definitely been power drain improvements in fairly recent releases of stock COS-DS.]

--

Sent from my HTC Swiss Army Phone running COS-DS
[G1 Android Development] dw9906:
I tried to do as you said and wipe sdext before doing anything, but still wont allow me to do a backup. Just reboots recovery as soon as it tries to backup system :( Does it work for you?
[G1 Android Development] roalex:
I'm not sure why you have problems with backups, works fine on both devices here.
[G1 Android Development] dw9906:
Hmmm. I don't know. It just wont backup for some reason. It sucks. I really wanted to use it too. I'm gonna try it one more time I guess.

Later edit//No go. I guess I'm destined to be stuck with 2.5.0.7. Still get the same reboot. I guess ill try again if or when you put out a newer version. :(
[G1 Android Development] roalex:
others confirm it to be working :)

now lets see how do you "update" it, it looks like your flasing the same img over and over ;)
[G1 Android Development] robuser007:
I had to format ext
[G1 Android Development] roalex:
I did tell you that, its on the first post ;)
[G1 Android Development] dadosmi:
Hi guys I want to install this rom!

Before I make you a question?

1) I have a dream date with radio and spl, which Langpack should I install?

2) how is the battery life?

thank you in advance to all!!
[G1 Android Development] cj chitwood:
I thought I had a dream date with a radio once, but she was a CB when I was looking for a Ham.

...and now you know where my sense of humour comes from.

Anyway, If you're in Rome, I assume you speak Italian as Romans do, so, from the first post:

Langpack Three has it_IT (Italian, from Italy) so that's the one I think you want. But, if you're only living in Rome for now and you actually Spreken sie Deutsch, you might rather try the one with de_DE in the list...

The battery life is comparable to other recent editions of this ROM. If I have only the phone radio on (no bluetooth, no WiFi, no 3G, no GPS, no sync, no background data, no foreground data, et cetera, I get about 1% of battery drain per 1 hour, roughly.

If I have everything turned on and I'm using it actively, it would be possibly for me to drain the phone dry in around an hour -- but I'd have to constantly be with it in my hand doing full 3G data with GPS lock and WiFi Tether going on.

So battery life's pretty good.

As always, your mileage (kilometerage?) may vary, so go ahead and do a backup then flash the ROM and see where you sit with it. If you don't like it, you can always revert back. Unless your NAND chip is messing up....
[G1 Android Development] dadosmi:
Sorry, but I do not speak English well, so use google translator.

Thank you for the answer, I'll do a test and then I will tell you!!
[G1 Android Development] dw9906:
I downloaded the one from first post each time.
[G1 Android Development] MattDrumz:
For some reason, this ROM won't let me install some T-Mobile themes, and LauncherPro from the market. It just says "Installation Unsuccessful." Any ideas on how to fix this? Other than this, this ROM is awesome.
[G1 Android Development] roalex:
well each time you flash a new recovery if you use CMTD you have to erase_image system;userdata;cache flash_image the recovery, erase_image system;userdata;cache then reboot into recovery, flash the CMTD, erase_image system;userdata;cache, reboot into recovery - only now you are good to go ;)
[G1 Android Development] dw9906:
I don't use cMTD.
[G1 Android Development] dw9906:
Recovery

Any suggestions as to why the new recovery won't work for me? Is there anyway i can format and delete my recovery? I'm not able to use fastboot due to S-ON. The way i've been doing it is flashing the recovery thru terminal. And when i realize the new recovery wont work i reflash the old recovery via rom manager. Am i causing a problem by flashing the recoveries over and over again over each other? If so how do i format the recovery without using fastboot? Thanks for your help...
[G1 Android Development] tvall:
# erase_image recovery
[G1 Android Development] dw9906:
I figured it was as easy as that! Thanks!
[G1 Android Development] lunotown:
CAUTION! You don't have "fastboot flash recovery" so don't erase your recovery unless you know how to flash it without using that command.
[G1 Android Development] tvall:
S-on only affects fastboot commands. you can read and write to anything from a booted system (flash_image [write to a partition] dump_image [read a partition to a file] and erase_image [erases partition] all work on any system as long as you have root access ). So in this situation you would do this:

$ su

# erase_image recovery

# flash_image recovery /path/to/recovery.img

The only thing s-on has prevented me from doing is flashing a new splash image

Edit: woah... you changed your post a lot... welll... I'm just gonna leave this here just incase anyone else needs it
[G1 Android Development] lunotown:
Ha... yea, I just remembered and edited my post too. I erased it once along with the rom a while ago and had to go through a bunch of stuff to get it back on. Thanks for the correction anyways.
[G1 Android Development] tvall:
Also if you have the 1.33.0013d so like your signature says, then you can use fastboot erase. Your just missing flash and some other stuff I think....
[G1 Android Development] dw9906:
I tried everything I can think of. It still wont let me do a backup. :( I guess I'm screwed.
[G1 Android Development] roalex:
Quite odd you should try to grab this logs after the error happens:

"cp /tmp/recovery.log /sdcard/" and

"dmesg > /sdcard/dmesg.log"

and upload them here.
[G1 Android Development] ra100x:
SK,CZ

@roalex: could you please put Slovak language to one pack with Czech? They are very close.

And why there are not many SK letters when I have SK keyboard? e.g. ľ,ĺ,ŕ,ď,.. i there any easy way how to add new letters? :)
[G1 Android Development] vermaekansh:
kernel link

I want the kernel link used in the latest build.
[G1 Android Development] BlackF09:
ADW crashes

Since "14 June 2011" release we are back on ADW launcher. :) I've set the main dock style to three icons and enabled the desktop dots for switching desktop. If I press the dots ADW gets a FC.

Restore screen settings seems to not work either.

Can someone confirm that?

What I already did:

ADW settings, restore default and changed to three icons and dots

run fix_permissions

save and restore adw settings

deleted /data/data/com.android.launcher/databases/* and /data/data/com.android.launcher/files/*

wipe cache and dalvik_cache
[G1 Android Development] dw9906:
Ill get them both uploaded today.
[G1 Android Development] roalex:
yup i can confirm it, i never notice it since im always using 5 icons :)
[G1 Android Development] BlackF09:
I like using the dots to switch screen or activate the preview (long press). But I have no version info, it worked for me before the last switch of the launcher.

Am I right that save/restore screen should save and restore the icons and widgets on screen? Or does it save just the number of configured screens?
[G1 Android Development] roalex:
it won't save any widgets at least, that's for sure
[G1 Android Development] cj chitwood:
From Google Translator:

Traduttori spesso non sono corretti in modo Terrò questa breve.

Se si parla italiano, uso pacchetto di lingua 3 (cercare "it_IT" nella lista delle lingue e localizzazioni)

La durata della batteria è decente fino a quando si spegne cose che non state utilizzando.
[G1 Android Development] Khizzer:
can i get the launcher2 zip file??

plz
[G1 Android Development] roalex:
get the apk form one of the older builds
[G1 Android Development] darkshino:
Just to tell, by deleting ThemeChooser.apk/.odex and ThemeManager.apk/.odex in system/app, then pushing ThemeChooser.apk and ThemeManager.apk from a CM7 release, everything concerning theming is working again here :-)
[G1 Android Development] roalex:
latest is 19 an AFIK there's no issue with theme chooser
[G1 Android Development] darkshino:
I still don't have theme chooser working with 19 release, same error. I'm too lazy to give full wipe a chance now, and if I'm the only one getting this strange behavior, that's not a problem. Everything else is awesomely smooth :-)
[G1 Android Development] robuser007:
Is there anyone else having issues with icoyote (on france market, marketenabler) ?

I have no sound using it, I've chequed all options on gsm/the app.

In the past (with an much older) build it worked fine.
[G1 Android Development] ilovebbq:
hi people

trying to get the g1 working with the latest build

stuck on the setting up screen

"can't estblaish a reliable data connnection...."

4 bars, the up/down arrow with H underneath it are visible

how can i fix it?

new radio image?

:(

new gapp?
[G1 Android Development] ilovebbq:
at least i was able to root it, which was not as easy as the thunderbolt root lol

i tried to use the cm 7.1 build but could it would abort installation every time :mad:
[G1 Android Development] dw9906:
You must of ignored the rest of the post on the CM 7.1 ROM. The fail just needed to be ignored and then a kernel flashed and rebooted. It was an issue writing the boot. Anyways, not for this thread. :)
[G1 Android Development] cj chitwood:
Touch all four corners of the setup screen starting with top-left, then top-right, then bottom-right, then bottom-left. If fail, repeat. This will get you past that screen so that you can at least troubleshoot the connection problem with e.g. ADB. Or, set up WiFi or whatever.

This was in a post in this thread, but admittedly it's been like 2 or 3 months/years :p ago when Roalex posted about it. Maybe early May or so?
[G1 Android Development] roalex:
Some good news, manage to fix the build gesture bug, the ADW FC thingy and Pacman shows apps names instead of com.... stuff, maybe others things were affected by this issues :)

update in a little ;)
[G1 Android Development] ilovebbq:
i'm reading through it and have no idea still lol

doesn't work for me :(
[G1 Android Development] Khizzer:
livewallpapers dont work on the lockscreen:o
[G1 Android Development] roalex:
O rly? How about installing some?
[G1 Android Development] dw9906:
Thanks for your help yesterday. I finally got the repo to sync. Its working right now.
[G1 Android Development] Khizzer:
they work on home screen but not on lockscreen

when i lock the phone they are gone:D
[G1 Android Development] roalex:
Well im sorry i cant provide lock screen live wallpapers ;)

You can however disable the lockscreen under tablet options, that way you get your live walls at all times, imo its close to SM to even run LW on D/S :)
[G1 Android Development] roalex:
Good, but only know is getting hard, you will need a few months to figure things out, which is np if you like it .
[G1 Android Development] dw9906:
Yeah, I don't expect to be outputting ROMs right away. Lol. I'm sure it will take me awhile. I really want to learn though. I want to be able to trully contribute to the community. After I figure everything out. I'm not sure if ill be able to figure out and setup a github so I can share the sources. May need some help with that one. It'll be awhile though. Lol. Thanks again.
[G1 Android Development] dw9906:
When its done to download the most recent nightlies do i change

curl http://sandbox.devnull.name/android/gingerbread/GINGERBREAD-DS-CheckPoint-20110501.zip > sapphire_update.zip

TO:

curl http://sandbox.devnull.name/android/gingerbread/GINGERBREAD-DS-Beta-20110605.zip > sapphire_update.zip

?

EDIT/ Its done syncing
[G1 Android Development] tvall:
You can but you dont hhave to. We just pull proprierary files from that and those rarely chsnge
[G1 Android Development] darkshino:
As usual, full wipe fix it. Sorry for the spam...
[G1 Android Development] Paul Shirley:
browser slowdown

I've been tweaking and it looks like the browser slow down (which affects Dolphin not just the stock browser) is caused by the aggressive 'allow purging of bitmap assets' option. It suspect it's leaking RAM (possibly native RAM) in the WebView cache - eventually killing Zygote and causing massive concurrent gc processing along the way. So any app using a web view is going to accumulate problems.

If anyone wants to try it fire up an adb shell and try:

T:\android-sdk-windows-1.6_r1\platform-tools>adb shell
~ # setprop persist.sys.purgeable_assets 0
setprop persist.sys.purgeable_assets 0
~ # exit
exit

then

adb shell stop
adb shell start

or restart the phone.

Running Jit-on, 32M VM. The Jit makes little difference, larger VM makes the slowdown much worse. I got through 15 forum pages at giffgaff without problems. Normally the whole phone would slow rapidly then totally freeze by 10.

If we can confirm this can we have the settings option back while we wait for a real fix?
[G1 Android Development] roalex:
So anybody noticed that Youtube HQ are working on the latest build ? ;)

@Paul Shirley

Suppose i will give the option to turn it off then
[G1 Android Development] dw9906:
Forgot to change the title to 6/23 lol. :)
[G1 Android Development] rysk29:
is "COS-DS-full-05202011-signed.zip" the latest or am i missing something.. also is there any fix for wen opening market, it takes 4ever to load
[G1 Android Development] tvall:
6.24 us the newest. First post
[G1 Android Development] roalex:
if you have such a question maybe you should try something else
[G1 Android Development] rysk29:
this might be wierd, but i dont see any way to download a rom on 1st post, all i see is links to git, recovery and language pack 1-4... where on 1st post is the link?
[G1 Android Development] rysk29:
Dont be mean.. just tryin a new rom i know how all this works, but the link is quite hidden.. .. im guessing its one of the language packs links, which should just say here is the rom.. which language pack tho?

1, 2, 3 or 4

there is no link in 1st post pointing to "6.24 us"

my question isnt technical.. simply just asking where the link is on 1st post to newest
[G1 Android Development] rysk29:
Thank god i didnt ask something like.. how do i wipe.. i feel sorry for the person who asks something technical, since even a simple which link question, gets hated on by someone i would expect to help rather than flame for a simple question.. if u dont want people asking a question when they are about to flash your rom for the first time, then you shouldnt even post the rom to begin with...
[G1 Android Development] darkguy2008:
I differ.

Actually, you should do your homework first before doing so. I read A LOT of info before getting my hands dirty on ROM flashing. It didn't take me more than a day... just look for a few tutorials, maybe even a simple acronym glossary (ROM, SPL, RUU, etc), then read the first post CAREFULLY, it should have the most important info on which file is the latest one and what does it contain and such. The first post is very clear on that...

In my case, first thing I looked for was to how to make a backup I could restore back in case I bricked my phone. I was introduced to the recovery and boot/spl/radio flashing. With that done and over with, I then looked for info on which ROMs were available for my device and read the damn first post and after that, if I had any doubts that weren't already specified in such post, I asked them.

Of course, it's also a good idea to ask stuff related to the ROM... you don't go into a ROM kitchen post asking how to flash MIUI... it's just plain rude, unrelated, and makes you look like a n00b, and people will treat you like that, because you're behaving like one... I was a n00b too, but some information research gets you one level higher.
[G1 Android Development] rysk29:
As i said my question WASN'T technical... i know how to flash and all that, i just needed to know where the rom link was... langpack doesnt sound like a rom to me so i asked.. and got a smart A$$ answer... all the other roms on here were easy to find.. anyways.. im done.. this reminds me of the ps3 hacking scene.. a bunch of stupid smart people who would rather flame, than just say something as simple as "its this one"
[G1 Android Development] tvall:
But we are supposed to treat noobs the way we wanted to be treated when we were noobs
[G1 Android Development] GuyInDogSuit:
I tried that theme but it doesn't even change anything except status bar icon colors. Theme Chooser complains that some resources are missing.

Updated recovery to 4.0.0.5 and it works great. Nice new interface.

Also, have you thought about updating the Superuser apk to the latest? It's at 3.0beta1 and the binary is at 3.0alpha7. Since I have that installed, every time I flash an updated ROM it messes SU up for some reason.

Edit: Just read the update notes about enabling Superuser updates in Development. Not sure if it was required, since I normally remove Development, DSP Manager, and a few other apps from the ROMs before installing.