yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy SL i9003] crazbanditz:
So now my question is do u tink I shud update to DXKP9 or XXKPQ?? And if I shud which firmware should I update to?
[Samsung Galaxy SL i9003] davew:
For me I wouldn't do it unless I can get a backup of my current ROM that I know will work in the event of problems with the flash.

If that issue doesn't bother you, and you're not bothered about voiding your warranty, then just flash whatever you like the look of best - but follow the instructions to the letter. As I understand it, you can't flash from Froyo straight to the latest GB version as the older ROMs contain three files and the newer ones only one.

If you were going with European ROMs (XX) you'd have to flash KPE twice first before flashing KPQ. So I'm told. I've not tried it, at your own risk etc.
[Samsung Galaxy SL i9003] hjs89:
I haven't tested the Samsung warranty. But didn't have any problem with Motorola and Sony-Ericsson when my Moto C385 and my SE K610 stoped working. The both services fixed me the phones without problems.

So, if I where you I'll flash the phone with XXKPQ (is what I done hehe)
[Samsung Galaxy SL i9003] cike:
update to KPQ if you are alright with dim recording of video... IMO its not really that bothersome
[Samsung Galaxy SL i9003] mzone1510:
KPQ has the highest amount of developer support, but now it seems that most 2.3.6 firmwares work well with stuff designed for kpq, so take a pick! I for one do not find any difference between different regions 2.3.6 roms like xxkpq,ddkp2 etc is there actually any difference or is it just region specific versions?
[Samsung Galaxy SL i9003] crazbanditz:
Oh kay... Thanks
[Samsung Galaxy SL i9003] jimmychoy1995:
More people are using KPQ and more mods are made for it, so KPQ is a good choice
[Xoom General] thomast5:
Hey,

Can someone provide me with the telephony files for Optus?

/data/data/com.android.providers.settings/databases/settings.db

/data/data/com.android.providers.settings/databases/settings.db-wal

/data/data/com.android.providers.settings/databases/settings.db-shm

/data/data/com.android.providers.telephony/databases/telephony.db

/data/data/com.android.providers.telephony/databases/telephony.db-journal

I flashed to ICS and forgot to pull these from my rom. I took a nandroid backup but for some reason it's corrupt, don't know why but now I can't restore my backup

Thanks!
[Xoom General] thomast5:
No need to worry, I managed to locate the files on my hard drive!
[Samsung Galaxy S (4G Model)] adobrakic:
Lately, I've noticed my SGS4G randomly reboots itself. I'm not exactly sure why, I haven't changed anything about my phone since the latest Valhalla version came out, and it never rebooted itself when I first flashed the ROM.

