yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamesRF:
This ROM works great. Thank you for the 2-25 update, the previous one caused freezing once the display shut off with just a line showing as other users reported as well(thought I was the only one).

In the power menu, was reboot options like recovery, download taken out intentionally or is it just me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Re: [ROM] MROM-d2att [4.2.2][CM10.1][3.0.66] build:20130225 *** NEW VERSION ***

No problem, hope everything works great for you. Strange about the menu, on order to make reappear, go to settings about phone, push 7 times the build number (just in case that was not done already), then under developer option, push advanced menu... that should take care of it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamesRF:
Yup that worked fine. The 2-16 version had the reboot options, but it went away once updated to 2-25. Not really a big deal, but thank you for that fix. This ROM is awesome and a great daily driver, very smooth and quick...still 1.2GB free RAM. More people should try this one it is like the Atrix one you made :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jburks725:
Thanks. I have a good nandroid that is my fallback. I'm quite familiar with the process. I was not saying I don't want to, or know how to, test this ROM. I was simply telling the maintainer that I wouldn't be able to test it this week because of work. I had had a previous exchange with him on this thread about testing the capacitive button fix in 2/23 build, and noted that I got the CRT-off animation freeze, which he also got the next morning. I told him I'd test his next build when it came out. Now I can't, at least not until Monday, so I thought I'd let him know I hadn't abandoned him. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigmike34:
As far as CM10.1 roms go, this has been the most stable, smooth, battery efficient rom i've tried yet. Only Liquidillusion (still my favorite) and Carbon compare. Hate the theme but obviously that's as quick a fix as there is. I have a soft spot for PA and the other feature rich roms out there but I do "see the difference" alluded to in the OP.

Just wanted to leave some love for this underrated rom.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamesRF:
I am not sure if this is a ROM specific problem or a 4.2.2 issue, but has anyone noticed that ringtones/notification sounds seem to be quieter? I downloaded the stock S3 ringtones and notification sounds and the "samsung whistle" sound seems to be a lot softer then it was when the phone was stock. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LSUtigers03:
I tried flashing this rom today and the phone wouldn't go past the boot screen. I know the first boot takes longer but I waited 10-15 minutes and I never got past the boot screen. I'm coming from the stock rom so I wipe system and cache. Also I'm using twrp. Has anyone had issues with this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
This could be the result of an incorrect install procedure. Please make sure to follow all the steps. Including wiping data...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ghost__:
Which gapps would you recommend installing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
New Version Posted!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
There is a new version of gapps posted. 0301. I would recommend that version...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] terrymc:
Re: [ROM] MROM-d2att [4.2.2][CM10.1][3.0.68] build:20130309 ***NEW VERSION***

Awesome ROM , one thing I have seen on another ROM that would be cool is to remove the text limit for mass texting. Where they also failed is to be able to select a "group " rather than having to select each person individually. I currently use handcent but it would be cool to have same functionality from stock SMS app. Again thanks for this ROM I love it!:o
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Re: [ROM] MROM-d2att [4.2.2][CM10.1][3.0.68] build:20130309

Will initiate a new build process soon. Any suggestions of things to add before I begin?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aodhan:
The orange is super distracting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dannieloco:
add this if you can :)

http://xdaforums.com/showthread.php?t=1950443&highlight=group
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Longer battery life, lol. Just kidding.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Do I have to put naked girls on the thread to get some attention?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] warri:
I'll check it out.. Though I suggest you keep a date in your title will help people know when releases are :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
I appreciate the response, but the date is currently in the title, is it maybe in a format that it's not easily seen?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] warri:
You are right my mistake.. On tapatalk I couldn't see the end of the title my apologies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] OSNPA:
I heard there would be naked girls? I am gonna try this my Atrix brethren. Looks like a well-featured ROM :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Spurtle:
No you just need to add a few bugs to the ROM. If no one is posting it's only because they are not having any problems.

This runs buttery smooth with great battery life.

Of course I'm not opposed to your idea though. :thumbup:

Sent from my GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jacqstrap:
Great ROM! It's really simple and clean.

Few questions though. I started my day around 7:00 AM at 100 percent and as of now it's 6:30 PM and I'm at 40 percent. My use has been very minimal only in that i check twitter and Instagram every few hours. Is that bad?

Oh, and is there a reason why developer options is not available?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
It's this your first day with the Rom?

