yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] CyberpodS2:
Hey bro, v1.1.0 is rockin! I wanted to ask if you can look into why on the AOSP recovery you can hold up or down to scroll through the files to flash but not on these. I can only guess, but I hope it's a feature that could be brought over?? I did not even realize how much I use it till I missed it. :) Thanks again man.
[Samsung Epic 4G Touch] agat63:
I'm not sure I understand what you mean.

You can scroll up and down with this recovery as well.

Never did run AOSP/AOKP or CM roms so I can't compare.

Can you be a bit more specific?
[Samsung Epic 4G Touch] dataman:
Can we get rid of the warning right before reboot in recovery?

Do u want to keep the recovery?

Or something like that...
[Samsung Epic 4G Touch] agat63:
What warning?

I didn't spend much time with my wife's phone yesterday but can't recall any warnings.

May be I missed it or didn't pay attention.

When does it happen?

If I know what I'm looking for I might be able to find it and possibly fix it.
[Samsung Epic 4G Touch] CyberpodS2:
install zip from sdcard > try holding down the op or down buttons. on my phone, I need to keep hitting the button to go from file to file. on some kernels you can hold down and it will scroll.
[Samsung Epic 4G Touch] agat63:
Gotcha.

Now I understand what you talking about.

Will have to download AOSP recovery source and compare. (run diff).

May be can figure out where and how it's done.
[Samsung Epic 4G Touch] dataman:
Not a warning but this screen right before reboot.
[Samsung Epic 4G Touch] agat63:
I'm positive I did reboot few times while doing back up, flash and restore but I never saw that screen.

Anyone else have this warning while trying to reboot to system?

What rom are you running?

May be it's somehow rom related?
[Samsung Epic 4G Touch] Slobadon:
I think im going to try and run through all 4 test versions here in order. Im on Project-X with 3minit and Comadose 1.5 which is optimized for agats 1.3. I will remove comadose and then flash the test versions and report back here for edits. Im mostly concerned about the phone turning off and freezes as I got that on 1.4 and not 1.3. Are they're any other particular actions I need to run through? Never really done a test like this so any heads up on what to look for would be helpful. After some time for settling, I'll flash CB on the F versions. I suppose I'll flash the latest at the time. And by flash I mean mobile ODIN

- For organizational purposes...

Edit- Whoops. went out of order a bit. I've been running the second one listed, 1.4.2.tar for half the day. First half the day on the charger then on my way home I started using more heavily. Froze on the notifications drop down actually, pulled battery. Then I was using the XDA premium app and let the screen time out then came back to SOD, twice. 8hrs

Edit- 1.4.2F with CB 6.23 for 10 hours - over night and no problems 24hrs

Edit - 1.4.3 is loaded up with CB 6.23 and still no problems for me, well I got a SOD over night. I did not get an SOD the second night. 48 hrs

Edit 1.4.f is now loaded, along with CB 6.23 from the start. Wow, I didnt even have to post this edit, It frooze within the 1st hour. And then frooze again the next hour running 4g and sprint wifi hot spot.

Back to 1.4.2F!
[Samsung Epic 4G Touch] remotehugger:
well, I went back to 1.4.3f yesterday and uninstalled CB 6.20 and haven't had a freeze up yet - gonna run it the rest of the day then try the new 6.23 CB and see what happens - I thought that CB 6.20 was meant to run with frandom ??? idk -

from jdsingle's deodexed ROM w/ agat63's 1.4.3f kernel - with TT 2
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Yes, as far as I know, all versions of CB are made to work with Frandom, although Frandom is optional. Note that I believe the author of CB considers it alpha or beta, so your mileage with different versions of CB may vary. I didn't have a great experience with 6.20 but 6.23 seems much better so far.
[Samsung Epic 4G Touch] jayhi74:
The new CB 6.23 seems too be playing well with Agats 1.4.3f flashed yesterday and its been running smooth using sio/ Pegasusq and Project X Rom.

