[GUIDE] LT18i - Arc S - General Tips, Guides, and Mods - Xperia Arc General

Sony Ericsson LT18i – Arc S
I’ve decided to line up a few important tips about this phone, which may or may not help the new users. I’ve migrated here from a Samsung i9000-GT Galaxy S, so my reviews are based in comparison with the Galaxy S. Overall one thing I like about Sony Ericsson is that Sony Ericsson is looking after their mobiles, The Firmware That the phone was shipped with (4.0.2.A.42 – 2.3.4) is bug less and Quite smooth. Sony Ericsson has even provided a convenient page with guidelines to unlock your bootloader and, They even released an Official Alpha Ice Cream sandwich Rom.
Despite what’s on the news about Sony Ericsson’s current status, I’d say It’s better than many other Mobile Manufacturers I know. This is My second Sony Ericsson Phone, First one being the S700i.
Mods and APK's I posted are for the 4.0.2.A.42 – 2.3.4 Firmware. Please Check that in Settings -> About Phone before replacing mine over yours.
Pros
Sleek design
Active Noise Cancelling Mic
Leather Pouch in the Retail Pack
HDMI Port
Sony Ericsson Goodies such as Timescape, FB Inside and Track ID
Being on the Ice cream Sandwich announced List
Sony Ericsson Retail Headset. You can actually enjoy music on these
Automatically connects over Mass Storage Mode even when debugging is enabled
Cons
USB On the Go needs a SE Live Dock
Camera Produces washed out Low Quality Images
Heats up when Playing a game for more than 15 Minutes (Fishing Kings HD)
Google Maps scrolling, dragging around is Not smooth
When you’re on a Call over the wired Headset, You can hear yourself through the headset
MicroSD cannot be hot swapped
Tips
Root Access
I believe rooting is quite important, and Rooting has never been easier. All you gotta do is visit this Guide by DooMLord and download the Easy Rooting Toolkit. The Rest is Just Click and wait.
Clockwork Mod Recovery
Yeah, this is Important. Mainly because of the Backup Function, At least to me. Other Than that, CWM is a necessary if you’re planning to flash custom ROMs that come in ZIP packages. To get this, There’s a Tool. No Flashing, or Flash Tools are required. Just Root Access is enough. This is the Link and Thread for the Tool. Read the Thread for Guidelines.
Modding System APKs.
Some APK files need facelifts and a mods here and there. The Most Important thing to remember when you’re dealing with Sony Ericsson is that File Permissions matter. Unless you set the Permissions correctly to the Modified APK’s, Your APK is worthless and might even result in a system crash or a Bootloop. Also, The required permission cannot be set when the File is in the SD card. You need to Move it to System\ and then set the permission and Move it to the Apps folder. If you paste it right away at the System\App\ folder, the System Force Closes before you set the permissions. So make Sure to Move it to the Root of the System\ folder first, Set the Permission and then move it to wherever you want it. The correct permission for System Apk’s are displayed below. Many People write it as rw-r-rx and in numbers. I didn’t Understand that, But I can perfectly understand this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changing the Font
This is easy, You don’t need third party tools to do this. Browse to the System/fonts/ folder and locate the DroidSans.ttf file. This is the main font that displays everything. Now there are two things you can do, Grab a new font and change its name to this and Paste it over the original file, or Grab the Original file and open it in a Font editor (I prefer Highlogic) and Paste the Glyphs from your Favorite Font. I recommend the latter because these fonts contain extended characters and dialects that might be handy in sending romantic text messages. If you’re going for the first option, Make sure to grab font that has everything. My favorite is the Ubuntu font I used in the Galaxy S. grab it if you want it.
Homescreen and Docks
No, Five Homescreens are not enough for me. Also I don’t like the Thick Dock with those four Shortcuts, I’d prefer it to be Transparent, so that It wouldn’t outstand over the wallpaper. So Going over the Android Development Pages, Thanks to various modders I’ve found the Mods. I’ve made myself a Homescreen with 7 Pages and a Transparent Dock. Grab it if you want. Sorry, To post credits Honestly I don’t remember who I leeched these tips from. This is where I started Reading.
Notification Bar
Seriously? There are no Quick Toggles in the Pull down Notification Bar? That was so disappointing and Heart Breaking. I need those toggles and I use them to switch the Status of Wifi, Bluetooth, and GPS. Who wants scroll several Homescreens to find the widgets that does it or go all the way to the settings page? After some searching I’ve found that someone has ported it. But the icons were a bit pixilated. So I corrected it with new icons. Once again, Sorry, I don’t know who I leeched this from. Its not from a single page. This is where I Started reading.
Yours to grab it If you like it.
Settings Page
Ok, this looks so gloomy in Sony Ericsson. The Settings Page on Samsung Galaxy S was a lot nicer and Colorful. While browsing around, I found the Perfect Solution, The Galaxy SII Theme for Sony Ericsson by thomassafca. I wouldn’t recommend everything in the Theme Package, But the Settings Page is a Must. Head over to the Thread and Get the Theme. You can grab mine from here, If you are also on 2 - 42 firmware
Correct Size for the Wallpaper
Picking up Wallpapers is a wee bit too hard, But then again If you know the Correct Resolution You can make one for yourself like below. The Correct Resolution for the LT18i is
960 x 854
You may Use a Editor of your choice (Mine is Photoshop) to make one. Yeah, In case you need the Megan Fox one I made, You can get it from here.
World Clock
Oops, There is no World Clock support in the default clock. So to get that, You can visit this thread download the widgets.
Full Screen Call Image
One thing more I love about Sony Ericsson. This is coming from their earliest phones. Back then All the other phones only displayed only a Tiny Image. When someone calls, If you have their Picture saved in the Contact, It is displayed Full screen (well Almost).
The Best Part about this is, The Image is actually saved in the VCF file (Contact Card), So you dont have to keep it in the Phone memory. Earlier days, You had to keep the Photo in Phone memory, and It shows up in the gallery as well. Those days are gone it seems.
Even when browsing through the contacts, The image is displayed vividly across the header.
So, What is the Correct Image Size for a Contact Picture ?
Its -> 3264 x 1990 (pixels). Resize Any Image of your choice, and Transfer it to the SD card. Open the Contacts Application and Browse for the Image using the Gallery or a File Explorer. Once You add the Image, You can delete it from the memory.
Will Update - Thank you. !

Thanks for the post bro, but I have a little question, why does SystemUI.apk needs permission to make phone calls ?! I just couldn't understand why :thinker:

DeepUnknown said:
Thanks for the post bro, but I have a little question, why does SystemUI.apk needs permission to make phone calls ?! I just couldn't understand why :thinker:
Click to expand...
Click to collapse
This is the SystemUI manifest:
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:sharedUserId="android.uid.system" android:process="system" android:versionCode="10" android:versionName="2.3.3" package="com.android.systemui"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-sdk android:minSdkVersion="10" android:targetSdkVersion="10" />
<[B][COLOR="Red"]uses-permission android:name="android.permission.STATUS_BAR_SERVICE"[/COLOR][/B] />
<application android:label="@string/app_label" android:icon="@drawable/ic_launcher_settings" android:allowClearUserData="false" android:persistent="true">
<service android:name=".statusbar.StatusBarService" android:exported="false" />
<activity android:name=".usb.UsbStorageActivity" android:excludeFromRecents="true" />
<activity android:theme="@android:style/Theme.Dialog.Alert" android:name="com.android.internal.app.ExternalMediaFormatActivity" android:excludeFromRecents="true" />
</application>
</manifest>
Statusbar Service is the only permission it requires.
Where did you get that it requires permission for phone calls?

