Jump to content


Photo

[Q] OC kernel for GPU or CPU


  • Please log in to reply
76 replies to this topic

#1
djfnz

djfnz

    Regular

  • Members
  • PipPip
  • 120 posts
  • Gender:Male
  • Location:Hungary, Hajdúhadház
  • Devices:SGSIII-LTE & SGSM2

I read the today a topic on XDA in HTC Desire 500 section and the oblikas developer  made a custom kernel! 

 

Includes in kernel:

 

- Added GPU OC up to 450 MHz
- Added sio and fiops
- Added Smartassv2
- Enabled KSM

 

http://forum.xda-dev...d.php?t=2600294

 

We can port this to Blade V?


  • 1

#2
GaBBren

GaBBren

    Newbie

  • Members
  • Pip
  • 34 posts
  • Devices:ZTE Blade V

That is really nice. We need that for our Blade! Somebody please port it...


  • 0

#3
targetbsp

targetbsp

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 4,007 posts
  • Gender:Male
  • Devices:Blade V, I9000, Blade

I could use some init.d support.  I'm running out of room and could do with mounting an ext partition as data


  • 0
My Blade site - includes vanilla KANGS's of CM7. Also available: modified GB Gapps with various market versions, mini ICS Gapps for 160mb system partitions and Flash for ARMv6
CM7 Blade changelog

#4
KonstaT

KonstaT

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,681 posts
  • Gender:Male
  • Location:Finland
  • Devices:Moto G, ZTE Open C
  • Twitter:@konstatuomio

I could use some init.d support.  I'm running out of room and could do with mounting an ext partition as data

You don't need to touch kernel or even ramdisk for that. There's already plenty of scripts that are run on init. E.g. you could add your stuff to /system/etc/init.qcom.post_boot.sh or even make it run scripts from init.d folder.


  • 1

#5
targetbsp

targetbsp

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 4,007 posts
  • Gender:Male
  • Devices:Blade V, I9000, Blade

Ah thanks.  I'll have a play.  I tried using apps to add init'd support. I guess they just attempt do your latter suggestion of enabling init.d from another auto running location but said apps didn't work.  I shall try doing it myself. :)


  • 0
My Blade site - includes vanilla KANGS's of CM7. Also available: modified GB Gapps with various market versions, mini ICS Gapps for 160mb system partitions and Flash for ARMv6
CM7 Blade changelog

#6
djfnz

djfnz

    Regular

  • Members
  • PipPip
  • 120 posts
  • Gender:Male
  • Location:Hungary, Hajdúhadház
  • Devices:SGSIII-LTE & SGSM2

Any news?


  • 0

#7
targetbsp

targetbsp

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 4,007 posts
  • Gender:Male
  • Devices:Blade V, I9000, Blade

If that question is aimed at me, I'm afraid I haven't had chance to play yet.


  • 0
My Blade site - includes vanilla KANGS's of CM7. Also available: modified GB Gapps with various market versions, mini ICS Gapps for 160mb system partitions and Flash for ARMv6
CM7 Blade changelog

#8
targetbsp

targetbsp

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 4,007 posts
  • Gender:Male
  • Devices:Blade V, I9000, Blade

Nah, I can't get anywhere with this.  I don't know why.  It looks easy!

 

I can't get post boot to run another script.  Either the init.d folder or even a specific script.

I have an init.d test program that creates a log file and nothing happens when I try to call it from post boot.

If however, I copy the contents into post boot then the log is created so the test file works.

 

If I copy the int2ext script into post boot, nothing happens.  And the way I figure it, if I can't diagnose why I can't get one script to execute another, I sure as heck can't debug an entire Ext script!

 

I'm great at Windows but I don't have much of a clue at Linux so when the various instructions over at XDA don't work for no good reason - I'm kinda stuck!


Edited by targetbsp, 17 March 2014 - 10:08 PM.

  • 0
