yashsingh1/xdaforums huggingface dataset:
[Galaxy S II Android Development] Twiq:
Since it tries to connect to mobile data i think it is SIP calls..

Anyway, from the log it says apn type DUN.. Isn't DUN = Dial Up Networking ? Like when you try to connect modem from PC, and i don't think DUN is a valid entry for apn type (at least on android).. You could check for the APN and change apn type to "default, supl" and see if it resolves the problem

Edit: i did some reading, a good one from http://forums.whirlpool.net.au/archive/1663451

For Android phones if an application needs to talk to the network it talks to Android ConnectivityManager on the phone, When the application calls the connectivity manager it requests the type of network it needs to talk to.

For Android these are:
1. Dial Up Network (TYPE_MOBILE_DUN)

This is really old but might be used for some very old networks. Networking Bridge so that the carrier is aware of DUN traffic. It may coexist with default data connections.

Not used anymore. Pretty sure the HTC desire does not support.

2. WiMAX data connection TYPE_WIMAX

The Default Worldwide Interoperability for Microwave Access data connection.

Pretty sure the HTC desire does not support.

3. High Priority Mobile data {TYPE_MOBILE_HIPRI}

A High Priority Mobile data connection. This connection is typically the same as {TYPE_MOBILE} but the routing setup is different. Only requesting processes will have access to the Mobile DNS servers and only IP’s explicitly requested via {@link #requestRouteToHost} will route over this interface if a default route exists.

Something you don’t need to think about

4. WIFI data connection. (TYPE_WIFI)

When active, all data traffic will use this connection by default.

Used to connect to your home wireless router.

Below are the APN TYPES that you set in the APN config on your phone.

1. Default (TYPE_MOBILE)

The Default Mobile data connection. When active, all data traffic will use this connection by default. Should not coexist with other default connections.

2. mms (TYPE_MOBILE_MMS)

An MMS-specific Mobile data connection. This connection may be the same as {TYPE_MOBILE} but it may be different dependant on the network. This is used by applications needing to talk to the carrier’s Multimedia Messaging Service servers.

3. supl (TYPE_MOBILE_SUPL);

A Secure User Plane Location specific Mobile data connection. This connection may be the same as {TYPE_MOBILE} but it may be different. This is used by applications needing to talk to the carrier’s Secure User Plane Location servers for help locating the device

How does the config on the phone get chosen?

When an application wishes to talk to the “network” it sets the APN type when it requests ConnectivityManager. ConnectivityManager then checks if you have an “APN type” set that matches. So for instance if the “APN type” it checks is MMS it will scan you configuration setting for a match and use say testra.mms APN. It will then use this configuration for the network connection. What you use for the APN name does not matter.
[Galaxy S II Android Development] mauriicio21:
Skype have bug in 5.x use 4.9x work fine, viber and hangouts dont know because i dont have
[Galaxy S II Android Development] fusionjack:
for skype, it is a known problem in his latest version.

for hangouts n viber, at least i didn't receive bug report till now...

not sure how 'easy' that could be...nevertheless it could cause problem for other dpi like 240. i think because of this reason, they are not enabled at the same time.
[Galaxy S II Android Development] alstonleo:
m not able to take a log of this issue.. as my screen just hangs up n i cant do anything bt restart.. any suggestions
[Galaxy S II Android Development] fusionjack:
do you use custom kernel?

i never see something like that...i'd try a full wipe and install only viber and see if that still happens.
[Galaxy S II Android Development] fusionjack:
there isn't much changes on slimroms side as well from my side. let's see tomorrow...
[Galaxy S II Android Development] alstonleo:
i am using the latest slim kernel.. will try doing a full wipe.. was trying to avoid this solution bt well guess it has to b done then.. will post back if issue still continues ..
[Galaxy S II Android Development] Gandalf19:
For first time I have trouble with black screen with FB :(
[Galaxy S II Android Development] george_shudi:
Everything is fine here
[Galaxy S II Android Development] aceman2013:
Reinstall FB should solve the problem with the app
[Galaxy S II Android Development] j1gga84:
This does not help.. It is app and dpi related I think but nobody found the exact problem until now..

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] CounterC:
[MENTION=1228651]fusionjack[/MENTION] any news on this one?

Thanks
[Galaxy S II Android Development] SnowmanDK:
Great rom. I am surprised how smooth it runs :)

I have one problem though.