Do you use the Ubuntu font in your screenshots?
Because it looks nice.
Might add it to my Arc after christmas, won't start flashing now on christmas
Sent from my iPad 2 using Tapatalk

Thanks mate, really nice tips.
Flo95 said:
Do you use the Ubuntu font in your screenshots?
Click to expand...
Click to collapse
JazonX said:
My favorite is the Ubuntu font I used in the Galaxy S. grab it if you want it.
Click to expand...
Click to collapse

DeepUnknown said:
Thanks for the post bro, but I have a little question, why does SystemUI.apk needs permission to make phone calls ?! I just couldn't understand why :thinker:
Click to expand...
Click to collapse
iridaki said:
This is the SystemUI manifest:
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:sharedUserId="android.uid.system" android:process="system" android:versionCode="10" android:versionName="2.3.3" package="com.android.systemui"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-sdk android:minSdkVersion="10" android:targetSdkVersion="10" />
<[B][COLOR="Red"]uses-permission android:name="android.permission.STATUS_BAR_SERVICE"[/COLOR][/B] />
<application android:label="@string/app_label" android:icon="@drawable/ic_launcher_settings" android:allowClearUserData="false" android:persistent="true">
<service android:name=".statusbar.StatusBarService" android:exported="false" />
<activity android:name=".usb.UsbStorageActivity" android:excludeFromRecents="true" />
<activity android:theme="@android:style/Theme.Dialog.Alert" android:name="com.android.internal.app.ExternalMediaFormatActivity" android:excludeFromRecents="true" />
</application>
</manifest>
Statusbar Service is the only permission it requires.
Where did you get that it requires permission for phone calls?
Click to expand...
Click to collapse
Now that's a Good Question, I still dont know how to check the Permissions required by Apps, or to understand what is needed by what. I found the original file over the thread where it had scrolling widgets with another APK that can move them around. They were already in a better order, So didn't go moving em or disabling them. Hmmm...

that's what I see when I attempt to install the apk file, so what do you think guys?
another quick question, I updated my phone yesterday to: 4.0.2A.0.62, will I be still able to use what's posted in this thread?
iridaki said:
This is the SystemUI manifest:
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest android:sharedUserId="android.uid.system" android:process="system" android:versionCode="10" android:versionName="2.3.3" package="com.android.systemui"
xmlns:android="http://schemas.android.com/apk/res/android">
<uses-sdk android:minSdkVersion="10" android:targetSdkVersion="10" />
<[B][COLOR="Red"]uses-permission android:name="android.permission.STATUS_BAR_SERVICE"[/COLOR][/B] />
<application android:label="@string/app_label" android:icon="@drawable/ic_launcher_settings" android:allowClearUserData="false" android:persistent="true">
<service android:name=".statusbar.StatusBarService" android:exported="false" />
<activity android:name=".usb.UsbStorageActivity" android:excludeFromRecents="true" />
<activity android:theme="@android:style/Theme.Dialog.Alert" android:name="com.android.internal.app.ExternalMediaFormatActivity" android:excludeFromRecents="true" />
</application>
</manifest>
Statusbar Service is the only permission it requires.
Where did you get that it requires permission for phone calls?
Click to expand...
Click to collapse

It needs all of these to display your notifications and make them interactive too. As I said, the manifests registers this app as Starusbar Service.
iR¡[email protected]!* via Tapatalk

Otg doesnt need a dock...you just need a otg adaptor or cable
Sent from my Xperia Arc using Tapatalk

DeepUnknown said:
that's what I see when I attempt to install the apk file, so what do you think guys?
another quick question, I updated my phone yesterday to: 4.0.2A.0.62, will I be still able to use what's posted in this thread?
Click to expand...
Click to collapse
I never Installed them to notice this, I just Paste them over the file in System/App/
Afaik, System Apps are never installed.
rkanwar said:
Otg doesnt need a dock...you just need a otg adaptor or cable
Sent from my Xperia Arc using Tapatalk
Click to expand...
Click to collapse
Yeah, That's for us.
For beginners who have no idea about Module loading, Terminal / ADB commands, There is no OTG without the Dock. To enable OTG (for Flash Drives) there's so much work to be done.

JazonX said:
I never Installed them to notice this, I just Paste them over the file in System/App/
Afaik, System Apps are never installed.
Click to expand...
Click to collapse
Fair enough, thanks bro, will do so once I am able to root my device since I updated last night.

JazonX said:
I never Installed them to notice this, I just Paste them over the file in System/App/
Afaik, System Apps are never installed.
Yeah, That's for us.
For beginners who have no idea about Module loading, Terminal / ADB commands, There is no OTG without the Dock. To enable OTG (for Flash Drives) there's so much work to be done.
Click to expand...
Click to collapse
Oh right my bad. To be honest the only difficulty im having is choosing between arc and arc s
Sent from my Xperia Arc using Tapatalk

rkanwar said:
Oh right my bad. To be honest the only difficulty im having is choosing between arc and arc s
Sent from my Xperia Arc using Tapatalk
Click to expand...
Click to collapse
Arc S (LT18i) is a actually an Arc (LT15) with a Faster Processor. The Rest is Almost the same.

Thanks dude! Much more understandable.

World Clock link sends me to Arconium ROM, do I have to have it, or it's somewhere in that thread??

It's a amazing guide, THX ;-) I consider to change the settings apk, do you know if the language will be in english or the file will work normally and use the language my phone is set to?
Sent from my Sony Ericsson Xperia Arc using Tapatalk

JazonX said:
Cons
...
Camera Produces washed out Low Quality Images
...
Click to expand...
Click to collapse
What?? The Arc has one of the best cameras around. Do you consider these as low quality images? Just look at this thread and you will see how good the camera really is. The camera kicks ass if you know how to use it.

DerEineDa said:
What?? The Arc has one of the best cameras around. Do you consider these as low quality images? Just look at this thread and you will see how good the camera really is. The camera kicks ass if you know how to use it.
Click to expand...
Click to collapse
I can show you the same or better with a Galaxy S or a Galaxy SII. Just check on the GSMarena Camera comparison chart, you will notice what gets washed out.
on the other hand,
The camera kicks ass if you know how to use it.
Click to expand...
Click to collapse
Can you guide me to the basics then ?

This guide is awesome! Thanks so much for this.
One thing - changing the font, can you also change the size (make it smaller) so that the screen displays more? When replying to a text message I can hardly see the message that came before! I can't believe this isn't an option on such an advanced phone.

JazonX said:
Arc S (LT18i) is a actually an Arc (LT15) with a Faster Processor. The Rest is Almost the same.
Click to expand...
Click to collapse
Not forget a better internet connection (instead of 7.2 MBit/s are 14.4 MBit/s).

Related

ADWLauncher Running on Adam