Regarding the developer options, you have to push the build id 7 times in phone settings...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markysd:
love the rom but been getting the same issues on 4.2.. not stable wifi when bluetooth is connected drops to data network and lose of data.. going back to 4.1 ill be back when that is fixed:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Interesting, no one has reported that up to now, will look into it... I don't use Bluetooth, would help if you could provide a logcat while the issue occurs...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Do we have any mirrors?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
No mirrors yet... what is the problem?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Slow speed, 1mb in 10 minutes. Will wait until things improve with dev-host
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
I am open to suggestions for alternative high speed mirrors...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Goo.im can be good alternative
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andy55:
I'm having issues installing this rom using twrp. I've downloaded it twice with same error, says package error unable to install. No issues with any other rom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jacqstrap:
A suggestion I have is to include the "power off" option for the hardware keys. I find that option very useful
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Spurtle:
Anyone else have an issue with the advanced reboot menu not appearing? I have activated the developer options and selected it and I have the reboot menu option checked off in power menu but my only option is reboot. It does not give me the reboot to recovery option. :confused:

Sent from my GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
I just double checked and the option works, after selecting it and long pressing the power button, select Reboot and the different options, Reboot, Recovery, and Download mode should appear. If it does not appear, reboot in recovery by pressing power vol-up and home at the same time, and select fix permissions, this should take care of it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
FAQ

Built a new FAQ, please help me keeping it up to date... suggestions are always welcomed!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Spurtle:
Fixing permissions did the trick.

Sent from my GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamesRF:
I've noticed this glitch in every build since February. Google voice crashes when I try to open it, both in text messages or on the Google search bar...it says "unfortunately, voice has crashed". Is Google voice not installed on this ROM? If so, how can I get it installed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Strange because I use Google voice. What is the actual error in logcat?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamesRF:
Ok I attached a logcat hopefully it's enough info for you. If I try to do a Google search from the search bar and press the microphone it crashes, OR if I try to open Voice in a message. I then have to go to settings-input-and uncheck Google Voice to be able to type again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Which keyboard do you use? Seams related to input settings and auto-correction...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamesRF:
I use the default keyboard include in your ROM ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Did some research, seams to be related to Google Quick Search Box application. It should be in 2 places:

/system/app/QuickSearchBox.apk

and

/data/app/com.google.android.googlequicksearchbox-2.apk (the 2 I am not sure, it might change)

Please verify that you have the apps. If not, install it from market.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JamesRF:
I have the app installed I guess from the ROM but the version wasn't compatible. Once I updated it through Google Play it works perfectly! You sir, are the man! Thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
I am only as good as the users who give me a chance to help them. Without your time and support, I would not have been able to help...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
Great ROM

I installed this last night and I must say I am impressed. I am an end user not a developer, but this does seem like a very solid ROM and I do love the theme. I have used my phone heavily in the last three hours since with a half an hour of screen time and almost an hour and a half with blue tooth voice calls and I am only down to 78% battery. Very Nice keep up the great work!!! All subjective opinions but thought I would pass along the feedback!!

---------- Post added at 12:56 PM ---------- Previous post was at 12:55 PM ----------

It helps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toxictaru:
Not sure why, but I've downloaded and flashed the update, it still says I'm running the last March version of MROM. I redownloaded it, flashed again, same thing. I can't assume that is standard fare.

Edit: I flashed both of the files for the newest version, phone info still says its running the March compile, with the old kernel as well. Not sure.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Let me check the file and get back to you...

Edit: I verified the files and they are correct. Please describe the process of you downloading the files and update. Do you manipulate the build.prop file?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toxictaru:
I'm following the directions exactly. Nothing modified. The only thing I haven't done is a full clean flash (I hate the idea of restoring everything), so its been dirty flashes of both the update file and the normal one. Not really sure what's going on there, but clearly the dirty flashing isn't working properly. And in case it matters, I am using CWM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] countrylife:
been running good for the last 6 hours, haven't done the update yet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Could you post the screenshot of your about phone? Make sure to scroll all the way to the bottom before taking it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toxictaru:
And just to show I'm actually flashing in the new version and not an old one:

Obviously the About Phone screenshot shows that I am using the old version. This is despite having flashed in either of the files in the second shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
You are right, you are using the old version. Question for you, are you performing the update by rebooting in CWM manualy and selecting the file or using an automated update? Sometimes the automated CWM does not work properly...