When I use my Bluetooth headset, I am told it sounds like I am far away from the microphone.

I can hear people fine.

Is there a way to boost the Bluetooth microphone?
[Galaxy S II Android Development] Gandalf19:
And the black screen don't appear on every page..... :eek:
[Galaxy S II Android Development] j1gga84:
I will try another ROM these days until Theme Chooser will be implemented I think and will report back if this issue is only in Slim (Saber) ROMs or not.

Regards
[Galaxy S II Android Development] jj one:
I have this rom from a week and like it.

I noticed lags in some app and games that were not in Samsung stock JB and Neatrom JBI had previously.

How can I fix it? Is a kernel problem?

Thanks a lot!
[Galaxy S II Android Development] souler456:
If you mean some stutterings, then either stop Underclocking / Undervolting your device, or if that's not your case, then get another Custom Kernel. Don't ask me what's good, cause I'm using Stock Kernel and it works pretty sexy for me :good:

:D :) ;) :good:
[Galaxy S II Android Development] root:
FIX: the problem came from the croudsourced rules of xprivacy... not related to rom at all... sorry for whining bellow...

I encountered a problem where f-droid doesnt install apk and fails with "There was a problem parsing the package."

After downloading the application manually i encountered the same problem.

SAME application moved to the SD card installs fine. Does maybe someone knows what is the fix for this? I have chkdsked it from windows but it doesnt show any errors... Before installing 4.4.4 this was working fine :(

Furthermore, when i used the Settings, Storage option "Switch external memory", the application on SD card (which now became the primary memory) can no longer be installed.

Looks like something on software side is blocking the primary memory apk execution.

As a potential interference: I have installed the XPrivacy and updated the settings from the crowd.
[Galaxy S II Android Development] stylemessiah:
As far as i know, it can only be done with a custom kernel. Ive tired volume increasing apps and never found one that worked...

I use Dorimanx kernel and via Stweaks (the tweaking App installed with it) you can adjust the Headset/Speaker.Mic and Master volumes

I boost my phone speaker volume using it...

Before going to the extent of flashing a custom kernel i would make sure that the headset itself wasnt the issue, have you used it with another ROM on the same device, if so was the issue present on that as well? Or does it have the same issue when on another device completely?
[Galaxy S II Android Development] j1gga84:
Anybody is using BaNkS GApps ?

I want to use the GApps_Minimal_4.4.4_signed but there is no GoogleCalendarSyncAdapter in it.

Must I flash 7-15_AOSP_Calendar_Sync_4.4.4_signed.zip in addition?

Regards
[Galaxy S II Android Development] hawaiisteve:
Banks gapps w/ calender sync working fine for me
[Galaxy S II Android Development] j1gga84:
So I don't need to flash the AOSP calendar sync in addition? I ask because I need calendar syncronisation.

Regards
[Galaxy S II Android Development] hawaiisteve:
You need to flash both
[Galaxy S II Android Development] fusionjack:
games are working better on stock rom because they use the original graphic driver whereas we on aosp is using an outdated hacked graphic driver.
[Galaxy S II Android Development] fusionjack:
app is probably corrupted.

when you want to switch storages, make sure you move all apps back to data partition as you won't see them anymore as they are located on other storage.
[Galaxy S II Android Development] SnowmanDK:
I used it without problems on a 4.4.2 rom earlier.

Also note it is only when using the Bluetooth headset. Using the inbuilt microphone is fine.

I'll try out that kernel. Thanks :)
[Galaxy S II Android Development] Rachid.Ala:
Can you try your Bluetooth headset with stock rom or with another phone ?

Just to be sure that your headset's microphone is working properly :)
[Galaxy S II Android Development] SnowmanDK:
I used it on my LG Optimus 2X, both on stock rom and a custom rom and it worked fine there.
[Galaxy S II Android Development] j1gga84:
[MENTION=4546441]Twiq[/MENTION] [MENTION=1228651]fusionjack[/MENTION]

I thought the freezing SwiftKey keyboard and WhatsApp is Dorimanx related but I had the same now with stock kernel and Apolo so I think it is ROM related. Maybe I will try another ROM with Dorimanx and see if the problems also occur there.

Wenn the keyboard/WhatsApp freezes and I have to reboot, I cannot send a logcat but one of you wrote something about a file that is available after a reboot if system hung. Something with A.. but I cannot remember. Any idea how I can give you some input of my error?

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] JavaScout:
[MENTION=1228651]fusionjack[/MENTION], can you please upload standalone twrp recovery, the same as integrated in slimsaber?
[Galaxy S II Android Development] m1trand1r:
impossible w/o kernel ....:p
[Galaxy S II Android Development] Rachid.Ala:
Kernel and recovery are in the same partition on our device afaik
[Galaxy S II Android Development] fusionjack:
just finished done two little things:

