• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Luvin' FroShedYo v10

I've tried several ROMs too such as KaosFroyo, CELB, and a few others and I believe the original poster has it right. This ROM is by far the snappiest one I've seen to date. I have to keep this Eris until I can upgrade in September and so I think this ROM has made me feel better about hanging on to it for the time being.
 
I've tried several ROMs too such as KaosFroyo, CELB, and a few others and I believe the original poster has it right. This ROM is by far the snappiest one I've seen to date. I have to keep this Eris until I can upgrade in September and so I think this ROM has made me feel better about hanging on to it for the time being.

I agree. Besides White Widow, I've been on this rom the longest of any I've flashed.:) I would probably still be on WW but it went dead.:(
 
Here's question for everyone. Did anyone change their cpu boost settings? I changed mine to max(710) and min(480). I left the Governor at Ondemand. To tell you the truth I really dont know if it does anything. My phone rebooted once for no apparent reason. Not sure if it has anything to do with changing those settings.
 
I haven't even bothered with overclocking this rom yet. Personally I don't think ocing does anything and if it does I don't see it.:)
 
Here's question for everyone. Did anyone change their cpu boost settings? I changed mine to max(710) and min(480). I left the Governor at Ondemand. To tell you the truth I really dont know if it does anything. My phone rebooted once for no apparent reason. Not sure if it has anything to do with changing those settings.

I have not OC'd. I find it very snappy on it's own. :)
 
i wont pretend that the extra 200 mhz makes a difference i can see,but in my mind it should be processing faster since that gives it a 100mhz advantage over my droid 1 :)

i set my main screen at 729 max abd 528 min. i set the charging and sleep screens both at 245 min and 528 max. "on demand" on all. i think it does help... with pretty heavy use i can still make it thru a whole day on one charge
 
Well one would assume (and everybody knows what assume means:eek:) that any increase over factory setting would make the processor work more efficiently (to a point before it melts down) and possably make the battery drain a little quicker. However that being said the small amount of increase over stock I don't beleive you could tell the difference. If you was able to double the factory setting then you would be able to tell the difference. Just saying:)
 
Got two questions this morning.

1. There's one little thing that has really be getting on my nerves.:mad: Sometimes when I receive a call and I accept it and before I get a chance to click the speaker (if I want to hear it out loud) the screen will go black and no matter weather I hold it to my ear and lower it the only way to get back to it is hit the end button (which will end the call). Now this has been happening with every rom I've installed so It can't be the roms or is it.
PS. I have read in some other forums (with ww anyway) to press the send button or trackball. No go.

2. When having a conversation sometimes it will make the sounds as when one is hanging up and the call drops and the wierd thing is a second or two later it will make the sounds again and the other party is still talking like nothing happened. Sometime it will just drop. Bear in mind that this happens every now and then but it really gets on my nerves.:mad:

Has this problem happened to any of you?:confused:

Edit: Should I started a new thread with this?
 
Got
Edit: Should I started a new thread with this?


since youre using froshedyo i think this is an ok place for it :)

Got two questions this morning.

1. There's one little thing that has really be getting on my nerves.:mad: Sometimes when I receive a call and I accept it and before I get a chance to click the speaker (if I want to hear it out loud) the screen will go black and no matter weather I hold it to my ear and lower it the only way to get back to it is hit the end button (which will end the call). Now this has been happening with every rom I've installed so It can't be the roms or is it.
PS. I have read in some other forums (with ww anyway) to press the send button or trackball. No go.

1)after youve engaged in phone conversation you should be able to shake the phone sharply(i just give it one good swype... like im gonna throw it on the ground :eek: ) and make the screen come back on so you can push speaker or dial pad. sometimes the screen may not stay on long enuff to push the button so youlll have to do it a couple of times.(*note: the screen not staying on long i dont think is the fault of the rom. every one ive tried is the same,including stock 2.2.1 on my droid 1)

*edit: you might also try the volume buttons. im not sure if that will bring the whole screen back,or just the in call volume bar.

2. When having a conversation sometimes it will make the sounds as when one is hanging up and the call drops and the wierd thing is a second or two later it will make the sounds again and the other party is still talking like nothing happened. Sometime it will just drop. Bear in mind that this happens every now and then but it really gets on my nerves.:mad:

Has this problem happened to any of you?:confused:

