So the problem with the camcorder on this base isn't a kernel issue, as I've tested it with leankernel AND the stock kernel, and neither work. Ran a logcats when the FC occurs
Logcat on stock kernel:
http://pastebin.com/2rZY9Xyi
Logcat on leankernel:
http://pastebin.com/CVJPb2M2
Interesting differences between the two. leankernel I get a LOT more output about camera. Stock kernel was just a few lines.
I'm looking into it. If anyone has any input please share
I am now going to run a logcat on leankernel to see if there is any difference
orkillakilla said:
So the problem with the camcorder on this base isn't a kernel issue, as I've tested it with leankernel AND the stock kernel, and neither work.
Click to expand...
Click to collapse
So I'm not sure which "stock kernel" you used but I was having the same issue using imoseyon lean kernel but everytime I put it back to stock my camcorder immediately started working again. Obviously not an issue with the base. We just need someone to make a special kernel just for this 2.11.605.19 build lol.
Is Imo's kernel based from the kernel pulled from the latest ota or is it compiled from the previous base and modified to work with the newer base?
Sent from my ADR6400L using Tapatalk 2
Any solutions? I am having the same issue and very frustrated...
no soultions that I've found yet I just flashed the stock Rom again and deal with the lag. The weirdest thing is that I can't get back to 2.11.605.9. which I loved! The stock rooted Rom just gets stuck on the splash screen. Adding to the suck factor is that a lot of the file sharing sites are no longer up so finding options is getting harder and harder.
Related
I wanted to root for a while, just looking for a rom that looks and feels stock, but has better battery and all..
well I followed
watch?v=-hPSrzRqtX4&feature=player_detailpage (cannot post link as I'm new)
and successfully got to supra rom.. well I don't like the vanilla 5 screen non sense homescreen, though I do like the crt visuals lol...
Anyways, I can't even use my wifi, it just says error, and I NEED wifi, I use it at home non-stop as I have horrible service.
Well I tried to switch to viperRom - I did the reset in bootloader, then full wipe, then cache and all that..
well, once I installed the viperRom .zip, I started my phone and its just the same as before... I can't switch roms! I know this is prolly some nooby thing I don't understand but I've been searching all night and just want to get everything working and need to sleep haha
any help GREATLY APPRECIATED
What do you mean about not being able to switch roms?
Sent from my PG86100 using Tapatalk
I figured out that I was trying to flash to viperRom using only the update
I'm now on viper, with stock kernel and still cannot get wifi to work, any ideas? Any searching turns up kernel issues, and to revert to stock.. well I'm on stock kernel
jlear3 said:
I figured out that I was trying to flash to viperRom using only the update
I'm now on viper, with stock kernel and still cannot get wifi to work, any ideas? Any searching turns up kernel issues, and to revert to stock.. well I'm on stock kernel
Click to expand...
Click to collapse
unless you're having hardware wifi issues, which the best way to determine would be through running a stock rom and stock kernel, my guess is you have a kernel and rom mismatch issue.
the way htc has their kernels compiled includes two things: kernel and modules.
the modules include a wifi module.
if you flash a kernel and then load a rom, chances are the rom might overwrite either the kernel, the kernel modules, or both.
the best way to avoid this scenario is to flash the rom first and then flash the kernel. the kernel flash will load the kernel itself and its modules. i.e. if you're on a rom you want to stay with now, flash the kernel again and then wifi should work.
hope that helps!
Thank you, o figured this out myself, but you were right lol I was using 2.3.3 roms on 2.3.4
Sent from my PG86100 using XDA App
Because I can't post in the development related threads yet I was going to ask here, I just installed TSM Resurrection yesterday and have had a few random reboots when it locks up and freezes then just reboots. Any ideas what it is, maybe kernel?
What kernel are you running? they're saying the GeeWiz 2.1 kernel is working better over there...I might try it out since I'm in the same boat as you.
I'm just using whatever kernel came with it. I haven't flashed anything else and so I was thinking about the GeeWiz kernel or I think there may have been another one mentioned I may try out if GeeWiz doesn't fix it.
EDIT: Actually it doesn't come with a kernel does it? If not I'm using whatever kernel comes with PWGB as that is what I was on before TSM.
Yeah, so you're on the PWGB packaged kernel. There's a new kernel out 10/21 that might fix the reboot issues. In the TKSGB thread, linked near the top. Hasn't been out long though, might want to wait until it has been tested well? Good luck.
I'm on the PWGB kernel and have zero issue, I wonder where this is coming from.
Skidoo03 said:
Because I can't post in the development related threads yet I was going to ask here, I just installed TSM Resurrection yesterday and have had a few random reboots when it locks up and freezes then just reboots. Any ideas what it is, maybe kernel?
Click to expand...
Click to collapse
Flash TKSGB 1021 which is the latest release. Run it for a day and see how it goes. While you're at it, download the 1006 version and leave it on your SD. If you run into problems, flash the 1006. Always wipe dalvik between kernel changes
TSM Resurrection 1.0,TKSGB10-21, XIX,ec09 radio.
i just installed stock ics on my galaxy tab, rooted it, and i installed pershoots kernel which messed my system all up, it made it really glitchy and the wifi wouldn't turn on, thank God for a nandroid backup. Is their a way to fix that or does pershoot's kernel just not install right on a stock os?
Sent from my GT-P7510 using Tapatalk
hotshot247 said:
i just installed stock ics on my galaxy tab, rooted it, and i installed pershoots kernel which messed my system all up, it made it really glitchy and the wifi wouldn't turn on, thank God for a nandroid backup. Is their a way to fix that or does pershoot's kernel just not install right on a stock os?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
I asked about this because I wanted to use pershoot's ICS kernel to resolve a screen flicker issue. It did do that, but I lost the ability to use wifi which of course makes a p7510 pretty useless.
Task mentioned (and pershoot also mentions on the DB blog) that the latest version of the kernel is really designed for use with CM ROMs and is AOSP based. It didn't work properly for me on Task's ICS and probably won't for stock either. Stock firmware with stock kernel is the way to go for now, I guess.
Thanks! Yea, the same thing happened to me about the wifi, it wouldn't work at all. Maybe they'll come out with a custom ics rom with the camera working sometime soon. I like using a rooted stock ics better than a custom honeycomb, it's just better.
Sent from my GT-P7510 using Tapatalk
djmatt604 said:
I asked about this because I wanted to use pershoot's ICS kernel to resolve a screen flicker issue. It did do that, but I lost the ability to use wifi which of course makes a p7510 pretty useless.
Task mentioned (and pershoot also mentions on the DB blog) that the latest version of the kernel is really designed for use with CM ROMs and is AOSP based. It didn't work properly for me on Task's ICS and probably won't for stock either. Stock firmware with stock kernel is the way to go for now, I guess.
Click to expand...
Click to collapse
i think the pershoots kernel is not for ICS.. correct me if i am wrong...there is A1 kernel that few ppl have used with task ICS rom
Hi,
I've been experiencing a flickering screen for a while on my Droid DNA with Viper 1.2. I've tried to re flash my rom and it hasn't helped and i'm pretty sure it's a kernel issue anyway. I initially had the cubed kernel installed and tried to go back to the stock rom using the file available here:
http://forum.xda-developers.com/showthread.php?t=2024776
That didn't do the trick so I tried installing the kernel that is listed on the viper page but it only has boot.img file listed and no modules so my Wifi isn't working. It looks like the modules are supposed to be included with the ROM but that isn't working for me for some reason. It seems to not flicker now but my Wifi isn't working.
Any idea where I can get the correct modules from?
Thanks!
You can't use kernels based on the new base l, such as cubed, on roms based on the new base, such as viper 1.2
Just flash a different custom kernel, such as beast mode
Sent from my HTC6435LVW using xda app-developers app
beastmode or cpalmer's kernels should work for you. if you want to go back to the stock one with viper 1.2, fastboot the boot.img and reflash the ROM (the modules are included in the ROM package)
Device: Maguro
ROM: crDroid build 16
I know this error is often due to 3G/4G connection in 4.3, but I had no problem with this before when I was with CarbonROM.
However when I flashed Vanir yesterday with a custom kernel, 'process.android.com.phone stopped working' kept popping up..
I tried switching ROM to crDroid which many other folks had no trouble flashing Mpokang v10 kernel with, and the same error occurred.
I tried wiping data, cache and dalvik, and reflash again but to no avail.
I'm desperate for help folks, please lend a hand. Thanks.
Try flashing again but sticking with stock kernel that comes with the rom, it has something to do with changes in the latest CM nightlies that most aosp roms are based on. Wait for your favorite kernel devs to update or repack the kernel yourself.
Sent from my OptimusX4HD using Tapatalk
spamcakes said:
Try flashing again but sticking with stock kernel that comes with the rom, it has something to do with changes in the latest CM nightlies that most aosp roms are based on. Wait for your favorite kernel devs to update or repack the kernel yourself.
Sent from my OptimusX4HD using Tapatalk
Click to expand...
Click to collapse
Funny thing is other folks are flashing custom kernels on the same build as I am on and having no troubles. any ideas?