* extended overflow menu button

* show/hide network speed arrow icons
[Galaxy S II Android Development] fusionjack:
well, whatsapp is never hanging on my device.

you also have problem with touch key timeout. perhaps it is time to full wipe :)

i'll upload latest kernel tomorrow
[Galaxy S II Android Development] fusionjack:
[MENTION=4919255]CounterC[/MENTION]: i still didn't have time to contact Sale.
[Galaxy S II Android Development] j1gga84:
What do you mean with key timeout?

I am sorry to say that but I am not the only one with this issue. Until now I got 3 private messages from users with the same problem and one user in german forum also had problems so there must be something wrong. Maybe it is only a setting, I don't know but a fullwipe again? I did a fullwipe 2 weeks ago and before this fullwipe i had the same problem and I flash ROMs since over 3 years so I definitely know what I am doing ;)

One or two weeks ago we were writing about a file that is created when system freezes. Immediately after reboot this file is still available and you had a look into this file and told me nowadays that my file system could have been corrupted but I don't know what file this was. ANR or something like that..

Regards

Sent from my GT-I9100 using german Tapatalk 4
[Galaxy S II Android Development] la_malacoda:
I'm also having freezes with SwiftKey man, both on Slim base or Cyano, with Apolo and stock kernel. AFAIK is a SwiftKey problem, that since it's free it takes too much ram :S
[Galaxy S II Android Development] Rachid.Ala:
This issue is very random, it can be also app related since swiftkey uses about 40mb of ram. Maybe it gets killed automatically by oom killer

Next time try catching a logcat via adb if you're near a computer, we'll hopefully find something useful
[Galaxy S II Android Development] hispanico957:
Also me have freezing SwiftKey keyboard and WhatsApp.. but i use SlimSaber 4.3.1 :)

(stock kernel)

Hispa
[Galaxy S II Android Development] paludi06:
I switched to TouchPal because Swiftkey hanged all the time and the back button didn't work until I force closed Swiftkey. Furthermore the Swiftkey popup is really slow compared to TouchPal.
[Galaxy S II Android Development] m1trand1r:
oh boy.....I hope you guys with Swiftkey issues will ever realize that Swiftkey is like Sammys roms....bloated with useless stuff....imho....and big ram eater....I even tried to use Per app settings module to lock it In memory and it won't stay..,it will always get killed.....this is very annoying matter imo....;)...and everything else was wrong till now....rom...kernel ....what not....but no....no one thought that it could be app itself which is very much obvious ;)
[Galaxy S II Android Development] JavaScout:
Great, I never liked those arrows [emoji41]
[Galaxy S II Android Development] j1gga84:
Ok, I also consider that it COULD be SwiftKey itself .. Older Versions worked just perfect but since they introduce this cloud thing everything became worse.. So what is an alternative to SwiftKey? I don't want to (use) Swipe, I want to type my words AND I need a (german) "self-learning" (for additional words) dictionary that is not 4 years old like for Smartkeyboard Pro which is a very good keyboard in my opinion. I used it for a long time before switching to swiftkey but there are not much (good) keyboards around I think.. If you see, the android keyboard app also has 30MB.. I think [MENTION=1228651]fusionjack[/MENTION] mentioned ai.keyboard pro some time ago. maybe I will test this one again..

Regards and sorry for OT
[Galaxy S II Android Development] JavaScout:
Is this package going to be flashable by jellybean recovery (philz v3 something..., touch-enabled)? You see, my brother also has i9100, but the power button is malfunctioning, almost not usable. So, I hope that this package is the only step left to upgrade his phone to slimsaber [emoji6]
[Galaxy S II Android Development] fusionjack:
yes, a recovery can be flashed from other recovery...but keep in mind that flashing a recovery is the same like flashing a kernel and vice versa.

if you plan to use that recovery/kernel, you need a compatible rom that can use that kernel. this means slimkernel-4.3.1 should only be used with aosp jb roms, not for stock roms and slimkernel-4.4.4 only for aosp kitkat roms.

