yashsingh1/xdaforums huggingface dataset:
[Atrix 4G Q&A, Help & Troubleshooting] okasion:
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.
[Atrix 4G Q&A, Help & Troubleshooting] jisse44:
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
[Atrix 4G Q&A, Help & Troubleshooting] Slymayer:
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.
[Atrix 4G Q&A, Help & Troubleshooting] ishimarumakoto:
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.
[Atrix 4G Q&A, Help & Troubleshooting] kkuuo:
I think so, too.

LOL
[Atrix 4G Q&A, Help & Troubleshooting] cb5264:
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.
[Atrix 4G Q&A, Help & Troubleshooting] djluis48:
Doesn't matter. The devs here hopefully will make stable roms using these drivers.
[Atrix 4G Q&A, Help & Troubleshooting] BigMatza:
Some things Motorola just needs to let slide...
[Atrix 4G Q&A, Help & Troubleshooting] SlimThePineapple:
So yeah, so far so good the ROM worked fine, but the lack of installing side apps kind of made me upset.
[Atrix 4G Q&A, Help & Troubleshooting] ishimarumakoto:
Mine is installing everything without no problem.
[Atrix 4G Q&A, Help & Troubleshooting] sjerome1:
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:

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. :o
[Atrix 4G Q&A, Help & Troubleshooting] wudien:
sauce on homescreen picture? lol.
[Atrix 4G Q&A, Help & Troubleshooting] ccrows:
Yes we know how much time and resources Motorola has for their previous phones... lol
[Atrix 4G Q&A, Help & Troubleshooting] cb5264:
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?
[Atrix 4G Q&A, Help & Troubleshooting] hakoch2:
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.
[Atrix 4G Q&A, Help & Troubleshooting] consolation:
It varies a lot from phone to phone
[Atrix 4G Q&A, Help & Troubleshooting] sssssbarn:
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.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Grady Llwyd:
Apologies for the fairly noobish question, but I am trying to track down some good ROMS for the G-Note, preferably a vanilla style JB with S-Pen support. Any suggestions are appreciated.

Thanks in advance :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
nothing with the samsung apps of Smemo or snote. only work with TW... JB roms has other apps that might work with spen

---------- Post added at 06:09 PM ---------- Previous post was at 06:05 PM ----------

check the link below. it has most of the customer roms for note thanks to jeetu

http://xdaforums.com/showthread.php?t=1847786

---------- Post added at 06:41 PM ---------- Previous post was at 06:09 PM ----------

another link for you

http://xdaforums.com/showthread.php?t=1874960
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] cyapalmpos:
Yeah I like Touchwiz and the Samsung apps (s-memo, photo editor, s planner...) so I'm holding out for a Jelly Bean build with all of 'em. I've been searching around and haven't found one yet.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] ginopunsalan:
I am not sure if Paranoidandroid Utaka has pen support. I've been using this rom for quite some time and love it. It seems very vanilla JB. I had to manually install Gapps (install zip) and Maps (Google Play).

http://xdaforums.com/showthread.php?t=1871713
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] cris.esza:
There are no stock JB ROMs for the N7000 yet.

That said, all Jelly Bean ROMs (CM10-based) support the S Pen, but you need to find your own apps for using it, like Jotter: https://play.google.com/store/apps/details?id=com.intulon.android.jotter
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] SpyderTracks:
Spen apps from samsung rely on TouchWiz framework, so as yet there are none available until samsung release the jb update. There are alternative apps that'll work with cm based roms such as cm10 and paranoid android as mentioned above, but none of them support Touchwizz and never will do.
[HTC EVO 3D] caaznkid:
Hello,

I was wondering which rom you guys could recommend for better than stock battery life? Seems like a lot of the roms are tweaked for smoothness and speed not battery life. Currently on d3rpICS but the battery life isn't so great...barely getting 8 hours with 1 hour on screen time. If anyone could point me in the right direction I'd appreciate it. Thanks!
[HTC EVO 3D] Jsparta26:
Meanrom ICS comes to mind. Your kernel can also play a role on battery life too. Overclocking will drain your battery, so will certain governors. Experiment around a lil bit to see what settings work for you.
[HTC EVO 3D] coal686:
How are you only getting 1 hour of screen on time? I suspect something else is the issue. Are you in an area with poor signal reception (that is usually my worst battery drainer)? Or maybe you have a runaway app. I recommend that you download Better Battery Stats XDA to monitor what apps are eating your battery.

