Hello,
This is my firs thread/post in the forum, I have been following this site since I got my Motorola Atrix, and I thanks in advance to all devs who makes possible for us to toy with our phones.
I created this post just to show and tell you guys how Ice Cream Sandwich/Android 4.0 behaves on this phone. I think the Motorola Atrix is a well known phone that has been a little underrated by Motorola.
First, the pics: (since it's my first post, the forum rules won't let me post them directly here)
About phone
i50.tinypic.com/2myalvb.png
The "Desktop" customized a little
i49.tinypic.com/j64o0k.png
The battery drain
i50.tinypic.com/2ihnkeu.png
Picture gallery
i46.tinypic.com/8wbg4l.png
The experience:
Before ICS/Android 4.0 I used CyanogenMod 7/Android 2.3, just for reference. ICS on an Atrix right now, it's almost usable. The problem is the memory, because it takes a long time to open an app the first time, but once it's on memory, it runs perfectly. I'm talking about apps like YouTube, Gmail, Google Plus, Weather EX, etc; I don't think it would be possible to watch a movie in MKV format with say, MX Player, and in case it would be possible, it could take several minutes to load. I think it's not only lack of memory of the Atrix, but the memory management and swapping it's probably not optimized at all.
In resume, I'll leave ICS in my phone one or two days more just to toy with it, it seems to be very stable, although everything will take a lot of time the first time it runs, I didn't experienced any hangups, freezes, or loss of data.
I think it's very slow because
1- the limitation of hardware of the phone, specially the memory, the CPU and Tegra GPU seems to be good enough to run everything fast enough)
2- the build (you need to install a new Linux btw, which has a newer kernel) is not optimized for the phone.
If these points would be fixed, I think the Atrix could easily run ICS.
Hope this helps other Motorola Atrix owners who wants to try the actual Ice Cream Sandwich/Android 4.0 right now.
Edit: I forgot to add that the battery usage is really badly optimized, or, because the phone is working at 120% when you use it, it naturally discharges faster.
okasion said:
I think it's very slow because
Click to expand...
Click to collapse
1- It's a dev leak ICS. Not official, not final, so all debugs are active
2- You might have to apply the Mem fix if you don't have all
The memory is slow ? Well it has LPDDR2 RAM, I don't think this matters. The issues you encountered are due to the lack of optimization of the kernel (Not enough time ? Maybe they didn't even try to optimize it...). This is a dev kernel, not a nightly, beta or stable release. It's not even finished.
This leak was the best thing that have happened on Atrix.
Now, all the drivers can be exported and finally we can have CM9 and even CM10 working good as in the Galaxy S.
Thansk to the one who leaked, to epinter and now, just have hope.
ishimarumakoto said:
This leak was the best thing that have happened on Atrix.
Now, all the drivers can be exported and finally we can have CM9 and even CM10 working good as in the Galaxy S.
Thansk to the one who leaked, to epinter and now, just have hope.
Click to expand...
Click to collapse
I think so, too.
LOL
Sent from my MB860 using xda app-developers app
leaked drivers
I am not sure if the CM team wants to use the leaked drivers as they might problematic - from the legal point of view.
cb5264 said:
I am not sure if teh CM team wants to use the leaked drivers as they might problematic - from the legal point of view.
Click to expand...
Click to collapse
Doesn't matter. The devs here hopefully will make stable roms using these drivers.
cb5264 said:
I am not sure if teh CM team wants to use the leaked drivers as they might problematic - from the legal point of view.
Click to expand...
Click to collapse
Some things Motorola just needs to let slide...
So yeah, so far so good the ROM worked fine, but the lack of installing side apps kind of made me upset.
SlimThePineapple said:
So yeah, so far so good the ROM worked fine, but the lack of installing side apps kind of made me upset.
Click to expand...
Click to collapse
Mine is installing everything without no problem.
I mdofied what was installed from the leak, so as not to wipe out my clockwork touch recovery.
Just made my own version of the script.
I live in the US but my Atrix was purchased from Newegg and came international (Italian). Immediately after flashing the leak img files along with my clockwork recovery.img, the script of course reboots the phone. I then go straight into the recovery and flash both the SuperUser and Ramfix zip files, then I let the phone boot up all the way. These files are also posted in the DEV forum.
This dramatically increase the first boot time, and because of the memory issue, is very fast and responsive during initial google setup.
I have yet to try WebTop 3.0, as all i have at work is my lapdock, my HDMI cradle and cables are at home. Attempting lapdock use fails as the screen resolution is not coded correctly, it shows up on the phone, but only about half of the image shows on the lapdock.
The only other Issues I have experienced is the USB audio in my motorola atrix cardock does not work, need to plug aux into the headphone jack.
There was also a post over in DEV saying the phone hard locked on an incoming call, requiring pulling the battery. This is true. I tested this twice. Then on a whim I changed the default ringtone from draco to pegasus. Now it works no prolem. I have also tried 2 other ringtones that escape me at the moment, so I beleive all you have to do is change the default ringtone.
My phone does not get hot. It did reboot once while copying files from internal to external sdcard. Other than that is has been rock solid.
Just some info for anyone trying it.
Flash method:
Download and unzip the leak - Link over in the DEV forums
I use linux and fastboot. But windows and moto-fastboot will probably give same results.
I edited my install script as you see here:
Code:
cat flash-ics.sh
#!/bin/bash
echo "Erasing recovery..."
fastboot erase recovery
sleep 2
echo "Erasing system..."
fastboot erase system
sleep 2
echo "Erasing userdata..."
fastboot erase userdata
sleep 2
echo "Erasing webtop..."
fastboot erase webtop
sleep 2
echo "Erasing preinstall..."
fastboot erase preinstall
sleep 2
echo "Flashing recovery..."
fastboot flash recovery recovery.img <> a note here, I copied the supplied motorola recovery to old-recovery and renamed my clockwork one
sleep 2
echo "Flashing boot image..."
fastboot flash boot boot.img
sleep 2
echo "Flashing preinstall..."
fastboot flash preinstall preinstall.img
sleep 2
echo "Flashing radio..."
fastboot flash radio radio.img
sleep 2
echo "Flashing system..."
fastboot flash system system.img
sleep 2
echo "Flashing Webtop 3.0..."
fastboot flash webtop vendor.img
sleep 2
echo "Rebooting phone..."
sleep 2
fastboot reboot
Those are the only things I am running.
Hope this helps someone.
Regards.
sauce on homescreen picture? lol.
cb5264 said:
I am not sure if the CM team wants to use the leaked drivers as they might problematic - from the legal point of view.
Click to expand...
Click to collapse
Yes we know how much time and resources Motorola has for their previous phones... lol
Sent from my GT-I9100 using xda premium
Current issues with ICS
* fingerprint
* cam
* some chipset glitches proudly sponsored by nvidia (insert quote of Linus here)
Anything new I am not aware of?
Overall how would you say the new mods are working? Since the unofficial ics it seems we have seen 3 or 4 new mods and each have a few nonfunctioning items. Do the updates include pieces of the leak? I'd like to know before i dive into modifying my atrix for the first time. Thanks in advance for your patience. I ask because i dont know whether to expect a brand new awesome perfect mod or a very good update to an existing one, maybe a CM.
Sent from my MB860 using xda app-developers app
It varies a lot from phone to phone
Sent from my MB860 using Tapatalk 2
So.... Loaded ArtICS 1.0 5 days ago, initially had some issues. Ramfix,removing the sd card and easy battery saver made a huge difference.
It is extremely stable for my, more than cm7.
Still outstanding :
-Stock camera, flash timing off, installed pro capture and works amazing.
-High battery consumption still high, getting 9hrs with medium usage.
-Reboots when sleep with sd card
-Uninstalling winamp huge improvement, stability wise, no idea why.
-Delayed screen illumination after sleep, this is only random, can see outline of objects on lock screen but if I wait 5 seconds the screen lights up.
-Stock music app fc constantly, kinda irrelevant, poweramp works flawlessly.
The only apps that wouldn't work is Motor Trend but who cares.
I was planning on making some tweaks to build.prop but i allow access via superuser to build prop editor and I get a message that it has no root access, need a little help! Nevermind, solved it.
Also, anyone figure out the sd/reboot issue? I read something about file allocation size being incorrect, anyone have any news or know how to modify this?
Cheers
Guys.... Really try a batt saver app..... I get through the day without charging, seems to make the rom more stable too.
Sent from my MB860 using xda app-developers app
Related
Didn't notice this before, but according to http://stats.cyanogenmod.com/ , there are two installs for 'daytona' (codename for Droid X2).
Also, cvpcs recently tweeted "i'll see what i can muster together. need to get some DX and X2 stuff posted".
Good news? Old news?
I didn't know they had even started on the X2, I knew the X1 already had it, or an RC at least.
cvpcs, who I believe ported CM4DX, just recently got the X2, but has been busy with life.
Also, the Droid X is becoming, or already is, an official CM supported device.
Before my brother got his X2, I was trying to get the CM7 build on it, but couldn't find the correct one on their site, this was almost 2 months ago though.
Actually I'm pretty sure that was me... I've been working on porting some cyanogen components out of an unofficial atrix build and one of the few things that did work was stats. Installed it twice
Sent from my DROID X2 using xda premium
drapp said:
Actually I'm pretty sure that was me... I've been working on porting some cyanogen components out of an unofficial atrix build and one of the few things that did work was stats. Installed it twice
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Do tell plz
They were just some of the apps i pulled from my cm7 on my old droid 2. I have however Been messing around on the ATRIX forums of cyanogen and noticed nighties being posted so I've been pulling as much as I can out in an effort to port it minus the kernel tweaks. As far as progress goes I've gone from it not installing at all, to starting to install and failing for a few different reasons, to installing successfully but stuck at boot logo... after 4 hours of sbfing and flashing my current status is successfully installs but starts bootlooping about 3 mins into powering on and not sure what my next move should be. Haven't gotten it to launch yet. 2 more sbfs and subsequent framework edits and im calling it a night
drapp said:
They were just some of the apps i pulled from my cm7 on my old droid 2. I have however Been messing around on the ATRIX forums of cyanogen and noticed nighties being posted so I've been pulling as much as I can out in an effort to port it minus the kernel tweaks. As far as progress goes I've gone from it not installing at all, to starting to install and failing for a few different reasons, to installing successfully but stuck at boot logo... after 4 hours of sbfing and flashing my current status is successfully installs but starts bootlooping about 3 mins into powering on and not sure what my next move should be. Haven't gotten it to launch yet. 2 more sbfs and subsequent framework edits and im calling it a night
Click to expand...
Click to collapse
Stupid question but did you remember to Wipe Everything Individually... From data to dalvic cache?
ericerk said:
Stupid question but did you remember to Wipe Everything Individually... From data to dalvic cache?
Click to expand...
Click to collapse
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
If at first u dont succeed... sbf and flash again lmfao
Sent from my DROID X2 using xda premium
drapp said:
If at first u dont succeed... sbf and flash again lmfao
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
Yup yup xDD
---------- Post added at 01:25 AM ---------- Previous post was at 01:20 AM ----------
drapp said:
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
If you still have time to give it (X2) back i'd recommend it,Get a Bionic or something or the droid 3, something thats more popular, d3 has cm7 booting same with the bionic, don't lock your self in a crap phone if you don't absolutely have to...
drapp said:
Yeah, wiped cache and delvik b4 nandroiding to save a little space, and again after just in case. Wiped data then installed. After install, wiped batt stats and fixed permissions while still in tenfars recovery. Then rebooted. After boot loop went into stock recovery and wiped data/cache again. Still no luck. [email protected]#ty thing is I go out of the country on business for a month so not gonna have time. Im working with the 1.2rc3 eclipse and the ATRIX or as is its referred to on CM site. olympus nightly 3 as my main base. Im thinking of downgrading to 2.3.3 just to try it with the x2 ATRIX port as a base instead, may help compatibility I think. The problem is I dont know just how much of cyanogen the custom kernel affects. Or if its only the cpu controls and various system tweaks. I do iphone development for a living yet ironically switched my own phone to a DROID 2 a couple months ago bc a friend had one lying around and my iphone screen broke. Found how to jailbreak(root) it a couple hours later. Had heard of cyanogen from a friend. Found a nightly found clockwork mod and fell in luv. That phone stopped charging and Verizon gave me an early upgrade to the x2 a couple weeks ago so here I am... Even if I can't make a full port my 2nd goal is a theme engine port. I have all the apks and frameworks from the newest ATRIX cm nightly its just trying to figure out what needs to be replaced or deleted to stop it from conflicting with another running process. For instance I got the theme chooser app to install In eclipse but either something in the frameworks the systemui.apk or framework-res.apk causes it to force close. It may even be the few blur components that are left. I've got a day left to work on this then im gone for a month. And does anybody know off hand if theme engine is in any way controlled by the kernel. Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Sent from my DROID X2 using xda premium
Click to expand...
Click to collapse
2nd init for the x2 was created on GB. I believe our ATRIX ports use 2nd init. Naven and dragon just made them flashable in CWM by including the 2nd init hack in the flash.
drapp said:
Also I read froyo has 2nd int'd, if some1 can get it on gingerbread this would be alot easier. Im working mostly solo tho so its all trial and error...
Click to expand...
Click to collapse
the posted 2nd-INIT in dev section for us works on gb if that is what you are referring to.
About CM7 & 2nd-init
the 2nd init that is used for all motorola devices (except the ATRIX) for cyanogenmod is designed for both froyo and gb. It has a check in there to see if the executable bit exists and figure out what to do from there. that way any motorola device could (in theory) use it. I know that this version of 2nd init works for the X2 and will pretty much be used when it comes to porting over cm7. We're going to have to use GB as our base (not Froyo) simply because of the requirements of our kernel (which we can't change).
About my involvement
now i know that I was original one who was trying to crank out cm7 and that it kinda died out. that doesn't mean that i don't play around with it from time to time. I'm starting from scratch, but if naven and/or cvcps or whomever get it running before I do, more power to them. I have little to no time to work with this, but I know what approach i'm taking this time. It is to simply base it off the ATRIX (obviously) but then work in the 2nd-init and edify scripts that the X uses. I kinda did that the first time, but got too mixed up in all of the details.
I don't want anyone to think that because I'm working on it that any results will arise. I'm merely trying to say that someone is working on it. Just maybe not as fast or with as much time as you guys will like. I want to have CM7, too. But we don't have a team or anything so it takes a lot of work.
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Peperm1nt said:
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Click to expand...
Click to collapse
Here's a link to cvpcs blog entry regarding 2nd-init when he was porting CM to Droid X.
http://cvpcs.org/blog/2011-06-14/2nd-init._what_it_is_and_how_it_works
Peperm1nt said:
@dragonzkiller
Quick question. I understand the 2nd INIT allows scripts to be ran at bootup to alter the kernel in a "temporary" environment(ie. Whatever settings are in place in the Init.d folder is used instead of default.. blah blah), at least that is my understanding of it. But the question here is
What does 2nd Init have to do with CM7? Or MIUI? To my understanding it simply allows scripts to Be ran in front of the Kernel settings. Unless I am wrong, What does this have to do with Heavily Modified roms if you are simply allowing a performance boost, etc?
Click to expand...
Click to collapse
2nd-init allows us to have a new init.rc script, not just scripts in general and in reality has no affect on init.d unless the init.rc script is told to do so. Basically 2nd-init kills the init process (and all spawned processes) that uses the stock init.rc and uses a new one which we copy during hijacking the boot process and starts the init process again.
The root directory (where init.rc lies) of our phone is writable, but is reflashed every time the phone boots up, thus erasing any changes we might have made to init.rc (kinda defeats the purpose of having a custom script). This script is the script that gets everything set up during the boot sequence starting roughly around the time the motorola logo first shows up and all through the boot animation. We need to have a custom init.rc to get our phone's environment setup for CM7.
Our problem arises when we have to have the script satisfy both the OS and the kernel. Motorola's kernel expects certain criteria to be fulfilled within the phone to allow it to do it's thing. If these aren't satisfied, the kernel panics and reboots the phone (hence why we get bootloops). We can use logging (a rather tedious, slow, and painful method) of finding out where the kernel panics, and adjust as needed. But we need to have the environment ready for CM7 also, so those changes need to be in there without causing a kernel panic.
"Heavily modified" is a bad way to put it, more like "non-BLUR." If we could get CM7 working we can use the init and build files/setup/etc to allow us to have more ROMs based of AOSP. MIUI is based off of AOSP and in theory if we figure out CM7 we can even have AOSP ourselves. In fact the ATRIX recently got a port of AOSP (albeit buggy, but still).
The link above to cvpcs's blog goes into the details about it. It's really good read.
dragonzkiller said:
The link above to cvpcs's blog goes into the details about it. It's really good read.
Click to expand...
Click to collapse
It is also written in a '2nd init for dummies' fashion. Don't be afraid to read it!
Sent from my DROID X2 using XDA App
I agree this phone is one big piece of poo!
SE7EN- said:
I agree this phone is one big piece of poo!
Click to expand...
Click to collapse
I don't remember seeing anyone in this thread say that. Who are you agreeing with?
I am living with what I'll refer to as a successfully rooted NT...
Got 9.9.9 showing
installing a lot of apps - most work, some don't but that's due to no camera, bluetooth, etc. that I discover later
Now, as crazy as this may seem, I'm sure there are some of us out there who want to get our NT's as fully "droided up" as possible, and then, lo and behold, leave it alone. Just enjoy it (with all due credit to the devs who have made it possible!).
So, for the rest of us, can someone offer a "checklist" of any outstanding mods that should be done? I am not out here too much but what about this CM7 and/or CM9 I hear about? Will this represent the final frontier?
My goal in asking this question is to understand when I've reached a point where I no longer feel compelled to fiddle with my device, but also feel I've advanced it as far as technologically and functionally possible
once we get a fully working cm7 and cm9, the NT will essentially be a full android tablet.
cm9 is ice cream sandwich(android 4), cm7 is gingerbread(android 2.3)
final frontier? maybe but right now both are in alpha stage development -and it has come really far in the past 2 weeks since the bootloader was cracked/hacked/bypassed
Great! Now, the question becomes, will it be necessary to install CM7 to get to CM9, or will it be possible to go right to CM9 (which I am assuming is the better of the two choices).
wedmiston said:
Great! Now, the question becomes, will it be necessary to install CM7 to get to CM9, or will it be possible to go right to CM9 (which I am assuming is the better of the two choices).
Click to expand...
Click to collapse
straight to cm9
Sent from my Nook Tablet using XDA PREMIUM
Anybody willing to risk a guess as to timeframe to CM9? Just curious...I'm patient.
wedmiston said:
Anybody willing to risk a guess as to timeframe to CM9? Just curious...I'm patient.
Click to expand...
Click to collapse
When it's done. the main holdup on cm9 from reading the dev section is- sleep of death other than that essentially everything else works i believe. personally my guess is probably next week for an alpha release, but that is completely upto the people working on it.
no hardware video acceleration yet.
cm7 main holdup is wifi and sleep of death- again they fix those two items and -again- probably next week depending
Forgive my ignorance, but what is "sleep of death?" unless by that you mean bricking it. What would be the reason to go with CM7 if CM9 is apparently a more advanced version of android and is on a parallel development track?
wedmiston said:
Forgive my ignorance, but what is "sleep of death?" unless by that you mean bricking it. What would be the reason to go with CM7 if CM9 is apparently a more advanced version of android and is on a parallel development track?
Click to expand...
Click to collapse
1 Sleep of death is basically the inability to wake the nook from sleep mode. On stock nooks and working android devices the power button usually puts it to sleep. Right now CM on the nook puts it to sleep without allowing it to wake. It doesn't brick the device but it requires you to hard reset/reboot the device to make it usable again. When I say "hard reset," I mean in the traditional sense (holding a button sequence or cutting off power to FORCE a restart the device). I do NOT mean a "factory reset" that erases everything.
2 CM7 is already fully developed and released on other devices. In theory it should be far more stable and reliable than CM9, which is bleeding edge and unfinished in general. In other words, CM9 is practically guaranteed to have more bugs since it's got so much new stuff in it.
wedmiston said:
Forgive my ignorance, but what is "sleep of death?" unless by that you mean bricking it. What would be the reason to go with CM7 if CM9 is apparently a more advanced version of android and is on a parallel development track?
Click to expand...
Click to collapse
cm9 is a different kernel then cm7. What this means is not all apps will work on cm9. cm7 in theory should have better app compatibility, but cm9 should be better optimized for the NT.
As for sleep of death, I am pretty certain what it is, is every time the tablet goes to sleep. it dies.... why by now they have probably buried dozens of poor helpless NTs who never got a proper chance at life.... all in the name of progress. (ok sarcasm aside, SOD is simply you can't bring it back out of sleep. while I suppose you could simply disable sleep mode, doing so would badly hurt battery life, Also I believe they are trying to get bluetooth up and running as well for cm9)
So I hear you say cm7 = better app compatibility and cm9 = better optimized for the NT. In honor of super bowl season, sounds a bit like "great taste, less filling."
In other words, which would be the better choice between the two (assuming bugs have been worked out and both are stable)?
personal preference?
honestly, it'll be whichever you like best, with the way they have it setup to bypass the bootload in the nook tablet, you should be able to flash Either with the press of a button or two, try one for a week, try the other for a week, then decide which you like best.
you do have to remember cm7 is more for phones, which cm9 is more for tablets....
I agree with lenardo. The better of the two is the one that meets your needs. That said, I am more looking forward to CM9. I installed it on my phone a month ago and love it. It feels so much more polished. Not that I had any issues with CM7, but it just feels like "this is what Android should be." But beware ... once you start flashing and modding, it's quite addictive.
Sent from my SCH-I500 using Tapatalk
Thanks - based on your reply and what I was reading in a recent thread on choosing CM7 or CM9, I think I'll wait for 9 since I don't have the phone , only the NT.
I assume there will be some big announcement and posting along with step by step installation instructions?
wedmiston said:
Thanks - based on your reply and what I was reading in a recent thread on choosing CM7 or CM9, I think I'll wait for 9 since I don't have the phone , only the NT.
I assume there will be some big announcement and posting along with step by step installation instructions?
Click to expand...
Click to collapse
announcement is likely, step by step instructions will most likely involve using cwm to install. So if you haven't already installed it, install cwm now so you will be ready
http://forum.xda-developers.com/showthread.php?t=1458630
as for cm9 vs cm7 as the others have stated most people are waiting for cm9. I will most certainly give both a try. unless there is an app that I can't live without that just won't run on cm9, I will probably be using it. If I find I can't use certain apps with cm9, then I will be moving to cm7. However I will give both a try. there is little point in making a decision with only looking at one side of the choice.
ckevinwelch said:
I agree with lenardo. The better of the two is the one that meets your needs. That said, I am more looking forward to CM9. I installed it on my phone a month ago and love it. It feels so much more polished. Not that I had any issues with CM7, but it just feels like "this is what Android should be." But beware ... once you start flashing and modding, it's quite addictive.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
Oh, I forgot to mention that CM9 should support tablet-focused apps as well.
Sent from my SCH-I500 using Tapatalk
Checked out the thread and downloaded the Nook recovery Flasher.apk - is this is what I install and use if necessary?
lol I couldn't agree more with wedmiston post on developments of the NT.. I know these guys are working full time to ~freethenook~ and it takes some diligence to simply stay up to date with these fast moving mods and alterations.... But its interesting to see how these is evolving.
---------- Post added at 10:35 PM ---------- Previous post was at 10:33 PM ----------
I'm patient.....................lmao
wedmiston said:
Checked out the thread and downloaded the Nook recovery Flasher.apk - is this is what I install and use if necessary?
Click to expand...
Click to collapse
Yes. to explain what the recovery flasher app does. it installs clockworkmod (cwm) or the nook stock recovery. the stock recovery is what you would use to fix your nook if you really screw it up somehow. you can access it by holding the power and nook buttons at the same time while booting up. (i.e. the power is off, turn it on with both the n button and the power button, holding them until it gives you the option to restore stock firmware).
Clockwork mod would replace this. If you use the recovery flasher to flash cwm, then instead of the option to reset the device to factory settings, holding the power button + n button on bootup will get you into the CWM menu. cmw can be used for several things. It can backup your firmware so you can restore things if you screw up. (i.e. backup your rooted firmware, so resetting isn't unrooting anymore) or it can flash zip files to modify your existing firmware. you would be using the flash zip files function to flash the cm9 or cm7 firmware once they are done.
There isn't much atm that you can do with cwm other then backup your current firmware in case you screw something up, however I would suggest doing so. it's always good to have an easy way to fix things if you screw it up somehow playing around makes it easy.
The flasher apk will also allow you to flash back to the default barnes and noble recovery if you wanted to get rid of cwm for some reason I can't think of.
EDIT: you can also download "Quickboot" from the google market to get to the recovery menu without rebooting and holding the n button + power button.
Also useful to know. controls in CWM: + and - buttons will move between options. n button will select whatever you are on, and the back button is the power button.
To piggyback on the reply above there really isn't any need for quick boot as Indirect's App ALSO allows to "reboot recovery" from within the app.
As the system would need to be running in order you use this, there really isn't any need for both app's strictly to get to recovery.
The advantage of Quick Boot is that it also offers you the option to "reboot" the device which I believe is currently only possible by turning it off and then back on. Not a big deal but it will save an extra step.
The disadvantage of Quick Boot is that it will also provide you with the option to boot into the bootloader. DON"T click that.
Land Master said:
To piggyback on the reply above there really isn't any need for quick boot as Indirect's App ALSO allows to "reboot recovery" from within the app.
As the system would need to be running in order you use this, there really isn't any need for both app's strictly to get to recovery.
The advantage of Quick Boot is that it also offers you the option to "reboot" the device which I believe is currently only possible by turning it off and then back on. Not a big deal but it will save an extra step.
The disadvantage of Quick Boot is that it will also provide you with the option to boot into the bootloader. DON"T click that.
Click to expand...
Click to collapse
u can also do a quick reboot by using terminal emulator, and doing su and then reboot, very quick...
So I have seen alot of threads asking on how to go back to Gingerbread if you have installed the newest leaked RUU that came out about 5 days ago. Also once you go back to GB, the SD card mounts have changed, so you need to fix that too. Here are some simple ways.
If you have a nandroid (which you should have made) you can restore your backup from that. You then have install the correct kernel. You can do this one of two ways.
Download this PH98IMG.zip and place it on your SD card's root. Meaning not in a folder. Then boot back into hboot and let this install.
The other way is to take that PH98IMG.zip and open it. Grab the boot.img out of it and place it on your computer in the same folder that has adb.exe and fastboot.exe in it. (Same place that you used to unlock your phone). Next open up the command prompt and change directories to where you have adb and fastboot. For example, mine is C:\Android so the command would be "cd c:\android" Then type the following command "fastboot flash boot boot.img" Remember that you need to be in fastboot mode on your phone and connected to the usb port.
Once that is complete, boot into recovery and flash this file. This is the SD card mount fix that scrosler posted. This should get back up and running.
If you don't have a nandroid backup (shame on you) then you can use any of the GB roms to flash like you have before, making sure that you flash the kernel also. Then flash the SD card mount fix in recovery.
Things of note, once you have flashed the leaked RUU, there is no way right now to run the Official RUU's. The leaked RUU updates your hboot and radios, there is no way to downgrade those.
As always I am not responsible if your phone catches fire, starts talking in a foreign language, or causes spontaneous combustion.
Hopefully I have helped someone out.
Special shout out to scrosler for making the SD card fix and hosting the PH98IMG.zip on his site.
I will probably never go back to GB but thank you for putting this together for those users who would like to.
EmerikL said:
As always I am not responsible if your phone catches fire, starts talking in a foreign language, or causes spontaneous combustion.
Click to expand...
Click to collapse
LOL, no doubt.
The current latest leak: 3.11.605.22 is too good! I don't know why anybody would want to go back to Gingerbread.
Fiosonlinegaming said:
LOL, no doubt.
The current latest leak: 3.11.605.22 is too good! I don't know why anybody would want to go back to Gingerbread.
Click to expand...
Click to collapse
Do it for teh kernalz!! but hopefully we have some great kernels when the source is released
Very helpful until these battery/heat issues are resolved.
taptaptouch said:
Do it for teh kernalz!! but hopefully we have some great kernels when the source is released
Click to expand...
Click to collapse
The GB Kernels all wind up crashing the phone eventually, except for the Non-OC ones.
Since my phone is my alarm clock, I have to be 100% stable.
The ONLY OC Kernel that I have been able to run for weeks without waking up to a rebooting phone (and being late for work), period, is this one
http://forum.xda-developers.com/showthread.php?t=1496934
All day, every day. And I'm on not even on the .22 ICS leak, I'm on .1.
dsb's, ziggy's, and all the other GB kernels EVENTUALLY make bootloops happen (even though I always ran them at 1.5ghz), even if it takes days or weeks.
This guy's ICS kernels are perfect. Minor tweaks, and From-Factory level stability.
ICS wasn't ready a month ago, IMO, but it's ready now. .22 (and .1, in my opinion) are ready for launch. Smooth as butter.
cpurick said:
Very helpful until these battery/heat issues are resolved.
Click to expand...
Click to collapse
Why is it that some people have issues with the battery and heat (ME) and others have all day battery life and no heat issues?? And my radios seem to be worse but most people say they are better??
Thanks for the helpful instructions. I may end up going back if I cant find an ICS rom that has the functions working that I need.
infamous_6969 said:
Thanks for the helpful instructions. I may end up going back if I cant find an ICS rom that has the functions working that I need.
Click to expand...
Click to collapse
What functions do you need that don't work?
Why is it that some people have issues with the battery and heat (ME) and others have all day battery life and no heat issues?? And my radios seem to be worse but most people say they are better??
Click to expand...
Click to collapse
I too wonder the same thing. I am having terrible heat issues and my battery is drained in 4-5 hours if I use the Rezound. I love some of the features of ICS, but no enjoyable to use the phone with out it heating up is bothersome.
-- Sent from my TouchPad using Communities
The instructions work, but I had two problems -- first, my WiFi only works with the latest ICS kernel for some reason. Must have something to do with the radio changes, even though others have been able to run other kernels on theirs.
Also, it's now hotter than ever running GB -- probably because there's no WiFi and all traffic's going over 3g/4g.
Back to the leak for now. God, I hope they fix this.
just curious, will this work to go back to old firmware and still run the older ICS roms? i have a suspsicion that either new firmware or soemthing else might be MURDERING my battery nowadays, and i'm wondering if i should go back to old firmware or not.
Nope there is no going back. That hope was defeated a couple of days ago when they couldn't get the hboot to downgrade like the EVO.
Sent from my ADR6425LVW using xda premium
meh oh well lol thanks for the reply, though! and the writeup, either way
I found and applied the fix for WiFi errors, and I'm now back up running GB. Still have the new radio firmware, so only time will tell if it's any better with power/heat.
I found and applied the fix for WiFi errors, and I'm now back up running GB. Still have the new radio firmware, so only time will tell if it's any better with power/heat.
Click to expand...
Click to collapse
Please keep us updated on the power/heat
-- Sent from my TouchPad using Communities
Better. For me anyway.
Sent from my ADR6425LVW using xda premium
Phone still will not charge unless it's turned off. If I put it in airplane mode it will charge overnight. But if I'm actually using it while plugged in to power, it will actually discharge even if it doesn't get very hot. The heat, btw, is much better since reverting to GB, even with the ICS baseband.
I did not have this particular problem before I took the leak.
I was able to get back to the GB rom, but now my SD card (internal & external) wont mount. I've ran the SD card fix a couple of times.
Any idea what could be wrong?
is there anyone in south florida who's an android expert who'll tinker with my sgp for me? ill pay you...ive been on reading and searching on this form for about 5 hours now and im left with even more questions and more confused. have i said ill pay you?
No offence but this seems a bit dodgy. Most of the stuff available on here is free and there are many people who can answer your questions so you don't need to pay anyone to help you
Sent from my Nexus 7 using XDA Premium HD app
Supermaster34 said:
No offence but this seems a bit dodgy. Most of the stuff available on here is free and there are many people who can answer your questions so you don't need to pay anyone to help you
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
He is right.
Sent from my GT-I9000 using xda premium
ok ill run my problem in this thread too, maybe i can get this working. i posted this question/problem in another thread too and i dont know how to reference via link to other thread thru my SGP so forgive me for double posting.
this is what i did, i downloaded dd_03052012.zip from entropy. unzipped it in winrar. then when i tried adding the tar to pda section of odin, it wasn't there (but if i were to open its folder thru win explorer then i would see it) just odin wasn't recognizing it. so i renamed the zimage file with .tar at the end, now odin sees it so i go ahead and add it into pda field and push start (player was in download mode) odin said reset....then after a couple secs it said passed! and then it reboot itself...still stock kernal. please help, I've literally been working on this for twelve hours with a break to go grocery shopping thanks in advance.
(all im trying to accomplish right now is gettin cwm)
Sent from my YP-G70 using xda app-developers app
How to flash .zip releases:
Put it on your sdcard, enter CWM, flash the .zip using CWM
If you do not have CWM, install an older .tar release then flash, or follow the "Any rooted device" instructions above, but extract the zImage from the .zip instead of a .tar
Click to expand...
Click to collapse
this is from the thread itself. It also says to read the first 3 posts fully before flashing so that might be a good idea
Sent from my Nexus 7 using XDA Premium HD app
i know..I've read every post on every page in that thread as well as several other threads.
and ive also tried that method u mentioned from the post. but after i installed the initial tar file (so i can have the cwm) my player is still at oem kernel, even tho it said passed in odin. I've checked and unchecked my steps, i dont know what im young wrong. im just trying to make nandroid backup before i do anything else. thanks
Sent from my YP-G70 using xda app-developers app
1 .Go to the OP (Original Post) of this thread:
http://forum.xda-developers.com/showthread.php?t=1445840&highlight=entropy512
2. Download this kernel:
DD_01142012.tarThen, place it on the desktop directory, or an otherwise easily accessible directory, on your computer.
Do not attempt to unzip it or manipulate it in any way!
3. Run ODIN.
4. Now, put your SGP into download mode by holding the volume down + power button until your device turns back on with a yellow construction-like sign.
5. Insert USB cable now, and ensure that ODIN has recognized the device by looking to see if a device is registered in the ID:COM field.
You should see something like this: 0:[COM11]
Now, you're ready to flash the kernel!
6. In the ODIN interface, press the PDA button and navigate to the directory where you saved the kernel you downloaded and double-click to open.
7. Now press START and wait about 20 ~ 30 seconds to finish the flash.
As this is but a kernel, and not a ROM, the flash time will be short!
8. ODIN WILL REBOOT YOUR DEVICE FOR YOU!
9. Now you should have entropy512's kernel on your device.
Good Luck!:good:
P.S. - Once you've flashed the original .tar file, you should have CWM active on your device. From this point forward, you should put entropy512's kernel updates on your SD Card and flash them from CWM and NOT ODIN!
You have to flash the CWM.tar in Odin PRIOR to even TRYING to install the kernel.
Once you have CWM, place the dd_1234567etc.zip AS IS in the root of ext sdcard.
Flash .zip in CWM.
Done.
Higgs_Boson said:
1 .Go to the OP (Original Post) of this thread:
http://forum.xda-developers.com/showthread.php?t=1445840&highlight=entropy512
2. Download this kernel:
DD_01142012.tarThen, place it on the desktop directory, or an otherwise easily accessible directory, on your computer.
Do not attempt to unzip it or manipulate it in any way!
3. Run ODIN.
5. Now, put your SGP into download mode by holding the volume down + power button until your device turns back on with a yellow construction-like sign.
6. Insert USB cable now, and ensure that ODIN has recognized the device by looking to see if a device is registered in the ID:COM field.
You should see something like this: 0:[COM11]
Now, you're ready to flash the kernel!
7. In the ODIN interface, press the PDA button and navigate to the directory where you saved the kernel you downloaded and double-click to open.
8. Now press START and wait about 20 ~ 30 seconds to finish the flash.
As this is but a kernel, and not a ROM, the flash time will be short!
9. ODIN WILL REBOOT YOUR DEVICE FOR YOU!
10. Now you should have entropy512's kernel on your device.
Good Luck!:good:
P.S. - Once you've flashed the original .tar file, you should have CWM active on your device. From this point forward, you should put entropy512's kernel updates on your SD Card and flash them from CWM and NOT ODIN!
Click to expand...
Click to collapse
dude..i LOVE u!! thank u sooo friggin much ur help. i actually did all of that exactly last night but to no avail. but what you did to help me was when you said something like 'download the tar and dont unzip it or manipulate it in any way'...i never unzipped it before either but when i downloaded it, winrar would automatically turn it into a 'winrar' file. so in a sense, my computer was "manipulating" it, so i uninstalled winrar (7zip is better anyways) and voila, everythings kosher. thanks dude. i wouldve never have thought of that if it wasnt for that one piece of instruction.
so i have done entropys updates yet, but when i powered it off to try out cwm (it was still plugged into cpu) it powered off and kept re-cycling the powering off action, until i disconnected it from cpu and everything was fine. i wonder if thats normal. anyhow, i trust the rest of my tinkering will fruitfull...thanks again bro.
Scymynd said:
...so i have done entropys updates yet, but when i powered it off to try out cwm (it was still plugged into cpu) it powered off and kept re-cycling the powering off action, until i disconnected it from cpu and everything was fine. i wonder if thats normal. anyhow, i trust the rest of my tinkering will fruitfull...thanks again bro.
Click to expand...
Click to collapse
What you mentioned is a known bug. It is kernel related. You cannot charge via USB plugged into a computer. Although, can charge via USB plugged into a wall.
In order to get to CWM mode (aka recovery mode) follow these steps:
1. Press and hold Power + Volume UP
2. The device will reboot and you'll see the Samsung logo. Don't let go yet!
3. The device will reboot once again. When you see the Samsung logo, let go of only the power button.
4. You should now be in recovery mode.
This is how I do it on my SGP 5.0 Korean model. The USA model may be different, and you may be able to skip STEP 3.
Ok sweet...well ive literally been playin around with this player since we spoke last. Im makin it tailored to my liking, however, theres one big and one small problem im having. The small one which isnt really anything is that when the players off and i plug it into wall charger the battery screen pops up but it doesnt display any juice in it - so im not even sure its charging in off mode, but it charges while its on no problem. Big problem is that when i have my earplugs plugged in, the player randomly owers the volume all the way to mute by itself and after i raise vol again it lowers it back down. But once i unplug earphones then the vol behaves again. I dont think its the earphones cuz theyre bose and i doubt they would make a faulty product (although its possible i suppose). Other than those two problems, everythings perfect. Any ideas? Tried doing a search on volume bug to no avail. Thanks!
Sent from my YP-G70 using xda app-developers app
Scymynd said:
Ok sweet...well ive literally been playin around with this player since we spoke last. Im makin it tailored to my liking, however, theres one big and one small problem im having. The small one which isnt really anything is that when the players off and i plug it into wall charger the battery screen pops up but it doesnt display any juice in it - so im not even sure its charging in off mode, but it charges while its on no problem. Big problem is that when i have my earplugs plugged in, the player randomly owers the volume all the way to mute by itself and after i raise vol again it lowers it back down. But once i unplug earphones then the vol behaves again. I dont think its the earphones cuz theyre bose and i doubt they would make a faulty product (although its possible i suppose). Other than those two problems, everythings perfect. Any ideas? Tried doing a search on volume bug to no avail. Thanks!
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
A couple of questions:
1. What ROM are you using? *
2. What app are you using to listen to music? **
*The reason I ask is because the charging issue could be a ROM issue. I am running Supermaster34's CM9 build on my SGP 5.0 Korean model and if I charge my device while powered off I can see the juice registering in the battery. It could also be a kernel issue. Since I have a Korean model, I use an entirely different kernel, which could provide an entirely different outcome.
**As for the volume issue, I thought that it could be software related. Be sure there is not a automatic volume minimizer setting within the app itself. It could also be kernel or ROM related.
I am not an expert on kernel or ROM issues, but there are definitely people in this forum that could give you a proper developer's response. But, go ahead and answer those questions and I'll see what I can help you with.
I'm using the chip rom and I poweramp for tunes. And most of the high fps games I play freeze up on me. shouldn't it be smoother now that I'm overclocked to 1.3?
Sent from my YP-G70 using xda app-developers app
Scymynd said:
I'm using the chip rom and I poweramp for tunes. And most of the high fps games I play freeze up on me. shouldn't it be smoother now that I'm overclocked to 1.3?
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
Not necessarily. GB doesn't manage ram too well IMO so games still tend to lag at times. ICS has better ram management, its still not perfect, but most games run pretty smoothly
Sent from my Nexus 7 using XDA Premium HD app
Scymynd said:
I'm using the chip rom and I poweramp for tunes. And most of the high fps games I play freeze up on me. shouldn't it be smoother now that I'm overclocked to 1.3?
Sent from my YP-G70 using xda app-developers app
Click to expand...
Click to collapse
If you're not too adamant about using the camera on your device, I'd say Supermaster34's CM9 build is a great way to go. He even put together a Bluetooth patch, so really the only things that aren't working on CM9 for the SGP 5.0 are the camera and hardware acceleration.
Like I mentioned earlier, that's the ROM I use, and I don't have any volume or RAM issues. In most instances, CM9 runs quite smooth for me, except for a couple widgets that really need hardware acceleration to be optimal (and, I stress the word optimal).
Better yet, we have some amazing developers in the SGP forum that are working tirelessly to get CM10 (Jelly Bean) working on our devices, along with a 3.x kernel for hardware acceleration and addressing other bug issues.
Worst case scenario, you could use stock ROM rooted for optimal performance.
Sorry to throw my two cents in but if you want to keep your camera, format the file system to ext4. If your fimilar to quadrent benchmark, this is my score after the ext4 file system tweak. I compared it to my dad's SGP 5 with the same rom and he got under 1300 so this tweak is a must have.
Sent from my Chip 1.5 ROM + Entropy512's Kernal Samsung Galaxy Player 5.0 U.S.
nightfire37 said:
Sorry to throw my two cents in but if you want to keep your camera, format the file system to ext4. If your fimilar to quadrent benchmark, this is my score after the ext4 file system tweak. I compared it to my dad's SGP 5 with the same rom and he got under 1300 so this tweak is a must have.
Sent from my Chip 1.5 ROM + Entropy512's Kernal Samsung Galaxy Player 5.0 U.S.
Click to expand...
Click to collapse
im just now making an effort to learning about ext4. from what ive read so far, it partitions 1gb on external sdcard for use as internal memory? and if thats true then would it still be beneficial for me even though i have over a gig free internally anyway? thanks
Supermaster34 said:
Not necessarily. GB doesn't manage ram too well IMO so games still tend to lag at times. ICS has better ram management, its still not perfect, but most games run pretty smoothly
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
ive new with android as far as the mechanics of the software(s) and stuff so i dont understand the differences of each, the pros/cons of each, and/or which one is tailored to my life. theres so much info on these forums and i just get caught up reading about one thing, then i see something in that post that i want to search on, so i search for info on that and before i know it, my firefox is filled with tabs up the wazooo..lol....and then i forget what i initially was searching for. i guess im just gonna have to keep flashing roms until i find one i like the best? is that what you did in the beginning? is it good to keep flashing roms like that?...im now using chip rom and i love it so far, but i guess i cant say i like it the best cuz i dont know what to compare it to =/ ...or even WHAT im trying to compare, i guess the speed, interface, if it makes any features less functional on device...?
Scymynd said:
...i guess im just gonna have to keep flashing roms until i find one i like the best? is that what you did in the beginning? is it good to keep flashing roms like that?...im now using chip rom and i love it so far, but i guess i cant say i like it the best cuz i dont know what to compare it to =/ ...or even WHAT im trying to compare, i guess the speed, interface, if it makes any features less functional on device...?
Click to expand...
Click to collapse
My friend, that's what we all do around here. Flash as many ROMs as you like. Just be sure to always keep a backup in CWM recovery! Also, take care to flash ROMs that are meant for your device. Always read the OP of any ROM's thread to make sure there is no technical detail overlooked.
Be cautious, but have fun.:good:
cool..well im going to tryout supermasters rom right now...wish me luck. and forgive me if this is a dumb question but are all launchers compatible with all roms? or just the launchers that are packaged with it?
Nothing was the same after rooting my atrix.
-The HD games started to freeze, and on the worst cases crashing (e.g. GTA VC).
-Background apps (e.g. Gauge Battery Widget) rebooted very often (specially when browsing).
-When surfing multiple heavy pages, the browser tends to crash sometimes. Also when it crashes, it returns me to the start screen and if i have a live wallpaper running it stops and changes to a generic black screen.
-When trying to upload an image file on an image board, the browser refreshes the page.
-Overheats without reason from time to time. Seriously, its like a pocket heater.
-When the screen animations are activated, returning from landscape to vertical orientation turns the notification bar blurry and when i pull down the notifications tray it turns the screen blurry as well. Though it returns to normal when going back to landscape.
This is a major issue for me since if i turn off the screen animations, i can't tell if an app i opened is running (e.g. YouTube). And like i don't use the stock video player and use another player (e.g. MX player), when the animations are activated instantly crashes when opening a video.
Also before rooting, the battery only lasts me 5 hours without running apps and the problem persists ever since.
One thing. The first time i got the phone it came with stock FROYO 2.2.1 and i changed it right away to GINGERBREAD 2.3.6 skipping the 2.3.4, i unlocked the bootloader first and then rooted it.
Is there anything i can do to fix the problems previously mentioned?
I have a feeling you are an international user and did not flash the ramfix, search for it in development section, download to sd and flash.
jorno88 said:
I have a feeling you are an international user and did not flash the ramfix, search for it in development section, download to sd and flash.
Click to expand...
Click to collapse
Every tutorial i looked for didn't mentioned that, i'll give it a try.
But if i do that, does it mean i will have to do a hard reset?
It is surely mentioned in subsequent posts in the tutorial thread.
RAM fix has nothing to do with data so factory reset (or hard reset as you call it) is not needed.
ravilov said:
It is surely mentioned in subsequent posts in the tutorial thread.
RAM fix has nothing to do with data so factory reset (or hard reset as you call it) is not needed.
Click to expand...
Click to collapse
Not in the tutorials i've followed, they never mentioned it. FYI none of the tuts where from here.
Good to know i won't have to hard reset. So were does the zip go, internal or external?
always follow xda, it's the best
as for the zip, place it wherever you like and flash it with a custom recovery like cwm or twrp
Yeah I could never understand people who follow a tutorial on forum X then ask about it on forum Y... Makes no sense to me. Why are people on forum Y supposed to know anything about forum X or its contents?
Questions about a tutorial on some forum should be asked on that same forum.
And yeah, everything you need is on XDA, no need to go search for random sources.
Just to help the OP:
https://www.dropbox.com/sh/cu2bd61dh6ytzda/C-z3zfNBcr (just get the RAMfix.zip from this link)
http://www.youtube.com/watch?v=p5T9hJ4Yjek
Hope this helps OP. I have a At&t and I don't need to do the RAM fix. U can give this a shot. All the best.
5HoofedStallion said:
Not in the tutorials i've followed, they never mentioned it. FYI none of the tuts where from here.
Good to know i won't have to hard reset. So were does the zip go, internal or external?
Click to expand...
Click to collapse
Ramfix may not be mentioned in root tutorials because it's related with unlocking bootloader. Since you first unlocked, then rooted, you'll have to flash it anyway.
GH0ST DR0NE said:
Just to help the OP:
Hope this helps OP. I have a At&t and I don't need to do the RAM fix. U can give this a shot. All the best.
Click to expand...
Click to collapse
Off topic, but now that you brought the subject. I have seen this a while ago, and looks tempting but is it convenient for me to use the leaked ICS rom? Is there any bugs in it to be concerned about?
It's a shame that motorola decided to leave the atrix in the shadows with GB, they could at least made ICS the final and definitive update. I mean, the rom looks like it was 99% finished and ready to launch.
saldirai said:
Ramfix may not be mentioned in root tutorials because it's related with unlocking bootloader. Since you first unlocked, then rooted, you'll have to flash it anyway.
Click to expand...
Click to collapse
I followed both root and bootloader unlock tutorials and NONE brought that out. Since i'm LATAM, it made sense for me to seek in latin android forums instead here because of the firmwares, and boy they skip a lot of useful info in those forums.
Also, how do i exactly run the ramfix? Im eager to fix the buggy notification tray right away, that and fixing my battery not charging at 100%. I tried pulling the battery while charging and it turned worse, it went from 90% to 70%
I also need to know how to wipe the battery data from the CWM.
5HoofedStallion said:
... is it convenient for me to use the leaked ICS rom? Is there any bugs in it to be concerned about?
It's a shame that motorola decided to leave the atrix in the shadows with GB, they could at least made ICS the final and definitive update. I mean, the rom looks like it was 99% finished and ready to launch.
Click to expand...
Click to collapse
If it's running well for you, you should consider yourself very lucky. You should also read some of the threads concerning it and related ROMs (AtrICS etc) - the thing is so buggy very few people even wonder anymore how come it was never released.
Even if it's running so great for you as you say, I still wouldn't keep it if I were you. The ROM is a development build, it was never meant to be used as a daily driver. But that's just me.
5HoofedStallion said:
Off topic, but now that you brought the subject. I have seen this a while ago, and looks tempting but is it convenient for me to use the leaked ICS rom? Is there any bugs in it to be concerned about?
It's a shame that motorola decided to leave the atrix in the shadows with GB, they could at least made ICS the final and definitive update. I mean, the rom looks like it was 99% finished and ready to launch.
I followed both root and bootloader unlock tutorials and NONE brought that out. Since i'm LATAM, it made sense for me to seek in latin android forums instead here because of the firmwares, and boy they skip a lot of useful info in those forums.
Also, how do i exactly run the ramfix? Im eager to fix the buggy notification tray right away, that and fixing my battery not charging at 100%. I tried pulling the battery while charging and it turned worse, it went from 90% to 70%
I also need to know how to wipe the battery data from the CWM.
Click to expand...
Click to collapse
I agree with u. But Motorola is infamous for such antics. One if the reasons I don't have a RaZr anymore. But it is running good. I will b honest. Its OK. This phone isn't made for anything but GB in mind. I would pick a low end, second hand Windows Phone any day over this.
But this is as far as it goes for Atrix. Jelly Bean...naah.
Sent from my Π Σ Χ U S 4.
How am i supposed to run the ramfix?
Sent from my rooted & unlocked Motorola Atrix.
It's a flashable zip so just install it like gapps or a rom. Install from sd card
Which are the commands on the atrix?
Sent from my rooted & unlocked Motorola Atrix.
Use a custom recovery... You can manually adjust the cmdline but flashing the zip is much easier
You mean, with the RSD Lite?
Sent from my rooted & unlocked Motorola Atrix, using Tapatalk 2.
Don't ever touch RSD, RSDLite or any SBF (except pudding) unless you're at gunpoint.
Then how the hell do i run ramfix on clockwork!?!
Sent from my rooted & unlocked Motorola Atrix, using Tapatalk 2.
Would do you good if you could learn to search and read. It's all explained many times...
Hint: CWM = ClockWorkMod recovery
Another hint: How do you usually use a flashable zip?