Here's a video with ADWLauncher installed incase people didnt like the Notion Ink UI. It worked very well. I'm not too familiar with the settings in ADWLauncher, so bear with me for a bit.
I really hope the XDA community can help me getting the natural google experience back on this device. the hardware with PQ is really nice, Adam's Specific Programs run well, but UI is a bit beta still with some FC.
------------------------------------
update with two more videos
------------------------------------
another view demonstrating the gps error, google maps, and the gyroscope
and Notion Ink Adam's ability to handle online adobe flash applications (www.sumopaint.com)
-------------------------------------
I dont take credit for this, but the people at notioninkhacks.com and xda-developers have finally rooted Adam and installed the Android Market!
How is the touchscreen in terms of sensitivity? Also is there any give to the display when you press on it?
The screen seems very responsive. seems comparesble to the nexus one minus the screen issue
Sent from notion ink adam
Thanks for the walk though.
BTW, Appbrain uses official Android Market for access, so since it isn't on the Adam, it can't work.
Care to try applnet and or the other "alternate" markets?
-CC
How is the Pixel Qi in terms of brightness/evenness? Are the colors washed out enough to make you consider the LCD model? Thanks again for the walk-through!
Video looks good, it's the only video of the Adam that I've watched without wanting to throw up.
How're you liking the non-backlit Pixel Qi? Decent for everyday use? Or only in situations where LCD has problems (sunlight) or battery saving?
bemymonkey said:
Video looks good, it's the only video of the Adam that I've watched without wanting to throw up.
How're you liking the non-backlit Pixel Qi? Decent for everyday use? Or only in situations where LCD has problems (sunlight) or battery saving?
Click to expand...
Click to collapse
the non-backlit PQ is interesting. i dont know whether it's a good thing or bad thing long term, but for battery wise, it's a good thing. but i've been using it in color mode mostly. but with the PQ mode, the view angel are much better. I say it'll take a bit getting use to seeing things in b/w lol~~. It's like kindle but more responsive in a nutshell
What about in portrait mode? Saw some apps that you used in portrait, but what about like homescreen, facebook, twitter, etc. Was a bit saddened how the stock launcher seemed to be fixed to landscape.
I am impressed.......!!!!!!!!wow ..
is there any website in particular you used to download the .apk files
Sent from my Nexus One using XDA App
benyameen said:
What about in portrait mode? Saw some apps that you used in portrait, but what about like homescreen, facebook, twitter, etc. Was a bit saddened how the stock launcher seemed to be fixed to landscape.
Click to expand...
Click to collapse
ADWLauncher is not locked in landscape mode. the home screen can rotate. it resizes the icons and widgets and it's not too bad. facebook can rotate too, but it's rotates according to the app as you see it on your smartphone
posted some new videos for you guys
inspiron41 said:
ADWLauncher is not locked in landscape mode. the home screen can rotate. it resizes the icons and widgets and it's not too bad. facebook can rotate too, but it's rotates according to the app as you see it on your smartphone
Click to expand...
Click to collapse
Thanks for the reply and video.
The biggest worry I had about the Adam was that it would only be usable in landscape mode - this is clearly not the case =]
Just can't wait for the next round of open orders... Definitely buying...
inspiron41 : can you confirm that Adam comes pre rooted ..?
Are you able to install Super User ? Can you try VISIONary and post results here for Temp root..? or may be Perm Root..??
zabaknilesh said:
inspiron41 : can you confirm that Adam comes pre rooted ..?
Are you able to install Super User ? Can you try VISIONary and post results here for Temp root..? or may be Perm Root..??
Click to expand...
Click to collapse
i never rooted anything, but i'm following the development section carefully trying to learn as i go. i dont want to do anything to brick my device lol. i'll let you know when i figure things out
zabaknilesh said:
inspiron41 : can you confirm that Adam comes pre rooted ..?
Are you able to install Super User ? Can you try VISIONary and post results here for Temp root..? or may be Perm Root..??
Click to expand...
Click to collapse
It is not pre-rooted but rooting is work in progress:
http://notioninkhacks.com/forums/viewtopic.php?f=29&t=345
Also NI had to release a complete recovery procedure due to an issue with the first update. This procedure includes a bootloader and recovery image which should recover any bricked device.
http://notioninkhacks.com/forums/viewtopic.php?f=29&t=364
two new videos
2-finger Rotation on Google Maps
I noticed on one of your videos that the two finger rotation on Google Maps is not working. There is a file called /system/etc/permissions/handheld_core_hardware.xml that tells Android about the hardware. I don't have my Adam (yet -- 1/29 shipping -- I hope), so I can't check. However you might check if the the following permissions are included:
<feature name="android.hardware.touchscreen" />
<feature name="android.hardware.touchscreen.multitouch" />
<feature name="android.hardware.touchscreen.multitouch.distinct" />
These are needed for "independently-trackable multiple-finger multitouch," or so it says in the associated xml file (that you could alternately include if it exists in the same directory):
<feature name = "android.hardware.touchscreen.multitouch.distinct.xml"/>
Good luck.
ptok said:
I noticed on one of your videos that the two finger rotation on Google Maps is not working. There is a file called /etc/permissions/handheld_core_hardware.xml that tells Android about the hardware. I don't have my Adam (yet -- 1/29 shipping -- I hope), so I can't check. However you might check if the the following permissions are included:
<feature name="android.hardware.touchscreen" />
<feature name="android.hardware.touchscreen.multitouch" />
<feature name="android.hardware.touchscreen.multitouch.distinct" />
These are needed for "independently-trackable multiple-finger multitouch," or so it says in the associated xml file (that you could alternately include if it exists in the same directory):
<feature name = "android.hardware.touchscreen.multitouch.distinct.xml"/>
Good luck.
Click to expand...
Click to collapse
/etc/permissions/handheld_core_hardware.xml
where do i start looking for that file? on root drive?
Oops sorry, its /system/etc/permissions

Droid X AOSP Camera/Camcorder Tweaks (higher quality and FPS recording)

