Does anyone feel free to port this .apk for 2.1?
It's SDK 8 but as we know many things can be backported
http://rs977.rapidshare.com/files/389687602/Launcher2.apk
Regards,
Tim
i made a froyo themed launcher pro in the launcher pro themes ^_^
best you can get for now
seraphimserapis said:
Does anyone feel free to port this .apk for 2.1?
It's SDK 8 but as we know many things can be backported
http://rs977.rapidshare.com/files/389687602/Launcher2.apk
Regards,
Tim
Click to expand...
Click to collapse
If I just push it, would it working?
Andrewtst said:
If I just push it, would it working?
Click to expand...
Click to collapse
Nope I tried it - didn't work - it's SDK 8 not 7.
When you reboot you'll get a bootloop.
Nope tried already, Android can't parse the package on install and if pushed i can't chose Launcher only LauncherPro and adv. Launcher :S even if it's in the /system/app folder it won't work at all :S
I just try also, not working also.
how about unzipping the apk, importing it into eclipse sdk, changing apk version 8 -> 7 and rebuilding it?
But the 3D effect(yet), mine is like it plus a lot more customizable http://forum.xda-developers.com/showthread.php?t=684874
AnderWeb said:
But the 3D effect(yet), mine is like it plus a lot more customizable http://forum.xda-developers.com/showthread.php?t=684874
Click to expand...
Click to collapse
ADW Launcher is very nice, i use it as my main launcher. But the bigger icon on the new stock launcher is very tempting
DocRambone said:
ADW Launcher is very nice, i use it as my main launcher. But the bigger icon on the new stock launcher is very tempting
Click to expand...
Click to collapse
Yes, and the look is not quite accurate either. I rather have the actual thing than simply a replication, that was based off the first Froyo desktop picture I believe, when there are currently more clearer images available.
Eclair~ said:
Yes, and the look is not quite accurate either. I rather have the actual thing than simply a replication, that was based off the first Froyo desktop picture I believe, when there are currently more clearer images available.
Click to expand...
Click to collapse
Metamorph it
SO, did anyone try to resign it by now?
bump for an answer!
I had a bit of a go with resigning it, the problem is the Froyo packages are in a new format. apktool, samili don't work too well with the formats.
You can edit /system/build.prop and set the sdk version number in there for the whole phone but the older system doesn't know how to read the new format.
Code:
W/PackageParser( 143): Unknown element under <manifest>: original-package at /system/app/Launcher2.apk Binary XML file line #26
W/ResourceType( 143): Bad string block: string #553 extends to 12157, past end at 11140
W/PackageParser( 143): /system/app/Launcher2.apk
W/PackageParser( 143): java.lang.IndexOutOfBoundsException
W/PackageParser( 143): at android.content.res.StringBlock.nativeGetString(Native Method)
W/PackageParser( 143): at android.content.res.StringBlock.get(StringBlock.java:81)
W/PackageParser( 143): at android.content.res.AssetManager.getPooledString(AssetManager.java:258)
W/PackageParser( 143): at android.content.res.TypedArray.loadStringValueAt(TypedArray.java:675)
W/PackageParser( 143): at android.content.res.TypedArray.getValueAt(TypedArray.java:659)
W/PackageParser( 143): at android.content.res.TypedArray.peekValue(TypedArray.java:620)
W/PackageParser( 143): at android.content.pm.PackageParser.parsePackageItemInfo(PackageParser.java:1563)
W/PackageParser( 143): at android.content.pm.PackageParser.parsePermission(PackageParser.java:1150)
W/PackageParser( 143): at android.content.pm.PackageParser.parsePackage(PackageParser.java:742)
W/PackageParser( 143): at android.content.pm.PackageParser.parsePackage(PackageParser.java:390)
W/PackageParser( 143): at com.android.server.PackageManagerService.scanPackageLI(PackageManagerService.java:2072)
W/PackageParser( 143): at com.android.server.PackageManagerService.scanDirLI(PackageManagerService.java:2022)
W/PackageParser( 143): at com.android.server.PackageManagerService.<init>(PackageManagerService.java:602)
W/PackageParser( 143): at com.android.server.PackageManagerService.main(PackageManagerService.java:350)
W/PackageParser( 143): at com.android.server.ServerThread.run(SystemServer.java:129)
I did manage to get a basic apk dump using apktool, converted the binary xml to normal xml in the hopes of editing out the offending line but upon installing the repackaged file I get a thing about corrupt binary XML (even though it should be non-binary now).
Also as there is no way to decompile the new odex format it might not work on the older Dalvik vm since it had a lot of work done.
In any case according to @googleio: "Froyo will be made available to OEMs and the open source community in the coming weeks.", at that point we should just be able to make a proper apk and the mods can get going properly.
I have a buggy but somewhat working version of froyo's Launcher2 for 2.1 which works with one major bug -- icons, widgets, etc don't appear on any of the other homescreens except the default one. Has anyone seen this before or has an idea how to fix?
Related
Hi,
I was trying to modify status_bar.xml in framework-res.apk. I downloaded the source from git, and started changing the xml files. Then I used aapt to package them into an apk. However, when I move the binary status_bar.xml to some other framework-res.apk that worked before, I get stuck in a boot loop. I compared both status_bar.xml's in a hex editor, and it seems aapt inserted a lot of zero bytes (see screenshot, left the new one, right is the working one), at first I thought it might have something to do with UTF-8, but setting another encoding didn't do anything. Anyone know what I'm doing wrong here?
Yeah, you're right, file on the right was built using new encoding introduced in Froyo and it can't work on Android <= 2.1 . It's used when you set minSdkVersion to 8.
But you said, that this one is ok and that normal encoding ("normal", cause it was here for last 2 years) on the left isn't working. I don't really know, why.
Brut.all said:
Yeah, you're right, file on the right was built using new encoding introduced in Froyo and it can't work on Android <= 2.1 . It's used when you set minSdkVersion to 8.
But you said, that this one is ok and that normal encoding ("normal", cause it was here for last 2 years) on the left isn't working. I don't really know, why.
Click to expand...
Click to collapse
The status_bar.xml on the right is from this AOSP Desire rom. I just tried to built it with minSdkVersion set to 8 and it seems to work. Thanks for the help!
Got one more question on the subject. It's working now, in the sense that I edit the XML file, use aapt to build an apk, then move the binary xml to the original framework-res.apk. When I try to sign the homebuilt framework-res.apk and boot my phone it goes into a boot loop. Is there any way that you can replace framework-res.apk without resigning all other apps?
I think you must install it through an update.zip file.
And right you are. Thank you very much
And here I am again. It does seem to work, signing it and putting it into an update.zip, however, when I boot my phone, it gets to the sim unlock screen, and it starts FCing. Logcat has the following messages:
Code:
W/PackageManager( 400): Unknown permission android.permission.VIBRATE in package com.google.android.gsf
W/PackageManager( 400): Unknown permission android.permission.WAKE_LOCK in package com.google.android.gsf
W/PackageManager( 400): Unknown permission android.permission.WRITE_CONTACTS in package com.google.android.gsf
Basically it shows these messages for all applications, for all permissions. The weird thing is, I tried this yesteray, right after your post and it worked fine. But now it doesn't work anymore. This is, by the way, the newest framework-res.apk from git, no changes.
So, I extracted my Tweetdeck .apk and edited the .9 inside for the widget; I recompiled (AKA renamed the .zip back to .apk) and now the application won't install. "Application Not Installed" it says, after saying "Installing...". Anybody know how to fix this? I didn't edit anything but that .9.png....
obsidianchao said:
So, I extracted my Tweetdeck .apk and edited the .9 inside for the widget; I recompiled (AKA renamed the .zip back to .apk) and now the application won't install. "Application Not Installed" it says, after saying "Installing...". Anybody know how to fix this? I didn't edit anything but that .9.png....
Click to expand...
Click to collapse
if you edit a market app (or any nonsystem app) you have to resign the apk...if you use apkmanager put the app in "place here for signing" and then hit option 16 (in windows version anyway)
Alright, so, the file I edited is in res/drawable-hdpi . It's the widget_bg.9.png. I install the app (it worked great, thanks!), but... the bar widget looks no different.
I've been trying to do this for TWO HOURS... what did I do wrong, man?
Sorry for double post, but here's my CURRENT error log:
java.io.FileNotFoundException: ..\place-apk-here-for-modding\unsignedunsignedcom.thedeck.android.app-2.apk (The system cannot find the file specified)
at java.util.zip.ZipFile.open(Native Method)
at java.util.zip.ZipFile.<init>(Unknown Source)
at java.util.jar.JarFile.<init>(Unknown Source)
at java.util.jar.JarFile.<init>(Unknown Source)
at com.android.signapk.SignApk.main(SignApk.java:437)
Could Not Find C:\Users\Owner\Desktop\apk_manager_4.9\place-apk-here-for-modding\../place-apk-here-for-modding/unsignedunsignedcom.thedeck.android.app-2.apk
When trying to sign with apkmanager. Well, I checked, and that file is in both the "place for modding" and in the "place for signing" folders.
I am facing problem when i edit xml's and try to compile apk
Code:
C:\Users\SARTHAK ACHARYA\Downloads\apk_manager_4.9\other\..\projects\framework-res.apk\res\values\public.xml:3898: error: Public symbol drawable/zzzzzzz_sec_noti_icon_decryption declared here is not defined.
C:\Users\SARTHAK ACHARYA\Downloads\apk_manager_4.9\other\..\projects\framework-res.apk\res\values\public.xml:3899: error: Public symbol drawable/zzzzzzz_sec_noti_icon_encryption declared here is not defined.
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\Users\SARTHA~1\AppData\Local\Temp\APKTOOL5554419900531165905.tmp, -x, -S, C:\Users\SARTHAK ACHARYA\Downloads\apk_manager_4.9\other\..\projects\framework-res.apk\res, -M, C:\Users\SARTHAK [B]ACHARYA\Downloads\apk_manager_4.9\other\..\projects\framework-res.apk\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(Unknown Source)
at brut.androlib.Androlib.buildResourcesFull(Unknown Source)
at brut.androlib.Androlib.buildResources(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.androlib.Androlib.build(Unknown Source)
at brut.apktool.Main.cmdBuild(Unknown Source)
at brut.apktool.Main.main(Unknown Source)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\Users\SARTHA~1\AppData\Local\Temp\APKTOOL5554419900531165905.tmp, -x, -S, C:\Users\SARTHAK ACHARYA\Downloads\apk_manager_4.9\other\..\projects\framework-res.apk\res, -M, C:\Users\SARTHAK ACHARYA\Downloads\apk_manager_4.9\other\..\projects\framework-res.apk\AndroidManifest.xml]
at brut.util.OS.exec(Unknown Source)
... 7 more
The system cannot find the file specified[/B].
Any help will be appreciated!
When you edit xml you must assign ids properly in public.xml
Sent from my GT-I9003 using XDA App
ronhoover88 said:
When you edit xml you must assign ids properly in public.xml
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
thanks.......
can u tell me how to get the id's ?
PS:newbie @ themeing
What exactly are you trying to do??
Sent from my GT-I9003 using XDA App
ronhoover88 said:
What exactly are you trying to do??
Sent from my GT-I9003 using XDA App
Click to expand...
Click to collapse
i m trying to port ics animations
sakindia123 said:
i m trying to port ics animations
Click to expand...
Click to collapse
that's what i tried to do, but if would shows error in the apk manager when building it and if i continue and push the file to system/framework using root explorer, many apps would fc immediately and when rebooting, the phone would end up in a boot loop
rocker529 said:
that's what i tried to do, but if would shows error in the apk manager when building it and if i continue and push the file to system/framework using root explorer, many apps would fc immediately and when rebooting, the phone would end up in a boot loop
Click to expand...
Click to collapse
of course it would,since the xml's are not properly converted into binaries into apk manager
I'm making a theme for go sms and I compiled the APK thru APK Manager, but when I try to upload the apk file on the market, it says,
"Market does not accept apks signed with certificates issued by Android team.Market does not accept apks signed with certificates issued by Android team."
Click to expand...
Click to collapse
What should I do?
The theme I made was made at Go SMS' website then I decompiled the APK to edit some images that it can't be edited at the website. I compiled it back with no errors. I tried signing it and not. When it's unsigned, market says
The server could not process your apk. Try again.
Click to expand...
Click to collapse
Any suggestions please?
UPDATED 8/15 !!!
Original Post:
The method explained here: http://forum.xda-developers.com/showthread.php?t=1109962
works for SGS II but not the III. I have copied the xml sip permissions file to /system/etc/permissions, and I have decompiled framework-res.apk, where the res/values/bools.xml file already reads
Code:
<bool name="config_sip_wifi_only">false</bool>
<bool name="config_built_in_sip_phone">true</bool>
I've looked over the rest of framework-res.apk and can't find anything. Verizon must be blocking this somewhere else.. any ideas??
Click to expand...
Click to collapse
---------------------------
My own research/efforts:
I have added /etc/permissions/android.software.sip.voip.xml from a sprint Galaxy S III (its the same on all versions, its only like 4 lines) and set permissions to rw-r--r--
I have replaced my deodexed SecPhone.apk and SecContacts.apk with deodexed Sprint ones. These run fantastically (no FCs anywhere). I've also double checked the boolean values in framework-res.apk which allow SIP (as previously stated)
PROGRESS
By installing the xml SIP permissions file and then editing build.prob to imitate the sprint model:
Code:
ro.product.model=LPH-L710
ro.product.name=d2spr
ro.product.device=d2spr
or the Galaxy Nexus:
Code:
ro.product.model=Galaxy Nexus
ro.product.name=yakju
ro.product.device=maguro
it opens up the "internet call options" submenu within the dialer options. You now have sip calling... Over wifi only though, as this wipes out your data connection.
In order to keep data working, you must set set the model, name, and device to be something from verizon, which in turn disables SIP calling. It is a vicious cycle.
Therefore, in order to use SIP calling on the Verizon Galaxy S III we must either use an AOSP ROM or find where this check is occuring in smali and remove it or make it constantly return true. However, I have no clue where it could be...
preusstang said:
The method explained here: http://forum.xda-developers.com/showthread.php?t=1109962
works for SGS II but not the III. I have copied the xml sip permissions file to /system/etc/permissions, and I have decompiled framework-res.apk, where the res/values/bools.xml file already reads
Code:
<bool name="config_sip_wifi_only">false</bool>
<bool name="config_built_in_sip_phone">true</bool>
I've looked over the rest of framework-res.apk and can't find anything. Verizon must be blocking this somewhere else.. any ideas??
Click to expand...
Click to collapse
just looking at it rather quickly, the way sip stack works in ICS is different than gingerbread. The guide you have is for gingerbread. You will need to find a guide that supports ICS. I would help you with this, but I already have to many projects on my table.
nosympathy said:
just looking at it rather quickly, the way sip stack works in ICS is different than gingerbread. The guide you have is for gingerbread. You will need to find a guide that supports ICS. I would help you with this, but I already have to many projects on my table.
Click to expand...
Click to collapse
That's the thing. There are none. The menu shows up fine on the i9300. I have a copy of their SecPhone.apk that I'm looking at now.
I'm having some trouble with apktool and apk manager tho, whenever I extract, I'm not seeing the "res/values/" folder or the smali folder.
preusstang said:
That's the thing. There are none. The menu shows up fine on the i9300. I have a copy of their SecPhone.apk that I'm looking at now.
I'm having some trouble with apktool and apk manager tho, whenever I extract, I'm not seeing the "res/values/" folder or the smali folder.
Click to expand...
Click to collapse
What version of apktools are you using?
Sent from my SCH-I535 using xda app-developers app
nosympathy said:
What version of apktools are you using?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
ok so I now have apktool 1.4.3, with the windows helper files - apktool.bat and aapt.exe.
Code:
C:\apktool-1.4.3>apktool d originals/framework-res.apk
I: Loading resource table...
I: Loaded.
I: Decoding file-resources...
I: Decoding values*/* XMLs...
I: Done.
I: Copying assets and libs...
C:\apktool-1.4.3>
decompiles everything fine. including the values/ xml files. I still see no smali folder though. how do you get access to that?
also, im not able to recompile the apk. its decompiled to framework-res/, but trying to build it results in epic failure:
Code:
C:\apktool-1.4.3>apktool b framework-res
W: Could not find sources
I: Checking whether resources has changed...
I: Building resources...
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
20dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
20dp-w533dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
60dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
60dp-w640dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
60dp-w640dp-xhdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw3
60dp-xhdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/drawable-sw6
00dp-xhdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw320
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw320
dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw320
dp-w533dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw360
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw360
dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw360
dp-w640dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw360
dp-xhdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-sw600
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/layout-w600d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-h720d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw320
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw320
dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw360
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw360
dp-hdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw360
dp-xhdpi
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw600
dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw600
dp-land
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw600
dp-w1024dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-sw600
dp-w1280dp
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-w360d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-w480d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-w500d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-w600d
p
invalid resource directory name: C:\apktool-1.4.3\framework-res\res/values-w720d
p
Exception in thread "main" brut.androlib.AndrolibException: brut.common.BrutExce
ption: could not exec command: [aapt, p, -F, C:\Users\Kyle\AppData\Local\Temp\AP
KTOOL3864608409932162932.tmp, -x, -S, C:\apktool-1.4.3\framework-res\res, -M, C:
\apktool-1.4.3\framework-res\AndroidManifest.xml]
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:193)
at brut.androlib.Androlib.buildResourcesFull(Androlib.java:301)
at brut.androlib.Androlib.buildResources(Androlib.java:248)
at brut.androlib.Androlib.build(Androlib.java:171)
at brut.androlib.Androlib.build(Androlib.java:154)
at brut.apktool.Main.cmdBuild(Main.java:182)
at brut.apktool.Main.main(Main.java:67)
Caused by: brut.common.BrutException: could not exec command: [aapt, p, -F, C:\U
sers\Kyle\AppData\Local\Temp\APKTOOL3864608409932162932.tmp, -x, -S, C:\apktool-
1.4.3\framework-res\res, -M, C:\apktool-1.4.3\framework-res\AndroidManifest.xml]
at brut.util.OS.exec(OS.java:83)
at brut.androlib.res.AndrolibResources.aaptPackage(AndrolibResources.jav
a:191)
... 6 more
C:\apktool-1.4.3>
for some reason the program is changing directory backslashes to slashes midway, but those directories it mentions do not exist. more importantly, I don't know what is causing the error with exec'ing aapt - aapt.exe runs fine and is in my PATH.
any ideas? thanks for your help.
EDIT: if i run the failed exec command manually:
Code:
aapt p -F C:\Users\Kyle\AppData\Local\Temp\APKTOOL7789083448626722688.tmp -x -S C:\apktool-1.4.3\framework-res\res -M C:\apktool-1.4.3\framework-res\AndroidManifest.xml
I get more directory errors, but these directories really do exist.
Can someone tell me what sip is?
Sent from my SCH-I535 using xda premium
SIP = Session Initiation Protocol.
The short of it - VoIP (GTalk/Voice, Vonage, etc).
Stock Android supports it natively since 2.3.x.
I'm not sure if this would help but I found that there's an option in AnyCut:
Activity
Sip settings
I'd create a shortcut on the home screen to this and try setting up your sip account credentials
My phone gives me the option, I just have no sip account to my knowledge
Afterwards, I've read you should go to the Dialer settings to enable ask each call.
Sent from my SCH-I535
Josolanes said:
I'm not sure if this would help but I found that there's an option in AnyCut:
Activity
Sip settings
I'd create a shortcut on the home screen to this and try setting up your sip account credentials
My phone gives me the option, I just have no sip account to my knowledge
Afterwards, I've read you should go to the Dialer settings to enable ask each call.
Sent from my SCH-I535
Click to expand...
Click to collapse
the sip settings dialog that shows when you use the anycut widget is a big part of the sip calling. it allows you to set up accounts and register them, it then says its receiving calls but it doesn't.. Here's what the menu(s) look like:
{
"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"
}
However, the actual call settings menu still lacks the buttons required to set up/allow dialing out with SIP.
because that internet calling section is missing, this dialog is never presented:
I have tried decompiling the SecPhone.apk from nosympathys stock OTA VRALG (deodexed) rom and get errors:
Code:
C:\apktool>apktool d SecPhone.apk
I: Baksmaling...
Exception in thread "main" java.lang.RuntimeException: bad magic value: 64 65 78
0a 30 33 36 00
at org.jf.dexlib.DexFile.(DexFile.java:377)
at org.jf.dexlib.DexFile.(DexFile.java:274)
at brut.androlib.src.SmaliDecoder.decode(SmaliDecoder.java:48)
at brut.androlib.src.SmaliDecoder.decode(SmaliDecoder.java:33)
at brut.androlib.Androlib.decodeSourcesSmali(Androlib.java:68)
at brut.androlib.ApkDecoder.decode(ApkDecoder.java:85)
at brut.apktool.Main.cmdDecode(Main.java:128)
at brut.apktool.Main.main(Main.java:65)
C:\apktool>
I've also tried replacing our SecPhone.apk with one from the i9300, obtained here:
http://forum.xda-developers.com/showthread.php?t=1706310
(in the posted zip file)
but it results in mad FC's. I'm not sure what else to do here..
EDIT: all screens were stolen from http://blog.brightpointuk.co.uk/setting-sip-voip-account-samsung-galaxy-s-iii
Any further progress on this. I am really interested to try this out. However, my knowledge of modding things is somewhat limited.
joebob296 said:
Any further progress on this. I am really interested to try this out. However, my knowledge of modding things is somewhat limited.
Click to expand...
Click to collapse
Unfortunately, no. It seems the community here [is used to getting bent over backwards by verizon and/or doesn't know about the awesome benefits of SIP(!) and] is not interested in making/receiving FREE calls nationwide with their Google voice # or another outward trunk to the PSTN (public switched telephone network)
Instead of actually modifying our touchwiz dialer (or installing other carriers' GS III touchwiz dialer) I think we have a better chance of some dev around here building an ASOP dialer from source. But I think that also necessitates an ASOP build of the contacts app.
Could we use the dialer from cm9/10 giant that aosp? I don't know if we could use that apk or have to modify it to use on a stock touchwiz ROM.
Edit: Or maybe the sprint app if they have that feature still open to them.
Sent from my SCH-I535 using xda app-developers app
joebob296 said:
Could we use the dialer from cm9/10 giant that aosp? I don't know if we could use that apk or have to modify it to use on a stock touchwiz ROM.
Edit: Or maybe the sprint app if they have that feature still open to them.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Good thinking. I'm not sure why I didn't see that.. I'll extract them from one of the CM builds tonight. I'm still unsure though of exactly what apks need copied out.
update:
I made a zip which removed SecPhone, SecTelephonyProvider, SecContacts, and SecContactsProvider and installed:
Phone.apk
TelephonyProvider.apk
Contacts.apk
ContactsProvider.apk
all from invisiblek's cm9 build. this caused mad FC's with the gallery, messaging, sync service, and google.process.gapps.
fail somewhat of a learning experience though.
I'm now gonna try installing the "Sec" apks from a sprint ROM. *crosses fingers*
if you have google voice here is an awesome app for talking for free. its well setup.. its called groove ip and you can get it here..
https://play.google.com/store/apps/details?id=com.gvoip&hl=en
i have been using it for a long time now, never fails
mrbracht said:
if you have google voice here is an awesome app for talking for free. its well setup.. its called groove ip and you can get it here..
https://play.google.com/store/apps/details?id=com.gvoip&hl=en
i have been using it for a long time now, never fails
Click to expand...
Click to collapse
It is a good app and works very well. its just disappointing that you need to download a 3rd party app for something that the android OS already provides for. And verizon is the only carrier to do this. isn't surprising tho..
preusstang said:
It is a good app and works very well. its just disappointing that you need to download a 3rd party app for something that the android OS already provides for. And verizon is the only carrier to do this. isn't surprising tho..
Click to expand...
Click to collapse
Verizon is pretty much a joke. I still can't believe they get away with all the **** they do
Sent from my SCH-I535 using Tapatalk 2
preusstang said:
update:
I made a zip which removed SecPhone, SecTelephonyProvider, SecContacts, and SecContactsProvider and installed:
Phone.apk
TelephonyProvider.apk
Contacts.apk
ContactsProvider.apk
all from invisiblek's cm9 build. this caused mad FC's with the gallery, messaging, sync service, and google.process.gapps.
fail somewhat of a learning experience though.
I'm now gonna try installing the "Sec" apks from a sprint ROM. *crosses fingers*
Click to expand...
Click to collapse
Yea I'm learning to. I read today that the dialer app relies on more then just the app itself if I recall correctly we have to change some framework files. So we would have to modify more then just the app. But I think that an app with that already allows sip calling would be a good place to start. I think that we would have a better chance using sprints stock dialer if they have it enabled, because that should be based on touchwiz.
Sent from my Galaxy Nexus using xda app-developers app
---------- Post added at 02:30 AM ---------- Previous post was at 02:20 AM ----------
mrbracht said:
if you have google voice here is an awesome app for talking for free. its well setup.. its called groove ip and you can get it here..
https://play.google.com/store/apps/details?id=com.gvoip&hl=en
i have been using it for a long time now, never fails
Click to expand...
Click to collapse
How is the voice quality over 3g/4g? Any complaints about the app?
Sent from verizons soon to be unlocked galaxy s3
joebob296 said:
Yea I'm learning to. I read today that the dialer app relies on more then just the app itself if I recall correctly we have to change some framework files. So we would have to modify more then just the app. But I think that an app with that already allows sip calling would be a good place to start. I think that we would have a better chance using sprints stock dialer if they have it enabled, because that should be based on touchwiz.
Sent from my Galaxy Nexus using xda app-developers app
---------- Post added at 02:30 AM ---------- Previous post was at 02:20 AM ----------
How is the voice quality over 3g/4g? Any complaints about the app?
Sent from verizons soon to be unlocked galaxy s3
Click to expand...
Click to collapse
None what so ever. Loving it to be honest, been using it for a while now
Sent from my SCH-I535 using Tapatalk 2
I've been debating whether or not to try it. Right now I use talkatone which was free for 3g/4g calling but I've had issues with it recently.
Sent from Verizon's soon to be unlocked Galaxy S3.
Guys,
I was checking the post ....deleted... Thanks to this effort by the Author, I have always wanted to use S-Note on my S4.
This ROM is in the nascent stage and people are reporting boot loops. What I did was to download the Rom.
Extracted SNote3.apk from the above ROM and tried installing it. It did not install
So used root explorer and copied the file to system\app directory and set the permissions. This launched the S-Note and took me to the initial setup of S-Note of selecting templates etc.. after two screens it crashed and exited. Played with Logcat and found that it was looking at some libraries for the SPen. So Searched in the downloaded rom the SPen File and Found it to be SPenSDK3.apk
Then I copied the SPenSDK3.apk from the above ROM, and installed it (Note - I did not copy using root explorer but Installed it by launching the apk.). And Bingo S-Note Works wonderfully on my S4 (Stock ROM but Rooted) !!!
Link to the two files -- > https://dl.dropboxusercontent.com/u/53085065/S-Note.zip
Error On Re-booting
shaji_ka_71 said:
Guys,
I was checking the post related to the Note 3 UI --> http://forum.xda-developers.com/showthread.php?t=2446924. Thanks to this effort by the Author, I have always wanted to use S-Note on my S4.
This ROM is in the nascent stage and people are reporting boot loops. What I did was to download the Rom.
Extracted SNote3.apk from the above ROM and tried installing it. It did not install
So used root explorer and copied the file to system\app directory and set the permissions. This launched the S-Note and took me to the initial setup of S-Note of selecting templates etc.. after two screens it crashed and exited. Played with Logcat and found that it was looking at some libraries for the SPen. So Searched in the downloaded rom the SPen File and Found it to be SPenSDK3.apk
Then I copied the SPenSDK3.apk from the above ROM, and installed it (Note - I did not copy using root explorer but Installed it by launching the apk.). And Bingo S-Note Works wonderfully on my S4 (Stock ROM but Rooted) !!!
Click to expand...
Click to collapse
Rebooting the device crashes the S-Note App when launched (( But I can again install the SPenSDK3.apk and it works fine ))
Wonder what happens on re-boot! back to logcating!!
it need some libs for framework and snoye crash on hand recognition
Sent from my GT-I9505 using Tapatalk 2
Logcat - Error
damador said:
it need some libs for framework and snoye crash on hand recognition
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
Would you know what this error points to? I find that it mostly crashes when saving though it saves the files and the saved note can be used. It crashes and restart and opens the saved note
E/AndroidRuntime( 5948): FATAL EXCEPTION: main
E/AndroidRuntime( 5948): java.lang.NoClassDefFoundError: com.samsung.android.secretmode.SecretModeManager
E/AndroidRuntime( 5948): at com.samsung.android.snote.control.core.filemanager.secretbox.SecretService.getSecretDir(SecretService.java:134)
E/AndroidRuntime( 5948): at com.samsung.android.snote.control.core.filemanager.secretbox.SecretBoxReceiver.onReceive(SecretBoxReceiver.java:39)
E/AndroidRuntime( 5948): at android.app.ActivityThread.handleReceiver(ActivityThread.java:2449)
E/AndroidRuntime( 5948): at android.app.ActivityThread.access$1600(ActivityThread.java:152)
E/AndroidRuntime( 5948): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1358)
E/AndroidRuntime( 5948): at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime( 5948): at android.os.Looper.loop(Looper.java:137)
E/AndroidRuntime( 5948): at android.app.ActivityThread.main(ActivityThread.java:5328)
E/AndroidRuntime( 5948): at java.lang.reflect.Method.invokeNative(Native Method)
E/AndroidRuntime( 5948): at java.lang.reflect.Method.invoke(Method.java:511)
E/AndroidRuntime( 5948): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1102)
E/AndroidRuntime( 5948): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:869)
E/AndroidRuntime( 5948): at dalvik.system.NativeStart.main(Native Method)
shaji_ka_71 said:
Would you know what this error points to? I find that it mostly crashes when saving though it saves the files and the saved note can be used. It crashes and restart and opens the saved note
E/AndroidRuntime( 5948): FATAL EXCEPTION: main
E/AndroidRuntime( 5948): java.lang.NoClassDefFoundError: com.samsung.android.secretmode.SecretModeManager
Click to expand...
Click to collapse
You need to add this class to your phone framework. This class could be found as separate .jar file in Note3 framework or it could be in framework2.jar.
Sent from my GT-I9300 using Tapatalk 2
Hope Some one can fix this
Arsaw said:
You need to add this class to your phone framework. This class could be found as separate .jar file in Note3 framework or it could be in framework2.jar.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Hope Some Senior Member can fix this!