*** Latest Build 10-11-2013 ***
For d2vzw! Note the forum you're in!
If you're as big of a fan as I am of KToonsez's KT747 kernel then you'll be happy to know there is now an updated version.
This is a forked version of KToonsez's KT747 kernel with commits pulled from the CM10.2 branch of the d2 kernel.
Disclaimer: Standard disclaimer goes here. I nor KToonsez are responsible for the actions you take when working with your phone. I've done a significant amount of testing and so have others but situations arise where a hiccup could cause data loss, IMEI loss, or phone failure. You, the flasher, assume these risks. Please make sure you backup/nandroid, use nvbackup, etc.
Note:
It has been reported that this kernel will not work with 4.3.1 ROMs, notably the latest nightlies of PAC-MAN. If you're on a 4.3.1 ROM flash with extra caution. If you find otherwise please alert me.
Branch "currentCherry" (my cherry picking branch) CI status:
Branch "mr2" (KT's 4.3 branch) CI status:
Instructions:
There seems to be an odd permissions issue that we've uncovered. Follow these exact steps so when you boot you'll have working cell data:
Reboot Recovery
Clear Caches
Flash your current ROM
Flash kernel
Reboot
Profit!!!
I'm working on clearing this up. I've verified the above process against mastamoon's unofficial CM10.2 10/07 build.
Download Link:
10-11-2013
A big thanks to shane269 for helping me test this from a bootlooper to working kernel!
Thanks!
KT747's sources can be found here:
https://github.com/ktoonsez/KT747-JB
Visit the official KT747 thread here:
http://forum.xda-developers.com/showthread.php?t=1853816
Visit kt's original, ORIGINAL kernel thread here:
http://forum.xda-developers.com/show....php?t=1756776
Also if you like this kernel then please consider donating to the dev that made it all happen, ktoonsez: http://forum.xda-developers.com/donatetome.php?u=4325945
Previous Builds
10-10-2013
10-09-2013
XDA:DevDB Information
KT747 For D2VZW Cherry Picked, a Kernel for the Verizon Samsung Galaxy S III
Contributors
mikejr83, KToonsez
Kernel Special Features: KT747 kernel with latest CM10.2 commits
Version Information
Status: Beta
Created 2013-10-09
Last Updated 2013-10-16
Change log:
-10/11/2013
* Merged the commit for touchscreen optimizations
* Cherry-picked commit for reverting portions of the touchscreen optimizations which may cause us camera issues.
* Changed updater-script to hopefully resolve issue with no data after flashing (still researching issue)
First?
Looking forward to this
tapped from a carbonized d2vzw
ktoonsez gave the OK. Download link is now up. Please follow the instructions or you'll get no data. If you accidently goof and do this just reflash your ROM and then in the same session flash the kernel.
Thanks!
Mike
Thanks for this I've been using this without issues pacman ROM.
Sent from my SCH-I535 using Tapatalk 2
Just flashed on Slim 1.6 weekly and set my kernel settings. No initial issues, thanks for the update. I was going through kernel flashing withdrawals.
Sent from my SCH-I535 using Tapatalk 4
Well @mikejr83 so far so good, thanks for the update!
sent from a custom s3 powered by pacman, ROM ,KT747 kernel w/mods by team kernelizers ,themed by blackout1911,Pimped by the candyshop, and modded by all!
Is anyone not seeing OC working? I have mine set to 1728 but I'm still seeing 1510 in BBS.
Sent from my SCH-I535 using xda app-developers app
mikejr83 said:
Is anyone not seeing OC working? I have mine set to 1728 but I'm still seeing 1510 in BBS.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
I normally don't overclock my phone doesn't do well with it. I tried 1728 and it wasn't ever using it. Then I bumped it up to 1809 and it instantly rebooted. As expected, my processor just won't do it. After the reboot the phone was still set at 1728 and it was using that frequency. So maybe requires a reboot work?
Sent from my SCH-I535 using Tapatalk 2
Rebooting seems to make it stick or show up in the apps where I see freq values.
Sent from my SCH-I535 using xda app-developers app
OP Updated
Went through my cherry pick branch and realized I missed some commits. I missed about 2 days worth of merges at the end of August. These are now all added.
There is a gerrit reviewed commit for touchscreen optimizations (and a subsequent fix for camera issues). I'm having trouble merging this commit into my branch. I'll try to get that into the build for tomorrow.
Thanks!
Mike
Can I ask why there is a unofficial version of KT kernel? Did he drop support for s3?
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Rinkle McBally said:
Can I ask why there is a unofficial version of KT kernel? Did he drop support for s3?
Click to expand...
Click to collapse
He's just been really busy and this guy wanted to put a more recent build out since there have been many commits to cm 10.2
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
Are we able to flash the kernel separately yet?
Sent from my SCH-I535 using Tapatalk 4
no cigar said:
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Click to expand...
Click to collapse
Shoot! Ok. Just want to ask a couple of questions to make sure I'm on the same page and I can collect some info to try and figure this out.
10/10 build? Probably a silly question since you posted after I posted the new build, but just checking.
Are you using CWM? If you are what version?
Just to be clear, are you flashing ROM and then the kernel in the same recovery session?
I'm not familiar with liquidsmooth. Is the 2.10 release version 4.3 of Android? I'm assuming it is otherwise you probably would have gotten a bootloop instead of no data.
Thanks for the feedback. It's important that I see these. I've been worried sick that there are people downloading this, having this problem, and immediately thinking that I through out something that is bunk. I want this effort to live up to the expectations that everyone has for KT's kernel. Last thing I want to do is turn people off to his great work!
jamminjon82 said:
He's just been really busy and this guy wanted to put a more recent build out since there have been many commits to cm 10.2
Sent from my SCH-I535 using Tapatalk 4
---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------
Are we able to flash the kernel separately yet?
Sent from my SCH-I535 using Tapatalk 4
Click to expand...
Click to collapse
I was able to flash 10/10 over 10/09 without having to flash the ROM and still have data. I have not gone from sans KT to ROM with KT on the 10/10 build.
I'm going to try to get some input from some devs. I originally thought it was the updater-script applying the wrong permissions during the flash. I did, however, change the script to mimic more how LeanKernel does its flash but that fix was put in 10/09. This along with the touchscreen fixes are my top priorities to get fixed.
See responses below. Thanks!
mikejr83 said:
Shoot! Ok. Just want to ask a couple of questions to make sure I'm on the same page and I can collect some info to try and figure this out.
10/10 build? Probably a silly question since you posted after I posted the new build, but just checking.
Yep 10/10 for sure.
Are you using CWM? If you are what version?
Yes. 6.0.4.3
Just to be clear, are you flashing ROM and then the kernel in the same recovery session?
Yes, all in the same session
I'm not familiar with liquidsmooth. Is the 2.10 release version 4.3 of Android? I'm assuming it is otherwise you probably would have gotten a bootloop instead of no data.
Correct. I'm running android 4.3
Thanks for the feedback. It's important that I see these. I've been worried sick that there are people downloading this, having this problem, and immediately thinking that I through out something that is bunk. I want this effort to live up to the expectations that everyone has for KT's kernel. Last thing I want to do is turn people off to his great work!
I was able to flash 10/10 over 10/09 without having to flash the ROM and still have data. I have not gone from sans KT to ROM with KT on the 10/10 build.
I'm going to try to get some input from some devs. I originally thought it was the updater-script applying the wrong permissions during the flash. I did, however, change the script to mimic more how LeanKernel does its flash but that fix was put in 10/09. This along with the touchscreen fixes are my top priorities to get fixed.
Click to expand...
Click to collapse
Eclipse build 6
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Quie2TP said:
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Click to expand...
Click to collapse
^
SAME
New build in the OP.
Also, changelog is in the second post.
no cigar said:
Followed instructions to the letter and re-attempted 2x and still getting no data when running this kernel. Running liquidsmooth 2.10 final release. Thanks!
Click to expand...
Click to collapse
Quie2TP said:
I flashed the new version 10/10 on my Eclipse build 6 which is 4.3. I cleared cache, flashed rom, flashed kernel, and rebooted. No data at all. I then flashed the rom back over the top to get the other kernel and everything is fine. I am using the newest CWM.
Click to expand...
Click to collapse
grislieber said:
^
SAME
Click to expand...
Click to collapse
Thanks for the reports guys. Researching this issue is proving difficult as no one seems to have documented it in the "usual" places. The only suggestion I have so far is checking to make sure the permissions are correct on everything that is flashed. I took a look at a couple of other kernel dev's updater-scripts and tried to modify this one accordingly. Flashing from 10/10 to 10/11's still gave me working data. I'm trying to follow up with a few other devs so please don't think that I'm not working on this. If you flash 10/11 please report your findings!
Thanks!
Related
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
See the 9-11-12 Cyanogenmod Announcement at bottom of post! There are now regular Nightlies you are used to and now the M-Series Roms, I will let the CM Team speak for it themselves as to what it is, see quote and link at bottom of post.
As of 8-18-12, the Verizon Galaxy S III, yes the one with the formerly locked bootloader that everyone loved to hate, has now been accepted into the Official CM10 Jelly Bean Nightly builds. Bookmark THIS PAGE to check for the latest nightlies. Many thanks to everyone involved in getting the d2vzw this far including you, African Canadian Sock Monkey!
Official Announcement from Cyanogenmod 8-18-12
Today we kick off the nightly builds of the CM10 JellyBean code branch, builds will show up later this evening.
CM9 nightly builds for devices that don't receive a CM10 nightly will continue (for the meantime) but we are changing the timing on them to be once a week instead (aka weeklies). This will allow a means for us to test bug fixes and the like as they get merged into the ICS branch - as stated before, the CM9 branch is in an otherwise perpetual code-freeze.
The devices receiving CM10 nightlies this evening include (but aren't limited to):
# The US SGS3 variants
# The Galaxy Nexus variants
# The Nexus S varaints
# The Nexus 7
# The Transformer and Transformer Prime
# The SGS1 variants (Vibrant, Captivate, International, and i9000b)
# The SGS2 i9100g
# P3 and P5 tablets
Other devices will join the roster as they become ready and gain their maintainers blessing for nightlies.
Edit d2vzw nightlies will require the insecure bootloader. See http://goo.gl/CST0K
Click to expand...
Click to collapse
Source
I didn't see a thread for this so I figured I would go ahead and create this thread for the discussion and following of the d2vzw Official CM10 Jelly Bean Nightlies. Our maintainer cvpcs has stated that the initial official nightlies may not have all of the fixes such as MMS fix in them until those fixes are merged into the official tree.
YOU MUST BE ROOTED:
I recommend using the Casual app from Adam in THIS THREAD.
YOU MUST BE UNLOCKED:
As stated the official version of CM10 nightlies for d2vzw requires you be on an unlocked Verizon GSIII. As an alternative to the Casual method Adam posted up, you can now unlock your device using a simple one-click app made by fellow dev mmmeff called VZW GS3 EZ-Unlock on the play store.
YOU MUST BE RUNNING A CUSTOM RECOVERY:
Also see his EZ-Recovery for VZW Galaxy S3 app for the easiest way to load any custom recovery you want. Please note the Touch CWM 5.8.4.9 available in the app doesn't play nice with CM10. Don't use it. I personally recommend using the CWM (non-touch) versions such as 6.0.1.2. If you prefer 6.0.1.2 Touch and want to flash it using the EZ-Recovery app using the "custom" option, simply flash this file using the app.
If you would rather not use that app, see THIS THREAD for CWM 6.0.1.2 files and install instructions.
blade7840 said:
Can I use TWRP recovery to flash this Rom?
Click to expand...
Click to collapse
Don't see why not. As usual, make sure you have a nandroid just in case. I previously stated TWRP Data Wipe was broken. Which is only partially true, because it FAILS for a REASON. If it worked it would format our internal sdcard! Proper use of TWRP would be to use the Factory Reset option which should take care of things. The Format Data option would be rather dangerous if it worked. So there you go.. It should work as well as CWM. More of a preference thing. You can find TWRP 2.2.2.0 in THIS THREAD. If you like using mmmeff's EZ-Recovery app and want to flash TWRP 2.2.2.0 using the custom option, use this file.
BECAUSE WE ARE NOW UNLOCKED, WE NO LONGER REQUIRE OR USE ANYTHING KEXEC
* In case anyone is still running CWM 6.0.1.0 from the kexec kernel days it is fine to use still. It functions as a standard custom recovery but had the additional ability to run kexec enabled kernels. So you can continue to use it or upgrade to another version. Because we are unlocked you are free to use any recovery now and Kexec is no longer applied.
So now all you need to do is root your phone, load up those two apps, load the recovery (i recommend the newest TWRP 2.2.2.0), unlock the device, and download and install the latest nightly in recovery.
GOOGLE APPS (including Play Store) ARE NOT INCLUDED IN OFFICIAL CM:
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Google Apps by default.
If you do a complete wipe and install an official CM10 build clean and you still have gapps remaining without having ever installed a gapps package, you likely didn't get a clean wipe. Recommend rebooting and wiping again and re-install.
WILL I LOSE MY IMEI IF I FLASH THIS?:
WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Click to expand...
Click to collapse
There is a chance you will lose your IMEI on these devices any time you flash anything. If you are not willing to accept the risk inherent in flashing your device, regardless of what you are flashing or what you are worried about, then DONT FLASH ANYTHING, remain stock, and locked. If you want to read more on the "how to" for IMEI backup and restore, see THIS THREAD for latest IMEI discussions and detailed methods for backup and restore.
CM OFFICIAL NIGHTLIES DO INCLUDE A KERNEL:
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Click to expand...
Click to collapse
Yes. If you want to try custom kernels on CM10, it is of course at your own risk.
Flash, MMS, NFC or Native Tethering work on these builds?
Let's put it this way. They have all worked at some point or another. Then you have the fact that so many people posting here are contaminating the results with comments about unofficial builds and people that are flashing using different methods, etc......There's no good way for me to track and update this portion accurately. If you rely on any single feature to work properly, you are using the wrong ROM. Go back to stock. If you are flashing Nightlies of anykind you should expect things that have worked all along, some days will be broken. So the best thing to do is try it yourself and report here for others to see. These might be official nightlies but it's still very BETA and WIP (Work In Progress) and should be treated as such.
MMS WORKS
I can confirm personally as of the 8-20 build MMS is working and persistent after a reboot!
NFC WORKS
NFC fix found here.
WPA/WPA2 Native Tethering WORKS
You can flash the file in THIS POST to fix native tethering with WPA/WPA2 security intact.
FLASH WORKS
Sideload the newest Adobe Flash app found in THIS THREAD to get Flash on Jelly Bean. Of course you must have "Unknown Sources" enabled in Settings->Security to sideload any apk
If things change, let me know via PM, I'll try to update the OP.
UNOFFICIAL ALPHA BUILD THREAD IS OVER HERE.
In that thread you can find discussion and info on the unofficial alpha builds by people such as cvpcs, invisiblek, dhacker and others who have been part of the efforts to get us to where we are today. Their contributions are invaluable. Those builds right now may actually run smoother and have less bugs because they are UNOFFICIAL which means they can do what's called "cherry picking" and include code that has not been committed into the OFFICIAL builds yet. The official build may or may not have all those features. They are sometimes different ROMs functionally.
Now that we have an Official Nightly build in order to not confuse people please take Alpha Unofficial talk to that thread. Please keep posts here on topic and relevant to the Official Nightly builds. Things that work on those doesn't work on these and vice-versa.
CHANGELOG IS HERE and UnOfficial CM10 Bugtracker is HERE
-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
UPDATE, Official Announcement from Cyanogen Mod, M-Series Roms Announcement 9-11-12
Something we have learned over the past few months is that if you don’t release, someone else will do it for you. Since we are open-source, we absolutely encourage it! Unfortunately, the quality of unofficial builds can vary, and we are serious about quality. Of course nightlies are always available, but we realized that having something that is a bit more stable on a more frequent basis is important. Starting now, we are rolling out our M-Series releases. M-Series builds will be done at the beginning of every month. We did a soft freeze of the codebase for the last week, blocking new features in order to stabilize. Our plan is to continue this (assuming that the response is good) up until stable release, and onward.
We aren’t exactly sure what M stands for. “Monthly”, “milestone”, or perhaps “MINE ALL MINE!”. Whatever it is, I hope that we are meeting the needs of community.
M-Series builds will be available under the EXPERIMENTAL tag. The filename will include the date stamp as well as the M version. These builds should be stable enough for daily use, and we encourage feedback and bug reports.
Tonight’s M1 build is available for these devices:
Galaxy Nexus GSM (maguro)
Galaxy Nexus VZW (toro)
Galaxy Nexus Sprint (toroplus)
Galaxy S2 GT-I9100G (i9100g)
Galaxy S (galaxysmtd)
Galaxy S B (galaxysbmtd)
Captivate (captivatemtd)
Galaxy S3 Sprint (d2spr)
Galaxy S3 VZW (d2vzw)
Galaxy S3 AT&T (d2att)
Galaxy S3 TMO (d2tmo)
Galaxy S3 US Cellular (d2usc)
Nexus S (crespo)
Nexus S 4G (crespo4g)
Galaxy Note AT&T (quincyatt)
Google Nexus 7 (grouper)
Sony Xperia Acro S (hikari)
Sony Xperia S (nozomi)
In standard CM style, we will continue to add devices as time goes on up until our stable release.
Head over to Get.CM to grab the latest build for your device. Installation instructions and other documentation can always be found at the CM Wiki and help is always close at hand over on our official forums.
Happy flashing!
Click to expand...
Click to collapse
Source
If you need a more general "all things GSIII guide" to bail out of a problem, or to do other things that aren't necessarily CM10 specific, I highly recommend THIS THREAD
So to start it off I'd like to know if anyone is running the cm-10-20120818-NIGHTLY-d2vzw.zip build from early this morning? Does it have the MMS fix? Is it significantly different from the alpha builds we have been running for a couple weeks?
Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've unlocked your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.
Do these include google now, if not where can I get it?
ilogik said:
Do these include google now, if not where can I get it?
Click to expand...
Click to collapse
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Make sure you also have a copy of the CWM flashable Google Apps on your ext sdcard which can be found HERE thanks to our friends at goo.im because CM doesn't come with Play Store by default.
Click to expand...
Click to collapse
Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium
Immolate said:
Flashed this directly over my Synergy 1.7 a few hours ago and it's working great.
Make sure you've disabled your bootloader. I understand there is a one-click in the play store for those who can't bear the horrors of one-clicking on Casual.
Did a factory wipe/cache/dalvik.
I haven't found anything yet that's not working.
I'm running CM on my tenderloin so I'm used to some of the conventions.
Click to expand...
Click to collapse
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies
WizeGuyDezignz said:
Is there still a chance to lose your imei with these?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
YES. Op updated.
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2
Schaweet said:
Lol. I'm pretty sure you don't want to disable your bootloader. Now, you do need to unlock your bootloader. The difference is kind of a big deal. Just sayin
Sent from my SGS3 on Synergy Nightlies
Click to expand...
Click to collapse
Yeah yeah, acknowledged. I'm sure if you can disable your bootloader, I'll figure out a way.
ive had one random reboot hopefully it was just a once time thing cause im loving this rom..much better than touchwiz
hopefully that flickering thing when texting gets fixed soon cause it gets a bit annoying..(ive also noticed that my widgets flicker)
neyenlives said:
Please read the OP. CM never has and never will come with Google Apps, per Cyanogenmod.
Click to expand...
Click to collapse
I think he's talking about Google now(voice search assistant), Not Google apps. It should be built into the ROM but you should still flash gapps anyways
Sent from my SCH-I535 using Tapatalk
Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
---------- Post added at 01:02 PM ---------- Previous post was at 01:00 PM ----------
tombepa said:
Do the nightlies flash a kernel? I'm on imo's leankernel and just needed to know if I need to flash a non-kexec one or if it does it itself?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The ROM comes with a kernel, but you can flash any non-kexec kernel for AOSP ROMs that you want. I'm currently running an AT&T kernel.
Sent from my Galaxy S III
TheBiles said:
Can we update the OP with important commits like the MMS fix when they go through?
Sent from my Galaxy S III
Click to expand...
Click to collapse
mms is working for me with the latest build:good:
XTRoRDiNAiRE said:
mms is working for me with the latest build:good:
Click to expand...
Click to collapse
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III
Can I use TWRP recovery to flash this Rom?
TheBiles said:
Does your phone number stick after a reboot? CVPCS said that the commit wouldn't be in the first build.
Sent from my Galaxy S III
Click to expand...
Click to collapse
Phone number and MIN are blank for me (after a few reboots). Also, the LTE toggle doesn't seem to function properly. Everything else is working flawlessly; this ROM is definitely a daily-driver. Enjoy!
EDIT: I just realized that MMS isn't working for me....I can live without it for now but those that need it, may want to wait for another build.
neyenlives said:
YES. Op updated.
Click to expand...
Click to collapse
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium
Nice. I was just thinking about flashing this
Sent from my Verizon Samsung Galaxy S 3 running SynergyROM v1.6
WizeGuyDezignz said:
Thanks. Will this issue ever be fixed?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
The IMEI issue from my personal standpoint and based off of the opinions of the smart guys in IRC, is that it is very possibly a hardware design issue. Samsung could have put the EFS data which contains the IMEI in a non-volatile un-changable part of the memory but it looks as though they left it writable. This means we can try to write it back if we lose it but it also means bad data could be written to it thus erasing it.......that's what I have gotten out of it so far. So every time you flash you take the risk. I seriously doubt any fix will ever officially come because as long as you buy the phone and use it in stock form, you would never see the issue. It's an issue that only affects custom flashers, so don't expect to see a fix.
I am trying to install Franco kernel on my phone, and I have found the thread for this, but I am really confused on how to install it on my phone. I know that it's the same as installing a ROM, so I downloaded the appropriate version for my phone, but it said "Failed" while flashing it with TWRP. Am I doing something wrong?
SketchySean said:
I am trying to install Franco kernel on my phone, and I have found the thread for this, but I am really confused on how to install it on my phone. I know that it's the same as installing a ROM, so I downloaded the appropriate version for my phone, but it said "Failed" while flashing it with TWRP. Am I doing something wrong?
Click to expand...
Click to collapse
Yes, you are doing something wrong. FranciscoFranco does not have a kernel for the Verizon GSIII. Stop what you're doing and use a kernel from the VZW GSIII Original dev section.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
Yes, you are doing something wrong. FranciscoFranco does not have a kernel for the Verizon GSIII. Stop what you're doing and use a kernel from the VZW GSIII Original dev section.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
SketchySean said:
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
Click to expand...
Click to collapse
I personally love ktoonsez kernel, lots of tweaks and governors to it.
Sent from my SCH-I535 using Tapatalk 2
SketchySean said:
Ahh! Not gonna lie, I feel stupid right now. And thanks, I will. But what kernel would you recommend in terms of battery life-friendly? I've seen you around in the threads. You're awesome at helping people!
Click to expand...
Click to collapse
All the Touchwiz kernels do a good job with increasing battery life.
Wow, I tried to flash the Zeus kernel and it just messed up my phone.. I rebooted and my screen was black. Couldn't reboot again, so I went into recovery mode and restored from back up :/ What did I do wrong?
which rom have you?
I am currently on CM10.1
Sent from my SCH-I535 using xda app-developers app
SketchySean said:
I am currently on CM10.1
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
You need an AOSP kernel. Not TW. KT747 is probably the way to go. Just make sure you download the AOSP version. Next time say what ROM you're running. That way you can avoid confusion early on.
Oh, alright. So that kernel is battery friendly? And is there a specific thread where I can find kernels for my ROM and or phone?
Sent from my SCH-I535 using xda app-developers app
SketchySean said:
Oh, alright. So that kernel is battery friendly? And is there a specific thread where I can find kernels for my ROM and or phone?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Not sure if there is a single thread that lists all the kernels. Just go here to the original android development forum:
http://forum.xda-developers.com/forumdisplay.php?f=1692
and look for threads that have AOSP and Kernel in the thread title.
Edit - actually, perhaps this thread may help you:
http://forum.xda-developers.com/showthread.php?t=2064506
landshark68 said:
Not sure if there is a single thread that lists all the kernels. Just go here to the original android development forum:
http://forum.xda-developers.com/forumdisplay.php?f=1692
and look for threads that have AOSP and Kernel in the thread title.
Edit - actually, perhaps this thread may help you:
http://forum.xda-developers.com/showthread.php?t=2064506
Click to expand...
Click to collapse
Okay, so I flashed the Ktoonz kernel.. and now my screen is black again. I really don't know what I'm doing wrong.
SketchySean said:
Okay, so I flashed the Ktoonz kernel.. and now my screen is black again. I really don't know what I'm doing wrong.
Click to expand...
Click to collapse
When is your CM10.1 rom dated as? When was it released? You might need a kernel from before the rom's date.
SlimSnoopOS said:
When is your CM10.1 rom dated as? When was it released? You might need a kernel from before the rom's date.
Click to expand...
Click to collapse
I can't check cause my screen is black.. but I think I got the one dated at 3/4/2013
I checked the ROM that was in my ext hard drive, and I think it's CM 10.1- 201330304-EXPERIMENTAL-d2vzw-M2
SketchySean said:
I can't check cause my screen is black.. but I think I got the one dated at 3/4/2013
Click to expand...
Click to collapse
As in, from March? lol Ahh, you basically can't flash any current kernel out unless it's from around March 4th. Ahh, you're using the Linux 3.0 based version then. All AOSP roms have moved to the Linux 3.4 kernel as of early April Edit: Actually,mid-March was the Linux 3.0 to 3.4 switch which means all kernels are now incompatible with roms dated say before early March.
Here's KT747 from March 5th, should be fine flashing this.
Edit: flash the AOSP 4.2 version btw, that's what CM10.1 is based on
SlimSnoopOS said:
As in, from March? lol Ahh, you basically can't flash any current kernel out unless it's from before March 4th. Ahh, you're using the Linux 3.0 based version then. All AOSP roms have moved to the Linux 3.4 kernel as of early April which means all kernels are now incompatible with roms dated say before early April.
Here's KT747 from March 5th, should be fine flashing this.
Edit: flash the AOSP 4.2 version btw, that's what CM10.1 is based on
Click to expand...
Click to collapse
If I flash this kernel, will it wipe everything? And is this the only kernel that I can use? I'm really sorry if I'm asking a lot of questions, lol...
SketchySean said:
If I flash this kernel, will it wipe everything? And is this the only kernel that I can use? I'm really sorry if I'm asking a lot of questions, lol...
Click to expand...
Click to collapse
Nah, flashing kernels only necessitates you wiping Cache and Dalvik Cache in recovery. Neither of which is user data. Cache and Dalvik Cache get rebuilt once the rom boots so it's not something you'll notice besides the initial boot.
As for your second question, no this is not the only kernel you can use. If you want to stay on this exact rom, then you'll just have to do a lot of searching through kernel threads, for their Linux 3.0 based kernels from early March. However, this goes along with what I said in my prior post. Given that you are on a March 4th rom, you can only use Linux 3.0 based kernels which kernel devs usually mention in their changelog. Most (honestly all) kernel devs have stopped actively developing these and have moved onto Linux 3.4 kernels which will not boot on the rom you are on because it is outdated.
I encourage you to upgrade your rom to a current one and to keep up with active development that way you don't get left behind when flashing kernels (if that's your thing).
SlimSnoopOS said:
Nah, flashing kernels only necessitates you wiping Cache and Dalvik Cache in recovery. Neither of which is user data. Cache and Dalvik Cache get rebuilt once the rom boots so it's not something you'll notice besides the initial boot.
As for your second question, no this is not the only kernel you can use. If you want to stay on this exact rom, then you'll just have to do a lot of searching through kernel threads, for their Linux 3.0 based kernels from early March. However, this goes along with what I said in my prior post. Given that you are on a March 4th rom, you can only use Linux 3.0 based kernels which kernel devs usually mention in their changelog. Most (honestly all) kernel devs have stopped actively developing these and have moved onto Linux 3.4 kernels which will not boot on the rom you are on because it is outdated.
I encourage you to upgrade your rom to a current one and to keep up with active development that way you don't get left behind when flashing kernels (if that's your thing).
Click to expand...
Click to collapse
Alright, I will flash the 3.0 kernel right now. And as for updating my CM10.1, can i just update it through my phone? I've came across this option where I can just update it through settings. Will updating ROMS wipe my stuff? And I REALLY appreciate your help.
SketchySean said:
Alright, I will flash the 3.0 kernel right now. And as for updating my CM10.1, can i just update it through my phone? I've came across this option where I can just update it through settings. Will updating ROMS wipe my stuff? And I REALLY appreciate your help.
Click to expand...
Click to collapse
I wouldn't. Being that you're moving from a March CM build to a May CM build with a lot of changes, you need to do a full wipe in recovery to upgrade roms. Doing a dirty flash in this case introduces way too much room for issues to arise. As long as you do not wipe internal storage then you will not lose your data on the internal sdcard.
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
I wouldn't. Being that you're moving from a March CM build to a May CM build with a lot of changes, you need to do a full wipe in recovery to upgrade roms. Doing a dirty flash in this case introduces way too much room for issues to arise. As long as you do not wipe internal storage then you will not lose your data on the internal sdcard.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
So if I flash from recovery, everything will be exactly the way it was?
List all Questions and Off-Topic discussions here
Welcome to VanirAOSP. Our mission is to deliver a clean optimized version of Android to as many devices as possible. This is not a kang rom. You will find versions of the features you love that we've rewritten and improved on plus a few we wrote ourselves. we've tried to acheive a more organized and cohesive setup to improve the user experience while correcting any performance regressions and improving functionality.
If you're the kind of person that needs options to change the font and color on every letter and expect the ROM to end up looking like kid's cereal box then GTFO. You will not find customizations that are done just because someone figured out how to do them. Everything in here has a purpose and is held to a high standard of coding.
General features:
stock mode - ability revert to stock AOSP code with the exception of a few custom features we chose to keep active
enhanced performance.. longer uptime with less slowdown
custom written CRON and init.d.
minor UI and graphics improvements
custom navbar, navring, and hardware key features
active notifications (improved active display + lockscreen notifications)
usability improvements like power reboot menu and sound
animation control
Improved Vanir keyboard
CM's profiles & quicksettings
additional quicksetting tiles
immersive desktop <- fully configurable immersive mode
low profile mode
statusbar mods
clock & battery mods
lockscreen blur and other mods
soon to come -> quick cam and flash notifications
busybox, embedded root, init.d, cron etc
many improvements and new features unique to vanir
more to come when i feel like updating the op
issues:
- stop flashing the moto X binaries. they do not improve anything for you and aren't even for your device.
- open source camera and launcher3 do not have the same featuers as the google versions. use the latest
banks standard gapps if you'd like these. His gapps are super legit and always up to date.
Join our Google+ community for news/updates
Nightly downloads are available on our google+ page or directly from our server
if you're interested in becoming a maintainer.. or just need help please send an email to [email protected]
Download:
http://www.emccann.net/nuclearmistake/VanirAOSPNightlies
Check Vanir Updater for updates daily
Gapps: http://goo.im/devs/BaNkS/GApps i recomend Banks Gapps
Experimental (These are downloads built by me that are not official and may or may not be stable but your welcomed to test them and give feedback)
http://downloads.codefi.re/ethanj99/vanir_evita
Please Consider Rating this thread 5 Star and press the like button
Credits:
Vanir
Slim ROMS
AOKP
AOSP
PAC-Man
codefireXperiment
Code Aurora Forum
DHOMD
nuclearmistake
Jason Downing
PrimeDirective
LorDClockan
tbalden
pingpong
Rc420head
Flashalot
Source:
ROM Source: https://github.com/VanirAOSP
KernelSource: https://github.com/CyanogenMod/android_kernel_htc_msm8960
if you want a clean aosp rom than go into development settings on this rom and enable stock mode and reboot!
List all Questions and Off-Topic discussions here
MINE!!!!!!!!!!!
MINE!!!!!!!!!11
Vanir q&a/t thread:
http://forum.xda-developers.com/showthread.php?t=2797109
Sent from my Evita
Remember all development related questions and comments and bug reporting can be here in this thread. things like questions on how something works or why something happens or descussion about the rom should go in the Q&A thread
Scozzar said:
There is no camera on the 8/15 build? What.
Click to expand...
Click to collapse
List all Questions and Off-Topic discussions here
I flashed the latest nightly (0819) and WiFi seems to be broken...it doesn't even turn on. Great ROM otherwise it's smooth as butter
Edit : torched 4.8 fixed WiFi for me now this ROM is perfect
nicolahaye said:
I flashed the latest nightly (0819) and WiFi seems to be broken...it doesn't even turn on. Great ROM otherwise it's smooth as butter
Edit : torched 4.8 fixed WiFi for me now this ROM is perfect
Click to expand...
Click to collapse
Confirmed.
Edit: Will try torched, did you flash after flashing Vanir, or reflash?
CyanJustice said:
Confirmed.
Edit: Will try torched, did you flash after flashing Vanir, or reflash?
Click to expand...
Click to collapse
I flashed ROM yesterday and WiFi was broken and today I flashed only kernel (torched 4.8) and WiFi is working
I have to say, this ROM is very impressive! Great UI tweaks, very fast, ART works very well. The only bug I've noticed is my cell signal goes out completely for a few seconds every once in a while. Otherwise, very awesome indeed!
Sent from my One X using XDA Premium 4 mobile app
Is this ROM discontinued ? I haven't seen any nightly since 0819...
nicolahaye said:
Is this ROM discontinued ? I haven't seen any nightly since 0819...
Click to expand...
Click to collapse
The latest nightly is pretty stable, been having no issues whatsoever, except the need to flash a new radio every few days or so, but that could just be due to my own location.
Sent from my One X using XDA Premium 4 mobile app
CyanJustice said:
The latest nightly is pretty stable, been having no issues whatsoever, except the need to flash a new radio every few days or so, but that could just be due to my own location.
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
And also WiFi doesn't work on stock kernel. Only working with torched 4.8. I guess it's related to the latest changes with the WiFi. When I first flashed the ROM it didn't work so I flashed torched to fix it but I've had a lot of random reboots since 3-4 days so I just got back on stock kernel only to remember WiFi is broken.
Edit : still getting random reboot also on stock kernel. I'll try and grab a last_kmsg next time it happens.
nicolahaye said:
And also WiFi doesn't work on stock kernel. Only working with torched 4.8. I guess it's related to the latest changes with the WiFi. When I first flashed the ROM it didn't work so I flashed torched to fix it but I've had a lot of random reboots since 3-4 days so I just got back on stock kernel only to remember WiFi is broken.
Edit : still getting random reboot also on stock kernel. I'll try and grab a last_kmsg next time it happens.
Click to expand...
Click to collapse
Well that's odd, I don't get reboots at all. Maybe that's because of an app incorrectly allocating memory?
Sent from my One X using XDA Premium 4 mobile app
CyanJustice said:
Well that's odd, I don't get reboots at all. Maybe that's because of an app incorrectly allocating memory?
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have no idea :s I got a last_kmsg but I can't post it from this app I'll do it as soon as I'm near my computer I don't quite understand what it's saying.
nicolahaye said:
I have no idea :s I got a last_kmsg but I can't post it from this app I'll do it as soon as I'm near my computer I don't quite understand what it's saying.
Click to expand...
Click to collapse
Have you updated to the newest nightly?
Sent from my One X using XDA Premium 4 mobile app
CyanJustice said:
Have you updated to the newest nightly?
Sent from my One X using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I haven't but I will as soon as possible. I didn't know there was a new built. I'm actually on 0819 I'll let you know
I installed the 0902 nightly via vanir updater and WiFi now works very well I still get random reboots though, here's the last_kmsg I grabbed while on 0819 nightly, i'll try to grab another one while on the latest as well.
Newest nightly refused to boot for me.. Just endlessly sat on the Vanir splash screen.
Vanir 4.4.4 build required
Hi,
I see that the last vanir build for evita for 4.4.4 was this vanir_evita_4.4.4.112414
But the official repo for vanir only hosts 5.0 builds. If somebody has it downloaded can you please send it to me.
Any help is much appreciated.
TIA!
I love AOSP ROMs but the latest nightlies that I've installed have crashed right after the boot. Please, look into that.
Thanks.
Sent from my One X
WildKernel
for AT&T Samsung Galaxy S II
Go check out Tame! It goes great with this and it handles OTA updates for this kernel.
This is a Linux based (3.0.101) Kernel which is maintained by me kept inline with the Cyangenmod Kernel so this is compatible with ALL the latest KitKat Roms (unless otherwise stated in the ROM).
Please report anything good and bad so that I know what to keep and what not to keep for the next release. This also helps me push out fixes faster when presented with lots of information (such as logs etc.).
Please see changelogs for an in-depth look at features. Also take a look at the screenshots for a sneak peek.
Feeling like a critic? Leave a review!
Link broken? Try one of the mirrors, Still a no go? Goto my signature and click the file backups link, then navigate to what you were looking for.
v013: AFH
TRU Mirrors: #1 / #2
All Releases: AFH | TRU Mirrors
[#WildKernel-Celox-CL]
[/HIDE]
Thanks:
TeamChopsticks & CyanogenMod
TeamSXL
Cl3Kener
Team Hydra
TeamDS
faux123
Sultanxda
Tamcore
cretin45
showp1984
RomanBB
and any others I may have missed
Info on Governors/Schedulers
You may find my source hosted @ Github
There is NO need to clear caches, kernel installer handles everything. Just flash and reboot.
My recommended Governor/Scheduler setups:
Battery w/ Good Performance at 96-1350mhz:
Intellidemand/SIO (personal choice)
Lazy/SIO
Badass/SIO
Ondemand/SIO
Wheatley/SIO
'lil more Performance at 96-1512mhz:
Smartass/SIO
Hyper/Deadline
Samsung/Deadlne
lulzactive/Deadline
Savagedzed/Deadline
Best Performance (worst battery): 384-???mhz
Gaming/Deadline
Performance/Deadline
Did you read the announcement? (page header)
XDA:DevDB Information
WildKernel for the AT&T Galaxy S II (skyrocket), Kernel for the AT&T Samsung Galaxy S II Skyrocket SGH-I727
Contributors
Emmanuel U
Source Code: https://github.com/EmmanuelU/wild_kernel_samsung_msm8660/tree/android-msm-skyrocket-3.0
Kernel Special Features: Too many features to list, just install it.... now.
Version Information
Status: Stable
Current Stable Version: 013
Stable Release Date: 2015-01-29
Created 2014-10-15
Last Updated 2015-02-01
Tried to install but keep getting an md5 error and a message about getprop device not equaling.
Downloaded and tried twice...
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Installer zip fixed, please re download if you downloaded kernel before seeing this message....thanks!
The new installer worked, thanks. I'll play around with it and report back but I can already say that WiFi direct doesn't work (it's always the first thing I check b/c it's the only problem I have with any of the skyrockets current kernels)
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
tsew2674 said:
The new installer worked, thanks. I'll play around with it and report back but I can already say that WiFi direct doesn't work (it's always the first thing I check b/c it's the only problem I have with any of the skyrockets current kernels)
Sent from my SAMSUNG-SGH-I727 using XDA Free mobile app
Click to expand...
Click to collapse
Are you sure that problem is directly related to the kernel? It sounds more like a Rom issue....does it work on your rom's stock kernel?
Emmanuel U said:
Installer zip fixed, please re download if you downloaded kernel before seeing this message....thanks!
Click to expand...
Click to collapse
I guess the burning question for me if this includes all of Sultan's bluetooth fixes. His kernel for CM really is the gold standard for our device thus far.
I see you mentioned him in the OP so I am hopeful lol. I'd love to be able to flash this kernel with any rom knowing the usual plagues (such as the constant BT disconnect) are no longer an issue.
Thanks a lot for this! Nice to see the SR still getting some love
Emmanuel U said:
Are you sure that problem is directly related to the kernel? It sounds more like a Rom issue....does it work on your rom's stock kernel?
Click to expand...
Click to collapse
I'm pretty sure it's at the kernel level only because it works with @Sultanxda's kernel. His is the only 4.4.x kernel that WiFi direct has ever worked on for me on the skyrocket. It worked on the official CM10.2 ROMS/kernels but every since CM11 was introduced it's been broken. The ROM I'm using now could connect with WIFI direct when built with Sultan's kernel.
Even with Sultans kernel, Miracast (with uses WIFI direct) will connect but the graphics are all scrambled. I suspect that has to do with some of the memory enhancements he's made. If I knew how to build kernels I'd like to try using the official CM11 kernel source and only applying his WIFI direct commit to see what the results are, but unfortunately I don't know how to build them and can't seem to find the time to do the research to learn. Maybe one day.
I've had no issues otherwise and I've been using it for a few days now. Thanks
I tried flashing usin dirtya unicorns i can get oast boot logo ut restarts
raptorddd said:
I tried flashing usin dirtya unicorns i can get oast boot logo ut restarts
Click to expand...
Click to collapse
Once your screen goes black from the reboot, hold both the volume buttons until your device goes into recovery. Then either use ADB or your recovery's file manager to retrieve /proc/last_kmsg and it post it here. It always helps to present issues with a log ready, for future reference.
So... I got bored.
I installed the following ROM's and got bootloops for each (basically every 4.4.4 ROM I know of for Skyrocket):
AOKP - Dated 15-Sep-14
CM11 - Dated 19-Oct-14
PacRom - Dated 25-Aug-14
Mokee - Dated 12-Oct-14
Dirty Unicorns - Dated 2-Oct-14
SlimKat - Dated 14-Oct-14
CarbonRom - Dated 17-Oct-14
Beanstalk - Dated 9-Oct-14
CandyKat - Dated 18-Oct-14
Paranoid - Dated 9-Oct-14
I didn't test the following ROMs:
SultanXDA CM11 - Dated 19-Oct-14 Didn't test since I was told it would bootloop
MIUI V6 - Currently getting a bootloop so no reason to try it
Emmanuel U said:
Once your screen goes black from the reboot, hold both the volume buttons until your device goes into recovery. Then either use ADB or your recovery's file manager to retrieve /proc/last_kmsg and it post it here. It always helps to present issues with a log ready, for future reference.
Click to expand...
Click to collapse
Never done this before (well, I know how to get into recovery...lol). I'll post the file in a few minutes after reflashing one of the ones above. Can i empty this folder when I'm done? There's 200 or so subfolders in there.
ETA: Added attachment.
xonelith said:
So... I got bored.
I installed the following ROM's and got bootloops for each (basically every 4.4.4 ROM I know of for Skyrocket):
AOKP - Dated 15-Sep-14
CM11 - Dated 19-Oct-14
PacRom - Dated 25-Aug-14
Mokee - Dated 12-Oct-14
Dirty Unicorns - Dated 2-Oct-14
SlimKat - Dated 14-Oct-14
CarbonRom - Dated 17-Oct-14
Beanstalk - Dated 9-Oct-14
CandyKat - Dated 18-Oct-14
Paranoid - Dated 9-Oct-14
I didn't test the following ROMs:
SultanXDA CM11 - Dated 19-Oct-14 Didn't test since I was told it would bootloop
MIUI V6 - Currently getting a bootloop so no reason to try it
Never done this before (well, I know how to get into recovery...lol). I'll post the file in a few minutes after reflashing one of the ones above. Can i empty this folder when I'm done? There's 200 or so subfolders in there.
ETA: Added attachment.
Click to expand...
Click to collapse
Hmm interesting, since I dont have this device, I can't do this myself. But do u think u can you do the following?
1. Flash one of the Roms you listed that bootlooped above
2. Open my kernel installer and delete /system/bin/thermald
3. Push it to your device and install
4. Does it boot?
Emmanuel U said:
Hmm interesting, since I dont have this device, I can't do this myself. But do u think u can you do the following?
1. Flash one of the Roms you listed that bootlooped above
2. Open my kernel installer and delete /system/bin/thermald
3. Push it to your device and install
4. Does it boot?
Click to expand...
Click to collapse
Sadly, bootloops again (I installed the AOKP rom; clean, no GApps, let it boot once, boot to recovery and flash modified zip).
xonelith said:
Sadly, bootloops again (I installed the AOKP rom; clean, no GApps, let it boot once, boot to recovery and flash modified zip).
Click to expand...
Click to collapse
Too bad i hope emmanuel fix this.. Anything i can do ..
Reboots
I was playing around in Tame earlier and my phone rebooted a few times. I wasn't doing anything too crazy, turned off SweepToWake, changed the governor to Lazy and it froze and rebooted. The first time it happened I had changed the max frequency and a couple of other things, so I attributed the reboot to that, however when it booted back up I only changed the two items mentioned above and it rebooted again, this time it stayed off so I booted into recovery and got the kMsg, hopefully it helps. That's not the first time I've used Tame, I initially installed it, changed a few things and everything was fine, but my phone had been turned off since then so I was going back in to set it back the way I had it.
I'm currently using the liquidsmooth as my ROM, and this is really the first issue I've had with your kernel (other than WIFI direct, but that's pretty much all the kernels for this device). I think you've even improved my battery life, I don't do gaming or anything so I don't really ever notice any performance gains or that sort of thing, but I haven't noticed anything moving slower, which is good.
Update
Another minor update today, sorry about the initial discrepancies! Blame me, since I don't actually have this device. Well it should boot on all ROMs now, enjoy .... I guess.
Works great on PA! I'll mess with it for a bit and provide useful feedback.
Sent from my SGH-I727 using XDA Free mobile app
Flashed successfully on Carbon 10/17 nightly. Seems pretty snappy so far. Nice work! :thumbup:
Hi. Thanks for sharing this Kernel. I have a question...
Before, I was using Carbon with its stock kernel, Conservative governor and noop; there was no lag at all, but battery seems to last too little time in continous use and even when it was with screen off. Even before that, the CPU governor was set by default at Interactive, but the Skyrocket freezes in several times, sometimes after unplug it from charger or after unlocking it after a time (like 1 hour or something), sometimes the device hangs so long until I reboot it or it reboots itself. So, Interactive isn't the best choice for me.
The question is: What is the best choice for a governor if I want the longest battery life, but with any freezing any time?
Could you please help me?
franzpimp87 said:
Hi. Thanks for sharing this Kernel. I have a question...
Before, I was using Carbon with its stock kernel, Conservative governor and noop; there was no lag at all, but battery seems to last too little time in continous use and even when it was with screen off. Even before that, the CPU governor was set by default at Interactive, but the Skyrocket freezes in several times, sometimes after unplug it from charger or after unlocking it after a time (like 1 hour or something), sometimes the device hangs so long until I reboot it or it reboots itself. So, Interactive isn't the best choice for me.
The question is: What is the best choice for a governor if I want the longest battery life, but with any freezing any time?
Could you please help me?
Click to expand...
Click to collapse
See the OP for ny recommendations.
Emmanuel U said:
See the OP for ny recommendations.
Click to expand...
Click to collapse
Yes, I'm sorry, I forgot to say that actually I'm using Lazy governor at 96-1350 and sio as you recommended it, but I thought that maybe there's a no listed recommendation for maximun battery or something like that.
This thread is for updates of temasek cm12.1 built by myself. I will be building for hlte and hltespr.
Temasek made this all possible and it is all his work I am just taking the time to build and upload.
V19.3+ root removed, you will need to flash SuperSU zip to achieve root.
Downloads:
Hlte or Hlte on my BasketBuild
Hltespr or Hltespr on my BasketBuild
Credits: @temasek
XDA:DevDB Information
Temasek cm-12.1 unofficial cyanogenmod, ROM for the Samsung Galaxy Note 3
Contributors
trader418, Temasek
Source Code: https://github.com/temasek/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: Cyanogenmod
Version Information
Status: Beta
Created 2016-03-26
Last Updated 2016-03-26
Thanks for keeping support for the Note 3 alive.
Great, good to see 12.1 back alive. Anything I can do to help, just say so.
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Buslova said:
Thanks again! Always willing to help however I can.
BTW, really good job on creating the thread using just your phone! I've seen FAR worse.
Click to expand...
Click to collapse
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Straw poll whether to include root in the build here http://strawpoll.me/7191529
trader418 said:
Haha thank you, I try my best
Glad to see all of you guys showing support. If I ever don't see temasek updated the version and any of you do just post here and I'll build, however I think most of the time I should be okay. I'm going to set up a straw poll in the include root vs not include. I also could start to use the ota app if you guys really would like that
Click to expand...
Click to collapse
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Buslova said:
I will always use root however I understand some people's need for it to be rootless and well, let's be honest, it ain't hard to flash supersu right after flashing the rom. lol.
OTA is a nice lazy option for the USER but I've gathered from past posts in other threads that it's not always so easy for the dev since the OTA app is maintained/owned by another dev and sometimes has issues. Again, we're talking about a community here who is flashing custom roms on their devices. Manually downloading and flashing shouldn't be a major issue.
Having said all that, if i were to vote I'd say:
Built-in root: No
OTA: Yes (if it's not a headache)
Click to expand...
Click to collapse
Ota isn't too bad, I'll probably use it soon tbh, but I won't promise anything
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
redfuryjr55 said:
hey guys, I have been having trouble with tema's cm 13 builds so i decided to give 19.1 a shot. Unfortunately, I haven't had any luck with the rom. The rom just boot loops after every installation. I have tried with gapps aroma and pico with different wipes with no luck. continues to bootloop as soon as I reboot and i never get into the rom. I am back on tema's for now but would love to switch to 19.1 if I could get some help. Sorry for being a noob, Im probably messing something up somewhere and I thank you for your help in advance!
Click to expand...
Click to collapse
Start with which device you have
trader418 said:
Start with which device you have
Click to expand...
Click to collapse
haha sorry! htlespr!
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
trader418 said:
I'm not sure mate, has anyone else got any suggestions?
There has been reports of multiple wipes and reboots and then flashing the ROM helps but I cannot say it will help
Click to expand...
Click to collapse
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
redfuryjr55 said:
hmmm.. well I managed to get booted by installing temasek's last build (12.9 i think, the one from jan) along with his kernel. It booted fine and made it into setup. I then rebooted to recovery and dirty flashed you 19.1. Got bootlooped and said fk it and re-flashed the kernel and got into 19.1! Now that is great and all, but super weird/inconsistent. Also, once I got everything set up I could not turn on wifi or bluetooth; is this a known issue with a fix? Also, are there recommended installation instructions or is there a recommended kernel for you build? Thanks in advance for your help and patience with my noobness! Again I am on htlespr!
Click to expand...
Click to collapse
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
trader418 said:
All I know is that all my hlte builds are tested with a clean wipe and then a flash and reboot. I have no problems. I am using temaseks device tree so the only difference between his and my build should technically be root and ota app. Other than that it should be identical
Click to expand...
Click to collapse
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
swukjay said:
I am using this as my daily Rom, the only problems I get are the weather widget doesn't update and it wont connect to the wifi in my local hospital, I am using build v19.0 build date 17th of march, even my s-pen works !
I will test this later and post back results
Click to expand...
Click to collapse
Either change weather provider to another or customize your location. Sometimes yahoo weather isn't working well.
As for WiFi, check your dev options.
redfuryjr55 said:
haha sorry! htlespr!
Click to expand...
Click to collapse
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
eseregin said:
Just in case - have updated your Modem and Bootloader to the latest? All wireless related problems might be connected to it.
Click to expand...
Click to collapse
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Hmm, still no luck eh? I tried helping ya last night in the other thread. I'm also a hltespr user. I'm still running OH1 baseband however OK2 is the latest. Also, as I told you last night, I'm using an older version of TWRP recovery (ver. 2.8.7) however the latest is 3.0.0.
What baseband are YOU running? Go to settings, "About phone", and look for "Baseband version" and let us know. =)
redfuryjr55 said:
what modem/baseband should i use for htlespr? what is tested and working, does anyone know?
Click to expand...
Click to collapse
Sorry, I have different phone..
Might be the latest here
https://idlekernel.com/flash-tools/firmware/hltespr_SM-N900P/N900PVPUEOK2/
But I am far away from sure