2)i did experience the click you described once,but so far its only been the once so i dint give it much thot. i hope it doesnt become an annoying issue cause i still like this rom alot(froshedyo vanilla)

3) back to the battery discussion- the OCed processor may use a lil more use when its processing heavily. setting the min at its old max threoretically the battery drain would not be any worse than stock when its not thinking very hard. setting the min lower may help with battery drain,as it wouldnt be spinnins as fast when its not thinking real hard.

the potential battery savings come from setting the values lower when the phone is sleeping. im not sure why the min and max shouldnt be set the same(like 245 or 190) as it doesnt seem the phone will ever use its max while sleeping. i set mine differently(245 and 528) after some pokin around as this is what seemed to be workin for people.

when chosing sleep settings just dont set them too low as this may make the phone "groggy" and a lil slower to wake up :)
 
1. There's one little thing that has really be getting on my nerves.:mad: Sometimes when I receive a call and I accept it and before I get a chance to click the speaker (if I want to hear it out loud) the screen will go black and no matter weather I hold it to my ear and lower it the only way to get back to it is hit the end button (which will end the call).

This has probably only happened with the CyanogenMod Froyo ROMs, I'll bet. I believe that if you press vol-up and send at the same time the screen will reappear without losing the call. See the KF FAQ, partway down: https://github.com/punk-kaos/KaosFroyo/wiki/kaosfroyo-faq . This has never happened to me, but I've read about it often with the Froyo ROMs, and never with a 2.1 based ROM - at least the HTC Frameworks ROMs like xtrROM, xtrSENSE, Evil Eris, Sensable, etc.

2. When having a conversation sometimes it will make the sounds as when one is hanging up and the call drops and the wierd thing is a second or two later it will make the sounds again and the other party is still talking like nothing happened. Sometime it will just drop. Bear in mind that this happens every now and then but it really gets on my nerves.:mad:

Again, this is a well-known CyanogenMod problem. I believe it also happened with the 2.1 based, CyanogenMod 5 based ELB by Conap. There is a big discussion about that here, I believe, but I know that EU1 started one for sure on xda-developers: [Q] What's up with Froyo/CyanogenMod "Undead" calls? [UPDATED 9/14/2010] - xda-developers

The solution to both, if it really bugs you enough? You may not like it, but start using xtrROM or xtrSENSE (or PlainJane or xtrRCMix or EvilEris etc.).
 
Thanks, but it's not enough to make me change roms. Now I know it's an issue and you've gave me something to read up on.:)

There was one more thing that somebody noticed - it may have nothing to do with anything (based on what i have read in that thread at xda). However, somebody reports that selecting settings->wireless & networks->mobile networks->national data roaming on seems to fix this problem. Give it a try and report back (though, of course, it takes a long time to determine that something that happens randomly isn't happening.)

If EU1 reads this, one thing that I have noticed in Cyanogen ROM is that when I turn on WiFi, it turns off the 3G data - but, when it does, the signal indicator gets a very brief "no signal" indicator. I wonder if the phone issue happens when a background app trying to send data over 3G tries to enable data, which is immediately turned off because you are in a call - giving that brief "no signal" situation, forcing the call to briefly disconnect?

In other words, perhaps a solution is to use something like the app Tasker to automatically disable data when a phone call is made or received and re-enable when the call is ended?

are all of these 2.1 based roms?

Yes. As far as I know, nobody has seen this behavior is ROMs based on the stock (or stock Hero) Sense-based ROMs. I imagine the same would be for the beta 2.2 ROMs, though, of course, you sacrifice all of the things not working in those ROMs now (i.e., the camera).
 
There was one more thing that somebody noticed - it may have nothing to do with anything (based on what i have read in that thread at xda). However, somebody reports that selecting settings->wireless & networks->mobile networks->national data roaming on seems to fix this problem.

do you really mean national data roaming? this option says it will "allow you to use a different network provider in your country".

international data roaming,on the other hand, is "connect to data services when roaming"

i have finally traced the troubles i was having sending picture messages to not having the latter checked(international data roaming)

when i flashed nonsensikal, settings were automatically checked on data enabled and international data roaming. national data roaming was unchecked,and system select was set to automatic. with these settings the picture messages went right thru as long as wifi was disabled. sending a pic message with wifi on,the message would stay in limbo until wifi was disabled,then it would go right away.

when i was having issues with v10,i had had it backwards... national data roaming checked,and international data unchecked. with these settings,messages would sometimes stay in limbo for extremely long periods of time wether wifi was enabled or not.

when i flashed vanilla i made sure the settings were as mentioned above,and my pic mssging is fine. i reloaded my v10 backup,flashed the black on black fix,and changed the settings to same as above. dint play with it for long,but looks like it behaves the same now as what nonsensikal and vanilla do.

i checked on my droid 1(stock 2.2.1) to see what it was set on to find that there is only one box to check-to enable data while roaming(or not). there were not national and international settings.

i dont know that my findings are relevant to the call issue,but thot i would mention it since they definately had a direct impact on the prollem i was having with my picture messaging. :)
 