This should be posted in the development section, but I don't have enough posts to do so... Either way, I found this mod so useful that I wanted to share it with the rest of the community that has helped me out so many times in the past.
I have found a way to increase the Droid X's video recording capabilities by modifying system/etc/media_profiles.xml. Note, this is for the 2.2 AOSP camera app only(as far as I know). The AOSP camera comes as the default in the Liberty 1.0 ROM.
Modifying a couple of points in the media_profiles.xml file, one can increase the maximum bitrate from 10000000 bits/second to 17000000 bits/second(or more, this is the value I settled on).
I've noticed better fast motion video capture as well as better low light capture. I've also seen an increase in FPS. The maximum FPS for the Blur camera(stock) is 24 FPS, I've been able to capture at an average of 29 FPS(in 720p mode!).
See the attached picture witch shows an average of 19501 kbps and 29 FPS for one of my recorded videos. Normally, one would only see ~100000 kbps and under 24 FPS.
I modified the following lines of code in the XML file:
Code:
<EncoderProfile quality="high" fileFormat="mp4" duration="60">
<Video codec="m4v"
bitRate="17000000"
width="1280"
height="720"
frameRate="30" />
I modified the "low" setting to be the "high" bitrate's old value:
Code:
<EncoderProfile quality="low" fileFormat="mp4" duration="60">
<Video codec="m4v"
bitRate="10000000"
width="1280"
height="720"
frameRate="30" />
Code:
<VideoEncoderCap name="m4v" enabled="true"
minBitRate="64000" maxBitRate="17000000"
minFrameWidth="176" maxFrameWidth="1280"
minFrameHeight="144" maxFrameHeight="720"
minFrameRate="1" maxFrameRate="30" />
I have uploaded a sample of a recording that I made to youtube, but I can't post the link because of the forum rules.
If you don't want to do the modification yourself, I have attached a copy of my media_profiles.xml file. .xml files are not legal uploads here, so I've changed it to .txt. Simply change the extension to .xml and place it in place of your current media_profiles.xml file using Root Explorer or ADB.
Enjoy your new enhanced video recording functionality on your Droid X!
Edit: High quality image capture
It turns out that modifying this block of code increases the quality of pictures:
Code:
<ImageEncoding quality="100" />
<ImageEncoding quality="90" />
<ImageEncoding quality="70" />
<ImageDecoding memCap="20000000" />
The three ImgageEncoding quality tags correspond to "Super Fine", "Fine", and "Normal" when in the preferences of the AOSP Camera App. The original values where: "90", "80", and "70".
A picture at "Super Fine" resulted in a file size of 3333 KB.
The same picture at "Fine" resulted in a file size of 2054 KB.
In all honesty, I could not discern the difference in quality, even when I placed the pictures side-by-side on my 24 inch monitor. Perhaps the "Super Fine" picture looked sharper. This should at least give the user the ability to get the absolute best quality pictures from their Droid X. I would post the comparison pictures, but I am not allowed to(file size restrictions and no outside links). If you would like to see this evidence, please petition an XDA Moderator.
Lastly, the values of the ImageEncoding quality tags in the media_profiles.xml file that is attached to this post are: "100", "80", and "70".
Edit: One last tip, if you recently used Pandora or Slacker radio there appears to be a bug that causes the AOSP camcorder to crash if you use the camcorder soon after using one of these music services. The solution is to go to Settings->Applications->Running Services and kill the services that each of these music apps has created. My hunch is that these apps are not handing the media service to the camcorder app when it requests it because these music apps are holding onto it even when you have left the app by not closing their service. I made a Tasker profile to handle the process automatically when the camera button is pressed.
Interesting, nice to see there is some possible head room with the DX.
While we are on this topic, does anyone know how to install the aosp camera along with the blur camera, I would like to have both. As of now they replace each other because they have the same name.
Sent from my DROIDX using XDA App
frub3nz said:
While we are on this topic, does anyone know how to install the aosp camera along with the blur camera, I would like to have both. As of now they replace each other because they have the same name.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Why not just rename one of the cameras before you install it. I haven't tried it but maybe it work.
While we are on this topic, does anyone know how to install the aosp camera along with the blur camera, I would like to have both. As of now they replace each other because they have the same name.
Sent from my DROIDX using XDA App
Click to expand...
Click to collapse
Originally Posted by frub3nz
We could write a script that lets the user pick which camera to use when a shortcut is pressed or the camera button is used to bring up the camera. The Liberty 1.0 Toolbox is doing something similar when the user selects the AOSP camera or the Blur camera in the Toolbox App section. From what I recall, it swaps them pretty quickly.
Just did this myself on my phone, looks promising, but don't really have the desire to test it out. Maybe something like this can be done on the Camera and maybe we can get even better pictures using that as well.
Thanks for the heads up.
how do we verify if it worked and why wouldn't this work with the blur camera?
bravo1234 said:
Just did this myself on my phone, looks promising, but don't really have the desire to test it out. Maybe something like this can be done on the Camera and maybe we can get even better pictures using that as well.
Thanks for the heads up.
Click to expand...
Click to collapse
I did modify something that looked like it pertained to pictures.
Code:
<ImageEncoding quality="100" />
<ImageEncoding quality="80" />
<ImageEncoding quality="70" />
<ImageDecoding memCap="20000000" />
The first quality level was originally set to "90". The attached media_profiles.XML file attached to this thread already has this modification.
The pictures from the AOSP camera look much grainier than the pictures I got from the Blur Camera. Take it for what you will. Ay least we have some control over the quality of pictures/video the Droid X captures.
carbonwhiskey said:
how do we verify if it worked and why wouldn't this work with the blur camera?
Click to expand...
Click to collapse
To verify that it worked, take a video before the modification of the same scene, lighting, and camera movements. Copy the video from the phone to your computer. Then right click->properties(in windows). Go to the details tab and compare the bitrate to a video taken with the modification. The modified one will have around double the bitrate and around double the file size(if the recording is the same length).
I don't know if the Blur camera references the media_preferred.XML file. I guess I just assumed that it did not. Let me know if it does anything to the blur camcorder. The blur camcorder uses the 3gp extension and h.264 compression. Modify the bitrates for this extension and compression.
rquellet said:
I did modify something that looked like it pertained to pictures.
Code:
<ImageEncoding quality="100" />
<ImageEncoding quality="80" />
<ImageEncoding quality="70" />
<ImageDecoding memCap="20000000" />
The first quality level was originally set to "90". The attached media_profiles.XML file attached to this thread already has this modification.
The pictures from the AOSP camera look much grainier than the pictures I got from the Blur Camera. Take it for what you will. Ay least we have some control over the quality of pictures/video the Droid X captures.
Click to expand...
Click to collapse
I have noticed that the pictures seem a bit grainier, maybe due to the blur camera having post filtering settings?
Fission 2.6.1
bravo1234 said:
I have noticed that the pictures seem a bit grainier, maybe due to the blur camera having post filtering settings?
Click to expand...
Click to collapse
I noticed that you were running the Fission 2.6.1. Was wondering if by chance have you installed the 2.6.1 update and what changes if any were made to this rom?
ilpleasu said:
I noticed that you were running the Fission 2.6.1. Was wondering if by chance have you installed the 2.6.1 update and what changes if any were made to this rom?
Click to expand...
Click to collapse
check your pm.
Basically just a bug or two was fixed, and everything is blurless/AOSP now.
I prefer the blur video recorder. Is this Mod possible with the Blur camera app?
Since I can't so this with Blur UI. Can I install the AOSP Camera with the stock UI? If so where can I get the camera app?
I was sent the AOSP Camera app from the Liberty Rom. I'm running stock. All I did was rename the file from Camera.apk to AOSP_Camera.apk. Put in the root/system/app folder. Set the permissions. Rebooted the phone and BOTH Blur and NON Blur Camera apps appeared and WORK!
i tried the mod. but was only able to get 15 fps max in hd using the AOSP Camera.
Being an ex video editor, this has been one of my major complaints about camera hardware. The only two companies using a decent image sensor are Apple and Samsung. But, 24fps is crap to work with when you have to view it on 30fps devices and monitors. The X doesn't do bad outdoors where I use it the most but the framerate thing has pissed me off since I have had it.
I'll definitely give this a whirl and see what happens. Thank you so much for posting.
Max FPS
xmguy said:
i tried the mod. but was only able to get 15 fps max in hd using the AOSP Camera.
Click to expand...
Click to collapse
The maximum framerate is a function of a couple of factors:
the available ambient light
the amount of compression that has to occur
the maximum FPS value set by the camcorder app
I'm guessing that you were taking this video indoors, probably at night, with no/little natural light. I've seen this mod increase my low light FPS capture, this is probably due to the lower compression ratio needed.
Keep in mind that the camcorder will reduce it's framerate into the single digits when not enough light is available. This is because the camera's CCD cannot take in enough light to create a frame in the time interval you want. In short, this mod raises the maximum from 1/24 to 1/30, it does not guaranty that you will get the maximum FPS. I'm not sure what part of the process is dictating the current FPS rate at the time of capture. It could be the camera driver(which we wouldn't be able to change, since it is part of the kernel). If it's something in the app, it is not available to change in the media_prefs.xml file(that I know of).
SUCCESS!!
I took some HD Video yesterday. Outdoors. I just now ran it though a FPS decoder. Got 29 FPS.
Only one issue. There seems to be alot of jitter in the image when played back. Like the screen is refreshing slowly.
May be a issue with my video card however.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
xmguy said:
SUCCESS!!
I took some HD Video yesterday. Outdoors. I just now ran it though a FPS decoder. Got 29 FPS.
Only one issue. There seems to be alot of jitter in the image when played back. Like the screen is refreshing slowly.
May be a issue with my video card however.
Click to expand...
Click to collapse
I'm glad that you were able to get it working. You might also notice that the Droid X will drop a few frames while playing the video back on the phone. You can confirm this by plugging the Droid X into a computer with debugging mode filtered to "Errors". It shows how may frames were late/dropped vs. on time.

[Mod][How to][Updated Camera 3.3.20.8]Unlock Advanced Camera Settings | Non-Root/Root

