Baked Snack Froyo EB13/EC05 "More Undisputed ;)"

[sinfony78]

couple things

i downloaded BS2.1 from this thread and installed. i get this:

Kernel Version: 2.6.32.9
Build Number: Baked Snack 2.0

and I no longer have an android keyboard, can only use swype

can someone comment on these 2 things please?

 

[ragnarokx]

Hero forgot to edit build.prop - you have the correct version.

Copy this apk to /system/app on your phone.

 

[sinfony78]

sorry, how do i copy stuff over to system folder...i used to be able to do it using ES File Explorer with the option for root access, but it doesn't work anymore...i also don't see any option like that in Astro

 

[ragnarokx]

My preference: Root Explorer, however it is a paid app.

Free option: ES File Explorer. You need to enable the root explorer feature in ES. Go to: Menu>Settings>Root options and check both boxes. When it asks you which ROM you're on, choose Cyanogen. This will allow you to copy apk files with executible permissions.

 

[sinfony78]

i already tried ES explorer with both ROM options (cyanogen, hiAPK) and both say "test failed. sorry this feature cannot be used on your phone"

EDIT: well, i was getting force closes on the gingerbread keyboard after flashing, so i reinstalled it from the market and it seems to work now...after a minute of using it, i can work with it and probably don't need the apk you sent...i'll see how this goes

thanks

 

[ragnarokx]

Gonna make me do this the hard way huh?

Flash this zip that I made in Clockwork: Samsung KB

I strongly recommend investing in Root Explorer. It is hands down one of the most frequently used tools I own.

 

[duytienle]

So everything was working wonderfully. Then I flashed the 1.2 Low kernel still great. Then 1.28 Low and now I'm getting this drm process error. I'm trying to remember if i did anything else but I can't think of anything. Any one else have this problem?

 

[thebullfrog]

Well the fun is over . The phone keeps locking up whenever its asleep for more than like 5 minutes and I have to do a battery pull. At first I attributed it to an app, but after removal the problem persists. Worse yet the battery life is simply ATROCIOUS. I put the phone to sleep at midnight last night with 96% battery. At 7:30 AM (after doing another battery pull) it had 21% remaining. So in 7 hours of being asleep it used some 70% of the battery, whereas it normally uses about 5% or so. It's a shame because it was great in use and I certainly notice the drop in performance being back on Twilight, but it basically ruins the phone.

EDIT: I want to re-iterate that this did NOT happen with Baked Snack. I extracted the Baked Kernel and used it with SRF. The Baked Snack ROM/Kernel may actually work fine, as this may be an issue from combining the Kernel with a ROM it wasn't intended for, or could simply mean the undervolting played havoc with my particular batch of silicon, so don't take my observations as a demerit against the Baked Snack ROM itself.

It may be worth someone else trying the Kernel on it's own to see if they run into the same problems, because the performance was quite frankly fantastic, just make sure to do a Nandroid backup beforehand.

 

[GSF1200S]

Well the fun is over . The phone keeps locking up whenever its asleep for more than like 5 minutes and I have to do a battery pull. At first I attributed it to an app, but after removal the problem persists. Worse yet the battery life is simply ATROCIOUS. I put the phone to sleep at midnight last night with 96% battery. At 7:30 AM (after doing another battery pull) it had 21% remaining. So in 7 hours of being asleep it used some 70% of the battery, whereas it normally uses about 5% or so. It's a shame because it was great in use and I certainly notice the drop in performance being back on Twilight, but it basically ruins the phone.

EDIT: I want to re-iterate that this did NOT happen with Baked Snack. I extracted the Baked Kernel and used it with SRF. The Baked Snack ROM/Kernel may actually work fine, as this may be an issue from combining the Kernel with a ROM it wasn't intended for, or could simply mean the undervolting played havoc with my particular batch of silicon, so don't take my observations as a demerit against the Baked Snack ROM itself.

It may be worth someone else trying the Kernel on it's own to see if they run into the same problems, because the performance was quite frankly fantastic, just make sure to do a Nandroid backup beforehand.

Yeah, that has to be a conflict with SRF/baked snack kernel. I backed up ACE rom and installed the entire BakedSnack ROM and the battery life is incredible. 2 hours off the wall and its at 98% (and remember the annoying Epic bug where it shortly drops to 97% after 100% elapses!), and thats after installing a few things (flash, couple of apps, etc).

Only 1 thing is supremely annoying with this ROM: if one uses the menu button, the text under the icons (regardless of what app menu options are being accessed, including the ADW launcher options) is completely unreadable unless you click on the respective menu option. Its fine once out of the menu options at the bottom (fine once a window opens as opposed to just the box at the bottom with options). For example: try to import/export a contacts list in Contacts- one can see the import/export icons fine, but the text is unreadable. This is a theming issue, so its not likely the fault of Baked Snack itself. Not a dealbreaker, just highly annoying at times- especially with apps that heavily utilize the menu key (gmail).
**EDIT 3** I feel so stupid. I simply did not even see "Menu Fix" in red bold letters at the beginning of the thread. I get angry with myself when I do stupid things like this. Thanks for the quick fix to this problem, and never mind my temporary stupidity.

I still had major issues with the Gallery, but I like QuickPic more anyways, so it doesnt matter.

Another minor bug: I downloaded and flashed Baked Snack 2.1, but it shows Baked Snack 2.0 in the About Phone screen. I know im on 2.1 by comparing the features I have with the feature list of 2.1 on this thread.