If EU1 reads this, one thing that I have noticed in Cyanogen ROM is that when I turn on WiFi, it turns off the 3G data - but, when it does, the signal indicator gets a very brief "no signal" indicator. I wonder if the phone issue happens when a background app trying to send data over 3G tries to enable data, which is immediately turned off because you are in a call - giving that brief "no signal" situation, forcing the call to briefly disconnect?

In other words, perhaps a solution is to use something like the app Tasker to automatically disable data when a phone call is made or received and re-enable when the call is ended?

neat. i just tried this,and sure enuff when i turned on wifi via the power bar, the wifi icon would appear in the left corner very briefly,then replace the 3g icon to the left of the signal strength indicator,with a little X appearing and the disapearance of the signal bars for just a split second.

i notice that turning wifi back off results in no signal loss.

your theory as to why t he call issue exists sounds quite reasonable,and likely. :cool:

as mentioned above,i have international data roaming checked,national data roaming unchecked,and system select set on automatic. have you tried changing these settings to see if the momentary signal loss is affected?
 
do you really mean national data roaming? this option says it will "allow you to use a different network provider in your country".

international data roaming,on the other hand, is "connect to data services when roaming"

Definitely National Data Roaming. See these posts:

[ROM][GPL] CELB Froyo 4.1(Plain CM Rom)1-9-10 - Page 190 - xda-developers
[ROM][GPL] CELB Froyo 4.1(Plain CM Rom)1-9-10 - Page 191 - xda-developers
[ROM][GPL] CELB Froyo 4.1(Plain CM Rom)1-9-10 - Page 191 - xda-developers



i have finally traced the troubles i was having sending picture messages to not having the latter checked(international data roaming)

when i flashed nonsensikal, settings were automatically checked on data enabled and international data roaming. national data roaming was unchecked,and system select was set to automatic. with these settings the picture messages went right thru as long as wifi was disabled. sending a pic message with wifi on,the message would stay in limbo until wifi was disabled,then it would go right away.

when i was having issues with v10,i had had it backwards... national data roaming checked,and international data unchecked. with these settings,messages would sometimes stay in limbo for extremely long periods of time wether wifi was enabled or not.

when i flashed vanilla i made sure the settings were as mentioned above,and my pic mssging is fine. i reloaded my v10 backup,flashed the black on black fix,and changed the settings to same as above. dint play with it for long,but looks like it behaves the same now as what nonsensikal and vanilla do.

i checked on my droid 1(stock 2.2.1) to see what it was set on to find that there is only one box to check-to enable data while roaming(or not). there were not national and international settings.

i dont know that my findings are relevant to the call issue,but thot i would mention it since they definately had a direct impact on the prollem i was having with my picture messaging. :)

Oh, wow. That's good to know. Excellent. I'm going to save your post in case I see that problem again.


neat. i just tried this,and sure enuff when i turned on wifi via the power bar, the wifi icon would appear in the left corner very briefly,then replace the 3g icon to the left of the signal strength indicator,with a little X appearing and the disapearance of the signal bars for just a split second.

i notice that turning wifi back off results in no signal loss.

your theory as to why t he call issue exists sounds quite reasonable,and likely. :cool:

as mentioned above,i have international data roaming checked,national data roaming unchecked,and system select set on automatic. have you tried changing these settings to see if the momentary signal loss is affected?

Here's the thing: lucky me, I have never had that interrupted call problem.
 
Oh, wow. That's good to know. Excellent. I'm going to save your post in case I see that problem again.

lol im happy to finally be able to contribute a lil something :D

thinkin maybe i should check national data roaming box(so theyre both checked) give it a reboot and see if it changes anything picture message wise.


