yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] bhundven:
Yes. At the same time I gave raver the zImage... to test >.<, I also made a cwm package.

Since it was an 'rc' I didn't ever expect to release it, except maybe after the release of the final v0.1.1.
[Samsung Galaxy S (4G Model)] itzik2sh:
I did not use any updater script, I pushed the files using root explorer.

It's the original ROM files just decompiled and recompiled using APKTOOL. I changed only resources (language values).

Sent from me
[Samsung Galaxy S (4G Model)] bhundven:
I'm not really a 'rom dev', so if you can find a rom dev that will help, and it is a problem with my recovery, I would be happy to fix it. But I wouldn't know where to start.. at this point.

Although I'm trying to learn...
[Samsung Galaxy S (4G Model)] htaak:
Very exciting stuff. We are very fortunate to have you working on this Bryan. Thanks man.
[Samsung Galaxy S (4G Model)] ericmpanda:
Try with newest kernel yet ? and instead of pushing them try dropping them directly in the .zip you flash. respond in PM please.

On topic : any sense testing and sending logcats Bryan or wait for next build bro ?
[Samsung Galaxy S (4G Model)] Fluidification:
I have a suggestion that I have posted many times.

1. After you have your compiled apk, go the /apktoolbuilddirectory/build/apk/...

(e.g. /users/example/desktop/framework-res/build/apk/...)

2. Now, find your original apk, like the one directly from your rom.

3.a. If you are on Windows, download 7zip and open up the apk via 7zip. You don't need to rename or anything. Just double click on it and when the computer asks you how to open it, select 7zip and make it default for apk files.

b. If you are on Mac, download or purchase Winzip for Mac, or go to a windows computer for this step.(parallels or vmware will work too). I you are on mac, rename the file to .zip and open it up. Now leave it open.

4. add the "resources.arsc" file from the build into the opened 7zip or Winzip. It will copy your values folders.

5. If you used winzip, change the extension back to apk.

6. Push the original file which you modified back to your phone. It "WILL" work. This isn't kernel specific.
[Samsung Galaxy S (4G Model)] RaverX3X:
ya i didnt mean to include it with black lol but i forgot to swap the kernels out i told bryan about it he was ok with it so i left it as is :P..
[Samsung Galaxy S (4G Model)] bhundven:
None of this has to do with the kernel. Please pm who you are talking to.
[Samsung Galaxy S (4G Model)] bhundven:
If it is something useful, sure. But I'd wait.
[Samsung Galaxy S (4G Model)] nazcalito:
Anyone looked at modem source code? Seem like the text length limitation might be an easy fix.
[Samsung Galaxy S (4G Model)] lowsnamebrand:
Pm me theres a simple work around
[Samsung Galaxy S (4G Model)] bhundven:
Is there a code drop for the modem? I would love to see that!
[Samsung Galaxy S (4G Model)] jules2142:
Hey bhundven **** YOU MEN YOUR FREAKING AWESOME :P

THANK YOU SO MUCH !!!!!:):):):):):rolleyes::rolleyes::rolleyes::rolleyes::rolleyes::rolleyes::):):)
[Samsung Galaxy S (4G Model)] bhundven:
I'm not sure if I should be offended or how to take that.

You ended with thank you, so I will just :shrug: and say, you're welcome... I guess! :D
[Samsung Galaxy S (4G Model)] jules2142:
LOL im sorry if i offend you but im so EXCITD :D

BTW, how to get into recovery CWM?
[Samsung Galaxy S (4G Model)] bhundven:
http://xdaforums.com/wiki/Samsung_Galaxy_S_4G#Clockwork_Mod

read the wiki ;)
[Samsung Galaxy S (4G Model)] jules2142:
tnx awesome dude :P
[Samsung Galaxy S (4G Model)] Fluidification:
I am not annoying you, but I have a question. If I was to look at your screwed CM7 manifest. Can you point me in the direction of fixing it?
[Samsung Galaxy S (4G Model)] finch8423:
Question: Does disabling deep idle improve battery life, even if it wasn't working before?