sent from the 2Deuce4fo block
[Samsung Epic 4G Touch] remotehugger:
I am just having bad luck I guess - just had to hardboot 1.4.3f again - the only mod I have is the bootanimation4u zip that I flashed a few days ago - I wouldn't think that that's interfering with the kernel - gonna go back to 1.3 and see how that goes - so far, that's been the only one that doesn't freeze up on me -

from jdsingle's deodexed ROM w/ agat63's 1.4.3f kernel - with TT 2
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Still doing very well on 1.42F with CB 6.23.
[Samsung Epic 4G Touch] btvolta:
Me too. Not one issue to report.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] leaderbuilder:
Not to throw a towel on the bunch. But with and without CBi had issues of lockups and sod s on everything but 1.3. 1.40 was the fastest and most responsive for me. But even it would lock up doing system intensive things like turning Wi-Fi on and off, switching networks, and switching on and off ,3g/4g and playing streaming videos. I finally went back to 1.3.

Can't take the chance of not getting a server alive notice if the phone locks up in the middle of the night. But for the past two days while traveling and with heavy usage. my phone hasn't locked up or sod'd.

Maybe later in the week when I get some time I'll try some more Werth and without CB.

Either way Agat's support and those here in the community is just freaking great.
[Samsung Epic 4G Touch] remotehugger:
I agree - great folks and support ! and its the same for me, all versions of 1.4 have given my phone problems - with and without CB - I haven't tried the newest CB yet with any of the 1.4's - and rite now I'm just running 1.3 with no mods - I really like the way my phone responds with the frandom kernel and CB though - super fast and responsive -

from jdsingle's deodexed ROM w/ agat63's 1.4.3f kernel - with TT 2
[Samsung Epic 4G Touch] btvolta:
Almost 3 days on 1.42f and cb 6.23, and absolutely no issues.

Edit** Now over 3 days, no issues and battery life is good too.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] Doctor_XXX:
Same here. :good:
[Samsung Epic 4G Touch] btvolta:
Doing well on 6.26 now.

Sent from my SPH-D710 using Xparent BlueTapatalk 2
[Samsung Epic 4G Touch] remotehugger:
I don't get it - lol- must be my phone - no freezes or sod's since going back to 1.3 - and been running CB 6.26.13 since it came out with no issues -

from jdsingle's deodexed ROM w/ agat63's 1.3 kernel and CB 6.26.13 with TT 2
[Samsung Epic 4G Touch] Samsung Fanboy:
I have an update from my last post. I was on 1.4.3f with cb and V6 installed and I started to play more with the governors. I then started to experience the SOD and random reboots. I also noticed I couldn't get frandom to work properly either. So now I been on 1.4.2f with cb and V6 installed for 9 hrs. I have also been playing with the governors and have not came across a problem yet. Frandom is sticking and I did noticed a huge difference in my battery life on 1.4.2f kernel. No undervolt at the moment but I am on ondemand, sio, 1000mhz max with a 200mhz min. I think I have to agree with the others in this thread that 1.4.2f is the stable kernel. I tested 1.4.3f for a few days and there is a huge difference between the two kernels. Thanks for all your hard work.

Edit: I also noticed on 1.4.3f every time I reboot from recovery it always asked if I wanted to disable flash recovery. I always said yes but every time it asked again. 1.4.2f I don't have that problem.

Sent from my V6 Supercharged Samsung Galaxy S2
[Samsung Epic 4G Touch] remotehugger:
I thought that disable flash recovery came from CB - I get it as well -

from jdsingle's deodexed ROM w/ agat63's 1.3 kernel and CB 6.26.13 with TT 2
[Samsung Epic 4G Touch] leaderbuilder:
This option - disable flash recovery (in the custom recovery/cwm), had been discussed before. It is a great option of your flashing a ROM that has its own recovery and you wish to keep the one you're currently using to flash.
[Samsung Epic 4G Touch] Samsung Fanboy:
This I do know, what I was trying to say was I wanted it disable but it would never do it.

