I didn't find how to do this, but rather..
@JoelZ9614 over here Fix for MMS in Hangouts - Verizon
I am just sharing with all you peeps.
1. Decompile Hangouts
2. Go to res/xml/apns.xml
Add:
Code:
<apn carrier="LTE - VZW Roaming Internet" mcc="204" mnc="04" apn="VZWINTERNET" type="default,dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - VZW Roaming FOTA" mcc="204" mnc="04" apn="VZWADMIN" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - VZW Roaming IMS" mcc="204" mnc="04" apn="VZWIMS" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - VZW Roaming CBS" mcc="204" mnc="04" apn="VZWAPP" type="cbs,mms" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="EHRPD - VZW Roaming Internet" mcc="204" mnc="04" apn="VZWINTERNET" type="default,dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - VZW Roaming FOTA" mcc="204" mnc="04" apn="VZWADMIN" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - VZW Roaming IMS" mcc="204" mnc="04" apn="VZWIMS" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - VZW Roaming CBS" mcc="204" mnc="04" apn="VZWAPP" type="cbs,mms" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="LTE - VZW Test Internet" mcc="246" mnc="81" apn="VZWINTERNET" type="default,dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - VZW Test FOTA" mcc="246" mnc="81" apn="VZWADMIN" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - VZW Test IMS" mcc="246" mnc="81" apn="VZWIMS" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - VZW Test CBS" mcc="246" mnc="81" apn="VZWAPP" type="cbs,mms" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - VZW Test Internet" mcc="246" mnc="081" apn="VZWINTERNET" type="default,dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - VZW Test FOTA" mcc="246" mnc="081" apn="VZWADMIN" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - VZW Test IMS" mcc="246" mnc="081" apn="VZWIMS" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - VZW Test CBS" mcc="246" mnc="081" apn="VZWAPP" type="cbs,mms" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="EHRPD - VZW Test Internet" mcc="246" mnc="81" apn="VZWINTERNET" type="default,dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - VZW Test FOTA" mcc="246" mnc="81" apn="VZWADMIN" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - VZW Test IMS" mcc="246" mnc="81" apn="VZWIMS" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - VZW Test CBS" mcc="246" mnc="81" apn="VZWAPP" type="cbs,mms" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - VZW Test Internet" mcc="246" mnc="081" apn="VZWINTERNET" type="default,dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - VZW Test FOTA" mcc="246" mnc="081" apn="VZWADMIN" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - VZW Test IMS" mcc="246" mnc="081" apn="VZWIMS" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - VZW Test CBS" mcc="246" mnc="081" apn="VZWAPP" type="cbs,mms" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="Verizon Internet" mcc="310" mnc="004" apn="VZWINTERNET" type="default,dun" protocol="IPV4V6" roaming_protocol="IPV4V6" />
<apn carrier="Verizon FOTA" mcc="310" mnc="004" apn="VZWADMIN" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" />
<apn carrier="Verizon IMS" mcc="310" mnc="004" apn="VZWIMS" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" />
<apn carrier="Verizon CBS" mcc="310" mnc="004" apn="VZWAPP" type="cbs,mms" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" roaming_protocol="IPV4V6" />
<apn carrier="Verizon" mcc="310" mnc="006" apn="internet" type="default,mms,dun" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" />
<apn carrier="Verizon Internet" mcc="310" mnc="006" apn="VZWINTERNET" type="default,dun" protocol="IPV4V6" roaming_protocol="IPV4V6" />
<apn carrier="Verizon FOTA" mcc="310" mnc="006" apn="VZWADMIN" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" />
<apn carrier="Verizon IMS" mcc="310" mnc="006" apn="VZWIMS" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" />
<apn carrier="Verizon CBS" mcc="310" mnc="006" apn="VZWAPP" type="cbs,mms" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" roaming_protocol="IPV4V6" />
<apn carrier="LTE - Verizon Internet" mcc="311" mnc="480" apn="VZWINTERNET" type="default,dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - Verizon FOTA" mcc="311" mnc="480" apn="VZWADMIN" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - Verizon IMS" mcc="311" mnc="480" apn="VZWIMS" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - Verizon CBS" mcc="311" mnc="480" apn="VZWAPP" type="cbs,mms" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="14" />
<apn carrier="LTE - Verizon SUPL" mcc="311" mnc="480" apn="VZW800" type="supl" protocol="IPV4V6" bearer="14" />
<apn carrier="EHRPD - Verizon Internet" mcc="311" mnc="480" apn="VZWINTERNET" type="default,dun" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - Verizon FOTA" mcc="311" mnc="480" apn="VZWADMIN" type="fota" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - Verizon IMS" mcc="311" mnc="480" apn="VZWIMS" type="ims" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - Verizon CBS" mcc="311" mnc="480" apn="VZWAPP" type="cbs,mms" mmsc="http://mms.vtext.com/servlets/mms" protocol="IPV4V6" roaming_protocol="IPV4V6" bearer="13" />
<apn carrier="EHRPD - Verizon SUPL" mcc="311" mnc="480" apn="VZW800" type="supl" protocol="IPV4V6" bearer="13" />
Compile.. and bang you have working MMS in Hangouts for Verizon carrier..
To Fix AT&T.. Nevermind, been told AT&T is functioning...
Also to adjust... MMS mesage size
edit res/xml/mms-config.xml
Worked perfectly. Thanks!
jedimyndtryx said:
Worked perfectly. Thanks!
Click to expand...
Click to collapse
No problem...
Gunthermic said:
I didn't find how to do this, but rather..
@JoelZ9614 over here Fix for MMS in Hangouts - Verizon
I am just sharing with all you peeps.
1. Decompile Hangouts
2. Go to res/xml/apns.xml
l
Click to expand...
Click to collapse
can you upload the apk with the updated vzw apns please?...This is way above my paygrade to do myself, thanks in advance.
millerd79 said:
can you upload the apk with the updated vzw apns please?...This is way above my paygrade to do myself, thanks in advance.
Click to expand...
Click to collapse
If you follow the link I included in the OP, he has it posted. I didnt want to steal his complete thunder sir..
I opened theis so other Dev's could also do the edit.
millerd79 said:
can you upload the apk with the updated vzw apns please?...This is way above my paygrade to do myself, thanks in advance.
Click to expand...
Click to collapse
Its the first post in the link that Gunthermic linked to.
For me: I deleted all updates in Play Store. Deleted the original Hangouts.apk in System/App. Moved the modified APK to that location. Changed permissions. Rebooted. SAS! Done.
Good luck
jedimyndtryx said:
Its the first post in the link that Gunthermic linked to.
For me: I deleted all updates in Play Store. Deleted the original Hangouts.apk in System/App. Moved the modified APK to that location. Changed permissions. Rebooted. SAS! Done.
Good luck
Click to expand...
Click to collapse
so I uninstalled the old hangout via root explorer. DL the new version from the other thread and copied the file to system/app and rebooted.
everytime I try to send a mms hangouts FC....
the only thing I see that you did different was change the permissions. What did you change them to?
millerd79 said:
so I uninstalled the old hangout via root explorer. DL the new version from the other thread and copied the file to system/app and rebooted.
everytime I try to send a mms hangouts FC....
the only thing I see that you did different was change the permissions. What did you change them to?
Click to expand...
Click to collapse
RW-R--R--
Very nice find bro!
jedimyndtryx said:
RW-R--R--
Click to expand...
Click to collapse
This is what I have now
I deleted all updates and the original app then moved this one to system app and still force closes.
Sent from my VZW Galaxy Note 3
millerd79 said:
This is what I have now
Click to expand...
Click to collapse
Untick the Write Access on the 2 bottom right. Should be RW, then only R, and R then Reboot.
jedimyndtryx said:
Untick the Write Access on the 2 bottom right. Should be RW, then only R, and R then Reboot.
Click to expand...
Click to collapse
I did that and I still am fcing when sending MMS
Still FCing here as well.
Sent from my SM-N900V using Tapatalk
Folks,
This thread was made so Dev's could add the functionalty to Hangouts, not a place to ask questions how to install, and run the app. I appriciate all those trying to help, but all these type of questions should be in Q&A.
Last piece of advice.
1. Get the app from the link provided in the OP.
2. You must remove older versions
Talk.apk
Hangouts.apk
HangOuts.apk
com.google.android.talk-*.apk
Thats just some examples. Also if their is a .odex file..
3. Copy the file over to system/app
4. Change premission to rw-r-r
5. reboot, enjoy
If you have problems where it FC's.. I know the problem.. Your mms database is corrupt.. How? Most likely you restored you old database when transfering to your new phone. The MMS database from Android 4.2.2 in not compatiable with Android 4.3 with Hangouts. The MMS database is fine for just Android 4.3, but becuase of the way that Hangouts works, it is not...
If you delete your database and then go into Application Manager and remove cache/wipe Hangouts. Restart it just works then.
I have not tried it by going into App Manager and wiping messages from there. I removed the databases completely..
I love helping people, but when threads get off subject, moderators close threads. Don't want it.. lol
How do you wipe the database?
Sent from my Nexus 7 using xda app-developers app
Bsmith0731 said:
How do you wipe the database?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I would suggest using the Application Manager first to wipe both caches/data..
Which database
Hangouts is already uninstalled
Sent from my SM-N900V using xda app-developers app
does video calling work? and thank you...no FC for me on sms integration. Awesome!
Bsmith0731 said:
Which database
Hangouts is already uninstalled
Sent from my SM-N900V using xda app-developers app
Click to expand...
Click to collapse
I would do Messages if it was Fc'ing trying to MMS.
yakitori2 said:
does video calling work? and thank you...no FC for me on sms integration. Awesome!
Click to expand...
Click to collapse
I am sorry, but this thread is for Dev's on How to fix Hangouts to be able to MMS if your on Verizon.. Video calling function works if you flash the correct lib file while installing the apk.
Related
I hated how the battery percentage took up status bar real estate, but loved that I could show it. So I looked at the Epic 4G Touch for inspiration and figured out how to bring the small battery percent to the Galaxy S III
Decompile SystemUI.apk and go to SystemUI\res\layout and open tw_status_bar.xml
Look (around line 13 in Notepad++) for:
Code:
<LinearLayout android:gravity="center" android:orientation="horizontal" android:id="@id/signal_battery_cluster" android:paddingLeft="2.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent">
<include android:id="@id/signal_cluster" android:layout_width="wrap_content" android:layout_height="wrap_content" layout="@layout/tw_signal_cluster_view" />
<TextView android:textSize="12.0dip" android:textColor="#ffa6a6a6" android:layout_gravity="center" android:id="@id/battery_text" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="@string/status_bar_network_name_separator" />
<ImageView android:gravity="center" android:id="@id/battery" android:layout_width="wrap_content" android:layout_height="wrap_content" />
</LinearLayout>
Replace it all with this:
Code:
<LinearLayout android:gravity="center" android:orientation="horizontal" android:id="@id/signal_battery_cluster" android:paddingLeft="2.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent">
<include android:id="@id/signal_cluster" android:layout_width="wrap_content" android:layout_height="wrap_content" layout="@layout/tw_signal_cluster_view" />
<FrameLayout android:gravity="center" android:paddingLeft="4.0dip" android:paddingRight="2.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent">
<ImageView android:gravity="center" android:id="@id/battery" android:layout_width="wrap_content" android:layout_height="fill_parent" />
<TextView android:textSize="7.0dip" android:typeface="sans" android:textStyle="bold" android:textColor="#ffffffff" android:layout_gravity="bottom|center" android:id="@id/battery_text" android:visibility="gone" android:layout_width="wrap_content" android:layout_height="wrap_content" android:text="@string/status_bar_network_name_separator" android:shadowColor="#ffffffff" android:shadowDx="0.0" android:shadowDy="0.0" android:shadowRadius="1.0" />
</FrameLayout>
</LinearLayout>
After you do that just save, recompile and get it back on your device.
I highly recommend a blue battery icon for this mod. With the stock TouchWiz green, it is very hard to read the percentage.
Here is a screen shot of mine
{
"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"
}
Great find man.....
Thanks! I'm very happy with it. Even more since this is my first contribution to XDA.
Sent from my SPH-L710 using xda app-developers app
Tsudeily said:
Thanks! I'm very happy with it. Even more since this is my first contribution to XDA.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Awesome! Great job!
That is pretty freaking sweet! Then you don't have the number thing to the left anymore. More room in your status bar!
My exact goal. I am glad to see people are enjoying it as much as I am.
Sent from my SPH-L710 using xda app-developers app
Great job.. I'll throw this in my next ROM with credit to you good sir
Can u make this into a flashable zip please?!
Sent from my SPH-L710 using xda app-developers app
jorv976 said:
Can u make this into a flashable zip please?!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
/agree, and if you do will it work ok stock deodexed rom
Sent from my SPH-L710 using Tapatalk 2
I have attached a stocked deodex'd copy of the mod for you. Green icons still remain. If needed, I can upload one with blue icons, or a copy of the one I use.
jorv976 said:
Can u make this into a flashable zip please?!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
bog3nator said:
/agree, and if you do will it work ok stock deodexed rom
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Tsudeily said:
I have attached a stocked deodex'd copy of the mod for you. Green icons still remain. If needed, I can upload one with blue icons, or a copy of the one I use.
Click to expand...
Click to collapse
It worked awesome and works good with the green. Thank you very much
Sent from my SPH-L710 using Tapatalk 2
do u no how to remove the % sign by any chance?
This mod is based on this thread. I tried to increase the bitrate of our CM9's stock camera from 6mbps into 12mbps. And it works well:
{
"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"
}
This can be done by editing these lines on media_profiles.xml on system/etc:
Find these lines:
Code:
<EncoderProfile quality="720p" fileFormat="mp4" duration="60">
<Video codec="h264"
bitRate="6000000"
width="1280"
height="720"
frameRate="30" />
<Audio codec="aac"
bitRate="128000"
sampleRate="48000"
channels="2" />
</EncoderProfile>
<EncoderProfile quality="480p" fileFormat="mp4" duration="60">
<Video codec="h264"
bitRate="3000000"
width="720"
height="480"
frameRate="30" />
<Audio codec="aac"
bitRate="128000"
sampleRate="48000"
channels="2" />
</EncoderProfile>
And edit them into these:
Code:
<EncoderProfile quality="720p" fileFormat="mp4" duration="60">
<Video codec="h264"
bitRate="12000000"
width="1280"
height="720"
frameRate="30" />
<Audio codec="aac"
bitRate="128000"
sampleRate="48000"
channels="2" />
</EncoderProfile>
<EncoderProfile quality="480p" fileFormat="mp4" duration="60">
<Video codec="h264"
bitRate="6000000"
width="720"
height="480"
frameRate="30" />
<Audio codec="aac"
bitRate="128000"
sampleRate="48000"
channels="2" />
</EncoderProfile>
Save, wipe cache and dalvik cache. If you got FC on the Camera, wipe data of the Camera apk.
hey can tell me what does this do to camera?? it works on slimbean btw. i just want to know what it does, like speeding the frames, improving quality etc
7amada100 said:
hey can tell me what does this do to camera?? it works on slimbean btw. i just want to know what it does, like speeding the frames, improving quality etc
Click to expand...
Click to collapse
It's improving the quality. It's like bit per second. Higher the bits, higher the quality will be
dewadg said:
It's improving the quality. It's like bit per second. Higher the bits, higher the quality will be
Click to expand...
Click to collapse
Cool, thanks for sharing!
Sent from my GT-I8150 using xda app-developers app
7amada100 said:
Cool, thanks for sharing!
Sent from my GT-I8150 using xda app-developers app
Click to expand...
Click to collapse
Thanks for confirming it's working too
good job Bro
Adi_ai****eru said:
good job Bro
Click to expand...
Click to collapse
Thank you bro
Looks pretty cool to me..Thx so much.
Warren87 said:
Looks pretty cool to me..Thx so much.
Click to expand...
Click to collapse
Thank you for trying
Decompile camera.apk brow?
Sent from my GT-I8150 using xda premium
mikrotik said:
Decompile camera.apk brow?
Sent from my GT-I8150 using xda premium
Click to expand...
Click to collapse
Can you read it's only tweak on media_profiles.xml on system/etc/
does it mean that we will need more space for bigger video file sizes?
dewadg said:
Can you read it's only tweak on media_profiles.xml on system/etc/
Click to expand...
Click to collapse
owh ..
sorry
vetusa2 said:
does it mean that we will need more space for bigger video file sizes?
Click to expand...
Click to collapse
Well of course higher quality needs more size. But not a lot though, just don't worry you will have enough space for other files. Unless you have a really small sdcard that would be sad.
Sent from my GT-I8150 using xda app-developers app
vetusa2 said:
does it mean that we will need more space for bigger video file sizes?
Click to expand...
Click to collapse
Logically...Yes...but the fps down from 27 to 24/s...
cifoel said:
Logically...Yes...but the fps down from 27 to 24/s...
Click to expand...
Click to collapse
It's randomly changed. I often got between 24-27 ~
i think it will be better if you change channels to 2
Channel 2? For what is that?
hadidjapri said:
i think it will be better if you change channels to 2
Click to expand...
Click to collapse
stereo sound. 1 channel means mono
hadidjapri said:
stereo sound. 1 channel means mono
Click to expand...
Click to collapse
Yeah, I've just realized that. Will test it
I was wondering what is the best DPI for my Galaxy Note 2, I tried other people's suggestions but it didn't work for me so I was wondering how Google decided on their DPI. Considering they're in charge of Android they must know the optimal level so I used the Nexus 7 and the Nexus 4 as reference:
{
"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"
}
So if Google designed a 5.5 inch screen device with 720x1280 resolution, it would most likely be at 270 DPI
I know this won't help a lot of you how it helped me but just thought I'd share it just on the hunch that it might at least help the 1% :silly:
I dropped my dpi to 268(closest I could get on liquidsmooth) and it's great. Your totally right dude.
Sent from my GT-N7105 using xda app-developers app
webbles17 said:
I dropped my dpi to 268(closest I could get on liquidsmooth) and it's great. Your totally right dude.
Sent from my GT-N7105 using xda app-developers app
Click to expand...
Click to collapse
lol thank dude!
268 looks great, on beanstalk ROM thanks!
268 looks great on CleanROM 4.8! Funny how the only apps that don't line up right are the Samsung TouchWiz apps *snicker*
Sent from a van down by the river on an AT&T Galaxy Note 2 and Tapatalk.
Indeed. 268/270 is a great place to be.
Sent from The Bacon Pope's Galaxy Note 2
Hate to ask the obvious question, what is the easiest way to change the DPI? Build prop edit?
opuscroakus said:
Hate to ask the obvious question, what is the easiest way to change the DPI? Build prop edit?
Click to expand...
Click to collapse
That's how I always do it.
Sent from The Bacon Pope's Galaxy Note 2
Thanks for the tip. Running 270 and it looks great.
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
No problem
rohail6 said:
I was wondering what is the best DPI for my Galaxy Note 2, I tried other people's suggestions but it didn't work for me so I was wondering how Google decided on their DPI. Considering they're in charge of Android they must know the optimal level so I used the Nexus 7 and the Nexus 4 as reference:
View attachment 1899144
So if Google designed a 5.5 inch screen device with 720x1280 resolution, it would most likely be at 270 DPI
I know this won't help a lot of you how it helped me but just thought I'd share it just on the hunch that it might at least help the 1% :silly:
Click to expand...
Click to collapse
Just changed to 270 DPI, and love it... Need to find right launcher to fully utilize the whole screen. Looks kind odd with TWLauncher..
Thanks for the finding!
dvdmkr said:
Just changed to 270 DPI, and love it... Need to find right launcher to fully utilize the whole screen. Looks kind odd with TWLauncher..
Thanks for the finding!
Click to expand...
Click to collapse
Nova Launcher at 270 DPI with 5x6 Desktop Grid and Icon Size at 110%.
Worth a try. Good luck.
Got a question need help ive changed my dpi to 240 and never had any problems but now my dialer wont come up and I got the muti dpi dialer and have tried reflashing but still nothing but I can call ppl from the contacts but I can't dial a number
Sent from my SAMSUNG-SGH-I317 using xda premium
275
Sent from my GT-N7105 using xda app-developers app
terpin32 said:
Got a question need help ive changed my dpi to 240 and never had any problems but now my dialer wont come up and I got the muti dpi dialer and have tried reflashing but still nothing but I can call ppl from the contacts but I can't dial a number
Sent from my SAMSUNG-SGH-I317 using xda premium
Click to expand...
Click to collapse
Never tried 240. Maybe it's the specific multi DPI dialer file you have? But by all means you're free to try 270. Every single thing works perfect, just the dialer is a bit to the left. It's like the sweet spot the Note 2 should've came with, you just gotta give it some time. But yeah sorry I don't have an actual answer to your question.
270
rohail6 said:
Never tried 240. Maybe it's the specific multi DPI dialer file you have? But by all means you're free to try 270. Every single thing works perfect, just the dialer is a bit to the left. It's like the sweet spot the Note 2 should've came with, you just gotta give it some time. But yeah sorry I don't have an actual answer to your question.
Click to expand...
Click to collapse
I tried going back to stock at 320 and it still won't work but im using the file multi dpi dialer note2 (4.1.2) universal twrp.zip
Sent from my SAMSUNG-SGH-I317 using xda premium
cwhitney24 said:
That's how I always do it.
Sent from The Bacon Pope's Galaxy Note 2
Click to expand...
Click to collapse
Mind sharing which line you change? I see the same line twice - once within system.prop for smdk4x12 and within ADDITIONAL_BUILD_PROPERTIES - do you change both?
ro.sf.lcd_density=320
Anyone have a SS they're willing to post?
dawheat said:
Mind sharing which line you change? I see the same line twice - once within system.prop for smdk4x12 and within ADDITIONAL_BUILD_PROPERTIES - do you change both?
ro.sf.lcd_density=320
Anyone have a SS they're willing to post?
Click to expand...
Click to collapse
I changed both and I saw I had to change the de.robv.android.xposed.mods.tweakbox file and add the last part <int name="dpioverride/com.sec.android.app.camera/density" value="240" /> to get it to change and it worked for the longest time but just recently hasn't been working
<?xml version='1.0' encoding='utf-8' standalone='yes' ?>
<map>
<int name="low_battery_low" value="15" />
<boolean name="unplug_turns_screen_on" value="true" />
<int name="long_home_press_behaviour" value="2" />
<boolean name="crt_off_effect" value="false" />
<boolean name="battery_full_notification" value="true" />
<boolean name="phone_enable_sip" value="false" />
<int name="low_battery_critical" value="5" />
<boolean name="phone_vibrate_waiting" value="false" />
<boolean name="crt_effect_orientation" value="false" />
<int name="num_signal_bars" value="4" />
<boolean name="phone_call_recording" value="false" />
<boolean name="show_ongoing_ime_switcher" value="true" />
<int name="low_battery_close" value="20" />
<boolean name="phone_increasing_ringer" value="true" />
<boolean name="volume_keys_skip_track" value="false" />
<boolean name="crt_on_effect" value="false" />
</map>
<int name="dpioverride/com.sec.android.app.camera/density" value="240" />
Sent from my SAMSUNG-SGH-I317 using xda premium
dawheat said:
Mind sharing which line you change? I see the same line twice - once within system.prop for smdk4x12 and within ADDITIONAL_BUILD_PROPERTIES - do you change both?
ro.sf.lcd_density=320
Anyone have a SS they're willing to post?
Click to expand...
Click to collapse
Exactly. Edit the ro.sf.lcd_density
Sent from The Bacon Pope's Galaxy Note 2
***Enable home and lock button in status bar***
Tools required:
-Any tool which can decompile and recompile apk (e.g apktool i use)
-Notepad++
GUIDE:
STEP1:
Decompile your systemui.apk
STEP2:
Navigate to res/layout/tw_status_bar.xml and open it with notepad++
STEP3:
FIND:
Code:
android:id="@id/doNotDisturbIcon"
#thanks to @engloa
And paste the below code after id/doNotDisturbIcon line
Code:
<com.android.systemui.statusbar.policy.KeyButtonView android:gravity="right" android:id="@id/home" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginRight="0.0dip" android:src="@drawable/ic_sysbar_home" android:singleLine="true" android:layout_alignParentRight="true" android:contentDescription="@string/accessibility_back" systemui:keyCode="3" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
#this will add home button on the right side
STEP 4:
Find:
Code:
<com.android.systemui.statusbar.policy.Clock android:textSize="@dimen/status_bar_clock_text_size" android:textColor="#ff9a9a9a" android:ellipsize="none" android:gravity="left|center" android:id="@id/clock" android:paddingLeft="3.0dip" android:layout_width="wrap_content" android:layout_height="fill_parent" android:singleLine="true" android:includeFontPadding="false" />
AND paste the below code after the above code
Code:
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/back" android:layout_width="wrap_content" android:layout_height="wrap_content" android:layout_marginLeft="0.0dip" android:src="@drawable/ic_sysbar_lock" android:singleLine="true" android:layout_toRightOf="@id/recent_apps" android:layout_alignParentLeft="true" android:contentDescription="@string/accessibility_back" systemui:keyCode="26" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
#this will enable lock button on the left side
STEP5:
Download the pngs from the attachment and paste them in drawable-hdpi
STEP6:
Recompile your systemui.apk
Result:
{
"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"
}
FILES:
https://www.dropbox.com/sh/ohmhrlnkdbz4oca/b1KnsUlYHr
Download link for Mods:
AROMA_HOME_LOCK_XWMS3
credits:
@engloa for helping me in moving the home button on the right..tnx buddy. @_Sale_ for his systemui.apk
You're welcome buddy
I did a little tinkering and placed the following code after id/doNotDisturbIcon
Code:
<com.android.systemui.statusbar.policy.KeyButtonView android:gravity="right" android:id="@id/home" android:layout_width="wrap_content" android:layout_height="wrap_content" android:src="@drawable/ic_sysbar_home" android:layout_alignParentLeft="true" android:singleLine="true" android:contentDescription="@string/accessibility_back" systemui:keyCode="3" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
This way, when notifications comes, the ticker doesn't overlap the status bar icons
Awesome work my dear friend 5*
Very awesome to see tuts like these here. Thanks mate!
As avirk said.. 5*
avirk said:
Awesome work my dear friend 5*
Click to expand...
Click to collapse
TheGovernment said:
Very awesome to see tuts like these here. Thanks mate!
As avirk said.. 5*
Click to expand...
Click to collapse
It dont deserve 5*.
Just a simple guide imo
Anyways thnx buddies
Sent from my GT-I9100 using Tapatalk 2
corruptionfreeindia said:
It dont deserve 5*.
Just a simple guide imo
Anyways thnx buddies
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Anything that somehow contributes to this awesome community deserves 5* :good:
XDA'd via my Galaxy
engloa said:
You're welcome buddy
I did a little tinkering and placed the following code after id/doNotDisturbIcon
Code:
This way, when notifications comes, the ticker doesn't overlap the status bar icons
Click to expand...
Click to collapse
Thanks a lot mate.
I was doing this
@id/ticker android: paddingLeft="4.0dip"
But no changes lol
Bad
Sent from my GT-I9100 using Tapatalk 2
Subscribed
Happy New Year Man
Troubadour666 said:
Subscribed
Happy New Year Man
Click to expand...
Click to collapse
Same to u m8
Hope u had a great party.
Sent from my GT-I9100 using Tapatalk 2
avirk said:
Awesome work my dear friend 5*
Click to expand...
Click to collapse
+1
Sent from my NeatRom'ed GT-I9300 wifi hotspoting from my NeatRom'ed GT-I9100
corruptionfreeindia said:
GUIDE:
STEP1:
Decompile your systemui.apk
STEP2:
Navigate to res/layout/tw_status_bar.xml and open it with notepad++
STEP3:
FIND:
Code:
android:id="@id/doNotDisturbIcon"
#thanks to @engloa
And paste the below code after id/doNotDisturbIcon line
Code:
#this will add home button on the right side
STEP 4:
Find:
Code:
AND paste the below code after the above code
Code:
Click to expand...
Click to collapse
Missing strings...
Sent from my S3 with skippioROM cooked by linus98
linus98 said:
Missing strings...
Sent from my S3 with skippioROM cooked by linus98
Click to expand...
Click to collapse
Oops..am very sorry.
It happens often whenever I edit thru tapa..the code disappears.
Am updating
Sent from my GT-I9100 using Tapatalk 2
Great Work Mate.
Nice share, thanks...
Is there any chance of placing home button next to lock button? I mean in the right side too
xddd00 said:
Nice share, thanks...
Is there any chance of placing home button next to lock button? I mean in the right side too
Click to expand...
Click to collapse
Place @id/home line after @id/back line
Sent from my GT-I9100 using Tapatalk 2
corruptionfreeindia said:
Place @id/home line after @id/back line
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Thanks dude
A very easy example for starters. Good job.
You made the front page news o_o
Congrats CFI :thumbup::thumbup:
Sent from my GT-I9100 using Tapatalk 2
Thank u all very much
Sent from my GT-I9100 using Tapatalk 2
This is native call record for Kitkat NB4. Deodexed only. Will work on all custom US TW ROMs. Also removed increment ringing as well as the ugly and pointless end call screen. You hang up and it goes right back to the last screen you were on before the call. Enjoy
DOWNLOAD
Just download and flash. Nothing else needed.
For developers. Feel free to use in your ROM, credit would be appreciated. If you want to do it yourself check out my commit on my github - Link to how to.
Kitkat doesn't support call record stock. To get it record correctly you have to modify the mixer_paths.xml under system/etc. Otherwise you only get static when you play the recording.
Just add the blue section and reboot. Enjoy
Code:
<!-- TX part -->
<path name="audio-record">
<ctl name="MultiMedia1 Mixer SLIM_0_TX" value="1" />
</path>
<path name="audio-record bt-sco">
<ctl name="MultiMedia1 Mixer AUX_PCM_UL_TX" value="1" />
</path>
[COLOR="Blue"] <!-- incall recording -->
<path name="incall-rec-uplink">
<ctl name="MultiMedia1 Mixer VOC_REC_UL" value="1" />
</path>
<path name="incall-rec-downlink">
<ctl name="MultiMedia1 Mixer VOC_REC_DL" value="1" />
</path>
<path name="incall-rec-uplink-and-downlink">
<ctl name="MultiMedia1 Mixer VOC_REC_UL" value="1" />
<ctl name="MultiMedia1 Mixer VOC_REC_DL" value="1" />
</path>[/COLOR]
<!-- call part -->
<path name="voice-call">
<ctl name="SLIM_0_RX_Voice Mixer CSVoice" value="1" />
<ctl name="Voice_Tx Mixer SLIM_0_TX_Voice" value="1" />
</path>
{
"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"
}
You . rock . my . sock !!!
Thx!
Sent from my SM-G900T using Tapatalk
sexyyyyyyy!!
Nice
Sent from my SM-G900T using Tapatalk
Jamison904 said:
Will work on all custom US TW ROMs.
Click to expand...
Click to collapse
What about non-US TW?
It should work. Let me know if not.
Sent from my SM-N900T using Tapatalk
Hi jamison I dl and flashed the zip file and can't find the call record button while im on the phone.. im on wicked k.k v.1 using compulsion kernel.. if u could give me the right instructions how to install it that would be great.. thx in adv
Sent from my SM-N900T using XDA Premium 4 mobile app
Jamison904 said:
It should work. Let me know if not.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
It is posible to make it auto record?
Thanks
Has anyone tried this on NE6? I may try this later when I get to first make a backup. Just not sure if I have time today.
DriftorX said:
Has anyone tried this on NE6? I may try this later when I get to first make a backup. Just not sure if I have time today.
Click to expand...
Click to collapse
Did you ever end up trying this?
DeeXii said:
Did you ever end up trying this?
Click to expand...
Click to collapse
Does Not work on E6.
Jamison904 said:
It should work. Let me know if not.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Doesn't work. com.android.phone stops working.
Fwiw - this mod does not seem to be necessary on ne6 - the edits that were necessary on nb4 already exist on ne6 (though they look slightly different)
ACR is working fine for me on NE6 (no root).... again, this is NOT Microphone recording, it sounds excellent.
It only wanted to work when I changed the directory from "/storage/emulated/0/ACRCalls" to "/storage/sdcard0/ACRCalls" despite both of these directories pointing at exactly the same place. I Only tested AMR and MP4-HQ but they both work fine (although AMR sounds like complete crap).
EDIT: Skvalex's call recorder works even better (sounds a lot less muffled) and works fine with the standard API, you really don't even need to configure it. I will reiterate, its not mic recording and works without root on NE6.
https://play.google.com/store/apps/details?id=com.skvalex.callrecorder
now I'm just gonna cross my fingers and hope samsung/t-mobile doesn't take out the API in the next OTA (as I can only guess they added it by mistake).
Any luck for nf1?
Sent from my SM-N900T using XDA Free mobile app
ezsoulja said:
Any luck for nf1?
Sent from my SM-N900T using XDA Free mobile app
Click to expand...
Click to collapse
It seems the changes put in place on NE6 have carried over to NF1 - the mod here still should not be needed.
So this will work on nf1?
Nope. Doesn't not work. Phone won't boot past Samsung logo
Sent from my SM-N900T using XDA Premium 4 mobile app
Hi mate,
Can you help me with S3 Neo call rec mod?
Thanks!
Edit:
I made it myself.
thx