Related
Was curious what the lag was. I have a fully stock vibrant. Not by choice, my phone is hardware locked. It runs very smooth, opening apps is very snappy.
Sent from my SGH-T959 using XDA App
Some phones suffer slow performance that can be seen in certain areas like the market or generally while operating the the phone.
Thanks G1. I appreciate the response.
Sent from my SGH-T959 using XDA App
All~G1 said:
Some phones suffer slow performance that can be seen in certain areas like the market or generally while operating the the phone.
Click to expand...
Click to collapse
Is it undoable though?
Like I want my phone unrooted and un modded when the update comes out.
*I've heard having it unrooted and unmodded = less problems when updating?
Jhnboy said:
Is it undoable though?
Like I want my phone unrooted and un modded when the update comes out.
*I've heard having it unrooted and unmodded = less problems when updating?
Click to expand...
Click to collapse
Yes it is completely reversible. I would say look into the "tips and tricks sticky" & the "rom bible". Search the forums for ODIN & adb, because they will be need to be up & running to revert.
As for the OTA update, there are 3 things that could happen. 1. You'll lose root and it will be locked (till someone roots that specific code) 2. Possibly the code (any code for example) will include something that can cause your phone to brick, not permanently, but it's possible. 3 nothing at all could happen but the update.
If the updates are anything like what we see on other phones, someone here will have that sucker modded by the time you wake up the next morning.
All~G1 said:
Yes it is completely reversible. I would say look into the "tips and tricks sticky" & the "rom bible". Search the forums for ODIN & adb, because they will be need to be up & running to revert.
As for the OTA update, there are 3 things that could happen. 1. You'll lose root and it will be locked (till someone roots that specific code) 2. Possibly the code (any code for example) will include something that can cause your phone to brick, not permanently, but it's possible. 3 nothing at all could happen but the update.
If the updates are anything like what we see on other phones, someone here will have that sucker modded by the time you wake up the next morning.
Click to expand...
Click to collapse
If its reversible then can't we just reverse the root and lag fix and have no problems with the OTA update?
Yes. As long as you take the right steps you can go back to non-rooted vibrant & get the OTA
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.
So, I understand the process of it.. but not really as to why.
Are you able to install anything N4 you want? Roms, kernels, etc? Or is it just the N4 converted roms from the dev section?
Is everything working? I've read mixed reports.
Thanks,
Nicholas
xsaqzw said:
So, I understand the process of it.. but not really as to why.
Are you able to install anything N4 you want? Roms, kernels, etc? Or is it just the N4 converted roms from the dev section?
Is everything working? I've read mixed reports.
Thanks,
Nicholas
Click to expand...
Click to collapse
The lgog and the nexus 4 are fairly similar phones. The reason we can't run nexus 4 ROMs is because some differences in the partitioning. Flashing the modified tot for the conversion converts your partition layout to that of a nexus 4 and installs the stock nexus 4 rom with an unlocked bootloader.You are supposed to be able to use nexus 4 ROMs and kernels. I've flashed like a 3 different nexus 4 ROMs
The problems that you might run into are with lte but that is fixable.
There is a fix for capacitive keys , nfc , and the external SD card which I were originally not working. The fix is a ROM so if you want all those things working you have to use it or properly patch another ROM with some of its files. There is also a flash able zip that but it is only compatible with certain ROMs.
The only "issue" in not having the full internal SD storage. You only have 8gb in comparison to 16gb but having large external SD should help storage wise.
However, apparently the conversion breaks the camera for the jelly bean stock port from the lg e973http://forum.xda-developers.com/sho...an LG-E973/1/5/0 CANADA / ATT / INTERNATIONAL. Camera works fine on every other stock based ROM when you convert back but apparently not on the jellybean port. It has not been proved but it has many claims supporting it. My camera does not work and I have converted.
Sent from my LG-E970 using xda premium
Dr0!dFreek said:
The lgog and the nexus 4 are fairly similar phones. The reason we can't run nexus 4 ROMs is because some differences in the partitioning. Flashing the modified tot for the conversion converts your partition layout to that of a nexus 4 and installs the stock nexus 4 rom with an unlocked bootloader.You are supposed to be able to use nexus 4 ROMs and kernels. I've flashed like a 3 different nexus 4 ROMs
The problems that you might run into are with lte but that is fixable.
There is a fix for capacitive keys , nfc , and the external SD card which I were originally not working. The fix is a ROM so if you want all those things working you have to use it or properly patch another ROM with some of its files. There is also a flash able zip that but it is only compatible with certain ROMs.
The only "issue" in not having the full internal SD storage. You only have 8gb in comparison to 16gb but having large external SD should help storage wise.
However, apparently the conversion breaks the camera for the jelly bean stock port from the lg e973http://forum.xda-developers.com/sho...an LG-E973/1/5/0 CANADA / ATT / INTERNATIONAL. Camera works fine on every other stock based ROM when you convert back but apparently not on the jellybean port. It has not been proved but it has many claims supporting it. My camera does not work and I have converted.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Dr0!d thanks for explanation. I have a question. Ever time I come back to stock I get an encryption error. What am I doing wrong?
Sent from my Xoom using xda app-developers app
jimi_pooh said:
Dr0!d thanks for explanation. I have a question. Ever time I come back to stock I get an encryption error. What am I doing wrong?
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
I got that error once. lgpnst doesn't really wipe partitions correctly before flashing ROMs. NownI wipe all of my partitions in recovery and then fastboot -w in command prompt before flashing back to stock . A data and cache is probably all that's needed but the flashing process takes a minute and I haven't had time to try it out. I think there is also something you can do at the encryption screen . it says like reset phone or something I think I've read that if you keep hitting it it will reset your phone or something idk sorry.
Sent from my LG-E970 using xda premium
Dr0!dFreek said:
I got that error once. lgpnst doesn't really wipe partitions correctly before flashing ROMs. NownI wipe all of my partitions in recovery and then fastboot -w in command prompt before flashing back to stock . A data and cache is probably all that's needed but the flashing process takes a minute and I haven't had time to try it out. I think there is also something you can do at the encryption screen . it says like reset phone or something I think I've read that if you keep hitting it it will reset your phone or something idk sorry.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Dude thanks a bunch. I'm going to try wiping like u suggested
Sent from my Xoom using xda app-developers app
jimi_pooh said:
Dude thanks a bunch. I'm going to try wiping like u suggested
Sent from my Xoom using xda app-developers app
Click to expand...
Click to collapse
That's what did the trick for me when I came back. Good luck
Sent from my Nocturnal'd Optimus G
Dr0!dFreek said:
I got that error once. lgpnst doesn't really wipe partitions correctly before flashing ROMs. NownI wipe all of my partitions in recovery and then fastboot -w in command prompt before flashing back to stock . A data and cache is probably all that's needed but the flashing process takes a minute and I haven't had time to try it out. I think there is also something you can do at the encryption screen . it says like reset phone or something I think I've read that if you keep hitting it it will reset your phone or something idk sorry.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
I tend to go back and forth doing the N4 conversion and back to At&t stock. I get this fail to encryption screen,some times after I LGNPST back to stock. Pressing the "reset phone" repeatedly never does anything for me. What i've been doing is when this happens is, I'll shut the phone down and press the Vol down and HOLD first and then hold the power button. It will bring you to some kind of factory recovery where it says "HARD RESET MODE" Just press the power button to confirm the reset and it essentially just wipes the phone and brings it back to stock.
Hope that helps!
Dr0!dFreek said:
The lgog and the nexus 4 are fairly similar phones. The reason we can't run nexus 4 ROMs is because some differences in the partitioning. Flashing the modified tot for the conversion converts your partition layout to that of a nexus 4 and installs the stock nexus 4 rom with an unlocked bootloader.You are supposed to be able to use nexus 4 ROMs and kernels. I've flashed like a 3 different nexus 4 ROMs
The problems that you might run into are with lte but that is fixable.
There is a fix for capacitive keys , nfc , and the external SD card which I were originally not working. The fix is a ROM so if you want all those things working you have to use it or properly patch another ROM with some of its files. There is also a flash able zip that but it is only compatible with certain ROMs.
The only "issue" in not having the full internal SD storage. You only have 8gb in comparison to 16gb but having large external SD should help storage wise.
However, apparently the conversion breaks the camera for the jelly bean stock port from the lg e973http://forum.xda-developers.com/sho...an LG-E973/1/5/0 CANADA / ATT / INTERNATIONAL. Camera works fine on every other stock based ROM when you convert back but apparently not on the jellybean port. It has not been proved but it has many claims supporting it. My camera does not work and I have converted.
Sent from my LG-E970 using xda premium
Click to expand...
Click to collapse
Thanks so much man!
Are there going to be any AOSP roms coming out native for the LGOG soon? If so, I'll hold off on the conversion. But if not, then I think I'll go ahead and do the conversion and flash Ginsex or one of the other JB ports. Are the cameras working on this if you flash the fix?
Nicholas
xsaqzw said:
Thanks so much man!
Are there going to be any AOSP roms coming out native for the LGOG soon? If so, I'll hold off on the conversion. But if not, then I think I'll go ahead and do the conversion and flash Ginsex or one of the other JB ports. Are the cameras working on this if you flash the fix?
Nicholas
Click to expand...
Click to collapse
Yes there are a couple of people working on aosp ROMs right now just give them a little more time
Sent from my LG-E970 using xda premium
I know some people are against the conversion as such, but I think in the long run, this will be the only benefit of this phone - I'm expecting LG to do its thing where they don't provide any updates once their newer phones come out.
And here comes the nexus4 conversion - we'll be able to advance our phones thanks to the actual updates for nexus4 that google and the community will provide. Probably we'll lose LTE at some point when the modems will no longer be compatible with newer android versions.
My previous phone, the captivate was in a similar scenario - slightly different from the international galaxy s, but the devs worked out a set of patches to be applied against the galaxy s roms to make them work on the captivate and the captivate has long lived since, becoming one of first phones to get cm10.1 nightlies and enjoying more than a few 4.2.1 roms. It's definitely slowing down, it's been more than 2 and half years since the phone launched and people have moved on to newer devices.
So if it wasn't for the nexus4 conversion, I wouldn't have jumped on the lgog for my upgrade - the phone shipped with ICS, might get a 4.1 update eventually, but I don't expect LG to follow up with further stock updates after 4.1.
I know there is speak of AOSP roms coming to the LGOG, and I'm really thankful for the all the devs who work bringing these, and hoping we'll even see official cm10.1/cm11 then probably we won't need the conversion at all, but if it doesn't happen, or devs give up on the lgog the conversion will be the only path to newest android.
I still dont understand why any dev is working on anything other than perfecting the n4 conversion. Doing anything else seems like a huge waste of effort and time to me. A perfectly functioning n4 conversion = this phone will be in the game for years and years. Anything else just means everyone is sol when the developers for this specific phone jump ship.. that will never happen with the n4 conversion.
There is also the odd (cant put my finger on it) veil of secrecy with this phone that i never bumped into before. So much info no one knows because its just simply not shared in any way.
whiteguypl said:
I still dont understand why any dev is working on anything other than perfecting the n4 conversion. Doing anything else seems like a huge waste of effort and time to me. A perfectly functioning n4 conversion = this phone will be in the game for years and years. Anything else just means everyone is sol when the developers for this specific phone jump ship.. that will never happen with the n4 conversion.
There is also the odd (cant put my finger on it) veil of secrecy with this phone that i never bumped into before. So much info no one knows because its just simply not shared in any way.
Click to expand...
Click to collapse
While I personally don't really agree with the first comment (I feel as though stock LG development has its place and there are dangers to the conversion), I definitely agree with the secrecy, on my old inspire I knew just about everything the devs were working on, what was and wasn't working, as well as which problems they were facing. With the LGOG I feel like I'm in the dark quite often.
Sent from my "Canadian" LG-E970
whiteguypl said:
I still dont understand why any dev is working on anything other than perfecting the n4 conversion. Doing anything else seems like a huge waste of effort and time to me. A perfectly functioning n4 conversion = this phone will be in the game for years and years. Anything else just means everyone is sol when the developers for this specific phone jump ship.. that will never happen with the n4 conversion.
There is also the odd (cant put my finger on it) veil of secrecy with this phone that i never bumped into before. So much info no one knows because its just simply not shared in any way.
Click to expand...
Click to collapse
This phone is already essentially a N4. We are working on methods of porting the nexus 4 kernel to our phone that do not require any modifications, so we will always be able to run anything the n4 can run anyway. Basically, there will be a longer wait because this is harder to do, but it will be better in the long run, as we fully understand what is going on.
Accept that the problem still stands with a ported kernel doesnt it? You guys leave and we need a new kernel and are s.o.l. . Also please dont take what im saying as any kind of insult, its not. Just looking to understand better.
Though i guess the same could be said for a perfected conversion is something in that needed changing.
There is now a fix for jelly bean rons after converting back to stock
http://forum.xda-developers.com/showthread.php?t=2146816
[FIX][Re-stock after N4][E970] Camera Fix for JB !!!ALPHA!!!
Sent from my LG-E970 using xda premium
whiteguypl said:
Accept that the problem still stands with a ported kernel doesnt it? You guys leave and we need a new kernel and are s.o.l. . Also please dont take what im saying as any kind of insult, its not. Just looking to understand better.
Though i guess the same could be said for a perfected conversion is something in that needed changing.
Click to expand...
Click to collapse
Of course both would need kernel changes to make everything work 100%. Either way, someone would need to fix things. Fixing the kernel to boot with full stock may take more work, but I would consider something that does not require modifying the non "normal" partitions of the phone to make work better than something that modifies the base bootloader of the phone.
whiteguypl said:
I still dont understand why any dev is working on anything other than perfecting the n4 conversion. Doing anything else seems like a huge waste of effort and time to me. A perfectly functioning n4 conversion = this phone will be in the game for years and years. Anything else just means everyone is sol when the developers for this specific phone jump ship.. that will never happen with the n4 conversion.
There is also the odd (cant put my finger on it) veil of secrecy with this phone that i never bumped into before. So much info no one knows because its just simply not shared in any way.
Click to expand...
Click to collapse
You're so right about the veil of secrecy!
C2fifield said:
While I personally don't really agree with the first comment (I feel as though stock LG development has its place and there are dangers to the conversion), I definitely agree with the secrecy, on my old inspire I knew just about everything the devs were working on, what was and wasn't working, as well as which problems they were facing. With the LGOG I feel like I'm in the dark quite often.
Sent from my "Canadian" LG-E970
Click to expand...
Click to collapse
HA! thank you! i HATE this stupid secrecy thing that alot of people in this community have. i have also never experienced anything like it. it really keeps things from expanding. people in here know that they run the risk of damaging their phone anytime they flash anything. the reason these people are keeping things secret is because they think that "dumb people will brick their phone". i have personally been running a solution to running n4 roms/aosp stuff without having to do any conversion for multiple weeks without any harm to my phone. i have a completely working cm-10.1 rom with full internal (16gb), full access to external, cap buttons, led lights, LTE, etc. everything works but i was told by members of team codefire that if i release it then i am an effing moron.
sk8erwitskil said:
HA! thank you! i HATE this stupid secrecy thing that alot of people in this community have. i have also never experienced anything like it. it really keeps things from expanding. people in here know that they run the risk of damaging their phone anytime they flash anything. the reason these people are keeping things secret is because they think that "dumb people will brick their phone". i have personally been running a solution to running n4 roms/aosp stuff without having to do any conversion for multiple weeks without any harm to my phone. i have a completely working cm-10.1 rom with full internal (16gb), full access to external, cap buttons, led lights, LTE, etc. everything works but i was told by members of team codefire that if i release it then i am an effing moron.
Click to expand...
Click to collapse
Who cares what team codefire thinks just keep doing what you are doing and thanks for everything can't wait to try something out. If you need more/any tester just let me know I have best buy insurance so not worried about bricking.
Sent from my LG-E970 using xda premium
sk8erwitskil said:
HA! thank you! i HATE this stupid secrecy thing that alot of people in this community have. i have also never experienced anything like it. it really keeps things from expanding. people in here know that they run the risk of damaging their phone anytime they flash anything. the reason these people are keeping things secret is because they think that "dumb people will brick their phone". i have personally been running a solution to running n4 roms/aosp stuff without having to do any conversion for multiple weeks without any harm to my phone. i have a completely working cm-10.1 rom with full internal (16gb), full access to external, cap buttons, led lights, LTE, etc. everything works but i was told by members of team codefire that if i release it then i am an effing moron.
Click to expand...
Click to collapse
I'd like to just chime in and say 1) one person said you'd be an effin moron and he is far from the whole of team codefire. His words and actions don't represent the team as a whole, and his words were uncalled for. He could have said things in a nicer way. 2) The cm-10.1 you have relies on a testing version of freegee that was developed, but since abadonded. The reason it was abadonded was quickly we discovered that it bricked sprint radios. We had 4 people, including myself, loose radio. Thus this new freegee method was dropped.
We are instead working with 3.4 lge kernel source. I've also narrowed down what I believe the issue is on mako kernel not booting stock, to be the lge power management vs caf/mako power management. We'd probably have lge 3.4 working by now, but all of us, sk8 included jumped on using mako kernel once it was discovered about this slightly different freegee method. However like I said, after we bricked 4 radios on sprint, we didn't expand the testing any further and stopped.
OK, so I bought an Xperia Z Ultra a few days ago, and I ensured it was a unlockable device, after owning all my previous Xperia phones unlocked.
The main reason I was unlocking before on my previous Z, S and T was because battery savings, meaning custom kernel undervolting, and several battery friendly moded stock kernel options. And of course, some easy rooting, mainly for changing the ugly high dpi the Z has, and have some real screen state, not big clunky icons, fonts and stuff on a 5" display.
I never been attracted to CM and or PAC for that matter either, because they break too many things to even consider them my daily drivers IMHO, and with the arrival of the Snapdragon 800 chipsets speed is never an issue, unlike before on weak handsets like S and X10 on which a custom rom did wonders for the performance.
On the Z Ultra, on the other hand, battery life is proving itself to be outstanding, way more than I expected it to be, as I was afraid the 3000mah battery wasn't gonna cut it due to screen to battery size ratio. Standard dpi is also excellent, alongside kit kat performace. Also, having a quick look on the development section, there isn't too much going on, unlike the Z, I can't seem to find a completely stock kernel that has just undervolting and some recovery options, heck, I don't recall there being a stock based kernel at all.
So, what's your main reason for unlocking this precise device?
Also, how the battery life on stock rom compares to Google Play edition?
DrKrFfXx said:
OK, so I bought an Xperia Z Ultra a few days ago, and I ensured it was a unlockable device, after owning all my previous Xperia phones unlocked.
The main reason I was unlocking before on my previous Z, S and T was because battery savings, meaning custom kernel undervolting, and several battery friendly moded stock kernel options. And of course, some easy rooting, mainly for changing the ugly high dpi the Z has, and have some real screen state, not big clunky icons, fonts and stuff on a 5" display.
I never been attracted to CM and or PAC for that matter either, because they break too many things to even consider them my daily drivers IMHO, and with the arrival of the Snapdragon 800 chipsets speed is never an issue, unlike before on weak handsets like S and X10 on which a custom rom did wonders for the performance.
On the Z Ultra, on the other hand, battery life is proving itself to be outstanding, way more than I expected it to be, as I was afraid the 3000mah battery wasn't gonna cut it due to screen to battery size ratio. Standard dpi is also excellent, alongside kit kat performace. Also, having a quick look on the development section, there isn't too much going on, unlike the Z, I can't seem to find a completely stock kernel that has just undervolting and some recovery options, heck, I don't recall there being a stock based kernel at all.
So, what's your main reason for unlocking this precise device?
Also, how the battery life on stock rom compares to Google Play edition?
Click to expand...
Click to collapse
The only need to unlock bootloader is to install the custom room set or custom kernel, but I'm like you and find the stock Sony experience ticks all the boxes I'm interested in. They've done a great job with the stock rom.
Guess the main appeal is for the gpe build.
Sent from my C6833 using XDA Premium 4 mobile app
SpyderTracks said:
The only need to unlock bootloader is to install the custom room set or custom kernel, but I'm like you and find the stock Sony experience ticks all the boxes I'm interested in. They've done a great job with the stock rom.
Guess the main appeal is for the gpe build.
Sent from my C6833 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
its funny you guys are trying to get the gee rom and I'm trying to get away from it.
So, what's your main reason for unlocking this precise device?
Click to expand...
Click to collapse
It makes rooting incredible easy. Are you on KitKat? Just flash Jackie's kernel and flash SuperSU. Done. I also like to change ROMs and environments once in awhile, so i typically flash between stock and the GPe ROM, which brings me to....
Also, how the battery life on stock rom compares to Google Play edition?
Click to expand...
Click to collapse
It's quite good actually. The GPe ROM doesn't have Stamina, so you have to be a little careful with IM services and stuff like that, but it's not bad at all.
canarycny said:
its funny you guys are trying to get the gee rom and I'm trying to get away from it.
Click to expand...
Click to collapse
That's the thing with "Nexus'" (Nexi?). Want a different ROM environment? Too bad. You're stuck with AOSP. Got the original Ultra? You got two environments to choose from. Stock Sony and AOSP, so when you get bored with one of them, you can easily swap. That's one thing that's scarying me away from the Nexus-line. And we also have the GPe version which means that the GPe will get 4.5/5.0 early, and we'll be able to just flash it (after some minor modifications).
I guess it's possible to get a Sony ROM running on the GPe version, but there aren't that many devs around here, so stuff like that will take a fair bit of time. Just hang in there though!
LordManhattan said:
It makes rooting incredible easy. Are you on KitKat? Just flash Jackie's kernel and flash SuperSU. Done. I also like to change ROMs and environments once in awhile, so i typically flash between stock and the GPe ROM, which brings me to....
It's quite good actually. The GPe ROM doesn't have Stamina, so you have to be a little careful with IM services and stuff like that, but it's not bad at all.
That's the thing with "Nexus'" (Nexi?). Want a different ROM environment? Too bad. You're stuck with AOSP. Got the original Ultra? You got two environments to choose from. Stock Sony and AOSP, so when you get bored with one of them, you can easily swap. That's one thing that's scarying me away from the Nexus-line. And we also have the GPe version which means that the GPe will get 4.5/5.0 early, and we'll be able to just flash it (after some minor modifications).
I guess it's possible to get a Sony ROM running on the GPe version, but there aren't that many devs around here, so stuff like that will take a fair bit of time. Just hang in there though!
Click to expand...
Click to collapse
i more or less want the xperia apps and i've already bricked one gee trying to root so i won't be trying again until theres a dummy guide for myself. unfortunately googles choices for media suck and i feel like the xperia integration will work a lot better for me.
canarycny said:
i more or less want the xperia apps and i've already bricked one gee trying to root so i won't be trying again until theres a dummy guide for myself. unfortunately googles choices for media suck and i feel like the xperia integration will work a lot better for me.
Click to expand...
Click to collapse
Well that's a lot easier. The Sony KitKat apps are all over the place her at XDA, so just find and install them. I did it myself when I ran the GPe ROM and it worked just fine. You may have to adjust the DPI, but that's not an issue.
Sent from my Desire HD using Tapatalk
LordManhattan said:
Well that's a lot easier. The Sony KitKat apps are all over the place her at XDA, so just find and install them. I did it myself when I ran the GPe ROM and it worked just fine. You may have to adjust the DPI, but that's not an issue.
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Fair enough I've found a few and also a few that won't install I've looked for a stock camera apk and a few others I couldn't get to install without root.
I doubt the camera will work, but Album, Movies, Walkman and all those works fine (or so they should)
Sent from my Desire HD using Tapatalk
LordManhattan said:
I doubt the camera will work, but Album, Movies, Walkman and all those works fine (or so they should)
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
Yea couldn't find a camera apk but I do have the others but did have to find an older movies apk that would actually work. My situation is that I was looking forward to trying xperia out but also wanted the 6806 model but came across a great deal for the gpe and forgot that it wouldn't have xperia on it.
Hi all,
just jumped from my Mega 6.3 to ZU, and it's been ages I've had a sony device (Arc, I think ), but the price I found it at was just too good to pass.
Now, I've been reading the various threads about downgrading FW then up again, and so on...
I have to say I am usually not afraid of that stuff, but this time I've got really no waranty, and I'm too concerned about breaking something. I already officialy upgraded to KK.
So My question : unlocking the bootloader will make me lose the DRM keys, BUT will also allow me to bipass all the downgrade stuff and jump on custom KK roms? (of course, flashing custom reco and stuff first!)
I must say i do not care for the Bravia engine and others.
Thanks to let me know
Edit : probably LordManathan answered my question :
It makes rooting incredible easy. Are you on KitKat? Just flash Jackie's kernel and flash SuperSU. Done. I also like to change ROMs and environments once in awhile, so i typically flash between stock and the GPe ROM, which brings me to....
That's fine then?
kipue said:
Hi all,
just jumped from my Mega 6.3 to ZU, and it's been ages I've had a sony device (Arc, I think ), but the price I found it at was just too good to pass.
Now, I've been reading the various threads about downgrading FW then up again, and so on...
I have to say I am usually not afraid of that stuff, but this time I've got really no waranty, and I'm too concerned about breaking something. I already officialy upgraded to KK.
So My question : unlocking the bootloader will make me lose the DRM keys, BUT will also allow me to bipass all the downgrade stuff and jump on custom KK roms? (of course, flashing custom reco and stuff first!)
I must say i do not care for the Bravia engine and others.
Thanks to let me know
Edit : probably LordManathan answered my question :
It makes rooting incredible easy. Are you on KitKat? Just flash Jackie's kernel and flash SuperSU. Done. I also like to change ROMs and environments once in awhile, so i typically flash between stock and the GPe ROM, which brings me to....
That's fine then?
Click to expand...
Click to collapse
I guess you still need to downgrade and root to backup TA partition before you unlock the bootloader and flash jackie's kernel.
manigma said:
I guess you still need to downgrade and root to backup TA partition before you unlock the bootloader and flash jackie's kernel.
Click to expand...
Click to collapse
Haha, yeah... I was hoping I wouldn't have to really care about the TA partition!
Aside from losing DRM keys, is there any other issue?
Thanks for you quick answer!
Edit:
I kept reading (yes I do read the forums a lot before and after a question, haha!) and I read that unlocking the bootloader on an official KK rom will not break x-reality ? Is that correct?
kipue said:
Haha, yeah... I was hoping I wouldn't have to really care about the TA partition!
Aside from losing DRM keys, is there any other issue?
Thanks for you quick answer!
Edit:
I kept reading (yes I do read the forums a lot before and after a question, haha!) and I read that unlocking the bootloader on an official KK rom will not break x-reality ? Is that correct?
Click to expand...
Click to collapse
There should not be any other issue. Personally I have never had good experiences with rooting and installing custom kernels/roms. Stock ROM's are always best (just disable bloatware apps, no need to delete them).
X-reality is not disabled on KK after unlocking. But you can always add xpose modules custom bravia etc after rooting.
The only reason that I might root my ZU is for 'SD card functionality' which I hope Sony re-enable in a future update.
Here sign this 'Petitioning Sony Mobile'
https://www.change.org/petitions/so...ed-to-all-our-sony-phones-via-software-update
manigma said:
There should not be any other issue. Personally I have never had good experiences with rooting and installing custom kernels/roms. Stock ROM's are always best (just disable bloatware apps, no need to delete them).
X-reality is not disabled on KK after unlocking. But you can always add xpose modules custom bravia etc after rooting.
The only reason that I might root my ZU is for 'SD card functionality' which I hope Sony re-enable in a future update.
Here sign this 'Petitioning Sony Mobile'
https://www.change.org/petitions/so...ed-to-all-our-sony-phones-via-software-update
Click to expand...
Click to collapse
Cool.
I'll also keep it stock for a week or so, to enjoy it properly, then the flashing finger will start to hitch again
Will take it from here, thanks for taking the time to answer to me
kipue said:
Cool.
I'll also keep it stock for a week or so, to enjoy it properly, then the flashing finger will start to hitch again
Will take it from here, thanks for taking the time to answer to me
Click to expand...
Click to collapse
If you aren't worried about the DRM keys the I would just unlock the BL. The DRM keys are needed for netflix and track ID and maybe some other things?
blueether said:
If you aren't worried about the DRM keys the I would just unlock the BL. The DRM keys are needed for netflix and track ID and maybe some other things?
Click to expand...
Click to collapse
My research pointed to that too, those DRM keys are actually pretty limited in scope (for me).
The biggest thing to lose is the Bravia engine, since that affects the phone in a more general way. But as I read, if unlocking the bootloader when on official Kitkat, the keys are no longer affected.
Well, I guess better safe than sorry, and I'll try to backup the TA partition anyway ^^
kipue said:
The biggest thing to lose is the Bravia engine
Click to expand...
Click to collapse
Are you sure? I would think that your warranty is the most important thing to keep intact, no? Let's say you just drop backing up the TA partition and you run into some hardware issues that can't be fixed by flashing. What do you do? Throw it into the nearest river? Pay $XXX to fix it? Or, just restore the backup?
It's pretty easy and straight forward. Downgrade to 532, root, backup TA, update to 681 (KitKat) again, and do whatever you want.
LordManhattan said:
Are you sure? I would think that your warranty is the most important thing to keep intact, no? Let's say you just drop backing up the TA partition and you run into some hardware issues that can't be fixed by flashing. What do you do? Throw it into the nearest river? Pay $XXX to fix it? Or, just restore the backup?
It's pretty easy and straight forward. Downgrade to 532, root, backup TA, update to 681 (KitKat) again, and do whatever you want.
Click to expand...
Click to collapse
Yep, you are right of course, but this device I've got has no waranty. Well, gray market waranty at any rate where I guess they don't check the bootloader state, and any breakage will have to be paid at full price.
I will do the backup, just to be sure, as I concluded in my post
Thanks for all the advice!
kipue said:
Yep, you are right of course, but this device I've got has no waranty. Well, gray market waranty at any rate where I guess they don't check the bootloader state, and any breakage will have to be paid at full price.
I will do the backup, just to be sure, as I concluded in my post
Thanks for all the advice!
Click to expand...
Click to collapse
Ahh, I see. Well, I guess you're free to do whatever you feel like then
Sent from my Desire HD using Tapatalk
Hi all. I am running 4.1.1 and have become aware my stock-rooted android version is at risk because of this latest "bug that affects SSL security. I like the "stock with goodies" rom that I have and want to keep everything the same as it is now. I read that you can flash an update file, but am concerned with the known issues this may cause. I cannot find any other custom rom that I like enough to want to switch to.
Android version: 4.1.1, Htc Sense 4+, Software version 3.16.651.3 710RD, HTC SDK API level 4.63, Baseband (Radio) 1.13.11.0830, Hboot 1.12 2222
TWRP version is 2.4.1.0
I want to stay rooted and be able to wifi tether without issues. Other roms I had issues with wifi tether among other things so Ive liked and stuck to this rom.
What would you do?
Moved to Q&A
write.artie said:
Hi all. I am running 4.1.1 and have become aware my stock-rooted android version is at risk because of this latest "bug that affects SSL security. I like the "stock with goodies" rom that I have and want to keep everything the same as it is now. I read that you can flash an update file, but am concerned with the known issues this may cause. I cannot find any other custom rom that I like enough to want to switch to.
Android version: 4.1.1, Htc Sense 4+, Software version 3.16.651.3 710RD, HTC SDK API level 4.63, Baseband (Radio) 1.13.11.0830, Hboot 1.12 2222
TWRP version is 2.4.1.0
I want to stay rooted and be able to wifi tether without issues. Other roms I had issues with wifi tether among other things so Ive liked and stuck to this rom.
What would you do?
Click to expand...
Click to collapse
Before I give my input...what update file are you referring to? Was it an update file released from HTC, or from Google? Is it the 4.3 update that's been the latest rave around here (which is awesome, for the record)? Are you comfortable using Sense 5.0 (or 5.5)?
Sorry for all of the questions. While I can easily tell you that I would update, you don't seem very interested in doing so. Therefore, I need to know what you want, and you will get my educated answer.
My goal is to not be vulnerable to this SSL bug. I have not tried sense 5.0 or 5.5. Apparently google released a file to update to 4.3.
aarsyl said:
Before I give my input...what update file are you referring to? Was it an update file released from HTC, or from Google? Is it the 4.3 update that's been the latest rave around here (which is awesome, for the record)? Are you comfortable using Sense 5.0 (or 5.5)?
Sorry for all of the questions. While I can easily tell you that I would update, you don't seem very interested in doing so. Therefore, I need to know what you want, and you will get my educated answer.
Click to expand...
Click to collapse
koolcat7 said:
My goal is to not be vulnerable to this SSL bug. I have not tried sense 5.0 or 5.5. Apparently google released a file to update to 4.3.
Click to expand...
Click to collapse
I'm in the same boat running a 4.1.1-based ROM ... MeanBean ... that I would like to keep, too, because I like it a lot. I'm not in a hurry to change because I do no financial transactions on my phone, plus I have a complicating factor in that my Sprint device has been flashed to run on Page Plus, the Verizon MVNO, and I'm concerned that making a really drastic change like to 4.3 or 4.4 will break the flash and force me to get that redone (although the person I bought the phone from tested it and flash survived a factory reset in TWRP, so I'm feeling pretty good that wiping it's not going to be an issue).
I've done a Titanium Backup of my user apps and used TWRP to create a nandroid ... I'm a noob but I'm learning ... and I've downloaded Yankees 2450's Y14 Aroma 4.1.2-based app to my SD card and I'm planning to flash it at some point, "when I get around to it," as much to get in on the ROM fun as out of any concern over HeartBleed (although I won't deny that some concern exists). Maybe that's one you should consider, the reviews in the development section seem pretty solid, and again it doesn't seem like it would be a massive change, that's why I'm going with it.
Thanks for your input. Im looking at that thread now
where 4.1.2 aroma roms are. There are quite a few versions.... not sure which would be best to try.
aarsyl said:
Before I give my input...what update file are you referring to? Was it an update file released from HTC, or from Google? Is it the 4.3 update that's been the latest rave around here (which is awesome, for the record)? Are you comfortable using Sense 5.0 (or 5.5)?
Sorry for all of the questions. While I can easily tell you that I would update, you don't seem very interested in doing so. Therefore, I need to know what you want, and you will get my educated answer.
Click to expand...
Click to collapse
prw94 said:
I'm in the same boat running a 4.1.1-based ROM ... MeanBean ... that I would like to keep, too, because I like it a lot. I'm not in a hurry to change because I do no financial transactions on my phone, plus I have a complicating factor in that my Sprint device has been flashed to run on Page Plus, the Verizon MVNO, and I'm concerned that making a really drastic change like to 4.3 or 4.4 will break the flash and force me to get that redone (although the person I bought the phone from tested it and flash survived a factory reset in TWRP, so I'm feeling pretty good that wiping it's not going to be an issue).
I've done a Titanium Backup of my user apps and used TWRP to create a nandroid ... I'm a noob but I'm learning ... and I've downloaded Yankees 2450's Y14 Aroma 4.1.2-based app to my SD card and I'm planning to flash it at some point, "when I get around to it," as much to get in on the ROM fun as out of any concern over HeartBleed (although I won't deny that some concern exists). Maybe that's one you should consider, the reviews in the development section seem pretty solid, and again it doesn't seem like it would be a massive change, that's why I'm going with it.
Click to expand...
Click to collapse
koolcat7 said:
Thanks for your input. Im looking at that thread now
where 4.1.2 aroma roms are. There are quite a few versions.... not sure which would be best to try.
Click to expand...
Click to collapse
I downloaded the Y14 build which is the latest. I think 4.1.2 has the vulnerability but the actual HeartBleed bug hasn't been engaged as in 4.1.1.
Ah, i just downloaded the Y14 as well, but if theres still vulnerability there im not sure id feel okay with that.
prw94 said:
I downloaded the Y14 build which is the latest. I think 4.1.2 has the vulnerability but the actual HeartBleed bug hasn't been engaged as in 4.1.1.
Click to expand...
Click to collapse
koolcat7 said:
Ah, i just downloaded the Y14 as well, but if theres still vulnerability there im not sure id feel okay with that.
Click to expand...
Click to collapse
Well the Hisense Sero 7 tablet I'm using to post (running 4.2.1) "has the vulnerability," but it's safe because HeartBleed isn't enabled. It's only enabled on 4.1.1 from everything I've heard.
Im going to give it a go now, and flash Y14.
prw94 said:
Well the Hisense Sero 7 tablet I'm using to post (running 4.2.1) "has the vulnerability," but it's safe because HeartBleed isn't enabled. It's only enabled on 4.1.1 from everything I've heard.
Click to expand...
Click to collapse
koolcat7 said:
Im going to give it a go now, and flash Y14.
Click to expand...
Click to collapse
Let me know how it works for you, I need to go ahead and flash mine, as noted I'm concerned about HeartBleed but not over panicking based in my usage.
So do you think this version 4.1.2 will ever have that ssl bug enabled? Im flashed and already having issues, only 1x signal and profile wont update =/
Activate this device does nothing as well. Even in WiFi settings, ALL networks show full bars, when i know many are very far away. Looks like im going back to my nandroid backup and decide what to do when i find more info. ALSO, 4G LTE did connect, but kept going away every 10 seconds or so, back to 1x which is not normal.
prw94 said:
Let me know how it works for you, I need to go ahead and flash mine, as noted I'm concerned about HeartBleed but not over panicking based in my usage.
Click to expand...
Click to collapse
koolcat7 said:
So do you think this version 4.1.2 will ever have that ssl bug enabled? Im flashed and already having issues, only 1x signal and profile wont update =/
Activate this device does nothing as well. Even in WiFi settings, ALL networks show full bars, when i know many are very far away. Looks like im going back to my nandroid backup and decide what to do when i find more info. ALSO, 4G LTE did connect, but kept going away every 10 seconds or so, back to 1x which is not normal.
Click to expand...
Click to collapse
No, HeartBleed will not be enabled in anything save 4.1.1. You need to read up about the origin of this thing and the mechanism by how it is or isn't a threat.
Your only option is to go to a custom ROM that is not 4.1.1 based, or wait on HTC to issue the update for the stock ROM that they've promised, but have given no ETA for (and I wouldn't hold my breath).
I don't know if you have enough posts here to post on the development board ... that's another reason I've held off doing anything, although I'm getting close thanks to this thread ... but the developer of that ROM is very responsive to people with issues, and as I said the thing is very popular and seems pretty bulletproof from the response.
I promise I'm not his PR person, have never spoken to him, just found that ROM when I was looking for something that would be the least drastic change from what I'm running now, because of being flashed to Page Plus (which only gives me 3G, but I knew that going in). 4.3, you have to do more than just wipe and flash because of the partitions changes.
When I think about it, I don't see how changing the partitions on the phone will affect the functionality of the phone while using Page Plus. Maybe I'm looking at it incorrectly, but I don't reactivate my phone with Sprint every time that I flash a new rom, root it, change partitions, or anything at all. I could be wrong, though, for I have never flashed my phone to any other service.
aarsyl said:
When I think about it, I don't see how changing the partitions on the phone will affect the functionality of the phone while using Page Plus. Maybe I'm looking at it incorrectly, but I don't reactivate my phone with Sprint every time that I flash a new rom, root it, change partitions, or anything at all. I could be wrong, though, for I have never flashed my phone to any other service.
Click to expand...
Click to collapse
I really don't know, thus my hesitance in my own situation. Had a "recommend a ROM thread locked because I was unaware that wasn't kosher, so I went back to the boards (which can be a daunting experience for a noob) and found that particular ROM and I've also downloaded CM10 stable.
Am basically just acclimating myself to this stuff (phone was rooted, running MeanBean and flashed to PP when I bought it, have never done any of this), learning how to use Titanium and TWRP to make backups, etc.
I''d be lying if I said HeartBleed wasn't a concern to me, but I'm not as panicked as the OP about it. I know I need to probably change, although I'm quite happy as is with MeanBean. Biggest priority aside from security is not having to spend $50 or so to get the phone reflashed to PP.
4.1.1 has three digits the ones that matter are the first two. 4.1.2 may still be vulnerable to heart bleed. As for flashing to page plus you can do that on your own for free there are guides for how to do this all over. The best bet for every one running below 4.3 is to update to a Rom that is 4.3+ also with that update comes many fixes for the most common phone issue one might have while running below 4.3. There are 3 fully functioning roms currently available for the evo running on the updated partitions. Sense 5.5 by chubbz and I captain's stock Rom. And vins viper 4.0 with sense 5.5. Now with all this knowledge I've given you go explore, test the waters jump in. And always remember to post a question Rom related after at least 1 hour of thread searching Google and running the basics of Rom flashing. Wipe caches, dalvik if all else factory reset.
Sent from my EVO using Tapatalk
Thanks for the advice. I have searched threads, as noted I have been practicing to test the waters ... I have a Titanium Backup of my apps and a Nandroid of current system with MeanBean on my SD card so I'm comfortable with that. I think I'm pretty clear on wiping the phone ... although I thought the factory reset took care of everything, do you still need to wipe caches/dalvik after that? Searching the threads is where I picked up on the 4.1.2 ROM which seems to be pretty bulletproof stable, and as far as I know HeartBleed isn't enabled in 4.1.2. I was basically looking at that as an intermediate step, again just to dip my foot in the pool of ROM flashing before attempting anything more elaborate. The instructions for going to 4.3 are a bit more complicated than wipe, flash, reboot, and I'd prefer to learn to swim a little better before jumping off the high board. Same with the Page Plus flashing. I'm sure I could eventually figure out how to do it myself, problem is I use my phone pretty much perpetually for work and can't afford to have it out of service for a millisecond, so it's worth the cost to me to get it done right first time, although I'd rather not break the flash in the first place. I've gotten some advice from folks who do such flashing that 4.3 will break it, every time.
Sinistertensai said:
4.1.1 has three digits the ones that matter are the first two. 4.1.2 may still be vulnerable to heart bleed. As for flashing to page plus you can do that on your own for free there are guides for how to do this all over. The best bet for every one running below 4.3 is to update to a Rom that is 4.3+ also with that update comes many fixes for the most common phone issue one might have while running below 4.3. There are 3 fully functioning roms currently available for the evo running on the updated partitions. Sense 5.5 by chubbz and I captain's stock Rom. And vins viper 4.0 with sense 5.5. Now with all this knowledge I've given you go explore, test the waters jump in. And always remember to post a question Rom related after at least 1 hour of thread searching Google and running the basics of Rom flashing. Wipe caches, dalvik if all else factory reset.
Sent from my EVO using Tapatalk
Click to expand...
Click to collapse
So, I talked to a friend of mine who knows alot about alot... and he assured me that you will only be susceptible to heartbleed attacks on open or public wifi spots. So this bug does not affect anything over 3G/4G, which puts most of my concerns at risk. So don't be too worried if you don't constantly connect to open wifi networks you cannot completely trust. In conclusion, im not too concerned anymore and am going to leave the android version alone.
prw94 said:
Thanks for the advice. I have searched threads, as noted I have been practicing to test the waters ... I have a Titanium Backup of my apps and a Nandroid of current system with MeanBean on my SD card so I'm comfortable with that. I think I'm pretty clear on wiping the phone ... although I thought the factory reset took care of everything, do you still need to wipe caches/dalvik after that? Searching the threads is where I picked up on the 4.1.2 ROM which seems to be pretty bulletproof stable, and as far as I know HeartBleed isn't enabled in 4.1.2. I was basically looking at that as an intermediate step, again just to dip my foot in the pool of ROM flashing before attempting anything more elaborate. The instructions for going to 4.3 are a bit more complicated than wipe, flash, reboot, and I'd prefer to learn to swim a little better before jumping off the high board. Same with the Page Plus flashing. I'm sure I could eventually figure out how to do it myself, problem is I use my phone pretty much perpetually for work and can't afford to have it out of service for a millisecond, so it's worth the cost to me to get it done right first time, although I'd rather not break the flash in the first place. I've gotten some advice from folks who do such flashing that 4.3 will break it, every time.
Click to expand...
Click to collapse
koolcat7 said:
So, I talked to a friend of mine who knows alot about alot... and he assured me that you will only be susceptible to heartbleed attacks on open or public wifi spots. So this bug does not affect anything over 3G/4G, which puts most of my concerns at risk. So don't be too worried if you don't constantly connect to open wifi networks you cannot completely trust. In conclusion, im not too concerned anymore and am going to leave the android version alone.
Click to expand...
Click to collapse
OK good luck, still going to update mine as soon as I make the final call on which one to try. Decisions, decisions ...