Team Epic announces a proof-of-concept source-built kernel for the Verizon SGS3, complete with kexec hardboot support. This kernel serves two purposes:
1. To be included in custom recovery images, as it proves the capability of booting-via-kexec custom kernels from recovery.
2. To serve as a proof-of-concept boot kernel, to demonstrate that custom kernels are capable of running on the Verizon SGS3 in its present form.
Please see our blog post, Kexec, and a Proof-of-Concept Source-Built Kernel for the Verizon SGS3, for full details and source links.
CyanogenMod's Team Epic specializes in Sprint's flagship Android phones on Sprint.
If you appreciate our work, please consider supporting us with a tiny contribution. Thanks!
Awesome! Thank you so much for your guys efforts
Sent from my HTC Rezound via Tapatalk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
MyColorScreen
Good luck guys.
☞ sent from my GS3
Just to confirm, the kexec hardboot approach used here is a bit different from the typical kexec. The main difference is that we actually perform a hardware reboot, reinvoking the bootloader just prior to booting the kexec'd kernel.
The advantage to this approach is that it maintains a high-degree of compatibility and minimizes buggy behavior. The disadvantage is that it requires that the bootloader is capable of booting custom recoveries, which the present Verizon SGS3 bootloader is capable of doing.
Thus, it's very important that folks do not apply any over-the-air (OTA) update, until it is confirmed that custom recovery booting remains intact.
If it eventually arises that booting from a stock kernel/recovery is necessary, then it's likely a bunch of kernel bugs will have to be fixed, and it might still have compatibility issues observed in previous kexec attempts. It's linked in the blog post, but there's a bit more of a technical description of the hardboot approach in this old thread.
Thanks to invisiblek and captjtkirk for testing.
you guys are awesome xda has the best devs ever! I worship you guys!
Wow! Thanks for taking the time to do this even though you guys aren't vzw owners. Great example of how great this community is.
Sent from my DROIDX using xda app-developers app
Unbelievable...you guys are awesome.
Jelly Bean here we come!
mkasick said:
Thus, it's very important that folks do not apply any over-the-air (OTA) update, until it is confirmed that custom recovery booting remains intact.
Click to expand...
Click to collapse
Forgive my paranoia, but does Verizon have the ability to force an OTA without us pressing an "OK" button?
Thanks to all who worked on this, you're awesome!
jh120 said:
Forgive my paranoia, but does Verizon have the ability to force an OTA without us pressing an "OK" button?
Thanks to all who worked on this, you're awesome!
Click to expand...
Click to collapse
nope. you have to accept the OTA
Just a question does the kexec allow the sgsiii to use both cores. I have heard that kexec on both the droid razr and droid 3 doesn't allow for dual core yet. Any such issues with sgsiii or is it too soon to tell?
Sent from my DROID X2 using xda app-developers app
Neverendingxsin said:
nope. you have to accept the OTA
Click to expand...
Click to collapse
Depends. My rezound didn't ask. I would wake up with my phone in recovery. It would fail to install the update because the stock recovery wasn't there but it never gave me a choice to install or refuse
Sent from my ADR6425LVW using Tapatalk 2
Say we needed to return to stock, can we just use Odin, flash back the ROM or would their be a bit more to it?
And THANKS! You are just missing the raised finger picture to Verizon over this.
densetsu86 said:
Just a question does the kexec allow the sgsiii to use both cores. I have heard that kexec on both the droid razr and droid 3 doesn't allow for dual core yet. Any such issues with sgsiii or is it too soon to tell?
Sent from my DROID X2 using xda app-developers app
Click to expand...
Click to collapse
I know this was an issue back in April(?) I haven't read anywhere that this has changed and I am curious to know this as well.
skennelly said:
I know this was an issue back in April(?) I haven't read anywhere that this has changed and I am curious to know this as well.
Click to expand...
Click to collapse
According to Noobnl in the IRC channel, the dual core thing isnt an issue since its a hard reboot so it reloads the bootloader; "this is a more advanced form kexec."
Glad to see some love from familiar faces. This is one if those times when i nuts being on sprint. From the galaxy tab, to the og epic, to the touch, sprint has allowed great things to happen on their devices. Now in big red, it's great to see we can use/reuse stuff across networks.
Big thanks!
Sent from my DROID RAZR using Xparent ICS Tapatalk 2
ceo.mtcl said:
Good luck guys.
☞ sent from my GS3
Click to expand...
Click to collapse
+1
densetsu86 said:
Just a question does the kexec allow the sgsiii to use both cores.
Click to expand...
Click to collapse
In short, yes.
Longer answer:
Traditionally kexec works by having one instance of the kernel boot a second instance directly, that is, by avoiding the bootloader. For this to work, every kernel driver has to shutdown in such a way that the same driver (in the kexec'd kernel) can revive and restart the hardware it controls.
The problem is that some, maybe many, drivers aren't actually capable of doing that. For the most part, it's a feature only needed by kexec, so unless the device manufactuer is specifically targetting kexec support, usually one or more drivers will put some part of the hardware in a confused state. That's the main source of compatibility bugs with kexec.
Now, what we do in the kexec hardboot approach is use the Linux kexec infrastructure to load and stage a new kernel in memory. Then we perform a hardware-level reboot, reinvoke the bootloader, and then at the very beginning of the recovery kernel code, we check to see if there's a kexec'd kernel out there in memory and if so, jump to that instead.
The advantage with this technique is that once the kexec'd kernel is booted, the environment is the exact same as if it was a kernel flashed to the device--there shouldn't be any hardware compatibility issues.
As it turns out, the one compatibility thing we have seen, which is unusual reboot behavior, isn't actually an artifact of kexec. The same thing would happen if you flashed a "boot kernel" to the recovery partition and booted it directly.
---------- Post added at 09:30 AM ---------- Previous post was at 09:28 AM ----------
ErylFlynn said:
Say we needed to return to stock, can we just use Odin, flash back the ROM or would their be a bit more to it?
Click to expand...
Click to collapse
This is a temporary mechanism. To return back to the stock kernel, simply reboot the device.
To remove the custom recovery and fully flash back to stock, yes, you would use Odin.
Great work guys. You guys are awesome.
Amazing news!
So when you say you just reboot to get back to the stock kernel, is it a certain way of rebooting?
As in, if you were running soap and a kexec aosp kernel and rebooted and it forced you to the stock Samsung kernel, the phone wouldn't boot right?
Sent from my ADR6425LVW using xda app-developers app
Related
Keep a stable stock rom, Keep your recovery, and run a custom built rom like CM9!
First, credit to all the peoples threads I'm linking to, especially bbelos, mkasick, rothnic and CVPCS, invisiblek and Beanstown106.
Neyenlives for inspiring me to do this with his cm9 install post http://forum.xda-developers.com/showthread.php?t=1774408
I take no credit, and thats why I'm not just linking a fixed up rom. This is just my preferred way to run these
I didn't want to give up my stock (or beans) rom for a buggy cm9.
Before you start, if you haven't already, BACK UP YOUR IMEI!!!!
http://forum.xda-developers.com/showthread.php?t=1791291
just to be safe
You can dual boot using Cyanogen Mods Team Epic dual boot method (FakeCWM) which will install on the EMMC:
http://www.epiccm.org/2012/07/dualboot-cm9-on-sgs3-lte-sprint-t.html
The link tends to break, so if it doesn't work just go to their blog (maybe even donate to them!)
I am using the the CWR that rothnic put together with mkasick's kexec kernel
http://forum.xda-developers.com/showthread.php?t=1773514
I had started with the twrp from that post, but it didn't recognize my internal sdcard.
Rothnic pointed me in the right direction to "add one line to Invisiblek's updater-script that "flashes" the boot.img to the bootloader partition in the multi boot folder."
so take cm9 rom:
invisblek's http://goo.im/devs/invisiblek/i535/roms
Beans build of CVPCS': http://goo.im/devs/B...ICIAL-d2vzw.zip
and unzip it, and open the file
\META-INF\com\google\android\updater-script
with notepad++ on windows http://notepad-plus-plus.org/
or text wrangler for mac http://www.barebones.com/products/textwrangler/ (thanks usatf1290)
add in this line
package_extract_file("boot.img", "/dev/block/mmcblk0p7");
so that it is 3rd to last in the script
make sure you have the unix EOLs flags as mentioned here
http://boardreader.com/thread/update_zip_error_status_6_677jjXi0hq.html
And then add a cm9 boot.img into the root
invisiblek's , http://goo.im/devs/invisiblek/i535/roms/boot.img
Bean's http://goo.im/devs/B...zw/cm9/boot.img
zip up your system and META-INF folders and your boot.img and
flash it in place of the CM9 nightly build.zip mentioned in the team epic instructions
also get gapps from here http://goo.im/gapps and
flash in fake cwr after flashing cm9
Hopefully invisiblek and others will start packaging their original roms in this format so we can just dual boot them.
Thanks again everyone for your hard work.
So, you'd just do a reboot to get back to the Stock Rom?
And if you want to go back to CM9 from stock, you'd have to reflash the cm9 correct? and would that start the rom from scratch again?
Once in cm9, if you reboot, it will put you into recovery again. From there you either reboot system and that takes you back into stock, or, you install zip, install from internal sdcard, go to multi boot/cm9/boot_cm9.zip and that will take you back to cm9, just as you left it, not from fresh install.
Keep stock, keep recovery , keep custom kernel rom!
If the reboot options are eventually set up properly in the cm9 (or any custom rom) rebooting from cm9 can put you right back in cm9, I think.
Sent from my SCH-I535 using Tapatalk 2
silasrye said:
Once in cm9, if you reboot, it will put you into recovery again. From there you either reboot system and that takes you back into stock, or, you install zip, install from internal sdcard, go to multi boot/cm9/boot_cm9.zip and that will take you back to cm9, just as you left it, not from fresh install.
Keep stock, keep recovery , keep custom kernel rom!
If the reboot options are eventually set up properly in the cm9 (or any custom rom) rebooting from cm9 can put you right back in cm9, I think.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot! Will try this now!
---------- Post added at 06:00 PM ---------- Previous post was at 05:38 PM ----------
Good stuff!
Thanks for the information.
I think i might make a video guide on this. Im excited. Haha:laugh:
You should, it's very exciting, I wanted to make one, but the only camera I've got is on my phone.
I still would love to see the bootloader unlocked, but really, dual booting with a stable rom as backup is pretty sweet. At this point I'm looking forward to the ril fix more than the bootloader cracking.
Sent from my SCH-I535 using Tapatalk 2
silasrye said:
You should, it's very exciting, I wanted to make one, but the only camera I've got is on my phone.
I still would love to see the bootloader unlocked, but really, dual booting with a stable rom as backup is pretty sweet. At this point I'm looking forward to the ril fix more than the bootloader cracking.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I will tomorrow, when nobody is home. But I'd have to record it with my Bionic.
If you wanted to reverse this, all you would have to do is delete the multiboot folder, correct?
I'm not sure about that, it might be better to try and ask team epic
Sent from my SCH-I535 using Tapatalk 2
NightxFall said:
If you wanted to reverse this, all you would have to do is delete the multiboot folder, correct?
Click to expand...
Click to collapse
Yes that is correct. It is all consolidated in that folder. It creates separate images to be used for boot, system, and data that can be deleted easily.
Will do this when CM9 gets data Thank you!
Installed this last night, including the kexec CWM. Works great except for the data, as expected.
Wicked fast; can't wait for the RIL to be taken care of. Like someone else said, I'd rather see that happen now than bootloader unlock.
---------- Post added at 11:05 AM ---------- Previous post was at 10:49 AM ----------
Question-
Since we're using the Sprint SGS3's CM9 nightlies, will data ever work?
I mean, is team Epic working on the VZW RIL, or is someone else, or are they the same (spr/vzw)?
I'm a little confused by this bit.
If you followed the guide completely you should be using invisiblek 's cm9 for i535, Verizon. I don't really know what's the difference, but we aren't just using the sprint nightlys so I believe the goal is to achieve data at some point and that there are folks working on it.
Now I'm going to stray just a bit and mention that I believe it was dhacker that got data running on the Motorola devices,
Edit: he is working on the vzw sgs3,
Check @dhacker29 on twitter
Sent from my SCH-I535 using Tapatalk 2
silasrye said:
If you followed the guide completely you should be using invisiblek 's cm9 for i535, Verizon. I don't really know what's the difference, but we aren't just using the sprint nightlys so I believe the goal is to achieve data at some point and that there are folks working on it.
Now I'm going to stray just a bit and mention that I believe it was dhacker that got data running on the Motorola devices, I had a bionic when he was working on it. He may have some advice for figuring out a verizon lte ril.
http://droidmodderx.com/2012/02/10/ics-for-the-bionic-now-has-4g-lte-5-5-902/
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
cvpcs is heading up the effort to fix RIL. He updated IRC last night that he ruled a lot of issues out and had some plans to try a few approaches.
One difference with the VZW S3 is that I believe it is their first phone to have the LTE radio on the SOC instead as a separate package. I did notice that he has a hijack solution to automatically kexec a custom (CM) boot.img without having to go through recovery.
Basically, he is using the hijack used for the DroidX to interupt the normal initialization process. Then instead of killing all processes and substituting the custom init, he is killing all processes then kexec'ing the completely separate CM boot.img. This gives us a clean boot solution, and severability from the stock boot.img. Now that he has this working(meaning he can easily try out different builds without dealing with less clean hacks), he is putting his efforts into RIL.
So, once RIL is fixed, we should have no reason not to have a fully working CM9 and possibly CM10 build (it appears he is applying these patches to a jellybean branch).
silasrye said:
If you followed the guide completely you should be using invisiblek 's cm9 for i535, Verizon.
Click to expand...
Click to collapse
You're right, and I did.
confused myself on that one, lol...
I can't get this to work for the life of me i have tried with the touch recovery flashed manuelly and through ezrecovery app. My script editing and repackaging went off with out a hitch. once I go to fakecwm and flash boot-cm9.zip it completes the install and nothing happens so i click reboot phone and it boots into beans rom. I know my recovery is kexec compatible because I have already loaded invisibleks kernel via kexec method. Any ideas ?
Sent from my SCH-I535 using Tapatalk 2
rendering the video atm . then uplaoding to youtube
Did you remember to put boot.img into your zip?
If so I guess wait for the video. It looks like this will soon be obsolete however
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I535 using Tapatalk 2
Here's the video.
http://www.youtube.com/watch?v=emDdQmNXLi8
Sent from my locked Verizon Samsung Galaxy S III
I think this is what you meant
https://plus.google.com/105844328547178759011/posts/NaZUCL6oe1q
Yes, problem is, if there is a way to share or even copy the url of a google+ post from the Google+ app, I don't know how. Do you?
Sent from my SCH-I535 using Tapatalk 2
CyanogenMod 10.1 Unofficial
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ReadMe:
This is a beta build of cm10.1 with the new htc 3.4 kernel (compliments of intervigilium)
BUGS:
video only works on 480
slight to moderate battery drain getting better with each build.
REQUIRED:
The latest htc jellybean firmware head to this thread to upgrade firmware. Please direct all questions and issues concerning upgrade there.
DOWNLOADS:
STOP DO NOT FLASH UNTIL YOU READ THE ENTIRE OP
cm_10.1_20 June Download
CM_10.1_19 June Download
CM_10.1_18 June Download
CM_10.1_14 June Download
CM_BETA_2 Download
CM_BETA 1 Download
THANKS/CREDIT
HUGE HUGE thanks to Intervigilium for sharing his booting kernel source with us..
Cyanogenmod team
please help me justify all the time spent on these roms to my wife by considering a small donation$droyd$
How to properly run an ruu
in order to run the new 3.4 kernel you will need to install the latest jelly bean firmware.. This is how i did it and the easiest way i know how..Please do not sharp shoot my directions as i am dooing this off sheer memory so it may be a little fuzzy ... If you dont under stand something you can find it with a little google search ... lets get started:
I will not be held responsible for your phone do at your own risk
required items:
A windows computer.( you can not to my knowledge run an ruu with linux)
fastboot installed on your pc ( adb/fastboot)
the 2.35 or similar depending on your provider but you want to stay in the ice cream sandwich version ruu designed for your phone make sure it is the correct one or it will not work and may cause severe damage..(i have no link for this as i will not be the reason you flashed the wrong one sorry your on your own finding it)
htc usb drivers easiest way to install is htc sync (htc sync will automaticly install the drivers you need)
SETTING THINGS UP:
You will need to extract the ruu if it is in zip format(it needs to be a basic exe file(i always just keep it on my desktop for easy access)
boot your phone into boot loader and select fastboot this is where everything will happen.
navigate to where you have your fastboot installed in your terminal on your pc.
ITS TIME TO MAKE IT HAPPEN
using a usb 2.0 cable(3.0 will not work) connect your phone and wait for it to say 'fastboot usb'
Now lets re lock the boot loader type ' fastboot oem relock your phone should reboot
navigate back to boot loader select fastboot again
now while in fastboot usb go to your selected ruu and double click it (this will take some time to load)
follow the on screen instructions to navigate through the ruu..
if you get errors you probably didnt get the right ruu for your device.
Thats it now you will be 100% stock
GETTING THE UPDATE:
boot your phone wait a few minutes and check for ota updates in about phone.
you will likley not get the jellybean update first so be sure you take the couple updates and that you are running jellybean sense before you root again.
YOU ARE DONE
I do not recommend going and flashing the jellybean ruu because if you have problems you can not flash an ruu lower than your current hboot
NOW ROOT YOUR PHONE
I Highly Highly recomend getting kernel tuner and disableing vsync in misc..... all jitter lag freeze gone.... i will disable it in source asap...
No screen tearing and full fps seem great!
please disable vsync its un believable
Downloading now, thx for the great work
Sent from my HTC One S
proxuser said:
Downloading now, thx for the great work
Sent from my HTC One S
Click to expand...
Click to collapse
Disable vsync in kernel tuner..
Sent from my One S using xda premium
Please disregard the android.com camera and mirror ... Forgot to remove em... Won't forget next time..
Sent from my One S using xda premium
I wish I could have One s S4 instead of S3 Looks great
Donated 10$ will donate more later
Great work thank you
Donate guys
I'm so happy you guys have collaborated on this.
It was literally yesterday I posted in the Q&A asking when we might see Linux 3.4 for AOSP. Everyone else I have seen using 3.4 has seen vast improvements compared to older versions.
I will be more than willing to test this everystep of the way, in fact I'm about to flash it right now!
EDIT:
Wiped everything about 5 times, flashed in recovery, rebooted flasheed boot.img in bootloader, rebooted and it was still on splash screen after about 5 minutes?
Dirty flashed and working now
This and a Sense 5 port coming?! Things are moving quite fast now for our loved device. Can't wait to try a stable release.
Awesome rom !!!!
Enviado desde mi One S usando Tapatalk 2
CazeW said:
This and a Sense 5 port coming?! Things are moving quite fast now for our loved device. Can't wait to try a stable release.
Click to expand...
Click to collapse
Something else might just be coming soon...
I am experiencing very regular reboots roughly every 10 minutes.
What voltages is it running stock 1150mV for all frequencies? My phone is very sensitive but still excited to help get this thing going!
usaff22 said:
Something else might just be coming soon...
Click to expand...
Click to collapse
Tell it :$
RichardW1992 said:
I am experiencing very regular reboots roughly every 10 minutes.
What voltages is it running stock 1150mV for all frequencies? My phone is very sensitive but still excited to help get this thing going!
Click to expand...
Click to collapse
Did you get kernel tuner and disable vsync..?
Sent from my One S using xda premium
$droyd$ said:
Did you get kernel tuner and disable vsync..?
Sent from my One S using xda premium
Click to expand...
Click to collapse
Certainly did, and it has successfully disabled. Just getting very frequent reboots. I might try another fresh install but I think its just my phone being extra temper mental.
RichardW1992 said:
Certainly did, and it has successfully disabled. Just getting very frequent reboots. I might try another fresh install but I think its just my phone being extra temper mental.
Click to expand...
Click to collapse
Its the kernel at this point ..its not quite stable yet... Although it is the kernel made by htc for our phone there are a lot of factors here... Try ondemand gov.. Tinker in kernel tuner this is beta so if you find a way to make it more stable please tell... Disable hw overlays and those things in dev options like we used to..
Sent from my One S using xda premium
Once I start building linaro I will post in the second post if any one wants to try custom versions otherwise in each ROM I will only add what's committed to repo to keep it stock for every one...I know that's the way you cm users like it.... All cm all the time lol.
Sent from my One S using xda premium
GUMMY
As of October 9, 2014 Team Gummy has disbanded. The final M4 release can be found here:
M4 Final Release
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Gummy ROM is made for speed, stability and to stay as closely in line with AOSP as possible while still supporting a large amount of devices and giving you all of the features you love. It isn’t slowed down by features you’ll never use nor is it so slim as to be just another AOSP build.*
Features:
* New base built from AOSP
* Status Bar Mods
* Hardware Key Mod
* Many Wallpapers
* Performance Control
* Application Permission Controls
* Carrier Label Options
* Lock clock widget
* QuickSettings
* Theme Manager
Device Specific:
Whats not working...
* what else (you tell us)
ChangLOG:
Please review out Gerrit instance to keep up with changes daily...
Instructions for installations:
1. Download ROM
2. Download Gapps
3. Push to sdcard
4. Reboot Recovery
5. Wipe Data and Cache
6. Install ROM
7. Install Gapps
8. Reboot System
Contributions:
- Thank you to Cyanogenmod for device and hardware repositories. Without this, porting * * Gummy to QCOM devices would have been nearly impossible.
- Thank you to Google for the best source code.
- Androidfilehost.com for hosting our file servers!
Team Members: In alphabetical order
Primary Developers:
Cphelps76, Kejar31, DHacker29
Developers and Device Maintainers:
apascual89, Bkjolly, Buckmarble, BytecodeMe, Hashcode, hedwig34, Papi92, TDM
Artwork direction and development
Cphelps76, Kejar31
Github- https://github.com/TEAM-Gummy
Gerrit- http://review.gummyrom.com/#/q/status:open,n,z
Twitter- @gummyRom
GAPPS - we now recommend PA-Gapps
As of 2/19 the build is know know as d2lte. You can download it here:
Gummy ROM
BOOM! I was hoping for a pure AOSP and/or Gummy.
I've heard some good things about Gummy. Can't wait to try it out. But before I go through the trouble of flashing and such, is there circle battery w/ percentage on this? That's ultimately the deal breaker for me so far on KitKat
DubleJayJ said:
I've heard some good things about Gummy. Can't wait to try it out. But before I go through the trouble of flashing and such, is there circle battery w/ percentage on this? That's ultimately the deal breaker for me so far on KitKat
Click to expand...
Click to collapse
Yes, circle battery w/ percentage is included. Using it myself right now.
Sent from my SCH-I535 using Tapatalk 2
Everybody make sure you are using the latest recovery . twrp 2.6.3.1 works for kit Kat previous versions do not.
Sent from my SCH-I535 using Tapatalk 2
Have you tested any of the custom kernels? I assume BMS and KT work, as they work with all the CM11 builds out there, but I thought I'd ask.
My deal breaker would be with Tap-to-Pay. Will this work with Google Wallet's TTP?
Downloading now. Really hoping this one doesn't have the FC and random reboot issues like some of the others.
chad783 said:
My deal breaker would be with Tap-to-Pay. Will this work with Google Wallet's TTP?
Click to expand...
Click to collapse
No Verizon phone will, due to the ongoing disagreement VZ has with the Google payment method. Don't expect ANY rom to come out with functioning tap-to-pay until Verizon works out their beef with Google. You can try some of the hacks people have posted for 4.3 roms, but I haven't seen anyone report that it worked on a 4.4 rom; make sure you use one of the older Wallet versions, because all newer versions for VZ devices have that functionality broken.
beepea206 said:
No Verizon phone will, due to the ongoing disagreement VZ has with the Google payment method. Don't expect ANY rom to come out with functioning tap-to-pay until Verizon works out their beef with Google. You can try some of the hacks people have posted for 4.3 roms, but I haven't seen anyone report that it worked on a 4.4 rom; make sure you use one of the older Wallet versions, because all newer versions for VZ devices have that functionality broken.
Click to expand...
Click to collapse
Other roms have got TTP to work.
Also, does FB sync with the contacts?
chad783 said:
Other roms have got TTP to work.
Click to expand...
Click to collapse
Yes, other 4.3 roms got it to work, through using the hack and an older version of Wallet.... which I already said was the case. No one has successfully had T2P work with Wallet on a 4.4 rom on a VZ Samsung device yet... at least not that's being reported on xda. You will not find T2P working on a flashable rom until Verizon and Google settle their dispute; devs are not going to incorporate the hack because it works for some and not for others.
If you need T2P, try the 4.3 hack and report back to us if it worked... otherwise, stick with a hacked 4.3 rom if you need the functionality.
---------- Post added at 01:07 PM ---------- Previous post was at 12:45 PM ----------
FYI... just flashed and didn't get a data connection. Tried the usual techniques to get it to work, but no dice. :/
On it an loving it. Great work. Only other thing I need on this ROM is RAM Usage Bar on Recents and a notification status bar toggles.
beepea206 said:
Have you tested any of the custom kernels? I assume BMS and KT work, as they work with all the CM11 builds out there, but I thought I'd ask.
Click to expand...
Click to collapse
I have not but I see no reason why they wouldn't work. Let us know how it goes
beepea206 said:
FYI... just flashed and didn't get a data connection. Tried the usual techniques to get it to work, but no dice. :/
Click to expand...
Click to collapse
Data has been working well for me. Sometime it takes a few minutes to hook up but has always come on eventually. Check under status your IMEI and see if you didn't lose it.
thanks running nice havent ran into any problems :good:
hedwig34 said:
Data has been working well for me. Sometime it takes a few minutes to hook up but has always come on eventually. Check under status your IMEI and see if you didn't lose it.
Click to expand...
Click to collapse
Ahh good call. I believe my IMEI was there (I glanced really fast), but it might not have been. Does a firmware flash remedy that? I've never had that issue before.
No a firmware flash won't do it. Best to flash to a backup where it was there. Then make backup of the IMEI. There is a script I think on xda that will do it. I keep a copy of the back on my PC too just in case.
Sent from my SCH-I535 using Tapatalk 2
beepea206 said:
Ahh good call. I believe my IMEI was there (I glanced really fast), but it might not have been. Does a firmware flash remedy that? I've never had that issue before.
Click to expand...
Click to collapse
hedwig34 said:
No a firmware flash won't do it. Best to flash to a backup where it was there. Then make backup of the IMEI. There is a script I think on xda that will do it. I keep a copy of the back on my PC too just in case.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Here's the link you were looking for - http://forum.xda-developers.com/showthread.php?t=1852255
I did method A and B just to be safe
Nice work. Just an FYI Nightly is spelled wrong in the title. Keep up the good work!
Sent from my SCH-I535 using xda app-developers app
DubleJayJ said:
Here's the link you were looking for - http://forum.xda-developers.com/showthread.php?t=1852255
I did method A and B just to be safe
Click to expand...
Click to collapse
Perfect. Thx! I didn't know I could do this from a terminal, so now I'm set!
Please forgive me for the Noob question. This is my first time having a device with an unlocked bootloader so I'm not used to searching or even discussing custom kernels. Just wanted to do the smart thing and ask questions before I do something that could potentially cause harm to my phone. I would really like to test one out and experience the added benefits, but it looks like development for the Droid Ultra is slim. Do any of you guys know of a Custom Kernel that works with the Droid Ultra? I am currently on Snakes's Venom 4.4.4 Moto X Port Build #96. My current Kernel version is: 3.4.42-gb444bf1-00004-g6b785f7. I downloaded "Faux123 Kernel Enhancement" and within the Kernel Download section, there are a few downloadable kernels. "ghost-faux123-kk443-012u.zip" being one of them. Are these safe to use on my device? Thanks a head of time for any help!
Radiohead84 said:
Please forgive me for the Noob question. This is my first time having a device with an unlocked bootloader so I'm not used to searching or even discussing custom kernels. Just wanted to do the smart thing and ask questions before I do something that could potentially cause harm to my phone. I would really like to test one out and experience the added benefits, but it looks like development for the Droid Ultra is slim. Do any of you guys know of a Custom Kernel that works with the Droid Ultra? I am currently on Snakes's Venom 4.4.4 Moto X Port Build #96. My current Kernel version is: 3.4.42-gb444bf1-00004-g6b785f7. I downloaded "Faux123 Kernel Enhancement" and within the Kernel Download section, there are a few downloadable kernels. "ghost-faux123-kk443-012u.zip" being one of them. Are these safe to use on my device? Thanks a head of time for any help!
Click to expand...
Click to collapse
I don't believe there are any custom kernels for the droid ultra/maxx/mini. The kernel you are looking at is, I'm pretty sure, for the Moto X. You could use it but you'd also need a moto x ROM, and bootloader maybe, (it's been a while since I had one of these devices) for it to work.
The rom you are currently using is a Ghost Rom with modifications to make it run on the Maxx/Ultra. The kernel that it uses isn't a maxx kernel, and won't run with a maxx boot.img.
While safe is a really relative term... With an improper kernel one of the worst problems you could have is not being able to boot, or a boot loop. If you make a backup before you start, you should be able to flash back to the backup and be working again. The faux123 kernel was originally said to work for the maxx also, same kernel.
All of that said, insert general disclamer here... (I take no responsibility for what you would like to try on your phone, I am however flashing it now)
edit: I flashed and it boots fine, I will let you know if I find any glaring issues.
edit2: On the stock droid maxx, active notifications aren't working, Your mileage may vary with the TopSnake rom.
hijjt said:
The rom you are currently using is a Ghost Rom with modifications to make it run on the Maxx/Ultra. The kernel that it uses isn't a maxx kernel, and won't run with a maxx boot.img.
While safe is a really relative term... With an improper kernel one of the worst problems you could have is not being able to boot, or a boot loop. If you make a backup before you start, you should be able to flash back to the backup and be working again. The faux123 kernel was originally said to work for the maxx also, same kernel.
All of that said, insert general disclamer here... (I take no responsibility for what you would like to try on your phone, I am however flashing it now)
edit: I flashed and it boots fine, I will let you know if I find any glaring issues.
edit2: On the stock droid maxx, active notifications aren't working, Your mileage may vary with the TopSnake rom.
Click to expand...
Click to collapse
Uninstall active display and reinstall it. The kernel is fully compatible with maxx stock Roms
Sent from my XT1080 using XDA Free mobile app
hijjt said:
The rom you are currently using is a Ghost Rom with modifications to make it run on the Maxx/Ultra. The kernel that it uses isn't a maxx kernel, and won't run with a maxx boot.img.
While safe is a really relative term... With an improper kernel one of the worst problems you could have is not being able to boot, or a boot loop. If you make a backup before you start, you should be able to flash back to the backup and be working again. The faux123 kernel was originally said to work for the maxx also, same kernel.
All of that said, insert general disclamer here... (I take no responsibility for what you would like to try on your phone, I am however flashing it now)
edit: I flashed and it boots fine, I will let you know if I find any glaring issues.
edit2: On the stock droid maxx, active notifications aren't working, Your mileage may vary with the TopSnake rom.
Click to expand...
Click to collapse
This is correct. The port runs the Moto X kernel.
Radiohead84 said:
Please forgive me for the Noob question. This is my first time having a device with an unlocked bootloader so I'm not used to searching or even discussing custom kernels. Just wanted to do the smart thing and ask questions before I do something that could potentially cause harm to my phone. I would really like to test one out and experience the added benefits, but it looks like development for the Droid Ultra is slim. Do any of you guys know of a Custom Kernel that works with the Droid Ultra? I am currently on Snakes's Venom 4.4.4 Moto X Port Build #96. My current Kernel version is: 3.4.42-gb444bf1-00004-g6b785f7. I downloaded "Faux123 Kernel Enhancement" and within the Kernel Download section, there are a few downloadable kernels. "ghost-faux123-kk443-012u.zip" being one of them. Are these safe to use on my device? Thanks a head of time for any help!
Click to expand...
Click to collapse
Ok, thank you guys for the info! I appreciate it!
akellar said:
Uninstall active display and reinstall it. The kernel is fully compatible with maxx stock Roms
Sent from my XT1080 using XDA Free mobile app
Click to expand...
Click to collapse
Any new updates with running the faux kernel? I'm about to jump in and try it out also.
Answered my own question, Faux's kernel works great with my Droid Maxx running Topsnake's 4.4.4 Moto X ROM. Installed Faux123 Kernel Enhancements and is currently tinkering around with the billion new settings.
Here's the FAQ for the Kernel
Here's the link to the discussion.
Here are the pics:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Antutu Benchmark score:
Overclocked to 1.944 ghz
Stock
CAUTION with 5.1.1 UpdateG925PVPU2B0F7I've been spending some time reading T-mobiles issues with the update. This isn't a super new conversation, but is probably new to many Sprint users. The update appears have rollback protection, which effects both kernel and bootloader from what they are saying... Which I find slightly confusing since I didn't think that their was a locked bootloader on the US versions (maybe someone can assist with that)
Figured we could start the conversation early for Custom Root/Recovery/etc. users, so that we may save some of us some trouble with Soft/Hard brinks in the next week or so.
This is the thread I've been looking at.
http://forum.xda-developers.com/tmobile-galaxy-s6-edge/general/psa-odin-5-1-1-t3136151
EDIT:
NO, the bootloader is not locked with the 5.1.1 update.
Rather, "Factory Reset Protection" (an Android thing - not a Samsung thing!) is now an option, which allows you to lock the bootloader yourself, protecting your device from someone installing a custom recovery, wiping your device and making it their own. It makes the device somewhat less valuable, and therefore (supposedly) less likely to be stolen.
The 5.1.1 upgrade looks to be a "permanent" upgrade, meaning we're not able to revert back to 5.0.2 kernels and recoveries.
So, I would suggest to sit tight with your current set up. In order to customize our devices we will need to wait for:
A) Root for 5.1.1
-Root has been achived: http://forum.xda-developers.com/spr...elopment/5-1-1-stock-of7-kernel-root-t3153396
B) Samsung to post the source code for the new kernel.
C) Custom Recovery
-Recovery has been achived:
Once we have the above, we can get back to modding our devices.
If I'm wrong, someone please correct me.
Interesting article, I remember several other older Samsung devices where you could not downgrade bootloaders and modems. IE Galaxy S3, note 3, s5. But there was still root, Roms and the ability to flash kernels. Hopefully there's no need to go back anyway. The kernel thing is something new so I may hold off on upgrading. Thanks for the info
Soooperstar said:
Interesting article, I remember several other older Samsung devices where you could not downgrade bootloaders and modems. IE Galaxy S3, note 3, s5. But there was still root, Roms and the ability to flash kernels. Hopefully there's no need to go back anyway. The kernel thing is something new so I may hold off on upgrading. Thanks for the info
Click to expand...
Click to collapse
This is my first Samsung, so the whole root recovery process was almost too smooth since I've been on the HTC side for 5 years. Unlocking bootloaders, S-off and requesting tokens to push.. Ugh, as must as I likes HTC and Sense, that sucked.
I think I'm holding off as well, untill Sac23/ Ram9200 might have spare time to look over the update first and make sense of it all and could at least get it to where V.2 is right now. But it sounds like the Kernel could be our hold up, without Hybridmax's current support.
wildjeep said:
This is my first Samsung, so the whole root recovery process was almost too smooth since I've been on the HTC side for 5 years. Unlocking bootloaders, S-off and requesting tokens to push.. Ugh, as must as I likes HTC and Sense, that sucked.
I think I'm holding off as well, untill Sac23/ Ram9200 might have spare time to look over the update first and make sense of it all and could at least get it to where V.2 is right now. But it sounds like the Kernel could be our hold up, without Hybridmax's current support.
Click to expand...
Click to collapse
Yea but based off of my years of experience and having Samsung devices, I'm pretty sure that someone will find a way moving forward, but going back probably won't happen. I too had an HTC evo years back lol and I couldn't stand the root process. I feel your pain. But yea it may be wise just to wait for a while on the update
Root added
wildjeep said:
Root added
Click to expand...
Click to collapse
I've been keeping up with the thread. Looks like T-Mobile got it worked out and looks like it didn't affect the international variant. US cellular just got it. Let's see what happens with them
Soooperstar said:
I've been keeping up with the thread. Looks like T-Mobile got it worked out and looks like it didn't affect the international variant. US cellular just got it. Let's see what happens with them
Click to expand...
Click to collapse
I agree. Definitely a step in the right direction.
Any Sprint rep on here that can tell us when the update is going live?? Someone has to know something ..
just heard 6/30.
Sent from my SM-G925P using XDA Free mobile app
Got it today
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G925P using Tapatalk
Poxie said:
Got it todayView attachment 3384936
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
Thank you for the update. Were you rooted before updating?
wildjeep said:
Thank you for the update. Were you rooted before updating?
Click to expand...
Click to collapse
No
Sent from my SM-G925P using Tapatalk
Poxie said:
No
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
That makes sense. Thank you for the confirmation. 5.1.1 is only a stock update for the time being
http://forum.xda-developers.com/showthread.php?t=3083442
International got twrp working for their phones. We will see if someone gets something working for us
Sent from my SM-G925P using Tapatalk
xadidas4lifex said:
http://forum.xda-developers.com/showthread.php?t=3083442
International got twrp working for their phones. We will see if someone gets something working for us
Sent from my SM-G925P using Tapatalk
Click to expand...
Click to collapse
Thanks for the update, I'll add that Link to the OP