Finally! The moment all of you have been waiting for. This is the Tutorial on "How to unlock the advanced camera settings in the motorola camera app" (ladybug icon) :victory:
first of all, this could be the most useful tutorial for stock rom users, since most of the custom rom already have this.
This mod should also work with:
MOTO DEVICES
-Moto E ------------------Confirmed working by @AshuGite and @spiked_mistborn
-Moto G 4G (LTE)--------Confirmed working by many users
-Moto X (2013)-----------Not confirmed, yet. But it should work
-Moto G 2 Gen. (2014)---Confirmed working by @prateek.khurana31
-Moto X 2 Gen. (2014)---Confirmed working by @neh4pres
OTHER DEVICES:
-Xperia Z2----------------Confirmed working except for recording Videos(missing libs) by @ogunja
If you owned one of the Devices mentioned above and the Mod is working for you, pls let me know for which specific Device it worked, hit the thanks Button below and feel free to open a new Thread in one of the above mentioned Devices' Forums, mentioning this Thread. Thank you
EASY METHOD
For NON-ROOT and ROOT users:
DON'T WORRY, this camera app will install as a seperate app so you will still have the original Motorola Camera app
Here is the camera app with unlocked hidden menu for non-root and root users: Motorola Camera v3.3.20.8 (unlocked hidden menu). Just install as normal apk. Thanks to @jefish for making this awesome Mod
How to access the hidden settings: After you swipe out the settings wheel you will have a "Ladybug" icon in the lower right corner (Screenshots below at the end of this post). just press it enjoy the advanced settings for your Camera
Recommended Settings based on @juanchotazo99 tests: Turn off Wavelet Noise, as it screws up your image quality. Morpho VNR seems to reduce noise in the cameras live view (not on the final image). QC Tintless seems to reduce the reddish tint on final images. So it is up to you if you want to set the last 2 options to on or off
ATTENTION: The Methods below are only necessary if you have ROOT and don't want to install the modded apk.
If you have the Play Store Version of the camera app, pls uninstall and flash one of these flashable zips through CWM Recovery. Thanks to @lost101 for making these.
Moto G (2013) 4.4.4 Stock Camera app: (Wavelet noise, Morpho VNR and QC Tintless settings available)
or
Moto G 2nd Gen. (2014) 4.4.4 Stock Camera app
If you don't want to manually edit your build.prop, you can have a look at this Xposed Module which unlocks the hidden settings without editing anything. Thanks to @S0bes for his Xposed Module
Also, check out @juanchotazo99 's awesome camera test with this new settings in this post. this is also really helpful to understand where the photos get better quality.
Completely Manual Method
Here is the tutorial for those who want to get the hidden settings by manually editing the build.prop
Step 1
Make sure you device is rooted and download or use any File Explorer that has root access.
Step 2
navigate to: Root>System>build.prop
edit the build.prop file (MAKE A BACKUP FIRST) and search for this line:
Code:
ro.build.tags=release-keys
and change it to
Code:
ro.build.tags=test-keys
and save the file.
Step 3
Finally reboot your Device and you're done.
Now after you swipe out the settings wheel you will have a "Ladybug" icon in the lower right corner (pictures below). just press it enjoy the advanced settings for your Camera :victory:
Screenshots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Don't forget to hit Thanks i would be really happy if you do that
Post process noise reduction, morpho VNR (NR, what else could that be, than noise reduction?). Let's disable these two settings and test. I'll give the camera a try tomorrow in daylight with these changes. I mean, scenes with foliage and plants, that suffer greatly from the noise reduction and become painting-like in pictures. Before, and after.
Thanks a lot for this!!
Hidden above is the original. Let's make a better use of this post.
--------------------------------------------------------------------------
Bringing all of this to Moto's attention:
In my camera testing post quoted above I had added the following at its end:
Based on all the previous testing done by people in Motorola's official thread on Moto G's camera quality, BEFORE what @GodOfPsychos has discovered, a Motorola representative stated the following:
https://forums.motorola.com/posts/e2f2722bfc?page=1
https://forums.motorola.com/posts/e2f2722bfc?commentId=801623#801623
We’ve been exploring several options to improve the camera. Some items are already on the list – we will fix the intermittent split-flash problem that produces a picture split into light and dark halves. We are working on the intermittent red-tint issue. Other areas are more difficult because any change to improve one area will create other artifacts -- and someone will object to those.
That being said, we have a plan to improve, and much of it is based on the feedback gathered from this thread and others. Thank you. It won’t be fast because it requires changes beyond what we can do through updates to the Camera app itself. But we’re going to make changes that in addition to the items above, should improve sharpness and detail.
I cannot comment on the timing of updates, so I can only ask for patience as we work through this. And again, thanks for the feedback; the photos and observations posted and sent via email were instrumental in helping us get to this point.
Click to expand...
Click to collapse
Image quality improvements have been promised for the next update, that would be Android L.
Android L is itself a big deal for imaging because it exposes the entire picture/video taking pipeline to camera apps... that means someone can write a camera app with their own picture processing algorithms which in our case can definitely help us with the quality issue.
Meanwhile, we can enjoy better pictures thanks to OP's findings on the camera app's hidden settings. Anyway, if you read what I've bolded in the quoted comment from that official thread... What the hell, Motorola? I mean, he's probably meaning that the stuff that has to be changed is regarding the sensor itself (it presumably does in-sensor noise reduction, outside the scope of what the camera app does by itself) but when the camera app is doing useless noise reduction and you tell people that it can't be solved that way, then @GodOfPsychos finds out about the app's hidden settings being some simple on/off toggles for that useless noise reduction... just... what the hell. This defies logic.
I've made a user in the Motorola forum and have been posting all our findings in that thread. This can't go unnoticed there because their representatives are able to communicate with the camera team. All my posts so far, under the name JohnRambo:
https://forums.motorola.com/posts/e2f2722bfc?commentId=808803#808803
https://forums.motorola.com/posts/e2f2722bfc?commentId=809381#809381
https://forums.motorola.com/posts/e2f2722bfc?commentId=809421#809421
https://forums.motorola.com/posts/e2f2722bfc?commentId=809547#809547
https://forums.motorola.com/posts/e2f2722bfc?commentId=810521#810521
https://forums.motorola.com/posts/e2f2722bfc?commentId=812005#812005
https://forums.motorola.com/posts/e2f2722bfc?commentId=812831#812831
Silence so far, and people are starting to get upset about the matter. You would be, if the representatives all along said that the camera was fine, and the required tweaks are beyond what they can do with the camera app.. yeah, you get the idea. People shouldn't have to root their phone to fix its camera. EDIT: well, there's the modded camera APK now which is just great! Everyone can now enjoy their moto G's camera as it should be.
They updated the Moto X 2013's software to improve its camera quality, we've proven they can do the same with the Moto G 2013...
01/10/14, 9 days later
https://forums.motorola.com/posts/e2f2722bfc?commentId=813675#813675
I went back and marked my previous post as "best answer" to keep it a little more in sight. We're continuing to evaluate improvements, balancing how changes in one area might impact other aspects of the photos. As I wrote before, it will take a firmware update to implement some of the changes; not something we can do via a faster Play Store update.
Click to expand...
Click to collapse
Finally, an answer. So, no mention of the camera app doing this useless NR. Okay. Well, it seems we'll have to wait for the L update.
This actually made it to the XDA front page.
--------------------------------------------------------------------------
Added 28/09/14
Old camera app, before the update:
So, we have three settings to tweak, what do they do?
Wavelet NR is the offender, if you want to improve your pictures then disable that one.
Morpho VNR reduces color noise in the camera live view, I've been taking pictures with it on and off, and there's no difference in the final picture, nor in its file size. Its effect is especially noticeable in low light conditions, try it out. This one is up to you, if you prefer a cleaner live view.
QC Tintless affects color rendering, in particular the amount of red in the final picture. It is presumably the 4.4.4 fix for people who had too much red in their pictures in 4.4.2, so this one is up to you to tweak. Keep it enabled if you want more neutral colors, disabled if you want a little more red in your pictures out of the camera.
Just disable Wavelet NR. The other two are beneficial either to the live view's quality, or to the final picture through better color rendering.
--------------------------------------------------------------------------
Added 12/10/14
There has been an update to the camera app.
Wavelet NR is now QC denoise, still enabled by default. Do the right thing and disable it to improve picture quality.
Morpho VNR has been renamed to Morpho denoise and is no longer selectable. It doesn't affect you, don't mind this change. It is enabled by default and it should be, otherwise the viewfinder becomes a color noise mess under low light conditions, unlike the pictures taken with QC denoise off.
QC Tintless is unaffected. Keep it enabled.
--------------------------------------------------------------------------
Added 03/10/15
Go here for the latest camera app, with hidden settings enabled. Thanks @S0bes for all your hard work on this.
The camera app's hidden settings have changed a bit since the last update to this post, some other interesting settings have appeared (which I haven't tested by the way), but the recommendation that's been on this post for a year so far stays the same. Disable QC denoise, leave the rest as it is, enjoy!
As always your mileage may vary, the app can be installed on most Motorola phones so far (all of them?), and the improvements depend on how bad your phone's sensor is. The 1st gen Moto G has a particularly bad 5MP sensor that its output suffers too much by the noise removal done by the app. On phones with better cameras, well, you'll have to test for yourself to see if it's worth it.
juanchotazo99 said:
Post process noise reduction, morpho VNR (NR, what else could that be, than noise reduction?). Let's disable these two settings and test.
Will give the camera a try tomorrow in daylight with these changes. I mean, scenes with foliage and plants, that suffer greatly from the noise reduction and become painting-like in pictures. Before, and after.
Thanks a lot for this!!
Click to expand...
Click to collapse
im gonna do a test tomorrow, too.
juanchotazo99 said:
Will give the camera a try tomorrow in daylight with these changes. I mean, scenes with foliage and plants, that suffer greatly from the noise reduction and become painting-like in pictures. Before, and after.
Thanks a lot for this!!
Click to expand...
Click to collapse
GodOfPsychos said:
im gonna do a test tomorrow, too.
Click to expand...
Click to collapse
but guys, pls upload it on imgur.com (imgur does not compressing images, so it's in it's full quality) and post links, thx
Didn't work for me
I'm on Stock 4.4.4 (XT1033) and the Camera app version is 3.2.54.1.
Any suggestions?
Sent from my XT1033 using XDA Premium 4 mobile app
KDB223 said:
Didn't work for me
I'm on Stock 4.4.4 (XT1033) and the Camera app version is 3.2.54.1.
Any suggestions?
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i don't know either. im a noob at stuff like this. i just found this out at midnight after hours of looking for the cause, that made those settings visible (never thought it would be just an easy build.prop entry).
which file explorer did you use for editing the build.prop?
if it is root explorer, then it could be that the build.prop didn't really saved. in this case the easy solution for that is, before editing the build.prop file, press the "Mount R/W" button in the upper right corner. after that you can edit the build.prop and save it
Working fine on xt1032 4.4.4.:good:
Testing...
KDB223 said:
Didn't work for me
I'm on Stock 4.4.4 (XT1033) and the Camera app version is 3.2.54.1.
Any suggestions?
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
make sure changes were saved then reboot and check again
Working fine here, I can tell these pictures have much more fine detail, but a little bit of noise in low light conditions.
For the people that is not working, I had the same problem, just change the line, save and delete the .bak of the build prop.
2hipso said:
make sure changes were saved then reboot and check again
Click to expand...
Click to collapse
GodOfPsychos said:
i don't know either. im a noob at stuff like this. i just found this out at midnight after hours of looking for the cause, that made those settings visible (never thought it would be just an easy build.prop entry).
which file explorer did you use for editing the build.prop?
if it is root explorer, then it could be that the build.prop didn't really saved. in this case the easy solution for that is, before editing the build.prop file, press the "Mount R/W" button in the upper right corner. after that you can edit the build.prop and save it
Click to expand...
Click to collapse
I'm more than sure that my changes have stuck. I used Turbo Editor to the edit and then checked with ES File Explorer.
Sent from my XT1033 using XDA Premium 4 mobile app
GodOfPsychos said:
i don't know either. im a noob at stuff like this. i just found this out at midnight after hours of looking for the cause, that made those settings visible (never thought it would be just an easy build.prop entry).
which file explorer did you use for editing the build.prop?
if it is root explorer, then it could be that the build.prop didn't really saved. in this case the easy solution for that is, before editing the build.prop file, press the "Mount R/W" button in the upper right corner. after that you can edit the build.prop and save it
Click to expand...
Click to collapse
I'm more than sure that my changes have stuck. I used Turbo Editor to the edit and then checked with ES File Explorer.
Sent from my XT1033 using XDA Premium 4 mobile app
Please delete this post. (Sorry)
I still don't know what "Morpho VNR" and "QC Tintless" are.
btw. I recognized that the pre-installed motorola camera app is different to the motorola camera app installed through play store.
in the play store version are a few other options available like:
"Image Stabilization" (somehow unavailable on the pre-installed version), "Video Stabilization" (not greyed out like on pre-installed version),
"Dual Video Encode"(somehow unavailable on the pre-installed version), "Preview history" (not greyed out like on pre-installed version),
"HDR save EV0" (not greyed out like on pre-installed version), "Log AEC; AF; AWB" (not greyed out like on pre-installed version)
But the play store version is also missing some options that appear to be only available on pre-installed version like:
"Morpho VNR" (somehow unavailable in play store version), "QC Tintless" (somehow unavailable on play store version), "Video Size" (somehow unavailable on play store version),
"ALTM" (somehow unavailable in play store version), "Exposure compensation" (somehow unavailable in play store version), "White Balance" (somhow unavailable in play store version)
If someone has all these options available and not greyed out, i would really appreciate it, if you share your "MotCamera.apk" with us. i would attach it to the thread and of course give credit to you.
PS: sorry for my bad english.
Working FIne!!
xt1032 4.4.3
Thank you @GodOfPsychos
I will be grateful if someone tells me what is Morpho VNR and QC Tintless. And if it somehow improves the quality of photos, maybe also with Wavelet noise.
I can't test it because is night
Sent from my tablet./Odoslané z môjho tabletu.
been using the moto camera on a custom ROM & can't believe I just noticed that little ladybug lol, thanks op!
Does this affect OTA update in anyway also do I need to root to edit?
sonygoup said:
Does this affect OTA update in anyway also do I need to root to edit?
Click to expand...
Click to collapse
about the ota update i am not sure. but i think it will work. and yes you need root access
KDB223 said:
I'm more than sure that my changes have stuck. I used Turbo Editor to the edit and then checked with ES File Explorer.
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
then i am out of ideas.
Damn could a modded apk work? If so can someone do it?

