Sourcery ROM 2.2

[YankInDaSouth]

Me custom ring tones don't seem to be working ... got slayher's 900 kernel installed with min cpu set at 300 scaling on demand. Don't recall having this issue with Sourcery ... although I can't remember much of what worked and didn't work on what lately - I have been a ROM whore for several weeks now!

Hope u used protection and always backed up as for ur custom ringtones whiich ones aren't working and where are u placing them?

Sent from my Droid using DroidForums

Just ones I downloaded using Zedge, not sure where they end up. But when I set them they show up with the rest of the system ringtones. Think I should track them down and move them to /system/media/audio/ringtones?

 

[Bang Pow Boom]

My phone has been idling for 5 hours and my battery is at 60%. It says sourcery system used 44% and android os used 29%. Any suggestions?

Sent from my Droid using DroidForums

 

[YankInDaSouth]

Maybe try another kernel?? I am at 40% after 14 hours use today ... slayhers 900 kernel OCed to 800.

 

[jam40jeff]

I cracked open the 2.0 zip and 01_sysrw is the only init.d script in there. 2.2 adds 02_sysrw, 04modules and 11_depmod. However, none of these ever remounts /system as ro, so it seems like it is rw in both 2.0 and 2.2. Adding a script to run at the end seems to work.

So here's the problem I'm running into now...

If I leave the init.d scripts as is, the /system mount is always rw. If I add my script, it's ro. So far so good. However, I have noticed that even if drop into a shell and do sysrw (or sysro) the /system mount will be set correctly, but within about one second it returns to whatever it was on boot (the last init.d script). I did some digging and figured out that the init.d scripts are being run constantly in a loop. I verified this by putting one in there that simply does a touch on a debug file I place in /data. I do in fact see the date updated continuously on this file.

I believe I tracked the problem down to a line in /init.sholes.rc where it creates the sysinit service and then starts it. However, I believe this should be setup with the oneshot option so it doesn't loop.

If anyone agrees, is there any chance someone could modify this file and repack boot.img? I am a noob and have about 0% chance of getting this right.

Thanks.

 

[otter34]

Some the theme images on the site should have a screenshot of the drop down, the different menus and icons. Easiest way is to try a theme. Its a one click install..

I must be an idiot because I can't see any screenies of anything. I know it's easy to install, but I'm trying to save the time of instaling, wiping and waiting forever for my apps to load, etc, etc. Does it have the dropdown power notification? That's most important; bluetooth, wifi, brightness

 

[eagle1967]

please remember this rom is not supported officially..but

Some the theme images on the site should have a screenshot of the drop down, the different menus and icons. Easiest way is to try a theme. Its a one click install..

I must be an idiot because I can't see any screenies of anything. I know it's easy to install, but I'm trying to save the time of instaling, wiping and waiting forever for my apps to load, etc, etc. Does it have the dropdown power notification? That's most important; bluetooth, wifi, brightness

yes it has the galaxy-s type widget on the pull down it must be turned on in settings.

 

[Bang Pow Boom]

Maybe try another kernel?? I am at 40% after 14 hours use today ... slayhers 900 kernel OCed to 800.

I just reinstalled the rom and that fixed the battery problem. The other problem I still have is when I charge my phone, it stays at 110 degrees all night. So off to another rom.

Sent from my Moto Droid using DroidForums

 

[eagle1967]

dock?

Maybe try another kernel?? I am at 40% after 14 hours use today ... slayhers 900 kernel OCed to 800.

I just reinstalled the rom and that fixed the battery problem. The other problem I still have is when I charge my phone, it stays at 110 degrees all night. So off to another rom.

Sent from my Moto Droid using DroidForums

