yashsingh1/xdaforums huggingface dataset:
[Galaxy S Plus I9001 Android Development] Christopher83:
Some benchmark results:

Benchmarks run with K^Kernel v1.5.5 OC/EXUV 360MB on CM10 Release 1 by Ivendor

The first result has been run using 245MHz-1401MHz cpu frequencies, OnDemand cpu governor and ROW I/O scheduler

The second result has been run using 245MHz-1824MHz cpu frequencies, SmartAssV2 cpu governor and SIO I/O scheduler

​

You can get even higher results by using the 370MB kernel version and by using other cpu governors (eg. Interactive, Performace, Lulzactive, Hyper) and/or V(R) IO scheduler
[Galaxy S Plus I9001 Android Development] EB20XY:
3.0.72 - 1.5.5

Thanks for the new kernel.

Testing ...
[Galaxy S Plus I9001 Android Development] hecvalve:
thanks for your great work
[Galaxy S Plus I9001 Android Development] miloytyn:
Not 100% sure if this is ROM or kernel related error and I still haven't tried 1.5.5. In 1.5 with Xistance's CM10.1 Google Talk video from front camera was upside down in both preview as for the other party. I'll check that with 1.5.5 also. However, in Skype the video is correctly shown.
[Galaxy S Plus I9001 Android Development] Christopher83:
If I well remember this is a known issue of the CM 10.1 rom:

xdaforums.com/showpost.php?p=39889162&postcount=1310
[Galaxy S Plus I9001 Android Development] jcah73:
your kernel is fantastic, thanks for your work Christopher
[Galaxy S Plus I9001 Android Development] miloytyn:
Yeah, now I remember where I read about that. Doomsday fixed it in his version of CM10.1.
[Galaxy S Plus I9001 Android Development] rickvrolings:
It also was in alpha versions of cm9. I think it isn't a hard thing to fix.

Verstuurd van mijn GT-I9001 met Tapatalk
[Galaxy S Plus I9001 Android Development] kouros17:
Christopher, the new edition of kernel (v1.5.5. ExUV, 370MB) works perfectly on cm10 release 1!

Many thanks for the frequent updates, which include the latest changes of arco's repos. This is the only 3.0.72 kernel so far, for our devices.
[Galaxy S Plus I9001 Android Development] EB20XY:
3.0.72

The new kernel works fine. Low battery drain and smooth. Nice!
[Galaxy S Plus I9001 Android Development] muhammadnajmi96:
Hey Christopher , can I use your kernel in Slimbean 4.2.2 by Tim? :confused:
[Galaxy S Plus I9001 Android Development] davidteri91:
You ask to Tim because I don't Know if the slim rom use the same ramdisk like cm ROM

Inviato dal mio GT-I9001 con Tapatalk 2
[Galaxy S Plus I9001 Android Development] hecvalve:
i´m flashed k´kernel 4.2.2 v1.5.5 oc-exuv-370mg with slim rom 4.2.2 build 3 and no problem
[Galaxy S Plus I9001 Android Development] magicw:
+1 - no problems so far.

However, I have one issue but it's not really related to christophers Kernel as every Kernel I tried recently shows this issue.

I can't do logcat.

Is there any advice on how to acitvate logcat?

Some 3.0.6x Kernels were able to do it but recent revisions did not work with apps like catlog or others.
[Galaxy S Plus I9001 Android Development] omegaRED7:
In terminal emulator:

su

logcat >/sdcard/log.txt

Be sure to setup a CTRL key in Settings of Terminal Emulator (I use volume down). When you want to stop logging, just press CTRL + C (in my case vol down + c).

Sent from my GT-I9001
[Galaxy S Plus I9001 Android Development] magicw:
yeah thanks - but I will try this variant - but why doesn't work catlog app?

Edit: even terminal based command does not work for me:
[Galaxy S Plus I9001 Android Development] sziggins:
gps drain issue

Hi Christopher,

I installed your kernel EXUV, 360MB for ivendor's b4. As always smooth with great battery save. But I tried to turn on gps using the applications "copilot gps" and "gps test". I didn't lock any satellites because I was in a place with tall buldings. I just turn off the gps and after some hours I saw a huge drain as the phone didn't go in deep sleep. I think Rhonin had a same issue mentioned in ivendor's thread as I reported there too, my problem solved with a reboot... I think it is a rom realated or an application I mentioned above.

Anyway, except this the phone is working really good, thanks.
[Galaxy S Plus I9001 Android Development] dr.wtf:
had the same problem with castignaits kernel, using pacman 19 without mentioned apps. it was enough to accidentally activate gps in the status bar (missed the button)

