Related
I'm running the CM9 beta 0.2.0 by jokersax11 ([Ics] cm9 beta with camera CDMA/GSM/UMTS/HSDPA/WCDMA/roaming 2/22/12) and my capacitive touch buttons at the bottom of the screen*(Menu, Home, Back and Search) are not lighting up at all! I can't figure it out at all and I really need these buttons to light up, due to my recent switch from the LG Optimus S, and before that I had an AT&T HTC Inspire 4g (which have the home and menu buttons reversed). I use my phone alot at night and I desperately need to get this fixed! Is there something in the CM9 settings I'm overlooking? Or is there an app or mod that I could use to get control of them and get them working again? PLEASE HELP! I WOULD REALLY APPRECIATE ANY ADVICE OR ANY INFO ON HOW TO GET THESE BUTTONS TO LIGHT UP AGAIN! This is really frustrating!
Click the link below for the answer ...
http://forum.xda-developers.com/showthread.php?t=1526546
EDIT - Well that was fun. If you haven't figured it out, the link above goes to the other thread you started, with the same title, and the same body, in the same forum .... You should not create duplicate threads. For future reference best practice is create 1 thread and wait a minimum of 24 hours between bumps.
With that out of the way my actual advice is as follows, i dont believe the capacitive buttons are an issue with jokers CM build although i dont personally use it. This would indicate the answer lies in a) something you did b) something you didnt do c) something you installed
1. You can eliminate a and b without losing any info by going into your custom recovery and wiping cache and dalvik cache then doing a dirty flash on the rom (dirty flash = don't wipe data/factory). In this case there would be no reason to reflash gapps.
2. If that doesn't work, do a full wipe (data factory/system/dalvik) and reflash the ROM, then gapps. Be slow to in stall your apps and test the capicitive buttons frequently to ensure you haven't done anything to break them
Set the phone's brightness to Automatic.. Fixed..
People are so over dramatic sometimes lol.
Sent from my MB855 using Tapatalk
Thanks, that pointed me in the right direction. My auto brightness isn't working. I'm gonna do a "dirty flash" and see if that helps. Oh and btw,the second post was an accident and you can't delete your own thread.So, sorry about that.
eszumlas1985 said:
Thanks, that pointed me in the right direction. My auto brightness isn't working. I'm gonna do a "dirty flash" and see if that helps. Oh and btw,the second post was an accident and you can't delete your own thread.So, sorry about that.
Click to expand...
Click to collapse
Please come back and update the thread on if it works or not. Others may experience the same issue in the future and this thread could assist them.
Cheers!
i just now notices mine dont light up but o well my thumb pretty much know ware to push
Well, it's fixed. Don't know what the heck was going on but reflashed my CM9 & Google apps and voila my automatic brightness switch in settings started working again. No more problems and capacitive buttons work fine. Strange but at least it's fixed
Sent from my MB855 using xda premium
And sorry to anyone that needed a fix to this. I was involved in the tornado that hit Branson, Missouri and was unable to keep phone charged due to the power outage that lasted over a week, and had bigger things to worry about at the time, like getting shelter and food. But everything is ok now and hope this thread helps anyone that has this problem. Check to see if your automtic brightness switch is working under settings (mine wasn't working) So if it isn't working just reboot into recovery, wipe dalvik cache & /cache, and reflash your rom and gapps, then check in your settings to see if your automatic brightness is now working. If so your problem should be fixed and your capcitive buttons should now light up. It worked for me, hopefully it will work for you.
Sent from my MB855 using xda premium
eszumlas1985 said:
Check to see if your automtic brightness switch is working under settings (mine wasn't working) So if it isn't working just reboot into recovery, wipe dalvik cache & /cache, and reflash your rom and gapps, then check in your settings to see if your automatic brightness is now working. If so your problem should be fixed and your capcitive buttons should now light up. It worked for me, hopefully it will work for you.
Click to expand...
Click to collapse
Thanks man i just had to set the screen brightness to automatic and reboot once. It worked like a charm
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
luizlee86 said:
Hi all! I'm having some brightness issues on my Razr i and any help would be great!
I'm on stock 4.1.2 and was using Power Toggles brightness slider to change the brightness, but suddenly, with no changes on the phone, the brigthness level would change only after turning screen off/on. But the problem is not related to the app I think, because even auto brightness isn't working properly... I mean, when it has to get brighter, it works, but when it has to dim, again only if I turn off/on the screen.
Does anyone know what could be causing it?
Thanks in advance!
Sorry for the bad english.
Click to expand...
Click to collapse
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
shimp208 said:
Although you don't think the app is causing the brightness problem's I would recommend uninstalling it for troubleshooting purposes and seeing if after you have uninstalled the app and rebooted the phone if after some time the problem persists. This way we can rule out if the app is or isn't causing the problem.
Click to expand...
Click to collapse
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
luizlee86 said:
Thanks for the reply. I did uninstall it and the problem remains... I installed volume slider (which has a brightness slider too) and the same happens: non "real time" brightness changing and the auto brightness still doesn't work properly... =/
Click to expand...
Click to collapse
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
shimp208 said:
That is odd, I would recommend booting into recovery and performing a factory reset and then see if that fixes your problem.
Click to expand...
Click to collapse
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
luizlee86 said:
This is what I was afraid of... =/
I will just wait a little longer to see if anybody faced this issue before. I'm pretty sure a factory reset will do (since it started to act like this all of a sudden) but I want to find the cause so it won't happen again or, if it happens, I won't need to do a factory reset...
It's weird... what could make this issue appear? =/
Click to expand...
Click to collapse
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
shimp208 said:
One possible way of figuring out what is causing this issue to happen is to generate a logcat when you are adjusting the brightness settings and see if the log reports any background processes that are causing errors with the brightness control.
Click to expand...
Click to collapse
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
luizlee86 said:
Thanks for helping me!
I never generated a logcat before. So I installed CatLog from Store and generated a logcat doing the following:
1) Set brightness to auto
2) Put the phone under a lamp
3) Turned of all the lights: the brightness didn't change
4) Turned off and on the screen: when the screen turned on, the brightness was already on a lower level
The logcat is pretty messed... it shouldn't be like that right? =/
Is this helpful?
Click to expand...
Click to collapse
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
shimp208 said:
From looking at the logcat there is a lot of errors and warning messages with loading certain library files and Android runtime services that relate to power and screen brightness sensing. Another peculiar thing I noticed was that NFC seemed to be generating a couple error messages as well. Overall you were definitely right about it not being a normal log in this situation, I also like your testing methodology :good:.
Click to expand...
Click to collapse
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
luizlee86 said:
NFC is disabled... =/
Well, so any suggestion? Or just a factory reset would do?
Click to expand...
Click to collapse
Unfortunately a factory reset would probably be the best thing to do.
shimp208 said:
Unfortunately a factory reset would probably be the best thing to do.
Click to expand...
Click to collapse
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
luizlee86 said:
Just wiped data through CWM and the autobrightness still doesn't work properly...when it has to get brighter, it gets, but when it has to dim, it doesn't...
Click to expand...
Click to collapse
You could also try re-flashing the stock ROM to see if that fixes it, another suggestion that could possibly work is running a fix permissions utlity.
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
EDIT: found what was causing it! It is the latest version of Floating Notifications (when show on lockscreen is enabled)!
Thanks a lot shimp!
luizlee86 said:
Reflashed stock rom and reinstalled all my apps. Everything was fine. Went to bed and woke up, the same problem with power toggles reappeared...
Click to expand...
Click to collapse
That's wicked bizarre that even after all those things the problem still persists. You could try bringing it in to Verizon to see if they can do anything otherwise a hardware issue may have arisen.
Sent from my SCH-I535 using xda premium
As above, is there any way to do this?
An xposed setting maybe?
Edit Solved... Gravity Box setting under Display Tweaks / Unplug turns on screen
I KNOW that i saw an option to do this in a Sony app. It was either in the STAMINA settings or the Smart Connect app. I remember seeing it and thought "Hmm... nah, i don't want to disable that".
LordManhattan said:
I KNOW that i saw an option to do this in a Sony app. It was either in the STAMINA settings or the Smart Connect app. I remember seeing it and thought "Hmm... nah, i don't want to disable that".
Click to expand...
Click to collapse
Yeah I thought Id seem it somewhere without using exposed, but I'm buggered if I could find it today. In the end I just concluded it must have been in a custom rom I'd flashed to try out.
Yeah, i searched for it now, but i give up. I bet it'll show up when i least expect it, like in a year or something
LordManhattan said:
Yeah, i searched for it now, but i give up. I bet it'll show up when i least expect it, like in a year or something
Click to expand...
Click to collapse
Either that or I've already considered the Sony app as bloat and frozen it with TB :silly:
Anyway problem solved. Loving Gravitybox
baileyjr said:
As above, is there any way to do this?
An xposed setting maybe?
Edit Solved... Gravity Box setting under Display Tweaks / Unplug turns on screen
Click to expand...
Click to collapse
I installed GravityBox but I don't know now whether to keep Xblast Tools or not... after all, they both do almost the same things...
Also, it does work with stock rom, but Pie Controls (I love them, but the play store ones are fugly) just work when both status and nav bar are showing... tried all possible combinations but nothing..
Anyway, I thought for a second to discard the led when charging but then again 4 out 5 times I plug it in the full dark and the led is the only thing telling me it's charging...
Sent from my C6833 using xda app-developers app
fastest83 said:
I installed GravityBox but I don't know now whether to keep Xblast Tools or not... after all, they both do almost the same things...
Also, it does work with stock rom, but Pie Controls (I love them, but the play store ones are fugly) just work when both status and nav bar are showing... tried all possible combinations but nothing..
Anyway, I thought for a second to discard the led when charging but then again 4 out 5 times I plug it in the full dark and the led is the only thing telling me it's charging...
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
After playing with gravity box I uninstalled Xblast and the advanced power menu modules.
Is there something in Xblast that is missing from GravityBox... Im not a huge fan of Pie control. However I have set it to pie control when in expanded desktop mode and it works just fine, but not from the bottom border, I had to set it from the top border :good:
Edit, I set the trigger area to 15 and its working just fine from the bottom borner now
I tried it too and it was working... until I decided to change the transparency of the status bar to 100%...
Then, SystemUI stopped every 2 seconds, so I deselected the module and restarted, cleared cache and data or Gravitybox, reselected it, restarted.
SystemUI stopped like crazy again.
And then (who knows why) I pressed (I'd say involuntarily, but that was not the case) the "expanded desktop" button thinking that maybe the mess had to do only with the status bar.
Needless to say that it hadn't.
At that time SOD like crazy, I mean I turned on/off like 15 times to make it work again.
Eventually the screen (with SystemUI error) came up, I deselected and uninstalled the Gravitybox module and made a reservation with my tattooist for a tattoo on my forearm that says: "If it's supposed to work on AOSP ROMs ONLY, and you have a [email protected]£&ING stock ROM, DON'T INSTALL IT!".
Seen that I crapped in my pants tonight too, I'd say it's time to go to bed. (And unlocking the bootloader comes closer and closer...).
Sent from my C6833 using xda app-developers app
fastest83 said:
I tried it too and it was working... until I decided to change the transparency of the status bar to 100%...
Then, SystemUI stopped every 2 seconds, so I deselected the module and restarted, cleared cache and data or Gravitybox, reselected it, restarted.
SystemUI stopped like crazy again.
And then (who knows why) I pressed (I'd say involuntarily, but that was not the case) the "expanded desktop" button thinking that maybe the mess had to do only with the status bar.
Needless to say that it hadn't.
At that time SOD like crazy, I mean I turned on/off like 15 times to make it work again.
Eventually the screen (with SystemUI error) came up, I deselected and uninstalled the Gravitybox module and made a reservation with my tattooist for a tattoo on my forearm that says: "If it's supposed to work on AOSP ROMs ONLY, and you have a [email protected]£&ING stock ROM, DON'T INSTALL IT!".
Seen that I crapped in my pants tonight too, I'd say it's time to go to bed. (And unlocking the bootloader comes closer and closer...).
Sent from my C6833 using xda app-developers app
Click to expand...
Click to collapse
Its working for me now, so I'll run with it, without changing any transparency settings lol
I had the system UI thing with Gravity Box a few weeks ago before I had unlocked the bootloader and I crapped myself as well..
Happier these days with my bootloader unlocked and regular nandroid backups.
So I think the capacitive buttons on my Rezound have bit the dust. I was having trouble with CM 10.2, and thought that was the cause. I have since tried various roms that had worked in the past and have tried going back to a stock rom to no avail. I now believe I just have a good old fashioned hardware failure.
I'm trying to figure out a work around, as I can't really afford a new phone currently. Does anyone know if we have any ROMs that have the home and back buttons on them like a Nexus device, (where they are the black and white softkeys at the bottom)?
YTHero said:
So I think the capacitive buttons on my Rezound have bit the dust. I was having trouble with CM 10.2, and thought that was the cause. I have since tried various roms that had worked in the past and have tried going back to a stock rom to no avail. I now believe I just have a good old fashioned hardware failure.
I'm trying to figure out a work around, as I can't really afford a new phone currently. Does anyone know if we have any ROMs that have the home and back buttons on them like a Nexus device, (where they are the black and white softkeys at the bottom)?
Click to expand...
Click to collapse
All CM10.2 based roms have em, just need to enable the buttons. Using PIE controls is an option also.
To enable the Nav bar, try adding this to your build.prop and reboot.
qemu.hw.mainkeys=0
Edit: Just noticed a typo, cut it from another site, it's fixed now.
Thanks for your reply. I've never edited any build.prop before, I knew you could do that but didn't know why you would or what it did.
I installed CarbonRom to get the nav bar and it seems to work pretty well.
Edit: can I turn off the lights for the capacitive buttons with a build.prop?
YTHero said:
Thanks for your reply. I've never edited any build.prop before, I knew you could do that but didn't know why you would or what it did.
I installed CarbonRom to get the nav bar and it seems to work pretty well.
Edit: can I turn off the lights for the capacitive buttons with a build.prop?
Click to expand...
Click to collapse
You can use kernel tuner and slide the slider to 0. That'll disable the lights.
Sent from my ADR6425LVW using Tapatalk
YTHero said:
Thanks for your reply. I've never edited any build.prop before, I knew you could do that but didn't know why you would or what it did.
I installed CarbonRom to get the nav bar and it seems to work pretty well.
Edit: can I turn off the lights for the capacitive buttons with a build.prop?
Click to expand...
Click to collapse
Check to see if Carbon has a Buttons section under the Settings, if so you can turn the brightness off.
tmanschuette said:
You can use kernel tuner and slide the slider to 0. That'll disable the lights.
Sent from my ADR6425LVW using Tapatalk
Click to expand...
Click to collapse
mjones73 said:
Check to see if Carbon has a Buttons section under the Settings, if so you can turn the brightness off.
Click to expand...
Click to collapse
I added that line to build.prop in CM 10.2, and nothing changed. Also I couldn't find the pie control options, so I dunno.
Carbon had no buttons section, and I couldn't find an option anywhere else to disable the led lights.
Hmm, you may need expanded desktop on also, I'll try it on mine later.
Sent from my Rezound on Tachyon using Tapatalk
I found the error, what you typed earlier was wrong - it's "qemu.hw.mainkeys=0".
I changed that, rebooted and now it works.
Sorry, copied that from another thread, guess they had it wrong also..
Sent from my Rezound on Tachyon using Tapatalk
I can confirm that this works on CM11 too.
Q&A for [ROM][4.4.4][CyanideMod]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][4.4.4][CyanideMod]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
CyanideMod V2 volume
I am currently having a problem. The volume buttons on the phone are not working for Ringtone and Notification. They will only adjust the volume of the music, games & other Media. I have it set in Sound/Volumes, but it is not working. Also, I am not able to adjust the volumes in the profiles, they just stay set at defaults.
ke7vng said:
I am currently having a problem. The volume buttons on the phone are not working for Ringtone and Notification. They will only adjust the volume of the music, games & other Media. I have it set in Sound/Volumes, but it is not working. Also, I am not able to adjust the volumes in the profiles, they just stay set at defaults.
Click to expand...
Click to collapse
After media volume shows up click to make the volume extendable and then adjust the notification volume. I just noticed this so I'll be looking before I start working on it again
Sent from my SGH-I317 using XDA Premium 4 mobile app
In v3, the classic (stock) recent apps panel seems to crash systemui. Slim recents works OK.
radoo7701 said:
In v3, the classic (stock) recent apps panel seems to crash systemui. Slim recents works OK.
Click to expand...
Click to collapse
Will you check if omniswitch can be set as default recent app still? I fixed the stock recent issue before I uploaded but if omniswitch can still be selected as default then I uploaded the unfixed version. I'll upload V3.5 soon. Working on a kernel/recovery mod at the current time
Sent from my SGH-I777 using XDA Premium 4 mobile app
Yes I can set omniswitch as the default for recents. Just to be sure I did a clean install and still have the issue with stock recents.
radoo7701 said:
Yes I can set omniswitch as the default for recents. Just to be sure I did a clean install and still have the issue with stock recents.
Click to expand...
Click to collapse
Well poop lol. That's actually good tho. Like I said I did already fix this, I just apparently uploaded the unfixed version. Oops. I can run a build fairly quickly as a still have the s2 build cached but I'm using build environment to build and make some recovery changes at the moment
FUSE support?
Hi,
I found this ROM last night and flashed it, and want to say thanks. I was having trouble with other ROMs aborting installation, but this one installed without a hitch. Everything works as it should, and way better than my old CM9 ROM. This was completely painless.
Question: Does the kernel have FUSE support?
I'm trying to get SSHFS working; I can ssh into the target server via terminal emulator, but SSHFS will not mount. It appears to mount but doesn't really. When I click unmount, It complains:
fusermount: error getting lock: Invalid argument
I know this isn't the place to get help with SSHFS, but it will only work if the kernel has FUSE support, so that enters into your bailiwick.
Oh, and a possible issue: It seems I'm not getting as strong a network signal now as I did before flashing this ROM. Is it even possible this could be due to a software issue?
Thanks again for the great work. You are awesome!
Stock recent panel is not working. Could just be my dirty flash. Thank you for your hard work. This ROM is amazing.
Sent from my SGH-I777 using XDA Free mobile app
modem not working
I've been running a CyanogenMod-9 version for quite awhile, until about a week ago when I decided to upgrade. I tried some of the CM-10 versions, and installation aborted midway, leaving me stuck with a non-working phone for a few days.
I flashed CyanideMod-V3-S2 a few days ago, and was very pleased to see it install effortlessly. It looks great, and everything seems to be working, EXCEPT the modem.
The network signal is very weak. I can make calls if I am in town, or on top of a high hill, but often I get no signal at all. I do live in a rural area, but it has never been this weak. Even when I get full bars, they are always white, never blue as they should be. I have no access to data.
I don't know much about AT&T's network; frequencies, etc., but my semi-educated guess is that I'm not picking up all the frequencies I should.
In my settings:
Mobile network is on.
Data is enabled
Preferred network type is set to 3G
Network operators is set to ATT
Access Point Names was set to ATT LTE. I stopped in today at an ATT store, and the rep's phone was set to "ATT Phone" so I experimentally changed to that and rebooted, but saw no change. The settings in the 7 available choices match the setting in other working phones in our household, so I don't think this is a settings problem.
I found the "Consolidated Modem" thread on this site, which lists 13 choices for modems. My phone reports a "Baseband version of i777UCKK6, which is one of the choices in that page, which I assume was installed with the ROM. I don't know if the modem is my problem, and wouldn't have a clue which of these to try. Are they installed through recovery in the same way as the ROM and gapps?
I love this ROM, but the phone is nearly unusable as it is. Has anyone else had this problem, or does anyone have any pointers?
Thanks so much for all your hard work.
Newest modern is UCMD8. Rom wouldn't affect the modem other then the usual kk signal issues
Thanks for the update. Amazing!! Stalk recents still does not work (maybe because of dirty flash, please confirm with other users). Also the power menu-reboot menu does not have reboot to recovery. Reboot to recovery is available in stweaks. But it would be nice to have again in power menu.
dagwoodmash said:
Thanks for the update. Amazing!! Stalk recents still does not work (maybe because of dirty flash, please confirm with other users). Also the power menu-reboot menu does not have reboot to recovery. Reboot to recovery is available in stweaks. But it would be nice to have again in power menu.
Click to expand...
Click to collapse
If you uncheck and recheck Advanced Boot in Developer Options you should get the boot to recovery to show back up. It still shows for me after update.
I am getting FC on Google play services after update and cannot access my account. Would reflashing gapps fix that?
radoo7701 said:
If you uncheck and recheck Advanced Boot in Developer Options you should get the boot to recovery to show back up. It still shows for me after update.
I am getting FC on Google play services after update and cannot access my account. Would reflashing gapps fix that?
Click to expand...
Click to collapse
Thanks for helping him. Yes just reflash gapps. Not sure why it's like that but for some reason it is. I don't need it while testing but then do later on. Strange
Awesome build (V4). Coming from CM of a few months ago, everything is real snappy (also due to flashing afresh).
A few bugs so far:
1) Tapping on notifications in the pull-down drawer doesn't seem to link to anything (the animation works, but the associated action doesn't fire). Additionally, the Halo/Quick Settings buttons at the top of the notification drawer seem to get pushed off the edge of the screen (Would be nice if the Halo button could be removed/Halo disabled).
2) Lock screen slider shortcuts cover up cLock
3) Volume buttons (including from home screen) control system volume, not ringer/notification volume.
Amazing work, in any case! Some day I'll need to get a new phone.
b
Gonna be starting from scratch here.. can you give me a quick runthrough.. I have a bricked i777 that I will be starting with.. starting with an Odin tar(stock rooted 4.1.2?) to get it back up and running. It' s been years but I'll figure it out. just need a simple outline like which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
tri0xinn said:
Gonna be starting from scratch here.. can you give me a quick runthrough.. I have a bricked i777 that I will be starting with.. starting with an Odin tar(stock rooted 4.1.2?) to get it back up and running. It' s been years but I'll figure it out. just need a simple outline like which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
Click to expand...
Click to collapse
I'm driving but maybe @creepyncrawly could point you there. Flash odin rom, flash odin custom kernel for recovery, make a backup, do a factory reset and wipe system, flash shift kernel, tenor to recovery abs flash rom and gapps. Use V3 of this rom. It's all here. You could probably fine before he sees this. I'm voice typing or I'd help you out
Sent from my SGH-I317 using XDA Premium 4 mobile app
tri0xinn said:
...which stock Odin tar.. then which android versions and recovery to install to get to your 4.4.4 .
thanks
Click to expand...
Click to collapse
Use latest stock 4.1.2, I777UCMD8 which you can get from the download repository (link in my signature) Also some other stuff there if you need it, but not the recovery and firmware you need.
thanks a ton, got everything back to square one with that I777UCMD8 tar, easy after that and now running cyanidemod and it's running as slick as my gs5.. at least it seems to be. thanks again:good:
After a couple days of use its still running super slick.. only issue thus far is pretty bad battery life.. any settings i can adjust to improve things? Or another kernel maybe.. anyone else have issues with battery life?