Sent from my V6 Supercharged Samsung Galaxy S2
[Samsung Epic 4G Touch] btvolta:
Well, it's been about 4 days now, and I haven't had any issues at all with 1.42F and different versions of crossbreeder installed. At this point, it has to be a very stable kernel.
[Samsung Epic 4G Touch] leaderbuilder:
Two days 1.42F NO crossbreeder and not a single lock up our freeze.

This weekend I'll grab the latest crossbreeder and spin that.
[Samsung Epic 4G Touch] helix4u:
Had 1.4.3F running for a while. With crossbreeder I eventually had a few freeze/reboots probably from hanging apps, but had less issues without crossbreeder. I've decided that I hate even the idea of dns caching, and I dont need the tether boost, so I'm upgrading my crossbreeder install to the latest and disabling the dns caching and tether boost portions of it. Meh, we'll see what that ends up doing for me... Oh, and for all you motorcyclists out there (I know there are a few in here), wear a helmet. One literally saved my little bro's life over the weekend. He's spent the week in the ICU along with a bunch of other motorcycle accident victims and has pretty extensive road to recovery ahead of him. As for the rest of you, it's that season, so watch out for motorcycles on the road. Thanks :)
[Samsung Epic 4G Touch] blackcanopy:
Just curious about the dislike of having DNS caching. I definitely Agee on disabling tether boost (only because I don't tether).

Thanks for the warning for the motorcyclist. I've been enjoying the open road with my knees in the breeze for about 23yrs now. A good friend of mine was hit 2 weeks ago by a driver not paying attention... But somehow he and his wife suffered no serious harm.

I'm very sorry to hear about your little brother. My prayers will be going out for him and your family. I pray for a speedy recovery.
[Samsung Epic 4G Touch] helix4u:
Thanks. He's lookin better every day.

The dns cache thing is more because of how I use the device. My networks are always changing. That and some minor issues with some public wifi... I wouldn't mind it if I could exclude certain subnets and junk.
[Samsung Epic 4G Touch] agat63:
Hey bro!

My best wishes to your little bro.

I've been in a bad accident this April and totaled my car.

Still recovering and I know what it is.

Hope for fast and full recovery for your brother.

And wish patience to all of your family thru this hard time.
[Samsung Epic 4G Touch] btoddweber:
So is the consensus leaning towards the 1.42?
[Samsung Epic 4G Touch] btoddweber:
Thread's been quiet
[Samsung Epic 4G Touch] cdss:
1.4.2f, no problems at all :thumbup:
[Samsung Epic 4G Touch] remotehugger:
I'm still stuck on 1.3 - all other variants cause complete freeze ups - :(

jdsingles deodexed ROM w/ agat63's 1.3 kernel Suped up w/ CB 7.2.13
[Samsung Epic 4G Touch] jayhi74:
I'm on 1.4.3f with 7.2 crossbreeder running smooth!

sent from the 2Deuce4fo block
[Samsung Epic 4G Touch] btoddweber:
So still lots of different scenarios..... Hmmm
[Samsung Epic 4G Touch] remotehugger:
Ok - fresh flash of jd's deodexed rom - no tweaks or mods - gonna try 1.43f and see what happens ! Fingers crossed !
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Rots of ruck! ;)
[Samsung Epic 4G Touch] remotehugger:
Froze up all ready - lol - wasnt even using it - phone just went to sleep and wouldnt wake up - gonna try 1.42f no and see how that goes -
[Samsung Epic 4G Touch] remotehugger:
Is this still 1.4.2f ? I dwnlded 1.4.2f and ot said that was what was flashing but now im not sure -
[Samsung Epic 4G Touch] remotehugger:
And are the original links gone ? I can only find up to 1.4.0 - and all the links given for 1.4.2 arent working ???
[Samsung Epic 4G Touch] btoddweber:
http://xdaforums.com/showthread.php?p=42789513

Try here
[Samsung Epic 4G Touch] blackcanopy:
Page 51 contains 1.4.2...

Page 52 contains 1.4.3...