Maybe you could try a fresh install of the ROM, but leave off the extra apps and see how it runs.
[HTC EVO 3D] caaznkid:
No I'm not in an area with poor reception...and the ROM was a clean install I haven't even put anything back on. I'll give meanrom a try and see how that goes. Thank you.
[HTC EVO 3D] meangreenie:
Coolexe's kernel UV's the screen, i'm getting 4+ hours scraping 5 hours+ on screen tme :) ... note not using 3g, i find 3g canes my battery.

tips.. stop the media service in running apps 'the one that often gets stuck restarting' .. mediadbmservice or something, i can't find anything that doesn't work after disabling

running 1188 -ondemand, cpu1 not forced always on and gpu3d/2d/266/200 using 'kernel tuner' and a small undervolt.. all 1xxx up to 1188 frequencies set at 1.0

I also stop apps that i don't need after their use, including 'kernel tuner', I know your not supposed to but i haven't seen any ill effect so far.
[Samsung Galaxy Nexus] Koki1337:
I already tried changing the sound by putting in the "TW_Touch.ogg" and "S_HW_Touch.ogg" but it doesn't seem to register at all

The reason why I'm changing is because the "cik cik cik" sound on certain custom ROMs are hell lot more annoying and I'd prefer the stock "pop" sound for the touch sound.

Anyone would shed some light on how to do this?
[Samsung Galaxy Nexus] Lesicnik1:
Probably a certain .ogg file inside /system/media/audio/ui
[Samsung Galaxy Nexus] Koki1337:
I tried listening to them all to see which is to be replaced, no luck
[Samsung Galaxy Nexus] Lesicnik1:
Did some testing on my own, Effect_Tick.ogg seems to be the one you need to change.
[Samsung Galaxy Nexus] Koki1337:
Wow, how could I miss that? But after replacing and rebooting (checked the name numerous times) it doesn't seem to work.

When I navigated to /system/media/ui/audio it doesn't play the Effect_Tick.ogg I wonder why
[Samsung Galaxy Nexus] Petrovski80:
How did you replace it? And with what?
[Samsung Galaxy Nexus] Koki1337:
Replaced with ES File Manager, got the Effect_Tick.ogg from another ROM
[Samsung Galaxy Nexus] ÜBER™:
Lol TW stands for Touchwiz which we don't have.
[Samsung Galaxy Nexus] Koki1337:
I don't get how I can replace the screen lock and unlock sound but not this Effect_Tick.ogg
[Samsung Galaxy Nexus] galaxy16:
this is what i always do.. i download the sound i liked i convert to ogg format then i rename to Effect_tick.ogg then i used root explorer copy the file that you just converted go to system/media/ui and paste.. if its still same untick the sound from setting or reboot phone..

ps dont forget to make it r/w
[Samsung Galaxy Nexus] Koki1337:
Yeah I did exactly that, not working even though I replaced. Lock/unlock sound had no problems
[Samsung Galaxy Nexus] frippad:
Make sure you change the permissions of the ogg file to match those of other system files.

Did manage to change the click sound a while back using the same method.
[Samsung Galaxy Nexus] Koki1337:
WOW you fixed my problem! I love you!
[Samsung Galaxy Nexus] Xeeroz:
I don't understand how to do this with cm10.1
[Samsung Galaxy Nexus] cmoG530:
Could you upload the alternative sound please?:)
[Nexus 7 Q&A, Help & Troubleshooting] freemanlowell:
Hi,

I've recently built 4.1.1 JRO03R and just now 4.1.2 JZO54K for the Nexus 7, from pure AOSP Google source and the five binary drivers for the grouper. I've followed the standard Google instructions as well as hints on this thread.

Both builds work almost perfectly, the screen, wifi, bluetooth etc. all function and the builds are both fast and stable, but both builds seem to lack other camera and sensor capability. There's no rotation sensor function, compass is not working etc. When you open a camera app (one that works in stock builds) you get "can't connect to camera". It's a real shame as otherwise the builds are great.