Seems a little, ironic. Btw, there are mods for the Nexus S for deep idle, have you looked at their work for help and/or ideas?

Thanks for the great work.
[Samsung Galaxy S (4G Model)] Fluidification:
I think removing deep idle doesn't affect battery, but if you don't sleep your phone, then it will.
[Samsung Galaxy S (4G Model)] bhundven:
for now just wait. trust me.
[Samsung Galaxy S (4G Model)] bhundven:
to give you a more technical answer. the problem with deep idle wasnt specific to the deep idle processing, but the drivers (like bluetooth, dma, wifi, etc) did not correctly support it.

my battle with deep idle is far from over. which is why the issue is still open on github.
[Samsung Galaxy S (4G Model)] leo321:
Woot! Progress!
[Samsung Galaxy S (4G Model)] recluse2:
I have a strong feeling Mr.Hundven is cooking up something wonderful, please have patience everyone. I think the wait will be well worth it.

The few things I have used from him is ROCK solid and outstanding in every way.
[Samsung Galaxy S (4G Model)] thomas.raines:
Brian, First off, thanks for everything you have done for this community. I recently flashed your KJ6 kernelv0.1.0. After which, I deicovered I was having some problems. When I try to enable bluetooth, it fails; however, after I reboot the bluetooth enables just fine. I also have the occasional issue with wifi not turning off. I understand these are known issues after reading a few other post in this thread, so I'm not going to say much more about it. But I have found some other issues that I did not find mentioned in this thread. As you may or may not know, I have a tweaks compilation that I created, and I am continually trying to improve it as I can. Some of the other issues I believe could be driver and/or kernel related; however, I am not sure and would like to confirm. It is build.prop additions that include enabling the various parts of media.stagefright and several signal tweaks. The resulting issue is slow and very laggy performance with random reboots where I haven't gotten a logcat on this as my time is rather limited because of life, but will do so at my first chance. In addition, I have also tried to create an OC tweak, but I am at a standstill due to lack of kernel support for the driver (I actually have a driver, but it fails when I try to insmod it with an output error of "insmod: init_module '/system/lib/modules/overclock.ko' failed (File exists)"). Any help or guidance on this would be appreciated.
[Samsung Galaxy S (4G Model)] bhundven:
I don't feel that I've done that much. Krylon360, drhonk, Whitehawkx, RaverX3X, FBis251, Golmar88, and many, many others have built the foundation. They deserve a lot of credit.

Those issues are all rom issues. Not kernel issues. Read this to fix those.

Anything's possible, but only understanding through logs. ;)

Logs.
[Samsung Galaxy S (4G Model)] bhundven:
I really do not want to introduce OC at this time.

I do not want users spaming my thread because there is a problem with your OC... and bluetooth (for example). I won't fix it.

The kernel is beta, but I always try to release something that 'works' (depending on your meaning of 'works'... kinda... somewhat... mostly untested). The ammount of time I have to just do the work I have planned is very limited.

Again, features like voodoo sound, bln, oc/uv, possibly other very awesome improvements are coming, it is just going to take time. I feel that as I remove unneeded code and get closer to aosp upstream - I will make mistakes, and you might see what 'unstable' really looks like. I know I've seen it. :D
[Samsung Galaxy S (4G Model)] RaverX3X:
not to be a **** but i would say kanged from desexton.. but anyways but to answer your question enableing the other parts of stagefright will in fact break things like media hub for people that use it and a few video codecs will no play back with them enabled. namly most things that are encoded with mp4. Enableing it gives no benfit other then quadscore epeen..