My Blade site - includes vanilla KANGS's of CM7. Also available: modified GB Gapps with various market versions, mini ICS Gapps for 160mb system partitions and Flash for ARMv6
CM7 Blade changelog

#9
shiftyc

shiftyc

    Regular

  • Members
  • PipPip
  • 92 posts
  • Gender:Male

Probably a case of the blind leading the blind here, but what did you do, put your script into system/etc/init.d?

 

So far as I can see, that folder doesn't exist in the stock ROM, which means that there's probably nothing to execute anything in there on boot. For example, often part of the ramdisk (init.rc) is responsible for running whatever scripts it finds in init.d.  As the stock ROM doesn't even have such a folder, I'd imagine the kernel doesn't have any code to attempt to execute scripts in there.

 

So you either need to find somewhere else to run the script from, or modify the kernel.  Alternatively, I think there are "autostart" apps that you could use?


Edited by shiftyc, 18 March 2014 - 09:33 AM.

  • 0

#10
targetbsp

targetbsp

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 4,007 posts
  • Gender:Male
  • Devices:Blade V, I9000, Blade

As konstaT suggested earlier in the thread, I was attempting to call the script from the post boot script (init.qcom.post_boot.sh ).  There are plenty of examples of doing this on XDA and it seems really easy (like 1 line) but I just couldn't get it to work. eg http://forum.xda-dev...d.php?t=1710980

 

Based on other examples I also tried busybox run-parts and directly naming the script I wanted to run.

 

The example script made the init.d folder and set the permissions for me.


Edited by targetbsp, 18 March 2014 - 10:16 AM.

  • 0
My Blade site - includes vanilla KANGS's of CM7. Also available: modified GB Gapps with various market versions, mini ICS Gapps for 160mb system partitions and Flash for ARMv6
CM7 Blade changelog

#11
shiftyc

shiftyc

    Regular

  • Members
  • PipPip
  • 92 posts
  • Gender:Male

I'm not exactly clear what you're trying to execute from init.qcom.post_boot.sh, but adding a command to the bottom of that script worked for me.  I just added a "touch" to create /data/test.log and the file appears after I reboot.

 

I suspect it's something to do with permissions, presumably you're mounting system as r/w in the script before you try to create anything?


  • 0

#12
targetbsp

targetbsp

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 4,007 posts
  • Gender:Male
  • Devices:Blade V, I9000, Blade

I can get commands to work direct like you have.  I cannot get it to run another script containing those same commands (in effect creating init.d support) the same way the XDA link shows (or various other ways I found)

 

Now, because I could get commands to work directly from post boot - I could theoretically post the script onto the end.  But it doesn't work.  And the fact that if I can't get something as simple as running another script to work, then I sure as heck can't debug a 150 line script.  I can do Windows but don't have much of a clue at Linux!

 

The goal is to add Ext partition support because Data is too small.


Edited by targetbsp, 18 March 2014 - 12:26 PM.

  • 0
My Blade site - includes vanilla KANGS's of CM7. Also available: modified GB Gapps with various market versions, mini ICS Gapps for 160mb system partitions and Flash for ARMv6
CM7 Blade changelog

#13
shiftyc

shiftyc

    Regular

  • Members
  • PipPip
  • 92 posts
  • Gender:Male

I tried the XDA article you linked and it didn't work, but that was because the "00test" script in the init.d folder didn't have execute permission.  I changed permissions to owner execute and it worked fine.


  • 2

#14
djfnz

djfnz

    Regular

  • Members
  • PipPip
  • 120 posts
  • Gender:Male
  • Location:Hungary, Hajdúhadház
  • Devices:SGSIII-LTE & SGSM2

I tried the XDA article you linked and it didn't work, but that was because the "00test" script in the init.d folder didn't have execute permission.  I changed permissions to owner execute and it worked fine.

Can you make tutorial & upload the files?


  • 0