I've also built Cyanogen mod from source (JRO03R branch) and that had exactly the same problems - no rotation sensor, no compass, no camera and so on.

Does anyone know if there's another binary I'm missing, that controls such things as compass etc.? Or perhaps there's a step in the build process I've missed? The Invensense driver seems to be the orientation driver, is there a chance I've broken that? I've re-downloaded and re-extracted it several times.

Importantly, when I flash back to a stock Google ROM all the sensors function correctly on my Nexus 7, so I don't think it's hardware-related. I've also just tried AOKP build 4 (JRO03R again) and all the sensors work there - Camera, Accelerometer, Light, Orientation, Gyroscope and Magnetic Field and none of those work in my builds.

Any thoughts welcomed! :D
[Nexus 7 Q&A, Help & Troubleshooting] jamesst20:
Hi,

You have to take some missing libs from the Stock Firmware to get it to work ;) (or take them from another working rom)
[Nexus 7 Q&A, Help & Troubleshooting] freemanlowell:
You're not wrong. In the CyanogenMod build process this morning I did an extract-files command that pulled the libs for the sensors and camera etc. from my Nexus 7 (at the time running AOKP build 4). When I rebuilt using the extracted libraries + the downloaded binaries, the resulting CyanogenMod built on AOSP 4.1.2 works really well, including all the missing sensors. Hooray, working CyanogenMod, right?

What I can't figure out is how to do that same extract files step on pure AOSP 4.1.2. I've tried copying over the "vendor" directory from my working Cyanogen mod source tree, but that combination won't build.

So I think you're right. I need to extract some libraries and binaries from a working Nexus 7 build into my AOSP source tree, but in a way that works for vanilla Android rather than Cyanogen. Or make the Invensense driver package work correctly, as it's this one that seems to cause the problems as the other binary packages seemed to work okay.

I'm still really pleased to have a working 4.1.2-based Cyanogen 10 that I built myself though, it's great! :D
[Nexus 7 Q&A, Help & Troubleshooting] cbdonohue:
I'm having a similar issue with my AOSP JB build for Nexus 7. It seems like all the other drivers and sensor are working except for the orientation. Flashing the factory image and everything works fine :(
[Nexus 7 Q&A, Help & Troubleshooting] simms22:
from google groups android building..
[Nexus 7 Q&A, Help & Troubleshooting] cbdonohue:
Thanks.

However, this makes me sad.

---------- Post added at 03:40 PM ---------- Previous post was at 03:36 PM ----------

What's the orientation driver listed on the binaries page for then?
[Nexus 7 Q&A, Help & Troubleshooting] simms22:
those are the proprietary binaries(for personal use, not for distribution ;) )
[Nexus 7 Q&A, Help & Troubleshooting] cbdonohue:
Can you post the extra files you extracted for the orientation sensor to work?
[Nexus 7 Q&A, Help & Troubleshooting] freemanlowell:
Well, I never succeeded in getting the sensors working on my AOSP build even after extracting all the binary drivers from Google including the Invensense driver which seems to cause all the problems. But I did get it all working on CyanogenMod 10 using these instructions. Once the files were pulled into the CyanogenMod source tree from my N7, the build worked fine with lunch and brunch and I've been using that build for several days with 100% working hardware and sensors.

XDA senior member AndroidUser00110001 has posted his AOSP 4.1.2 build though, with the new binary drivers, so it must be possible to do all this with AOSP as well as CyanogenMod, I just haven't figured out how yet.
[Nexus 7 Q&A, Help & Troubleshooting] cbdonohue:
I copied the vendor/asus/grouper/device-partial.mk and vendor/asus/grouper/proprietary directory from CM10 for Nexus 7 into my AOSP build and rotate works now
[Nexus 7 Q&A, Help & Troubleshooting] freemanlowell:
Really? Nice work, that's awesome. I did that too but must have broken something in so doing. I'll try again now, thanks for posting. :cyclops:

Do the other sensors like compass and camera work as well?
[Nexus 7 Q&A, Help & Troubleshooting] cbdonohue:
Compass and camera work :)
[Nexus 7 Q&A, Help & Troubleshooting] freemanlowell:
Nice! I'm going to try this later today once I've done a CyanogenMod build for my TF101. Fingers crossed, thanks for the tips. :good:
[Nexus 7 Q&A, Help & Troubleshooting] cbdonohue:
Something is still weird tho.