This update has been installed by many users, I have queried them personally and everything is ok.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toxictaru:
Booting manually to CWM, updating, clearing cache, that fun stuff. I didn't even know there was an automatic method x.x

Edit: Not sure why, but I just tried it again, and it worked. No clue at all why it wasn't working before, but I guess it doesn't matter any more.

Thanks though!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Glad I can help...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tobesedated:
So I installed your ROM and it is very, VERY, cool...I'm big into being able to customize my phone so it'll be fun to see what I can do. I also registered to check out your experimental builds and I just want to double check that the mixer ROM IS NOT to be flashed over this one? I am assuming it is an entirely different ROM, is that correct?

Thanks for your help :)

(((EDIT))).I'm thinking that build isn't even for this phone lol...sorry
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jacqstrap:
I am having a really bad problem with battery life and I can't seem to find out what it is. I will really only be using my phone for 20 minutes from 100 percent and it will drop around 10 or so. Please help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Are you coming from a 3.0 kernel? if so, you might want to calibrate the battery. If not, try to use system tuner to record what's actually using the battery...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Thanks for using my rom. You are correct. The mixer-mrom is targeted for gingerbread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] robin48:
Stable as stable can be. Loving it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
Just tried the experimental build and my phone wouldn't reboot. Had to restore from a nandroid. Just wanted to let you know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
There no experimental builds available for d2att, what file did you flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] countrylife:
hats off to the developer for this rom, been beating on it all day and cant find nothing wrong with
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
That's weird...goo.im notified me of an update to my ROM. I assumed it was a build of this ROM. The file was

http://www.goo-inside.me/devs/cm/d2att/snapshot/cm-10.1-20130411-EXPERIMENTAL-d2att-M3.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
I believe that's the latest monthly build for cm10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
MROM does not publish on goo.im. But eventually will use the file store to distribute the binaries...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] _ND_:
top of screen sweep for brightness adjustment

Final Update : Reverting back to Liquid .. Have been rebooting every 15 mins :(

UPDATE: After flashing this rom, I installed a couple of Apps like whatsapp, swiftkey and nova launcher.. and the phone keeps rebooting.

I tried installing alogcat to capture. no luck .. its empty and I still keep getting these reboots. help ?

------------------

Just flashed this rom (clean) and I have been using Liquid / Task for quite some time now. So far, it looks very smooth and stable.

I have been trying to get the brightness control to work using the top of the screen sweep but have not been successful. Sorry if this has already been discuss (I tried searching but no luck).

I will keep a watch on the battery life, as that is one reason why I thought of coming here.

Awesome job so far MMontuori :good:

Cheers!

ND
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
This was in response to my an earlier comment about an experimental build. Forgot to quote.

I know that now. I did find it strange that goo.im would pop up a notification on my phone like that. No harm done and I am back on track.

Have had the ROM for a few days now. It is solid. I have had no issues whatsoever. Everything works that I have tried.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mail_venu:
Hi. How can I remove exchange security ... Is there any update apk to install email bypass exchange security
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lionhart_1912:
Hi everyone

I would like to know if some of the program that are in stock firmware also are present in this rom, one of those are the gestures for the screenshots and the second plane video playback... If anyone knows, please tell me

thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
I haven't had any of those issues. The ROM has been quite solid for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] _ND_:
such issues are quite context specific, which is why I was trying to see if I was doing something that I should not be doing. I came from Liquid 4.2.2 but I followed the installation process closely. I also installed fresh apps instead of restoring (except for whatsapp).. this is the first time it has happened since I started flashing roms months back. Anyway, I will give it a shot again in a few weeks

thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Please next time, provide logs for me to examine, instead of just run away. It really does not help anyone to come on this post and say "it does not work" or "it's rebooting".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] _ND_:
I do not want to drag this further, but I already stated earlier that I tried alogcat and it did not gather anything for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Drag further? I am just trying to help. Good luck to you...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Striker333:
Response to Lionheart

The gestures from the stock ROM aren't present, at least from what I have found. However this is a nice solid ROM from my experience. I am no expert but do not think you will find the "smart" gestures of TW on any aosp, aokp or cm based ROM. The fun is in the looking :).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toxictaru:
Is anyone else having issues with the battery and display?

