I am unable to post to the [Rom] AOKP(Jellybean 4.2.1) | Task650 (1/22/13) (2nd Release!) thread due to being a noobie
So I am posting here hoping someone knowledgeable can clarify if this is a known issue or unique to me.
My device: i777 on T-Mobile. Previously on Task 650's AOKP 4.1.2 now on AOKP 4.2.1.
I like everything about this ROM. However, I noticed that I can no longer use my phone's Wifi-Tethering capabilities. I researched here and googled crazy and have not been able to find anything conclusive on this being a new issue/bug or an established issue.
I came across numerous posts where people seemed to loose their tethering capability with JB upgrades. In particular with the 4.2.1 upgrade. I even saw this in google's android bug reporting forums as well. Some claimed that this capability was removed as Google worked it out with the carriers. Yet many seem to be able to tether without any problems.
Hoping some one with good knowledge of this ROM can clarify if this is a ROM issue or somehow connected to my device. If it is my device appreciate suggestions on what I could do? I tried third party apps. They do not work as well.
Thanks for you time.
Reboot was a solution
Sent from my GS4 running CM11 Kandy Kane
122ninjas said:
Reboot was a solution
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
Sorry, I forgot to mention that I rebooted, reflashed, data wipe +flash, everything that I could think of and what were suggested for some generic issues with no such luck. Do not know if revising any APN settings will do any good.
I also found the following as a solution to this problem in a galaxy nexus thread for the same problem. Do not know if it applies to i777. Any advice will be highly appreciated.
"1. use apktool to de-compile framework-res.apk
2. navigate to res/values/arrays.xml
3. open arrays.xml in a notepad editor
4. edit the line "config_tether_upstream_types" change the 4 to a 5
5. save changes and re-compile framework-res.apk
from there you will be able to tether"
i have the same issue since updating from tasks december ROM to his January 4.2.1 & now 4.2.2 (3-13-2013) ROM
i dont use it often, but want it to actually work when i go to use it.
i set it up, checked the portable wi-fi hotspot box to turn it on and the text right below it says Turning hotspot on... but never actually does anything. on the december release it started working within a few seconds.
i used root explorer to look at framework-res.apk (as mentioned above) but there is no "values" folder in the "res" folder so i cant find arrays.xml
neelapala said:
I am unable to post to the [Rom] AOKP(Jellybean 4.2.1) | Task650 (1/22/13) (2nd Release!) thread due to being a noobie
So I am posting here hoping someone knowledgeable can clarify if this is a known issue or unique to me.
My device: i777 on T-Mobile. Previously on Task 650's AOKP 4.1.2 now on AOKP 4.2.1.
I like everything about this ROM. However, I noticed that I can no longer use my phone's Wifi-Tethering capabilities. I researched here and googled crazy and have not been able to find anything conclusive on this being a new issue/bug or an established issue.
I came across numerous posts where people seemed to loose their tethering capability with JB upgrades. In particular with the 4.2.1 upgrade. I even saw this in google's android bug reporting forums as well. Some claimed that this capability was removed as Google worked it out with the carriers. Yet many seem to be able to tether without any problems.
Hoping some one with good knowledge of this ROM can clarify if this is a ROM issue or somehow connected to my device. If it is my device appreciate suggestions on what I could do? I tried third party apps. They do not work as well.
Thanks for you time.
Click to expand...
Click to collapse
Jus flash a different kernel and you will be good to go. It has nothing to do with the ROM. Its jus the kernel u r using. Flash latest AJK kernel.
gireeshtty9 said:
Jus flash a different kernel and you will be good to go. It has nothing to do with the ROM. Its jus the kernel u r using. Flash latest AJK kernel.
Click to expand...
Click to collapse
Link?
Task doesnt like when you flash another kernel...if you don't keep the one he packaged with his latest release, you can never ask for any help in his thread.
dh4645 said:
Link?
Task doesnt like when you flash another kernel...if you don't keep the one he packaged with his latest release, you can never ask for any help in his thread.
Click to expand...
Click to collapse
That's actually true of any ROM thread, not just Tasks. If you alter the ROM in any way (replacing the kernel, etc), don't expect the developer to help if you encounter any problems... you're on your own, to a degree.
Sent from the i777
SteveMurphy said:
That's actually true of any ROM thread, not just Tasks. If you alter the ROM in any way (replacing the kernel, etc), don't expect the developer to help if you encounter any problems... you're on your own, to a degree.
Sent from the i777
Click to expand...
Click to collapse
He needs his issue to be solved. So thats the solution for his problem. If he wanted to get any help from Task then this thread probably wouldnt be here. And I personally dont think Task has any problems with anyone flashing any other kernel. No developer has. Maybe they may not help out jus coz they dont talk bout other kernels but everyone does this to clear the issues they have. No offence.
gireeshtty9 said:
Jus flash a different kernel and you wi. be good to go. It has nothing to do with the ROM. Its jus the kernel u r using. Flash latest AJK kernel.
Click to expand...
Click to collapse
I tried AJ's 1.48 with Task's 3/13 and tethering didn't work for me.
I'm using AOKP JB-MR1 SGH-i777 Build 5 | Android 4.2.2 [2013.03.05] [UNOFFICIAL-PORT] from the ported section with AJ's 1.25 kernel to provide internet to my nexus 10 to write this post. Tethering works perfect with that combo.
gireeshtty9 said:
He needs his issue to be solved. So thats the solution for his problem. If he wanted to get any help from Task then this thread probably wouldnt be here. And I personally dont think Task has any problems with anyone flashing any other kernel. No developer has. Maybe they may not help out jus coz they dont talk bout other kernels but everyone does this to clear the issues they have. No offence.
Click to expand...
Click to collapse
Let's not turn this into a he-said-he-said thing; my intent wasn't to bash anyone for flashing custom kernels, only to point out that, in general, developers won't support someone else's work.
Sent from the i777
SteveMurphy said:
Let's not turn this into a he-said-he-said thing; my intent wasn't to bash anyone for flashing custom kernels, only to point out that, in general, developers won't support someone else's work.
Sent from the i777
Click to expand...
Click to collapse
^This! If users run into an issue with a different kernel than the one that was packaged then the support one would get would be to re flash and keep the packaged kernel. Each developer chooses their kernel for a reason
Sent from my SAMSUNG-SGH-I317
Bump for a solution to this problem.
Caligula36 said:
Bump for a solution to this problem.
Click to expand...
Click to collapse
Unless you have the solution you shouldn't bump an old thread
Sent from my CLEAN Note ll
Related
Alright, I'm a noob...(loved the intro video!) and I've spent an hour or so searching for rooting info for my device. Did find a good thread that was over a year old about rooting SGH-i777 with older android versions, but was afraid to follow THOSE directions since mine has newer version (Android 4.0.4). And I find other threads about rooting other versions of GS2...not the AT&T.
So far I've learned NOT to use ROM Manager, and not to look to Galaxy2Root for help...so I guess there's that. I don't want to be stupid here, but can someone direct me to a thread with Rooting instructions for my phone with ICS already on it, and recommended ROMs. I'd like to have more control over my phone and take advantage of JB releases that seem to be out with good reliability. I'm used to doing this sort of thing on computers, but not with Android. Had my phone for about 15 mos....my first Android.
Suggestions?
TIA...
judib said:
Alright, I'm a noob...(loved the intro video!) and I've spent an hour or so searching for rooting info for my device. Did find a good thread that was over a year old about rooting SGH-i777 with older android versions, but was afraid to follow THOSE directions since mine has newer version (Android 4.0.4). And I find other threads about rooting other versions of GS2...not the AT&T.
So far I've learned NOT to use ROM Manager, and not to look to Galaxy2Root for help...so I guess there's that. I don't want to be stupid here, but can someone direct me to a thread with Rooting instructions for my phone with ICS already on it, and recommended ROMs. I'd like to have more control over my phone and take advantage of JB releases that seem to be out with good reliability. I'm used to doing this sort of thing on computers, but not with Android. Had my phone for about 15 mos....my first Android.
Suggestions?
TIA...
Click to expand...
Click to collapse
Use exynos abuse and you're rooted
Sent from my GS4 running CM11 Kandy Kane
122ninjas said:
Use exynos abuse and you're rooted
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
This is so far easiest thing to do, however be careful, DO NOT, DO NOT,
choose the "one click" patch option which come first, as that will patch
the system and you will NOT be able to root again. and there is NO way
to un-patch. I was not being careful and now trapped.
ExynosAbuse
122ninjas said:
Use exynos abuse and you're rooted
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
Appreciate the suggesting. Been researching ExynosAbuse, and looks like it could cause camera not to work, and in the compatibility list, though the Galaxy Sii 9100 is listed, the SGH-i777 is not...seems like a concern to me.
judib said:
Appreciate the suggesting. Been researching ExynosAbuse, and looks like it could cause camera not to work, and in the compatibility list, though the Galaxy Sii 9100 is listed, the SGH-i777 is not...seems like a concern to me.
Click to expand...
Click to collapse
It works trust me. Also you're going to flash a rom right after so you should be fine
Sent from my GS4 running CM11 Kandy Kane
I am also a noob when it comes to anything mobile. I got my GS2 last year (first android as well), and I've since updated to 4.0.4. I have also done some research on rooting(after my fiance keeps bugging me about "fixing" our gs2s due to them always turning off) but I was uncertain on what rom to use. I have no experience with phones, and I don't want to do something stupid and break our phones. I know that I am supposed to " use exynos abuse", but that's pretty much all I know/can find without reading every page on the 80 page threads. Are there any suggestions on a stable(ish) rom for us both to use/how easy is it to "use exynos abuse"? (without doing what tyhust did) We are fine with our ICS and I wont venture into the world of Jellybean yet... (maybe once I acquire some more experience)
Thanks in advance, and for the site in general, there is a TON of information on here...
tginouye said:
I am also a noob when it comes to anything mobile. I got my GS2 last year (first android as well), and I've since updated to 4.0.4. I have also done some research on rooting(after my fiance keeps bugging me about "fixing" our gs2s due to them always turning off) but I was uncertain on what rom to use. I have no experience with phones, and I don't want to do something stupid and break our phones. I know that I am supposed to " use exynos abuse", but that's pretty much all I know/can find without reading every page on the 80 page threads. Are there any suggestions on a stable(ish) rom for us both to use/how easy is it to "use exynos abuse"? (without doing what tyhust did) We are fine with our ICS and I wont venture into the world of Jellybean yet... (maybe once I acquire some more experience)
Thanks in advance, and for the site in general, there is a TON of information on here...
Click to expand...
Click to collapse
If you want you can downgrade to 4.0.3
Sent from my GS4 running CM11 Kandy Kane
4.0.4 to 4.0.3 root
122ninjas said:
If you want you can downgrade to 4.0.3
Sent from my GS4 running CM11 Kandy Kane
Click to expand...
Click to collapse
I'm also a noob... so if I want to down grade to 4.0.3 rooted from 4.0.4 stock, should I use ucle5_stock_rooted.tar with Odin?
Is is necessary to wipe since both are ICS?
Thanks!
[email protected] said:
I'm also a noob... so if I want to down grade to 4.0.3 rooted from 4.0.4 stock, should I use ucle5_stock_rooted.tar with Odin?
Is is necessary to wipe since both are ICS?
Thanks!
Click to expand...
Click to collapse
Yes, that should be the tar you use. Make sure it's from this thread. You should be okay without wiping, but if you have problems, I'd suggest flashing 2.3.4 and wiping from recovery once on 2.3.4; reason being, stock ICS kernel may brick your phone if you wipe with it (see linked thread for details on this eMMC superbrick bug).
OP, if you're uncertain about ExynosAbuse, try this method instead. I know it works, I used it myself very recently, albeit I was already on 4.0.3 and had not upgraded.
tginouye said:
I am also a noob when it comes to anything mobile. I got my GS2 last year (first android as well), and I've since updated to 4.0.4. I have also done some research on rooting(after my fiance keeps bugging me about "fixing" our gs2s due to them always turning off) but I was uncertain on what rom to use. I have no experience with phones, and I don't want to do something stupid and break our phones. I know that I am supposed to " use exynos abuse", but that's pretty much all I know/can find without reading every page on the 80 page threads. Are there any suggestions on a stable(ish) rom for us both to use/how easy is it to "use exynos abuse"? (without doing what tyhust did) We are fine with our ICS and I wont venture into the world of Jellybean yet... (maybe once I acquire some more experience)
Thanks in advance, and for the site in general, there is a TON of information on here...
Click to expand...
Click to collapse
This is a good thread.
I had the same issues with 4.0.4 and i found it was a live wallpaper app (water drops) causing my random "power off". Since switching to a different live wall paper, i have had NO random "shut downs".
I still want to root my S2 and this is the best thread i have found that addresses the stock 4.0.4
good luck.
Well, after a week of no shut downs, my phone just shut off. So i guess the live wallpaper was not the issue.
Back to the drawing board
Not to hijack the thread or anything but I'm new to this phone too. I understand the rooting process on ICS what I don't understand is installing a custom recovery and kernel. Why do you have to use a gingerbread kernel and why can you not just use stock? I've always just rooted, installed custom recovery and flashed roms on Verizon phones so installing a custom kernel to achieve custom recovery is foreign to me. I've been reading the stickies but I don't understand this....is it only to avoid the flash counter being tripped? Is there a easier way to install the recovery or am I making this harder than it needs to be? Thanks for any help!
Ryno77 said:
Not to hijack the thread or anything but I'm new to this phone too. I understand the rooting process on ICS what I don't understand is installing a custom recovery and kernel. Why do you have to use a gingerbread kernel and why can you not just use stock? I've always just rooted, installed custom recovery and flashed roms on Verizon phones so installing a custom kernel to achieve custom recovery is foreign to me. I've been reading the stickies but I don't understand this....is it only to avoid the flash counter being tripped? Is there a easier way to install the recovery or am I making this harder than it needs to be? Thanks for any help!
Click to expand...
Click to collapse
Our phone has recovery baked into the kernel. For what reason I don't know but I'm sure its a good one as just flashing recovery is IMO easier.
Thanks. Last question. After installing a gingerbread kernel and the baked in recovery do I need to install a new kernel to flash a jb or ics rom. Sorry for the noob questions. Thanks for your help.
Sent from my SCH-I535 using xda premium
Ryno77 said:
Thanks. Last question. After installing a gingerbread kernel and the baked in recovery do I need to install a new kernel to flash a jb or ics rom. Sorry for the noob questions. Thanks for your help.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Well since every ROM comes with a kernel in it (obviously or it couldn't run) then you just answered your own question bro. Flash away.
Phalanx7621 said:
Well since every ROM comes with a kernel in it (obviously or it couldn't run) then you just answered your own question bro. Flash away.
Click to expand...
Click to collapse
Thanks, that makes things easier. Appreciate the help!
Sent from my SCH-I535 using xda premium
Need more help.... There's so much information since this phone came out its overwhelming and it seems most of it was written for gingerbread. I have the phone rooted, mobile Odin lite installed and I'm confused on which kernel I need to flash. Phone is stock rooted lk3 4.0.4. Thank you!
Sent from my SCH-I535 using xda premium
Ryno77 said:
Need more help.... There's so much information since this phone came out its overwhelming and it seems most of it was written for gingerbread. I have the phone rooted, mobile Odin lite installed and I'm confused on which kernel I need to flash. Phone is stock rooted lk3 4.0.4. Thank you!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
If you're just trying to get into recovery to flash something then any kernel will do. Since the system won't need to boot up with that kernel installed you're just flashing one to enter recovery.
Phalanx7621 said:
If you're just trying to get into recovery to flash something then any kernel will do. Since the system won't need to boot up with that kernel installed you're just flashing one to enter recovery.
Click to expand...
Click to collapse
So I want to install a gb kernel and recovery only so I can flash a custom rom that comes with kernel and recovery, correct? So before flashing the gb kernel in mobile Odin I should have a rom already downloaded on the sd card so I can immediately flash that? I'm sorry for all the questions this is drastically different from what I'm used to.
Sent from my SCH-I535 using xda premium
Ryno77 said:
So I want to install a gb kernel and recovery only so I can flash a custom rom that comes with kernel and recovery, correct? So before flashing the gb kernel in mobile Odin I should have a rom already downloaded on the sd card so I can immediately flash that? I'm sorry for all the questions this is drastically different from what I'm used to.
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Download whatever ROM you want on your phone . Flash a kernel. Reboot into recovery. Profit.
I've been running AOSP 4.2 on my S4 for quite a while with no issues. Upon trying to upgrade to 4.3 though, boots take upwards of 5 minutes and the baseband isn't recognized (it literally shows "Baseband Version: Unknown"). I then tried to revert to one of the various 4.2 ROMs still out there, and am encountering quite a bit of general instability (lots of FCs), however, the baseband works fine. Any idea what is going on?
I should add that though I am using the ME7 modem, everything else is MDK and that these symptoms are pervasive through several different ROMs.
Update:
When trying to switch to RUIM/SIM in the Radio Settings, I get the following logcat:
Code:
/CdmaSubscriptionListPreference( 1762): Setting Cdma subscription source failed
I/Use2GOnlyCheckBoxPreference( 1762): get preferred network type, exception=com.android.internal.telephony.CommandException: RADIO_NOT_AVAILABLE
have you gone into network settings and verified that your subscription is set to RUIM/SIM instead of NV?
Did you compile the AOSP yourself? What build are you using? Project Elite's baseband and network all work out of the box no problems. I'm not sure if they posted it yet though.
Dubbsy said:
have you gone into network settings and verified that your subscription is set to RUIM/SIM instead of NV?
Click to expand...
Click to collapse
Yes; Whenever I do that I get the logcat I mentioned above and the setting doesn't stick (ie it immediately changes back to NV).
Edit:
When I retried, I got:
Code:
E/CdmaSubscriptionListPreference( 1618): Setting Cdma subscription source failed
Dubbsy said:
Did you compile the AOSP yourself? What build are you using? Project Elite's baseband and network all work out of the box no problems. I'm not sure if they posted it yet though.
Click to expand...
Click to collapse
No; this is with several 4.3 based ROMs including CM and Pacman.
Edit 2:
I'm downloading the Darkslide ROM to try to get that baseband installed and will keep this thread up to date with the result.
murphycr said:
Yes; Whenever I do that I get the logcat I mentioned above and the setting doesn't stick (ie it immediately changes back to NV).
Edit:
When I retried, I got:
Code:
E/CdmaSubscriptionListPreference( 1618): Setting Cdma subscription source failed
No; this is with several 4.3 based ROMs including CM and Pacman.
Edit 2:
I'm downloading the Darkslide ROM to try to get that baseband installed and will keep this thread up to date with the result.
Click to expand...
Click to collapse
Oh you aren't running pure aosp. Gotcha.
I was able to hold subscription on PAC, Slim, and CM10.2
Did you edit anything prior to install? Was your phone's data working just before switching to 4.3?
Dubbsy said:
Oh you aren't running pure aosp. Gotcha.
I was able to hold subscription on PAC, Slim, and CM10.2
Did you edit anything prior to install? Was your phone's data working just before switching to 4.3?
Click to expand...
Click to collapse
Yes. It also works if I switch back to 4.2, but then other things break. Anyway, I'm about to flash the baseband you referred to, so I'll see where that gets me.
Thanks!
murphycr said:
Yes. It also works if I switch back to 4.2, but then other things break. Anyway, I'm about to flash the baseband you referred to, so I'll see where that gets me.
Thanks!
Click to expand...
Click to collapse
the baseband used in all 4.3 builds I've used was MDK.
Me7 baseband is not as good as some people like to claim. It is buggy, and in my opinion it was rushed to release because Verizon wanted to quick kick everyone in the nuts. I tried me7 a few times and everytime I had worse spottier service.
The project elite aosp I was talking about is actually full aosp. And I haven't seen a post for it yet.
Another thing I've noticed in general... What recovery are you using? I don't trust CWM(any variation) at all anymore. I've seen too many installs act up and just not work right at all with CWM and after trying it on twrp 2.5.0.2 the same exact installer worked fine. :silly: I don't know why, but regardless the layout of CWM is piss poor anyway. If you are using CWM, click the link in my sig to go to my GE build. In the second post I have flashable recoveries posted. You can try one out just to see and if you get the same results just flash back to your desired/current recovery:good:
I was having the same problem with my own cm10.2 builds. I blew out my device and vendor repos several times and finally decided that there had to be something in frameworks that doesn't like the dev edition radios. The nightlies wouldn't even work. I ultimately wound up using the official cwm (non-loki only) and was finally able to change from nv to ruim/sim.
Sent from my SCH-I545 Dev Edition using xda app-developers app
So you used the non-loki'd CWM to do what fixed it? (I presume simply having it installed didn't fix it automatically)
On the dev edition, the general consensus in the beginning was that philz touch(cwm based) was the recovery to use probably because he offered a non-loki version. We don't need loki fortunately because of our unlocked bootloader. I later found out that official cwm was also not lokified. If you have the retail version, unfortunately you are stuck with the loki recovery. I was just suggesting that you might try a different cwm since they are not all created equal.
Edit: I guess what I was really trying to say is just try another recovery. Not necessarily one over the other (cwm vs. twrp). It's not the non-loki part that will make the difference. Hopefully you'll find one that works for you. But who would have known that would cause it.
Sent from my SCH-I545 using xda app-developers app
OLD&SLOW said:
On the dev edition, the general consensus in the beginning was that philz touch(cwm based) was the recovery to use probably because he offered a non-loki version. We don't need loki fortunately because of our unlocked bootloader. I later found out that official cwm was also not lokified. If you have the retail version, unfortunately you are stuck with the loki recovery. I was just suggesting that you might try a different cwm since they are not all created equal.
Edit: I guess what I was really trying to say is just try another recovery. Not necessarily one over the other (cwm vs. twrp). It's not the non-loki part that will make the difference. Hopefully you'll find one that works for you. But who would have known that would cause it.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I've tried both TWRP and PhilZ. Neither seemed to do it. At this point I'm just going to do a full ODIN.
Thanks for all the help though!
No problem, I just hope you figure it out. There are too many people using aosp 4.3 roms with no problems for this to be impossible. :thumbup:
Sent from my SCH-I545 using xda app-developers app
murphycr said:
I've tried both TWRP and PhilZ. Neither seemed to do it. At this point I'm just going to do a full ODIN.
Thanks for all the help though!
Click to expand...
Click to collapse
I have an already Loki patched cwm touch posted in my list if you wanted to try it too.
I've found Odin helps clean all the garbage out though. So either way
Good luck!
sent from my Verizon Galaxy sIV
So I've been working on my dna for about 4 days now trying to get a kit-kat rom that has working wifi on it. But as I've read I don't think one exist. Can anyone confirm this? I was on a NOS rom before that worked perfectly.
Also, been trying to update my baseband (to fix wifi?) but nothing seems to work. I keep getting a fail message when the tool kits try push the zip through.
Error messages and phone details are attached.
Thank you in advance for any help and suggestions you guys can offer.
tommynox said:
So I've been working on my dna for about 4 days now trying to get a kit-kat rom that has working wifi on it. But as I've read I don't think one exist. Can anyone confirm this? I was on a NOS rom before that worked perfectly.
Also, been trying to update my baseband (to fix wifi?) but nothing seems to work. I keep getting a fail message when the tool kits try push the zip through.
Error messages and phone details are attached.
Thank you in advance for any help and suggestions you guys can offer.
Click to expand...
Click to collapse
To varying degrees, WiFi works on all KitKat ROMs, with the exception of CM11 (at least that's been my experience). I've tried all of them, the two that I've found to be the best are Slimkat and AOSPA. Both of those worked best on my DNA.
As far as updating your radio is concerned, couldn't you use an app like Flashify?
In the end, I actually use a 4.2.2 ROM because everything works - and the WiFi/LTE is very stable. I currently use ViperDNA 2.5.2. Having the latest and greatest ROM isn't all that awesome if some of it doesn't work or is unstable.
Yehudah said:
To varying degrees, WiFi works on all KitKat ROMs, with the exception of CM11 (at least that's been my experience). I've tried all of them, the two that I've found to be the best are Slimkat and AOSPA. Both of those worked best on my DNA.
As far as updating your radio is concerned, couldn't you use an app like Flashify?
In the end, I actually use a 4.2.2 ROM because everything works - and the WiFi/LTE is very stable. I currently use ViperDNA 2.5.2. Having the latest and greatest ROM isn't all that awesome if some of it doesn't work or is unstable.
Click to expand...
Click to collapse
Flashify? Thats the first time I've seen that. I look into it, Thanks!
As for Roms, this whole mess started when I wanted to get the newer "Video Highlight" Feature that allows you to add your own music.
Im going to look into some other 4.2.2 ROMS and see what I can find. Im really digging Kit-Kat though. If anyone has a fave that they like please let me know.
Thanks for the help, Yehudah!
tommynox said:
Flashify? Thats the first time I've seen that. I look into it, Thanks!
As for Roms, this whole mess started when I wanted to get the newer "Video Highlight" Feature that allows you to add your own music.
Im going to look into some other 4.2.2 ROMS and see what I can find. Im really digging Kit-Kat though. If anyone has a fave that they like please let me know.
Thanks for the help, Yehudah!
Click to expand...
Click to collapse
My preference is ViperDNA 2.5.2. It's a Sense5 4.2.2 ROM with the Aroma installer. So you can install or not install as much or as little of the entire package as you like. I happen to like light ROMs, so I remove almost everything and only install stuff I use.
Haven't used any sense based KitKat roms, but I've never had a WiFi issue on cm or aosp based kk roms.
I use the viper 3.0.1 not updating to the newest version yet I'm letting them work some more bugs out.
Sent from my Nexus 7 using XDA Premium 4 mobile app
torecdude said:
Hi,
I'm trying to extend my battery life. I read fast dormancy can extend my battery life significantly, but it depends on my device and mobile network provider.
Should i remove it? any one has tried it and can give me some feedback?
Thanks!
Click to expand...
Click to collapse
after update to 4.2.2 atrix heats too much.......... any solution?
Samdroid1991 said:
after update to 4.2.2 atrix heats too much.......... any solution?
Click to expand...
Click to collapse
Create your own thread. it is a compkletely different problem. also, it has been answered in cm10.1's thread. in the last few pages, i think @palmbeach05 has covered this and other issues.
As for OP: AFAIK, fastdormancy comes preinstalled, depends upon your carrier and it automatically start to work whenever it detects your carrier supports it. but in my experience, i got better results removing it than wit it enablesd maybe due to the alpha nature of the kernel
andresrivas said:
Create your own thread. it is a compkletely different problem. also, it has been answered in cm10.1's thread. in the last few pages, i think @palmbeach05 has covered this and other issues.
As for OP: AFAIK, fastdormancy comes preinstalled, depends upon your carrier and it automatically start to work whenever it detects your carrier supports it. but in my experience, i got better results removing it than wit it enablesd maybe due to the alpha nature of the kernel
Click to expand...
Click to collapse
can u get me a link for atrix 4g stable ics kernel???
Samdroid1991 said:
can u get me a link for atrix 4g stable ics kernel???
Click to expand...
Click to collapse
Reported (again)
Samdroid1991 said:
can u get me a link for atrix 4g stable ics kernel???
Click to expand...
Click to collapse
All kernels nowadays are 3.1.10. This is, has been, and will be until officially upgraded, an Alpha stage kernel. This means that there are major bugs present. Are there kernels out there that are stable enough at this stage? Yes. Most are within the individual ROM threads, others are in krystian's dropbox.
There are 2 versions of ICS that are popular amongst A4G users, AtrICS v 2.0 and CM9. Which one are you trying to use?
andresrivas said:
Create your own thread. it is a compkletely different problem. also, it has been answered in cm10.1's thread. in the last few pages, i think @palmbeach05 has covered this and other issues.
As for OP: AFAIK, fastdormancy comes preinstalled, depends upon your carrier and it automatically start to work whenever it detects your carrier supports it. but in my experience, i got better results removing it than wit it enablesd maybe due to the alpha nature of the kernel
Click to expand...
Click to collapse
Thanks for your reply, do you use epinter CM 10.1 too? do you think i should make a nandroid backup and try removing it?
torecdude said:
Thanks for your reply, do you use epinter CM 10.1 too? do you think i should make a nandroid backup and try removing it?
Click to expand...
Click to collapse
ALWAYS make a backup prior to any test modifications. That way if removing fastdormancy makes things worse for you, you have something to fall back on without having to go through the hassle of reflashing the entire ROM.
torecdude said:
Thanks for your reply, do you use epinter CM 10.1 too? do you think i should make a nandroid backup and try removing it?
Click to expand...
Click to collapse
I used it for a while, then I got back to AtrICS. As @palmbeach05 said, always do a nandroid backup before messing with anything system related.
palmbeach05 said:
All kernels nowadays are 3.1.10. This is, has been, and will be until officially upgraded, an Alpha stage kernel. This means that there are major bugs present. Are there kernels out there that are stable enough at this stage? Yes. Most are within the individual ROM threads, others are in krystian's dropbox.
There are 2 versions of ICS that are popular amongst A4G users, AtrICS v 2.0 and CM9. Which one are you trying to use?
Click to expand...
Click to collapse
im trying to use CM9 screen goes black after lock!!!!!!! n never comes back untill restart
i had same prblm with CM10.1 but i solved it using anothr kernel
can u suggest any kernel for CM9 ??
Samdroid1991 said:
im trying to use CM9 screen goes black after lock!!!!!!! n never comes back untill restart
i had same prblm with CM10.1 but i solved it using anothr kernel
can u suggest any kernel for CM9 ??
Click to expand...
Click to collapse
Sorry, wrong thread ^^
Try them all and see the one taht fits you better
Samdroid1991 said:
im trying to use CM9 screen goes black after lock!!!!!!! n never comes back untill restart
i had same prblm with CM10.1 but i solved it using anothr kernel
can u suggest any kernel for CM9 ??
Click to expand...
Click to collapse
Ok and you're experiencing a problem everyone has had or still has. Stop complaining or start developing a fix. Can't develop? Don't complain. Simple as that. Besides that, I mentioned it before, but I will reiterate the point again. THE 3.1.10 KERNEL IS AN ALPHA STAGE KERNEL. ALL ROMS RUNNING A 3.1.10 KERNEL BECOME ALPHA STAGE ROMS AS WELL. ALL LOWER REVISION KERNELS ON ANY 4.0 AND UP ROM WILL PROVIDE ISSUES AS WELL. This is pretty much a deal with what we, the devs of xda, can provide to you and other users, or move onto a new ROM or a new device.
Okay so I have a Samsung galaxy s2 gt-i9100. I have rooted the phone and I thought to have installed cwm (which came with the root)
but I still boot into stock recovery (even though Rom manager tell me I have cwm 5.x.x installed or something along those lines).
I know now that the kernel resets to stock recovery. So i am running 4.1.2 and my build number (found in 'about phone') is JZO54K.I9100XWLSW.
I have downloaded 'philZ-cwm6-XWLSW-XEU-5.06.1.zip' from his XDA thread, and was wondering is this the right one for me. And since I am already rooted and all that I was also wondering if installing this will clash with my root and mess up everything- thanks in advance, I really appreciate the help.
You got the right one and are good to go.It won't "mess" anything,you'll basically get a stock kernel+cwm+root in a single flash.Good for starters if I may.
This is the exact method I used to root, and now I'm happily running my (probably) 30th different custom rom.......
Sent from my GT-I9100 using XDA Developers app
Don't use ROM Manager on S2. Ever. It's a sure way to screw things up. For some reason it seems to end up corrupting recovery on S2.
Why are n00bs so attracted to Rom Manager ? It's **** on any device. Only lazy people use it on the devices it actually works properly on.
MistahBungle said:
Why are n00bs so attracted to Rom Manager ? It's **** on any device. Only lazy people use it on the devices it actually works properly on.
Click to expand...
Click to collapse
Your not very nice, to be fair how am I supposed to know that it breaks the recovery. Everyone has to start somewhere
LiamFlannery said:
Your not very nice
Click to expand...
Click to collapse
There was nothing 'not nice' about what I said. Rom Manager is a POS. Lazy people use it. You weren't specifically mentioned in my post, you were lumped in with all the other n00bs. There's nothing special about you in that regard.
See ? That last sentence was somewhat 'not nice' *adds you to my ignore list*
okay thanks everyone for the helpful replies, also I was just wondering whats the difference between XWLSW-OXX and the one I am going to use which is XWLSW-XEU? just out of curiosity -thanks
LiamFlannery said:
okay thanks everyone for the helpful replies, also I was just wondering whats the difference between XWLSW-OXX and the one I am going to use which is XWLSW-XEU? just out of curiosity -thanks
Click to expand...
Click to collapse
Philz's kernel OP has answers to all your questions.
We should all do this on playstore.