Very nice ROM though- battery life has been awesome and +1,000,000 awesome points for deciding to use a different SMS client than the ugly bubble iphone ripoff..

Kudos Herver...

**EDIT**
Wow, almost forgot this bug! For some reason, if I try to enable Gingerbread keyboard, i keep getting a Force Close on Gingerbread keyboard, whether im attempting to use it or not. Problem is solved by just using swype.

**EDIT 2** Removed Gingerbread keyboard with Titanium Backup (free) and installed Keyboard from Android 2.3 from the market (Gingerbread Keyboard) and Gingerbread Keyboard works fine.

 

[Cel]

I'm running 2.2 from his forum. My phone has never been sweeter frankly. I have almost zero interest in updating to ec05 until hero gets his mitts into it.

Sent from my SPH-D700 using Tapatalk

 

[ragnarokx]

I'm running 2.2 from his forum. My phone has never been sweeter frankly. I have almost zero interest in updating to ec05 until hero gets his mitts into it.

Sent from my SPH-D700 using Tapatalk

Just one more reason not to update to EC05. Not for a while anyway..

 

[junglejiujitsu]

Just one more reason not to update to EC05. Not for a while anyway..

I agree, I haven't seen anyone post any reason to do so as of yet....

 

[thebullfrog]

I agree my issues were likely a conflict that sowed up by combining he kernel with SRF. I'm extremely happy with my current set-up, but I think I might run a nandroid backup and give the full ROM a try down the road a bit. My gf might choke meout if she catches me re-flashing this thing again lol.

 

[a_c_s]

I am on midNIGHT 4.2, have the 0.3a kernel mod, and just flashed the EC05 modem last night... no problems whatsoever... am I missing something? Is the kernel I have less optimal now than with EB13? My battery life has been the same... granted I can't wait for an EC05 kernel from BS, but in the meantime, the setup is stable and works fine...

 

[GSF1200S]

One issue: Bluetooth voice dialer loads when I push call button on headset, but it errors out right away (says "Error Occurred" on screen). I can still talk on the headset if I make the call from the phone.

Also, it almost seems the CPU scales in an On-Demand fashion as opposed to Conservative (which is the setting I have selected in SetCPU). I could be wrong, but I thought id see what others thought...

 

[eharty]

I flashed Baked Snack 2.1 a couple of days ago and it is running great. Today when I plugged my Epic into my laptop's USB port, it started looking for drivers. All the steps went OK except for RNDIS Communications Control which could not be installed. I uninstalled and reinstalled the Samsung drivers (32 bit on Vista) and got the same message about unable to install RNDIS Communications Control. Any suggestions? I just want to make sure I don't have any issues with Odin because of this.

 

[Paul627g]

I flashed Baked Snack 2.1 a couple of days ago and it is running great. Today when I plugged my Epic into my laptop's USB port, it started looking for drivers. All the steps went OK except for RNDIS Communications Control which could not be installed. I uninstalled and reinstalled the Samsung drivers (32 bit on Vista) and got the same message about unable to install RNDIS Communications Control. Any suggestions? I just want to make sure I don't have any issues with Odin because of this.

Ed, I had the very same issue on my laptop. All the sudden the RNDIS Communications Control driver wouldn't install.. I still haven't really resolved it, but it still connects fine for mass storage transfers and charging.

I did use Odin too and also rooted with this RNDIS driver issue still going. I did some Google searches and really couldn't find a fix for it. If you find something please PM me with the info and I will make sure its posted around here somewhere..


BTW, the laptop I had issues was a Dell Inspiron running Windows Vista 32 bit. It was always my go to machine for Odin and Rooting then out of nowhere this RNDIS thing happened.

 

[eharty]

Ed, I had the very same issue on my laptop. All the sudden the RNDIS Communications Control driver wouldn't install.. I still haven't really resolved it, but it still connects fine for mass storage transfers and charging.

I did use Odin too and also rooted with this RNDIS driver issue still going. I did some Google searches and really couldn't find a fix for it. If you find something please PM me with the info and I will make sure its posted around here somewhere..


BTW, the laptop I had issues was a Dell Inspiron running Windows Vista 32 bit. It was always my go to machine for Odin and Rooting then out of nowhere this RNDIS thing happened.

Thanks Paul. Glad to hear it doesn't seem to have any negative impact. I have been searching the Epic forums here on Android Central and found mention in a Syndicate ROM thread. Under kernel features it says "RNDIS no longer conflicts with ADB". Perhaps the same problem here.

I gather you change ROMs quite often. Did this happen after flashing Baked Snack by chance?

I'll keep looking for a fix or maybe Herver will have one.

 

[Paul627g]

Thanks Paul. Glad to hear it doesn't seem to have any negative impact. I have been searching the Epic forums here on Android Central and found mention in a Syndicate ROM thread. Under kernel features it says "RNDIS no longer conflicts with ADB". Perhaps the same problem here.

I gather you change ROMs quite often. Did this happen after flashing Baked Snack by chance?

I'll keep looking for a fix or maybe Herver will have one.

It may have, I've flashed so many different things over the last few days I can't remember. LOL.

 

[ESlogic]

The Rom runs fine until i reboot the 2nd time. so weird. i flashed a few times, wiped everything but each time, i would get FC on the second boot. also, ESfile explorer ask for permission, but it says im not my system isn't able too. and before someone asks, yes after second boot, on every single flash. anyone have any Similar experience?
-Details of last try. if i left my phone on all night, and it was fine. i turned it off, charged, turn it back on. worked fine. then i decided to reboot around 3/4 later to see if problem was still there, and it was.