I've been noticing some weirdness with my display from time to time, when I scroll the screen basically just gives me a bunch of horizontal scan lines. It basically looks like a TV with a really bad signal, or an LCD display that has had damage done to the connection. It sometimes spontaneously fixes itself, other times I have to FC the app, and other times I have to outright restart my phone to get rid of it. Nothing is free of it either, and happens on the lock screen from time to time. I've asked my brother who also uses the MROM if he is experiencing the same problems, and he has noticed it as well, so I don't believe it is an issue with my phone (and I've used other ROMs including stock and not had the issue).

Adding to this is my screen is using huge amounts of battery, which doesn't make much sense to me. I've attached some screenshots, showing that the screen is using huge amounts of my battery, but has had minimal "on" time. I've recalibrated the battery a few times. I suspect it COULD be a problem with the battery itself, but I've had this phone for no more than 8 months. I have experienced excellent battery time with MROM in the past, but in the past couple of weeks its been bad. I have a funny feeling that this could be related to the other problem mentioned. Display brightness is set to right around 50%.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toxictaru:
I managed to grab a picture of the display problems I mentioned. I took it with my N7 so it wasn't exactly the best shot, but you can see the problem I'm talking about.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Spurtle:
Actually mine has done the same thing to me a few times the last couple of days. It started after I fixed permissions to correct the reboot menu problem I was having. No crashes, just the fuzzy screen on occasion. It corrects itself when you touch the screen.

Sent from my GS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmontuori:
Thanks for posting this problem. I am looking into it... it would be helpful if you could provide dmesg and logcat it would be great...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] redstar299:
Hey is there a kill current application feature? On some of the other roms if you hold I down the back button it can kill the current application. I looked but I don't see it
[Kindle Fire Q&A, Help & Troubleshooting] dbalvo:
I'm new to the Kindle Fire flashing scene, and trying to get Jelly Bean on to my stock Kindle Fire. I've spent several hours on it so far, and haven't been able to get past the first step of getting KFU to see my Kindle Fire, so I can root it or do anything else. To be clear, this is a 1st gen Kindle Fire, running 6.3.1. I've never rooted or flashed it before, and it boots and works perfectly.

The main problem I seem to be having is that Device Manager (on my Win7 PC) shows the device as 'Android ADB Device.' It seems the expected description should be 'Android Composite ADB Device' but I can't get it there. Most of the posts and pages I've seen related to having trouble getting KFU to see a Kindle Fire focus on the drivers not being installed at all, which I don't think is my problem. And I've uninstalled/re-installed them at least 1/2 a dozen times with no effect.

The documentation would seem to suggest that seeing 'Android ADB Device' in the Device Manager implies my device is in Fastboot mode. However, when I uninstall the drivers I see 'Kindle' not 'kindle' in my device manager which suggests normal mode according to the 'Windows Device Drivers and the Device Manager' tutorial. This seems consistent with the fact that my device behaves perfectly normally, so I don't think it's actually in FB mode. Further, the FB tool can't see it.

I've tried connecting to the device from the command line using both the ADB (adb devices) and Fastboot (fastboot -i 0x1949 getvar product) tools. Neither one seems capable of connecting to the device. I also tried connecting the device on a second PC and there too I got 'Android ADB Device', suggesting the problem is device side. I don't have a factory cable to force FB mode that way.

I suspect I'm missing something obvious, but can't figure out what. Can anyone help me out?
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
It`s probably something strange I`m pretty good at working it out contact me tomorrow via Pm I would be happy to look at it for you. Check your user/.android folder for adb_usb.ini see if it has 0x1949 in it.
[Kindle Fire Q&A, Help & Troubleshooting] dbalvo:
Thanks, the adb_usb.ini has the 0x1949 line in it, so that's not the issue. My %userprofile% directory name has a space in it, which initially caused the install_drivers.bat that comes with KFU to have some issues (because it assumes it doesn't.) But everything is where it should be now. Look for my PM.
[Kindle Fire Q&A, Help & Troubleshooting] MRxxEGO:
Re: [Q] Can't get Stock Kindle Fire to show "Android Composite ADB Interface"

I had to used the drivers in superoneclick 2.3.3.
[Kindle Fire Q&A, Help & Troubleshooting] Thepooch:
This problem is solved he was running kfu from a temp directory.