yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] Goddly:
understood, now the tweak pack v 1.3 has Kobridges 41 tweaks with hotplug, i pulled that single script and everything is working, so the issue is deff hotplug, now these tests are strictly to find which governer is the problem? or are these potential fixes?
[Samsung Epic 4G Touch] garwynn:
Identifying first. While I saw you pulled hotplug on your side (and you'll see I did the test scenario to try and hopefully verify that as quickly as possible) - we want to make sure nothing else is causing issues. Then we'll either need to keep hotplug out or modify it to get it to play nice.
[Samsung Epic 4G Touch] garwynn:
Just an update... Mattix got through 0.3.7 and no issues so far.

So if he flashes 0.3.0 and it causes issues it effectively isolates hotplug as the cause.

Would be great news as then everyone can use 0.3.7 and we'll remove hotplug for the time being in future releases.
[Samsung Epic 4G Touch] Goddly:
yes but im thinking his scripts are not running, because i was running the 3.0 with out the one script, flashed 3.3 w/ smartassv2 then flashed 1.3 tweak pack and it will start and run for a minute then reboot... so its a no go right off the gates for me.. though when i flash the stock "leak" same as stock.. all is well.
[Samsung Epic 4G Touch] garwynn:
Looks like that's what happened. 3.2 even locked up on him which is bad news.

Well, at least we know that in a worst case I can just make 2 builds with 2 separate defconfigs - one with tweaks enabled, one without (and thus behaving as pure stock).

I'm going to hold here for a while and give you, Kobridge and others time to test and see what you find. I'm weary about going forward with any other changes until we see if the tweaks can play nice. Other additions - like voltage changes - may not easily be able to be set in the defconfig.
[Samsung Epic 4G Touch] Goddly:
I can agree, ive even tried a few others ( but knowing 3.2-3.3 didnt work no onthers would, I have no problems with just pulling Ko's 41tweaks script, it was an addition from 1.2-1.3 ..
[Samsung Epic 4G Touch] Mattix724:
Like garwynn said already, if you are running without tweaks then 0.3.7 is perfectly fine. But with the tweaks 0.3.2 with the enabled stock governors doesn't even work without locking up and rebooting.

What happened was I flashed GB27 again and forgot about flashing the original Comodose 1.3. Everything worked great, then I realized I was running without tweaks. Then I started testing with tweaks and had lockups/reboors.

My suggestion was to modify the tweaks around the kernel or just remove the offending tweak which Goddly has already done.
[Samsung Epic 4G Touch] leaderbuilder:
Testing 3.7 right now for me. Governors show but won't 'stick' on reboot.

After reboot also always get 'Adroid is upgrading'...

Install zip works, wiping caches works.

Backup failed!

Haven't checked mounts yet.

Keep going as I can
[Samsung Epic 4G Touch] boXerrumble:
I don't know about the rest of yall, but I've ran all three kernels 0.1.0, 0.2.0, and 0.3.0 without any issues.

Each time before installing each kernel, I removed the Exit Only and Crossbreeder tweaks. After installing the kernels (wiping cache and dalvik), I reinstalled the tweaks.

Phone has worked perfectly.

FWIW, I used the tar file for 0.1.0, and the zip files for 0.2.0 and 0.3.0.
[Samsung Epic 4G Touch] Goddly:
agreed , no need to mod any kernel.. though im not understanding why we shouldn't have hot plug working.. but yes I have released a variation this morning with Kos script removed, and if i know KO hell figure out something ;)
[Samsung Epic 4G Touch] Mattix724:
I don't know what the Crossbreeder tweak is but I tried flashing the Comodose tweaks after flashing the kernel using mobile odin and it locked up then rebooted.

I think it's safe to say that the kobridge tweak is what is causing the problem. It either needs to be rewritten or removed.
[Samsung Epic 4G Touch] boXerrumble:
Crossbreeder deals with entropy/lag reduction. Exit_Only says its compatible with his tweak, and I've had good results running both together. I haven't encountered any issues thus far with the Source kernel's Garwynn has posted.
[Samsung Epic 4G Touch] CyberpodS2:
I am running WOR with the modified comadose 1.3 that has the one script removed. I flashed 3.7 over 3.0 and it still keeps the pegasusq on reboots.I am still at work so have to be cautious about losing my phone. LOL Over all everything seems fine.

I am still having the issue that when I flash any of these besides 0.1.0 I lose my ringtones other than stock. The interesting thing is after some time I get them back. I have not nailed down if it's a delayed mounting thing or after reboots or what. If anyone else is running WOR can you see if you have the same thing?
[Samsung Epic 4G Touch] kobridge:
This makes sense because my 41tweak assumes that CPU governor is ondemand (which should work fine on ondemand governor).

For other governor settings, this needs to be tested out.

But strange part is, with my whole tweak pack which is including the dvfs.sh script, it should work fine because it sets the governor to ondemand.

Because of Kernel change, it seems like 41tweak runs first before system runs the dvfs.sh.

To test this, if we create the dvfs.sh file into init.d folder and if it runs fine with any other governors, then it should not be governor issue.

If this does not change anything, then we need to check the ondemand features from this kernel. As long as I know, the default kernel is ondemand and it should run fine at first time. But if the governor is changed then it could fails if the governor does not support the values changes in 41tweak.

There are lots of things to test but actually I don't have time yet...:(

If someone want to test this out, unzip attached tweak file and add the file to init.d folder. Assign the permission to 755. Reboot with new kernel 0.3 and see what happens.
[Samsung Epic 4G Touch] Goddly:
Im out as well....
[Samsung Epic 4G Touch] Mattix724:
I'll test it out in a few and see what happens... dinner first.

---------- Post added at 05:26 PM ---------- Previous post was at 04:54 PM ----------

Assuming the above script goes with the offending script, I tested and it still locked up and rebooted.
[Samsung Epic 4G Touch] colonel.shepard:
So is agats source made gb27 kernel 100% working?
[Samsung Epic 4G Touch] leaderbuilder:
Loaded file, Booted on 0.3.1 but still getting the 'upgrading adroid' thingy after successive boots.

Flashed 0.3.0 and it too booted. Though I also got that 'upgrading adroid' too.

Edit:

I guess I should at that yes it does boot and run fine. But the issues above persists, for me. And the others; like backup failing on 3.6 & 3.7, 3.12as mentioned before persist.
[Samsung Epic 4G Touch] Goddly:
Put this script in place of 41kobridge script... and its running fine KO ...

If theres anything else KO lemme know.
[Samsung Epic 4G Touch] dataman:
Thats a good news godly
[Samsung Epic 4G Touch] Goddly:
yes but im assuming it was for testing purposes .. ;) lemme know Ko if theres something else i can help with , btw ComaDose 1.3 has dvfs.sh file i added to /bin... its your v4.2A aggressive ondemand ....

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

I believe that would cause conflicts , as both scripts try to set ondemand settings,

btw these 3.2-3.12 are testing kernels with governors removed, 3.0 is a full working kermel with all governors .. 3.1 Is Stock kernel with Agats recovery... nothing else added.. I'm running 3.0... with my 1.3 modded tweak pack..... shouldnt go flashing kernels all willy nilly...
[Samsung Epic 4G Touch] kobridge:
Almost there. If CPU tweak works - I think you check the log file and everything's fine including the CPU governor & frequencies are same thru the rom toolbox - then put the 41 tweak back. Run it together with CPU tweak.

If the current governor is ondemand and If it runs fine then, the problem would be the different governor tries to run the 41tweak when the ondemand governor is not set yet.

If it fails, then the tweak values - hotplug or something from 41tweak does not work under custom ondemand governor. I or someone need to check the kernel settings for ondemand governor.
[Samsung Epic 4G Touch] boXerrumble:
As of now, I believe the only version that worked for everyone was 0.1.0, but that has the stock governors, Linux 3.0.31, and CWM. The newer versions have updated linux, and more governors, but have not worked for everyone (depends on your setup).
[Samsung Epic 4G Touch] JCred:
I too used the .rar (in mobile Odin pro) with no problem to flash 0.1.0. The other two versions generated a "partition not found in file" from mobile Odin, so, as you suggested, I downloaded the .zip and flashed in recovery. BOOM!

FWIW, I've strictly run the one-click rooted SXTP leak with no tweaks (other than freezing some things in Titanium) since its release. Maybe mobile Odin just doesn't feel good about flashing a repack over a repack?
[Samsung Epic 4G Touch] Goddly:
Checked the log, kobridge tweak .log shows on demand being set accordingly, checked rom toolbox Kernel tweaks to match up the presets , yes its ondemand ,

yes min and max are the same..though i might change the script from 1.2 to 1.0 then execute , look at log, double check rom tollbox...

Set to 1.0 , set permissions, executed, log checked out well , went to rom toolbox, set to 1.0 ;) looking good on that end KO