Here's the thing: lucky me, I have never had that interrupted call problem.

what do you have your mobile networks settings on?

i only had the interupted call prollem once,and i know my settings were as mentioned above.
 
what do you have your mobile networks settings on?

Data enabled: checked (unless I am out running - I turn it off then)

International data roam: off. (I've gone close to the Canadian border and I definitely don't want to pay roaming charges on data.)

National Data Roaming: On. I own a summer house in US Cellular territory, which must have a roaming agreement with VZW, as I occasionally see "Extended network". I want data in that case.

System Select is auto.

One thing is that I am frequently in areas with WiFi enabled and on, so a lot of calls that I get happen when I am on WiFi rather than VZW 3G. That said, again, even when I am away from WiFi, I never had this problem.
 
Okay. I just noticed a serious problem. When i open my web browserand type something in the adress. Bar I can't see the text! I believe this is a new issue. I did flash that file for the white on white submenu issue!

Does anyone know how to fix this?
 
Okay. I just noticed a serious problem. When i open my web browserand type something in the adress. Bar I can't see the text! I believe this is a new issue. I did flash that file for the white on white submenu issue!

Does anyone know how to fix this?


There were two fix files. After flashing fix2, the wht/wht issue was fixed for
most screens. Just checked browser, market, xscope and all are fine. Other sub menus in apps that I have still are not fixed.

I posted this on xda and Workshed is aware of it and must have removed the thread this morning as I cannot find it.

Hopefully, He will fix it soon.

Sf
 
Just wanted to chime in here to say that I have been using this ROM for two days. As far as I can see, everything works as it should. Everything is also very fast and snappy. And... Battery life seems to be pretty good too!

All in all I am very happy I switched from nonsensikal. Excellent job!
 
Okay. I just noticed a serious problem. When i open my web browserand type something in the adress. Bar I can't see the text! I believe this is a new issue. I did flash that file for the white on white submenu issue!

Does anyone know how to fix this?

in vanilla the text shows up on the stock browser. i dont know if i had that issue with the themed v10,as i dont use the stock browser. have you tried dolphin or skyfire? i prefer dolphin,but skyfire does have the added benefit of being able to play some flash videos. :)
 
got a question i am kinda new to this but i know what i am doing so i downloaded froyo a couple of days ago and i listen to a bunch of music plus my pandora in the car well i use the head phone jack to hook into my radio but froyo is not recognizing the jack so has anyone had any problems with this rom?
 
2. When having a conversation sometimes it will make the sounds as when one is hanging up and the call drops and the wierd thing is a second or two later it will make the sounds again and the other party is still talking like nothing happened. Sometime it will just drop. Bear in mind that this happens every now and then but it really gets on my nerves.:mad:

this is a well-known CyanogenMod problem. I believe it also happened with the 2.1 based, CyanogenMod 5 based ELB by Conap. There is a big discussion about that here, I believe, but I know that EU1 started one for sure on xda-developers: [Q] What's up with Froyo/CyanogenMod "Undead" calls? [UPDATED 9/14/2010] - xda-developers


Ok, there is a new update in EU1's thread that I quoted above at XDA. It seems that flashing the Sprint Hero radio version 2.42.02.10.29 may solve this problem, and it may give you stronger signal strength to boot. See xda-developers - View Single Post - [Q] What's up with Froyo/CyanogenMod "Undead" calls? [UPDATED 9/14/2010]

To get the new radio (and don't freak out that it is a radio for the Sprint Hero - both the Hero and the Eris use CDMA, are, with the exception of the Eris's proximity sensor, essentially the same hardware), you can find a flashable .zip file with installation instructions here: xda-developers - View Single Post - [Radio] NEW! 2.42.02.10.29 Sprint CDMA Hero

Step 7, where it reboots to recovery and says "Formatting cache..." at the bottom? It will say that until the battery dies if you do nothing. The instructions say to wait 5 seconds after the menu appears and then reboot. I waited a minute myself, but that "Formatting cache..." messages does not disappear when cache is formatted - the menu appears when that step is done.

Note: CHECK THE MD5 OF THE 2.42.02.10.29.zip FILE! If you download it to your PC and copy to your SD card, CHECK THE MD5 OF THE FILE ON YOUR SD CARD AS WELL!

(That said, Amon's Recovery will prevent you from flashing a bad file, but do it anyway.)
 
Back
Top Bottom