are you using the multimedia dock to cahrge? i bought one of those off amazon long before i ever made this rom and its caused my phone to heat up. so i couldnt use it . just a thought. 1 other thing is it appears that there are things in some of the rom that should not be there. although not sure they would cause this. but you could try going into ect/init.d and delete whats in there and see how it reacts.
Also if you are overclocked high unless you use set cpu and set the charging level lower the phone charges running at full speed. so if you are over clocked to 1 gig or higher and charging without having set cpu downclock it will run at 1 gig while charging.

not sure what else is out there froyo wise i do hear gimpsource is good and have talked with that develepor and hell treat you right and help you out so you may want to try that. project elite is great also but not sure they have a current froyo out but if you can find their last froyo its darn good also.
Good luck

 

[YankInDaSouth]

Maybe try another kernel?? I am at 40% after 14 hours use today ... slayhers 900 kernel OCed to 800.

I just reinstalled the rom and that fixed the battery problem. The other problem I still have is when I charge my phone, it stays at 110 degrees all night. So off to another rom.

Sent from my Moto Droid using DroidForums

That stinks! It still amazes me how each phone reacts differently to ROMs/kernels. For me personally this ROM has always been one if the coolest running ROMs I have tried. I keep my phone in the multi media dock all night and have never had heat issues. But like I said, every device is different. I'd recommend sticking with it and try finding that right ROM - kernel combo ... but that's just me

I never like pointing people to another ROM but being eagle did it, so will I lol ... Droid concepts is still working on froyo. Woodyman has been releasing some BETA builds that have been pretty stable. Last I ran one it was pretty basic but I know he is working on adding options/features ..

 

[eagle1967]

the woodyman

yeah forgot about that woody's a good guy so give his a run also.

CHIZZLE: returned the G2x so back to droid only.... sucks phone runs great but the signal was spiratic and there were places where it showed 4g and 5 bars and got .03mb or couldnt run speed test at all. not sure if its tmobile or the phone but want going to commit 2 years to a questionmark. so now its shoudl i get the revolution which is prety much the thunderbolt with hdmi or wait till sept decisions decisions. but i think i found the revolution has 512 of ram its like they make these phones than pull an apple and say o now what can we take out of it

 

[gflam]

Just come back to verizon eagle ha spell book is underway whole layout is done and a few sections are already completed it's packed with tons of stuff I think ur really going to like it.

As for rom recomendations I like project elite the most it's really zippy and some nice features in there and even miui is pretty nice I ran miui for a little while and was impressed

Sent from my Droid using DroidForums

 

[jam40jeff]

I cracked open the 2.0 zip and 01_sysrw is the only init.d script in there. 2.2 adds 02_sysrw, 04modules and 11_depmod. However, none of these ever remounts /system as ro, so it seems like it is rw in both 2.0 and 2.2. Adding a script to run at the end seems to work.

So here's the problem I'm running into now...

If I leave the init.d scripts as is, the /system mount is always rw. If I add my script, it's ro. So far so good. However, I have noticed that even if drop into a shell and do sysrw (or sysro) the /system mount will be set correctly, but within about one second it returns to whatever it was on boot (the last init.d script). I did some digging and figured out that the init.d scripts are being run constantly in a loop. I verified this by putting one in there that simply does a touch on a debug file I place in /data. I do in fact see the date updated continuously on this file.

I believe I tracked the problem down to a line in /init.sholes.rc where it creates the sysinit service and then starts it. However, I believe this should be setup with the oneshot option so it doesn't loop.

If anyone agrees, is there any chance someone could modify this file and repack boot.img? I am a noob and have about 0% chance of getting this right.

Sorry to keep replying to myself, but I'm thinking of trying to tackle rebuilding boot.img and I just wanted to check with eagle or gflam first to make sure there's not a reason the sysinit service runs continuously.

 

[eagle1967]

no reason

I cracked open the 2.0 zip and 01_sysrw is the only init.d script in there. 2.2 adds 02_sysrw, 04modules and 11_depmod. However, none of these ever remounts /system as ro, so it seems like it is rw in both 2.0 and 2.2. Adding a script to run at the end seems to work.

So here's the problem I'm running into now...

