Related
I checked as much as I could handle but wasnt successful in finding my specific issue..
here goes..
im running wicked sensations v2.0 on Sprint sgs3. battery life was less than desirable so I flashed k747 kernel. now I noticed my boot animation is different and seems off from the audio. I noticed the visual will be half over before the sound plays. im not able to change the boot animation either and have only a blue flashing samsung logo. any ideas on a fix or is it not fixable? ive tried flashing from the kuban but nothing changes. ive tried flashing anis with no luck. im convinced the k747 kernel has to be the culprit but thats the only issue Ive so far seen. id like to know if theres an easy fix or not?
thanks in advance for any assistance.
Go back to stock that's what runs best with wicked sensations.. I'm running the modded ma4 kernel with no issue its smooth and solid! Here try it...
boot.img,init.d, custom bootanimation & adb..
http://db.tt/IpBAdPhn
Make sure you flash the kernel cleaner first.. here it is..
http://db.tt/TOXoIaqC
ImEVO said:
Go back to stock that's what runs best with wicked sensations.. I'm running the modded ma4 kernel with no issue its smooth and solid! Here try it...
boot.img,init.d, custom bootanimation & adb..
http://db.tt/IpBAdPhn
Make sure you flash the kernel cleaner first.. here it is..
http://db.tt/TOXoIaqC
Click to expand...
Click to collapse
Very good. Thanks for your time. So with this kernel, can I change boot animations with no issues from the kuban downloader? The main issue I had was after changing the kernel to K747, I wasn't able to flash new boot animations. I love the ROM - the look of it is fantastic but it ran like the stock Sprint ROM and battery didn't last much of the day. I'm a flash fiend and found a few ROMs I like and have them in recovery and switch almost daily but Wicked is my favorite. I'll try the links and give it a go. Thanks a bunch.
harry46222 said:
Very good. Thanks for your time. So with this kernel, can I change boot animations with no issues from the kuban downloader? The main issue I had was after changing the kernel to K747, I wasn't able to flash new boot animations. I love the ROM - the look of it is fantastic but it ran like the stock Sprint ROM and battery didn't last much of the day. I'm a flash fiend and found a few ROMs I like and have them in recovery and switch almost daily but Wicked is my favorite. I'll try the links and give it a go. Thanks a bunch.
Click to expand...
Click to collapse
Update...
Ok, so I downloaded the files. I went to move them to my PC for backup purposes and noticed every app that came with Wicked is loaded on my card! Holy crap! Slight panic attack there... I'm thinking if I remove them, I lose the apps in Wicked. Can these be moved or do they have to stay on my internal SD memory? I've had other ROMs flashed and can say I've never had any of those do this. Is there a reason it's like that or is the ROM set up to put all apps on the internal SD card by default (app to SD)? If it is, it makes sense and I'll put them back where they belong so my internal memory is clean and clutter free. Can I put these into a folder on the internal memory or at least in the system app folder and still be OK?
so I was able go flash the kernel and things seem to be going well so far but I noticed my wifi is disabled. I can only use data. wifi wont turn on at all. any ideas? I've reflashed the rom amd wifi works we expected but when I flas the kernel wifi is disabled.
No I don't set the rom up to copy apps to you're SD card. Not sure why that happened to you. I know WiFi works with the stock kernel, so If your having issues flashing another kernel, then you might want to re download the kernel again and follow their instructions for flashing. I usually flash the kernel, then wipe cache, dalvik cache then fix permissions.
On the K747 kernel, you can flash the bootanimations4u file and custom boot animations should work for you.
But I've been using an app to flash the boot animations and it works perfectly fine with RomToolBox
or ( ROOT ) Boot Animation from the Play Store.
The battery issue with KToonez kernel however on JB 4.1.x based roms is there was a specific issue regarding certain
governers that use up too much bat life.
I'm running the stock MA6 JB with KToonez, It's working flawlessly and even better when its over clocked ( Heat issue
when you're doing certain things over a long period of time. ) Adding on top of that a few scripts
that also force cpu cores off when your screen is off and my phone can last 2-3 days when doing nothing.
link to ktoonez kernel on the forum is here
http://forum.xda-developers.com/showthread.php?t=1800576
Link to the bootanimation4u.zip can be found here
http://forum.xda-developers.com/showthread.php?t=2063280
If the kernel supports custom boot animations flash this and use an app that installs custom boot animations
and it should work.
Hope this info helps.
Spark91 said:
On the K747 kernel, you can flash the bootanimations4u file and custom boot animations should work for you.
But I've been using an app to flash the boot animations and it works perfectly fine with RomToolBox
or ( ROOT ) Boot Animation from the Play Store.
The battery issue with KToonez kernel however on JB 4.1.x based roms is there was a specific issue regarding certain
governers that use up too much bat life.
I'm running the stock MA6 JB with KToonez, It's working flawlessly and even better when its over clocked ( Heat issue
when you're doing certain things over a long period of time. ) Adding on top of that a few scripts
that also force cpu cores off when your screen is off and my phone can last 2-3 days when doing nothing.
link to ktoonez kernel on the forum is here
http://forum.xda-developers.com/showthread.php?t=1800576
Link to the bootanimation4u.zip can be found here
http://forum.xda-developers.com/showthread.php?t=2063280
If the kernel supports custom boot animations flash this and use an app that installs custom boot animations
and it should work.
Hope this info helps.
Click to expand...
Click to collapse
Thanks, I'll try that. I've found a bunch of boot animations I want to take a look at. I couldn't get any other kernels to work right. Everything keep the phone in an awake condition and sucks my battery dead in less than 8 hours. I've even done a full and complete wipe of everything, even the memory (just for fun and after backing it all up) and nothing works well but the stock kernel. Good news is, I get fantastic battery life after nuking my memory. Perhaps some lingering file was the cause? Either way, I could never get K747 to work without keeping my phone awake and I'm pleasantly content with the stock kernel now. I can go about 36 hours between charges with minimal use and using just the media player, I can easily last 12 hours. I'll definitely check out that boot animation file.
Thanks all for your help...
Awesome to hear that. Glad it worked out for you and with the stock kernel make sure it has the boot animation support otherwise
flashing the bootanimation4u file would be pointless.
UPDATE... so I just flashed v2.1. The Kuban Updater mod files are what I mistook for apps. Durrr! Only found that out when I deleted them and nothing would show up in the Updater. .. needless to say I had to reflash. Mistakes lead to discoveries I guess. So I believe I solved that issue. I noticed Awesome Beats is new. Going to play with that. Battery life is super impressive. Nice job on this...
Hey all -
I have a T-Mobile Galaxy SIII with TWRP, AOKP JB Milestone 5 and GooManager. I got a pop-up for AOKP JB Milestone 6 this morning, so I downloaded it and added that file, Lean Kernel 2.9 and gapps (latest that could be downloaded) to the flash list. I set my Dalvik cache to clear before flashing anything, then rebooted the phone to flash everything. Immediately after the flash, the phone seemed to reboot, but with a blank screen. After a while, the capacitive buttons on the front started working and when I plugged the phone into my computer the file transfer program popped up.
However ... at no point can I ever get anything to display on the screen. I've tried rebooting into recovery (volume up, home button, power button) and nothing. I don't really care about the data on my phone, I have proper backups of everything. But what I can't seem to do is get it to a point where I can recover it. What are my options here if rebooting into recovery doesn't work?
Thanks!
As an addendum, the phone is clearly booted into the OS. I have a blinking notification LED that indicates a new e-mail, and calls placed to the phone cause it to ring. I just can't see .... anything on it.
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
chuffykow said:
I was able to get into TWRP, somehow. I took out my T-Mobile SIM card and had it plugged into USB. I held down the recovery combo and then it booted up into recovery. It also displayed the Galaxy SIII white splash screen for the first time since the bad flash. What the hell.
Click to expand...
Click to collapse
so was you able to use your phone again i say go back to a nandroid you have or flash a rom that you know works good on your phone without that white screen and trouble shoot from there that it very strange indeed if you get success with the other just try posting in the ROM thread that you flashed you could possibly get more help where it happened :good:
I went back to AOKP Milestone 5 after doing a full wipe. I saw a number of graphics changes in the Milestone 6 code review, so it's possible that had something to do with it. In any case, I'm no longer panicing
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Ya its all kernel related and user error.
Aerowinder said:
Does mr6 use the 3.4 kernel? If yes, then you were using the wrong version of leankernel.
Click to expand...
Click to collapse
mt3g said:
Ya its all kernel related and user error.
Click to expand...
Click to collapse
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
chuffykow said:
I assumed it was user error. I just wanted to lay out the steps I took, so I could get some help on a recovery path. I thought that a JB based ROM would work with any kernel that supports JB. Looks like I was wrong.
Click to expand...
Click to collapse
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
mt3g said:
Nope, JB can be AOSP, TouchWiz, 4.1, 4.2, 4.2.2, 3.0 kernel, 3.4 kernel. Just need to read and make sure you know what you're doing before just doing it. That's why I frown at people being lazy (not just you) and not reading the forums and such, and just using apps to update and flash.
Click to expand...
Click to collapse
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
chuffykow said:
Thank's for the condescension, I appreciate being called lazy. I might not have an encyclopedic knowledge of Everything Android, but between the knowledge I do have and the details I read on the AOKP release page, I saw nothing that indicated I _couldn't_ run LeanKernel, especially when it was only a point release on the same ROM I was previously using.
Click to expand...
Click to collapse
calm down lol, you could have read up any of the kernel threads that there are some compatible issues with kernels and roms right now.
Aerowinder said:
I had a look at the changelog that's available on their page. It's pretty lame. http://gerrit.sudoservers.com/#/q/status:merged,n,z that one will probably have the kernel info. A good rule of thumb is when you flash a new rom, wait until the kernel is up to date (release date). For instance, don't flash a 3/01 kernel on a 4/24 rom - wait for kernel update.
I don't recommend flashing anything with the 3.4 kernel right now. Even if you manage to pull off stability, it's still laggy and eating about 3x the battery it should. This goes for the custom kernels, too. I'll put up with stability issues, but can't deal with bad battery. Already bad enough as it is. Need my phone during the day and not near a charger.
Click to expand...
Click to collapse
Thanks for the tip! I appreciate it.
Hello guys,
Since I updated to 1.40.401.8, I flashed viper latest rom. The phone heats up on minimal usage, and oh the battery....ultra drain. I can barrly make it to the middle of the day.
Anyone having the same problem after the update?
I tried to flash it again, factory reset but no use. Any ideas to fix this or should I flash the old firmware?
mr.dj26 said:
Hello guys,
Since I updated to 1.40.401.8, I flashed viper latest rom. The phone heats up on minimal usage, and oh the battery....ultra drain. I can barrly make it to the middle of the day.
Anyone having the same problem after the update?
I tried to flash it again, factory reset but no use. Any ideas to fix this or should I flash the old firmware?
Click to expand...
Click to collapse
Check over the apps you're restoring mate, keep the install clean, let it settle, set your CPU up right, install something to keep apps from starting up (auto starts) then see how the battery is, my guess is it'll be a lot better.
From that point just install the apps you need, followed by the ones you want.
Did you change up your firmware too? Obviously that should have been done but I thought I'd ask..
Hope this helps, seems obvious but its easily overlooked.
dladz said:
Check over the apps you're restoring mate, keep the install clean, let it settle, set your CPU up right, install something to keep apps from starting up (auto starts) then see how the battery is, my guess is it'll be a lot better.
From that point just install the apps you need, followed by the ones you want.
Did you change up your firmware too? Obviously that should have been done but I thought I'd ask..
Hope this helps, seems obvious but its easily overlooked.
Click to expand...
Click to collapse
what do you mean by change up the firmware? if the firmware and the rom didnt match it will fall into a bootloop . I flashed the latest firmware and a new rom with the new base. I didn't install any different apps I only use several app which are whats app, appy geek, 9gag,tasker and twitter that's almost all the app and I ran more apps in the older firmware.
I have 30% now from only 6 hours and 30 min. there is a huge difference. I will try ARHD since its almost stock but I really love viper rom its full of customization
.
Anyway, thanks a lot m8, ill flash and new rom and ill update you guys.
mr.dj26 said:
what do you mean by change up the firmware? if the firmware and the rom didnt match it will fall into a bootloop . I flashed the latest firmware and a new rom with the new base. I didn't install any different apps I only use several app which are whats app, appy geek, 9gag,tasker and twitter that's almost all the app and I ran more apps in the older firmware.
I have 30% now from only 6 hours and 30 min. there is a huge difference. I will try ARHD since its almost stock but I really love viper rom its full of customization
.
Anyway, thanks a lot m8, ill flash and new rom and ill update you guys.
Click to expand...
Click to collapse
I was under the impression that you could, some people had boot loops others didn't.
Leave all apps off, full wipe, then test.
If none of this works then I would try your luck in Viper thread.
dladz said:
I was under the impression that you could, some people had boot loops others didn't.
Leave all apps off, full wipe, then test.
If none of this works then I would try your luck in Viper thread.
Click to expand...
Click to collapse
Hey,
Its looks like an issue with viper rom, ARHD is way better, less heat and more battery for sure although I miss the customizations on the viper rom:crying:.
One thing I noticed, after flashing both roms I got the "android optimizing apps" for ARHD is was about 160 I think, while viper rom had like 240 -.-" There are a lot of things under that rom and i'm assuming they're causing the heat and battery drain.
ps. I always full wipe before flashing any rom
thanks
mr.dj26 said:
Hey,
Its looks like an issue with viper rom, ARHD is way better, less heat and more battery for sure although I miss the customizations on the viper rom:crying:.
One thing I noticed, after flashing both roms I got the "android optimizing apps" for ARHD is was about 160 I think, while viper rom had like 240 -.-" There are a lot of things under that rom and i'm assuming they're causing the heat and battery drain.
ps. I always full wipe before flashing any rom
thanks
Click to expand...
Click to collapse
Just pick the ones you need mate, I know about viper, it is a little heavy but that's just to ensure that people get what they need.
As for a different base with a different firmware its definitely possible as I'm running the 1.40 ROM with the 1.32 firmware, no overheating and no problems.
Glad your back up and running. Try leedroid too, that's the ROM I'm currently running.
Hi guys. I recently purchased this phone from t mobile and so far it has been terrible. I cannot return it because I traveled to a different country and there is no T-Mobile here, so I am stuck.
Some issues I have are:
- extreme over heating while simply using the phone to browse the internet.
- battery draining extremely fast, lasting 4 hours Max (basic usage)
I am using the Android revolution rom on 5.1 lollipop and I thought it was supposed too fix these issues. Can someone please tell me how to fix these issues? I feel ripped off and wish I bought an s6 instead
I would say you have a faulty device... ?
Did you flash the new firmware aswell? Not just the rom?
Sent from my HTC One M9 using XDA Free mobile app
dannylow79 said:
I would say you have a faulty device...
Did you flash the new firmware aswell? Not just the rom?
Sent from my HTC One M9 using XDA Free mobile app
Click to expand...
Click to collapse
I wasn't aware that you had to install the firmware as well. where can I get it?
http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678
latest firmware. Should help fix issues. If not, it's possible it is device related.
Do you use greenify or any other similar app to hibernate apps when the screen is off? Do you have a lot of apps that sync automatically throughout the day? Have you removed bloatware and other apps that run in the background that you dont use by using titanium backup or romtoolbox?
Simple things like resolving any issues with the above mentioned items can help prolong battery life by a fair bit. Kernel tweaks also help to reduce overheating / cpu usage if you dont require you're phone to run at top capacity.
with overheating you need to keep in mind this is an all metal casing on the phone ... this means it will naturally absorb a lot of heat which isnt always a bad thing as it takes some of the strain away from the phones core. Obviously if its so warm it's hot to the touch then thats definately not good. But doing a full wipe / reset / re-flash etc is worth doing to get you back to basics and then if the issue remains, and you have seen to the above tweaks like using greenify / uninstalling apps you dont need / changing apps sync frequency etc, then it is probably hardward related.
tomorio said:
http://forum.xda-developers.com/one-m9/development/firmware-red-t3097678
latest firmware. Should help fix issues. If not, it's possible it is device related.
Do you use greenify or any other similar app to hibernate apps when the screen is off? Do you have a lot of apps that sync automatically throughout the day? Have you removed bloatware and other apps that run in the background that you dont use by using titanium backup or romtoolbox?
Simple things like resolving any issues with the above mentioned items can help prolong battery life by a fair bit. Kernel tweaks also help to reduce overheating / cpu usage if you dont require you're phone to run at top capacity.
with overheating you need to keep in mind this is an all metal casing on the phone ... this means it will naturally absorb a lot of heat which isnt always a bad thing as it takes some of the strain away from the phones core. Obviously if its so warm it's hot to the touch then thats definately not good. But doing a full wipe / reset / re-flash etc is worth doing to get you back to basics and then if the issue remains, and you have seen to the above tweaks like using greenify / uninstalling apps you dont need / changing apps sync frequency etc, then it is probably hardward related.
Click to expand...
Click to collapse
I installed the android revolution rom which has no bloatware, I only have a few apps like facebook, snapchat, and twitter. The rest are never open. I have google syncing automatically. I am also currently in the process of installing the elitekernal that should help the CPU not overheat. Which kernal do you recommend? Can I use multiple kernals at one time? And yes, it eventually reaches the point where its not supposed to be that hot. I can understand if it get warm, but it really shouldn't get to the point where its hot to the touch. I really hope its not a hardware issue because then I'd have to be stuck with it.
OfficialBlox said:
I installed the android revolution rom which has no bloatware, I only have a few apps like facebook, snapchat, and twitter. The rest are never open. I have google syncing automatically. I am also currently in the process of installing the elitekernal that should help the CPU not overheat. Which kernal do you recommend? Can I use multiple kernals at one time? And yes, it eventually reaches the point where its not supposed to be that hot. I can understand if it get warm, but it really shouldn't get to the point where its hot to the touch. I really hope its not a hardware issue because then I'd have to be stuck with it.
Click to expand...
Click to collapse
as far as i know its a one kernel at a time kinda show.
I have only ever used the kernel that comes with the rom so far so cant recommend any others im afraid.
If after installing a different kernel you have the same issue and you have a set up like you've mentioned, it does sound like a hardware problem. With your setup it should very rarely get that hot unless you do a lot of flashing in a short space of time. My phone only ever gets hot to a point that i notice when i flash and set up a new rom, but it soon returns to normal.
good luck.
tomorio said:
as far as i know its a one kernel at a time kinda show.
I have only ever used the kernel that comes with the rom so far so cant recommend any others im afraid.
If after installing a different kernel you have the same issue and you have a set up like you've mentioned, it does sound like a hardware problem. With your setup it should very rarely get that hot unless you do a lot of flashing in a short space of time. My phone only ever gets hot to a point that i notice when i flash and set up a new rom, but it soon returns to normal.
good luck.
Click to expand...
Click to collapse
After installing the elitekernal my phone is stuck on the HTC logo.. it gets to the "optimizing apps" screen then restarts, and does it again.. bummer.
OfficialBlox said:
I installed the android revolution rom which has no bloatware, I only have a few apps like facebook, snapchat, and twitter. The rest are never open. I have google syncing automatically. I am also currently in the process of installing the elitekernal that should help the CPU not overheat. Which kernal do you recommend? Can I use multiple kernals at one time? And yes, it eventually reaches the point where its not supposed to be that hot. I can understand if it get warm, but it really shouldn't get to the point where its hot to the touch. I really hope its not a hardware issue because then I'd have to be stuck with it.
Click to expand...
Click to collapse
While you were still on stock, did you update the phone through Software Updates? You're likely on the originally released version of the firmware, which is probably 90% of your problems. Mismatched firmware/ROM isn't helping either.
Either return the device to stock to be able to take the OTA update, or S-Off ($25 through sunshine) and flash the latest developer edition firmware (2.8.617.4).
---------- Post added at 11:03 AM ---------- Previous post was at 11:00 AM ----------
OfficialBlox said:
After installing the elitekernal my phone is stuck on the HTC logo.. it gets to the "optimizing apps" screen then restarts, and does it again.. bummer.
Click to expand...
Click to collapse
Bro. you really got to do some reading before you just start flashing stuff. Elite is NOT compatible with 5.1 roms.
if you are on 5.1, you HAVE to use the stock kernel . There are NO custom kernels for 5.1 yet.
Restore the boot.img from the ARHD rom. Either by restoring from the backup you made before you flashed the elite kernel, by dirty flashing ARHD, or by extracting boot.img from the ARHD zip and flashing it with fastboot.
jollywhitefoot said:
While you were still on stock, did you update the phone through Software Updates? You're likely on the originally released version of the firmware, which is probably 90% of your problems. Mismatched firmware/ROM isn't helping either.
Either return the device to stock to be able to take the OTA update, or S-Off ($25 through sunshine) and flash the latest developer edition firmware (2.8.617.4).
Click to expand...
Click to collapse
I did not update the phones firmware. I was doing this whole thing in the first place because I thought updating to 5.1 android would update my firmware lol.
Right now I am trying to adb sideload the android revolution ROM but the phone says "Starting adb sideload feature" and gets stuck there. I have the correct drivers. Fastboot works fine, but I can only flash stock roms with fastboot. Do you have any link for the stock T-Mobile rom?
OfficialBlox said:
I did not update the phones firmware. I was doing this whole thing in the first place because I thought updating to 5.1 android would update my firmware lol.
Right now I am trying to adb sideload the android revolution ROM but the phone says "Starting adb sideload feature" and gets stuck there. I have the correct drivers. Fastboot works fine, but I can only flash stock roms with fastboot. Do you have any link for the stock T-Mobile rom?
Click to expand...
Click to collapse
This will wipe your internal storage, so back it up first, but it's going to be the easiest way to get out of the mess you've gotten yourself in.
http://www.htc.com/us/support/htc-one-m9-t-mobile/news/
FYI-You need to have HTC Sync Manager installed on your computer for the RUU to run (or at least you USED to). If you get error 155 it's likely because it's not installed.
I fixed it by putting android revolution rom on my sd card then flashing it via twrp.
Now I have a simple question:
Does Lolipop 5.1 include all those fixes that HTC introduced? Or do I need to wait for the firmware for that? I am talking about the fixes like camera, overheating, battery, etc.
OfficialBlox said:
I fixed it by putting android revolution rom on my sd card then flashing it via twrp.
Now I have a simple question:
Does Lolipop 5.1 include all those fixes that HTC introduced? Or do I need to wait for the firmware for that? I am talking about the fixes like camera, overheating, battery, etc.
Click to expand...
Click to collapse
Firmware fixes those issues, not the rom...or at least you need the firmware for any of the fixes to actually work And using the latest ARHD with 1.32 firmware is likely making some of your issues worse.
There should be one firmware update for T-Mobile right now. But like I said, you'll have to return to stock system image to get the update. Either that or S-Off your phone which will make it possible to update to the 2.8 developer edition firmware which ARHD would run awesome on. The only downside to s-off and using developers firmware is if you use t-mobile wifi calling. For that to work, I think you need official t-mobile firmware.
jollywhitefoot said:
if you are on 5.1, you HAVE to use the stock rom . There are NO custom roms for 5.1 yet.
Click to expand...
Click to collapse
Not to confuse the OP, but @jollywhitefoot what do you mean there are no custom roms for 5.1? Did you mean kernal? Another question, Is the new T-mobile update out already? I heard it comes out on the 17th.
bigp951 said:
Not to confuse the OP, but @jollywhitefoot what do you mean there are no custom roms for 5.1? Did you mean kernal? Another question, Is the new T-mobile update out already? I heard it comes out on the 17th.
Click to expand...
Click to collapse
Sorry. Thanks for bringing that to my attention. I meant to write kernel instead of rom. There are no custom KERNELS for 5.1 roms yet.
I've fixed my original post to avoid future confusion...but hopefully we'll see a custom kernel for this device in a couple of weeks.
You probably know more about T-Mobile update schedule than I do. I'm on AT&T and they're the worst about pushing updates, so I don't even bother keeping up with them.
We probably won't have any custom kernels for a few more weeks. Nothing can happen until HTC releases source, which has been coming a couple of weeks to a month after the OTAs.
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Aztek92 said:
Hi, im using CM13, moved from stock rom kitkat 4.4 few months ago. After that time of using cm13 im kinda tired of how unstable it is, on the same time i dont want to go back to stock rom, which seemed to be fat and had a lot of issues as well (bugged front camera for example, sd card issues).
Actually everything worked 'fine' untill last snapshot, that ****ed everything up. Battery is super low (not lasting whole day, at night it drops for ~20%, used to 5% - i callibrated it), phone is randomly restarting and when that happens i cant turn it on, cuz it often stucks on lockscreen (in other word, i cant unlock phone after restart) and need to restart again and again and again (it takes sometimes 30min to make it work). And even before that update it didn't support NFC.
So, here i am, saying 'enough' and looking for best rom for Samsung S4 Mini. Hoping that it will be Android 6 that won't make any conflict with Xposed framework.
Click to expand...
Click to collapse
You must have had a bad install as I've not heard of anyone else with those sorts of issues. Though it could be an incompatible app or bad/old data etc Z you might want to ry fixing first eg wiping all app data or factory reset or fresh install (backup your files first )
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Aztek92 said:
@IronRoo
Ok, i will try.
1. What about NFC? Can it be something about bad install? Does it work for you?
2. That thing about battery - im not sure. I saw someone with same issue on reddit.
3. I flashed TWRP via Heimdall Suite, not Odin. Could it be an issue? Do i have to flash it again to maybe fix something? Or having TWRP there, working is enough? Do i have to update recovery to one that came with snapshot? https://download.cyanogenmod.org/?device=serrano3gxx
Click to expand...
Click to collapse
1. I see from your link you have the 3g version of the mini, I didn't think that one supports NFC, only the LTE (I9195) has it I think. As NFC needs the right hardware you won't be able to get it. But I don't have the 3g version so I'm not 100% certain if it has support or not.
2. Ii don't think the battery is related to CM13 directly otherwise there would be lots of people with the issue. What is the exact date of the snapshot? There was one that had battery issue but they updated it a few days later is it definitely 20160820 and not the one from a few days before you are running?
Else: If there any app showing high battery usage that doesn't normally? Or is there a problem white a wakelock? You can install an app like Trepn that will show you apps with high cpu usage (even when they are showing in about the usual place in battery stats, my browser recently locked into some sort of loop and was using a high % of cpu occasionally)
3. Always possible but unlikely it's due to Heimdal flash. TWRP should do fine. More likely the wrong Gapps causing instability, you should be on Open Gapps 6 for CM13
Sent from my Galaxy S4 Mini using XDA Labs
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
2. I have 20160820 snapshot, updated from previous one - 20160816. That's where things went wrong. On 20160418 everything (besides NFC) was working fine. Since then battery turned into garbage. At the beggining i thought that it was about Pokemon Go, that has big need for battery. Nonetheless, when i stopped playing it turned out that battery is pretty low on that snapshot. I recallibrated it, but that doesn't help. I had an issue, when battery was droping about 40% in a minute or two. https://www.dropbox.com/s/6oc4yyd1f44pfe7/2016-09-01 14.03.36.png?dl=0
3. Should i check 'update recovery along with cm'? I don't know how it will work.
4. And i forgot - everytime i turn on the phone there is notification that system stopped working. Clicking OK or Wait solves the problem (ofc when its not stuck on lockscreen). That probably is leading me to format and install clean system from new snapshot i guess.
5. Btw. Do i need to format something beside Cache, Data and System for a clean install? Im asking, cuz at some point i tried to install stock rom, but it was stuck on booting, so i restore the backup of CM. This time i will probably wipe internal storage, since i installed a lot of apps, there is probably a lot of junk left.
Thx for helping btw c:
edit. I just installed SlimKat for GT-I9195, worked like a charm, NFC was working as well. Now i reinstalled CM13, clean install of 20160820 (3gxx)- we will see how it will work. Still NFC is not working and notifictation 'process system stopped working' is still there.
Click to expand...
Click to collapse
edit: see arco's reply below,
The 3g CM ROM will not have the NFC code I guess
No do not check "update recovery" as you might lose your current recovery
gotta go get my son now!
Sent from my Galaxy S4 Mini using XDA Labs
Aztek92 said:
@IronRoo
1. Yes, it was supported on stock rom, it's gone now. By the way, im not sure if i really have GT-I9190, since there are parts in my device with name of I9195, also it's called I9195 when booting (but i guess that's just recovery). Cyanogenmod doesn't allow mi to install I9195 (ltexx) roms, saying it's 3gxx device. Then again, when it comes to firmware, there is nothing for my country. Seems like I9190 is only for ~south america or something. No problem finding ROM for poland in I9195 tho.
Click to expand...
Click to collapse
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
arco68 said:
Turn off your phone. Remove the back cover and then the battery. On the white sticker the model number is printed. If it says GT-I9195, then you have the wrong recovery installed, since you say it says it's a 3gxx device when installing ltexx roms.
Click to expand...
Click to collapse
Thanks Arco!
(I was trying to say toggle the "signature verification" option but that could lead to more problems if he has the wrong recovery!)
Sent from my Galaxy S4 Mini using XDA Labs
Yup, its GT-I9195, maybe that's from all the problems comes, wrong rom, wrong recovery. I feel kinda dumb, that i didn't check under battery before, sorry for that.
I have work to do today i guess.
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Aztek92 said:
@IronRoo @arco68
Ok, few days into right and stable CM13. It's working ultra nice
Battery is still an issue here (again dropped ~30% in a minute), but i guess at this point its hardware problem. Maybe i screwed it with my powerbank.
Btw. Im kinda supprised that system let me install wrong recovery... and the wrong recovery didn't let me install right rom
Click to expand...
Click to collapse
Hi, sorry for bringing up this somehow old thread, but I have the exact same battery issue on my wife's serranoltexx.
I just installed CM13 on her phone, and after a reboot battery dropped from 40% to 5%. This happened twice, so no coincidence here.
Have you found where the problem came for ? Was your battery dead or have you found a fix ?
Also, I have seen your post about sview cover, very interesting. Will try it out tonight !
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Aztek92 said:
Hi, no worries
No, I didn't find an issue sadly - just like i said before, changing recovery and rom to correct version didn't help. I tried everything at this point, i recalibrated battery like 10 times to be sure, but it still likes to drop madly. For now im just trying to stay above 50%, but (don't take it wrong) im glad im not only one with issue Maybe someone who knows a thing or two about it will be interested in it.
Thanks about S-view. It's really more like noob-geeky-style solution, but it did work for me If you will have any problem, we will try to fix it
Click to expand...
Click to collapse
Thanks for your answer !
If changing ROM and calibrating did not help, then I guess it's a hardware problem. That was my first thought when I saw this drop yesterday and I already told my wife that we'll have to buy a new one. Cheers to Samsung for building phones with replaceable batteries !
Even a geeky workaround for the sview cover might suit her needs. I think she just wants to check the time and her notifications with the cover on, I don't think she even needs to answer calls (she said it never worked for her, a touchscreen sensitivity issue I believe).
If she doesn't like it, I still have the possibility to downgrade her to CM11. It seems that sview worked fine on this release. And I'm sure she won't mind kitkat as she's not as geeky as I can be
I've been using CM13 nightly (latest) for 4 days or so.
Pros:
Battery last much longer, you have many battery profiles which is nice.
External SD can be integrated as Internal (nice that some apps are automatically installed onto SD)
Cons:
Can't find tar file which is backup I made using CWM recovery rom. Looked everywhere!
Icons dissappear from home after every bootup
Can't move sys apps or preinstalled apps to ext sd card. Can't use Link2SD once you configure External SD as internal. Not so flexible.
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
kennyk09 said:
Overall, big improvement I feel is the battery life which is good, the bad thing is that Internal storage space gets filled up easily, especially because I know the CWM backed up ROM is stored there yet I can't find it. Which sucks big time.
Click to expand...
Click to collapse
Look in /data/media it should be there somewhere. Need root access though.
I recommend using TWRP instead of CWM.
arco68 said:
I recommend using TWRP instead of CWM.
Click to expand...
Click to collapse
Yes, but TWRP can't flash CM11 if I'm not mistaken. Old ROM, I know, but it's the latest one with S-View Cover support.
Also yesterday, I tried to restore my stock ROM backup with TWRP but could not get it to work. Stuck on "starting apps" during boot. Wiping Dalvik and cache did not help.
@thewild
If changing ROM and calibrating did not help, then I guess it's a hardware problem.
Click to expand...
Click to collapse
Not nessessary. Please notice, that i moved from CM13 (i9590) to... CM13 (i9595). I had an issue with wrong recovery. I also didn't have any problem on stock rom. If you're still gonna change battery, tell me how it worked for you.
Btw. there is something called hall monitor https://github.com/durka/HallMonitor But still i have no idea how and if it (still) works.
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10€, so I'll give them a try and let you know.
thewild said:
Yes I tried halmonitor on CM13. It worked... kind of.
Basically, it allowed the power button to turn the screen on when the cover is closed. The problem is that CM13 lockscreen is not suitable for the view cover.
Then I saw your solution, which should also work with halmonitor as long as dashclock and the xposed module are supported on CM13.
As for the battery, well I'm not 100% sure.
Battery was bad before CM. I'm quite confident that I flashed the correct recovery (i9195), and the correct ROMs. But it's not my phone, so I'm not familiar with it. I'd say that my problem is hardware, and new batteries (official ones) can be found for 10â?¬, so I'll give them a try and let you know.
Click to expand...
Click to collapse
€10, they would have to be fake! (or used)
What is the screen on time (battery>screen) you are getting? I bet it's low & that is the reason for your sudden drops, with my old battery (original Samsung) I was lucky to get 3hrs and that had sudden drops, new battery gives me 6hrs SOT.
Can't tell you the sot because it's not my phone, but it sure is very low. And the battery drops from ~50% to 0% in seconds.
10€ seems to be the right price. They are 20€ on samsung's store, but 10€ is on Amazon, sold by Amazon. I never got fake / used items from them.
Anyway, it's worth a try. I can send it back for free if it's not OK.