yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] capillonpub:
Hi,

I had the same issue just after feamod 1.4 + Skyhigh installation. But i also had this issue once with the stock kernel after changing the network in a foreign country. The solution is very simple, even if data connection is on, force it to off then on again:

- in the network setup, uncheck the data connection and validate. Then check again the data connection. (i dont know the exact wording of th option because my phone is setup in french)

Thanks for this kernel, work like a charm on my stock rom BVKPA 2.3.4 !
[Galaxy S Plus I9001 Android Development] skywalker01:
Upps, no offense chasemyass, but did all those noobish posts here confuse you too much lately ? :rolleyes:

The poster of post #71 asks how to enter CWM (aka RECOVERY mode aka FeaMod recovery on i9001) and NOT DOWNLOAD mode ! ;)

And the method described in post #75 is the correct one for RECOVERY mode if you use the buttons for that instead of software controlled methods. And as we are talking of it: while it is no problem at all to enter RECOVERY mode software controlled - this is actually my preferred method - NEVER do that with download mode. Odin will most probably fail on platform verification when you didn't use the "hardware button method" to enter download mode. But I know that this is already well known among the experts here, isn't it ?
[Galaxy S Plus I9001 Android Development] chasemyass:
I think they did LOL!!! and i`m not offensed at all skywalker :D my avatar says EVERYTHING ;)

and yes I know gettin` to download mode using anything else than built in buttons will fail in Odin, I know that because I "saw" it commin` 1-2 times after I bought my sgs+
[Galaxy S Plus I9001 Android Development] skywalker01:
Yes and no. Nothing new in the last 14 days since I wasn't at home a week and worked exclusively on the kernel for the other week.

But I made some progress before that which isn't published yet. But I still don't know if it is a good idea to publish that version at all because it is a "dead end solution" which causes more problems than it solves.

I know, I am talking in miracles but it is very hard to explain to non-coders even for me. So I must ask you to wait another week before I can continue on that matter.

I fear the same :(

So why do you do then ? ;)

> Just posted an update on my CM7 port status here: http://xdaforums.com/member.php?u=2062740
[Galaxy S Plus I9001 Android Development] Rhonin86:
few questions concerning Version 1.4

Hi Skywalker,

damn good work you have delivered ;) but i already mentioned it.

I've seen that you have taken the Simple IO-scheduler as default. Did you select it for stability purposes ?

You wrote that bootanimations are NOT included but supported. When i stalled version 1.4 i've got a new bootanimation :confused: ...

I often was asked in the german forum how much the kernel is undervolted and i had to admit that i couldn't tell. When i looked at the standard voltage configuration of your kernel OC/UV Beater2 told me that the minimum standard voltage was 900 mV, but i could to set it to 750 mV. :confused: So isn't it set to 750 mV by default or is there an unknown sideeffect ?

Did you implement the cache scroll tweak provided by dsexton702 ?

Thanks for all the information in advance - i'll really appreciate it. During this week i hope to send you some logs concerning the charging dock issue so that you may find a solution :cool:

Cheers

Rhonin
[Galaxy S Plus I9001 Android Development] b02:
I have a question considering battery usage... Is it longer lasting then in stock ?

at default 245/1401 ..
[Galaxy S Plus I9001 Android Development] uberto.costanzo:
hi all work good whit this kernel, only gps is very low and data 3g sometime is very low, any solution please ? thanks for reply
[Galaxy S Plus I9001 Android Development] chasemyass:
Definitely for me...and smother too ;)
[Galaxy S Plus I9001 Android Development] skywalker01:
I'm using the same gps.conf as in BroodROM RC4. It has a very long sat fixing time at first use and it will become normal after that first fix. But you can safely replace it with any other gps.conf that works better for you.

BTW: gps.conf is the only factor that incluences the gps performance. And it is located in /system/etc/ so it is not even part of the kernel itself and can be modified by anyone to his own likings (phone must be rooted of course to be able to write to /system).

3G data or any other radio related stuff is UNTOUCHED in this kernel and your problems with that must have another reason. Maybe you are using a custom ROM with a wrong apn list, missing stk.apk or something like this. Which ROM are you using ?
[Galaxy S Plus I9001 Android Development] uberto.costanzo:
oohh please please my sgs+ reboot always in recovery i can't go in downoad mode when i press vol- home button and on i have not download mode but only "samsung" if i on i go only in recovery feam recovery 1.4. i reflash kernel 1.4 but rebut only in recovery. please help super thanks for reply bye
[Galaxy S Plus I9001 Android Development] carlese:
i'm waiting for the skyhigh 1.4 for low sd cards.. :D
[Galaxy S Plus I9001 Android Development] uberto.costanzo:
is not possible format sdcard error in recovery please help
[Galaxy S Plus I9001 Android Development] skywalker01:
OK, here are your answers:

1. added FAQ #7 (in post #2) to cover that

2. added FAQ #8 to cover that

3. see also FAQ #7 for that (in more detail: being able to do something doesn't mean that you SHOULD do it. Actually it is a very bad idea in most cases to modify everything to the limits. But nevertheless I added all the customisation possibilities just for your convenience so that you can use them if you really want to. But you must find for yourself if it does help your device or not. Most probably it will cause harm instead of improvement ;) But there are always some devices out there that work fine with certain settings much beyond the stock limits so these features are primarily there for these exceptional devices.

4. this is no kernel tweak but a system tweak ! And it is ROM version dependent and therefore can only be safely integrated into a complete custom ROM. Additionally I don't know exactly what it does and if it would really improve the i9001 since it was originally made for a completely other hardware.
[Galaxy S Plus I9001 Android Development] skywalker01:
This is a recovery issue and not kernel related. I think I saw a patched FeaMod version in some thread lately that fixes this problem but can't remember where (in FeaMod or BroodROM thread perhaps ?)

Just found it in General Q&A where your questions actually belong. See here: http://xdaforums.com/showpost.php?p=24244850&postcount=487
[Galaxy S Plus I9001 Android Development] skywalker01:
:confused: ??? While I don't understand completely what you actually mean due to scary English I am absolutely sure that this is a recovery=FeaMod problem. You are in the wrong thread again ;)
[Galaxy S Plus I9001 Android Development] chasemyass:
http://xdaforums.com/showpost.php?p=21527547&postcount=875 there you go mate. Just download signed-delete......noreboot.zip and flash from cwm
[Galaxy S Plus I9001 Android Development] skywalker01:
This will only fix it temporarily and not permanently ;)

Well, since this still seems to be a big problem I just decided to release a completely fixed version of FeaMod recovery V1.4 curing all those reboot and boot loop issues. I already released a fix for the nonOC/nonUV capable devices back in January that caused the affected phones to remain in boot loops while not being able to enter recovery mode at all. I combined that now with a reboot fix I already use in my CM7 build which also stops affected devices to reenter recovery again and again instead of booting to system (android).

Actually the package is already finished, will have to test it first and then open a new thread for it.

Unfortunately this will postpone my other projects, so there will be no kernel fix today but hopefully in the next few days.

Sorry for the inconvenience, but that was just a quick job in between and should really help a lot of people, at least I hope so.
[Galaxy S Plus I9001 Android Development] c_shekhar:
Whatever is said and done, the

Sd card problem still remains with this kernel.
[Galaxy S Plus I9001 Android Development] Blumdum:
well not every phone is the same

for me the sdcard works perfect

but for example i had sdcard troubles with FeaCore

so every phone behaves in a different way and you have to decide which kernel is the best for you
[Galaxy S Plus I9001 Android Development] carlese:
skywalker said he's gonna release a new version to fix the problem.. let's wait for it!
[Galaxy S Plus I9001 Android Development] m4sterx:
Can I disable the audio boot? how?

thanks
[Galaxy S Plus I9001 Android Development] skywalker01:
Just delete /system/etc/PowerOn.wav
[Galaxy S Plus I9001 Android Development] skywalker01:
Patch is ready and will come today, just some tests and instruction updates to do.

EDIT: new version 1.4a uploaded and first 3 posts updated. Your tests may begin :D
[Galaxy S Plus I9001 Android Development] :
How I can replace the bootanimation? I tried it via replacing the sanim.zip but it hasn't worked. :/
[Galaxy S Plus I9001 Android Development] chasemyass:
try via bootanimation.zip

next time read OP carefull :D
[Galaxy S Plus I9001 Android Development] Coertmans:
change sanim.zip to bootanimation.zip works 4 me
[Galaxy S Plus I9001 Android Development] xeGox:
How can I undervolt the device?

I have installed incredicontrol,I've checked "set on boot", but if I reboot the phone,I find the old value (from 900 mv in lower freq...)

What's the under volt value put in the Kernel?

Sent from my Sgs+ Gt-i9001
[Galaxy S Plus I9001 Android Development] alessia3:
look carefully at the incredicontrol options, you have to check the box "save for boot" and then click "apply".

under that, you should find the following phrase: "Boot settings found".

your current settings will be saved for next boot.

is that right?

be aware: set as boot only the voltages you are sure.

wait and test carefully the correct voltages for your cpu before applying as boot.

undervolting cpu makes phone unstable at certain voltages, depending on how good is your piece of silicon...

about the kernel default voltages, do read yourself from incredicontrol.

cheers
[Galaxy S Plus I9001 Android Development] neluba:
And I'm using a 16gb class 10 sd card

Still getting this bug with your new kernel update :(

But the kernel is too awesome to change it :D
[Galaxy S Plus I9001 Android Development] Coertmans:
my sd is a 8gb class 10 and no problems for me ...
[Galaxy S Plus I9001 Android Development] skywalker01:
:confused: Did you actually reformat your sd card in the phone AFTER installing V1.4a ?
[Galaxy S Plus I9001 Android Development] neluba:
Yes, and i also tried this http://xdaforums.com/showthread.php?t=1058736

But it only appears while the phone is sleeping. I never got this error while im using my phone or while i'm hearing music
[Galaxy S Plus I9001 Android Development] skywalker01:
OK, the latter information might help while debugging that issue further. This really challenges me now and I'm also curious why this actually happens at all (on some phones). Stay tuned, next release is not far, most probably tomorrow.
[Galaxy S Plus I9001 Android Development] Rhonin86:
exactly the same problem....

Hi Skywalker, hi nebula,

i already asked in our german forum about the music-hearing issue. I haven't updated to your latest V1.4a. I use instead the original 1.4. There are no additional performance scripts in operation. The problem with the jerking songs appears as nebula mentioned during the sleep-state. (Is it really the sleep-state ? the music-player is playing but the screen is off) I tried different adjustments with the lowest frequency (raised it), with different governors but i didn't succeed :( Seems to be within the new kernel...

Hope you find a solution

Cheers

Rhonin

[My fault :o]: Sorry for posting this problem, because it wasn't caused by the kernel !

Only a misunderstanding of the used OCUV Beater 2.

Explanation: I thought that the daemon uses the sleep governor only for the sleep state. So i thought that during hearing music this governor is not activ, but it was the leading governor. So this little daemon distinguishes only between screen On/Off on our phone.
[Galaxy S Plus I9001 Android Development] seba2121:
My minimal working voltage try it but don't check "save on boot" in first time you test btw you fon mabey is unstable

Sorry for my english.
[Galaxy S Plus I9001 Android Development] rayiskon:
did u notice any improvement in battery ?
[Galaxy S Plus I9001 Android Development] seba2121:
Yes my battery is better life in undervolted and underclocked. Not big change but changes :)

Sorry for my english.

Napisane z SGS+ Brood RC4
[Galaxy S Plus I9001 Android Development] michhh:
Fix doesn't work form me.kingstorm 16gb class 4 got disconnected

Inviato dal mio GT-I9001 usando Tapatalk
[Galaxy S Plus I9001 Android Development] banditos88:
Doesn´t work for me, too. Got a 4GB MEDION Sd-Card.

And i got the problem, that i can´t make a CWM Backup to the sd card.

Always get the error "can´t mount backup path". It only works to the internal sd.
[Galaxy S Plus I9001 Android Development] chasemyass:
Have you tryied to flash again CWM? Or maybe try another version of recovery? we have like 3 versions of recoveryies now...;)
[Galaxy S Plus I9001 Android Development] suzuki6888:
Very like skyhigh kernel v1.4a but I also got the sd card auto eject when idle the phone for 5-10minutes.

My sd card is kingstone 16gb class 4.

I also found the phone will scan the sd card two times, when start the phone. The stock kernel and feamod kernel only scan 1 time only.

I flash it back to feamod v1.4 oc 1.8 kernel without the sd card problem.

maybe skywalker01 can compare feamod kernel and skyhigh kernel to find out the problem.

Thanks.
[Galaxy S Plus I9001 Android Development] chasemyass:
Ok guys, I think we can help skywalker with somethin` else than just telling him what SD cards we use and if they work or not ;)