If I leave the init.d scripts as is, the /system mount is always rw. If I add my script, it's ro. So far so good. However, I have noticed that even if drop into a shell and do sysrw (or sysro) the /system mount will be set correctly, but within about one second it returns to whatever it was on boot (the last init.d script). I did some digging and figured out that the init.d scripts are being run constantly in a loop. I verified this by putting one in there that simply does a touch on a debug file I place in /data. I do in fact see the date updated continuously on this file.

I believe I tracked the problem down to a line in /init.sholes.rc where it creates the sysinit service and then starts it. However, I believe this should be setup with the oneshot option so it doesn't loop.

If anyone agrees, is there any chance someone could modify this file and repack boot.img? I am a noob and have about 0% chance of getting this right.

Sorry to keep replying to myself, but I'm thinking of trying to tackle rebuilding boot.img and I just wanted to check with eagle or gflam first to make sure there's not a reason the sysinit service runs continuously.

that would explain some other things we forgot to put in oneshot i guess. the rom was stopped shortly after adding in the init.d stuff so we really never got it perfected. that would explain why we had some other things happen too. our fix was to remove the scripts. im not sure how the scripts got back into the rom though. i am in the middle of moving. once i get moved well look into a refresh of sourcery no promises but since im back on the droid now well see wht we can do.

 

[Bang Pow Boom]

Maybe try another kernel?? I am at 40% after 14 hours use today ... slayhers 900 kernel OCed to 800.

I just reinstalled the rom and that fixed the battery problem. The other problem I still have is when I charge my phone, it stays at 110 degrees all night. So off to another rom.

Sent from my Moto Droid using DroidForums

are you using the multimedia dock to cahrge? i bought one of those off amazon long before i ever made this rom and its caused my phone to heat up. so i couldnt use it . just a thought. 1 other thing is it appears that there are things in some of the rom that should not be there. although not sure they would cause this. but you could try going into ect/init.d and delete whats in there and see how it reacts.
Also if you are overclocked high unless you use set cpu and set the charging level lower the phone charges running at full speed. so if you are over clocked to 1 gig or higher and charging without having set cpu downclock it will run at 1 gig while charging.

not sure what else is out there froyo wise i do hear gimpsource is good and have talked with that develepor and hell treat you right and help you out so you may want to try that. project elite is great also but not sure they have a current froyo out but if you can find their last froyo its darn good also.
Good luck

Thanks! You guys are awesome and very supportive.

I was using my wall charger and I wasn't overclocked.

It might just be my phone or battery because I was running SS 5.2 (gb) and the only issue I had was that my battery would jump from 50-10 in seconds.

And with miui rom, it would get hot while charging ONLY if I left the screen on while charging and only in one version.

I might try (secretly) switching out my wife's battery and see if that works.

Sent from my Moto Droid using DroidForums

 

[Bang Pow Boom]

Maybe try another kernel?? I am at 40% after 14 hours use today ... slayhers 900 kernel OCed to 800.

I just reinstalled the rom and that fixed the battery problem. The other problem I still have is when I charge my phone, it stays at 110 degrees all night. So off to another rom.

Sent from my Moto Droid using DroidForums

That stinks! It still amazes me how each phone reacts differently to ROMs/kernels. For me personally this ROM has always been one if the coolest running ROMs I have tried. I keep my phone in the multi media dock all night and have never had heat issues. But like I said, every device is different. I'd recommend sticking with it and try finding that right ROM - kernel combo ... but that's just me

I never like pointing people to another ROM but being eagle did it, so will I lol ... Droid concepts is still working on froyo. Woodyman has been releasing some BETA builds that have been pretty stable. Last I ran one it was pretty basic but I know he is working on adding options/features ..

I'll give some of these a shot. I've been flashing at least once or twice a week. I think I may have a addiction...................but I found about 4 that are very stable on my phone. Thanks for your help

Sent from my Moto Droid using DroidForums