also i couldn't reproduce the issue
[Galaxy S Plus I9001 Android Development] luckana:
that's actually the best kernel I've tried for our phone... i really like how fast it turns the screen on after pressing the power button - it's starting at the spot with no delay.. its so smooth and battery friendly
[Galaxy S Plus I9001 Android Development] Christopher83:
Hi Magicw,

on which rom you're facing this problem?

The command is wrong, you should use:

logcat -f /sdcard/log.txt
# or
logcat > /sdcard/log.txt

I use always -v time parameters to get the readable time of each message...
[Galaxy S Plus I9001 Android Development] omegaRED7:
You forgot the > . It should be

logcat >/sdcard/log.txt

Obviously you can add "-v time" or other switches too (like "-b radio"). Radio logs are not displayed by default in logcat if you do not use the switch above.

Sent from my GT-I9001
[Galaxy S Plus I9001 Android Development] magicw:
still not working neither with ">" added nor with "-v time" or so.

SlimBean 4.2.2 from 04.04.13 - but neither worked with xistances cm10.1 revisions

K^Kernel for 4.2.2 370MB exUV

well, its not only your Kernel also others dont do this. Nor with an app like CATLOG.
[Galaxy S Plus I9001 Android Development] rmanuelb:
Thank you for your Kernel
[Galaxy S Plus I9001 Android Development] PatrickMac:
Really great job Christopher! Battery life is just awesome, by far the best I had so far with JB. And on top of that it is really smooth :)
[Galaxy S Plus I9001 Android Development] francescohtc:
are you gonna do a supermem version with 390 mb of ram?

i think it will be very interesting, because videos made with s plus sucks, so we don't need 720p...

IMHO.

Thanks
[Galaxy S Plus I9001 Android Development] Laurentyu1995:
so that mean if they'll be fixed we will don't have anymore that annoyance ( sometimes after a call google now opens itself ) ? THANKS !!
[Galaxy S Plus I9001 Android Development] Christopher83:
Yes, I pushed the fix for that problem yesterday.
[Galaxy S Plus I9001 Android Development] Laurentyu1995:
woooow, you're amazing !! and i hope other dev it'll include that change in next build ... THANKS !!!
[Galaxy S Plus I9001 Android Development] ktulu84:
That's a good news!

inviato dal mio telefono usando il tasto invia
[Galaxy S Plus I9001 Android Development] dr.wtf:
do other kernels have the same phantom key pressing issue? lately my phone shows weird behaviour with all of them. eg an app starting randomly...
[Galaxy S Plus I9001 Android Development] Christopher83:
Yes, no matter which is the rom or kernel used, as I said before, this is a well known hardware bug common on some I9001 and other Samsung phone models... I only tried to find some kernel workarounds to prevent the side effects caused by this hardware bug.

If there is someone that would like to help me in testing the phantom key presses fix, here you may find a fresh test build (I built it during my train journey to reach my workplace):

K^Kernel_JB-4.1.2_3.0_v1.5.6_Linaro_4.7.3_Test5_Signed.zip

Let me have your feedbacks... :fingers-crossed:

Thanks!
[Galaxy S Plus I9001 Android Development] sziggins:
Hi Christopher,

I will test it but after I return from work. Can you just mention the way to have the same extract of the debug log messages as you mentioned at post #163?

Thanks for your great work!
[Galaxy S Plus I9001 Android Development] Christopher83:
For that test release (K^Kernel_JB-4.1.2_3.0_v1.5.6_Linaro_4.7.3_Test5_Signed.zip), I silenced the debug messages and I disabled the dynamic debug option inside the kernel config, because I'd like to also test the performance and because, when the problem occurs, it will flood the log with debug messages...

If you want a debug release, here you can find the previous test version which has some verbose info messages:

K^Kernel_JB-4.1.2_3.0_v1.5.6_Linaro_4.7.3_Test4_Signed.zip

To watch the log messages, follow these steps:

- Put your phone in 2G mode only

- Open Terminal Emulator

- Run these commands for a live show of the kernel messages

su
cat /proc/kmsg

- Or, run these commands to save the log messages inside the file /sdcard/log.txt

su
cat /proc/kmsg > /sdcard/log.txt