---------- Post added at 11:50 PM ---------- Previous post was at 11:09 PM ----------

Also had an incident has been reported ,

On 3.0 phone off, plugging in , boots phone, strange I know.. But that's something else I wanna add.. Testing 41 script momentarily , phone is dead.. (Though I don't see why..... Lol)
[Samsung Epic 4G Touch] boXerrumble:
Well, that shouldn't really happen. Mobile Odin should flash anything regardless if its a repack or not. I just have preference in flashing zip files in recovery.

The only time I used the tar file version was when I flashed 0.1.0 over the Stock GB27 kernel in Mobile Odin, and I flashed with no issues (again after temp booting into the GB27 repack posted a while back to uninstall tweaks, then flash stock GB27 kernel).
[Samsung Epic 4G Touch] Goddly:
ok pushed the file , BTW ive trimmed it down from the original version KO (saves a lot of conflicts with other script in my pack) pushed ,permed, executed after around 40 sec, lock up reboot, ill strip the hot plug commands out, even though i know thats what the problem is.. but i can try ... lol ;)
[Samsung Epic 4G Touch] colonel.shepard:
Is agats gb27 100% working now?
[Samsung Epic 4G Touch] Goddly:
If your looking for "Pure Stock" kernel with custom recovery , then 3.1 is working perfectly fine if your running a rom with hotplug tweaks, (Kobridge tweak pack, ComaDose tweak pack....

Long Story short, yes and no..

3.1 = stock kernel+Agats custom recovery great for roms with tweak packs installed.

3.0 = All the different Govs, etc, great for roms with NO tweak packs, or use with Modded tweak pack, (ComaDose v 1.3GB27_C_R.zip variant)
[Samsung Epic 4G Touch] helix4u:
Ok, I've been messing around for a bit now... If I remove the "Other sysctl tweaks - Kernel, VM, file system" section of in 41tweaks_kobridge, it seems to work for me (aka, no reboots right after loading). Hopefully that can narrow it down better for someone who already speaks tweaker language (Haaa! :silly:) better than I do... Below is the section of script I removed.

# Other sysctl tweaks - Kernel, VM, file system

echo "$( date +"%m-%d-%Y %H:%M:%S" ) Other tweaks.." | tee -a $LOG_FILE;

sysctl -w fs.file-max=524288

sysctl -w fs.inotify.max_queued_events=32000

sysctl -w fs.inotify.max_user_instances=256

sysctl -w fs.inotify.max_user_watches=10240

sysctl -w fs.file-max=524288

sysctl -w fs.inotify.max_queued_events=32000

sysctl -w fs.inotify.max_user_instances=256

sysctl -w fs.inotify.max_user_watches=10240

sysctl -w fs.lease-break-time=10

sysctl -w fs.nr_open=1048576

sysctl -w kernel.hung_task_timeout_secs=30

sysctl -w kernel.msgmax=65536

sysctl -w kernel.msgmni=65536

sysctl -w kernel.panic=30

sysctl -w kernel.panic_on_oops=1

sysctl -w kernel.random.read_wakeup_threshold=256

sysctl -w kernel.random.write_wakeup_threshold=256

sysctl -w kernel.sched_latency_ns=18000000

sysctl -w kernel.sched_min_granularity_ns=2000000

sysctl -w kernel.sched_wakeup_granularity_ns=3000000

sysctl -w kernel.sem="500 512000 64 2048";

sysctl -w kernel.shmmax=268435456

sysctl -w kernel.shmmni=4096

sysctl -w kernel.threads-max=524288

sysctl -w net.core.rmem_max=524288

sysctl -w net.core.wmem_max=524288

sysctl -w net.core.netdev_max_backlog=2500

sysctl -w net.ipv4.tcp_rmem="6144 87380 524288";

sysctl -w net.ipv4.tcp_wmem="6144 87380 524288";

sysctl -w vm.block_dump=0

sysctl -w vm.dirty_background_ratio=70

sysctl -w vm.dirty_expire_centisecs=500

sysctl -w vm.dirty_ratio=95

sysctl -w vm.dirty_writeback_centisecs=1000

sysctl -w vm.drop_caches=3

sysctl -w vm.laptop_mode=0

sysctl -w vm.min_free_kbytes=4096

sysctl -w vm.min_free_order_shift=4

sysctl -w vm.oom_kill_allocating_task=0

sysctl -w vm.overcommit_memory=1

sysctl -w vm.page-cluster=5

sysctl -w vm.panic_on_oom=0

sysctl -w vm.swappiness=30

sysctl -w vm.vfs_cache_pressure=50
[Samsung Epic 4G Touch] Goddly:
OK, been at this for hours making head way, stripped down the script, narrowed the problems (thats right more than 1) down to systctl kernel rewrite commands.. stripped the two i thought were the culprits, pushed , permed, executed. the phone ran ran without rebooting... took KO's original "41 script" stripped those two lines, pushed etc. the phone started rebooting again so, i have one problem area nailed down . working on the next...

sysctl -w kernel.msgmax=65536

sysctl -w kernel.msgmni=65536

it was these two for me.. but i still reboot after strip, which Ko script are you running... ComaDose? Or Ko's?

ComaDose I removed a few things that would conflict for me...
[Samsung Epic 4G Touch] helix4u:
KO's 4.3A
[Samsung Epic 4G Touch] Goddly:
did you try removing those 2 lines to see if it works?
[Samsung Epic 4G Touch] helix4u:
I'll do that now.

Edit: no dice
[Samsung Epic 4G Touch] Goddly:
i had already stripped all the hot plug lines sleeper lines, then i stripped those 2 and had no reboots. but i tried just removing those two lines from KO's original and i get reboots.... what your saying is, you have all the hot plug lines still in? as of now im backtracking adding lines ...

which kernel are you running? I;'m on 3.0
[Samsung Epic 4G Touch] helix4u:
Right. I just extracted the script from kob's 4.3A and removed the entire "# Other sysctl tweaks - Kernel, VM, file system" section. Everything else is untouched.

I'm using 3.1 to do the changes on the device, but switch to 3.0 to test the changes.
[Samsung Epic 4G Touch] Goddly:
are you running all the rest of his tweaks? as well? ive removed all but the one m for certainty ...

again which kernel version are you on? sorry bro, but it seems were having the exact opposite working methods... lol
[Samsung Epic 4G Touch] helix4u:
HA! :highfive: Oh God... My brain hurts.
[Samsung Epic 4G Touch] Goddly:
There's a catch 22, I'm adding back as we speak
[Samsung Epic 4G Touch] helix4u:
Your # IO/Scheduler section is different than the one I'm using because in that version it was in dvfs.sh. I wonder what else is different...
[Samsung Epic 4G Touch] Goddly:
Dunno anymore..l. Can't see straight... Ive added a few more back.. With no reboot
[Samsung Epic 4G Touch] helix4u:
Yeah, I'm giving up for the night. I've got a real QA job that I have to wake up for in the morning.
[Samsung Epic 4G Touch] Goddly:
Enjoy!
[Samsung Epic 4G Touch] stryfe2010:
Thanks for the jb recovery kernel. just wanted to let you know that on the stock/root no data and also on Jellyverse 2.0 the ver .30 kernel recovery would randomly reboot the phone even during a task such as back up. But ver .31 has been working perfect with back up, restore and install zip.
[Samsung Epic 4G Touch] jaxon01:
Sounds like you might have had a couple of bad downloads.

Sent from my SPH-D710 using Xparent Cyan Tapatalk 2
[Samsung Epic 4G Touch] Goddly:
View attachment 41tweaks_kobridge.txt
[Samsung Epic 4G Touch] Goddly:
This is a working 4.2a KO, now the 4.2 is more ICS based , but if you compare it to to the original in your downloads , you'll see what I had to remove, I believe it was those two lines I mentioned earlier.. But I've moved and pushed so much I can't tell.. Lol. But here's the file, just remove the .txt you know the drill...

Also, checked the sys/no_standhotplug, there us no location with that name , I'm running

V 3.0 with all govs.

Not sure what the differences are betweenn4.2 and 4.3.
[Samsung Epic 4G Touch] btoddweber:
So would I flash that over the top of comadose 1.3?
[Samsung Epic 4G Touch] Goddly:
testing only guys... ill release another variant soon. Just trying to help ko... your not gonna be able to do much wirh a .txt :p
[Samsung Epic 4G Touch] btoddweber:
Figured that out after i hit send..duh..:rolleyes::rolleyes:

Thanks for the work
[Samsung Epic 4G Touch] Goddly:
Then hit he thanx button. :p
[Samsung Epic 4G Touch] garwynn:
So I finally got around to updating the defconfig...

https://github.com/garwynn/D710SPR_GB27_Kernel/commit/ec59bffbe728ae3e379e3964819550bb50584fe4

And one thing I noticed is that it removed hotplug. Other governors were left in, one line was relocated - only hotplug outright yanked.

I'll make another test build shortly after I finish going through the updated defconfig.

In other news noticed that I missed a few of Agat's kernel tweaks. I'll add those in today as well if time allows.
[Samsung Epic 4G Touch] jt_hatch:
If I'm reading your post correct, I'm seeing something similar: phone reboots itself in the middle of making a nandroid.

Nandroid backup usually nearly completes if backing up to internal SD; backing up to external card I've seen it reboot while still backing up the system.

Running Jellyverse 2.0, 0.3.0 kernel, no tweaks. Saw the same behavior with 0.3.0 kernel with Jellyverse 0.5 (GB08) before flashing the 2.0 ROM. Haven't tried 0.3.1 yet; will try to find time later today.
[Samsung Epic 4G Touch] sblarsen:
I've been unable to complete a nandroid backup with the 0.3.0 builds (worked fine with 0.1.0). The backup process gets through boot image, system image but reboots during the data image backup (on one of the .asec files when I actually saw it happen). I tried wiping cache/dalvik, fixing permissions, reflashing the kernel, etc etc to no avail.

Anyone else seeing this issue?
[Samsung Epic 4G Touch] leaderbuilder:
v0.3.1 (Current Linux, default defconfig) and will work smoothly for the ROM(s) and for backups and other tasks.

[One thing though, you may have to delete the /system/etc/init.d folder. I deleted my already by the time I got to this build but just a heads up].
[Samsung Epic 4G Touch] sblarsen:
That answers my "anyone else seeing this issue" question :)
[Samsung Epic 4G Touch] garwynn:
0.3.13 uploaded for those wishing to test it out.

