Any information on a kernel in the works for 6.0? Battery drain is rediculous (40-50%) from the stock kernel.
No active devs for any verison of this phone, really. No ROMs, no kernels, nothing.
Clear your cache partition and reboot.
What carrier/model number do you have?
Metropcs
Related
All,
Coming from Verizon Gnex and I'm reading the Verizon S3 forums and getting a bit confused on the flashing parts of this phone. I see the firmware baseband is "HE" as of a couple of days ago. I also see options to flash the radios and modem? What is the modem for? I never had to flash a modem for my GNEX. Am I missing anything else that I need to flash?
Also, if you would be so kind....I am planning to keep stock for the near future, so after I root and unlock. I need to flash the latest stock ROM which is "HE" then latest radios then modem? What is the latest version of each?
And one last thing, is it the same as GNEX where all I have to do when flashing something is just wipe cache and dalvik cache?
The current verizon updated stock baseband is vrlhe. It includes the most recent modem (radio) from that update. Once you start flashing rom's, the entire portion of the base is dependent on what the developer has built the rom on, and you can choose what radio works best for your phone. Example: synergy R73 is based on vrlg1, but flashing the vrlhe radio with it may give you better cell service.
And, NO on just wiping caches. That's only Ok if updating the same rom, based on the devs guidelines on his updated build. Full wipes between rom's always. It's not a dedicated developers device.
And before you flash anything read the thread in development on backing up your IMEI. There is a bug in this s3 variant that can lose your id when flashing. This is important if you don't want a major headache. And you'll need to unlock your bootloader too
Ha, or maybe he really likes puppies cause he'll end up with a nice chew toy for one...
Thanks for the info guys. And yes, I understand not to dirty flash when switching roms. I usually dirty flash when I'm upgrading from the same rom ie..Bugless Beast...I've dirty flashed the past 4 upgrades.
Was just confused from reading the forums of radios then I see modem....I'm like huh? But got it. Radio=Modem but refer as Radio.
I dont know if its my phone or what but I haven't had any luck with AOSP ROMS on this phone. It seems like there's always some sort of bug that just kills it. I flashed a CM10.2 rom that felt like speed of lightning but was bugging out. I tried ecilpse and some others but all were to buggy for me. I recently tried to flash liquid cause I wanted to run something else other than touchwiz but it ruined my phone and now I cant flash custom ROMS(i have a help thread up..feel free).. Anyone else having bad luck on these AOSP ROMS
Not what you want to hear, but I'm having no issues with flashing new ROMs. I'm only using LiquidSmooth and waiting/hoping for a 'complete' 4.3 version, but again, no problems with flashing to a new ROM. I have been running LS2.9 (4.2.2) for several weeks and on Sunday flashed up to LS2.10 (4.3) but went back to 2.9 because when I mirror my phone on my AppRadio3, it doesn't auto-rotate my screen to landscape, so I have a portrait orientation of my phone on the radio display, which makes it so small as to be unusable.
I don't recall what method I used to root my phone, but I'm using TWRP 2.6.3 to perform a) a clean wipe every time (Factory Reset + System), then b) install the new ROM, and c) a final reboot back in to recovery and flash the latest gapps image. Does it take a little longer to follow this process? Sure, but it's a reliable process that means I don't have issues afterwards to mess with, so the extra time spent on the front end is worth it to me.
I've had moderate success with the AOSP ROMS. Each one seems to have it's own small bugs, but the AOSP ROMs that I've tried didn't have anything that ruined functionality. Been running Dirty Unicorn ROM for the past couple days and it is really solid. Haven't noticed any issues at all with it yet.
It's got to be your downloads or install process. Do you check MD5? If no then start. Remember just wipe data for each install. Updater-script in ROM zip wipes system for you. Cache resides in data. Do NOT restore system data using TiBu. Other than that I don't know what else to tell ya bud :/
Sent from my SCH-I535 using Tapatalk
Haven;t had any trouble with AOSP flashes, but many of the ROMs or maybe most have some bugs. All the so called AOSP ROMs are built off the same base, CM10. None of them support all the hardware and software features that Tocuhwiz supports. I find the custom TW ROMs far superior in features and as good or better in speed as well.
Make sure you are flashing a compatible Kernel when you switch between CM based ROMs and TW based
I've got a rooted XT926 with unlocked bootloader. I've flashed plenty of custom ROMs on the phone including ones running 4.1, 4.2 and 4.3. I'm gradually moving back to earlier stock-based ROMs because, while the extra features are cool, I grew tired of random main functions that didn't work properly and my battery life was getting progressively worse.
Now I'd like to know for sure I'm running the stock kernel. How do I determine this? My kernel version is 3.0.31-g101ca72. The date of "Thu May 30 18:22:06 CDT 2013" also appears in this subheading of Settings/About Phone.
If I'm not running the stock kernel, where do I find it? I've done plenty of searching but can't seem to find a downloadable stock kernel that I could simply flash from TWRP recovery. Most of the posts of this nature are about unrooting and restoring stock. I don't want to do that. I want my phone to remain rooted but I'd like to know that I'm either on the stock kernel or can find it and flash it.
Not really sure how to check, but if you fastbooted back to stock you have the stock kernel. If you found a stock based ROM and flashed via recovery, unless stated otherwise in the post it should have the stock kernel. And have you tried arrrghhh's kernel? It works really well. It's for all msm8960 (or whatever msm we are) devices so it will work as long as you download the stock version.
Sent from my MB886 using Tapatalk
What would be the point of using arrrghhh's kernel with a stock rom? Or, what does his kernel do differently than the stock one?
At the moment I'm running RageHD 2.3, a straight-forward stock-based ROM running 4.1.2. It's doing pretty much what I want -- everything works, smooth and solid, better battery life than I was getting with 4.2.2 and 4.3 ROMs and improved signal strength. Still, I read from time to time that custom ROMs tend to give improved functionality and lessened bloat but that they also shorten battery life, sometimes substantially. To test this myself I need to know that either I'm on a stock kernel now or that I can find and flash a stock kernel.
Hello,
I searched for this issue but couldn't find the exact problem being experienced by others, so I'm asking about it now.
So I'm using the latest MultiROM and Lollipop firmware (the 02/09 one). I simply can't get any Lollipop ROM to stop bootlooping with a recent kernel. Boeffla, AK, Tyr, etc. all bootloop with every LP ROM I've tried, regardless if they're set as primary or secondary in recovery.
The only way I can get a ROM to boot is with a kernel meant for CM11/S, like AK r77 and Sensei r77, though I can't get the radios to work with these. But newer kernels simply won't work, period.
Am I missing something here? I thought the latest firmware and a recent kernel with kexec-hardboot was all I needed.
Edit: Also seems to happen with a fresh install of the latest CM nightly. Using the default kernel that comes with CM, too. There must be something that I am missing here...
Hi guys,
I'm experiencing reboots when I push my phone hard. I typically have reboots when I'm using Chrome to view webpages in desktop mode or when using GPS (Google Maps, Waze). I've used two different roms and a few different kernels, but seem to be experiencing the same reboots across all platforms (and various rom/kernel combinations). Any help would be greatly appreciated!
Device: T-Mobile Samsung Note 5 64GB
Recovery: Philz Touch
ROMs used (COJ5):
Hyperdrive RLS2
Hyperdrive RLS3
fOrEvErLoCo's BrEaKdOwN R3.0.1
Kernels used:
Stock Hyperdrive RLS2 Kernel
Stock Hyperdrive RLS3 Kernel
Stock fOrEvErLoCo's BrEaKdOwN R3.0.1 Kernel
arter97 N920TW8 9.4 Kernel
arter97 N920TW8 X Kernel
SkyHigh N920T TW LL Kernel
Could this have anything to do with SuperSU?
still random rebooting.
and apparently we currently can't downgrade from COJ5? Double
Any help would be very, very appreciated. Thanks in advance!
Have you odin'd to stock + factory reset?
10-K said:
Have you odin'd to stock + factory reset?
Click to expand...
Click to collapse
As of right now I'm on jovy23's COJ5 Deodexed Stock Rooted Rom, installed after a fresh wipe of cache, dalvik, data, system, etc.
I seem to have found what was causing the reboots. I think it's giving Lastpass accessibility rights.
All throughout the initial installing of apps, the phone never randomly rebooted. Shortly after I got all my apps up and running, the reboots would begin to happen (sometimes twice in 15 minutes.)
Even on this fresh install of the deodexed stock rom, I had one random reboot. Since turning off Lastpass in Settings > Accessibility, I have experienced zero random reboots.
Did anyone else experience this? I'm wondering if it's specifically Lastpass that's giving the phone issues or Accessibility as a whole.
Will try to see if turning off Lastpass on the other kernels and ROMs helps next week and will post an update.
Thanks everyone!