I have CatLog (logcat reader) and aLogcat, but I'm not exactly sure how to use them to be able to tell what happens to my phone just before it reboots itself. There are so many lines that I don't know which one to look at. Can anyone please provide some assistance? My biggest worry is my phone rebooting or shutting itself off at night, and my alarm not loading properly, causing me to miss class in the morning.
[Samsung Galaxy S (4G Model)] stephen_w:
What kernel is that running? I think (I might be wrong) it's bhundven's subtly modified stock. The versions past beta 2d (for me) have that issue. If that's the kernel it runs, go check the dev section for bhundven's kernel.
[Samsung Galaxy S (4G Model)] adobrakic:
Yup, I have his latest kernel, v0.1.1-rc1. I'll try to downgrade to beta 2c and see if the reboots stop. Thanks for the suggestion.
[Samsung Galaxy S (4G Model)] stephen_w:
I reverted back to beta 2d and it's working well thus far. Good luck :)
[Samsung Galaxy S (4G Model)] tehgyb:
I've actually seen this a lot on stock builds both out-of-the-box froyo and official gb. Have customers bringing these back constantly for this crap!
[Samsung Galaxy S (4G Model)] sunsurfer42:
This happens to my girlfriends stock gb. Can't figure out why. I'll try taking it back to t-mobile and see if a new one helps.
[Samsung Galaxy S (4G Model)] tehgyb:
That's normally what ends up happening when they bring it in :/ I've tried almost everything short of taking their phone and flashing stuff on it (because obviously that's not something a retailer can do lol)
[Samsung Galaxy S (4G Model)] adobrakic:
Seems like the problem, for me at least, was Bryans latest kernel I was using. Downgrading to beta 2d stopped the reboots so far, I've been up since 8am and now it's 3pm. I'll post back tonight for further results.

Sent from my SGS 4G.
[Samsung Galaxy S (4G Model)] sunsurfer42:
And she won't let me.
[Samsung Galaxy S (4G Model)] adobrakic:
Alright guys, it seems that the problem was for sure Bryan's latest kernel. I haven't noticed my phone reboot once today (unless it ninja'd the reboot). Thank you, stephen.
[Samsung Galaxy S (4G Model)] stephen_w:
No worries. Glad the problem is solved. I'm back on his latest kernel for testing. I've only been on it for a few hours, so I'm going to give it a day or two to see how it goes.
[Samsung Galaxy S (4G Model)] adobrakic:
The thing that gets me is that the kernel worked perfectly fine from the time I flashed it up until a couple of days ago. I'll reflash the latest version in a few days to see if I can see what's triggering the reboot.
[Samsung Galaxy S (4G Model)] bhundven:
raver nor myself have been able to reproduce this issue. i normally run pandora and android irc all day. not to mention i brick my unbrickable moded phone a lot (lately); when i do i flash sms kj6 one-click, flash bootloaders, flash v0.1.1-rc1+, wipe to factory, wipe cache, wipe dalvik cache, reboot, let the phone sit for a half hour. This allows time for the main OS's cache to build. I usually charge to 100% before flashing and plug it back in while it sits for the half hour.

After that I manually re-configure my phone settings and TB restore my apps (not my data, just the apps).

I dont trust system settings/data being restored across different roms.
[Samsung Galaxy S (4G Model)] itzik2sh:
Hi Bryan

I enjoy your latest kernel 3.1 beta for the past 2 days (on HebrewValhalla ROM) and it's simply awesome.

I only had problems on 2d. 2c has been great as well.

To me, it seems that all reboots ppl were getting were related to Black Valhalla tweaking more than to your kernel.

Anyway, f#k it, if someone is not content let him flash other old kernels, i think you're doing a sacred work here.

You deserve a bier house.

Sent from me
[Samsung Galaxy S (4G Model)] stephen_w:
My reboots were not attributed to Valhalla Black as I never loaded it. I reverted to beta 2d and the phone was stable. I'm back on his latest beta after a factory reset to see if it helps. Thus far, I am OK but I want to give it a few days to make sure.

I agree that Bryan's work is great. Unfortunately I think Bryan is leaving or is gone already. His kernel thread in the Dev section is closed & his signature indicates he's leaving. I wish him the best.
[Samsung Galaxy S (4G Model)] stephen_w:
Sigh...it just randomly rebooted. So it seems that a factory reset doesn't help the issue.

I will be reverting to beta 2d again shortly.
[Samsung Galaxy S (4G Model)] adobrakic:
Lol, wtf @ the signature. Seems rather childish. Anyway, I have exams for the next few days, so I'm gonna wait until those are done to wipe everything and try the latest kernel over again.

The problem just may be our phones. I'm sure there are hiccups in the manufacturing processing while the hardware is being compiled, so I doubt all of our phones are exactly the same. We may be that "lucky" few, Stephen. :P
[Samsung Galaxy S (4G Model)] Somairotevoli:
Give me logs, don't give me logs. Can't reproduce, you're doing it wrong. I'm leaving
[Samsung Galaxy S (4G Model)] itzik2sh:
Not that i don't admire Raver's work, but, has anyone got reboots on a non-Raver ROM ? I think he's power tweaking the ROMs, for sure he's done it in Octane.
[Samsung Galaxy S (4G Model)] stephen_w:
Yes, I have. I got a new phone and did the 2.3.6 update via Kies Mini then put Bryan's kernel on top of it. When I go back to beta 2d, it doesn't happen. I'm not sure what the deal is.
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
Its not the rom causing reboots its the kernel,

I used to have that problem, then i flashed another and WHaLaAa! It got fixed :-P

@ the OP their talking about he idle or something that causes the reboots,

Or the clock speed of the cpu

I'll try to get an xplanation for this:-P
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
Dude i think its the latest bhudhven kernel that is having problems.. Am I right?
[Samsung Galaxy S (4G Model)] stephen_w:
Yes; it was mentioned in this thread previously as well. It was also in Bryan's kernel thread but that thread has since been closed.

I had the problem with both versions past beta 2d.
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
Actually mine very stable :-P

Its the best rom and kernel i used yet
[Samsung Galaxy S (4G Model)] adobrakic:
My phone isn't overclocked, so it can't be that. The ROM I use doesn't reboot, as Stephen has mentioned, on the beta 2d version of the kernel and down. Something is wrong with the way the phone interacts with the versions of the kernel past 2d. Hopefully we can get it solved.
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
I know your phone isn't overclock but the kernel maube has a script thay lowers the CPU clock speed

Beta2 and down don't have this bug
[Samsung Galaxy S (4G Model)] stephen_w:
The kernel shouldn't be executing any scripts at all though it might have something built into it that governs the CPU speed. Bryan was working with some DMA and deep idle issues but I haven't looked through the code, change log details, or run a diff to see what exactly he was doing.
[Samsung Galaxy S (4G Model)] finch8423:
I'm not doing this just to defend Bryan, nor is this directed at the individuals that have said what I am about to say:

These reboots are anecdotes, meaning that no one has provided any sort of logs that help us actually see what is going on.

Here's an example of where your theory starts to fall apart- I had the reboots on 2d- I know this because I was running Valhalla final.

The problem is that without specific evidence, there are so many things that can, and will go wrong, that you cannot decisively say what is causing the reboots. It could, in theory be the roms. It could, in theory be the tweaks that no doubt all of you have applied. It could also be the fact that some roms don't require resets.

Strangely enough, my reboots went away after I did a clean flash, wiping everything, and flashing .1.0. Also, keep in mind, it is a beta.

Edit:

It's because of this crap that he locked his thread. I mean, how many times did he have to post, Logs, before people send, Logs. Now it's done.
[Samsung Galaxy S (4G Model)] stephen_w:
The last part there is key - it's beta. I have provided a log to Bryan, however, it didn't provide him any insight. So I followed his request to re-flash the latest beta & do a factory reset. I did this, it didn't help.

With it being beta, though, is why things like this should be discussed and hopefully addressed. Like you said, though, the logs didn't help so that makes it more difficult. This being discussed now does help us determine if there are any common denominators other than "we're on this kernel".

I hope no one took what I said as attacking Bryan in any way as that's not my goal. I've also tried to not address any of the comments that seem to do so. My goal is merely to try and help the developer (Bryan) determine if it's his product (kernel) that may be buggy and, if not, try to determine in what direction to look next.
[Samsung Galaxy S (4G Model)] adobrakic:
All of what Stephen said above ^, and

Uhhhhhhh..... link. Last four posts. I offered.
[Samsung Galaxy S (4G Model)] AntonX:
Do you know how to view logs of a kernel panic after the fact that the phone had crashed and rebooted? If you do, please advise.
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
Your all right guys

But the real deal is Bryan is leaving XDA :-\
[Samsung Galaxy S (4G Model)] stephen_w:
Are you just referring to a dmesg dump or is another log generated somewhere?
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
did u use logging app?
[Samsung Galaxy S (4G Model)] Somairotevoli:
Logs were offered. He said he didn't want them. Told the poster to read the thread and he wasn't going to help. Since he couldn't reproduce the issue, blamed it on not doing a full wipe. The thread was civil, and it is definitely an issue that needed to be addressed. When you share something, be prepared to help. If not, keep it to yourself or a select base of testers. We all appreciate what he has done, but he has moved on due to it being just too much.
[Samsung Galaxy S (4G Model)] AntonX:
Both dmesg and logcat will be helpful for troubleshooting. But we need to keep the logs after the phone silently crashed and already rebooted. I never tried this before, but trying it now. I started two scripts that keep running in the background, one with "cat /proc/kmsg > /sdcard/logs/dmesg.log" command, and the other with "logcat > /sdcard/logs/logcat.log". I'll see what will they collect if the phone reboots again.

Is there any easier way to see what's happened right before the crash and reboot?
[Samsung Galaxy S (4G Model)] stephen_w:
I provided a logcat to Bryan a few days ago. He couldn't find anything in it. I'm willing to put the latest beta on there and try and snag a dmesg log. I can knock that out later tonight.
[Samsung Galaxy S (4G Model)] AntonX:
How did you take your logcat? I think if you just take it after the phone has booted back up, then it's a fresh log, there will be nothing in it about last session events.

Does anybody know if "adb bugreport" will have any info on the last kernel panic and system crash? Or all logs are overwritten upon reboot?
[Samsung Galaxy S (4G Model)] stephen_w:
I used the command "adb logcat -d > logcat.txt" & it was after the reboot, but I'm not 100% it clears after a reboot. I'll double-check that, though.
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
Maybe beta2 will be the final one :-P

When i was running the latest one, my phone only reboots when it's just seating there idle.

But when i play heavy graphic games it doesn't reboot

My best bet is the cpu governor of the kernel or something related to a cpu speed. am i right?
[Samsung Galaxy S (4G Model)] adobrakic:
^ Hmm, you know, there might be something to what you just said, MostWanted. Come to think of it, I never noticed the phone reboot while I was using it either, it was only doing it when I had the phone just sitting there.

I'm not knowledgeable at all on how Android actually operates internally, so does anyone know if the two (the kernel and the governor) can cause interference?
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
Im better of running the beta2. And i don't have any problems yet. :-)

My rom and kernel feels like stock, but way way way fast:-P

Rom:Vahalla Black

Kernel : Bhudhven beta2
[Samsung Galaxy S (4G Model)] Vlad_z:
He is just cannot debug it... luck of time or knowledge or just a snobby ...

I asked him for a favor once if he would set module compilation flag and compile cifs.ko - just 5 second deal if one already have toolchain up and running... instead he BSed me with "let me Google it for you ".

In contrast - when I approached Pershoot with fix for Voodoo sound control, Pershoot compiled test kernel with my proposed changes as we were chatting and in 5 min. I was testing this kernel on my tab.
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
Come on give the guy a break'

He has his own life too you know?..

Maybe he can fix it when he has time... Hopefully :-P
[Samsung Galaxy S (4G Model)] RaverX3X:
the issue stimmed from the system in r/o and not being able to dump apps in and out of memory during wake lock so it trys to write it all to memory and reboots its been later corrected by settting system /rw and reboot cwm fix perms ;P
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
English plss... :-P

So what's the bottomline ? :-D
[Samsung Galaxy S (4G Model)] bhundven:
in english...

Fix your rom by doing this.

After that, reboot your phone to cwm and run: Advanced -> Fix permissions

I've said this over and over, but none of you read.

BTW, I told people to stop sending me logs of the reboot issue, not because I'm a SNOB or whatever, but because the logs were useless.

Vlad, your request got lost. Too much going on, and it fell through the cracks. Sorry I was a **** and didn't just do it for you right away... like you wanted. I should just do everything for everyone RIGHT NOW.
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
One more question.

Does this fix the sudden reboot issue right?
[Samsung Galaxy S (4G Model)] RaverX3X:
yep

10 chr
[Samsung Galaxy S (4G Model)] finch8423:
Ironically, my little rant wasn't directed at you at all Stephen. I mean, he made a damn thread saying he was considering leaving, and then low and behold, when nothing changed, he locked down his threads.

I wasn't specifically talking about this issue, but every issue in general. I've seen about 45,000 new threads every 3 seconds asking the same question (I'm adding a few for dramatic effect). I think it's pretty easy to see why developers would get irritated considering it pisses everyone else off.
[Samsung Galaxy S (4G Model)] adobrakic:
It's not that dude, it's that you wouldn't even throw us a bone. I realize that there are plenty of annoying members who want everything spoon-fed to them, but there are just as many members who are willing to do things manually. I don't understand why what just happened above couldn't have been done before. Now those of us who are having our phone reboot itself can test what you posted, and if it works you can post it to the main page of your kernel, which would stop for people from asking the same question in the future. It ends up saving more time than you would save telling people to figure it out by themselves over and over.

Thank you and Raver for your help. It's much appreciated.
[Samsung Galaxy S (4G Model)] champ1919:
Take someones work, change stuff and complain that it doesn't work. Well heck, I think I'm gonna ask my crack dealer for a refund cause I didn't get as high as yesterday.

Hey B, thanks for logging in to XDA. You've done alot for the advancement of a year old phone. Thank you on behalf of those that enjoy your work.
[Samsung Galaxy S (4G Model)] JuLes' MostWanted:
My account here is just two days old :-P
[Samsung Galaxy S (4G Model)] adobrakic:
WTF, who said they changed ANYTHING about his work? Have you even read this thread, or did you just come to the last page so you can do your boot-licking? We all appreciate and enjoy his work, it's just that a dozen of us were having problems and were trying to find a remedy. God forbid people have issues and want to try to fix it.
[Samsung Galaxy S (4G Model)] champ1919:
How many threads are on this forum go "I flashed this and then flashed that and now I'm not happy"?

Nobody owes anyone anything but a thanks for your work/efforts goes a long way.
[Samsung Galaxy S (4G Model)] adobrakic:
This is not similar to any of those threads.
[Samsung Galaxy S (4G Model)] stephen_w:
Agreed, this is not a similar thread to those, but it's slowly turning into something just as bad. I try not to even get involved in these things, however, this is one of the problems with this forum. Everyone wants to complain about everyone else.

The sense of camaraderie is missing

. I do my best to try and help people that need it, even if I'm annoyed with the fact that the question has been asked a million times. The fact is, none of us - new, junior members, members, senior members, recognized developers, or mods - can change the behavior of others. We can point out that people need to search, read through threads, etc., and I believe it could be done in a nicer fashion. Being a little polite, like you mentioned with giving thanks (and I agree with that totally) goes a long way.

I can't blame the devs especially for getting upset, though, because what they enjoy doing turns into evil rants and them getting the crap bugged out of them for senseless reasons. Their hobby & fun turns into something bad because people take them for granted. Not all people, of course, but a few bad apples can sure spoil the whole bunch.

Sometimes we just need to sit back, step away from the keyboard, and take a breath. Just my 2¢.

I digressed, which is what also keeps happening to these threads. My apologies to all for that.

Now I'm going to go back and read what was previously said with regard to troubleshooting the issue.

Sorry for the rant.
[Samsung Galaxy S (4G Model)] adobrakic:
I agree. I tried not to turn it into a stupid, irrelevant argument, but it has been a long day and I let myself get carried away.

Anyway, I have flashed Raver's latest ROM, which has the latest version of the kernel. This time, I wiped everything and started fresh. So far, so good. No reboots. I'll let it progress into tomorrow to see if any reboots occur, and I'll post back here with results.
[Samsung Galaxy S (4G Model)] FBis251:
Wrong thread.
[Samsung Galaxy S (4G Model)] htaak:
Thank you.
[Samsung Galaxy S (4G Model)] itzik2sh:
Hi guys

I'm glad a solution has been found.

Actually I lost you, so if I just "mount system" like any CWM executable does and then fix permissions through CWM, it will fix it ?

What about the next time that I'll run such a CWM executable and it will unmount system at the end ?

i tend to not work with adb shell.

Thanks.

Sent from me
[Samsung Galaxy S (4G Model)] adobrakic:
Update: Not only have I not experienced any unexpected reboots, but this is literally the smoothest-working ROM I've used thus far. Amazing work by Raver.
[Samsung Galaxy S (4G Model)] Core618:
I only just noticed the reboots a couple of days ago, so wiped and updated to beta3.1, thought it had fixed, but checked time on my phone, found out it apparently rebooted a few hours ago.

Came searching, found the link to the instructions... only one small problem:

C:\Android\android-sdk\platform-tools>adb shell

# mount -oremount,rw /dev/block/stl9 /system

mount -oremount,rw /dev/block/stl9 /system

# vi /etc/init.d/00sysctl

vi /etc/init.d/00sysctl

vi: not found

# vi /etc/init.d/00sysctl

vi /etc/init.d/00sysctl

vi: not found

#

So I thought I'd grab it with adb pull and edit it, push it back...

00sysctl doesn't exist.

pulled the whole init.d folder, I have 01sysctl

made the edit there, pushed it the file back

followed the rest of the instructions.

Checked with root explorer, confirmed the line took.

Now to wait and see.
[Samsung Galaxy S (4G Model)] Labaznik:
Sorry, I'm not complaining, but the whole issue is still confusing... Is the fix related only to Valhalla ROM? The phone reboots with the latest kernel and plain stock KJ6. Doesn't do it with 0.0.2d. So it's still the kernel not the ROM? Or do we have to remount /system as r/w at boot on stock ROM? Is this OK to always open /system to all programs, not even ones we give root access?
[Samsung Galaxy S (4G Model)] itzik2sh:
Hi Raver

I owe you an apology, i somehow thought the random reboots are related to your ROM and not to the kernel, since kernel worked flawlessly for 2 weeks for me on v.final. Just flashed it to my wife's barely used phone and it rebooted on v.final. so it is the kernel so i apologize for doubting you. Anyway i appreciate all work done by you and Bryan, but for me an adb shell workaround is a no go, so i returned to 2c kernel, unless i miss something.

Sent from me