#15
shiftyc

shiftyc

    Regular

  • Members
  • PipPip
  • 92 posts
  • Gender:Male

There's nothing to upload.  Just follow the steps in the linked article then use a file manager of your choice to change /system/etc/init.d/00test to have permissions of -rwxr--r--.

 

Or from the command line:

cd /system/etc/init.d
chmod 744 00test

Reboot and you should see /data/Test.log created.


  • 0

#16
djfnz

djfnz

    Regular

  • Members
  • PipPip
  • 120 posts
  • Gender:Male
  • Location:Hungary, Hajdúhadház
  • Devices:SGSIII-LTE & SGSM2

Thanks ;)

 

It WORKS!


Edited by djfnz, 18 March 2014 - 02:24 PM.

  • 0

#17
KonstaT

KonstaT

    Hardcore

  • Developer Team
  • PipPipPipPipPipPip
  • 2,681 posts
  • Gender:Male
  • Location:Finland
  • Devices:Moto G, ZTE Open C
  • Twitter:@konstatuomio
It shouldn't be much more than adding a single line and making /system/etc/init.d directory and it's content executable (755 permissions).
/system/xbin/busybox run-parts /system/etc/init.d

You might want to try to run that on command line as well and confirm that it works. If not, you might need to update your busybox as well.

 
If you've installed any of the latest updates, you should have /system/etc/install-recovery.sh (which CWM has made unexecutable). You could repurpose that for running init.d. It's better than init.qcom.post_boot.sh because the ramdisk service runs earlier in the init. ClockWorkMod might whine about it every time you boot out of though because it would still think it is trying to replace the recovery...

  • 1

#18
shiftyc

shiftyc

    Regular

  • Members
  • PipPip
  • 92 posts
  • Gender:Male

 

It shouldn't be much more than adding a single line and making /system/etc/init.d directory and it's content executable (755 permissions).
/system/xbin/busybox run-parts /system/etc/init.d

 

Confirmed that this also works for me.  You will need 755 permissions if you're testing from the command line.

 

 

 

ClockWorkMod might whine about it every time you boot out of though because it would still think it is trying to replace the recovery...

 

 

So what you're saying is that some really clever person needs to build us a CWM that skips the checking of install-recovery.sh...  :)


Edited by shiftyc, 18 March 2014 - 03:21 PM.

  • 0

#19
targetbsp

targetbsp

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 4,007 posts
  • Gender:Male
  • Devices:Blade V, I9000, Blade

I tried the XDA article you linked and it didn't work, but that was because the "00test" script in the init.d folder didn't have execute permission.  I changed permissions to owner execute and it worked fine.

 

/facepalm

I spent hours presuming the bits I were playing with were flawed - even though they should have been dead simple.  It never crossed my mind the test script installer would be flawed.  What's the point in it?? lol

Thanks


  • 0
My Blade site - includes vanilla KANGS's of CM7. Also available: modified GB Gapps with various market versions, mini ICS Gapps for 160mb system partitions and Flash for ARMv6
CM7 Blade changelog

#20
targetbsp

targetbsp

    Hardcore

  • MoDaCo Silver
  • PipPipPipPipPipPip
  • 4,007 posts
  • Gender:Male
  • Devices:Blade V, I9000, Blade

 

It shouldn't be much more than adding a single line and making /system/etc/init.d directory and it's content executable (755 permissions).
/system/xbin/busybox run-parts /system/etc/init.d

You might want to try to run that on command line as well and confirm that it works. If not, you might need to update your busybox as well.

 

Thanks!  Yeah I tried run-parts, and updating busybox.  I was thrown purely by the init.d test script I chose being itself faulty permissions wise lol.


  • 0
My Blade site - includes vanilla KANGS's of CM7. Also available: modified GB Gapps with various market versions, mini ICS Gapps for 160mb system partitions and Flash for ARMv6
CM7 Blade changelog




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users