I really hope this will give him a hand and is not only in my imagination ;) and also it`s pretty simple too, even for non experienced users :D

here we go:

open your dialer (stock one preferably) and type *#9900# and a menu like THIS will popup and press the option highlighted ;) then navigate to your SD card root (/sdcard) and look after THIS txt file and upload it here...would be nice if you do it as soon as you get the SD error...

I will attach mine with no SD problems so skywalker can compare them if he thinks he might get some answers from it ofc.
[Galaxy S Plus I9001 Android Development] addisuw:
Well here is mine. Actually it got disconnected twice in about 5-10minutes.
[Galaxy S Plus I9001 Android Development] skywalker01:
Totally agree on that :)

Sorry, but this is NOT the kernel log. It's just a log of the dalvik engine which doesn't help much in case of a kernel problem.

You can find in the FAQ how to create a proper kernel log (dmesg).
[Galaxy S Plus I9001 Android Development] skywalker01:
Can't agree on that:

1. actually my phone starts the media scanner twice with every kernel and I never saw it otherwise

2. but that's logical because it doesn't depend on the kernel (alone) how often the media scanner starts on startup; but I will try to dig deeper into that issue in the next days

Actually there are thousands of differences and I know them all so this won't really help. Or in other words: reverting all those differences would make SkyHigh equal to FeaMod, so what's the benefit of that ?

A comparison between SkyHigh V1.3 and V1.4 would be much more efficient, wouldn't it ?

But there are still more than thousand differences even between these two versions and I already compared them. Look at the changelog (post #3), I already reported some of my findings.

So it's hard to find the decisive difference when you can't test it because this problem doesn't even occur once on your device ;-)

I will release another test version with less sd card tweaks when time allows, can't tell exactly when right now.
[Galaxy S Plus I9001 Android Development] suzuki6888:
Yes u are right.

I use skyhigh v1.3 without any sdcard problem.

like it:)

1 noob suggest don't knows can help u or not.

i find 1 different at

/sys/devices/virtual/bdi/default/read_ahead_kb

/sys/devices/virtual/bdi/179:0/read_ahead_kb

/sys/devices/virtual/bdi/179:32/read_ahead_kb

at v1.3 all value is 128

at v1.4 got different value is 512 & at default is 3xxx

i also try to edit read_ahead_kb value at v1.4 to 128 but cannot help.

maybe can try use all content at /sys/devices/virtual/bdi/ at kernel v1.4
[Galaxy S Plus I9001 Android Development] c_shekhar:
The SDCard damaged issue still remains. It appears while the phone is in sleep mode...earlier as well as now wit this 1.4a.

[OP] needs to look more deep into it...
[Galaxy S Plus I9001 Android Development] skywalker01:
Did you read the first post of this page. especially the last line ?

New version will come most probably tomorrow ;)
[Galaxy S Plus I9001 Android Development] BrodaMGS:
Highly anticipated ;) rebooting my phone for the third time today ^^

Wysłane z mojego GT-I9001 za pomocą Tapatalk
[Galaxy S Plus I9001 Android Development] skywalker01:
Cool that of all changes you just found this one (coincidence ?). Because this is exactly the tweak I will change in the next release. Just hadn't the time yet, yesterday I wasn't at home till late night, but I try to release it tonight.

These are the stock values and I didn't tweak the read_ahead caches before V1.4 but as mentioned before that's just one among many other changes in V1.4 and we will go thru them one by one ;)

What exactly do you mean by default ? The default values from Samsung are 128, some custom ROMs tweak it to 3072. And Thunderbolt and Adrenaline shot also tweak them to some very high values (actual values depend on version) which doesn't make sense. I already explained that earlier in this thread.

But the point is that if you have SkyHigh V1.3 with Thunderbolt or any FeaMod version with Adrenaline shot for example you will get the same tweak. Since this seems to work for all phones it seemed very unlikely so far that it would make a difference in SkyHigh V1.4.

But as there are only 2 more other possibilities (even more unlikely) that could make the difference on some phones I will change it anyway to test if this is really the culprit for some very mysterious reasons.

See above, it works in other combinations so the most probable reason is some kind of unique combination of values that only occurs on certain phones with V1.4. Therefore it seems even likely now that the read_ahead cache is really at least one part of the problem. Stay tuned for an altered read_ahead tweak ;)
[Galaxy S Plus I9001 Android Development] chasemyass:
there you go my logs then
[Galaxy S Plus I9001 Android Development] suzuki6888:
hello skywalker01.

I find another problem at your kernel.

I flash skyhigh v1.4a with stock rom (without root) do not have any sd card problem.

If flash skyhigh v1.4a with stock rom (with root) it will got sd card unexpectedly removed message after idle about 5-10 minit.

Hope this can help u at find out the problem.:)
[Galaxy S Plus I9001 Android Development] vitaliy_y:
Hi skywalker01, I looked at your commits on githab, you copied my source from one blunder.

After the release of your kernel I deleted my source files on githab :)

Error is simple, find it!!:D

In my recent releases error has been solved.
[Galaxy S Plus I9001 Android Development] uberto.costanzo:
hi is possible instrall this kernel in KQ8 ? thanks for reply
[Galaxy S Plus I9001 Android Development] rayiskon:
U mean KQB right? Nways, it should work on all GB roms ;)
[Galaxy S Plus I9001 Android Development] uberto.costanzo:
but in kernell there is graphic driver i8500 in kq8 there is new driver for i9001? thanks
[Galaxy S Plus I9001 Android Development] rayiskon:
No in KQB (value pack) egl files are still the stock i9001. But it doesn't matter if u get the updated egl's with the kernel, both drivers work on KQB, i tried the i8150 files earlier and it worked normally.
[Galaxy S Plus I9001 Android Development] nail16:
The egl driver's seem to be slightly changed in KQB ,

it runs perfect with sky high kernel.
[Galaxy S Plus I9001 Android Development] FlorisNL:
If I want a custom bootanimation, do I have to rename sanim to bootanimation.zip? The OP says it..
[Galaxy S Plus I9001 Android Development] b02:
I installed kernel, and for now it works fine and i think smoother. It works faster than it was, and about battery, well its too early to speak on that... :) but i will give feedback.

Also i have 1 question, since i saw a value pack for our phone, is it safe to flash the value pack over this kernel, since im unsure what changes does it bring.

OR i should restore the stock nand, install the value pack, and then install your kernel over all of it ? :)
[Galaxy S Plus I9001 Android Development] rayiskon:
u know that old saying "y would u do it simple when u can complicate it" ? well u're doing it :P

just flash the value pack after a full wipe, and flash skyhigh over. (keep in mind if u're flashing the skyhigh package as it is , u will replace the stock KQB egl files).
[Galaxy S Plus I9001 Android Development] skywalker01:
Well, that's one possibility.

Or replace /bin/bootanimation with another version that looks for sanim.zip (e.g that from FeaMod V1.4) like in broodROM.
[Galaxy S Plus I9001 Android Development] kellermanv:
Changelog for 1.4b ? :D i mean, only sdcard issues ? if so, i don't need to update it, since i don't have an external sdcard. :)
[Galaxy S Plus I9001 Android Development] chasemyass:
skyhigh works flawless with KQ8 but as it for KQ8 I would recomand you a FULL wipe and remove sim and external SD when you will flash it with Odin ;)
[Galaxy S Plus I9001 Android Development] carlese:
link for 1.4b doesn't work..
[Galaxy S Plus I9001 Android Development] rahilsayed:
Same here...link isnt working
[Galaxy S Plus I9001 Android Development] chasemyass:
+1 on taht I get a bad arhive of ~400Kb
[Galaxy S Plus I9001 Android Development] rahilsayed:
+1 same here
[Galaxy S Plus I9001 Android Development] faust.deaconu:
+1
[Galaxy S Plus I9001 Android Development] skywalker01:
Sorry, uploaded it again but get the same error myself.

BTW: I also get this error when trying to download your log file ;)

Must be an xda server error, will upload the file externally now and give a link to that later.

EDIT: external link added to post #1, hope it works for all of you.
[Galaxy S Plus I9001 Android Development] kubson1999:
It says that this kernel supports init.d, but after the installation does not have this folder. Just create the folder? I read somewhere that

Wysłane z mojego GT-I9001 za pomocą Tapatalk
[Galaxy S Plus I9001 Android Development] RavoxX:
Still cannot push files via apk-manager, says me that the system is read-only.
[Galaxy S Plus I9001 Android Development] skywalker01:
Good question, answer is easy:

init.d is supported but folder must be created OUTSIDE the kernel

It depends on your ROM: most custom ROMs already have the folder, stock ROMs never have it.
[Galaxy S Plus I9001 Android Development] carlese:
I'm trying to change the boot animation but I can't..is it a bug?
[Galaxy S Plus I9001 Android Development] chasemyass:
make sure u have it named bootanimation.zip and if still doesn`t work, do a wipe cache/dalvik
[Galaxy S Plus I9001 Android Development] carlese:
I have a cwm version of the boot animation.. It worked with skyhigh 1.3..
[Galaxy S Plus I9001 Android Development] michhh:
corrupted sd card with GT-I9001_SkyHigh_kernel_V1.4b_CWM_signed.zip .kingstom 16gb class 4!