Please go to http://inc.sodpit.com/kernels/hydra/ for all your Hydra Kernel needs.
How do i install these i have rooted my phone and have su but when i go into recovery mode and try to update via sd card it says the package is not signed?
What am i doing wrong.
Thanks
why would we not use setcpu... i use it for battery profiles?
Any possiiblity of a .33 kernel with highmem support?
Got Hydra kernel working
Do you know of any bluetooth problems? I can't seem to pair my bluetooth with my car anymore, I've got v.07 oc/v.02 uv w/ wireless-N, everything else is money, runs smooth and fast.
Thank you!
Related
[Being a new member and not being allowed to post outside links (in case of spam), I've had to "unlink" the links. Sorry for inconvenience.]
Hi all,
Rooted my Nexus One last night and have been spending hours adding all the cool stuff. I'm a noob at all this so it took lots of reading and many hours to understanding rooting, flashing, adb'ing, etc. etc.
My problem is that I cannot get wifi-tethering to co-exist with overclocking.
WIFI-TETHERING
First, I installed wifi-tethering from here:
code.google.com/p/android-wifi-tether/
Updated my kernel first using the instructions here (following "user build" option):
code.google.com/p/android-wifi-tether/wiki/NexusOneKernelUpdate
It worked, and life was good.
OVERCLOCKING
Then I tried to overclock. I saw that most instructions wee based on Cyanogen's ROM, but I noticed that I can do it w/o Cyanogen with some extra work, by basically pushing a bcm4329 file to system/lib/modules:
forums.tmonews.com/index.php?topic=12923.0
I realized that I had already done that when doing my kernel update from wifi-tethering above, so I didn't do that again.
So I just: fastboot flash zimage zImagekmobs
My overclock worked (saw with SetCPU). Life was great!
WIFI-TETHERING PROBLEM
However, then I noticed my wifi-tethering no longer worked. I recovered back to pre-overclocking and my wifi-tether now works again.
Actually, I've encountered a similar problem before, except reversed:
Yesterday, I had actually installed Cyanogen, and overclocked first (got it working). However, I could not get wifi-tethering working. I described my experience here:
nexusoneforum.net/forum/nexus-one-development-hacking/5620-can-someone-help-me-installing-wireless-tether-root.html#post50886
(basically the same problem, except I couldn't update my kernel like I did today, and wifi-tether gave me a similar message.)
(After that, I went back to stock recovery image rom thinking that Cyanogen and wifi-tether did not go well together, and started over again, as described above.)
What do you think is the problem? It looks like the zImagekmobs file I'm using (a 2Mb file, and actually not even sure where I got it from anymore cos I can't find it anywhere now) seems to be incompatible with the kernel update I had done?
I also notice this guide:
nexusonehacks.net/nexus-one-hacks/how-to-overclock-your-nexus-one/
(seems to use a different file: zImage-cm_2633.1-oc-uv )
Should I follow this guide instead?
Any of you using the stock rom w/o Cyanogen and managed to get both wifi-tethering and overclock working? If so, how did you do it?
Would be grateful for any help! Sorry if any of my questions are noob questions but I really am very new to all this!
Thanks lots!
1) The kernel and wifi module go hand-in-hand, when you update one you need to push the compatible wifi module (driver) too. Otherwise wifi wont work.
2) Make sure the OC kernel you're using has support for tethering. It may have been left out when it was built.
Hello I am having an issue with wireless tether 1.6. On any of the sprint 2.1 roms I try it freezes my phone and reboots when I stop tethering. Was wondering if there was a fix I didn't see when I looked around. It works fine until I go to stop. The only Rom I can get it to work is the my touch 3g port.
Libinjo said:
Hello I am having an issue with wireless tether 1.6. On any of the sprint 2.1 roms I try it freezes my phone and reboots when I stop tethering. Was wondering if there was a fix I didn't see when I looked around. It works fine until I go to stop. The only Rom I can get it to work is the my touch 3g port.
Click to expand...
Click to collapse
Sounds like you have bigger problems if the only rom you can get to work is the mytouch port.
When you flash a rom, go into the Wipe menu and wipe everything except battery stats.
If it still doesn't boot repartion the SDcard to Fat ONLY.
If it still doesn't boot, you have some issues somewhere.
I took care of a lot of stupid issues I was having by running the 2.1 RUU and re-rooting and flashing the rom again.
Libinjo said:
Hello I am having an issue with wireless tether 1.6. On any of the sprint 2.1 roms I try it freezes my phone and reboots when I stop tethering. Was wondering if there was a fix I didn't see when I looked around. It works fine until I go to stop. The only Rom I can get it to work is the my touch 3g port.
Click to expand...
Click to collapse
I've been having the same problem. It works just fine until I want to stop using it then it locks my phone, doesnt reboot though. It will sit there locked for 30 minutes if I let it, I have to pull the battery and reboot
There was a market update this morning though, haven't tried it yet with the new version.
Kcarpenter said:
Sounds like you have bigger problems if the only rom you can get to work is the mytouch port.
When you flash a rom, go into the Wipe menu and wipe everything except battery stats.
If it still doesn't boot repartion the SDcard to Fat ONLY.
If it still doesn't boot, you have some issues somewhere.
I took care of a lot of stupid issues I was having by running the 2.1 RUU and re-rooting and flashing the rom again.
Click to expand...
Click to collapse
I don't think he meant the mt3g is the only rom he can get to work. I think he meant mt3g is the only rom that wireless tether works properly on..
Libinjo said:
Hello I am having an issue with wireless tether 1.6. On any of the sprint 2.1 roms I try it freezes my phone and reboots when I stop tethering. Was wondering if there was a fix I didn't see when I looked around. It works fine until I go to stop. The only Rom I can get it to work is the my touch 3g port.
Click to expand...
Click to collapse
Are you running kernel .29?
I'll go even futher...are these kernels SDX kernals?
Edit: And even though it does freeze my phone if i stop it...its still a tether. and i love my phone being over clocked. so if i have to restart my phone instead of stopping the tether, its a small price to pay!
I am running the toast oc kernel. And yes I meant the tether only works on the mt3g. I ran the oc kernel on the 2.1 roms also that's actually when it started. I went from the oc mt3g Rom to aloysius 2.1 oc version and it quit working. So now I'm back on the oc mt3g Rom .
Libinjo said:
I am running the toast oc kernel. And yes I meant the tether only works on the mt3g. I ran the oc kernel on the 2.1 roms also that's actually when it started. I went from the oc mt3g Rom to aloysius 2.1 oc version and it quit working. So now I'm back on the oc mt3g Rom .
Click to expand...
Click to collapse
Well i think most ROMS run the .29 kernal while mt3g runs the .65 kernal. Sounds like its the .29 kernal.
http://code.google.com/p/android-wifi-tether/downloads/detail?name=wireless_tether_2_0_2.apk&can=2&q=
Try this one it works like a charm xP.
and of course make sure your rooted
Edit:
Ive had problems in the past with wireless tether for root. this one works like advertised and works wonders no hot phone either
Ok Tyvm ill have to recover and install it then see if it works. And the kernel says .29 on the mt3g Rom so its the same one on both.
What I usually did to solve this was close the app with a task killer and it was ok with me. It's a known issue. However the problem I'm experiencing now is that If I want to change the SSID Name or any setting in the WI-FI app it takes me to a black screen labeled SU Permission? Suggestions anyone? oh and btw no one can see my her0 =/ help!
It works fine for me. I've used it several times and never had it lock up on me when I tried to stop it. I'm running the newest Damage Control 2.09.01 and android-wifi-tether 1.6.
subcypher said:
It works fine for me. I've used it several times and never had it lock up on me when I tried to stop it. I'm running the newest Damage Control 2.09.01 and android-wifi-tether 1.6.
Click to expand...
Click to collapse
I've always had trouble with 1.6 seems to work great for some people i linked the one for 2.0.2 same version for the evo and it works great even had a battery temperature shown in the program
Well the 2.02 doesn't work either. It freezes as soon as I give it root access.
Well i think most ROMS run the .29 kernal while mt3g runs the .65 kernal. Sounds like its the .29 kernal.
Click to expand...
Click to collapse
Actually, the my touch rom uses .29 kernel, but version 65, the others are like version 83 or something. Only basic difference is no bfs or comp cache
-------------------------------------
Sent via the XDA Tapatalk App
I am using a rooted nook color happily except for one detail. Does anyone out there know how to get the VPN support to function?
I tried upgrading to 1.1 and re-rooting, and i tried installing the updated kernel. Neither seems to affect the VPN settings. I also installed wi-fi buddy and in that app I see all of the advanced VPN related settings but they are grayed out.
Dies anyone have any suggestions, I am new to the tablet, but familiar with embedded linux.
Sent from my LogicPD Zoom2 using XDA App
Sorry, that's stock v1.1 firmware. Used autonooter to root, installed Dalingren's overclock kernel with MPPE support.
Forgot all the details.
Sent from my LogicPD Zoom2 using XDA App
I have the same question. Thanks. Does the overclock kernel keep the rest stock? Do you have the link to the post, I have only seen the other overclock.
I used the latest eclair kernel Dalingrin had at the time. It looks like he just released another one with von related changes. I will try that tomorrow and see if it helps..
The kernels can be found on xda search for dalingrin kernel and it should come up
Warning, installing kernels could brick the device requiring a factory reset. I don't recommend it until the von issue is really fixed. I ran into a number of problems doing this. One to be very aware of is that CWR rom recovery does not seem to be compatible with the nookcolor at this time. If you install RomManager Do Not flash CWR or you will end up with a boot loop.
That issue made me so leery of that package that I actually used the terminal emulator and command line to mount the boot volume and manually update the kernel image and its modules.. That is the only method I can directly confirm, I did not use RomManager to flash the kernel..
If you are really intersted in keeping everything stock but the kernel, the closest way I can think of to do that would be to use an sdcard image including car/rommanager. I believe you can put the flashable kernel on the sdcard and then flash the kernel onto the stock firmware that way.
I have not tried that, but I see no reason why it wouldn't work.
That would avoid the terminal and the jiggery-pokery with mkimage and remounting volumes manually. It's actually not very hard, but it is certainly more error prone, and it's all linux command line work.
Can anyone confirm that flashing the eclair kernel on stock rom is 'safe' ??
no eclair 3-8-2011 available yet
I was hoping to test the new kernel today, but there is no eclair build yet. From the traffic on that thread it looks like they are struggling with a wi-fi issue at the moment.
OK. So I am sure I am missing something obvious here. I've done a ton of searching and reading, but I'm still at a bit of a loss.
I am running CM7 with dalingrin's OC kernel flashed over the top of it. I see tons of people overclocking to 1.0 and 1.1 GHz, yet I can't seem to options for doing so.
In CM7 settings under performance, I have options for 100-950. I can O/C to 950 and that's great, but how do people try settings above that? I tried setCPU, but it seems to cap out at 950 as well.
What am I missing?
You need to get a different kernel, such as Dalingrin's, from the android development forum.
Hi,
Looks like you didn't successfully install the overclock kernel, see:
http://forum.xda-developers.com/showthread.php?t=925451
for instructions.
I have been using the CWM install method and am running CWM7 RC4 with
the interactive governor between 300 and 1100MHz.
I usually install the updated CM7 along followed by GAPPS then the
latest OC kernel. Perhaps you installed the kernel before CM7? CM7
comes with its own kernel that overwrites existing kernel when you install CM7.
Hope this helps,
Peter
solinar said:
OK. So I am sure I am missing something obvious here. I've done a ton of searching and reading, but I'm still at a bit of a loss.
I am running CM7 with dalingrin's OC kernel flashed over the top of it. I see tons of people overclocking to 1.0 and 1.1 GHz, yet I can't seem to options for doing so.
In CM7 settings under performance, I have options for 100-950. I can O/C to 950 and that's great, but how do people try settings above that? I tried setCPU, but it seems to cap out at 950 as well.
What am I missing?
Click to expand...
Click to collapse
That is odd. I have never had any issue like that with any of the oc kernels.
My one and only question is if you a sure you flashed the right one successfully?
http://nook.handhelds.ru/dalingrin/kernels/033111/
Note that there are 2 kernels for each ROM-
one is for internally installed (emmc)
One is for sd card installations (sd)
I do not know if any errors would show up if you flashed the wrong one or if there was an error with the download.
My suggestion would be to try again and see if it works.
My response may be too basic- I don't know your knowledge level.
One thing though- IN CM7 it is best to NOT use SetCPU or other apps to change cpu speed, or at least that used to be the case. I don't use them anymore.
rogerdugans said:
Note that there are 2 kernels for each ROM-
one is for internally installed (emmc)
One is for sd card installations (sd)
Click to expand...
Click to collapse
Ding ding ding, we have a winner. I was using the SD version, as I had a bootable CWM SD that I used to get into recovery. Once I loaded the emmc onto the SD card and flashed that, they showed up.
Thanks for all of the replies.
Nice!
Glad I was able to help-
Usually I am just getting all kinds of info and help for my own stuff here. Being able to pay that back is a good thing.
Be sure not to flash a cm7 nightly after you flash the kernel. If you do, you will flash there stock cnn kernel over the oc'Ed kernel
1Enoch said:
Be sure not to flash a cm7 nightly after you flash the kernel. If you do, you will flash there stock cnn kernel over the oc'Ed kernel
Click to expand...
Click to collapse
Actually a good point-
Nothing wrong with updating to the latest nightly but you WILL go back to having the stock CM7 kernel again.
Re-flashing the oc kernel fixes that problem, of course, but you'll need to reset max cpu speed and governor again.
Hi,
Very recently i bought a Galaxy tab 8.9 wifi only (P7310), and decided to flash the 'Overcome 8.9 Series v2.3.1' ROM by alterbridge86.
Obtaining root en flashing CWM went very smooth. After full wipe + dalvik wipe I flashed the overcome rom. Still everything was fine and the rom felt very smooth. However, when I woke the tab from standby the first time, my screen was glitching so bad I had to re-boot the tab. After a reboot everything was fine again, at least until i tried to wake it up again. The same glitching occurred..
The strange thing is, during the glitching I could still open apps and everything, so it doesn't look like sleep of death issues i had with custom roms on my Hannspad.
I already tried to flash the rom again and again but every time the same issues. Someone suggested to increase the min. frequency of the cpu to 312Mhz, but this also didn't do the trick..
Right now i'm running the Galaxiansoup ICS rom without any issues, but i would really like to use the camera (for video skype) which doesn't work right now with ICS.
Does this problem sound familiar to anyone? I already searched the dev topic, but couldn't find a solution. Hope you guys can help me out!! Thnx
I added a short video to show what I mean with the glitches, hope you guys can help me out here!
I dont have any issues when use it..p7300
Try to download the file again.. Maybe a bad download make your file corrupt.
Already tried to re download (checksum verified), but unfortunately still the same issue...
Hi Ruurd V.
What Kernel do you use ?
Is it this one ?
http://forum.xda-developers.com/showthread.php?t=1344330
And did you check step
4. Install SetCPU and use to set governor to "interactive" and desired OC frequency (recommend 1.4 to start). The default governor has been set to On Demand on purpose even though it is not the recommended governor to use in SetCPU. Setting the recommended interactive governor will help SetCPU trigger the instructions to sysfs causing it to take hold. Sometimes it is finicky and a reboot can help once you have the interactive governor set with your desired frequency.
Until now I used the kernel that came with the rom. I was under the impression that the rom included the latest kernel.
I tried the kernel from the thread you posted, however the v2d version didn't work for me (no lock screen, no play store acces, home button did not work).
I just flashed the v2c version and that one works fine so far! Haven't tried messing with the cpu though, but for now I will continue using this one! Thanks for the help!
I too had some screen issues with that ROM's kernel until I installed motley's v2d kernel, so yeah, it's the default kernel.