if you plan just use the recovery as a bridge to flash a rom, you should reboot to recovery directly (not to the system) after flashing recovery. if you want to flash kitkat rom, you should use slimkernel-4.4.4.

both recovery on 'R' and this build are twrp. so you can use it without hardware buttons.
[Galaxy S II Android Development] paludi06:
That's why I wrote the post above you, because I know that it's not rom related ;) Swiftkey is getting worse with each update and I wanted to share an alternative keyboard that is very fast, has good predictions and uses very few ram (not more than 20 MB) :good:
[Galaxy S II Android Development] JavaScout:
Yes, the "bridge" to kitkat. That's the case [emoji41] Thanks
[Galaxy S II Android Development] Twiq:
I'm not using swiftkey, but from ppls report i'm kinda leaning toward the idea that swiftkey has memory leaks which resulting it gets killed by android memory management.. Coz i can tell whatsapp is running fine on my end.

But maybe it has some bugs too which triggers ANR if combined with swiftkeys' "features" :silly:
[Galaxy S II Android Development] Harsha Raj:
Just want to chim in on this SwiftKey issue. I too used to face the same problem. Every now and then the keyboard used to change to default android keyboard. Before there was a performance update to SwiftKey, I used to end up with no keyboard popup at all and back key would stop working and restart used to fix it.

So right now I'm using SwiftKey on my old Galaxy Ace Duos running gingerbread 2.3.6. There is no problem of SwiftKey at all in this phone. But why on S2?

On side note. My s2 is permanently dead. Not repairable with current not herb. I think changing the motherboard in service center will fix it. But it will cost around 8000 INR (around 130$), which is a costly repair. So my journey with s2 probably ends here.

Thank you so much [MENTION=1228651]fusionjack[/MENTION] for building the SlimSaber ROM, which I had run on my device continuously for more than 6 months. Your ROM really made using s2 enjoyable, so much that I took time to make feature list of the your ROM.

And I may not be able to continue to update the feature list anymore. It would be better if someone using the SlimSaber take over.

Thank you again [MENTION=1228651]fusionjack[/MENTION] and other active members of this group, you have been kind to new and old users alike. Hoping the s2 will receive Android L update in near future.

See you all around!
[Galaxy S II Android Development] Noed:
[MENTION=1228651]fusionjack[/MENTION] any chance of getting this feature in SlimSaber?

http://xdaforums.com/showthread.php?t=2512337

I used it before, works better than other apps I tried.
[Galaxy S II Android Development] fusionjack:
sorry to hear that and thank you for your contributions to this thread and s2 community. keep it up...[emoji1] [emoji106]

we had it before...imo, this tool is too dangerous to play with since it could cause instability.
[Galaxy S II Android Development] fusionjack:
SlimSaber-i9100-4.4.4-20140820.zip

SlimKernel-i9100-4.4.4-20140819.zip (No changes, it is just latest kernel)

Changes:

Synced with weekly 7.4

Compiled with latest SaberMod 4.8.4 and 4.9.2 20130814

Lockscreen notifications

Settings - Security

Show/hide network speed arrow icons

Settings - Interface - Statusbar

Extended configurable overflow menu button

Settings - Navigation - Hardware buttons

PerformanceControl: Rework time in stats

libcore: Fix parsing of fractional seconds

See changelog for the rest of changes
[Galaxy S II Android Development] souler456:
I am soooo digging this New Update! :D

Lockscreen Notifs works like a charm! And the removal of the Arrows in the Network Speed Meter is a bonus treat for me as well! :good:

Although, I'm having trouble with SlimPie not reducing it's Trigger Size when on keyboard, causing the SlimPie to appear on times that I press the Space Button on my Keyboard. Hope it has been noticed and have time to be fixed...

Thanks, FJ! Am waiting for the "R" update as well... :D :) ;) :good:
[Galaxy S II Android Development] razen_kain:
Kii keyboard.
[Galaxy S II Android Development] Stoyanski:
After dirty flash I have FC when "Security" is selected. Also Wi-Fi is not working. Anyone having the same?
[Galaxy S II Android Development] pdario:
Take a look at TouchPalX too

---------- Post added at 10:06 AM ---------- Previous post was at 09:35 AM ----------

Confirm: I can't access Security settings anymore!

Will go back to previous version fix?
[Galaxy S II Android Development] hispanico957:
Thank for update... but i have strange problem now.