Since it's without HOTPLUG I'm considering it basically a 0.3.7 with new defconfig.
[Samsung Epic 4G Touch] dschachm:
Not sure if it was mentioned but I am running jellyverse with pegasusg and exits v0.3.2_r1 without issue and did the same to my wife's phone.
[Samsung Epic 4G Touch] btoddweber:
Forgive stupidity bit whats the diff between v3.1 & v0.1?

Are they both not stock with agats?
[Samsung Epic 4G Touch] jt_hatch:
Not running tweaks/have no init.d folder, so thought I was all good with 0.3.0 (I like the addn'l governors). I'll try 0.3.1 and/or 0.3.13 which I just saw is up if I get a few spare minutes between meetings this afternoon :D
[Samsung Epic 4G Touch] dschachm:
Flashed 3.13, no issues with exits tweaks.
[Samsung Epic 4G Touch] Mattix724:
Is this basically dastin's commit that I gave you the info about?
[Samsung Epic 4G Touch] cerj:
Yes, but v3.1 has updated Linux
[Samsung Epic 4G Touch] Takenover83:
I can confirm the following on 0.3.0

Recovery bugs:

Backup to internal : Rebooting during /data backup

Backup to external: Rebooting during /data backup

Tried changing the backup format to see if that would help, but just got a error backing up /system
[Samsung Epic 4G Touch] jt_hatch:
I've now confirmed this on 0.3.0, 0.3.1, and 0.3.13.
[Samsung Epic 4G Touch] garwynn:
No.

make garwynn_defconfig
[I](creates .config)
[/I]make oldconfig
[I](updates .config to 3.0.71)
[/I]

Then renamed old garwynn_defconfig and copied .config to become new garwynn_defconfig.
[Samsung Epic 4G Touch] leaderbuilder:
With .3.13 most worked, kernel changes stayed after reboots no system crashes. But back up failed
[Samsung Epic 4G Touch] Goddly:
this is not "kernel" related this is on Agats recovery Ramdisk...
[Samsung Epic 4G Touch] garwynn:
Passed on ramdisk issues to Agat. Will be Monday at earliest but promises to address them.
[Samsung Epic 4G Touch] kobridge:
Thanks for your time for testing out this. And sorry to Garwynn for painting out your thread with all debugging posts.

Can you test out the stand hotplug instead of pm hotplug?

Comment out pm lines with starting # and remove first #s from stamd hotplug lines... if it works, we will have better cpu control on this new kernel and it would work like conservative governor(benefits of ondemand and conservative)

I'm only forcusing on one thing and dont have time for others....
[Samsung Epic 4G Touch] garwynn:
No worries, that's actually what the thread is for.

I'm more than happy to address simple Q/A in the SXTP threads, PM or other means.
[Samsung Epic 4G Touch] helix4u:
Strange thing is though... hotplug isn't showing in my list of govs in 3.0

Like so?

# No stand_hotplug on stock JB ROM
#echo "30" > /sys/module/stand_hotplug/parameters/load_h0;
echo "50" > /sys/module/stand_hotplug/parameters/load_h0;
echo "20" > /sys/module/stand_hotplug/parameters/load_l1;

echo "2" > /sys/module/stand_hotplug/parameters/min_rq;
#echo "30" > /sys/module/stand_hotplug/parameters/load_rq;
echo "40" > /sys/module/stand_hotplug/parameters/load_rq;

#echo "400" > /sys/module/stand_hotplug/parameters/rate;
#echo "500" > /sys/module/stand_hotplug/parameters/rate;
echo "600" > /sys/module/stand_hotplug/parameters/rate;

# Added for Jelly Bean
# Stock value 20 - loadl 50 - loadh 400 - rate
#echo 20 > /sys/module/pm_hotplug/parameters/loadl
#echo 70 > /sys/module/pm_hotplug/parameters/loadh
#echo 400 > /sys/module/pm_hotplug/parameters/rate
[Samsung Epic 4G Touch] Goddly:
Ive got 4.2 a running and have had a few people test with 100 percent

Success. . Iv removed 5 lines .. my internet is down atm . upgraded service. Got new modem . Cant get activated right
[Samsung Epic 4G Touch] kobridge:
Exactly! You don't need to change the governor to hotplug. I want you stay on ondemand. Thanks!
[Samsung Epic 4G Touch] Goddly:
The codes I removed on 4.2 A are as follows

Sysctl -w kernel.msgmax=65536

Sysctl -w kernel.msgmni=65536

Sysctl -w kernel.sched_latency_ns=18000000

Sysctl -w kernel.sched_min_granularity_ns=2000000

Sysctl -w kernel.sched_wakeup_granularity_ns=3000000

Those 5 and all work well
[Samsung Epic 4G Touch] crawrj:
Apologize if this has been covered. Haven't had time to follow the thread. But doing a data wipe causes a never ending boot loop.
[Samsung Epic 4G Touch] cerj:
Some tweak paks are causing bootloops. So if you have any tweaks use 1.0 or 3.1
[Samsung Epic 4G Touch] Goddly:
Ramdisk. Agat will address all concerns by monday at the earliest..
[Samsung Epic 4G Touch] crawrj:
No this was pure stock. Just did a factory reset from recovery. Didn't try from the system. And tried a data wipe from one of my zips also. Any data wipe from recovery causes bootloops.
[Samsung Epic 4G Touch] cerj:
What rom? Im on JellyVerse v2.0 and using 1.0 or 3.1,and I have wiped both cache's. I havent used this kernel recovery to flash a rom, still use EL26 oe EL29 db
[Samsung Epic 4G Touch] crawrj:
Stock right from the stock tar. I can wipe cache and dalvik but doing a full factory reset puts me in a bootloop. I tested with 1.0 and 3.1. I just tried it with Agats repack and it does the same thing. I am sure it is in ramdisk, which I just read is going to be worked on.