[6.0.1] List of missing options on Android Marshmallow

I'm trying to gather information about the missing options or aspects on firmware 23.5.A.0.570 [6.0.1]
Any help will be acepted and added.
Missing Options
- STAMINA Mode
- Ultra STAMINA Mode
- Microphone Noise Supression
- Bug on recalling after call
Last Update: 04/18/2016
Possibly there'll be no stamina mode, because Marshmallow got a function for powersaving itself (it's called Doze).
fastlone said:
Possibly there'll be no stamina mode, because Marshmallow got a function for powersaving itself (it's called Doze).
Click to expand...
Click to collapse
Sony just said they will bring back stamina mod in future updates
Connect to Dual controller PS3
Depump said:
Connect to Dual controller PS3
Click to expand...
Click to collapse
in lollipop you could connect for ps3 and ps4. Only ps4 in marshmallow?
in MM ps4 only
A bug or a feature?! - Horrible black status bar is back for several views. Not for all but for many.
This makes the general UI really ugly!
Absolute best solution would be to make options to chose the color of status and navigation bar! Black or Dark Primary Color (nothing more)
Sony! Please read and use googles material design guideline.
https://www.google.com/design/spec/style/color.html
btw: I know there are Apps to do this. But most or even all are eating preformance. Only code adjusting will do this without affecting system.
http://www.xperiablog.net/2016/04/1...o-japanese-xperia-z4z5-models-on-marshmallow/
http://www.xperiablog.net/2016/04/14/stamina-battery-mode-is-returning-on-marshmallow-confirmed/
If not for the Z3 maybe someone can port it.
Clear phase and xLoud are no longer available
Location-based WIFI was a wonderful option in KitKat
istux said:
Location-based WIFI was a wonderful option in KitKat
Click to expand...
Click to collapse
It was ported to Lollipop by @niaboc79 and can be downloaded here http://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/app-location-based-wifi-lollipop-t3151669.
Best thing about it is that it's not only working on Lollipop, but perfectly on Marshmallow too! Give it a try!
Nevertheless it would be great if Sony implemented it again.
okij said:
It was ported to Lollipop by @niaboc79 and can be downloaded here http://forum.xda-developers.com/crossdevice-dev/sony-themes-apps/app-location-based-wifi-lollipop-t3151669.
Best thing about it is that it's not only working on Lollipop, but perfectly on Marshmallow too! Give it a try!
Nevertheless it would be great if Sony implemented it again.
Click to expand...
Click to collapse
It wouldn't be great, but waste of time IMHO. I tested how wifi always on is draining battery, and in the same situations - 10 hours daily connected to wifi, 14 hours away from any known wifi, and couldnt see difference in battery stats between turning wifi off or staying all the time with wifi on. There were some differences, but the deviations were in both directions.
The worst battey eater is mobile data, if you have internet always on with the synchronization, then using any wifi, even with the weekest signal will save a lot of battery than on mobile data, especialy 3g/hsdpa.
In terms of Stamina...
Right now I am using phone with disabled Stamina at all. First thing I noticed, that phones statistics showed me less than half of the time on battery cycle, but after some days phone this time grown to the same values - is working at least two whole days, sometimes almost 3. So with the same usage in the same area (means the same signal strength) I didnt saw any differences in using Stamina (of course it depends what software you are installing on the phone, and some of them could be kept in control thanks to setting Stamina on)
Is There An option to have sd card write ability for 3rd party apps?
Wysłane z mojego D5803 przy użyciu Tapatalka
STAMINA mode makes a return to Japanese Xperia Z4/Z5 models on Marshmallow
STAMINA mode makes a return to Japanese Xperia Z4/Z5 models on Marshmallow
http://www.xperiablog.net/2016/04/1...o-japanese-xperia-z4z5-models-on-marshmallow/
Ops... already been posted, sorry...
lamale78 said:
Is There An option to have sd card write ability for 3rd party apps?
Wysłane z mojego D5803 przy użyciu Tapatalka
Click to expand...
Click to collapse
Sure. If you have root, I suppose yes, then edit file: /etc/permissions/platform.xml
Look for a code:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
Add one line inside with gid media_rw like below:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
paffo said:
Sure. If you have root, I suppose yes, then edit file: /etc/permissions/platform.xml
Look for a code:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
</permission>
Add one line inside with gid media_rw like below:
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
<group gid="sdcard_r" />
<group gid="sdcard_rw" />
<group gid="media_rw" />
</permission>
Click to expand...
Click to collapse
this works in lp and kk but not in mm.
the code
Code:
<permission name="android.permission.WRITE_EXTERNAL_STORAGE" >
is not in the xml included.
marlontravagli said:
STAMINA mode makes a return to Japanese Xperia Z4/Z5 models on Marshmallow
http://www.xperiablog.net/2016/04/1...o-japanese-xperia-z4z5-models-on-marshmallow/
Ops... already been posted, sorry...
Click to expand...
Click to collapse
I dont need Stamina back. Doze in MM do a good job. And with xposed i can use "Power Nap" and have a better Standby as with Stamina + Log wich app would wake the phone.
I hope google bring back a fix for SD-card, so older apps can whrite to any folder.
Another missing option: any control whatsoever of emergency alerts. I was just disturbed earlier by receiving an emergency alert and it turned out to be the standard test broadcast and not even so much as an amber alert. I need to receive only the most extreme alerts only so I find this to be very very unpleasant. It looks like SONY has opted to remove the built in controls in the system settings or stock messaging app in favor of a separate emergency app. Previously apparently they did let you change the settings in their Lollipop ROM (I was using CyanogenMod up until this 6.0.1 release, so can't really attest to that) but I go to the emergency app in this and it has absolutely no settings or controls, just a list of the previously received alerts (so far just that test alert for me.) Normally test alerts shouldn't even be on by default, so someone dropped the ball here I guess.
EDIT: Apparently Google's own Messenger app can be separately downloaded: https://play.google.com/store/apps/details?id=com.google.android.apps.messaging&hl=en It has a setting for this. I'm not sure if this is system-wide, but I'll just switch to their app because there's not really any reason not to I guess.
EDIT2: I had manually loaded CellBroadcastReceiver.apk from CyanogenMod's packages (probably more or less AOSP standard, but I had CyanogenMod handy.) Apparently this was the reason I had that option. I removed it and the option was gone. Put it back on and the option has returned. It looks like it has to be loaded as a system app. I froze SONY's Emergency Alerts app. So far so good. I'll have to wait until the next real emergency alert to really know for sure. I can't tell if this specifically requires their Messenger app or not (I think maybe since I still have nothing at all in the SONY app for this.)
EDIT2: BTW, on the battery saving stuff, turning off WiFi -- as already discussed -- won't help much at all. In fact, it's mostly useless. In fact, if you leave data on and things start using it, that will hurt more. As far as 3g versus 4g goes, it takes significantly longer on 3g for even a small amount of data so while it uses less power, it uses it for longer and the net result is very little savings there too. To my mind at least, it's a much better solution to use Greenify to keep the apps I don't actually need running in the background all the time -- particularly those that like to phone home, but have no actual need to do so -- from actually running. (It doesn't work like a task killer killing tasks on a timer where they just restart a little bit later using more resources in the process of doing so but actually closes them down and blocks them from autostarting all the time, though I think maybe it allows them to wake up for just a bit from time to time.) This also can help keep things running a bit better even when not on battery by clearing up some resources since you don't have practically everything basically running 24/7.
On SD card access, I don't think Google plans to change anything for the better there. They've basically decided that it's "necessary" for security to do things this way. I guess mostly because it requires the user to explicitly grant access. But also, Google has been wanting to eliminate SD card support for ages (I guess OEMs pressuring them to let them do the Apple thing? Or maybe they just want to be lazy and not have to bother doing the work to support them. I don't know. But as it's Linux based I don't buy excuses that it's supposed to be really hard or whatever.)
No more download music info & senseme in music app
Sent from my D5803 using XDA-Developers mobile app
I've got a question about sd card as adoptable storage. What happens if my phone gets broken, can I take the card out, and use in a next phone?
Sent from Tapatalk Z3 compact

HTC Music App 8.10 for non-rooted HTC 10

Hello Guys,
Since last week I've tried to include library files to the latest update of HTC Music app (I don't like Google Play Music, personal taste - And I really don't understand why HTC has removed it from the One A9 and HTC10 considering how great those devices are for music). Anyway here is the first version I managed to port.
https://drive.google.com/open?id=0B_BPVbgprz1uUTUtUFpIWF9rSWs
Install it as a standard apk and let me know if it works for you guys.
It works on my unrooted, HTC 10 with android 7.0, and color themes apply normally.
As it uses Sense 7 libs, while this version is normally for Sense 8, and as I was not able to get my hands on the HTC One M9 nougat system files yet, some of the functionalities are missing (HTC Connect) and will make the app crash.
I'll try to update it when I have some more input to work with.
EDIT feb. 6th 2017:
Since chances are better to find what you're looking for there, I post the link to xpirt's thread on Sense apps for generic devices.
Has HTC Music as well as many other things.
HTC Sense™ Home - Themes | New Apps | Sense 7/8 | for all devices
Works on unrooted HTC 10(tw version 6.0)!!!!!love your share( I couldn't sucessfully use the one I downloaded on apkmirror)
Works but with few exceptions ( im with android 7 as well) Visualisations seem not to be working, HTC connect, as you have mentioned.
Play/pause button is static - does not change to play when playing and pause, when paused, unless i reopen the app.
Next/previous buttons do not work as well, untill I reopen the app.
Everything else - perfect, thank you! Hope you can update it soon
nuts77 said:
...and as I was not able to get my hands on the HTC One M9 nougat system files yet...
I'll try to update it when I have some more input to work with.
Click to expand...
Click to collapse
Here is the HTC Music folder from M9_Nougat_4.14.617.6_System_Image, from system/priv-app/ folder.
old.splatterhand said:
Here is the HTC Music folder from M9_Nougat_4.14.617.6_System_Image, from system/priv-app/ folder.
Click to expand...
Click to collapse
Great ! Thanks a lot. I checked and it seems lib files are the same as in the previous sense versions.
Maybe something changed in the framework though...
Would you be so kind to send me the framework apks too, or if you have some storage available, upload the system folder of your ROM dump so I can take a closer look at things ?
Thanks for your help !
nuts77 said:
Great ! Thanks a lot. I checked and it seems lib files are the same as in the previous sense versions.
Maybe something changed in the framework though...
Would you be so kind to send me the framework apks too, or if you have some storage available, upload the system folder of your ROM dump so I can take a closer look at things ?
Thanks for your help !
Click to expand...
Click to collapse
Well, i don't have a M9. I have only downloaded a system.img dump some other guy made available.
If you can unpack an img file, i can give you the link to that download.
On my end, i can't upload the whole unpacked dump, as my internet connection is to slow for that.
But framework folder should be possible (won't be ready before tomorrow, if i'll upload it).
old.splatterhand said:
Well, i don't have a M9. I have only downloaded a system.img dump some other guy made available.
If you can unpack an img file, i can give you the link to that download.
Click to expand...
Click to collapse
Sure, the link would be more than enough Thanks !
nuts77 said:
Sure, the link would be more than enough Thanks !
Click to expand...
Click to collapse
Here we go: https://www.androidfilehost.com/?fid=601307472480698410
That's a great job! I love Htc Gallery Apk too, could you include library files to the latest update of HTC Gallery app??
Thanks!
Amerikano88 said:
That's a great job! I love Htc Gallery Apk too, could you include library files to the latest update of HTC Gallery app??
Thanks!
Click to expand...
Click to collapse
Will try to, for sure. Still trying to igure things out for the Music app (as I said, I'm a complete newbie in APK tweaking), currently fighting with recompiling and signing errors - but when I get a better version of Music I'll look into the gallery.
nuts77 said:
Hello Guys,
Since last week I've tried to include library files to the latest update of HTC Music app (I don't like Google Play Music, personal taste - And I really don't understand why HTC has removed it from the One A9 and HTC10 considering how great those devices are for music). Anyway here is the first version I managed to port.
https://drive.google.com/open?id=0B_BPVbgprz1udDA2RG1JdWpZREk
Install it as a standard apk and let me know if it works for you guys.
It works on my unrooted, HTC 10 with android 7.0, and color themes apply normally.
As it uses Sense 7 libs, while this version is normally for Sense 8, and as I was not able to get my hands on the HTC One M9 nougat system files yet, some of the functionalities are missing (HTC Connect) and will make the app crash.
I'll try to update it when I have some more input to work with.
Click to expand...
Click to collapse
This is amazing. I would love to see the music widget return and be functional. It's so useful to quickly swap to any previously 9 or so recently played albums, synonymous to a CD changer, imo.
Unsure of why HTC would drop this. It is one of the best HTC apps.
Can you add Gallery too..Thanks for the contribution though...
Sent from my Pixel XL using Tapatalk
typhoonikan said:
This is amazing. I would love to see the music widget return and be functional. It's so useful to quickly swap to any previously 9 or so recently played albums, synonymous to a CD changer, imo.
Unsure of why HTC would drop this. It is one of the best HTC apps.
Click to expand...
Click to collapse
You can install the widget apk separately, the one from apkmirror works (it does not refresh as well on other launchers, but you can use the latest plays screen, it works ok).
http://www.apkmirror.com/apk/htc-corporation/htc-music-widget/
OK... Small progress update. I have understood (I guess !) most of the changes to port the app in a fully functional way have to be made in the AndroidManifest.xml file, before the apk is compiled - and signed. So in a few days (depending on how much time I have to spend on this idea !) I should be able to post a 100% functional app - assuming it is possible with Sense 8 stock resources... Then I'll start looking into Gallery app.
Thanks for your support !
Thanks man, it works, BUT, partially.
Here's some bugs I found:
- Tap on next song barely works;
- Tap on last song can only bring me to the start of current song, tap more times won't work;
- Tap no matter which song to play, the last song's title is still on, it won't switch to current song. But the song does play tho.
My device is full stock HTC 10 EU version, on android 6.0.1.
Take your time.
Related to this, might anyone know where the playlist files live that are created in the HTC app? I'd like them to be stored on the SD card so I don't loose them in the case of a wipe. I'm assuming they are .M3u, but searching and poking around in the apps folders gives nothing.
OK... So I didn't make any interesting progress. Basically I decompile original 8.10 apk, add the lib folder, edit one line in AndroidManifest.xml to remove device signature, recompile and sign. At this stage there are still a few bugs I didn't manage to solve - play panel not refreshing, widget not refreshing, and HTC Connect command making the app crash (while the three fingers gesture works perfectly on my HTC10).
Still trying to figure out how the apk in the post linked below (but edited from a previous version) work perfectly...
http://forum.xda-developers.com/ver...app-htc-10-t3379144/post66853084#post66853084
If any talented developer comes around here - help is much welcome !!
Is there any progress? Keep it up
nuts77 said:
Still trying to figure out how the apk in the post linked below (but edited from a previous version) work perfectly...
http://forum.xda-developers.com/ver...app-htc-10-t3379144/post66853084#post66853084
Click to expand...
Click to collapse
Those two apks were taken from originally posted by @xpirt in his thread http://forum.xda-developers.com/android/apps-games/htc-blinkfeed-plugins-devices-08-03-2015-t3049438
Editing AndroidManifest.xml alone, you'll get the not refreshing widget when you select play, pause & so on. You need to edit a few smali code.
Are you guys talking about these Music & Music widget version ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
ckpv5 said:
Those two apks were taken from originally posted by @xpirt in his thread http://forum.xda-developers.com/android/apps-games/htc-blinkfeed-plugins-devices-08-03-2015-t3049438
Editing AndroidManifest.xml alone, you'll get the not refreshing widget when you select play, pause & so on. You need to edit a few smali code.
Are you guys talking about these Music & Music widget version ?
View attachment 3981462 View attachment 3981463 View attachment 3981464
Click to expand...
Click to collapse
If yours are working, it would be nice if you can share them.
On all CM based Nougat roms the HTC Music Widget is crashing for me.

Categories

Resources