Hi all
I am looking to install CM7 on my phone and have been doing a fair bit of reading before taking the plunge.
I am relatively happy on the steps involved now, the order to do them in and (roughly) how to do them. The only bit which I am a little sketchy on is the RAM issue from unlocking the bootloader.
I am on an Orange UK handset and understand that a side effect of the unlock is ending up with ~300Mb RAM. The details in the fix here don't seem to quite make sense to me.
I guess what I am really asking is, after unlocking the bootloader and installing CM7 will my phone still only register ~300Mb or is that fix just for stock Gingerbread ROMs? The guide refers to Orange FR Gingerbread which I obviously do not want (I am currently running stock 2.2.2 Orange UK firmware).
I apologise as I am sure this has come up before but I want to do this correctly.
Many thanks for any guidance.
surrealjam said:
Hi all
I am looking to install CM7 on my phone and have been doing a fair bit of reading before taking the plunge.
I am relatively happy on the steps involved now, the order to do them in and (roughly) how to do them. The only bit which I am a little sketchy on is the RAM issue from unlocking the bootloader.
I am on an Orange UK handset and understand that a side effect of the unlock is ending up with ~300Mb RAM. The details in the fix here don't seem to quite make sense to me.
I guess what I am really asking is, after unlocking the bootloader and installing CM7 will my phone still only register ~300Mb or is that fix just for stock Gingerbread ROMs? The guide refers to Orange FR Gingerbread which I obviously do not want (I am currently running stock 2.2.2 Orange UK firmware).
I apologise as I am sure this has come up before but I want to do this correctly.
Many thanks for any guidance.
Click to expand...
Click to collapse
I rooted my phone and I never installed the ram fix. I was always sitting on350-400 of ram with like 60 other so apps on there. I installed cm7 and now get 550-600 with the same apps and settings. My phone boots up in 7 seconds top from when you see the bootlogo to the lockscreen. Its so fast
Heres my quad scores oced @1.3
Sent from my MB860 using xda premium
Keep in mind the OP is asking about international Orange versions of the Atrix not USA AT&T, I don't think USA AT&T versions are experiencing this odd RAM problem.
Phalanx7621 said:
Keep in mind the OP is asking about international Orange versions of the Atrix not USA AT&T, I don't think USA AT&T versions are experiencing this odd RAM problem.
Click to expand...
Click to collapse
Ahh good call, I had crap for ram on blur roms lol
Sent from my MB860 using xda premium
Incase anyone else is interested to know, I took the plunge and just went ahead and did it this evening:
1) Unlock bootloader
2) Root phone
3) Installed CM7
After point 1, I only had the ~300Mb available. After point 3, I have the full ~800Mb available...
So, the answer is the RAM restriction is only on Moto ROMs. I presume the obvious answer is this is linked to the kernel so CM7 works just fine.
surrealjam said:
Incase anyone else is interested to know, I took the plunge and just went ahead and did it this evening:
1) Unlock bootloader
2) Root phone
3) Installed CM7
After point 1, I only had the ~300Mb available. After point 3, I have the full ~800Mb available...
So, the answer is the RAM restriction is only on Moto ROMs. I presume the obvious answer is this is linked to the kernel so CM7 works just fine.
Click to expand...
Click to collapse
See. Same thing happened to me lol
Sent from my MB860 using xda premium
Smittyzz said:
See. Same thing happened to me lol
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Cm7 has the ram fix built into the ROM I believe
Sent from my MB860 using xda premium
Alcapone263 said:
Cm7 has the ram fix built into the ROM I believe
Sent from my MB860 using xda premium
Click to expand...
Click to collapse
Apparently de-blur ROMs all seem to do that, i'm an international user and flashed Home Base and also the ROM problem is gone and the phone is just saaaaaaaaaa fast!
Only one qualm though, it gets a tad too hot for my liking, next step is to learn more about undervolting to see if i can somehow control the overheating...
crofton said:
Apparently de-blur ROMs all seem to do that, i'm an international user and flashed Home Base and also the ROM problem is gone and the phone is just saaaaaaaaaa fast!
Only one qualm though, it gets a tad too hot for my liking, next step is to learn more about undervolting to see if i can somehow control the overheating...
Click to expand...
Click to collapse
It uses a 1.3 GHz kernel so you should set up profiles to underclock when you don't need all that power
Sent from my MB860 using xda premium
finally found a thread which got some info after searching for a month.i dont own an atrix planning to buy one.i also dont undestand this issue of ram.is it for those who use stock rom.because the fix is using an orangefr.
do other roms contain the fix like cm7.
im planning to use a stock middle east rom
or a custom rom which supports arabic.
its the kernel contained within the CM7 rom, it contains the unified kernel with the ram fix for at&t and international users...
surrealjam said:
Hi all
I am looking to install CM7 on my phone and have been doing a fair bit of reading before taking the plunge.
I am relatively happy on the steps involved now, the order to do them in and (roughly) how to do them. The only bit which I am a little sketchy on is the RAM issue from unlocking the bootloader.
I am on an Orange UK handset and understand that a side effect of the unlock is ending up with ~300Mb RAM. The details in the fix here don't seem to quite make sense to me.
I guess what I am really asking is, after unlocking the bootloader and installing CM7 will my phone still only register ~300Mb or is that fix just for stock Gingerbread ROMs? The guide refers to Orange FR Gingerbread which I obviously do not want (I am currently running stock 2.2.2 Orange UK firmware).
I apologise as I am sure this has come up before but I want to do this correctly.
Many thanks for any guidance.
Click to expand...
Click to collapse
ive had a similar problem after unlocking the bootloader on my tmob uk atrix while still on stock rom. i had ~500 free average before unlocking the bootloaader. after doing the unlock i now have ~100meg free at any time. i tried aliens#4 rom and still encountered this problem
UPDATE
i flashed faux's unified kernal. solved it
ram fix
i got bellgb2.3.6 im d00, everything works great including lapdock
now i have 300mb ram,
did you got any solution?
If I recall correctly, Faux v0.2.3 kernel has the fix built into it.
Sent from my MB860 using XDA App
Not trying to get off topic here but would it be possible with a hack to get all the ram to show up. For example, I want all the ram (1GB) to show up instead of 815MB Available. I understand that the android system allocates ~250MB for the OS but I heard that you can make it so all the ram shows up.
quick question, im running Nottach's wet dream rom with faux's 123 unified 1.3GHz kernal. Im not having any problems with the ram, i get an avg of 500mb. i did have a problem before with was solved with one of faux's kernels. what will happen if i flash the ramfix? nothing or will i get more available?
parkodrive said:
quick question, im running Nottach's wet dream rom with faux's 123 unified 1.3GHz kernal. Im not having any problems with the ram, i get an avg of 500mb. i did have a problem before with was solved with one of faux's kernels. what will happen if i flash the ramfix? nothing or will i get more available?
Click to expand...
Click to collapse
I flashed this ramfix over my wetdream 1.4.4 with the faux gb1.45Ghz kernel and nthing happened i get the same mount of ram i guess it was already built into the kernel
sk8trix said:
I flashed this ramfix over my wetdream 1.4.4 with the faux gb1.45Ghz kernel and nthing happened i get the same mount of ram i guess it was already built into the kernel
Click to expand...
Click to collapse
Thought it might be. I flashed the enhanced stock kernel when i was having ram issues on the Alien rom
Related
I'm about to be coming over to the LG Optimus T world here in the next few days. I'm coming from a T-Mobile myTouch 3G 1.2 (the one with the headphone jack). I've been messing with rooting for about 8 months now and have put up two guides in the myTouch section of these forums as well as provide daily help. I've already got rooting and installing a custom recovery on this phone down by reading through the forum and will surely get flash happy with the ROM's over the next few weeks. My question is this: is there anything else I need to know? Such as, are there different radio/bootloader versions for these devices? The myTouch has around 12 different bootloader/radio combinations. Is this the only recovery available? I may have to see if I can get a guy from the myTouch forums to theme it out a little. Either rate. If there's nothing else that I need to know to do, is there anything that should never be done with this phone?
I think Clockwork works, but I haven't tried it yet. I'm afraid of bricking my phone, so I just stick to the recovery you linked to.
Miscellaneous stuff:
- "axis inversion" issues with the touchscreen
- touch screen cpu spike, but already fixed by mik_os (from 100% cpu usage to somewhere less than 30%)
- random sdcard unmounts: haven't had this issue in a long time. this used to be very much talked about a few weeks back.
- there's already a working gingerbread rom (cm7 port) but the gps and camera doesn't work yet. also, ui is a bit slow.
I'll update this when I realize I have forgotten something
is there anything that should never be done with this phone?
Click to expand...
Click to collapse
The only thing I know of is drellisdee's warning of not flashing a radio.img from the recovery
I don't care much for ClockWorkMod so I'll just stick to the one linked. That one is built off of Among Ra's source code ands I'm currently running a themed version of it right now. The SD card issue is going to be annoying but hopefully I won't run into it much.
Sent from my T-Mobile myTouch 3G using Tapatalk
DonJuan692006 said:
I don't care much for ClockWorkMod so I'll just stick to the one linked. That one is built off of Among Ra's source code ands I'm currently running a themed version of it right now. The SD card issue is going to be annoying but hopefully I won't run into it much.
Sent from my T-Mobile myTouch 3G using Tapatalk
Click to expand...
Click to collapse
ClockworkROm has been ported to P500 i have installed it but haven't created any backups or flashed some ROMS
I've been looking around the web for a while and can't find an answer.
Does the locked-bootloader on the RAZR make it impossible to install a custom ROM on the phone?
I really want to get this phone but only if there is a chance I'll be able to put a custom ROM on it.
neurostu said:
I've been looking around the web for a while and can't find an answer.
Does the locked-bootloader on the RAZR make it impossible to install a custom ROM on the phone?
I really want to get this phone but only if there is a chance I'll be able to put a custom ROM on it.
Click to expand...
Click to collapse
Here is a quote from a user on Rootzwiki about the locked bootloader (user Soapinmouth posted this, not me)
I disagree i think the razr is going to be the hottest selling Droid since the og. You have to remember the people that even know what a bootloader is are an extremely small % of buyers, and then there's those that do and still buy it like me.
In all honesty the locked bl is way overblown, id say a good 75% of the community has no idea what the locked bl even prevents.
It
DOES NOT prevent custom roms
DOES NOT prevent overclocking
DOES NOT prevent rooting
It
Does prevent custom kernals
Well that's a relief, so a chance MIUI would be on this bad boy?
ImAustinJacobM said:
Well that's a relief, so a chance MIUI would be on this bad boy?
Click to expand...
Click to collapse
Miui and cm7 would need custom kernels, so no.
Sent from my skinny mopho o/c and all.
bricky23 said:
Miui and cm7 would need custom kernels, so no.
Sent from my skinny mopho o/c and all.
Click to expand...
Click to collapse
Although they did find a way to unlock the bootloader of the bionic so there is a chance they could find a way to unlock the RAZR too.....one can always hope!
Sent from my GT-P7510 using xda premium
bricky23 said:
Miui and cm7 would need custom kernels, so no.
Sent from my skinny mopho o/c and all.
Click to expand...
Click to collapse
The Droid x has both w/o custom kernels thru the magic of 2nd init.
Sent from my DROID RAZR using xda premium
I cannot WAIT for overclock. Push this thing to 1.8GHz+ and I'll keep it the full two years. With proper memory management (custom user values and/or 4.0) this phone is as future proof as you're gonna find in the next 6-12 months. Who wants Samsung plastics and no Gorilla Glass?
Isn't overclocking going to be out of the question without a custom kernel?
sovrce said:
I cannot WAIT for overclock. Push this thing to 1.8GHz+ and I'll keep it the full two years. With proper memory management (custom user values and/or 4.0) this phone is as future proof as you're gonna find in the next 6-12 months. Who wants Samsung plastics and no Gorilla Glass?
Click to expand...
Click to collapse
Lol why would you want to OC that high? Only benefit you'd get are higher bench scores and maybe a few more fps in some games. Also imagine the heat as this phone alreayd runs fairly hot. I doubt there is anything in Android that requires even more than a 1ghz DC. Pretty much all the performance issues we see now are due to poor coding. Also the software doesn't atm doesn't have proper hardware acceleration I believe? iPhone 5 with a 800mhz DC, hell even a single core has a smoother UI than most Android phones. Not an apple fan or anything, just stating what I have seen and facts. Good example is the HTC Rezound is 300 mhz "faster" than the RAZR and the RAZR performs quite better. Hardware is nice yes, but it's nothing without the proper software optimizations. If we do get to overlock I'd probably just pump it to 1.4 - 1.5 , since I think atm that's the point before you get diminishing returns.
Edit: Speaking of temps battery/cpu are at like 103-104 while watching Netflix with full screen brightness. I wonder how high the clock speeds can go without bumping voltage.
bricky23 said:
Miui and cm7 would need custom kernels, so no.
Sent from my skinny mopho o/c and all.
Click to expand...
Click to collapse
disagree.. i had MIUI (official) and CM7 (unofficial port) on my Milestone 1 which had locked bootloader as well. and RAZR will get unlocked eventually, Motorola said that.
a.mcdear said:
Isn't overclocking going to be out of the question without a custom kernel?
Click to expand...
Click to collapse
Dx got over clocked too.
Sent from my DROID RAZR using xda premium
It will get something no doubt. CM7 doesn't natively support webtop on atrix 4G so that would also apply for the razr...
Astrowe said:
....and RAZR will get unlocked eventually, Motorola said that.
Click to expand...
Click to collapse
Are you sure the bootloader can be unlock ?
EVEALEX62 said:
Are you sure the bootloader can be unlock ?
Click to expand...
Click to collapse
Well, Moto has explicitly said it will be unlockable so unless they were purposefully lying, I would say yes.
I read here (sorry it's in french forum) the bootloader is lock .... Because I must do a choice betwen GN and RAZR and I like more the Razr but if it s lock I chose the GN ....
When do you think we can say really if the bootlader is really lock or not ?
The BL is locked. However, it'll be unlocked with ICS update, coming in late december this year or january 2012.
The locked BL will make you unable to flash proper custom ROMs, only "hacked" ones and it isn't possible to make a decent and really performancewise custom ROM at the moment with a locked BL.
It will prevent you to install custom kernels, too.
Anyway, don't worry, from the statement Motorola made, if they won't unlock it with ICS (they will as they've done the same thing on ATRIX w/GB) they'll be suable as they've made a public statment confirming a thing that has made us to buy a 560 euros device.
Thanks for that, I hope because I prefer this phone ....
EVEALEX62 said:
Are you sure the bootloader can be unlock ?
Click to expand...
Click to collapse
positive, i'm absolutely sure it will get unlocked. Motorola already said that several times now..
So a locked bootloader will not prevent one from installing a custom ROM but only a custom kernel?
What's the difference between a ROM and kernel?
The XT720 is locked and had miui, overclocking and about a dozen roms.
Besides, I thought safestrap basically solves this problem for us?
hi, playing with my phone is not really a hobby for me.. i just want something free of stock bloatware, has a working GPS, and hopefully, no Carrier IQ. So I hope you can forgive me if i'm asking a basic question that is answered somewhere in the Vibrant bible or elsewhere.
i recently flashed to CM7 because of the Carrier IQ thing.. knowing that some people were having GPS issues. If the GPS were my only problem, i could probably live with CM7, but my phone is also suffering from ' Screen of Death ' unfortunately.
I do actually really like CM7.. it is very fast.. but between the no GPS and the SOD's i'm experiencing, i need to get off of it.
so, i believe i want to go back to a Froyo ROM. From there i guess i'll try the Carrier IQ removal tool.
my question is, can i safely flash to Axura or Bionix using CWM, directly from CM7 ...or must i 'odin' back to stock first ?
thank you
Odin first
thank you very much for the reply.
so i was reading through this
http://forum.xda-developers.com/showthread.php?t=849028
is this where i want to begin ? Odin back to Stock ?
strange, I'm on cm7, overclocked currently to 1500 with glitch kernel and have no GPS issues or anything. I've used axura and bionix they are cool... But I came to cm7 to use my ps3 controller with my psx roms...unfortunately no TV-out on cm7 :-(, that would make it complete.
Joker904 said:
strange, I'm on cm7, overclocked currently to 1500 with glitch kernel and have no GPS issues or anything. I've used axura and bionix they are cool... But I came to cm7 to use my ps3 controller with my psx roms...unfortunately no TV-out on cm7 :-(, that would make it complete.
Click to expand...
Click to collapse
i haven't tried a different kernal. is that just a download and install via CWM ?
popthree said:
thank you very much for the reply.
so i was reading through this
http://forum.xda-developers.com/showthread.php?t=849028
is this where i want to begin ? Odin back to Stock ?
Click to expand...
Click to collapse
this is as straight forward as it gets
http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
awesome, looks easy enough. thanks for the assistance. much appreciated.
popthree said:
awesome, looks easy enough. thanks for the assistance. much appreciated.
Click to expand...
Click to collapse
Just a little addition. From what I understand Carrier IQ is something that the carrier has to request. To my knowledge T-Mobile did not have Samsung build it into the Vibrant's Android builds. So no Vibrant rom "should" have CIQ. I've tried the majority of our roms and have never seen it. So I wouldn't worry too much about it; on the Vibrant at least.
The glitch kernel can be acquired through a $5 app on the market named (glitch)...note if you clock it to 1700 mhz....your phone will probably go into an infinite reboot loop.....um...merrr just got the news of cm bailing on us....oh well
Sent from my SGH-T959 using XDA App
jneal9 said:
Just a little addition. From what I understand Carrier IQ is something that the carrier has to request. To my knowledge T-Mobile did not have Samsung build it into the Vibrant's Android builds. So no Vibrant rom "should" have CIQ. I've tried the majority of our roms and have never seen it. So I wouldn't worry too much about it; on the Vibrant at least.
Click to expand...
Click to collapse
interesting.. i downloaded the app that detects carrierIQ and i thought i interpreted the results correctly.. i believed my vibrant running Axura had it. perhaps i misunderstood the results of the test.
Running 6.1 build of ics, no issues at all with stock kernel but was wondering what you guys think of the glitch kernel paired with this rom? Should I make the plunge even though stock is working flawlessly or should I keep stock? I usually don't post questions and figure stuff out for myself but I want the community's opinion on it before I make up my mind. I know its ultimately my decision but any input positive or negative would be appreciated, if you are going to reply please post reasons and not just a yes or no response,
Thanks.
Sent from my SCH-I500 using XDA App
I like glitch alot, but for now i would stick with stock...jmo
Well if it's working great, then don't try to fix something that isnt broken lol it would probably create more problems
Sent from my SCH-I500 using XDA App
I'm running glitch b3 and...I definitely recommend it if you're into tweaking. Live OC makes a pretty big difference in performance to me.
I'd agree with sendan. You're not losing any functionality with glitch, only gaining features and performance.
Also, it's just a kernel, there's no harm in trying it out. If you don't like it, restore a backup or reflash the rom. It's not like you have anything to lose.
I like glitch too. A live oc around 114-116% and 13xx as max clock makes this phone run like a dream.
Sent from my SCH-I500 using xda premium
bobloblaw1 said:
I like glitch too. A live oc around 114-116% and 13xx as max clock makes this phone run like a dream.
Sent from my SCH-I500 using xda premium
Click to expand...
Click to collapse
Installed glitch, ran your settings and threw phone into a constant reboot. Had to flash build 1 and then 6.1 to get it back up and running. My phone doesn't play nice with glitch I guess :-/ lol
Sent from my SCH-I500 using XDA App
mkuehl06 said:
Installed glitch, ran your settings and threw phone into a constant reboot. Had to flash build 1 and then 6.1 to get it back up and running. My phone doesn't play nice with glitch I guess :-/ lol
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Same problem for me too.
It's very touchy, nobody will disagree with that.
and thats why I posted what I did...glitch 13.1 runs great on mtd gb roms, but glitch 14b3 for ICS seems hit or miss on some devices. Im sure it will get better as development continues, until then sotck is probably the best bet for most.
droidstyle said:
and thats why I posted what I did...glitch 13.1 runs great on mtd gb roms, but glitch 14b3 for ICS seems hit or miss on some devices. Im sure it will get better as development continues, until then sotck is probably the best bet for most.
Click to expand...
Click to collapse
Yeah I understand man. The glitch runs fine on my phone if I don't tweak the CPU at all. Tweak it at all and the phone freaks out like a mf on crack or something lol.
Sent from my SCH-I500 using XDA App
Sorry about that. My phone was running fine at 115% for about 24 and then it also threw a reboot fit like yours had.
I;m not really sure what caused it but I guess it's still a bit temperamental at this point.
bobloblaw1 said:
Sorry about that. My phone was running fine at 115% for about 24 and then it also threw a reboot fit like yours had.
I;m not really sure what caused it but I guess it's still a bit temperamental at this point.
Click to expand...
Click to collapse
Yeah I think 1200mhz is about the most my phone will handle, and that's with 100%oc so maybe if I tweak it to 115 or something I'd have to drop it down a notch. I just don't feel like dealing with a reboot fit right now
Sent from my SCH-I500 using XDA App
I have mine at 107%...tbh it gets ridiculously hot with anything much higher.
mkuehl06 said:
Installed glitch, ran your settings and threw phone into a constant reboot. Had to flash build 1 and then 6.1 to get it back up and running. My phone doesn't play nice with glitch I guess :-/ lol
Click to expand...
Click to collapse
You could've just gone into recovery and erased your OC/voltage settings. Assuming you're using the glitch recovery, that is.
droidstyle said:
and thats why I posted what I did...glitch 13.1 runs great on mtd gb roms, but glitch 14b3 for ICS seems hit or miss on some devices. Im sure it will get better as development continues, until then sotck is probably the best bet for most.
Click to expand...
Click to collapse
Every phone responds differently to OC, *especially* it seems, with the new LiveOC system in v14. I haven't seen any issues reported by people using v14 with completely stock settings, so I wouldn't call the kernel itself unstable, just the utilization of some of the features it includes. I also suspect that a lot of the people that report issues with glitch haven't read and/or taken the time to understand the LiveOC guide that is linked to in the glitch OP.
k_nivesout said:
You could've just gone into recovery and erased your OC/voltage settings. Assuming you're using the glitch recovery, that is.
Every phone responds differently to OC, *especially* it seems, with the new LiveOC system in v14. I haven't seen any issues reported by people using v14 with completely stock settings, so I wouldn't call the kernel itself unstable, just the utilization of some of the features it includes. I also suspect that a lot of the people that report issues with glitch haven't read and/or taken the time to understand the LiveOC guide that is linked to in the glitch OP.
Click to expand...
Click to collapse
i agree...guess that i should of been more clear and said that most folks do not know how to properly setup v14 with nstools and can easily cause damage to the device...which is part of the reason i mention to stick with stock(if your not sure wth your doing lol). im currently running ths 6.1 with glitch 14 oc'd @ 1200mhz and undervolted -50 across the board, fiop/lagfree govenor and everything is working great.
droidstyle said:
i agree...guess that i should of been more clear and said that most folks do not know how to properly setup v14 with nstools and can easily cause damage to the device...which is part of the reason i mention to stick with stock(if your not sure wth your doing lol). im currently running ths 6.1 with glitch 14 oc'd @ 1200mhz and undervolted -50 across the board, fiop/lagfree govenor and everything is working great.
Click to expand...
Click to collapse
Well as of almost 12 hours ago or so, I'm running 105%liveOc 12xx setting, lag free and fiop, and seems to be no issues. I had to send my backup fas in for the ota brick that happened with a lot of peoples eh03 ota. Hopefully they send me a replacement cause we arent due for upgrading till October.
So until it comes back I'm a little hesitant to play with uv. I know the basics, but still don't wanna play the boot loop game
Sent from my SCH-I500 using XDA App
droidstyle said:
i agree...guess that i should of been more clear and said that most folks do not know how to properly setup v14 with nstools and can easily cause damage to the device...which is part of the reason i mention to stick with stock(if your not sure wth your doing lol). im currently running ths 6.1 with glitch 14 oc'd @ 1200mhz and undervolted -50 across the board, fiop/lagfree govenor and everything is working great.
Click to expand...
Click to collapse
Definitely agree that for most users the stock kernel is probably best, and it isn't really lacking any features the average user will miss. Except I thought I saw something about 6.1 not including voodoo sound? Not sure about others, but that's a must for me. Anyway, I'm personally running 110% liveOC with 1320mhz max with no undervolting and the phone feels really responsive a good part of the time. It's been good so far but I need to stress test it.
mkuehl06 said:
Well as of almost 12 hours ago or so, I'm running 105%liveOc 12xx setting, lag free and fiop, and seems to be no issues. I had to send my backup fas in for the ota brick that happened with a lot of peoples eh03 ota. Hopefully they send me a replacement cause we arent due for upgrading till October.
So until it comes back I'm a little hesitant to play with uv. I know the basics, but still don't wanna play the boot loop game
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I can definitely see being hesitant with the undervolting, and especially with being able to adust ARM and INT voltages. As I understand it, you could certainly end up with a brick if things are pushed too far.
I wanted to hear everyone's take on this. With all of the recent changes in AOKP and the incorporation of the Glitch kernel, is it still important to be on the GB bootloaders to use all of the Glitch features? I remember reading a little over a month ago about the various bugs, SODs, etc. that were being blamed on the absence of GB bootloaders. I know droidstyle runs fine without them, but do they do anything other than give the Glitch splash screen?
The official AOKP builds still have the stock Cyanogenmod kernel, so there's no point in using the Gingerbread bootloader unless you want to. Of course it'd be a good idea to flash it if you're using the Glitch kernel, but it's not a big deal to flash via Odin.
Sent from my SCH-I500 using Tapatalk 2
nm
I flashed the gb bootloaders after odining back to stock a couple weeks back....i dont notice anything different other than the glitch splash screen instead of samsung logo.
jawman27 said:
I wanted to hear everyone's take on this. With all of the recent changes in AOKP and the incorporation of the Glitch kernel, is it still important to be on the GB bootloaders to use all of the Glitch features? I remember reading a little over a month ago about the various bugs, SODs, etc. that were being blamed on the absence of GB bootloaders. I know droidstyle runs fine without them, but do they do anything other than give the Glitch splash screen?
Click to expand...
Click to collapse
I didn't notice any difference either but figured with all the experts recommending GB bootloader, what harm? Nothing negative to report. Just the Glitch animation on boot...
Since it's what the kernel is tested on afaik it also eliminates one thing to troubleshoot.
Sent from my SCH-I500 using xda premium
I always flash it because that is what they call for. That way if I have any problems, I know that I followed the instructions first. Sometimes I wonder if some of the issues people are complaining about are related to this. Probably not, but when most of the people detail their problems and how they did there Odin install, I don't think I recall any of them flashing the gingerbread bootloaders in their install.
I must also note that i have not had any problems ever with aokp.
Sent from my SCH-I500 using Tapatalk