as far as the singal tweeeks go anything for enableng 3g faster will not work and or will cause yuor device to loose signal as there is no 3g band in the sgs4g at all it lacks the entire band period. as far as hsdpa tweaks those can be further tuned.
[Samsung Galaxy S (4G Model)] thomas.raines:
I am not intending to get your thread spammed bhundven, just looking for possible causes of the failures, and I do apologize. As far as the bluetooth, I understood from a few other posts in this thread that it was a deep sleep issue with this kernel. I as well completely understand that it is BETA. I also understand and appreciate the words "limited time." Again, thank you, and I hope to see more "awesome" stuff from you in the future.

Raver thanks for your input. Those were the answers I was looking for. As you know, I am still learning, and your help is always appreciated.
[Samsung Galaxy S (4G Model)] neotoky:
So far so good. Is it just me but my phone boots really fast now :)
[Samsung Galaxy S (4G Model)] geekilized:
Every time I reboot the phone, it says my su binary is outdated. Anybody had this happen? Is there a way to fix it? BTW I flashed this on top of Raver's deodexed KJ6 ROM.

Also every time I try to update the binary, I see the following line:

Remounting /system as ro... fail!
[Samsung Galaxy S (4G Model)] bhundven:
Yup I know about this problem. It's a beta ;)

I got this bad boy up fast, so you could have something to flash.

Don't worry, I'm not gonna leave ya hanging... there will be updates. :)
[Samsung Galaxy S (4G Model)] bhundven:
update the binary. Could you please be more specific. Have no clue what the binary is.
[Samsung Galaxy S (4G Model)] Bassmanjames:
Try updating super user from the market or go open the app to check for an update. Doubt it's an issue with the kernel.

Edit: looks like you may have tried this already?
[Samsung Galaxy S (4G Model)] bhundven:
It's a problem with the kernel. :)

I'll have it fixed in the next version.
[Samsung Galaxy S (4G Model)] geekilized:
Ok cool. I thought it was only me and I was doing something wrong. Thanks for the quick reply. And I meant updating the su binary.
[Samsung Galaxy S (4G Model)] bhundven:
Ok, so when do you see:

?
[Samsung Galaxy S (4G Model)] neotoky:
For future reference where do I type the code to flash the zimage
[Samsung Galaxy S (4G Model)] bhundven:
The op!?

10char
[Samsung Galaxy S (4G Model)] geekilized:
When I try to update the su binary from Superuser app.
[Samsung Galaxy S (4G Model)] emod0705:
Had su issue with other kernels..don't think it's this..think su muffed up their update.
[Samsung Galaxy S (4G Model)] bhundven:
I just updated superuser, and ran the su update. Works for me. Didn't see your problem.

Maybe something with your rom install is wacked.
[Samsung Galaxy S (4G Model)] Somairotevoli:
Its an issue with the kernel.before it was because su was in the kernel.you could update but it would get rewritten after reboot.
[Samsung Galaxy S (4G Model)] Mykalus:
i was getting the SU issue before i flashed this kernel... i got it once after i flashed the kernel, updated the binary and haven't seen it again... but it used to come and go, so...
[Samsung Galaxy S (4G Model)] chadster214:
Superuser

Can you please update the Superuser to the latest version?
[Samsung Galaxy S (4G Model)] Somairotevoli:
Read the thread.its being worked on.beta guys
[Samsung Galaxy S (4G Model)] bhundven:
It's hard to update when I'm responding ;)

I was just doing that when you posted this. Patients :)

