Related
If there's already source for 4.0.3 why don't devs (whom i'll always not thanks enough for their work) makes an update? Only Google can make an incremental update and we need a full AOSP rom ?
? There are 4.0.3 roms
all the main roms i see in the dev section are 4.0.3
Sorry if i wasn't clear enough.
I mean: i'm on stock 4.0.1 and i don't want to wipe now. Isn't there a way to make an incremental update 4.0.3 instead of flashing an entire rom?
Also as a Nexus device, wasn't one of the benefits that Google would put out the updates very quickly?
They have 4.0.3 just sitting there, is there any reason why they're not putting it out?
The 4.0.3 roms are based off from the uncompiled 4.0.3 source that google releases to the public, which developers can compile and test their apps on.
As for your 4.0.1, is your device a yakju, or jakjuux? Check with the GN checker app on the market. If its jakjuux, it wont be updated until samsung says so, meanwhile if you are running jakju, you should be able to go to 4.0.2, which has been released as an OTA through google. Hope this helps.
Sent from my MZ604 using xda premium
F0l3ert said:
The 4.0.3 roms are based off from the uncompiled 4.0.3 source that google releases to the public, which developers can compile and test their apps on.
As for your 4.0.1, is your device a yakju, or jakjuux? Check with the GN checker app on the market. If its jakjuux, it wont be updated until samsung says so, meanwhile if you are running jakju, you should be able to go to 4.0.2, which has been released as an OTA through google. Hope this helps.
Sent from my MZ604 using xda premium
Click to expand...
Click to collapse
I'm yakju bu you didn't get my point or neither i'm not explaining what it could be only my imagination. BUT
If the source code it's released why it can't be a 6/10/20 mb packet that can upgrade my system like a FOTA update can do ?
Because 4.0.3 has some bugs that needs to be fixed. The 4.0.3 OTA was released for Nexus S then pulled because of the bugs it was having.
You think if it was ready, they'd release it. Give it time, people are so ungrateful when 95% of the Android Community are still on Android 2.3.X and below.
If you want it so badly, flash a custom ROM with 4.0.3 on it. If you don't want to, then you can't really complain.
zephiK said:
If you want it so badly, flash a custom ROM with 4.0.3 on it. If you don't want to, then you can't really complain.
Click to expand...
Click to collapse
I've never complained and you didn't answered my question
zephiK said:
Because 4.0.3 has some bugs that needs to be fixed. The 4.0.3 OTA was released for Nexus S then pulled because of the bugs it was having.
You think if it was ready, they'd release it. Give it time, people are so ungrateful when 95% of the Android Community are still on Android 2.3.X and below.
If you want it so badly, flash a custom ROM with 4.0.3 on it. If you don't want to, then you can't really complain.
Click to expand...
Click to collapse
Not really, there's a source released for the GNex from Google.
Sugar0, I will try compiling that stock source and tell you how it goes.
Arrio said:
Not really, there's a source released for the GNex from Google.
Sugar0, I will try compiling that stock source and tell you how it goes.
Click to expand...
Click to collapse
You don't need to! It's plenty of stock untouched AOSP roms and modified.
What i'm asking is:
is there an unofficial small update that will bring 4.0.3 to my GN that i can flash in recovery ? Not the full rom!
sugar0 said:
You don't need to! It's plenty of stock untouched AOSP roms and modified.
What i'm asking is:
is there an unofficial small update that will bring 4.0.3 to my GN that i can flash in recovery ? Not the full rom!
Click to expand...
Click to collapse
Oh then no.. not at the moment.
You could always just compile it yourself with "make otapackage", that will give you exactly what you're asking for.
Sent from my Galaxy Nexus using Tapatalk
magn2o said:
You could always just compile it yourself with "make otapackage", that will give you exactly what you're asking for.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Finally an on-topic answer! Why aren't those updates around ? Do i miss something ?
No, you didn't "miss" anything. It's just that most people who are going to take the time to setup a build environment are doing so to tinker with the source -- not just build a vanilla package. Either way, its not terribly difficult to setup and build -- especially with all the guides floating around XDA.
Sent from my Galaxy Nexus using Tapatalk
magn2o said:
You could always just compile it yourself with "make otapackage", that will give you exactly what you're asking for.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
That's not strictly true. The 'OTA' package you make when compiling the ROM from source is still a complete ROM as opposed to a small OTA update
It won't require a system wipe and will apply just like an OTA, which is what (I'm assuming) the OP wanted.
Sent from my Galaxy Nexus using Tapatalk
magn2o said:
It won't require a system wipe and will apply just like an OTA, which is what (I'm assuming) the OP wanted.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Yep! like nigthly build of Cyanogenmod. It doesen't matter if its 6mb or 120mb. So aren't there those updates around ? I can't understand why they don't make such updates
NOTE: DO NOT FLASH THIS TO YOUR PHONE> IT WILL HARD BRICK!
this is for any dev that wants to try and port android jellybean to the s3 Tmobile version. they already ported it to the internationl version so i think that might make it a little easier. here is the OP in the international section: http://forum.xda-developers.com/showthread.php?t=1737449
fcortes626 said:
NOTE: DO NOT FLASH THIS TO YOUR PHONE> IT WILL HARD BRICK!
this is for any dev that wants to try and port android jellybean to the s3 Tmobile version. they already ported it to the internationl version so i think that might make it a little easier. here is the OP in the international section: http://forum.xda-developers.com/showthread.php?t=1737449
Click to expand...
Click to collapse
Hmmm...
Wonder if we could take that ROM, change the updater-script to match our mounting points....then we just need a kernel....
Which we have one kernel already made. Not sure if it would work though.
If anyone would help set up a build environment that would work for our kernels and roms then I will gladly help and start learning.
Sent from my SGH-T999 using Tapatalk 2
brfield said:
Which we have one kernel already made. Not sure if it would work though.
If anyone would help set up a build environment that would work for our kernels and roms then I will gladly help and start learning.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
I think we'd need a stock CM9 based kernel though. If I understand correctly.
uoY_redruM said:
I think we'd need a stock CM9 based kernel though. If I understand correctly.
Click to expand...
Click to collapse
Well, it shouldn't take too long. It may be possible to build a CM9 Kernel for our phones using parts of the stock kernel that we have access to.
Once the JB source is released, an S3 port might actually be viable. Otherwise it's essentially just flashing a gnex image and praying something/anything works.
uoY_redruM said:
I think we'd need a stock CM9 based kernel though. If I understand correctly.
Click to expand...
Click to collapse
a CM9 kernel shouldn't be needed, just a modded kernel for our specific phone from what i believe.
We know this, but it's more of an experiment. Also, it helps work out anything we may need to do early on with the modules and drivers
Sent from my SGH-T999 using Tapatalk 2
Why not take this ROM, change the updater-script for our mount points, remove the flashing of the boot.img, flash ROM then flash the kernel Roman release?
Think that would work?
uoY_redruM said:
Why not take this ROM, change the updater-script for our mount points, remove the flashing of the boot.img, flash ROM then flash the kernel Roman release?
Think that would work?
Click to expand...
Click to collapse
It could, in theory. But we would need to work on the modules for anything to work. Could you post our mount points?
why does it have to be a cm9 kernel?
to be completely honest, as soon as we get a cm9 alpha, we will see some worth while stuff! but until then. TouchWiz it iz. We will have team kang's AOKP in no time im sure. i cant wait to see wuts to come. especially since this phone is at all the major carriers and they are all basically exactly the same! should be epic.
Radsolutionz said:
to be completely honest, as soon as we get a cm9 alpha, we will see some worth while stuff! but until then. TouchWiz it iz. We will have team kang's AOKP in no time im sure. i cant wait to see wuts to come. especially since this phone is at all the major carriers and they are all basically exactly the same! should be epic.
Click to expand...
Click to collapse
yea i think once one of the other major carriers (or ares) get cm9 then we will see some awesome stuff for everyones phone!
I think that the only thing that makes them different is the radios in the phone
uoY_redruM said:
Hmmm...
Wonder if we could take that ROM, change the updater-script to match our mounting points....then we just need a kernel....
Click to expand...
Click to collapse
uoY_redruM said:
I think we'd need a stock CM9 based kernel though. If I understand correctly.
Click to expand...
Click to collapse
uoY_redruM said:
Why not take this ROM, change the updater-script for our mount points, remove the flashing of the boot.img, flash ROM then flash the kernel Roman release?
Think that would work?
Click to expand...
Click to collapse
If aosp was that easy we would all be doing it but no... way more complex than that....
im on my phone. expect terrible typos.
howtomen said:
If aosp was that easy we would all be doing it but no... way more complex than that....
im on my phone. expect terrible typos.
Click to expand...
Click to collapse
Wishful thinking I suppose
in another note i found a mini tutorial on how to port it to other devices if anyone wants to try it here is the guide. it is an SDK port. note: i did not write this guide i am just posting a link to the authors op. you can thank him and/or donate to him. here isorum.xda-developers.com/showpost.php?p=28020178&postcount=36 the link:
fcortes626 said:
in another note i found a mini tutorial on how to port it to other devices if anyone wants to try it here is the guide. it is an SDK port. note: i did not write this guide i am just posting a link to the authors op. you can thank him and/or donate to him. here isorum.xda-developers.com/showpost.php?p=28020178&postcount=36 the link:
Click to expand...
Click to collapse
Link is broken, im not meaning to be a lazy pest.
sswb27 said:
Link is broken, im not meaning to be a lazy pest.
Click to expand...
Click to collapse
sorry about that :silly:
here you go: http://forum.xda-developers.com/showpost.php?p=28020178&postcount=36
fcortes626 said:
sorry about that :silly:
here you go: http://forum.xda-developers.com/showpost.php?p=28020178&postcount=36
Click to expand...
Click to collapse
i also have a deodexed system dump of jb if you want it let me know.
Source is out
Sent from my Galaxy Nexus using Tapatalk 2
THE ISSUES WITH THE NIGHTLIES/DAILIES NOT BEEN BOOTING HAS BEEN FIXED! THESE NIGHTLIES/DAILIES WORK PERFECTLY NOW!
Hey guys. I recently decided to do something to pass the time until I get my Nexus 4, in 13 days, as of today. I went with compiling a few AOKP nightlies, since I had a buildbot on my hands with nothing to do with it, haha. Before you guys go off on me saying there won't be any more changes because AOKP isn't doing any more builds until 4.2 gets published to the AOSP source tree, let me tell you this doesn't mean that they won't be making changes and adding features everyday to the source code. It just means no more builds. So, with these nightlies/dailies, you'll get all the newest features and bugfixes on the day they get pushed to the source code of AOKP. I will NOT be providing changelogs at this time, because I'm busy enough with school and homework, and don't want to add flashing a ROM everyday and sifting through the changes to create a log for you guys to it. Also, PLEASE REPORT YOUR EXPERIENCES IN THE THREAD. Anyways, without further ado, here you go.
Features
Compiled directly from AOKP source
Extremely fast
Compiled everyday, so it has the newest features.
Click to expand...
Click to collapse
How to Flash
I AM NOT RESPONSIBLE IF YOU DON'T MAKE A BACKUP OR IF YOUR DEVICE STARTS A WORLD WAR II BEACUSE YOU'RE RUNNING MY NIGHTLIES/DAYLIES.
1. Download the ROM and Gapps
2. Darkside Super Wipe (UNLESS YOU'RE ON CWM 6+. THEN JUST WIPE CACHE, DATA, AND DALVIK.)
3. Wipe Data/Factory reset once again, just to be safe.
4. Flash the ROM
5. Flash the Gapps
6. Darkside Cache Wipe (UNLESS YOU'RE ON CWM 6+. THEN JUST WIPE CACHE.)
7. Reboot and let it sit for 10 minutes.
8. Reboot again, and have fun.
Click to expand...
Click to collapse
Change Log
http://gerrit.sudoservers.com/#/q/status:merged,n,z
Click to expand...
Click to collapse
Downloads
Choose the latest ROM: Link
Gapps: Link
Click to expand...
Click to collapse
First! Nice work! Can't wait to see what this has over regular aokp
Sent from my iPhone kryptonite with H0tcakez
iNeedICS said:
First! Nice work! Can't wait to see what this has over regular aokp
Sent from my iPhone kryptonite with H0tcakez
Click to expand...
Click to collapse
It is regular AOKP, just compiled from source everyday, so all the new features and bugfixes released in the AOKP source everyday are implemented.
KonstantinKeller said:
It is regular AOKP, just compiled from source everyday, so all the new features and bugfixes released in the AOKP source everyday are implemented.
Click to expand...
Click to collapse
Oh ok still nice maybe u should consider adding a personal touch?
Sent from my iPhone kryptonite with H0tcakez
iNeedICS said:
Oh ok still nice maybe u should consider adding a personal touch?
Sent from my iPhone kryptonite with H0tcakez
Click to expand...
Click to collapse
Well, I only have 13 days before I get a new phone, so I don't think it would be worth it, since AOKP is still an amazing ROM.
so how is this any diff from dougshells aokp nightly builds?
tuffballa said:
so how is this any diff from dougshells aokp nightly builds?
Click to expand...
Click to collapse
No cherry picks bro
Sent from my iPhone kryptonite with H0tcakez
tuffballa said:
so how is this any diff from dougshells aokp nightly builds?
Click to expand...
Click to collapse
EDIT: iNeedICS beat me to it. No cherry picks. Pure AOKP. Plus, I'll be attempting to fix a few bugs myself, if any are reported.
thx for good work. i have a problem.?
wipe cache data /storage
flashed rom
flashed gapps
wipe cache and dalvik
reboot then
samsung text and BLACK SCREEN. i ve tried three times same result.
tiger19 said:
thx for good work. i have a problem.?
wipe cache data /storage
flashed rom
flashed gapps
wipe cache and dalvik
reboot then
samsung text and BLACK SCREEN. i ve tried three times same result.
Click to expand...
Click to collapse
How long have you waited at the black screen?
about 5 minutes
tiger19 said:
about 5 minutes
Click to expand...
Click to collapse
Hmm. Interesting. What recovery are you using?
KonstantinKeller said:
Hmm. Interesting. What recovery are you using?
Click to expand...
Click to collapse
twrp 2.3.1.1
tiger19 said:
twrp 2.3.1.1
Click to expand...
Click to collapse
Alright. I'll start another build where it uses a prebuilt kernel instead of building a kernel from source. Maybe that's the issue. Should be built in about 30 minutes.
this time i ve waited more than 5 min. and same
tiger19 said:
this time i ve waited more than 5 min. and same
Click to expand...
Click to collapse
Like I said, starting a new build. Anyone else have this issue?
Sorry about taking so long with the new build. I had to redownload the entire 10gb source code. Starting build now.
I've only gotten one report of this ROM not booting. Someone else who flashed this please give me some feedback here.
KonstantinKeller said:
It is regular AOKP, just compiled from source everyday, so all the new features and bugfixes released in the AOKP source everyday are implemented.
Click to expand...
Click to collapse
Thanks for the break. I will be laying low over the next few days taking care of my new born daughter. I may knock out another cherry build tomorrow but until then, hold it down brother
Sent from my SAMSUNG-SGH-T989 using xda premium
Dougshell said:
Thanks for the break. I will be laying low over the next few days taking care of my new born daughter. I may knock out another cherry build tomorrow but until then, hold it down brother
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I'll try. I'm currently having issues with the buildbot. Brunch isn't working correctly, and I can't compile without kernel source without it. I don't even know if the issue that guy is having is a legit issue, since nobody is giving me feedback when it has 25 downloads.
PSA - newest binaries released!
If anyone manages to extract them for TORO (or for magure/toroplus for that matter) and can build a flashble update zip, would you please post here? For some reason I can't extract the shell scripts...my ubuntu build must be shot. Source: https://developers.google.com/android/nexus/drivers#torojdq39
klobkelosh said:
PSA - newest binaries released!
If anyone manages to extract them for TORO (or for magure/toroplus for that matter) and can build a flashble update zip, would you please post here? For some reason I can't extract the shell scripts...my ubuntu build must be shot. Source: https://developers.google.com/android/nexus/drivers#torojdq39
Click to expand...
Click to collapse
I'm on a Windows machine and came across those on Google's site. I used a text editor to open the shell script and then deleted all lines above the binary data, then saved, then renamed the file with a .tar.gz extension. I could then open that and see all of the files. Try that.
Turns out I had a space on the file path! Thanks mmuzzy for pointing that out...
If anyone wants the TORO binaries as a flashable zip, here: http://d-h.st/fpN
Tested on cm 10.1 latest nightly. All ok. Even fixes a gps issue with cm.
Tiny did a few more tweaks. His version fixes the gps wakelock issue:
New link: URL=http://d-h.st/Lgo]422-JDQ39-toro-proprietaries.zip - 4.45 MB[/URL]
Tiny Pulled the file that caused dev-host to complain about a virus (fRom) that I originally included. Tiny can't find anything about this file so it's a false positive but to be sure, he uploaded a new zip and removed the old one
Thanks tiny!
Link fix
http://d-h.st/Lgo
Sent from my Galaxy Nexus using xda app-developers app
Maguro JB 4.2.2 JDQ39 Binaries
Hi guys!
Here's the Maguro JB 4.2.2 JDQ39 Binaries :good:
http://forum.xda-developers.com/showpost.php?p=38650434&postcount=2641
klobkelosh said:
PSA - newest binaries released!
If anyone manages to extract them for TORO (or for magure/toroplus for that matter) and can build a flashble update zip, would you please post here? For some reason I can't extract the shell scripts...my ubuntu build must be shot. Source: https://developers.google.com/android/nexus/drivers#torojdq39
Click to expand...
Click to collapse
I didn't know you were over here now :good:
CondemnedSoul said:
I didn't know you were over here now :good:
Click to expand...
Click to collapse
Hey hey cs! How you doing man?
Yeah, I've been over here since vzw gnex release day. You still deving?
klobkelosh said:
Hey hey cs! How you doing man?
Yeah, I've been over here since vzw gnex release day. You still deving?
Click to expand...
Click to collapse
Sweet.... I'm doing pretty good. Finally getting things in order with life. Yes, still deving.... just received a gnex yesterday. Checking things out over here and waiting on a sim card. Should have it Monday I think.
CondemnedSoul said:
Sweet.... I'm doing pretty good. Finally getting things in order with life. Yes, still deving.... just received a gnex yesterday. Checking things out over here and waiting on a sim card. Should have it Monday I think.
Click to expand...
Click to collapse
cool! Hoping you build for Toro!
I haven't pulled off my own ROM yet, but I've done a bunch of porting, theming, and tinkering, mostly for myself. See ya round!
Hi guys, can someone explain to me if these binaries are anything new for me if I previously installed Android 4.2.2 (JDQ39) factory image? Should I flash those new binaries now?
kamil.trebunia said:
Hi guys, can someone explain to me if these binaries are anything new for me if I previously installed Android 4.2.2 (JDQ39) factory image? Should I flash those new binaries now?
Click to expand...
Click to collapse
The binaries in this thread are for toro only. I wouldn't advise flashing them on maguro. There is a link to proper Gsm binaries a few posts back that can be flashed.
Sent from my Galaxy Nexus using Tapatalk 2
Nice.
Sent from my Paranoid Nexus 3.0
klobkelosh said:
cool! Hoping you build for Toro!
I haven't pulled off my own ROM yet, but I've done a bunch of porting, theming, and tinkering, mostly for myself. See ya round!
Click to expand...
Click to collapse
You should post them ... Don't be greedy! .... I will be soon
Sent from my ADR6400L using Tapatalk 2
kamil.trebunia said:
Hi guys, can someone explain to me if these binaries are anything new for me if I previously installed Android 4.2.2 (JDQ39) factory image? Should I flash those new binaries now?
Click to expand...
Click to collapse
Any factory image for the same android build will have the same binaries (and probably others that can't be distributed as open source) as the ones posted for aosp.
I pulled the GPS, Wi-Fi, and Bluetooth drivers from mwalt2's deodex of last night's ota leak: VZW_JDQ39_GPS+WIFI_DRIVERS.zip - 1.22 MB. Not sure if they are any different than the AOSP binaries, but here they are if you want them. Phone is deep sleeping like a baby, GPS locks right on, and Wi-Fi seems good.
klobkelosh said:
I pulled the GPS, Wi-Fi, and Bluetooth drivers from mwalt2's deodex of last night's ota leak: VZW_JDQ39_GPS+WIFI_DRIVERS.zip - 1.22 MB. Not sure if they are any different than the AOSP binaries, but here they are if you want them. Phone is deep sleeping like a baby, GPS locks right on, and Wi-Fi seems good.
Click to expand...
Click to collapse
Flashing these over Mmuzzy's 3/2 Vanilla build is ok?
n99hockey said:
Flashing these over Mmuzzy's 3/2 Vanilla build is ok?
Click to expand...
Click to collapse
Yes, should work fine.
Can these be flashed on a 4.1.2 ROM and get improvement?
Galaxy Nexus+Baked+Lean+TWRP=BOOM SHAKALAKA
TMFGO45 said:
Can these be flashed on a 4.1.2 ROM and get improvement?
Galaxy Nexus+Baked+Lean+TWRP=BOOM SHAKALAKA
Click to expand...
Click to collapse
Let us know after you flash it!
This thread is dedicated to my CM11.0 builds that will be built whenever I get around to it which will be at least weekly.
When I build it, it's always synced to the latest CM source along with a few additional cherry picks that either add functionality or are bug fixes/improvements.
Download ROM
There are several gapps packages floating around. Since there are none at http://goo.im/gapps for Kitkat, I use these:
http://www.androidfilehost.com/?a=show&w=files&flid=10306
As of the 12/18 buid, ART works with Banks' Gapps listed above.
Mirror (thanks MBQ_ for hosting space):
http://mbqonxda.net/tiny4579/gnex/cm11.0
You can help MBQ_ with hosting costs by donating to him.
Credits/Thanks
CyanogenMod team for the ROM
IAmTheOneTheyCallNeo for his tips and GCCFreedom build script
sparksco for his optimized Sabermod GCC 4.7 and 4.8 toolchains
Features
CM11.0
Sabermod GCC optimizations and commits (ROM built with 4.8/Kernel built with 4.7)
TODO
Add goo.im update support and instructions to github repo
MMS fix?
swarlesbarkely said:
MMS fix?
Click to expand...
Click to collapse
I don't know. I didn't include any special fixes. Can you link a source for this fix?
If it's synced from the latest repos, I'd imagine it's included.
Sent from my Galaxy Nexus using Tapatalk 4
I think he is referencing this commit. To fix mms and the about phone being unknown in the settings.
underwaterjr said:
I think he is referencing this commit. To fix mms and the about phone being unknown in the settings.
Click to expand...
Click to collapse
I believe you're right. Guess it hasn't been merged yet. fitsnugly must have cherry picked it for his CM builds.
modernbummer said:
I believe you're right. Guess it hasn't been merged yet. fitsnugly must have cherry picked it for his CM builds.
Click to expand...
Click to collapse
Nope. I don't have it yet.
http://review.cyanogenmod.org/#/q/status:merged,n,z
It's been merged.
So theoretically MMS should work fine?
MMS fix was just merged today not that long ago
Thank you tiny, love your 4.2.2 in my main driver and can't wait to try this one
Sent from my Galaxy Nexus using Tapatalk 4
swarlesbarkely said:
So theoretically MMS should work fine?
Click to expand...
Click to collapse
The MMS fix wasn't merged as of the time I built earlier today so the initial build doesn't have the fix. The next build will have the fix though.
The tuna kernel doesn't seem to play nicely with the Sabermod toolchain. Whether I compile CM's or mine with the toolchain, it always reboots right when it's about to finish booting the ROM.
tiny4579 said:
The tuna kernel doesn't seem to play nicely with the Sabermod toolchain. Whether I compile CM's or mine with the toolchain, it always reboots right when it's about to finish booting the ROM.
Click to expand...
Click to collapse
Maybe you could apply this fix to your ROM? I flashed it on a different ROM and it fixed MMS along with other framework issues
http://forum.xda-developers.com/showthread.php?t=1840666&page=364
Scroll down a little and you'll see non flashable and flashsble zip
antwong45157 said:
Maybe you could apply this fix to your ROM? I flashed it on a different ROM and it fixed MMS along with other framework issues
http://forum.xda-developers.com/showthread.php?t=1840666&page=364
Scroll down a little and you'll see non flashable and flashsble zip
Click to expand...
Click to collapse
As soon as I flash a kernel again the reboots stop. Are you able to flash the ROM without flashing the kernel afterwards and boot fine?
Sent from my One using Tapatalk 4
tiny4579 said:
As soon as I flash a kernel again the reboots stop. Are you able to flash the ROM without flashing the kernel afterwards and boot fine?
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
I'm not running this ROM right now, waiting to get home for WiFi to download.
I was just suggesting a fix for MMS problems.
Installed this last night, been playing with it all morning.
No problems so far... performs just as well as Tiny's 4.2.2 ROM. In other words, I love it.
tiny4579 said:
As soon as I flash a kernel again the reboots stop. Are you able to flash the ROM without flashing the kernel afterwards and boot fine?
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
Flashing without a different kernel causes a bootloop to the CM account setup screen. Flashing with your kernel works fine.
Sent from my Galaxy Nexus using Tapatalk 4
modernbummer said:
Flashing without a different kernel causes a bootloop to the CM account setup screen. Flashing with your kernel works fine.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Yep. I'm going to switch kernel toolchains. Do people want CM's kernel or mine built in?
Sent from my One using Tapatalk 4
tiny4579 said:
Yep. I'm going to switch kernel toolchains. Do people want CM's kernel or mine built in?
Sent from my One using Tapatalk 4
Click to expand...
Click to collapse
I, for one, am fine with either one.