- To stop the cat command, simply press Volume Down and C or close the Terminal Emulator window (don't use the back key, use the X icon on the top right)

Note:

The debug messages will be only related to the new fix for the phantom HOME key presses, the debug messages related to the phantom BACK and MENU key presses are silenced, if you want to see these messages too, I'll need to create a new build to re-enable the dynamic debug option...

Thank you very much for your support! :good:
[Galaxy S Plus I9001 Android Development] dr.wtf:
i'd like to have one for testing. i never had that problem with the home button.
[Galaxy S Plus I9001 Android Development] Christopher83:
Which is the strange behaviour you're facing? Google Now unexpected popups?

If so, this is caused by many induced phantom key presses on menu touchkey...

If you'd like to help me in testing you may use the Test5 kernel build for a while and tell me if the problem will disappear... I'm at work now, and I can't do anything else, sorry...

Thanks.
[Galaxy S Plus I9001 Android Development] dr.wtf:
its not google now. i blocked all the google-related apps. its some other apps starting randomly after i unlock the screen or quit apps. doesn't happen every time and sometimes everything runs without problems for a day

with test5 build i sometimes cant turn the screen on by pressing the home button. then i have to push the button twice fast.

had no phantom key pressures though.
[Galaxy S Plus I9001 Android Development] sziggins:
As always a detailed post!

I just returned from work. I experienced some battery drain NOT from gps this time...! I just toggle brightness (2 modes, auto & dim) from notification drawer, some calls and the phone didn't get in sleep mode. Some related screenshots at the end of the post.

Anyway, I just installed your (K^Kernel_JB-.1.2_3.0_v1.5.6_Linaro_4.7.3_Test5_Signed.zip) using TWRP 2.1.1 (safe...) and first impression is that I need some longer ( a little bit more than needed) press of "home key" for making it work!!! But that's really interesting as I always had a lot of tries before a successful one. For example I was trying to show the recent apps and it was just closing too fast (unsuccessful).

I’ll give some more feedback after some use.

Christopher you do a hard work here and it is really nice to see your achievements adopted by the others devs in their work.
[Galaxy S Plus I9001 Android Development] ktulu84:
just installed test4 (i wanted to read the debug information :D), it seems that sometimes the phone ignores me when i press home button (i guess it is difficult to recognize true key press and phantom key press), and sometimes when i press home button it's like i press it for long time and recent apps menu pops out
[Galaxy S Plus I9001 Android Development] dr.wtf:
still no phantom key pressure but i had a gps wakelock once again which drained my battery... somewhere in this log...

https://dl.dropbox.com/u/33668449/log.txt
[Galaxy S Plus I9001 Android Development] Christopher83:
Hi Sziggings,

thank you for those screenshots. From a first look, it seems that BetterBatteryStats (BBS) was preventing your I9001 to properly go into deep sleep...

Yes, as I understood, you suffered from the phantom key presses issue, is it right?

The need of a longer key press of the home key is simply caused by the workaround that seems to be not yet optimal for all. Unfortunately, I can't distinguish if there's a human fired key press or a phantom key press during the "storm" of induced interrupts caused by the antenna interference, so sometime the key press could be missed or need a longer press, but this should happen only in 2G mode and during those bad interference.

Sorry, I don't understand, are you facing that issue before the install of this kernel test version or during your testing session?

Thank you very much!!! :good:
[Samsung Galaxy Player 4.0, 5.0] safariking:
http://xdaforums.com/showthread.php?p=39364571#post39364571
[Samsung Galaxy Player 4.0, 5.0] gx36000:
For the 5.0?

I love this, except could you make one that fits the Galaxy Player 5.0 screen?

(i tried something like this meant for the 3.6, and some things were off center, so i restored it back to normal)
[Samsung Galaxy Player 4.0, 5.0] Matoxxi:
R: [THEME][YP-GS1] The Ultimate SGS2 JB Theme Vesion 2 [11-03-2013]

Safari why the volume bar in the music and video app looks bad? Also in media apps

How i resolve this problem?

Sorry for my bad english

Inviato dal mio YP-GS1 con Tapatalk 2
[Samsung Galaxy Player 4.0, 5.0] safariking:
yes i need to solve that i do that today
[Samsung Galaxy Player 4.0, 5.0] safariking:
New version (fixed the sound crappy bar bug)
[MDA, XDA, 1010 Software Upgrading] estebang:
I installed the XDA developers ROM flawless, but the GRPS browsing deosn't work, and I need it. I want to go back to the original ROM, or other original QTEK ROM, but when I run the installer it stops after "waiting 10 seconds.." I tried 2 different ROMS I've found inthe forum, the UK O@ 3.17... and the 3.16...

How can I go back? Is it possible? Please developers help me

Thanks
[MDA, XDA, 1010 Software Upgrading] dish:
yes, it's no problem to flash (downgrade?) it to O2 3.xx,

I am not very sure what happened in ur XDA, but I suggest try to use Image Tool to burn the O2 rom.
[MDA, XDA, 1010 Software Upgrading] estebang:
what's the image tool?

Is it different from the installer I tried?
[MDA, XDA, 1010 Software Upgrading] dish:
OK, here is the reason:

B coz the rom which from xda-developers is base on qtek rom, so the id of ur XDA has been changed to qtek's id, once u want to install the rom from O2, the upgrade program found a different id and refuse to upgrade it.

u can:

use Image tool to write the ROM from O2

or

run adaptRom.exe in ur pc to update the ROM from O2, and then u can 'install' it from ur pc to XDA
[MDA, XDA, 1010 Software Upgrading] esteban:
how exactly I use the ADAPTROM?

I run it from the pc and nothing happenned. (A dos window opened and closed immediately) In which directory should I run it? Or is it from the mobile device through the pc? Please explain me.

The other thing is that I didn't understand correctly the process with the ROM image tool. I copied the ROM from the QTEK to the SD, and then I wrote in the SD the upgrade. Now the pc doesn't recognize de SD, I can't even format it and I'm too afraid to put it back in the XDA.

ANy ideas what should I do? I even tried Isobuster but it didn't read it.

Esteban
[MDA, XDA, 1010 Software Upgrading] Peter Poelman:
Copy adaptROM.exe to same direcory as installer (under "Program Files", called "RUU", "Programme A" or somthing similar.

Go to this directory using the command prompt, and then run adaptROM in that directory.

Run "Programme A", it will not complain anymore...

We're working to make this easier...
[MDA, XDA, 1010 Software Upgrading] stranger2000:
i am facing the same problem

hello dear xda-develpoers .... i have the same problem but i have the qtek and i flashed it with the new o2 rom with the xda-developers 1.1 but i cant go back to my orgeinal qtek rom ..i have triyed copying the adaptROM.exe to same direcory as installer (under "Program Files", called "RUU" then i have tryied to flash the rom but nothing changes can u please help me....thanks very much :oops:
[MDA, XDA, 1010 Software Upgrading] Peter Poelman:
I hope you also ran adaptROM, and not just copied it. First run adaptROM, then "Programma A"...
[HTC Desire S] VnnAmed:
Edited Version

I just wanted to post similar one but You did it for me. Anyway i edited it cause it was a mess :) Still I wonder will this work without GoldCard on any phone...

This is a simple guide for newcomers to Android. Please be warned that you might damage your phone and also that your waranty voids after you unlock your bootloader and the author doesn't take any responsibility for that. Still things shouldn't go wrong.

Link for the necessary files.

1. Copy Cyanogen mod 7 android 2.3.3.zip to your SD card.

2. Go here and click THANKS button for hasoon2000. This is his tool and he takes all credit for his hard work.

3. Now open "HTC DESIRE S - All in one toolkit" and double click on Desire S.exe.

4. Follow all the instructions in the left hand corner on how to unlock your bootloader

5. Now we are going to flash recovery. Look in the right hand corner, select TWRP 2.4.0.0 and click Flash Recovery button and follow the instructions.

6. It's time to go to the recovery. While in fastboot select bootloader and then recovery. A htc logo will appear and then TWRP should start.

7. When you're in the recovery MAKE BACKUP. Then go to Wipe section. Now wipe these four: Cache, Dalvik Cache, Factory Reset, System. After that go back, click Install and select Cyanogenmod 7.zip you placed on your SD card. Slide to flash and wait.

8. After flash is complete go back to TWRP main menu and select Reboot and then Bootloader.

9. When you're in bootloader go to the folder where all my tools are located.

Go to android tools and press shift then right click and select open command window here.

10. In the Command Window copy and paste the following :

fastboot flash boot boot.img

11. After it's completed select the reboot option using your arrow keys.

Wait until cyanogenmod 7 boots up. This is first boot so it may take a while. Don't get nervous.

12. When Cyanogenmod 7 will start go to Settings > Applications > Developer options. Enable USB Debugging

13. After that go to android tools folder again and open the command window and paste the following :

adb push C:\downsaga\misc_version /data/local/tmp

adb shell chmod 777 /data/local/tmp/misc_version

adb shell

su

cd /data/local/tmp

./misc_version -s 1.27.405.6

exit

exit

exit

adb reboot-bootloader

14. When your phone will be in bootloader in fastboot USB mode type:

Fastboot oem lock

15. After that the phone will give you Warning. It's fine. Stay in bootloader in fastboot USB.

16. Open the RUU I have provided and run it until it completes flashing.

17. You have hboot 0.98.0002 now. Use the superoneclick app I provided.

18. After that run revolutionary tool and follow the instructions. After it's complete reboot into bootloader. Things should look like this:

-Revolutionary-

SAGA PVT SHIP S-OFF RL

HBOOT-6.98.1002

RADIO-38.03.02.11_M

eMMC-boot

(current date),(current time)

Big thanks to:

lY-AssassiN-Yl

hasoon2000
[HTC Desire S] warjar:
Thanks for this guide. I've seem to have run into an issue though...

It been 20-30 minutes now, and still booting. Is it now time to get nervous?
[HTC Desire S] VnnAmed:
Yes it's too long. Try connecting your device to PC and in command line (adb) type: adb reboot recovery.

If this doesn't work try Three button reset. Push power, volume up and down simultaneously. If this doesn't work too follow these steps

1. Connect phone to USB

2. Remove battery

3. Phone will still be running

4. Shutdown PC to cut the USB power

Now boot into recovery (hold vol down and click power). I'm sorry this is partially my fault. I just switched my brain off during writing this assuming this was right and n00b proof :silly:. It isn't. There is one more step before flashing Cyanogenmod that you may not be familiar with. When you manage to get into recovery go to Wipe section. Now wipe these four: Cache, Dalvik Cache, Factory Reset, System. After that flash (install) cyanogenmod again. This time it will boot. I'm updating guide right now and I'm sorry for your stress and inconvenience. If it works please report back.
[HTC Desire S] warjar:
Thanks for the anwser, although I managed to solve this shortly after posting last nigth. Basicly I just removed the battery break the loop, wiped data and cache and reflashed.

Yes, I will have to ID myself as somewhat of a noob on the andoid-front and want to point out some parts of the guide that aint 100% noob-proof. A couple of times I was actually forced to think for myself. That's outrageous! :D

1. Place the folder "Desire_S_All-In-One_Kit_v2.0" at your C:/ root and run the .exe from there. Won't work baked into some other directory I believe.

2. Replace "adb push C:\downsaga\misc_version /data/local/tmp" with "adb push misc_version /data/local/tmp". Otherwise you will be looking in the wrong dir the way this rest of this guide is set up.

3. At step 11. If stuck on loop, follw these steps:

A. boot into recovery

B. wipe data/factory reset

C. wipe cache

D. go into partitions menu, and format boot and format system. (I skiped this part this time)

E. install rom zip from sdcard

F. reboot

4. At the end of step 13 there seem to be one "exit" to many. (this is just a trivial thing ofc)

5. Step 17: I had to run this one several times before it got propper rooted. What seem to make the difference was actually the in order i did things during the su test after the "successful" root. Go to your phone app-list >>superuser>>Preferences>>Automatic responce>>Allow befor you click away the warning on your computer.

I also ran all programs as admin, didnt test if it would work without, but it's generally a good idea with these things.

Remember, when you write for noobs you have to include the obvious ;)

It's the first time i've touched this root-stuff so take this for what it is. It solved it for me, but may not always be the correct fix.

I've been wanting to root without using HTCdev, but resigned to this after beeing thrown around to some 10-15 differnet sites and guides, with missing software etc..

Now to figure out what ROM to use as this one had Sense 2.1, and why TiBu crashes when I attempt to remove bloatware. But that will have to be another story...

Thanks for the guide guys, and for providing all the software needed in one package, that's probably the most useful part for a newcomer =)
[HTC Desire S] hmz12:
RUU

Hey guys,

got up to the RUU part and it says when updating rom from "13.10.401.8" to "1.31.206.1" Cannot be updated due to it being the wrong RUU, please find one for your phone

Also Im in the UK

Background :

Flashed it before to run primo s 4.1. Did not have the S-OFF

had ext4 ? then it changed TWRP
[HTC Desire S] paulie-uk:
Wrong can mean two things:

1. Did you misc_version from a root/temproot environment? If you didn't have the right privileges, you can't do this step.

2. Your phone is Branded (to your carrier), you need to either choose a RUU that matches your carrier (see "+files" then RUU in my sig) or create a goldcard, which should let your phone ignore the carrier/region check.
[HTC Desire S] zeus.lny:
Will this method works on ICS Desire S updated via ICS RUU and unlocked via HTC DEv
[HTC Desire S] VnnAmed:
Sure. Actually it's how I did it :)
[HTC Desire S] zeus.lny:
i am already running Andromadus AOSP 4.2.2 with S-On for for me to S-Off my phone i have to follow from step 12 of your guide as i already have 4Ext recovery installed, Also 1 thing.. Do i have to make a gold card to run the RUU of my regions to Downgrade my hboot ?
[HTC Desire S] hmz12:
@paulie uk

hi, i figured i dont need s-off, just had to flash the boot.img

NOOB mistake

thanks anyways guys!!!