I used ES File Explorer.
I need some help guys.
On your internal and external sd cards there is a folder named logger which contains log files.
I may ask you to zip those files and PM me a link (Dropbox, whatever). But don't do that yet.
I need you to help me analyze those files to make sure there is no personal or location based information. I will be doing the same.
Just open the files as a text document and look for stuff like IMEI, GPS cooridnates, etc.
AndroZip https://play.google.com/store/apps/details?id=com.agilesoftresource
The unzipped text file is big. Use html viewer for fast performance.
The most personal info I see is the name of the carrier. "AT&T" Have not seen any other identifiers.
Sent from my MB860 using Tapatalk 2
Should check only on ICSROM or "that ICS rom"?. I'll flash ICSROM right away and report back the findings.I need some help guys.
On your internal and external sd cards there is a folder named logger which contains log files.
I may ask you to zip those files and PM me a link (Dropbox, whatever). But don't do that yet.
I need you to help me analyze those files to make sure there is no personal or location based information. I will be doing the same.
Just open the files as a text document and look for stuff like IMEI, GPS cooridnates, etc.
Not sure if this means anything, but on the original ICS leak for the atrix 2 some phones were running at 1.2ghz after installing their leak while others with the exact phone were still running at 1.0ghz (stock speed for that phone). Exact same phones, exact same file flashed. Nobody knows for sure but the speculation is that somehow the update from that leak checks for cpus from different batches and then selectively overclocks them according to whether they were from a "good" batch or not.
Maybe moto applied some of the same voodoo here with the atrix 4g leak?
Fastrite can you confirm you managed to get the screen stabilized the same way as I do ? People are asking for confirmation. It is funny on my 46 inch bravia picture is rock solid. I guess if I was a developer I wouldn't want to work on 4 inch ider
AT&T Atrix 4G, with tegrapart=mbr:1100:100:800
Aside from little slugginess issues that come and go, and obscene battery usage compared to CM10, this ROM is VERY good. After abandoning other Blur- based ROMs and using ICS and JB-based ROMs, i had no idea HW acceleration made things way better. Only thing i have "modded" is the DPI, from 240 to 220, via build.prop. Works like a charm.
Only thing i have disliked of AOSP ROMs is the boot-up logo, but that's up to me to change it
Will be trying it next week as a daily driver. I could've tried it last week, but needed a stable phone and lots of battery.
I have found my phone is not deep-sleeping, rather it is underclocking to 216 MHz with screen off. Is there any way to enable deep sleep? I have BT off and WiFi always on, but no notifications at all.
Same, mine doesn't deep sleep either. Do you experience loads of reboots too?
Also, HW acceleration really makes this phone seem new. Everything feels sturdy and not flimsy like in other roms where scrolling would hang for a while etc
Same, mine doesn't deep sleep either. Do you experience loads of reboots too?
Also, HW acceleration really makes this phone seem new. Everything feels sturdy and not flimsy like in other roms where scrolling would hang for a while etc
AT&T Atrix 4G, with tegrapart=mbr:1100:100:800
Aside from little slugginess issues that come and go, and obscene battery usage compared to CM10, this ROM is VERY good. After abandoning other Blur- based ROMs and using ICS and JB-based ROMs, i had no idea HW acceleration made things way better. Works like a charm.
Modifications done to build.prop:
- ro.build.type=userdebug > ro.build.type=user (made it slightly smoother)
- ro.sf.lcd_density=240 > ro.sf.lcd_density=220 (made stuff smaller)
- ro.mot.deep.sleep.supported=true > ro.mot.deep.sleep.supported = false (enabled deep sleep)
- ro.mot.toggle.hotspot=true > ro.mot.toggle.hotspot=false (do NOT mistake with ro.mot.wifi.hotspot=1, doing so will make the phone go into boot crashes)
- ro.mot.btpan.disable=true > ro.mot.btpan.disable=false
- ro.mot.btdun.disable=true > ro.mot.btdun.disable=false
#ADDITIONAL BUILD PROPERTIES
- ro.camcorder.videoModes=false > ro.camcorder.videoModes=true (got rid of a bit of camcorder's lag)
- debug.mot.hprofdump=1 > debug.mot.hprofdump=0
Only thing i have disliked of AOSP ROMs is the boot-up logo, but that's up to me to change it
Will be trying it next week as a daily driver. I could've tried it last week, but needed a stable phone and lots of battery.