[ROM]CM10 4.1.2 SuperLite for Atrix 4g! [Wifi Tether Fix + Fastboot, 28 Sep 2014]

[sendust7]

is this stable/reliable enough to be used as a daily ROM?

SuperLite's main strengths are: lightweight, fast, highly customizable and reasonably stable. I've been using SuperLite as my daily since launching this thread and have never had a random reboot.

A few things don't work, like wifi tether, Netflix video (a general CM10 issue), no haptic feedback for Menu, Home etc (keyboard is fine though). But I fully expected things like this to happen since I ported SuperLite across manufacturers.

Some users report bad battery life. This happened to me once or twice (even with display off), and I attribute this behavior to my phone attempting to bind to weak signals: cell network, wifi, bluetooth, and/or GPS. Generally speaking, battery life is significantly better in areas with good signal strength.

By invoking Airplane Mode during times of expected non-use, I can get 1.5 days of battery life (and that's a conservative figure) with plenty of reserve. Of course you could probably do just as well on other devices and ROMs using this strategy.

You could also do things like modify /system/build.prop to increase the wifi supplicant interval from the default 30 seconds to, say 180 seconds.

Hope this helps.

 

[DuaBeo35]

How to install finger.....

 

[sendust7]

How to install finger.....

If you mean "fingerprint sensor", I believe this is (or was) broken in JB due to lack of compatible drivers. See http://www.droiddog.com/android-blog/2012/08/android-4-1-jelly-bean-ported-to-original-atrix-4g/

See also: http://www.linuxmobile.org/atrix/atrix and http://www.linuxmobile.org/atrix/cm10-1

For fingerprint, you may wish to consider one of these ROMs, though I am not sure FP works on all of them:

NottachTrix 2.0 (ROM zip is very large --- almost 1GB)
NottachTrix 1.3.1 (older but smaller)
ICSROM (see also my other thread: Project Stable Boot for ICSROM)

Not sure about CM7. Look at Neutrino's CM7 as well.

Of course the main problem with ICS builds is the kernel; however that is being worked (intensely) by a number of dedicated personnel: mmontuori, krystianp, scott.hart.bti, et al.

 

[Fastrite]

Re: [ROM]CM10 4.1.2 SuperLite for Atrix 4g! [New! Addons Flashable Zip, 16 Mar 2013]

Not sure about CM7. Look at Neutrino's CM7 as well.

FP unlock works on CM7.2 but I find its implementation a bit strange.

"It's not the fall that kills you, It's the sudden stop at the bottom"

 

[zip103]

Nice ROM, but

When I say to google voice "call john brown", it rarely gets it. The same names that are successful selected without an hitch, on epinters CM10 ROM.

 

[Dark Stranger]

The ringtones are working on this rom? When receiving a call the ringtone chosen rings or vibrates the device only?

 

[singreale]

The ringtones are working on this rom? When receiving a call the ringtone chosen rings or vibrates the device only?

The ringtones all seem to work for me.

However, one application (Talkatone) that I use for making international phone calls keeps crashing (no FC and no error messages). I'm wondering if this is an error in eprinter's rom or if a necessary library or resource was removed for SuperLite. Other than that, love the rom, great to have a spiritual successor to Neutrino.

 

[scottharris4]

When I go to sideload an app, I can't click install. I can click cancel, but not install.

 

[scottharris4]

NEvermind, I figured it out. AN app I downloaded was the issue.

 

[dontremember]

symlink: some symlinks failed

Booted ClockworkMod Recovery v5.8.1.8. Full wipe/factory reset, followed by wipe Dalvik cache. Started installing SuperLite. I get:

Formatting /system partition...
Mounting /system partition and extracting files...
symlink: some symlinks failed
E:Error in /sdcard/ROMS/SuperLite/SuperLite_CM10_V8_83MB.zip
(Status 7)
Installation aborted.

This is from a working microSD card with a pile of other stuff on it. I'm going to try it again from an empty, freshly formatted microSD and see if that makes a difference.

I just tried "unzip -t SuperLite_CM10_V8_83MB.zip" and I get "No errors detected"

Any ideas??

 

[dontremember]

Booted ClockworkMod Recovery v5.8.1.8. Full wipe/factory reset, followed by wipe Dalvik cache. Started installing SuperLite. I get:

Formatting /system partition...
Mounting /system partition and extracting files...
symlink: some symlinks failed
E:Error in /sdcard/ROMS/SuperLite/SuperLite_CM10_V8_83MB.zip
(Status 7)
Installation aborted.

This is from a working microSD card with a pile of other stuff on it. I'm going to try it again from an empty, freshly formatted microSD and see if that makes a difference.

I just tried "unzip -t SuperLite_CM10_V8_83MB.zip" and I get "No errors detected"

Any ideas??

OK, never mind - I think my Atrix is having issues with Sandisk's Class 10 Ultra. Everything installs just fine from a different microSD card.

 

[aaurnab]

I can't sign in google account but there is network enabled and can access browser...i saw in previous roms if there is internet then the network bar will seems to blue...But here is absent.

Edit: now I able to sign in Google account by correct flash method. ROM>reboot>Addons.

 

[sendust7]

I can't sign in google account but there is network enabled and can access browser...i saw in previous roms if there is internet then the network bar will seems to blue...But here is absent.

I sometimes have problems setting up Google Play via phone network (signal strength is weak), but not wifi.

If your wifi works, is on, and has access to Internet (instead of just the router), the wifi symbol at top right of home screen should be fan-shaped, where signal strength is represented by blue* bars displayed starting from bottom of the fan.

*Here is some related documentation: http://android.stackexchange.com/qu...ctivity-icons-in-the-status-bar-go-white-gray

"Network status icons turn green if you have a Google Account added to your phone and the phone is connected to Google services, for syncing your Gmail, Calendar events, contacts, for backing up your settings, and so on. If you don’t have a Google Account or if, for example, you’re connected to a Wi-Fi network that is not connected to the Internet, the network icons are white."

I think that for JB ROMs (like SuperLite), the wifi icon turns from blue to gray if your phone cannot access Google servers.

Hope this helps...

 

[aaurnab]

I sometimes have problems setting up Google Play via phone network (signal strength is weak), but not wifi.

If your wifi works, is on, and has access to Internet (instead of just the router), the wifi symbol at top right of home screen should be fan-shaped, where signal strength is represented by blue* bars displayed starting from bottom of the fan.

*Here is some related documentation: http://android.stackexchange.com/qu...ctivity-icons-in-the-status-bar-go-white-gray

"Network status icons turn green if you have a Google Account added to your phone and the phone is connected to Google services, for syncing your Gmail, Calendar events, contacts, for backing up your settings, and so on. If you don’t have a Google Account or if, for example, you’re connected to a Wi-Fi network that is not connected to the Internet, the network icons are white."

I think that for JB ROMs (like SuperLite), the wifi icon turns from blue to gray if your phone cannot access Google servers.

Hope this helps...

all that problem solved by several times delete APN and insert APN but now i am facing google play store download...this sometimes 927 or 921 error... strange..... your development is so nice so i like to stay here...

 

[sendust7]

all that problem solved by several times delete APN and insert APN but now i am facing google play store download...this sometimes 927 or 921 error... strange..... your development is so nice so i like to stay here...

It seems you are close to solving the problem. Are you downloading Google Play via wifi? Because...http://support.google.com/googleplay/bin/answer.py?hl=en&answer=2740059

"We've received reports that users in Australia are having trouble with all downloads over the carrier network, receiving either error 927 or 495. We're aware of this issue, and we're currently investigating. At this time, there are no workarounds available - we recommend using a WiFi connection for downloads temporarily. We’ll continue to update this page with developments, so check back soon." --- updated Feb 2013

Also this OP, which addresses Error 921, may also help you solve: http://forum.xda-developers.com/showthread.php?t=1594135

[UPDATE, 1130 PST}: It may be as simple as selecting Airplane mode (disables phone network transmission). Then turn WiFi back on (while in Airplane mode) and try downloading Google Play.

 

[sendust7]

SuperLite NFC (Near Field Communication) and Battery Life

Are you experiencing unusually short battery life on SuperLite? It turns out that I retained a feature from the Galaxy S2 called NFC or “Near Field Communication”…
http://developer.android.com/guide/topics/connectivity/nfc/index.html

“Near Field Communication (NFC) is a set of short-range wireless technologies, typically requiring a distance of 4cm or less to initiate a connection. NFC allows you to share small payloads of data between an NFC tag and an Android-powered device, or between two Android-powered devices.”

NFC is a two-edged sword, though big plans are in the works according to this 13-page blog devoted entirely to NFC: http://www.near-field-communication.us/nfc-pro-con.html

“She took out the phone … and I thought she was going to take a picture with it. Instead, she held the thing up to the poster like she was trying to get better reception and in a second she was watching the trailer for the show…”

However because SuperLite’s NFC (/system/app/NFC.apk) is not native to Atrix, I wasn’t quite sure what to expect by keeping it on board. But I found out soon enough… After installing Boot-Time Auto-SuperLog: http://forum.xda-developers.com/showthread.php?t=2232502 my logs began to reveal a correlation between SuperLite’s NFC app and battery drain. Anytime your device tries to bind with another device, it can drain the life right out of your battery at a dizzying rate.

My log buffers were stacking up like crazy...

​

I reckoned something was amiss, so I opened the dmesg/logcat files and discovered that NFC was making numerous attempts to bind. And my NFC ON/OFF switch located in Settings > More… > NFC seemed inoperable as there was no feedback in the checkbox. So without logcat and/or dmesg, I could not readily tell what NFC was doing.

Even if NFC did work on Atrix, security issues come to mind: If we lose our phone, our personal information could be compromised --- though I am confident experienced Linux hackers would find other means. And I personally don’t need NFC since other (possibly more capable) wifi apps are available to fill the void (see below: Some Alternatives to NFC). So I disabled it on my Atrix using Root Explorer, which is very easy to do:

1. Navigate to /system/app and tap on "Mount R/W" near top right
2. Long press on NFC.apk and rename to NFC.apk.bak
3. Remount /system/app as read-only​

​

And...voila, without even needing a reboot, my Atrix immediately calmed down to the point of actually getting cold -- even with wifi on. And Bluetooth still worked.

And battery life was much improved (with good wifi signal).​

Some Alternatives to NFC

For scanning barcodes and related things, there are several apps available e.g. https://play.google.com/store/apps/details?id=me.scan.android.client&hl=en

For file transfer, we could use FTP. There are several variants of FTP server on Google Play, but I keep coming back to this one, which seems to have good security: https://play.google.com/store/apps/details?id=lutey.FTPServer&hl=en

On the client (computer) side, I use FileZilla (free): https://filezilla-project.org/

Or if the client is another Android device, we could try AndFPT: https://play.google.com/store/apps/details?id=lysesoft.andftp&hl=en

These server/client configurations yield a GUI-based wireless file transfer protocol with adjustable security levels. These may actually be more secure than NFC...

Anyway, I thought it would be good to pass this info along. My next version of SuperLite for Atrix will address NFC issues.

References

http://www.ghacks.net/2012/10/16/tu...hone-to-save-battery-and-make-it-more-secure/
http://www.examiner.com/article/nfc-is-a-battery-problem-to-be-solved
http://forum.xda-developers.com/showthread.php?t=1870689

 

[dontremember]

/snip/ ... So I disabled it on my Atrix using Root Explorer, which is very easy to do:

1. Navigate to /system/app and tap on "Mount R/W" near top right
2. Long press on NFC.apk and rename to NFC.apk.bak
3. Remount /system/app as read-only​

I don't have root explorer, but command-line works well:

adb shell
mount -o remount,rw /system
mv /system/app/Nfc.apk /system/app/Nfc.apk.bak
mount -o remount,ro /system

 

[sendust7]

I don't have root explorer, but command-line works well:

adb shell
mount -o remount,rw /system
mv /system/app/Nfc.apk /system/app/Nfc.apk.bak
mount -o remount,ro /system

That is interesting... Do you have "ro.secure" set to 0? Because if it's set to 1 (the default for SuperLite), I have to first get root (su)...

C:\Program Files\Android\android-sdk\platform-tools>adb shell
[email protected]:/ $ mount -o remount, rw /system
mount -o remount, rw /system
mount: Operation not permitted
255|[email protected]:/ $ su
su
[email protected]:/ # mount -o remount, rw /system
mount -o remount, rw /system
[email protected]:/ #

[email protected]:/ # getprop ro.secure
getprop ro.secure
1
[email protected]:/ #

ro.secure is set in boot image ramdisk/default.prop ...

 

[dontremember]

That is interesting... Do you have "ro.secure" set to 0? Because if it's set to 1 (the default for SuperLite), I have to first get root (su)...



ro.secure is set in boot image ramdisk/default.prop ...

I have ro.secure=0. I haven't changed anything, as far as I know. This is installed from SuperLite_CM10_V8_83MB.zip

md5sum SuperLite_CM10_V8_83MB.zip
0d3ee5935fb1a697cbaf1b7f4c998f61  SuperLite_CM10_V8_83MB.zip

md5sum boot.img 
badbee8eebccd9965093b888a3caaa31  boot.img

/default.prop looks like this:

[email protected]:/ # ls -l /default.prop                                           
-rwxr-xr-x audio    513           183 2013-02-28 23:35 default.prop

[email protected]:/ # cat /default.prop                                            
#
# ADDITIONAL_DEFAULT_PROPERTIES
#

# sendust7 (27 Feb 2013)

#ro.secure=1
ro.secure=0

# sendust7 (27 Feb 2013)

ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb

 

[sendust7]

I have ro.secure=0. I haven't changed anything, as far as I know. This is installed from SuperLite_CM10_V8_83MB.zip

Thanks very much. I retraced my steps and remembered that I am dual booting epinter's CM10 on SD. When I switched back to SuperLite, I flashed epinter's boot image which (I believe) sets ro.secure=1.

So it looks like I went slightly off-axis from the CM10 mainstream by setting ro.secure=0 in SuperLite . But I figured if my phone is rooted, I might as well take full advantage

SuperLite boot.img ramdisk/default.prop...

#
# ADDITIONAL_DEFAULT_PROPERTIES
#

# sendust7 (27 Feb 2013)

#ro.secure=1
ro.secure=0

# sendust7 (27 Feb 2013)

ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb

Thanks again.

[EDIT 1020 PST]: For everyone's benefit, here's a good article on rooting: http://cjix.info/blog/misc/how-rooting-works-a-technical-explanation-of-the-android-rooting-process/

ADB (see the official documentation for ADB) allows a PC or a Mac to connect to an Android device and perform certain operations. One such operation is to launch a simple shell on the device, using the command adb shell. The real question is what user do the commands executed by that shell process run as. It turns out that it depends on the value of an Android system property, named ro.secure. (You can view the value of this property by typing getprop ro.secure either through an ADB shell or on a terminal emulator on the device.) If ro.secure=0, an ADB shell will run commands as the root user on the device. But if ro.secure=1, an ADB shell will run commands as an unprivileged user on the device. Guess what ro.secure is set to 1 on almost every stock OEM Android build. But can we change the value of ro.secure on a system? The answer is no, as implied by the ro in the name of the property. The value of this property is set at boot time from the default.prop file in the root directory. The contents of the root directory are essentially copied from a partition in the internal storage on boot, but you cannot write to the partition if you are not already root. In other words, this property denies root access via ADB, and the only way you could change it is by gaining root access in the first place. Thus, it is secure.

Actually the answer is yes