Moved - http://forum.xda-developers.com/showthread.php?p=38551156
Please do not post in this thread.
moved - http://forum.xda-developers.com/showthread.php?p=38551156
So, any chance of a proper 4.1.2 ramdisk for cm10 users? Or can I use the stock + init.d one with cm10?
Right now, I have it scripted to remount /data and /cache, but I don't know what else I'm missing out on..
Also the download links for the stock kernels with and without ramdisk don't work
Jay Aristide said:
So, any chance of a proper 4.1.2 ramdisk for cm10 users? Or can I use the stock + init.d one with cm10?
Right now, I have it scripted to remount /data and /cache, but I don't know what else I'm missing out on..
Also the download links for the stock kernels with and without ramdisk don't work
Click to expand...
Click to collapse
No it won't work because cm10 uses their own custom ramdisk. I could look into making one for cm10 some time later. You should be alright with scripted remount of data and cache for now. Who knows when CM10 will decide to actually update it.
Metallice said:
No it won't work because cm10 uses their own custom ramdisk. I could look into making one for cm10 some time later. You should be alright with scripted remount of data and cache for now. Who knows when CM10 will decide to actually update it.
Click to expand...
Click to collapse
Well, then. Been running the 484MHz OC'd GPU version for three days. Absolutely rocks, man! Can't wait for MK+
Time to update my threads
---------- Post added at 02:41 PM ---------- Previous post was at 02:30 PM ----------
Switching to 446 GPU, now. Could use the boost on THD, but don't otherwise need a boost
Metallice said:
Introduction:
Jay Aristide asked if I could update _motley's kernel to 4.1.2 considering _motley's absence. So I decided I would go ahead and keep it updated until _motley returns.
Click to expand...
Click to collapse
Just flashed 484 and so far is running smooth. Thank you!
Thanks OP for continuing Motley work. His kernel always been my go to one. I test other kernels out but always came back to Motleys. Loved his work on Prime also.
Not sure what happened to Motley but looking forward to his return.
Also looking forward to M version. To see what kind of tweaks OP merges with motleys. Should be interesting.
demandarin said:
Thanks OP for continuing Motley work. His kernel always been my go to one. I test other kernels out but always came back to Motleys. Loved his work on Prime also.
Not sure what happened to Motley but looking forward to his return.
Also looking forward to M version. To see what kind of tweaks OP merges with motleys. Should be interesting.
Click to expand...
Click to collapse
Yep. Motley was always my steady base when trying out other kernels and building my own.
------------------------------------
Also I wouldn't call it the "M" version. M-Kernel is just shortened from Motley-Kernel, but doing this also lets it represent Metallice (pronounced like metallic with an "s" instead of a hard c BTW). Plus I think it sounds cooler .
I would stick to calling it M-Kernel, M-Kernel Plus, M-Kernel +, or the plus version. Calling it the M version makes no sense!
Can this be used on PA2.2? (Cm10 based)
Beamed from my Paranoid Google Nexus 7
tobitronics said:
Can this be used on PA2.2? (Cm10 based)
Beamed from my Paranoid Google Nexus 7
Click to expand...
Click to collapse
Yep. Running it now. No problems so far.
Sent from my Nexus 7 using xda premium
tobitronics said:
Can this be used on PA2.2? (Cm10 based)
Beamed from my Paranoid Google Nexus 7
Click to expand...
Click to collapse
Yes, but you need to remount /data and /cache yourself via init.d
Go to /data/local and create userinit.d if it's not there already and chmod it 0755
Put a file in there called 85remounts and chmod it 0755
Populate it as follows:
Code:
#/system/bin/sh
mount -o remount,discard /data /data
mount -o remount,discard /cache /cache
Make sure to leave a trailing blank line in the script.
This will remount /data and /cache with discard
Jay Aristide said:
Yes, but you need to remount /data and /cache yourself via init.d
Go to /data/local and create userinit.d if it's not there already and chmod it 0755
Put a file in there called 85remounts and chmod it 0755
Populate it as follows:
Code:
#/system/bin/sh
mount -o remount,discard /data /data
mount -o remount,discard /cache /cache
Make sure to leave a trailing blank line in the script.
This will remount /data and /cache with discard
Click to expand...
Click to collapse
Thanks. Can I also use your butter recipe in combination with this init.d file?
Beamed from my Paranoid Google Nexus 7
This kernel DOES NOT work with the latest Codename Android 3.7.0. I loaded it up and didn't get past the boatloader unlock screen. Motley is top notch and I hope CNA get up to speed in the future. Thanks for your work.
TRIM is only applicable on the 16gb version of this device, correct?
Benchmarrks, such as they are, don't seem as good with the 484 GPU. Will let it settle a bit and see what happens. Everything else is working perfectly, so maybe I'm expecting something that isn't meant to be.
atlharp said:
This kernel DOES NOT work with the latest Codename Android 3.7.0. I loaded it up and didn't get past the boatloader unlock screen. Motley is top notch and I hope CNA get up to speed in the future. Thanks for your work.
Click to expand...
Click to collapse
This. Also tried it with the latest AOKP nightly compiled by Dizzythermal and all it does is continuously show the boot animation. Haven't been able to get any 4.1.2 kernel working on a custom ROM. At least not on CNA 3.7.0 or AOKP.
atlharp said:
This kernel DOES NOT work with the latest Codename Android 3.7.0. I loaded it up and didn't get past the boatloader unlock screen. Motley is top notch and I hope CNA get up to speed in the future. Thanks for your work.
Click to expand...
Click to collapse
christianpeso said:
This. Also tried it with the latest AOKP nightly compiled by Dizzythermal and all it does is continuously show the boot animation. Haven't been able to get any 4.1.2 kernel working on a custom ROM. At least not on CNA 3.7.0 or AOKP.
Click to expand...
Click to collapse
Did you follow the steps under "before you flash" and can confirm that both rom and ramdisk are 4.1.2?
rootbrain said:
Benchmarrks, such as they are, don't seem as good with the 484 GPU. Will let it settle a bit and see what happens. Everything else is working perfectly, so maybe I'm expecting something that isn't meant to be.
Click to expand...
Click to collapse
Are you saying benchmarks on the 484 build are lower than the 416 build? or what?
smt8544 said:
TRIM is only applicable on the 16gb version of this device, correct?
Click to expand...
Click to collapse
Yes. As of 4.1.2 if you don't have the specific storage chip that needs trim the command to enable it will be ignored.
Thats the thing about it.Didnt check. Since I was running AOKP I decided to just flash the stock 4.1.2 kernel u posted. That one does not boot on aokp either.So stock 4.1.2 and your modifeid Motley kernel both do not work for me.
On 3.41 bootloader as well.
christianpeso said:
Thats the thing about it.Didnt check. Since I was running AOKP I decided to just flash the stock 4.1.2 kernel u posted. That one does not boot on aokp either.So stock 4.1.2 and your modifeid Motley kernel both do not work for me.
On 3.41 bootloader as well.
Click to expand...
Click to collapse
As explained in the OP, the stock kernel I posted will only boot on the stock ROM. Seriously one line above the download link it says not to flash with CM10, AOKP, etc.
Did you flash my kernel after you tried to boot up the stock kernel on AOKP? Or did you reflash AOKP before?
Metallice said:
As explained in the OP, the stock kernel I posted will only boot on the stock ROM. Seriously one line above the download link it says not to flash with CM10, AOKP, etc.
Did you flash my kernel after you tried to boot up the stock kernel on AOKP? Or did you reflash AOKP before trying my kernel?
Click to expand...
Click to collapse
"If you are on a stock-like 4.1.2 ROM that does not rely on a modified ramdisk (CM10, AOKP, etc.), flash one of the following zips and reboot before installing this kernel for the first time.
Stock 4.1.2 kernel - http://goo.im/devs/Metallice/Nexus7/...rnel_4.1.2.zip
Stock 4.1.2 kernel with Init.d support and insecure adb thanks to Faux123 - http://goo.im/devs/Metallice/Nexus7/...nitD_4.1.2.zip"
Maybe it is a language barrier, but your statement reads to me as in if you are running AOKP or CM10,u NEED TO flash one of the stock kernels and reboot before u flash your modified version. That is what I did. Flashed one of the stock kernels u linked and that did not boot up. Flashed your modified one to see if that would boot, and that didnt either.
Related
CAUTION: ANY CUSTOM ROM WHICH HAS A MODIFIED KERNEL, PROBABLY WILL BREAK BY USING THIS.
More than likely you will need to copy over the ramdisk. If you don't know how to do this, then wait until your ROM developer does it for you!
Who: For those who are ANXIOUS and the DEVELOPER type (more advanced users) who want to load the new kernel which comes with the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip released today.
If you're not an advanced user or the developer type, please wait for the builder of the ROM you're using to release their own update!
What: I've pulled the boot.img from the firmware.zip inside of the OTA_Supersonic_1.47.651.1-1.32.651.6_release.zip and put it into this update.zip.
Tech Details: This update.zip copies flash_image and boot.img to /system/bin and /system, flashes the new boot.img and deletes boot.img from /system. My first time creating this type of update.zip on the EVO!
Advantages:
npace said:
Here's a rundown of the issues that I tested for fixes:
1. Touch input lag -- fixed -- tried with multitouch visualizer 2
2. Improperly grounded touchscreen -- fixed -- tried on multiple surfaces
Click to expand...
Click to collapse
http://www.joeyconway.me/evo/stock/jk-stock-OTA-1.47.651.1-kernel-signed.zip - WiFi will not work until the System Software portion of the OTA update is loaded
I got my retard helmet on and I'm ready to test this baby on Avalaunch's Froyo ROM.
Sorry for the noob question, I'm new to android. Is this for stock rooted roms? I am running stock evo rom rooted and nand unlocked, so is this essentially an update for rooted users running stock rom? And will I have to update the radio with a seperate flash? Thanks for your help, and everyone's hard work!
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
snandlal said:
I'm using Jk-original 1.0.8 odex and I flashed the update image...giving error..."Can't chown/mod /system/flash_image (No such file or directory) Failure at line 3:set_perm 0 0 0755 SYSTEM:flash_image Installation aborted." I do have "flash_image" in /system/bin.? Also, followed Joey's script for that update.zip in adb manually and didn't get any error, I just don't know how to verify the install. Will it show in build???
Click to expand...
Click to collapse
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Any comments from people that have this applied (and working with full root)?
Shane Pitman said:
Re-download. He had to make a change and just re-uploaded it, I just downloaded and applied it without a problem, after having the same error you did with the first file.
Click to expand...
Click to collapse
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
That worked Thanx
Kernel's working just fine with Avalaunch's Froyo ROM.
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
I've got most of the Sprint/HTC crap removed, rooted, nand unlocked, custom recovery, running joeykrim-original-1.0.8 deodex rom, and this worked just fine.
lafrad said:
Any comments from people that have this applied (and working with full root)?
Click to expand...
Click to collapse
this ONLY updates the kernel and will not effect root access.
Kiraly said:
Do you have any of the Sprint and/or HTC apps removed? I removed a bunch of that bloatware and I read that some people couldn't get the update to install. Wondering if OP fixed that in this kernel.
Click to expand...
Click to collapse
this is ONLY the kernel. has nothing to do with ANYTHING in /system including bloatware/apps.
npace said:
joeykrim,
Have you used Koush's anykernel? I think you can make a update.zip that works with any kernel..
It just hasn't worked properly for me yet...
Here's link:
http://github.com/koush/AnyKernel
It should extract the ramdisk and everything from your current kernel and just replace the zImage and then flashes boot.img.
Click to expand...
Click to collapse
nice. i remember seeing this once but had forgot about it.
i prob wont delve into this yet cuz i haven't modified the ramdisk at all, but this is encouraging!
ill prob wait till we get some htc source code for the kernel, and then dive into customizing the kernel and the ramdisk or if i get bored and wanna customize my ROM with this stock kernel and custom ramdisk!
this is def good to know! thanks for the link!
Did anyone else have an issue with 4G stuck saying its turning on? Worked fin again after.restoring a backup.
Yep... 4th got stuck for me. Camera ad ADW also crashed a bunch too
Sent from my PC36100 using Tapatalk
Hello FB, will you help me.
I'm not sure which of these kernels is stable, except the v0.0.2d with CWM3.
From your post:
sms-T959V-KJ6-v0.1.1-rc2.zip
From bhundven post:
Subtly Modified Stock for T959V KJ6 v0.1.1-rc1+: sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip {same as #1 ? (above rc1+)}
sms-T959V-KJ6-v0.1.0-unsigned-update.zip
Besides the /system unmount issue, what is the advantage of CWM5 vs CWM3?
Thank you
Fb's latest kernel is the most stable kernel as off now.
i would say go for fb's kernel
fb modified or i should say upgraded bhudven kernel...
and it got team acid splash screen which is a very nice touch
bark777 said:
Hello FB, will you help me.
I'm not sure which of these kernels is stable, except the v0.0.2d with CWM3.
From your post:
sms-T959V-KJ6-v0.1.1-rc2.zip
From bhundven post:
Subtly Modified Stock for T959V KJ6 v0.1.1-rc1+: sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip
sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip {same as #1 ? (above rc1+)}
sms-T959V-KJ6-v0.1.0-unsigned-update.zip
Besides the /system unmount issue, what is the advantage of CWM5 vs CWM3?
Thank you
Click to expand...
Click to collapse
I got 66 hours with no reboots on RC2.
The main differences between CWM 3 and 5 are that CWM 5 doesn't have trouble making and restoring backups (made in CWM 5), the ability to have ADB in recovery and the option to reboot to download.
Additionally, it has most of the changes made after Dec 7, 2011:
https://github.com/teamacid/android_kernel_galaxys4g/commits/sgs4g-aosp
FBis251 said:
I got 66 hours with no reboots on RC2.
The main differences between CWM 3 and 5 are that CWM 5 doesn't have trouble making and restoring backups (made in CWM 5), the ability to have ADB in recovery and the option to reboot to download.
Additionally, it has most of the changes made after Dec 7, 2011:
Click to expand...
Click to collapse
Thank you JMW and FB.
Is this the normal message state?
CWM-based VooDoo LagFix Recovery v5.0.2.7
Voodoo lagfix is actually: disabled
......................next boot: enabled
Option:
/system lagfix conversion: yes
...................debug mode: no
I show this from a terminal session:
/system ext4 rw,
/cache ext4 rw
/data ext4 rw
I tried to disable VooDoo but it does not disable, do I need to start with VooDoo disabled from version 0.0.2d?
I went back to v0.0.2d and disabled VooDoo, then flashed v0.1.1 rc2. The conversion took place per the voice. But it still shows that it is disabled as above.
Bark, read the OP under Features
http://forum.xda-developers.com/showthread.php?t=1513287
The RC2 version of the kernel forces you onto ext4 (lagfix) since there's no real reason why you should stay on RFS (lagfix disabled).
Not sure why that was confusing to me, but I really appreciate your quick response. Thank you for straightening me out!
Whoops! I heard my phone rebooting as it sat on the table. I guess I'll go back to v0.0.2d.
I'm running stock GB with AS 14.1 and Tegrak UV/OC to 1.2.
I have been running this kernel without any problems whatsoever.
I would check your UV/OC values to see if that is causing the reboot.
FBis251 said:
The main differences between CWM 3 and 5 are that CWM 5 doesn't have trouble making and restoring backups (made in CWM 5), the ability to have ADB in recovery and the option to reboot to download.[/url]
Click to expand...
Click to collapse
jigglynuts said:
I have been running this kernel without any problems whatsoever.
I would check your UV/OC values to see if that is causing the reboot.
Click to expand...
Click to collapse
Hello JN,
I'm going to chose oc/uv over the latest version of this kernel. I checked my settings and they are as suggested. I guess if the v0.0.2d kernel can tolerate my OC/UV settings and not reboot then I would deem it a tad more stable.
Since I can use the CWM5 version at will, I will use it to do backups. But I will use the v0.0.2d version daily as the OC'ing does make this device snappier. I don't understand the "ADB in recovery" part of the explanation, got to do some reading.
Do you overclock your phone, I would be interested in the setting you use.
Thanks!
my phone rebooted once after flashing the latest kernel.
after half a month no problems yet
Sent from my SGH-T959V using xda premium
JuLes' MostWanted said:
my phone rebooted once after flashing the latest kernel.
after half a month no problems yet
Sent from my SGH-T959V using xda premium
Click to expand...
Click to collapse
Hello JMW,
That is interesting. I wonder if after some time the kernel adjusts something and then calls for a reboot.
I will go back and run the latest again and then give it some time based upon your input.
Thank you.
Common causes for phone to reboot is the voltage governor is too low or just something wrong with it
just for the record Bhudven and Fb nailed the values ;-)
JuLes' MostWanted said:
Common causes for phone to reboot is the voltage governor is too low or just something wrong with it
Click to expand...
Click to collapse
The voltage/cpuspeed 's have not changed between v0.0.2d and latest.
The thing is, I only know of a few people that have any problems and no one has given me or fb any kind of logs to prove there is a problem.
No logs, nothing to fix.
JuLes' MostWanted said:
just for the record Bhudven and Fb nailed the values ;-)
Click to expand...
Click to collapse
The values have always been nailed. The have not changed.
The only problems I have with this kernel is going from BML (fsr/rfs/ext4) to MTD then back to BML.
I try using heimdall and odin and the only way for me to revert back to bml is using the 'eraseall' command at the sbl prompt (which isn't easy to get to if you don't have the right tools or know what your doing) then one-click with bootloaders. Something wrong with the erase-block-size/page-size with mtd vs. bml. idk, still trying to figure that one out.
too bad i cannot provide logs.
as far as observe it always reboot once after i install the latest from fb....
note: before reboot, laggy
but all runs great after that reboot
i dunno why this happens but I think it a great thing
i just wanna make people aware of it.
damn this kernel diving must be mind boggling thats why I will stick to theme
bhundven said:
The voltage/cpuspeed 's have not changed between v0.0.2d and latest.
The thing is, I only know of a few people that have any problems and no one has given me or fb any kind of logs to prove there is a problem.
No logs, nothing to fix.
The values have always been nailed. The have not changed.
The only problems I have with this kernel is going from BML (fsr/rfs/ext4) to MTD then back to BML.
I try using heimdall and odin and the only way for me to revert back to bml is using the 'eraseall' command at the sbl prompt (which isn't easy to get to if you don't have the right tools or know what your doing) then one-click with bootloaders. Something wrong with the erase-block-size/page-size with mtd vs. bml. idk, still trying to figure that one out.
Click to expand...
Click to collapse
Thank you for your work, but can you please address why the kernels you released since you disabled Deep Idle and DMA Engines have random reboot issues. Many many people who have reverted back to the 2d kernel no longer have these issues.
I'm fairly sure it's because of init.d scripts messing with the CPU settings and other kernel settings.
I'm going to write a "stability" build of RC2 that just backs up your init.d on boot and wipes the directory. Bet you'll get rid of your reboots until you start messing with Tegrak and OC/UC/UV settings.
bhundven said:
No logs, nothing to fix.
Click to expand...
Click to collapse
I am so willing to submit logs, if I only knew how. I have read thousands of posts on this site and have learned a ton about my phone and how to upgrade it. But try as I may and I have tried, I cannot find a good reference document on collecting logs. I heard some people say I will run a logcat and I have downloaded log collector from the market.
I used to work in the field service arena and it was common that our customers would collect error data for us to use to find their problems, but they would always collect the wrong things until we gave them a list of what we needed and how to collect it. So I am sure that it is my noob searching that has made it difficult for me to throw a lasso around this issue, but if someone would direct me to a thread or give instructions I am sure it would help me and I think maybe some others too.
I would also like to thank the devs that replied in this thread. I'm sure there are better things to do then reply again to the reboot issues some are experiencing. I truly appreciate your time, offerings and effort.
Thx
FBis251 said:
I'm fairly sure it's because of init.d scripts messing with the CPU settings and other kernel settings.
Click to expand...
Click to collapse
I have no init scripts, no init.d directory, & do not oc/UV. I have the reboot issue. Bryan looked @ a logcat I took a while back but it held no clues. I'll see if I can find the time to install a kernel past 2d and troubleshoot.
Sent from my SGH-T959V using xda premium
Well if you DO wind up testing this, we needs these files:
hampsterblade said:
I'm currently looking through
/proc/last_kmsg
/data/tombstones/
/data/system/dropbox/
I just found something suspicious in system server wtf about the time the phone shut down
.
Here are the logs if anyone wants too look over.
Click to expand...
Click to collapse
Hi all,
here's the official ClockWork Mod recovery, built from the Gingerbread branch.
Disclaimer: this piece of software is not for the unexperienced and might bring you in a situation you can't resolve yourself. So don't use it if you fear the potential danger of bricking your device. I am responsible for nothing related to this piece of software and therefore won't help. If you decide to use it anyway you agree to be ultimately responsible for all consequences that may occur. So you have been warned !
I don't use ODIN, so I only provide the images file.
If someone want to make the Odin files, just reply in this post with the download link so I can update this post.
recovery-clockwork-5.0.2.8-2.zip
Install through adb:
Code:
$ bsdtar xfv recovery-clockwork-5.0.2.8-1.zip
$ adb push recovery-clockwork-5.0.2.8-1.img /sdcard/
$ adb shell
# dd if=/sdcard/recovery-clockwork-5.0.2.8-1.img of=/dev/block/mmcblk0p13
Odin package by broodplank1337
recovery-clockwork-5.0.2.8-2.tar.md5
Changelog said:
5.0.2.8-2:
* Mount /dev/block/mmcblk0p28 as /emmc
* Mount /dev/block/mmcblk1p1 as /sdcard
5.0.2.8-1:
* First
Click to expand...
Click to collapse
Suggestions are welcome.
Cheers!
may i know what's the difference this and feamod?
It's working, but I'll keep Feamod 1.4 since there is no difference at all except the logo
annoymous1234 said:
may i know what's the difference this and feamod?
Click to expand...
Click to collapse
Sure, from the FeaMod thread:
FeaCore Phoenix includes:
-BFQ I/O scheduler 2 r1
-SIO I/O scheduler
-OC up to 1.8 GHz
-smartassV2 governor (ondemand is default)
-JFS and CIFS support
-tun included
-bootanimation support
-new boot sound
- I8150 GPU librarys
-cleancache
Click to expand...
Click to collapse
This one is the upstream vanilla clockworkmod: https://github.com/CyanogenMod/android_bootable_recovery
I don't apply any patch.
broodplank1337 said:
It's working, but I'll keep Feamod 1.4 since there is no difference at all except the logo
Click to expand...
Click to collapse
This is vanilla. If you install this _after_ the feamod recovery you'll notice no change because the FeaMod installs the GPU driver and a custom boot, and this recovery do not remove them.
bashlnx said:
Sure, from the FeaMod thread:
This one is the upstream vanilla clockworkmod: https://github.com/CyanogenMod/android_bootable_recovery
I don't apply any patch.
Click to expand...
Click to collapse
That list is a list of Kernel features, the recovery can't have those tweaks inside,
Feacore Phoenix = Kernel
Feamod = Recovery
broodplank1337 said:
That list is a list of Kernel features, the recovery can't have those tweaks inside,
Feacore Phoenix = Kernel
Feamod = Recovery
Click to expand...
Click to collapse
Right, my fault. I misunderstood things.
The differences between this and the FeaMod recovery are these:
https://github.com/manveru0/FeaMod-Recovery/commits/gingerbread/
Every manveru0 commit (like replacing sd-ext by sdcard or changing some message) isn't included in the official one. Also, this one has some upstream change that aren't included in the FeaMod recovery because manveru0 left.
Hey, thank you for this. Finally someone is working again on the CWM recovery.
I just want to ask you something about a problem which I encountered during the development of my ROM Crybernation with AROMA-INSTALLER.
Its about the colors in CWM.
The colors on the screen seems to be right, but when I take a sreenshot in CWM with DDMS I get a red picture.
In AROMA there is a blue tint in CWM. But the screenshots have the correct colors. ( See attachments below)
So amarullz the developer of AROMA-INSTALLER said that there is something wrong with the framebuffer.
I'm not that familiar with this but perhaps you have an idea what could be wrong. So you think you can solve this problem?
Also could you delete the additional "No's", like manveru0 did it?
Thank's Man Nice work
I didn't think you would do it so fast
crybert said:
I'm not that familiar with this but perhaps you have an idea what could be wrong. So you think you can solve this problem?
Click to expand...
Click to collapse
I've no time right now to play with the framebuffer, but I'll let you know if I find something weird.
crybert said:
Also could you delete the additional "No's", like manveru0 did it?
Click to expand...
Click to collapse
No, sorry but I wanna keep it vanilla
tomsteel1 said:
Hey, Does this support "Rom Mananger" then?
Anyway, Thanks for carrying on CWM for i9001. Nice to see another dev working for our device, Too bad manveru0 left.
Anyway thanks again!
Click to expand...
Click to collapse
For some reason this doesn't work with ROM Manager yet. I asked some CWM dev, and they said ROM Manager works only if the ClockworkMod is installed using it.
I'll try to play a bit with it.
I suppose "newer" FeaMod backups can still be restored with this "older" version?
It detects my internal sdcard as the external and vice versa
nail16 said:
It detects my internal sdcard as the external and vice versa
Click to expand...
Click to collapse
Looking at the CWM code, the /emmc is called "the internal card".
I googled a bit, and the behavior is right.
thanks
odin http://www.mediafire.com/file/du42yxqswg5a3vl/recovery.tar.md5
still i didn't try it
good luck
mazen912 said:
thanks
odin http://www.mediafire.com/file/du42yxqswg5a3vl/recovery.tar.md5
still i didn't try it
good luck
Click to expand...
Click to collapse
with me Odin crashes when add the file as one package, somebody else have this problem??
wintel_mac said:
I suppose "newer" FeaMod backups can still be restored with this "older" version?
Click to expand...
Click to collapse
That never work... you have to set a backup BACK with the same cwm versios as you made the backup.
Someone correct me if i'm wrong....?
Here is a fixed odin version:
http://www.mediafire.com/download.php?z84wnnn55tihqmq
broodplank1337 said:
Here is a fixed odin version:
http://www.mediafire.com/download.php?z84wnnn55tihqmq
Click to expand...
Click to collapse
thx you your fixed version works fine!!
---------- Post added at 06:07 PM ---------- Previous post was at 05:57 PM ----------
Sh0rty007 said:
That never work... you have to set a backup BACK with the same cwm versios as you made the backup.
Someone correct me if i'm wrong....?
Click to expand...
Click to collapse
think your right, with feamod i could not restore data backed up with 1.4 and do a restore with 1.2. flashing back to 1.4 and there where no problems, so i think it will be the same for cwm
sorry guys i made it hurry
bashlnx said:
Looking at the CWM code, the /emmc is called "the internal card".
I googled a bit, and the behavior is right.
Click to expand...
Click to collapse
in cwm emmc is external storage, i find that behavior strange
Hey there guys,
I found these drivers http://forum.xda-developers.com/showthread.php?t=2238348, but they are not suitable ATM.
Sorry for making you all happy with something that doesn't work. Let's make a good discussion about how we can instead make all this work.
steyn_e said:
Hey there guys,
I found these drivers http://forum.xda-developers.com/showthread.php?t=2238348 for our Sensations, which solves the graphical glitches in Google Maps 7. Please all use these in your ROM's. I also found an even newer version, but that is not compatible with the Linux kernel we are currently using (3.0.x).
The build number for these are [JB_VANILLA.04.02.02.060.053]. These need a 3.4.x kernel.
I hope you can all enjoy these! The package can be downloaded here.
You can simply be flash it through 4ext, afterwards clear dalvik+cache.
Have fun!
Click to expand...
Click to collapse
If they need a 3.4.x kernel you need to state clearly that they are for JB sense. None of the aosp jb roms here use a 3.4.x kernel.
sjknight413 said:
If they need a 3.4.x kernel you need to state clearly that they are for JB sense. None of the aosp jb roms here use a 3.4.x kernel.
Click to expand...
Click to collapse
Only the latter ones (which I didn't include a link for) are for 3.4.x. The ones linked work for 3.0.x, and I am using them now on CM10.2. They will also work on CM10.1, and maybe on CM10 if the kernel is 3.0.x or over. I'll try to find a link for the other ones for people using a Sense based ROM.
Okay, I made myself clear. The first download is for kernel 3.0.x (tested on CM10.2 and working), the second download is for kernel 3.4.x (and maybe further), but I cannot test that as I am not using a Sense based ROM. It is sourced directly from Qualcomm.
Now I'm thinking of it: we should probably make a list of compatible kernels for the different drivers. I'm using the Albinoman 3.0.100 kernel.
Sad to say, but I've still got glitches.. Installed with 4Ext and wiped cache + dalvik cache.
Albinoman's 4.3.1 26-10 with his kernel.
84Guzz said:
Sad to say, but I've still got glitches.. Installed with 4Ext and wiped cache + dalvik cache.
Albinoman's 4.3.1 26-10 with his kernel.
Click to expand...
Click to collapse
You did install the upper one? Which version of Maps are you using?
Also, what is the Linux kernel version of your rom (in device info)?
Let's make this work...
steyn_e said:
You did install the upper one? Which version of Maps are you using?
Also, what is the Linux kernel version of your rom (in device info)?
Let's make this work...
Click to expand...
Click to collapse
Yes, I got the one for a 3.0 kernel
Maps: 7.3.0
Kernel version: 3.0.100
The glitches are not as bad as they used to be, but try drawing the notification bar. Also the dialog to turn on GPS when starting navigation will flicker.
Edit: Press the "go to my location" button (top right) it will prompt a dialog to turn on GPS, which will flicker between opaque and transparent
84Guzz said:
Yes, I got the one for a 3.0 kernel
Maps: 7.3.0
Kernel version: 3.0.100
The glitches are not as bad as they used to be, but try drawing the notification bar. Also the dialog to turn on GPS when starting navigation will flicker.
Edit: Press the "go to my location" button (top right) it will prompt a dialog to turn on GPS, which will flicker between opaque and transparent
Click to expand...
Click to collapse
Tried it. It does the same with me once, but the second time it didn't. And just moving through maps doesn't glitch anymore.
steyn_e said:
Tried it. It does the same with me once, but the second time it didn't. And just moving through maps doesn't glitch anymore.
Click to expand...
Click to collapse
Do you mean you tried the notification bar? This keeps glitching with me.
Moving trough maps is OK indeed.
I've now modded the 2nd set of drivers to install on my device, let's see how this goes.
A few things:
1. These libs don't boot. If they "booted" for you then that's because the installer never installed them. The line in the updater script to mount /system makes it try and mount system as a yaffs2 partition, but we don't use yaffs2 we use ext4, so /system is never actually mounted. I modified the installer so it actually installs the libs and they do not boot. Some more proof of this is that the zip flashes very quickly, when it should actually take about 10-15 seconds to flash. They probably require a kernel with ION and a GPU driver from a 3.4 kernel.
2. Our Maps glitches are not being caused by our Adreno libs. Read my post HERE
3. The package for 3.4 kernels is not a flashable zip.
4. The package for 3.4 kernels does not necessarily require a 3.4 kernel (I have booted them on a 3.0 kernel); all they require is a kernel with a GPU driver from a 3.4 kernel and ION.
android1234567 said:
A few things:
1. These libs don't boot. If they "booted" for you then that's because the installer never installed them. The line in the updater script to mount /system makes it try and mount system as a yaffs2 partition, but we don't use yaffs2 we use ext4, so /system is never actually mounted. I modified the installer so it actually installs the libs and they do not boot. Some more proof of this is that the zip flashes very quickly, when it should actually take about 10-15 seconds to flash. They probably require a kernel with ION and a GPU driver from a 3.4 kernel.
2. Our Maps glitches are not being caused by our Adreno libs. Read my post HERE
3. The package for 3.4 kernels is not a flashable zip.
4. The package for 3.4 kernels does not necessarily require a 3.4 kernel (I have booted them on a 3.0 kernel); all they require is a kernel with a GPU driver from a 3.4 kernel and ION.
Click to expand...
Click to collapse
Yes, I've noticed the META-INF was missing in the 2nd one. However, it did do something. Maps is not even nearly as glitchy as it was. It only glitches now if something pops in front (like that "do you want to enable GPS" or the notification bar).
Our Adreno drivers want ION, and the camera wants PMEM, however is it even close to possible to make the camera libs work with ION?
steyn_e said:
Yes, I've noticed the META-INF was missing in the 2nd one. However, it did do something. Maps is not even nearly as glitchy as it was. It only glitches now if something pops in front (like that "do you want to enable GPS" or the notification bar).
As it is nearly impossible to rewrite the Adreno libs to use PMEM, is it even close to possible to make the camera libs work with ION?
Click to expand...
Click to collapse
Sebastian modified VilleC2 camera libs to work with our camera sensor and rewrote the camera driver, but Sebastian is on a whole different level from me
Also, the first package did absolutely nothing. I tested it and nothing was flashed to /system because the installer couldn't mount /system (because it's trying to mount /system as yaffs2). My Adreno version did not change, and when I fixed the package to install correctly, my phone did not boot (as they probably require ION and a 3.4 GPU driver; my kernel has a 3.4 GPU driver but ION is still necessary to get them booting). There's no such thing as in between with these Maps glitches; the glitches are either there or they're not.
android1234567 said:
Sebastian modified VilleC2 camera libs to work with our camera sensor and rewrote the camera driver, but Sebastian is on a whole different level from me
Also, the first package did absolutely nothing. I tested it and nothing was flashed to /system because the installer couldn't mount /system (because it's trying to mount /system as yaffs2). My Adreno version did not change, and when I fixed the package to install correctly, my phone did not boot (as they probably require ION and a 3.4 GPU driver; my kernel has a 3.4 GPU driver but ION is still necessary to get them booting). There's no such thing as in between with these Maps glitches; the glitches are either there or they're not.
Click to expand...
Click to collapse
So I've noticed. Isn't Sebastian's kernel ION?
steyn_e said:
So I've noticed. Isn't Sebastian's kernel ION?
Click to expand...
Click to collapse
Yes. Sebastian's kernel satisfies all the requirements to use these libs (ION and 3.4 GPU driver) so they should boot on any ROM using his kernel.
android1234567 said:
Yes. Sebastian's kernel satisfies all the requirements to use these libs (ION and 3.4 GPU driver) so they should boot on any ROM using his kernel.
Click to expand...
Click to collapse
Now the final thing is obviously to make that kernel work with your ROM. Possible at all?
steyn_e said:
Now the final thing is obviously to make that kernel work with your ROM. Possible at all?
Click to expand...
Click to collapse
Even if I managed to get all the basic things working (which I don't think I can do), getting the camera working would be a problem and we'd probably be forced to use PMEM on the whole kernel (which would defeat the purpose of a 3.4 kernel).
android1234567 said:
Even if I managed to get all the basic things working (which I don't think I can do), getting the camera working would be a problem and we'd probably be forced to use PMEM on the whole kernel (which would defeat the purpose of a 3.4 kernel).
Click to expand...
Click to collapse
That means there is no hope for getting every single thing to work on our phones?
steyn_e said:
That means there is no hope for getting every single thing to work on our phones?
Click to expand...
Click to collapse
Man, we are running android 4.3 on phone which was officialy updated to 4.0 only. That is normal that some thing arent working
Wysłane z mojego HTC Sensation przy użyciu Tapatalk 4
szotaa said:
Man, we are running android 4.3 on phone which was officialy updated to 4.0 only. That is normal that some thing arent working
Wysłane z mojego HTC Sensation przy użyciu Tapatalk 4
Click to expand...
Click to collapse
That doesn't mean we shouldn't try. I'd love to learn more about this stuff. And if someone can teach me, we Sensation users will have another driven Devver. I won't be able to do this on my own however, as it has been too long since I've last been devving for a Phone (that was my Touch Pro 2).
I've spent some time trying to tweak and tune a kernel for the Nook HD+ ovation device.
This is the result so far:
http://www.mediafire.com/download/wwjq7jp1ppbohqb/cm-10.1.3-ovation_OC6.zip
It's packaged as a complete rom to avoid kernel module difficulties. The rom is completely stock minus the boot animation, kernel and kernel modules. Thanks to everyone who has made this possible.
Both the kernel and PVR module have been compiled with linaro.
The kernel has numerous performance and stability enhancements over any other kernel to date.
Great Work. Thank you very much!
Hi Jon, I upgraded to OC6 but it doesn't works so good like OC4? ( i did a clean install) i added last_kmsg may you can find why my device start rebooting again :<
wahidx said:
Hi Jon, I upgraded to OC6 but it doesn't works so good like OC4? ( i did a clean install) i added last_kmsg may you can find why my device start rebooting again :<
Click to expand...
Click to collapse
I appreciate the last_kmsg. I apologize for using everyone as beta testers, but this demonstrates why it is a good idea- because I have been running OC5 for a few days without a single hiccup at all. I am actually surprised OC4 did so well for you. OC4 was also the first version to sport a new pvr module.
One thing I had been noticing before being able to compile my own pvr was that I could have one kernel play well with the stock pvr, and I could have a kernel right after that not play well with the pvr at all. This was my major motivation to be able to compile my own pvr so that it could match kernel space every time.
Ok, with that said, I compiled the pvr against OC4, and didn't bother updating it against any subsequent kernels. I probably should have known better, but it was working well enough for me.
Your error looks suspiciously like a missmatch between the pvr and kernel space. So if you want to try this update:
http://www.mediafire.com/download/qyaqt9mukrqbdvj/cm-10.1.3-ovation_OC7.zip
and let me know if it works any better. I made sure to compile the pvr to specifically match the kernel.
Also, when I compiled the pvr before, I used PLATFORM_VERSION=4.1. I used this as an excuse to try
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabihf- BUILD=release TARGET_SGX=544sc PLATFORM_VERSION=4.2.2
I don't know if it makes a difference or not.
Another thing I noticed you have slightly different hardware than I do. You have elpida ram versus samsung which is what I have.
I modified samsung ram timings to be slightly faster, but the other ram types were left at stock speeds. I may eventually try to clock the elpida ram the same as I have done with samsung, that may or may not make a difference. This may affect pvr performance as well. (It seems your pvr was a little slow bringing up power a few times). Then again, it could be my pvr source (although it works flawless for me, it may be hardware differences- I dunno.
thx for fast replay man,
i will try this release and give you feedbacks.
i have the bad feeling that something is wrong with my hardware. can be the only explanation, why my device reboot so often with CM10.2, CM11 and your OC6 release :/
//EDIT
actually i had just 1 reboot after some hour OC6 using, i will try OC6 for the next 2-3 days, maybe it was just a bad accident. after that i will try your OC7
regards
//EDIT #2
OC6 Test
after 2 days more, just 2 freez-->reboots (check last_kmsg) but still better than CM 10.2 and 11 on my device
Jon Lee said:
I've spent some time trying to tweak and tune a kernel for the Nook HD+ ovation device.
This is the result so far:
http://www.mediafire.com/download/wwjq7jp1ppbohqb/cm-10.1.3-ovation_OC6.zip
<snip>
The kernel has numerous performance and stability enhancements over any other kernel to date.
Click to expand...
Click to collapse
Hi Jon:
Hey, since we're asking for the moon, and since you're making THE oc kernel, any chance you can implement f2fs? I've got a Gal Tab 2 and an xda developer over there has a page about what he's done to get f2fs to work. Mostly it seems to require a .101 kernel. And he was kind to update TWRP so it would support f2fs. (I think to keep it from automatically formatting in ext4.) And he even wrote some zips to format /data, /system and /cache to f2fs.
My Tab 2 doesn't benchmark any faster but it sure is faster with f2fs. I image the HD+ would be faster too.
I'm new to flashing the Nook HD+. I was previously using the SDcard booting option for CM 10.1, but I would really like to get Nook off of this completely. Where do I start? I downloaded the ROM, and I have a boot IMG from another ROM on an SD card that takes me to recovery. Where do I put this ROM and how do I overwrite the actual Nook ROM?
install fails using verygreens internal recovery. is there a trick to installing this?
So I was able to flash the ROM, but I cannot upgrade. Everytime it tries to upgrade to 10.2 it reboots, I see the Nook logo, and then I get a Nook error screen. Does that mean I don't have the right CWM installed? If that's the case, how do I install the correct CWM?
SynGamer said:
So I was able to flash the ROM, but I cannot upgrade. Everytime it tries to upgrade to 10.2 it reboots, I see the Nook logo, and then I get a Nook error screen. Does that mean I don't have the right CWM installed? If that's the case, how do I install the correct CWM?
Click to expand...
Click to collapse
Yes, that means you still have stock recovery installed. You need to go to my HD/HD+ CWM thread linked in my signature and download and install the 6036 CWM from item 5 there.
Edit: but you know if you upgrade to CM10.2 you lose this kernel, right?
Sent from my BN NookHD+ using XDA Premium HD app
---------- Post added at 04:42 PM ---------- Previous post was at 04:41 PM ----------
smatticus said:
install fails using verygreens internal recovery. is there a trick to installing this?
Click to expand...
Click to collapse
It depends on which verygreen internal recovery you are using. You need to have version 6036 or older to flash it. You can get one per my previous post.
Sent from my BN NookHD+ using XDA Premium HD app
Great Work! I used OC7, it now worked on 1620Mhz and I feel faster. Is it possible to run on some higher frequency like 1800Mhz?
i6941 said:
Great Work! I used OC7, it now worked on 1620Mhz and I feel faster. Is it possible to run on some higher frequency like 1800Mhz?
Click to expand...
Click to collapse
Does this work for CM11?
andtron said:
Does this work for CM11?
Click to expand...
Click to collapse
I think the answer is no, when you flash cm11 the OC kernel will be overwrite. But I didn't try this.
As the thread title indicates, this kernel is only for 10.1.3.
it says there is a new update from the option -- about menu...should I?
Jon Lee said:
http://www.mediafire.com/download/qyaqt9mukrqbdvj/cm-10.1.3-ovation_OC7.zip
Click to expand...
Click to collapse
I couldn't find a tabletUI patch to match the final cm10.1.3 stable so here's one for anyone else downgrading like me.
Here's another experimental kernel update.
http://www.mediafire.com/download/1lkesmn6si6hd1e/ovation-kernel-cm10.1.3_v5.zip
I'm using it on OC7 pvr without issue (?).
1) reduced elpida and hynix ram timings.
2) updated vivante gc320 gcx 2d composition drivers to gitorious.org/gcx staging/alexei-dev. These are significantly different from original. (FWIW Staging/master branch threw memory map bverror 2 logs, but otherwise worked fine).
3) reduced dsp carveout memory. Increased system memory.
If needed, here is just the plain kernel for OC7, should anyone wish to revert back to that for any reason. (So as to not have to flash the entire ROM).
http://www.mediafire.com/download/z4r59n8dasxgz93/ovation-kernel-cm10.1.3_v4.zip
Kernel source for OC7
http://www.mediafire.com/download/6rngvee6x471cc3/android_kernel_bn_omap-cm-10.1_v3.tar.gz
So oc7 has been very unstable for me. I started with a completely clean slate, but it's frequently rebooting and not waking up from sleep. I may remember having these same problems when I was regularly using cm10.1 last year.
I've gone back to cm10.2.1. You should consider developing your kernel for that one.
Ya'know, I make these for me first and foremost. They reflect what I'm working on, trying to fix or improve the performance of my device.
Each one is different, some have worked better than others, but I notice an overall improvement from the original kernel. It is substantially different than any other nook kernel out there and works the best for me.
Here's the last. I think it works well. Made some additional changes to mmc/sdio to try and improve stability with wl12xx.
Source (which includes the vivante driver change from before):
http://www.mediafire.com/download/v4ihnr46eo9ap4d/android_kernel_bn_omap-cm-10.1_v4.tar.gz
Flashable kernel
http://www.mediafire.com/download/c9bsziswrf7y0e4/ovation-kernel-cm10.1.3_v6.zip
I like 10.3.1 but it has two downsides. 1) No automatic TRIM. 2) Unsafe manual TRIM because of Samsung MAG2GA EMMC bug.
Is it possible to implement the workaround used for 10.2.1 and later? Then manual TRIM by using console "fstrim" should be safe.
http://wiki.cyanogenmod.org/w/EMMC_Bugs
I assume the source for the 10.2.1 kernel would have the ported patch.