Hey everyone, I kind of dropped out of the loop due to a soul crushing course-load, but I'm back! I've been reading around, but I want to ask a few questions to see what you all thing and make sure I didn't miss anything before getting back into Atrix dev/modding.
So without further ado!:
1) What ROMs are considered stable?- is CM7 a daily driver yet? Which ROMs that DO support webtop and the fingerprint sensor would you recommend as a daily driver?
2) Is there any way to upgrade to gingerbread that does NOT involve blowing an e-fuse? (from 4.1.83)
3) I see a lot of ROMs come with stock OC'd kernels. How does that affect battery life for those of you running these? Do the performance enhancements and battery savings from custom ROMs balance out the power usage from OCing on the Atrix?
4) Cake or pie?
Thanks in advance!
Redbluefire said:
Hey everyone, I kind of dropped out of the loop due to a soul crushing course-load, but I'm back! I've been reading around, but I want to ask a few questions to see what you all thing and make sure I didn't miss anything before getting back into Atrix dev/modding.
So without further ado!:
1) What ROMs are considered stable?- is CM7 a daily driver yet? Which ROMs that DO support webtop and the fingerprint sensor would you recommend as a daily driver?
2) Is there any way to upgrade to gingerbread that does NOT involve blowing an e-fuse? (from 4.1.83)
3) I see a lot of ROMs come with stock OC'd kernels. How does that affect batter life for those of you running these? Do the performance enhancements and battery savings from custom ROMs balance out the power usage from OCing on the Atrix?
4) Cake or pie?
Thanks in advance!
Click to expand...
Click to collapse
1)CM7 is stable for a daily driver, but only some BLUR based ROMs are going to be compatible with webtop.
2)http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
3)Battery has been the best ever for me on CM7 (even with OC), soooo much better than Blur imo!
4) The cake is a lie.
WiredPirate said:
1)CM7 is stable for a daily driver, but only some BLUR based ROMs are going to be compatible with webtop.
2)http://www.motorola.com/Support/US-EN/Android_Products/ATRIX-4G_Software_Update_Page
3)Battery has been the best ever for me on CM7 (even with OC), soooo much better than Blur imo!
4) The cake is a lie.
Click to expand...
Click to collapse
Thanks for the replies. I appreciate it
My problem with #2 is that the OTA update blows an e-fuse, which makes downgrading and other modding in general pretty difficult, if not impossible. Or have we worked a way around that now?
Redbluefire said:
Thanks for the replies. I appreciate it
My problem with #2 is that the OTA update blows an e-fuse, which makes downgrading and other modding in general pretty difficult, if not impossible. Or have we worked a way around that now?
Click to expand...
Click to collapse
Oh okay, I thought you meant the opposite, unlocking "blows a fuse" also. I would definately unlock and blow that fuse apposed to officially upgrading and blowing that fuse. I had read that upgrading to the official GB makes it much harder to go back and do all the mods and such, but didnt realize it "blew a fuse" just like unlocking does. How many "fuses" does this phone have lol?
Redbluefire said:
Hey everyone, I kind of dropped out of the loop due to a soul crushing course-load, but I'm back! I've been reading around, but I want to ask a few questions to see what you all thing and make sure I didn't miss anything before getting back into Atrix dev/modding.
So without further ado!:
1) What ROMs are considered stable?- is CM7 a daily driver yet? Which ROMs that DO support webtop and the fingerprint sensor would you recommend as a daily driver?
2) Is there any way to upgrade to gingerbread that does NOT involve blowing an e-fuse? (from 4.1.83)
3) I see a lot of ROMs come with stock OC'd kernels. How does that affect batter life for those of you running these? Do the performance enhancements and battery savings from custom ROMs balance out the power usage from OCing on the Atrix?
4) Cake or pie?
Thanks in advance!
Click to expand...
Click to collapse
1) CM7 is very stable, even in the weekly builds. Weekly builds have fingerprint scanner support, but you currently cant get webtop on CM. I would highly recommend it unless you absolutely need webtop. If you do, though, check out Darkside.
2)I belive if you install the unlocked bootloader and cwm, and then flash the Gingerbread fruitcake you wont blow the fuse. Avoid flashing the update either by OTA or through RSD, since those are the ways the fuse gets blown. Its been a while since I've looked into that so you may want to wait for someone else to confirm this.
In the event the fuse is blown, you can still downgrade to froyo through use of a cwm fruitcake.
Fruitcake cwm zips can be found here:
http://forum.xda-developers.com/showthread.php?t=1163009
3) I dont use an OC kernel so I cant say.
4) What kind of cake, and what kind of pie?
Jotokun said:
1) CM7 is very stable, even in the weekly builds. Weekly builds have fingerprint scanner support, but you currently cant get webtop on CM. I would highly recommend it unless you absolutely need webtop. If you do, though, check out Darkside.
2)I belive if you install the unlocked bootloader and cwm, and then flash the Gingerbread fruitcake you wont blow the fuse. Avoid flashing the update either by OTA or through RSD, since those are the ways the fuse gets blown. Its been a while since I've looked into that so you may want to wait for someone else to confirm this.
In the event the fuse is blown, you can still downgrade to froyo through use of a cwm fruitcake.
Fruitcake cwm zips can be found here:
http://forum.xda-developers.com/showthread.php?t=1163009
3) I dont use an OC kernel so I cant say.
4) What kind of cake, and what kind of pie?
Click to expand...
Click to collapse
Thanks for your response as well, but from what I understand the IHOP bootloader unlock also blows a fuse... albeit a different fuse, hence my question.
Related
Hello,
I have Vibrant firmware 2.2 T959UVKB5 Froyo Trigger Version 3.0.1 i need to upgrade to firmware 2.3, how can i do it? Sorry i'm newbie from android OS.
Thank for help
let me get this straight? ur on trigger 3.0.1 and u wanna know how to upgrade to 2.3.3 gingerbread? Well gingerbread hasnt been officially leaked for the vibrant yet. I mean u can download 2.3.3 roms that are ported from i900 gingerbread.
http://forum.xda-developers.com/showthread.php?p=13337270#post13337270
http://forum.xda-developers.com/showthread.php?t=1021383
those are both 2.3.3 roms i hope that helps.
The gingerbread Roms are VERY buggy. And not worth upgrading until all the bugs are worked out. I would stick with Trigger Rom until then. I am also using the Trigger Rom and also the Overstock kernel. Just my 2 cents throught. Good luck!
Sent from my SGH-T959 using XDA Premium App
darkside79 said:
The gingerbread Roms are VERY buggy. And not worth upgrading until all the bugs are worked out. I would stick with Trigger Rom until then. I am also using the Trigger Rom and also the Overstock kernel. Just my 2 cents throught. Good luck!
Sent from my SGH-T959 using XDA Premium App
Click to expand...
Click to collapse
Gingerbread roms are not "VERY buggy", not anymore anyway. With the exception of GPS almost everything is working like a charm. Surely battery might be an issue to some but even that have a fix or two now.
One thing though, these roms are anti-noobish, so make sure you read A LOT before flashing one. That's probably why many choose to stay away from them.
Abu-7abash said:
Gingerbread roms are not "VERY buggy", not anymore anyway. With the exception of GPS almost everything is working like a charm. Surely battery might be an issue to some but even that have a fix or two now.
One thing though, these roms are anti-noobish, so make sure you read A LOT before flashing one. That's probably why many choose to stay away from them.
Click to expand...
Click to collapse
I agree, it's very fast, responsive, and I've never had much trouble with 2.3.3 ROMs. I use Simply Galaxy RC3.2, and except for bricking my phone the first time I tried installing (ODIN'd back to stock, flashed trigger, flashed SG RC3.2), it's been working really well.
I calibrated my battery after installing which helped clear battery issues, Quadrant scores in 2200s, fast internet.
There are a few more issues than just GPS..
3D performances are not what they should be (fixed from what it used to be, but still can be laggy)
Battery can drain pretty quick if you aren't careful about what you leave running.
Headset jack auto-detect (must toggle headset jack to be active over the loudspeaker using a widget). Apparently there is a fix for this but it has not yet been successfully implemented into any kernel that is publicly available and no developer has looked at the fix which was posted.
On topic though, make sure you read the instructions and understand them before you try flashing a 2.3.3 ROM. If you have any questions about specific instructions for a ROM post it into the ROM development forum. Also know how to and be comfortable with going into download mode and using ODIN to flash to stock from the Vibrant splash screen or from Bootloop (vibrant splash screen to an attempt to boot OS and then a reboot and repeat indefinitely).
If you are uncomfortable with any instructions for the ROM installation even after clarification or are uncomfortable with the potential for bricking and cannot use ODIN or don't want to risk anything DO NOT FLASH A 2.3.3 ROM!
Happy flashing, I hope this helped.
This is more of a general suggestion to those making the TB GB roms and adding the kernel to them or thinking about it..
Since it would appear reading through the posts and trying out the kernel for myself, I have found that the current GB kernel just gives my phone fits and it appears that other's have the same issue. I know it works for some, wish mine did. But can we get or keep the GB Roms separate from the kernel for a bit?
My phone runs GB fine without the kernel, and it sounds like it runs fine for others as well, since the kernel appears to add issues, it makes it hard to try out Roms that have the kernel included.
Its just a suggestion and at least at some point down the road I (or we) could try the kernel(s) as it matures more. And for those that the kernel works on, they can use it..
Thanks!
If your talking about random reboots just let it throw a few, every time I change a GB kernel I get a few, then after that it's totally fine.
Me too. Mine usually reboots a few times right after I install and then just works.
Sent from my ADR6400L using XDA Premium App
I don't quite get what you're saying. Every rom has a kernel. It's basically what allows the software to communicate with the hardware. You can't take the kernel out of a rom or you don't have a complete functional operating system.
You need to remember that the leak was a test version, kind of like a cyanogenmod nightly. So things are going to be broken. They will fix them over time, especially as new leaks emerge.
In the meantime, if you are having problems, just go back to froyo for now. It's fast and fully functional. Gingerbread will be unleashed with ALL of it's greatness soon enough. Then we'll be anxiously awaiting ice cream sandwich
sent via rooted THUNDERBOLT with Tapatalk
sgtguthrie said:
I don't quite get what you're saying. Every rom has a kernel. It's basically what allows the software to communicate with the hardware. You can't take the kernel out of a rom or you don't have a complete functional operating system.
You need to remember that the leak was a test version, kind of like a cyanogenmod nightly. So things are going to be broken. They will fix them over time, especially as new leaks emerge.
In the meantime, if you are having problems, just go back to froyo for now. It's fast and fully functional. Gingerbread will be unleashed with ALL of it's greatness soon enough. Then we'll be anxiously awaiting ice cream sandwich
sent via rooted THUNDERBOLT with Tapatalk
Click to expand...
Click to collapse
He means including the modified kernel in the ROMs, and rather having users flash the modified version optionally. I think it is a valid point, and the kernel is something that is unrelated to the official release of Gingerbread. New kernels will come and the current ones are being worked on. What you may want to try is going into console and using speedtweak.sh to up the voltage if you are having reboot problems.
I know it gets hard to answer every question with a meaningless philosophical argument invalidating the question itself, but then again the forum has a minimum post count.
twistedumbrella said:
He means including the modified kernel in the ROMs, and rather having users flash the modified version optionally. I think it is a valid point, and the kernel is something that is unrelated to the official release of Gingerbread.
Click to expand...
Click to collapse
Exactly, I have no problem running the default kernel that comes with GB Gingerjane 1.2 Rom as their is another kernel to possibly fix camera issues and they are separate downloads. Once I load that kernel I start having all kinds of problems, I restore my backup and all is good. I have seen some posts that others run into a similar issue. I thought it would just be good to keep them separate right now if possible. Its possible that some of the other GB Roms would work too, but I have the same issue with those and they include the new kernel as well for camera fix. So I have assume (I know bad word) that the common issue with mine and possibly others just could be that kernel for whatever reason.
twistedumbrella said:
He means including the modified kernel in the ROMs, and rather having users flash the modified version optionally. I think it is a valid point, and the kernel is something that is unrelated to the official release of Gingerbread. New kernels will come and the current ones are being worked on. What you may want to try is going into console and using speedtweak.sh to up the voltage if you are having reboot problems.
I know it gets hard to answer every question with a meaningless philosophical argument invalidating the question itself, but then again the forum has a minimum post count.
Click to expand...
Click to collapse
"Meaningless philosophical argument"? I really don't see where you get that from, but whatever...
Also, a low post count doesn't mean you're a noob, just not as active at xda. This isn't the only forum site on the Internet.
I just saw something on twitter, jcase was posting the stock gb kernel in his thread, so there you go...
Edit: it's posted, happy flashing...
http://forum.xda-developers.com/showthread.php?t=1082001
Edit 2:
It's in the lightning rom thread too.
sent via rooted THUNDERBOLT with Tapatalk
sgtguthrie said:
I just saw something on twitter, jcase was posting the stock gb kernel in his thread, so there you go...
Edit: it's posted, happy flashing...
http://forum.xda-developers.com/showthread.php?t=1082001
Edit 2:
It's in the lightning rom thread too.
sent via rooted THUNDERBOLT with Tapatalk
Click to expand...
Click to collapse
Thanks.. that works too.
I'm trying to update my wife's phone to Simply Honey 5.1 coming from Sipmly Galaxy 2.8. Both ROMs use kernels by cmenard, and both kernels include Voodoo.
I have 2 questions about the installation:
1. The Simply Honey install instructions specifically say to use Odin. Is this necessary? I've never used Odin before and I've flashed my own Vibrant about a dozen times without a problem.
2. Since the ROM my wife is coming from has Voodoo enabled, and since Simply Honey 5.1 has Voodoo in the kernel, do I need to disable Voodoo before flashing? I thought that you only need to disable Voodoo if the kernel you're flashing doesn't support it -- is this inaccurate? Or is there some other reason to disable Voodoo before flashing?
Thanks for reading, and thanks in advance for any replies.
The more important question is: Does your wife like having her phone tinkered with?
The Gingerbread ROMs are coming along, but they're not quite stable yet. You might want to stick with Froyo unless your wife is a fan of tinkering and using workarounds for GPS and battery life issues.
As for your questions:
1) When in doubt, follow the creators install instructions to a "T".
2) I've seen quite a few ROMs recommend disabling Voodoo before flashing them, but never seen one say that disabling Voodoo would be harmful to flashing them. So I'd disable it just in case.
You're also going to need to switch to the Gingerbread bootloader if you're going to stick with an i9000 leaked Gingerbread ROM. Messing with the bootloader is the only way I know of to completely kill your phone if you mess it up. Fair warning!
If you want Gingerbread without having to mess with bootloaders, I suggest MIUI or CM7. CM7 just went stable, and I've had no major issues with MIUI since SS-12 Revamped came out. MIUI has the most robust theming system I've seen in a ROM, so your wife may enjoy it. Just be ready to have her phone covered in Pink with fluffy icons and whatnot when she's done with it
kaintfm said:
The more important question is: Does your wife like having her phone tinkered with?
The Gingerbread ROMs are coming along, but they're not quite stable yet. You might want to stick with Froyo unless your wife is a fan of tinkering and using workarounds for GPS and battery life issues.
...
Messing with the bootloader is the only way I know of to completely kill your phone if you mess it up. Fair warning!
Click to expand...
Click to collapse
Wow, thanks. You answered questions I didn't even know I had!
My wife wants a phone that "just works", but she wanted the speed and customizability of a custom ROM (her whole phone is already themed purple, haha), so I guess I'll go shopping for another Froyo ROM (or try to wipe and reinstall her current ROM to try to fix the crashes and accelerometer problems she's been having.)
Thanks again, I appreciate it.
A nice stable froyo ROM you can try is called toxic 8..since she likes themes, they have a bunch of them and the developer has added a lot of nice touches that are gingerlike
Again, if she likes theming and doesn't much use the GPS (it works, but requires an extra step or two), MIUI is unique and has the most robust theming of any Vibrant ROM.
I used to be a die hard fan of Simple Honey Roms, but they all became too unstable or had various issues, and caused me alot of problems and aggravation!! So far the only ROM that's been a super performer is team Toxic's Crazy 8 Froyo mixed with GB Rom, that works 100% with every option and with blazing speed and performance, Its your choice, but if you want to avoid the music from your wife when SH starts to hose up, Id stay away from it, especially 5.0 and double especially 5.1 but then again maybe your a gluten for punishment and NO MORE lovin from the wife, until things are right again. LOL Good luck JMHO based on experience with all the SH Rom's BTW I appreciates EB's work, but it still needs time to evolve, eventually there gonna be great ROM's.
I recently moved from an Evo to the Photon. I've used CM7 basically since it came out for the Evo and an very used to the interface and miss the simplicity of it... well, I think I miss the simplicity of it.
Since it has been about a month now I'm kind of itching for the hacking and tinkering that comes with custom ROMs instead of just stock. I'm curious, from those who have moved from Blur to CM7 or CM9 - is it worth it? I know CM9 is alpha and still missing features, which I'm fine with, I just need a little convincing that it's worth it. After 4 Evos I could root, install CWM and a ROM with my eyes closed, so any amount of effort on my Photon seems daunting again.
Once you get past the unlocking part, the rest is a cake walk. I'd recommend starting with CM7 just to get your feet wet again. CM9 is a great ROM (in my opinion) only lacking a camera. But you're going to be hard pressed to find too many people recommending against ROMing. Cm7 and CM9 are both quicker, seem to have better battery, and way less bloat.
Sent from my CWM OC'd CM7 Electrify.
Thanks. And with the Photon to get back to CM I need to unlock the bootloader right? Looks like the Pudding instructions are a one-stop shop for bootloader unlock, then root and getting CWM on. Once CWM is on I'm back into familiar territory.
I've had the pleasure of running both CM7 and CM9 alpha19 - personally, I really like the look and feel of CM9, and joker has done a fantastic job with it, but for my daily driver, I'm on CM7, and it has definitely not disappointed. You should try out both and have fun playing around, but right now CM7 is at a more polished state.
Best,
K
Unlocking break 4g as of now though... so be careful.
All the links for unlocking are broken. We need a new thread with new working links. I would start over from stock and tweak to CM7 till CM9 comes out. Which thread has the better CM7?
o1e63 said:
Unlocking break 4g as of now though... so be careful.
Click to expand...
Click to collapse
I don't have 4G where I live... probably never will since Sprint is transitioning to LTE.
Just curious - does unlocking permanently break 4g or will 4g work if you recover back to stock?
jeggen said:
I don't have 4G where I live... probably never will since Sprint is transitioning to LTE.
Just curious - does unlocking permanently break 4g or will 4g work if you recover back to stock?
Click to expand...
Click to collapse
It will recover to stock. Problem is the links provided are broken and I have no patience to look for hopeful working ones.
jeggen said:
I don't have 4G where I live... probably never will since Sprint is transitioning to LTE.
Just curious - does unlocking permanently break 4g or will 4g work if you recover back to stock?
Click to expand...
Click to collapse
It will not permanently break it. You just need to flash back to stock or locked ROM such as skinnyROM and you'll be fine.
Cm9
I would have to say to wait until cm9 has a better battery life and more stable but till then just use cm 7.2
OP,
I was in the same boat with the EVO on CM7. this is what id do and am doing...
Flash CM7 and configure it the way you want it. coming from the EVO, youll be blown away by the HP that the Photon has on CM7. be careful and wear a bib bc youll drool some. ha ha After youve enjoyed the CM7, id backup and then flash CM9 and help out with the testing. The more people we have catching issues and sharing tips, the better the project will be.
It only take that few minutes to restore the CM7 image and your back to a solid daily w camera. if you can live wo a camera for now (i personally dont need a phone as a camera) then hangout with CM9 crowd.
Either way, youll LOVE CM on the Photon over the EVO. Welcome to the Photon club!
This thread is making me want to root my Photon
I, too had an EVO that I rooted & loved CM7 on it. This thread is making me want to root the photon now. I know that I will for sure if the Photon doesn't get any ICS love!
You can oc cm7 with jokers kernels but that depends on your hardware. I was able to get 1.4, others could go 1.3. Even if you decide on jokers skinny rom, that has a custom kernel too.
Edit: I just read that you can of cm9. is that true?
Sent from my MB855
So my question still, Which thread is the CM7 I should use?
So it sounds like really no compelling reason to stay on stock rom except being lazy. Fair interpretation?
Sent from my MB855 using XDA App
jeggen said:
So it sounds like really no compelling reason to stay on stock rom except being lazy. Fair interpretation?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
Yes. The difference between bloated stock and light CM7 is night and day.
ZeroManArmy said:
So my question still, Which thread is the CM7 I should use?
Click to expand...
Click to collapse
Cm7.2 Kang rom 1-22
Sent from my MB855 using xda premium
This might be a silly question, but even with a locked bootloader, why can't we just use the stock bootloader as a bootstrap to launch a stripped-down ROM whose only purpose in life is to act like GRUB/HaRET and boot into our own kernel, then continue booting into our "real" ROM (which depends upon and actually uses the second kernel)? I have to admit that my kernel-level Linux knowledge is pretty minimal, but I was under the impression that on a Linux system, root is God and can do pretty much anything... so why not force a custom runlevel to shut down the stock kernel, then launch and fork into a different one after the fact?
Assuming this is possible, wouldn't it also solve the hard part of our 4G problem, by allowing the radio modem to be initialized with the hidden cert by the stock kernel, then pull the rug out from under it and replace the kernel with our own once it's done its job at startup?
For me there is no compelling reason to choose CM7 versus stock. CM9 would be the way to go if it had camera support.
Hopefully the upcoming Atrix soak test will give the devs the drivers they need to push CM9 to beta.
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
jeggen said:
So it sounds like really no compelling reason to stay on stock rom except being lazy. Fair interpretation?
Sent from my MB855 using XDA App
Click to expand...
Click to collapse
No - those of us who stay stock are not lazy, and there is absolutely no reason to descend into name-calling here.
I stay stock because I'm satisfied with my Photon stock - I will move to custom once ICS camera drivers are available.
Same here, CM7 on EVO was great.
Now that I have CM9 on my HP Touchpad, I am waiting for a stable build for CM9 for the Photon.
---
Deafcyclist said:
Sorry if the info is already out there. I'm nearing the end of the midterm week and may have missed the info. But I saw some mentions of burning a fuse on the motherboard if you flash the leaked ICS Rom and whatnot.
Other than your usual bricking risk, what is the hazard of flashing the roms with the newer drivers and even the leaked rom itself?
Will it make it impossible for me to downgrade?
Will it lock the bootloader? (I doubt it but better to be sure than anything else)
anything I should be aware of when flashing these roms?
I'm hoping to use the newer webtop so I can use DSLR Controller at the lapdock native resolution so I can tether and control my Canon T4i. the GB rom does not work that well with the app due to some limited cache that ICS apparently don't have the issue with.
Thanks
Click to expand...
Click to collapse
I'm not an expert, but:
1. No
2. No
I think the main risk is to burn something, since the reports from users are showing that phone is getting very hot.
Deafcyclist said:
Sorry if the info is already out there. I'm nearing the end of the midterm week and may have missed the info. But I saw some mentions of burning a fuse on the motherboard if you flash the leaked ICS Rom and whatnot.
Other than your usual bricking risk, what is the hazard of flashing the roms with the newer drivers and even the leaked rom itself?
Will it make it impossible for me to downgrade?
Will it lock the bootloader? (I doubt it but better to be sure than anything else)
anything I should be aware of when flashing these roms?
I'm hoping to use the newer webtop so I can use DSLR Controller at the lapdock native resolution so I can tether and control my Canon T4i. the GB rom does not work that well with the app due to some limited cache that ICS apparently don't have the issue with.
Thanks
Click to expand...
Click to collapse
You can downgrade to any rom but remember to do the proper formats. I installed the leak but it was too unstable in my phone so i downgrade to normal GB.
The bootloader won't lock as long as you don't flash it.
mateusdalpi said:
I'm not an expert, but:
1. No
2. No
I think the main risk is to burn something, since the reports from users are showing that phone is getting very hot.
Click to expand...
Click to collapse
Pretty much this (the possibility of the phone running warmer and putting extra wear and tear on your phone), and you can't relock the bootloader ever again.
Also IMO always do a Nandroid backup (and keep a copy of it stored somewhere other than your phone) before you jump into any new ROM...
Sent from my GT-I9100 using xda premium