When click on HOME button not come back to home... i can use only button right to come back to home ??

Thank

Hispa
[Galaxy S II Android Development] pdario:
FC upon accessing Security Settings:

W/10:21:06.841 ActivityManager( 2305)
Force finishing activity com.android.settings/.Settings
W/10:21:06.836 ActivityManager( 2305)
Force finishing activity com.android.settings/.SubSettings
E/10:21:06.836 AndroidRuntime(14517)
... 13 more
E/10:21:06.836 AndroidRuntime(14517)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2767)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.Activity.performResume(Activity.java:5330)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:1863)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1044)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1062)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:924)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.Fragment.performResume(Fragment.java:1743)
E/10:21:06.836 AndroidRuntime(14517)
at com.android.settings.SecuritySettings.onResume(SecuritySettings.java:843)
E/10:21:06.836 AndroidRuntime(14517)
at com.android.settings.SecuritySettings.createPreferenceHierarchy(SecuritySettings.java:421)
E/10:21:06.836 AndroidRuntime(14517)
Caused by: java.lang.NullPointerException
E/10:21:06.836 AndroidRuntime(14517)
at dalvik.system.NativeStart.main(Native Method)
E/10:21:06.836 AndroidRuntime(14517)
at de.robv.android.xposed.XposedBridge.main(XposedBridge.java:132)
E/10:21:06.836 AndroidRuntime(14517)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:611)
E/10:21:06.836 AndroidRuntime(14517)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:795)
E/10:21:06.836 AndroidRuntime(14517)
at java.lang.reflect.Method.invoke(Method.java:515)
E/10:21:06.836 AndroidRuntime(14517)
at java.lang.reflect.Method.invokeNative(Native Method)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.ActivityThread.main(ActivityThread.java:5034)
E/10:21:06.836 AndroidRuntime(14517)
at android.os.Looper.loop(Looper.java:136)
E/10:21:06.836 AndroidRuntime(14517)
at android.os.Handler.dispatchMessage(Handler.java:102)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1199)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.ActivityThread.access$800(ActivityThread.java:138)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2241)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:2806)
E/10:21:06.836 AndroidRuntime(14517)
at android.app.ActivityThread.performResumeActivity(ActivityThread.java:2777)
E/10:21:06.836 AndroidRuntime(14517)
java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException
E/10:21:06.836 AndroidRuntime(14517)
Process: com.android.settings, PID: 14517
[Galaxy S II Android Development] fusionjack:
which lockscreen security do you use? tried on slide, pin and pattern...no fc.
[Galaxy S II Android Development] pdario:
Face unlock, see previous log.
[Galaxy S II Android Development] hispanico957:
+ 1 there is a setting different for home button ?

SOLVED.... the problem was FULL GAPPS... i install mini gapps and all is ok :)
[Galaxy S II Android Development] Stoyanski:
I use gesture. I resetted the phone. Security is now available, but Wi-Fi is still not working
[Galaxy S II Android Development] pdario:
[MENTION=1228651]fusionjack[/MENTION]: can you suggest a few files to remove instead of a full wipe to reset security settings?
[Galaxy S II Android Development] fusionjack:
thanks for the log...

the code is not guarded when this option not available on some lockscreen security...hence fc :eek:

i'll fix it...

i was hesitating as i wanted to cherry-pick this feature...now security fc, what's next? :rolleyes:
[Galaxy S II Android Development] marjune23:
Nice update mate...

One question, how does notification in lockscreen work?...

Is it only notification to status bar?
[Galaxy S II Android Development] j1gga84:
Thank you! :good:

I will have a look to both keyboards.

german dictionary for Kii seems not very good and TouchPal X gets bad rating on PlayStore because of claiming too much rights during installation :confused: Hmm I will see, thank you guys! :)

Regards
[Galaxy S II Android Development] Nos_20:
Security settings are working fine here
[Galaxy S II Android Development] fusionjack:
yeah, i forgot to add 'lockscreen notification' into gesture lockscreen and the code is not guarded well, hence fc.

nothing is changed on the wifi and wifi is still working fine on my side. check again your setup.

basically, you just need to change the lockscreen security from face unlock to slide, pin or password. i couldn't found where this setting is stored.

you can flash previous build, change the lockscreen security and then flash latest build.

the notification will be shown in the lockscreeen...try it, you'll know what i meant. :p