http://xdaforums.com/showthread.php?p=42792112
[Samsung Epic 4G Touch] remotehugger:
Yea I tried those and niether one will let me click on them - am I doin' something wrong ? I can tap on your link and it takes me to the page but the dwnld links dont do anything -
[Samsung Epic 4G Touch] blackcanopy:
I taped then and it takes me to the download.
[Samsung Epic 4G Touch] remotehugger:
Well what the heck - lol - I have all my originals - 1.3.0 - 1.4.3f - just when I flashed my 1.4.2f it only shows as 1.4.2 in my settings soni wanted to re-dwnld it to make sure - idk why I cant get those links to work for me - very strange -

I just tried through tapatalk and it didnt work for me there either - AAAAAAGGGGHHHHHH.....whats wrong with my phone ?????? :confused:

---------- Post added at 09:46 PM ---------- Previous post was at 09:40 PM ----------

Ok - I cant open any dwnld links - just tried the deodexed AIO 4.0 and it didnt work either ???
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Try rebooting.

And yes that's 1.42F, as evidenced by the older version of Linux. 1.42 (not F) had a newer Linux.
[Samsung Epic 4G Touch] remotehugger:
Nothing - cleared eveything - un and re-installed xda and tapatalk - still no luck - could it be rom related ? Bad flash maybe ?

---------- Post added at 10:13 PM ---------- Previous post was at 10:08 PM ----------

OMG - im pretty sure im an idiot - let me do something real quick - brb......

---------- Post added at 10:18 PM ---------- Previous post was at 10:13 PM ----------

Well there you go - im embarrassed to tell you guys and sorry for wasting your time, but.........I forgot I deleted the stock browser ! DOH ! ! Hahahahahahaha ! So installed Chrome and all is well -
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Glad it was something simple!
[Samsung Epic 4G Touch] remotehugger:
Simple it was - smart it was not - lol - but def. glad it was simple - and glad I didn't start reflahing roms - lol - and thanks again for all the help - and btw, so far so good on 1.4.2f !
[Samsung Epic 4G Touch] btoddweber:
Using any tweaks?
[Samsung Epic 4G Touch] remotehugger:
No - nothing yet - gonna see how it does for a day or two and if all is well will try latest CB -
[Samsung Epic 4G Touch] btoddweber:
OK...running 1.3 w/ Comadose V2 and didn't know...thanks
[Samsung Epic 4G Touch] remotehugger:
OK - left phone on all night on 1.4.2f and so far so good - still no mods or tweaks - just jdsingles deodexed rom - oh yes, running at 300/1400 w/ smart@ssv2/sio - gonna let it run all day again and then add latest CB -
[Samsung Epic 4G Touch] remotehugger:
2 and a half days now without a problem on 1.4.2f - still no tweaks or mods but gonna start adding some stuff 1 by 1 starting with latest CB -

From my VM SG II w/ jdsingles' deodexed rom and agats' 1.4.2f kernel @ 1.4Mhz.
[Samsung Epic 4G Touch] jdsingle76:
Let me know as you add stuff remote. When I finish my custom build I intend on baking this kernel and some tweaks/mods in, and it'll be good to know what works and doesn't work.
[Samsung Epic 4G Touch] JonSCSL:
I am still getting random fc on video player is that still a normal annoyance we all deal with if we didn't debloat?
[Samsung Epic 4G Touch] remotehugger:
I have never used the stock video player and always delete it - so can't weigh in on that - sorry -

From my VM SG II w/ jdsingles' deodexed rom and agats' 1.4.2f kernel @ 1.4Mhz.

---------- Post added at 04:36 PM ---------- Previous post was at 04:35 PM ----------

Will do - gonna flash CB first -

From my VM SG II w/ jdsingles' deodexed rom and agats' 1.4.2f kernel @ 1.4Mhz.
[Samsung Epic 4G Touch] jdsingle76:
What rom?
[Samsung Epic 4G Touch] JonSCSL:
Kobridge's GB27 Stock Deodexed, AIO 4.0
[Samsung Epic 4G Touch] jdsingle76:
Hmmm...and you're getting fc with Agat's kernel with your video player?
[Samsung Epic 4G Touch] JonSCSL:
All Agat kernels other than stock.
[Samsung Epic 4G Touch] jdsingle76:
That's weird. I've not had that issue running Agat's kernel.
[Samsung Epic 4G Touch] Samsung Fanboy:
I tried all versions of this kernel and I never had a problem with video player.