Op updated.
[Samsung Galaxy S (4G Model)] QUIETLYloud:
So basically, if you have not had the su issues no need to flash the update?
[Samsung Galaxy S (4G Model)] bhundven:
Nah, the newest update just updates Superuser.apk and /system/xbin/su, also removed 'disabled' for the bootanimation service (I think that's what krylon asked me to do...)
[Samsung Galaxy S (4G Model)] AxleFolie:
How do I flash this? choose zip from sdcard or apply /sdcard/update.zip?

"sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip" :o
[Samsung Galaxy S (4G Model)] Lawful123:
A little research will answer your question. I would start by reading the OP. But if you are still stuck then I would choose zip from sd card. Then navigate to the file you downloaded. This question could have really been answered with you doing some homework. This question did not need to be asked.
[Samsung Galaxy S (4G Model)] HolyGhostBoy1:
Oh man!!!!! i appreciate u for working on cm7 that is awesome im gonna scream ahhhhhh!!!! falls out lol
[Samsung Galaxy S (4G Model)] nazcalito:
If you're talking about using some other modem, I tried that but it seemed to make things more unstable and the KJ6 modem has stronger wi fi.

---------- Post added at 03:59 PM ---------- Previous post was at 03:15 PM ----------

Sorry, my bad. I thought the source code drop in December included the code for drivers and modems as well since the file wasn't labeled "kernel" like the Froyo kernel update. I was looking through the driver section and couldn't figure out what the modem was but now that I look at it, the compiled modem is about twice as big as the kernel. Come to think of it, I haven't seen anything on xda about modem modding.
[Samsung Galaxy S (4G Model)] bhundven:
Basically, the source drop contains the kernel source (somewhat crippled) and a zip file that gets unzipped over aosp gingerbread. Im sure you have to use a specific version and merge (git merge --ours) newer versions on top to update. And I bet that build is partially crippled as well.
[Samsung Galaxy S (4G Model)] cannondale0815:
That's interesting. So doesn't Samsung violate the open source license by crippling their source code?
[Samsung Galaxy S (4G Model)] bhundven:
There's not really any violation. The license is "AS-IS".

If you don't know how the source-code is supposed to work, leave it to those who do.

The only violations I can think of are the software parts that are based open-source software that are not released like the SBL (which is based on u-boot, which is GPLv2... see: http://git.denx.de/cgi-bin/gitweb.cgi?p=u-boot.git;a=blob;f=COPYING;hb=HEAD). The source code for the SBL IS in violation, and should have been released within 60 days prior to release.

Things that are not in violation are proprietary firmware, like the broadcom firmware for their chips, and other proprietary licenced firmware (like for the camera).
[Samsung Galaxy S (4G Model)] Fluidification:
I agree. Also, shouldn't we also be given a modem source?
[Samsung Galaxy S (4G Model)] bhundven:
Not technically. But we wouldn't know. I'm not sure what is in the modem.bin, or how that is built.

My guess is that is just like the broadcom or camera firmware. So it is probably rightfully proprietary.

The modem.bin is only repsonsible for controlling initialization of the 4g/wifi, the drivers in the kernel are responsible for how the 4g/wifi work.
[Samsung Galaxy S (4G Model)] stephen_w:
Hi,

I've been experiencing random reboots since I upgraded from beta2d to the beta 3.1 kernel. The reboots seem to occur when my battery is low - 20% or less - but I'm working to verify that as fact.

Attached is the logcat from my phone. Let me know if there's anything else I can do to test/help troubleshoot/etc.

Thanks!
[Samsung Galaxy S (4G Model)] bhundven:
Thanks stephen!

I will look at this later, I have to go do some stuff.

I'll respond later tonight.
[Samsung Galaxy S (4G Model)] stephen_w:
No rush, man. Just wanted to make you aware in case it's the kernel.
[Samsung Galaxy S (4G Model)] bhundven:
I reviewed the log and don't see anything interesting. :(

I keep my phone well charged, so I guess I've never ran into this.

So, if I were to try to reproduce the issue, I just let it drain to 20%? Are there any other steps (Run a particular app, or what have you)? Also, what rom are you using? Have you applied anything besides the rom install.zip?

I will try to not charge my phone today, If I can reproduce this issue, I'll probably see what is going on with the usb uart.
[Samsung Galaxy S (4G Model)] stephen_w:
I was just getting ready to write you back & let you know it rebooted itself while at a 95% charge so the battery status is not the issue.

The reboots do not happen when I'm using the phone; it always (so far) seems to happen when it's literally just sitting there.

My phone is running the 2.3.6 official release, your 3.1 kernel, and I've debloated it with FB's app. Past that, no tweaks.

I wish I were able to reproduce it but it literally happens when it's just sitting there. If I have any other thoughts I'll let you know.

Thanks for taking the time to look into it.
[Samsung Galaxy S (4G Model)] bhundven:
Hmm. I basically run my SMS-KJ6 one-click (stock rom, custom kernel), then apply my beta3.1. I don't debloat.

Maybe there is a missing dependency from the debloat you did. Maybe try the sms-kj6+beta3.1, then debloat one app at a time until you reproduce the issue.
[Samsung Galaxy S (4G Model)] AntonX:
My phone did the same with v0.1.1-rc1. The reboots would happen once or twice a day when the phone was just sitting there with the screen off.

It also looks like battery drain is a lot higher with 0.1.1-rc1. History in BetterBatteryStats shows that the phone is awake a lot more than it should be.

I went back to v0.0.2d and both issues disappeared.
[Samsung Galaxy S (4G Model)] bhundven:
Interesting. I will have a tool soon to turn on some more debug info in the bootloader, even if you don't have usb uart. The extra debug info turns on some more battery stat information.

Which rom are you running? Which modifications have you applied or debloated?
[Samsung Galaxy S (4G Model)] AntonX:
I'm running krylon's NOCIQ version. I debloated with TB, but nothing special, just removed things I always remove on this phone. The same system seems to run fine with v0.0.2d.

I looked at the wakelocks in BetterBatteryStats trying to figure out what process is eating the battery, but found nothing obvious. So I assumed it's inside the kernel.
[Samsung Galaxy S (4G Model)] stephen_w:
Not a bad idea at all. I think I'll revert to beta 2d first, though, as it's a quicker option. If the problem reproduces itself at that point, then I'll start fresh.

Good point by Anton; it seems to happen when the phone is not in use and the screen is off.
[Samsung Galaxy S (4G Model)] bhundven:
Ok, that is very helpful info! Thanks! I'll keep my eyes out.

EDIT: oh, um, do you guys have any services running? Tegrek, voodoo sound, etc...?
[Samsung Galaxy S (4G Model)] stephen_w:
I'm not over clocking, under volting, or anything. I do have ext4 going on via voodoo lagfix, but nothing else. I can provide you a list of apps I've downloaded and installed if it helps.

If there's any troubleshooting I can do from this end just let me know.

Thanks again!
[Samsung Galaxy S (4G Model)] finch8423:
I know it's a little late to chime in, but I actually had reboots as well, except it was on the .2d version of the kernel.

Rather it was my phone would shut off, and when I went to wake it, I found it was actually booting up. Battery was full, etc.

I forgot about it since I flashed the .1.0 version. However, I have also wiped the phone completely clean as well (thanks FB), whereas when I installed Valhalla Final the first time (referring to the reboots above) I was coming from 1.3.2 Valhalla. I just assumed it was a problem with Valhalla final.
[Samsung Galaxy S (4G Model)] bhundven:
Maybe ya just need to fully wipe your phone to get rid of the random reboots.
[Samsung Galaxy S (4G Model)] Vicious89:
I get the most problems when i restore using TB after flashing a Rom. Try starting fresh with the one click heimdall, brians kernel and re downloading all your apps. And when your phone reboots is it sitting there doing nothing? or is it during high RAM usage.
[Samsung Galaxy S (4G Model)] jules2142:
I got reboots too and im running stock 2.3.6
[Samsung Galaxy S (4G Model)] hampsterblade:
Wow, jumped to this page, and glad to see I'm not the only one suffering from the random reboots. I am using Valhalla final with the latest kernel too, and have installed no strange apps. I'm working on getting a logcat, but for some reason my phone doesn't want to crash while it's plugged into usb. If it crashes I'll put up the logcat, if not I'll put it up anyway as it might help you find something. Like the others, I'll pick up my phone, and go to unlock it and instead it reboots. Also before the reboots, it tends to get really warm, unnaturally warm.
[Samsung Galaxy S (4G Model)] Fluidification:
I happen to have my phone on in my pocket all day(in school). And If I get some free time, I may take it out. Generally it is unpredictable. Sometimes I take it out, it is nice and cool, Battery little or no drop, then all of a suden, I check my phone 30 minutes later, it starts to heat up and then it's at 95 percent battery(not logical for hitting the power button one), then Maybe after a little, it gets hot in my pocket and it's at 85 percent battery. Then it repeats the cycle 2-3 times per 7-8 hours.Yes, i have wiped and whatnot. Right now, I am considering going back to stock kernel until issue gets solved, it's not worth losing the battery. Also, this generally happens after periods of inactivity. Maybe a DMA issue. I'll send a logcat if possible.
[Samsung Galaxy S (4G Model)] Shermer321:
I have the reboots as well. Playing a game and it locks up. Or anything intensive.
[Samsung Galaxy S (4G Model)] Fluidification:
OMG, while playing monopoly which I got for free from amazon app store, I got 3-4 reboots once. At the time, I was using 2d. Therefore, if it is kernel specific, then it isn't version specific, it is just one of those big first bugs.
[Samsung Galaxy S (4G Model)] bhundven:
Try a factory reset. Clear cache. Clear dalvik. Install rom of choice. Install kernel. Test again.
[Samsung Galaxy S (4G Model)] recluse2:
I had that game too, buggy. I've been running this for a few weeks, not a single reboot. stock 2.3.6 rom adrenaline shot v.12
[Samsung Galaxy S (4G Model)] hampsterblade:
Funny thing is I can't get it to do it with a log running. Plugged in to my computer and ran ADB logcat, after about an hour of it rebooting every 10 minutes, and nothing. no reboots. So I gave up and unplugged it, and it started rebooting again. Installed terminal emulator, started the logcat. Once again no reboots. Stopping TE to see if it reboots again. I don't know what it means if it does, but it could have something to do with log access maybe?

Edit: it did reboot, but the session resumed, and I must not have felt the vibrate. Here is the logcat. Error occured at line 10947. Sorry for the ridiculously long log. Wanted to leave everything running to better track it down.

Logcat at http://mhamptontech.com/logcat.txt
[Samsung Galaxy S (4G Model)] recluse2:
Almost sounds to me like you have a hardware problem. When it reboots, what are you doing? When you have logcat running you have it on the desk I assume? Try plugging it in and running logcat and do whatever you usually do when it starts rebooting
[Samsung Galaxy S (4G Model)] hampsterblade:
The strange thing is it doesn't have problems during heavy use or games. Only when it's sitting idle. perhaps it could be an issue with the deepidle settings or the lowest CPU clock? Also I should mention on Raver's valhala black I had no problems, after I flashed to Valhala final due to small issues in black, the rebooting issue started. I updated the kernel to the newest one here and the problem persisted. And yes I did factory reset when I flashed. When I updated the kernel I did wipe cache, delvik cache, and fix permissions.

Also, like the others with this problem I did remove bloat with TB, but nothing I haven't removed from every other rom, in fact I'd say I removed less this time. Also it could be running the logs prevents it from reaching the lowest CPU settings, thus preventing the reboots? Purely speculation. To test I'll install tegrek and remove the lowest clock and see what happens.

Update: so 20 minutes of testing so far with clock settings at 200 to 1GHz on demand and its stable, running cooler and not rebooting on idle. (Before it rebooted whenever it was idle for 5-10 minutes.) If the other people with the problem could try this we could confirm the issue and at least it could work as a temporary fix.

Ignore all this. It crashed again... but this time I managed to catch it right after starting a log cat yay mhamptontech.com/logcat2.txt