This is my first post on XDA but i have floated around for a bit learning things and picking things up for a while now. I appreciate all that i have learner. I started with the Nexus One which my gf now uses and i have the Galaxy Nexus.
A bit confused though,
I have the CDMA unlocked and rooted on stock rom with TUNA 13u Kernel. Id really like to use Franco Kernel and a new rom.
My question is, can i just flash a 4.0.3 rom onto the phone or will i lose my radios and not be able to make calls? Ive seen leaked radios but wasnt sure if those were just if you had poor signal, which i dont.
This is the ROM i was going after - http://forum.xda-developers.com/showthread.php?t=1424701
This is the Kernel i was after - http://forum.xda-developers.com/showthread.php?t=1422956
fwiw i looked all over the GNex pages, or what i believed to be the proper ones to find the answer... only thing i see is "for 4.0.1 - 4.0.2" or "for 4.0.3 - 4.0.4"
but nothing stating how to get from one to the other.
Thanks a TON for any input!
J
ROM's usually don't contain radios. They do come with their own kernel. The radio is what controls how Android connects with the baseband and therefore whether or not you can make calls or not. If you don't flash a radio, you'll be able to make phone calls same as you do now (aside from odd issues like the phone.apk crashing).
Kernels never come with radios. Kernels have to be compatible with the ROM you're using. Your chosen kernel is 4.0.3+, so it will work on your 4.0.3 ROM.
Flash your ROM, wipe everything and then flash the kernel. If something doesn't work right, try wiping everything again. If that doesn't work, reflash everything. If that still doesn't work, well, that ROM isn't for you.
ATnTdude said:
ROM's usually don't contain radios. They do come with their own kernel. The radio is what controls how Android connects with the baseband and therefore whether or not you can make calls or not. If you don't flash a radio, you'll be able to make phone calls same as you do now (aside from odd issues like the phone.apk crashing).
Kernels never come with radios. Kernels have to be compatible with the ROM you're using. Your chosen kernel is 4.0.3+, so it will work on your 4.0.3 ROM.
Flash your ROM, wipe everything and then flash the kernel. If something doesn't work right, try wiping everything again. If that doesn't work, reflash everything. If that still doesn't work, well, that ROM isn't for you.
Click to expand...
Click to collapse
Flash ROM then Wipe everything??
Ok, so only the Kernel is dependent on version.
I can flash any version or rom i want to my phone as long as i have an appropriate kernel?
If i do then have an issue with calls it is only because that kernel and rom are not mating well with my radios.
recovery - clear cache - wipe - load from .zip - wait - reboot - wait some more -enjoy?
thanks a lot ATnt!
J
Related
I want to preface this by apologizing if this has been covered, but I was unable to find anything with a search.
Every single 3.70 based ROM results in wakelock issues within 24-48 hours. I have tried everything, including flashing the stock rooted rom and no matter what, my phone stops sleeping after a day or so. I fully wipe, flash the rom, and I don't download a single app until the wakelock kicks in, at which point I grab spare parts and get no useful information.
I am currently alternating between CM7 and CM6 because AOSP roms work fine...they just aren't quite as solid as I would like them to be at this point. GPS bugs (I've tried the fixes), no HDMI (I've heard about the beta apps and I'll try those soon), no 4G (I realize this has been added to the nightlies for CM7, but the GPS issues are a deal breaker for now) and slow file transfers between my PC and my phone when using CM7 also kill the rom for me.
I figured I would simply flash the stock rooted 3.30.651.3 so that I could have a fully functional phone without wakelock issues if the need arose. But whenever I try to flash after a full wipe (including dalvik cache), I get stuck on the white HTC EVO screen. All 3.70 roms and AOSP roms flash fine so there must be something I'm missing...do I have to downgrade my radio or something? Any help would be greatly appreciated. And once again, I'm sorry for the post if this has been covered.
Yes the radio has to be downgraded first. I'm not sure which radio you need but you should check out one of Viruses rom threads since his roms are mostly 3.30 based.
Is there a way to for example flash wildfire s gingerbread rom and then change density?
Thanks.
No. Don't you think we would have had it a long time back then, if it were so simple? SFM is just that. Its based on the HTC Salsa Stock ROM, (The first release was based on the Wildfire S ROM, which had even more things not working) and you can see the results for yourself.
One more question... i installed jokersdroid 4.2 rom long ago, and i didnt have data connection. So i changed my rom to wildpuzzle, then cm etc. (everything was fine with data conn.) And now i flashed this http://forum.xda-developers.com/showthread.php?t=906557 (rooted), and the same problem appears... i tried to flash different radios, but still no change, i still cant activate my data connection. I really like stock roms, so i wanna keep this one... can you help me on this?
Thanks.
Aca902 said:
One more question... i installed jokersdroid 4.2 rom long ago, and i didnt have data connection. So i changed my rom to wildpuzzle, then cm etc. (everything was fine with data conn.) And now i flashed this http://forum.xda-developers.com/showthread.php?t=906557 (rooted), and the same problem appears... i tried to flash different radios, but still no change, i still cant activate my data connection. I really like stock roms, so i wanna keep this one... can you help me on this?
Thanks.
Click to expand...
Click to collapse
The custom ROMs include your operators APN by default (i.e. it's pre-configured). This is not the case in the Stock ROM (Since its untouched), so, you will have to add the APNs yourself, after which, I am pretty sure mobile data should work.
You have my thanks.
now i have other problems... sometimes i have singnal sometimes not, the same goes for data connection ... what now?
Honestly, I don't think this is ROM related, but, network issues. Were you getting such issues when you were on the Stock ROM (At that time when data wasn't working for you?).
Anyway, seems like the 2.34 Safe Flash RUU is causing you all sorts of problems (Which shouldn't really, because both WildPuzzle and JokerDroid use this very ROM as its base), so you might as well switch and install the WWE 2.22.405.1 Safe Flash RUU from here
http://forum.xda-developers.com/showthread.php?t=877977
You will have to re-enter APN again, as usual.
cant stop hitting the thanks button
i solved the problem with the signav and data conn... it seems it was all about nfinity kernel... strange...
Ok so I just recently updated to all the latest HBoots, PRI, WiMaxx, Radio etc and i am running the 3.5 version for latest Infected Rom w/ Beats....everything was working fine until I put the HBoot 2.16 on my phone. I also reflashed the Infected rom but for some strange reason my Wifi is not working on. Who knows who or what causes that to happen and how to fix it. Also when I first installed this Rom the Beats audio notify would display but no sound would play unless I disabled it....I might flash a new Rom soon but for future references what can I do or undo?
Sounds like the kernel didn't flash.
Hey, it sounds like either something is not compatible or it did not flash right, my rule of thumb is if it is working dont touch it lol, because there is no need to. But what you could do now, is either try flashing a new kernel but you may loose some of the features that the developer put in, or my suggestion just try out a new rom!
I'm looking to get some information on my what can be done to fix the Data Usage counter on my wife's i927R (Rogers) running the stock GB os. Currently any data counter application that is put on doesn't actually keep track of 3G/4G data correctly.
I have been reading up on just upgrading it to ICS but I recently read all about the phone call issues after it goes to sleep so I'll be holding off on that upgrade to that gets worked out.
I did notice that there were some GB Kernels (like ardatdat's) that say they fix the issue but they also do a bunch of other things like overclock which i'm not interested in.
Is there a way to just patch the existing stock kernal to correct the data counter issue? If so can you point me in the right direction of the files and steps to update?
Any help would be great.
Thanks
If you want a count of your data, message, and phone calls and are on att, dial *3282# into the phone and press call. It is very accurate and gives you the data in the form of a text message. Not sure if this is what you want, but this is what I do.
Sent from my SGH-I927 using xda app-developers app
The standard stock kernel can't be given that feature, you have to recompile it from source and then hope you get a working version. We are a small group compared to the other phones as our model is not quite as epic as the original as the original captivate galaxy s is still a great phone and being an attention whore still lol..
But we are All trying to do our best to get more mods out there.
I personally use ICS 4.0.4 stock (custom modded to my needs)
And run lite kernel 1.1.1 you may want to try an update to your ROM from gingerbread to ICS and I beleive at&t launched an official update with samsung, maybe try it and see if it helpa
Thanks for the replies but i'm not on AT&T but rather Rogers in Canada.
Also, I would update to ICS but from the other ongoing threads there is an issue with the phone not receiving calls\sms on those roms once it goes to sleep mode so i want to avoid that until it is fixed.
From the sounds of it the only solution is to flash a new kernel (such as ardatdat's) thats specifically says it fixes the issue. Perhaps I can figure out how to change overclock settings so that it runs stock speeds.
To flash a Kernel do I just use Odin like a Rom flash? Are there any How To's on Kernel flashing? I haven't found one around here for the glide.
Thanks
The AOSP ROMs default to stock clocks, why haven't you upgraded yet?
Craigatitus said:
Thanks for the replies but i'm not on AT&T but rather Rogers in Canada.
Also, I would update to ICS but from the other ongoing threads there is an issue with the phone not receiving calls\sms on those roms once it goes to sleep mode so i want to avoid that until it is fixed.
From the sounds of it the only solution is to flash a new kernel (such as ardatdat's) thats specifically says it fixes the issue. Perhaps I can figure out how to change overclock settings so that it runs stock speeds.
To flash a Kernel do I just use Odin like a Rom flash? Are there any How To's on Kernel flashing? I haven't found one around here for the glide.
Thanks
Click to expand...
Click to collapse
I come from rogers too.. the ICS update will work fine for you and overclock doesn't affect anything. I was using literom with lite kernel 1.1.1 before upgrading to cm10.. then pacman 18.2 and now on liquid smooth
You should at least upgrade to Ics.. phone runs faster and smoother and GPS is fixed in literom too.
What version of GB are you using ? I upgraded to the latest GB first when I got my glide and I don't recall data stats not working
The current os is 2.3.5 (Kernel 2.6.36.3), The latest one available for the phone through Kies. All the data usage counting apps do not work on this phone. They all report about 1/1000th of the actual usage. Wifi data reports correctly but thats not what's important.
roothorick: I searched for "AOSP Rom" and what i found was an alpha build with a bunch of known issues. As this is my wife's phone, this wouldn't go over well. Keeping the phone looking and functioning the same as much as possible is key.
yohan4ws: I was planning on upgrade to ICS but now i'm reading the threads about the issues with the phone not receiving calls or sms once it goes to sleep. That is unacceptable as it is the main purpose of having a phone. So you aren't experiencing any "no radio wake" issues with your setup?
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Could have been a bad flash / download
Did you check the md5sum?
leftcranium said:
Calls worked until I installed cm10.1 nightly. Now I can't be heard unless i turn on speaker phone. Sound is still crap but at least I can make a call.
I have tried a few nightly's and now I'm on the people's rom 3.14. (Loving tpr by the way). I doubt it is a hardware issue based on other reports and the fact it was fine until the custom roms.
I still use my phone as a phone from time to time and need it to work or I have to go back to stock.
Thanks
Click to expand...
Click to collapse
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
topherk said:
Let me make sure I'm understanding you correctly:
Your mic was working fine until you flashed the CM10.1 nightly. Afterwards, the other person could only hear you when you were on speakerphone.
You switched to TPR 3.14. This switch did not fix the mic problem.
You're thinking that switching back to stock (presumably unrooted) will fix this issue.
Please correct me if any of the above is incorrect.
If he issue isn't hardware-related, I'd bet it has to do with the kernel. Let me ask you the following:
Which CM10.1 nightly did you install? Did you see any other issues in the CM10.1 thread which might indicate problems with the nightly you flashed?
What kernel did you use while on CM10.1? I know that the newer kernels (3.4.y verses the old 3.0.y) have had issues and are just recently getting stable.
As CNexus asked,did you check the md5sum for the TPR Rom you flashed?
When you flashed TPR, did you do a full system wipe, or only a Factory Reset (data) wipe? I believe since you were coming from a 4.2.2 Rom (CM 10.1) to a 4.1.2 Rom (TPR), you should do a full system wipe. Some remnants of the CM10.1 kernel/system files could still be there, messing up the mic.
I would think re-flashing TPR (after checking the md5sum) with a full system wipe would fix your issue, but answering these questions would help us diagnose the problem better.
Click to expand...
Click to collapse
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
leftcranium said:
I think you have the symptoms correct.
I did a data wipe but not a factory reset before each rom install.
I started with this rom
cm-10.1-20130303-NIGHTLY-d2spr.zip
I tried 3/13, 3/24 and 3/27 before trying TPR3.14.
Click to expand...
Click to collapse
Yeah, a full system wipe might be the ticket. Let us know if that works.
I'm Back Baby
I tried a system wipe and a rooted stock rom. This didn't work. I then tried the LJ7_Stock_with_count_reset16 rom and my sound was ok. I cleaned out the mic hole with a pin and bam sound was like normal. I'm now back on TPRGS3.14 and everything is good. I think I had 2 issues but possibly only 1. messed up mic from multiple flashes and crap in the mic hole. I guess checking for a physical problem even as small as a mic debris is an easy first step.
thanks for the suggestions