Sent from my V6 Supercharged Samsung Galaxy S2
[Samsung Epic 4G Touch] jdsingle76:
Yeah, I'm thinking there's a conflict elsewhere. I've never had an issue, nor heard of one, between this kernel and stock video player :)
[Samsung Epic 4G Touch] JonSCSL:
There is another thread a little while back that others were talking about this problem. I am gonna find it and post back.
[Samsung Epic 4G Touch] leaderbuilder:
I'll jump in. John is right this ess discussed. Send no-one of the source built kernels will let you open the video player with it a force close.

However, if you launch a video from the web and are asked to choose the player you can choose the video player and if you open a file with the player it still play; you can't open the player and then open the file. If that makes sense
[Samsung Epic 4G Touch] jdsingle76:
Thanks! That sort of clears it up, except your autocorrect is killing me, lol :)
[Samsung Epic 4G Touch] Samsung Fanboy:
I don't get what he was trying to post but on all of Agat's kernels I have used when I open stock video player I get no fc's and all my videos show with their live thumbnails and they play when I click on one, also when I open it from a link on a web site it still works like it should.

Sent from my V6 Supercharged Samsung Galaxy S2
[Samsung Epic 4G Touch] JonSCSL:
Whats your rom?
[Samsung Epic 4G Touch] remotehugger:
Just wanted to say that I've been running 1.4.2f for 3 days now with no problems - 1 day with latest CB -

From my VM SG II w/ jdsingles' deodexed rom and agats' 1.4.2f kernel @ 1.4Mhz.
[Samsung Epic 4G Touch] blackcanopy:
It sounds like you are are running JellyVerse, which is using a ported video player, not "stock" video player. The stock video player doesn't have live thumbnails.
[Samsung Epic 4G Touch] btoddweber:
remotehugger...did you flash the kernel first then tweaks or after tweaks?

Also anyone have success with mobile Odin after tweaks? Read some different thoughts on that.

Just seeing if one of these has been dubbed as stable as this awesome 1.3(thanks Agat):thumbup::thumbup:
[Samsung Epic 4G Touch] remotehugger:
Yes - I flashed the kernel first and ran it a couple days to make sure all was well - then added CB -
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I believe I've had the experience where I had problems with Mobile ODIN, but I'm guessing it might've been only when I was trying to flash from the "external" SD. Since I started keeping things to flash with it on my internal SD, I haven't had any problems with Mobile ODIN.
[Samsung Epic 4G Touch] blackcanopy:
+1 on this. That's the only time I've had trouble with mobile Odin as well.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I'm glad it's not just me :)
[Samsung Epic 4G Touch] btoddweber:
So are the masses leaning towards with f or without?

Been trying to follow the thread and googling....just seems to be a lot of mixed reviews.
[Samsung Epic 4G Touch] remotehugger:
I've been using 1.4.2f for almost a week now with no problems at all !
[Samsung Epic 4G Touch] Samsung Fanboy:
I am on Ko's stock GB27 rom!

Sent from my V6 Supercharged Samsung Galaxy S2
[Samsung Epic 4G Touch] GrimeSyndicate:
Same here: 1.4.2F for over a week and not a single problem I could attribute to the kernel...
[Samsung Epic 4G Touch] CyberpodS2:
+1 here!
[Samsung Epic 4G Touch] dataman:
I guess its time to put the link to 1.4.2F on op.

Sent from my SPH-D710
[Samsung Epic 4G Touch] btoddweber:
Thanks guys....did y'all flash the kernel before or after tweaks were installed?

Or does it not matter?
[Samsung Epic 4G Touch] CyberpodS2:
Hmm, pretty sure flashed White Out Rom 5.0 then Comadose 2.0 then the kernel 1.4.2f
[Samsung Epic 4G Touch] remotehugger:
I've flashed tweaks after kernel - then only flash one at a time to make sure all is well -
[Samsung Epic 4G Touch] btoddweber:
I know it was explained somewhere I just cannot find it.....