I added launcher.force_enable_rotation=true to device/asus/grouper/device.mk so it is put in the build.prop allowing launcher rotation, but it only rotates the lock screen and not the launcher.
[Galaxy Tab 7.7 General] neimovirne:
Google today released update for nexus 7 Build Android 4.1.2. Added landscape mode..

Source code in AOSP.
[Galaxy Tab 7.7 General] marwanxx:
Hoping this version of Android will be on the 7.7. :)
[Galaxy Tab 7.7 General] sos_sifou:
haha i don't think so ^_^

best regards

Sifou

Galaxy Tab 7.7
[Galaxy Tab 7.7 General] marwanxx:
Nothing is imposible.
[Galaxy Tab 7.7 General] deani77:
It already merged by CM and you will get it on PA 2.18
[Galaxy Tab 7.7 General] sos_sifou:
yeah, i get a number (4.1.2 instead of 4.0.4) what's the big deal?

best regards

Sifou

Galaxy Tab 7.7
[Galaxy Tab 7.7 General] albert.mob:
not only number is changed. I'm using custom Paranoid ROM on my Galaxy tab 7.7. It has better performance and looks nicer ) User interface veery smoth
[Galaxy Tab 7.7 General] sos_sifou:
well, i must admit that the software experience improved a lot (its a huge improvement) from honeycomb to ics.

i dont think that it will be the same from ics to JB, or the 4.1.2

best regards

Sifou

Galaxy Tab 7.7
[Galaxy Tab 7.7 General] KuraKuraBesi:
If 7.7 doesn't get the JB update from Samsung I will sell my tab and gets an Ipad.:victory:
[Galaxy Tab 7.7 General] dr.fiazsadiq:
how to install this rom ?

hello, would you like to tell me please how did you installed this rom on tab 7.7 ? all whay i know is after installing this rom or other roms you will not get calls and bluetooth and wifi issues ... gps will not work anymore.. then what s the use behind ?
[Galaxy Tab 7.7 General] skeeterpro:
Well, FWIW ICS to JB (4.1.2 or 4.2.2) on my other tabs makes a marked improvement in the overall speed and fluidity of the tabs. Whether or not the same will hold true when (or if) the 7.7 gets stock 4.1.2 or 4.2.2 remains to be seen.
[Galaxy Tab 7.7 General] JAYZE:
is there anyone of you that still uses stock firmware like me? tried PA but have to revert back to stock ics despite the brick bug danger
[Galaxy Tab 7.7 General] ascariss:
If you mean stock as in from samsung, yes, I have it on my tab but I am using a different launcher though to speed things up.
[Galaxy Tab 7.7 General] JAYZE:
me too..using nova launcher instead of the ugly touchwiz..i can live without the bells and whistles of PA because stock is stable
[Galaxy Tab 7.7 General] skeeterpro:
The "BrickBug" has had me spooked also. But, after reading as much as I could from other sources, flashing CWM alleviates that issue. That said I still would shy away from Factory Reset from ICS nevertheless. Or proceed with caution.

Granted I could be wrong but am always on the lookout for a definitive "fix".
[Galaxy Tab 7.7 General] JAYZE:
so true..but i still encountered some soft bricks randomly when many apps were installed..for instance when i used the offline feature of Google Currents..my tab won't flash via odin so i have to reset using cwm many times..

do you think the new jelly bean firmware is free from brick bug?
[Galaxy Tab 7.7 General] skeeterpro:
One hopes so. But I'll always include CWM/kernel substitution. I'll deal with soft brick any day of the week compared to hard brick. Even jtag has failed for some.
[Galaxy Tab 7.7 General] feenty:
+1

Stock + nova here... This is good enough for me.

Im waiting for the JB update too, but i can live without it.
[Galaxy Tab 7.7 General] skeeterpro:
Pretty close to the same here. Am under the distinct impression that rooting and using CWM also offers as much "protection" from brickbug as can be had at the moment. Running LQ1 right now but was considering flashing LQ2. Looking for a bit better battery.

Been following daniel_hk in the Android section. His work on the JB CM10.1 looks very very promising! Check it out!