Is there one of these kernels that's basically 1.3 with Frandom???

Thanks in advance
[Samsung Epic 4G Touch] Cricket Droid:
I believe 1.4 is the one that your looking for, its in the op

---------- Post added at 02:25 AM ---------- Previous post was at 02:17 AM ----------
[Samsung Epic 4G Touch] GrimeSyndicate:
Kernel then tweaks is the order I've always done things. I believe that's the logical way to do things....
[Samsung Epic 4G Touch] roirraW "edor" ehT:
1.42F is 1.3 with Frandom. Just confirming in case there's any doubt.
[Samsung Epic 4G Touch] GrimeSyndicate:
What kind of problems are you referring to? I've only ever kept them on the external, without incident so far... though, I'd like to keep it that way
[Samsung Epic 4G Touch] roirraW "edor" ehT:
I can't speak for black canopy, but for me, at least the two or three times I happened to try to use Mobile Odin to flash something I had on external SD, it didn't flash it. I don't recall I'd there was anything other problem after it failed to flash. I haven't had one problem since I only use it on things on my internal SD instead. So for me, it's not proof of anything, because I don't care enough to bother testing with flashing from external SD, so it's just a suggested solution if someone like we did, do have a problem.

I'd like to add that flashing via recovery I haven't had a problem either way.
[Samsung Epic 4G Touch] blackcanopy:
That pretty much sums up my experience using the external SD as well.

The only other time I've had any issue of the same, on the Internal SD, is when I had the kernel file buried too deep within a folder, (within a folder, within a folder... within a folder). But again, that was a 1 time thing and haven't tried again since changing my method.
[Samsung Epic 4G Touch] btoddweber:
The reason I ask is already had tweaks running with 1.3...just don't want to go and run uninstall tweaks then reboot to flash 1.42f tar then reflash tweaks...if I don't have to. Guess I'll let ya know if I get bjorked up:D:D

Should the frandom be quicker?
[Samsung Epic 4G Touch] btoddweber:
+1 for 1.42F...running awesome with comadose v2...will report back later
[Samsung Epic 4G Touch] gradford11:
Might just be device specific, but I've gotten lockups on all but v1.3. 1.42f did feel much snappier but the lockups brought me back to 1.3 and the battery life is amazing with my current setup. :D
[Samsung Epic 4G Touch] btoddweber:
Pushed new ui and graph dropped...but still very happy with 1.42f and comadose v2:D:cool:
[Samsung Epic 4G Touch] GrimeSyndicate:
No sooner do I start talking about mobile odin errors and never having any, do I begin to both have and notice them. This is bull$^!7. I should've knocked on wood. After flashing the new kernel multiple times in Mobile-O, each and every time the outcome is the same, in about device the listed kernel is still 1.3.0, it's linux version 3.0.74+, it says SMP PREEMPT Wed Apr 24 20:57:22 PDT 2013 What am I supposed to do? Is there a flashable zip version of 1.4.2f??? Oh, yeah, and when I said I'd been on 1.4.2f for a week with no trouble, you can go ahead and nix that, as I'm not sure if I was before, but can't get there again after the rom update, or if I never was, in fact, on 1.4.2f in the first place. It's a mystery

BTW, I'm on Project X 2.6 and I'm Running Comadose 2.0....
[Samsung Epic 4G Touch] roirraW "edor" ehT:
Did you already try putting the Kernel in your internal SD and Mobile ODIN it from there? Otherwise you can ODIN it from PC and use TriangleAway after. AFAIK, there's no zip of 1.42F.
[Samsung Epic 4G Touch] remotehugger:
Also - try un and reinstalling MO and trying again -

Tapped in from my VM SGII, rockin' jdsingle76's deodexed ROM w/ agat63's 1.4.2f kernel
[Samsung Epic 4G Touch] SASQUATCH:
1.42f is kernel 1.3. So your running the correct kernel.
[Samsung Epic 4G Touch] roirraW "edor" ehT:
But his is dated April, that's not the right build I don't think.