yashsingh1/xdaforums huggingface dataset:
[Asus Transformer TF700] ShadowLea:
Do you kill most of the cached apps? If not, one of those may be keeping memory hogged. (top right when you're in Running Apps menu under settings). Don't kill all of them, but things like media, Google search and apps can be killed.

Does it mean the RAM memory or the internal SDmemory? I've never seen the warning, but it could be referring to too little free mamory space.
[Asus Transformer TF700] GaryParr:
It means RAM... have plenty of actual storage space. As for killing processs, I tend not to worry about that since Android is supposed to take care of them for me. Cached apps *should* be cleared when RAM gets low. I'm wondering if the low memory warning is being triggered before the system has time to reclaim resources. In other words, the threshold is reached, android starts to kill cached threads but it takes longer than it should so the warning pops up before the cleaning process completes. This would explain why the RAM shows around 50% usage right after I see the message. Well, if no one else is seeing anything like this it could just be some combination of processes I'm running that are holding on to things longer than they should.
[Galaxy S III Q&A, Help & Troubleshooting] OLYMPIAKOI:
Is the Australian LTE EUROPEAN COMPATIBLE?:silly:
[Galaxy S III Q&A, Help & Troubleshooting] speedyjay:
Compatible with what??
[Galaxy S III Q&A, Help & Troubleshooting] Sean88:
http://www.kogan.com/au/buy/samsung-galaxy-s3-4g-i9305-black-16gb/
[HD2 General] mrmomba:
Hey Guys,

i have a little Question.

I there a possibiliy to turn a windows 8 rt on the HD2?

Has someone take a try to port it to our lovely handy?

can some devs give us an info?
[HD2 General] 433Mhz:
Everything is possible I guess but I don't think anyone has tried it yet.

btw, stop using the word "Handy". It is a retardation of the German and English language.
[HD2 General] mrmomba:
thanks, yes, i will try to stop using the world "handy"

i mean mobilephone - i have learn to write a better english - it more than a little bit rusty :)
[HD2 General] pakure:
windows 7.8 (for ist tier devices) and windows 8 (for 2nd tier, dual core devices) will be released on 24 oct

we have already windows 7.8....:p........wait for it to get officially released...cotulla is onto something...wait and watch:p
[HD2 General] mrmomba:
that sounds awesome good. i'll be waiting like a little child for xmas for the new release.

but windows 7.8? i have not read anythin about that? windows 8 only for dualcore?

using windows 8 on my convertible - it is awesome good, now i am nosy how it works an little displays!

thank for your reply!
[HD2 General] Moon2:
Windows Phone 7.8, Windows Phone 8.
[HTC Sensation] rhd-android:
I thought I was smart, until this mystery completely stumped me. I've sought out as much data as possible, but I'm utterly puzzled as to what is causing the problem. I would be really curious to see if anyone can digest my data and come up with a conclusion! My phone is the Sensation 4G.

The Problem:

- Certain (but not all) HTTPS websites requiring SSL don't work and create an error #107 (screenshot below).

- The most notable example is Twitter's HTTPS site, but there are lots of others.

When it Happens:

- The error

does not occur

on my phone, if I switch to WiFi, or use someone else's SIM.

- The error

does not occur

on the Galaxy Note (stock), using my SIM.

- The problem

occurs

on the HTC Desire Z (CM9), using my SIM.

- The problem

occurs

on my phone, regardless of ROM used. It happens in ICS (AOSP), and in JB (CM10).

- The problem

occurs

in both Chrome and the stock browser.

Table Summarizing My Data:

Observations / Theories:

- It cannot be my SIM (or the account), because my SIM inserted into a Galaxy Note had no problem.

- It cannot be the Sensation 4G hardware, because the problem doesn't occur with WiFi, and the problem also occurs on the Desire Z hardware.

- It cannot be HTC phones in general, because the Desire Z has no problem with the Wifi or with a Rogers SIM.

- It cannot be ROM related, because the problem occurs in CM9, CM10, and AOSP.

But these observations don't actually lead to a conclusions about what the problem could be caused by.....

NEW INFORMATION:

A new development has lead me to believe that this must be a more widespread problem than I initially suspected. I think there's a common/persistant problem with CyanogenMod that affects certain SSL connections on Bell Mobility's network. What's this new development?

- I bought a brand new phone 2 days ago. A Galaxy SII HD LTE.

- This also means I got a brand new SIM card because the new phone required MicroSIM

- I didn't migrate anything from my old phone.

And here's the kicker. The new phone, with the new SIM, running a fresh install of CM9, also cannot connect to certain SSL sites. The same error #107 occurs, and just like before, if I switch the new phone onto WiFi, there are no problems. Similarly, if I leave the phone with the stock ICS, no problems.

At this stage, the ONLY common denominators are:

- Bell Mobility network

- CyanogenMod 9 or 10

And since the Bell Mobility network can be ruled out (since the stock OS on this phone works, as do other Bell Mobility phones), the problem must be something to do with CyanogenMod.
[HTC Sensation] rhd-android:
This thread hasn't seemed to attract attention, but some new information has lead me to the conclusion that this is really a problem someone should look at.

In a nutshell, I've bought a brand new phone, with a brand new SIM, and installed a fresh CM9. The problem is present in this new phone also. The only common denominator, apart from the mobile carrier (which can be ruled out for reasons discussed in the OP), is CyanogenMod.

Check out the bottom of the OP, under "New Information" in red.
[HTC Sensation] xraycat:
I have the same issues running an AOSP version of Android 4.2 (Paranoid Android 2.99.4) on my Galaxy Nexus. I use the Bell network as well and regularly get SSL errors. Once I switch to wifi I don't receive the errors.
[HTC Sensation] rhd-android:
I have talked to one other person (in real life) that has this issue too. For an issue that wouldn't naturally come up in conversation, it's pretty noteworthy that I've found even one other person with this issue (I'm not in a big population center, nor do I talk about phones with random people frequently). Just a passing acquaintance, so not somebody I could grill about the specifics. But he verified that he was running CM, and that the issue only occurred when using his Bell sim, and cell data. It didn't happen when using wifi, nor when on holidays using a foreign cell network.

So, there is something about CM that doesn't behave well with bell in certain situations. It's clear that some SSL sites do in fact work. That might seem like inconsistency, but it's not. The sites that don't work, CONSISTENTLY don't work. Twitter is the easiest example to point to, because it's a mainstream site that everyone recognizes. But there are tons of sites, that fall victim to this same issue when running on the Bell network with CM.

It's very frustrating that nobody has shown any interest in trying to figure this out.

Here's an interesting update:

- I tried an experiment, and setup a VPN to tunnel my mobile data through. I just signed up for one of those $5 per month anonymizer services that gives you a PPTP connection (is that what it's called?). Anyway, the minute I flip it on, everything works. Still using mobile data from Bell, but tunneling it through a VPN. No problems. The minute I turn back OFF the VPN and just use the straight Bell data, back to problems.

- It's not a permanent fix (because it's costing me $5 a month), but it's an easy workaround until someone takes an interest in this issue and helps sort it out. I've done everything I can, and even posted logcats. At this stage, finding a resolution is a few degrees above my comprehension level.
[HTC Sensation] Dream_Team:
Hello guys !

I'm the owner of a Nexus 4 (on Virgin, which is Bell's network), and while this is not the good forum, I am concerned by this bug.

Running CM10 nightly, I have this SSL error.

It's really a OS problem, as you guys figured it out. Except that this time, the stock rom works perfectly.

Sadly, I'll have to go back to vanilla, since it also breaks some apps.

If you only need a workaround for websites, consider using Firefox. It has it's own SSL implementation, and it works perfectly.
[HTC Sensation] rhd-android:
I hear you. Firefox helps, but as you've pointed out THE SSL/BELL FLAW IN CYANOGENMOD ALSO BREAKS APPS! For example, eBay. The eBay app obviously uses the OS SLL stack behind the scenes, because CM9 and CM10, when using Bell, break the eBay app.

Frankly, its really frustrating. Most people can change almost anything about their smartphone setup at will, EXCEPT their carrier (without paying dearly).

There is basically no way to use a custom CM rom on Bell, until someone addresses this. Unfortunately, I am a nobody on this forum, so until someone important notices the problem, I suspect the answer is to use vanilla factory roms, or avoid Bell (if you have that option)

Sad :(
[HTC Sensation] Dream_Team:
I'm starting to think that this is "easily" fixable.

I just installed an AOKP rom over my CM10 without erasing my settings and the SSL bug was STILL here. Once I wiped /data, the SSL bug was gone. So it's not really a CM codebase bug, as in a fautly lib, but some of it's settings that's broken. I'll investigate more since I have access to working/non working roms and get back to you guys.

EDIT : Ok, so I removed both the Proxy and it's port (they BOTH need to be undefined) from the pda.bell.ca APN and saved the changes. I can now access everything.

Too bad I had to sacrifice all of my music/pictures/app/settings for this, but heh. I hope it works for you ! Someone needs to report this to the CM team.
[HTC Sensation] rhd-android:
You, sir, have solved the problem.

I can confirm that on a previously "SSL-bug-ridden" CM9 rom, simply un-setting the Proxy, and the Port, has resolved the issue completely!

Brilliant!
[HTC Sensation] rhd-android:
Here's an annoying side-effect.

If you disable the proxy entry in the APN settings, you can't have LTE anymore :(
[HTC Sensation] stimoceiver:
more of the same

same issue on chinese made generic MTK6589 based "Star S7589" phone.

SSL error 107 errors.

from "about phone" page:

Model number: v89_jbl1a698

Android Version: 4.2.1

Baseband Version: MOLY.WR8.W1248.MD.WG.MP.V6.P4, 22013/04/12 17:49

Kernel Version: 3.4.5 root@android #1 Mon Apr 22 11:15:49 CST 2013

Build number: v89_jbl1a698_20130422

After seeing this error, I installed Kurt Huwig's SSL Verify from the app store:

url to play store -> play.google.com/store/apps/details?id=de.huwig.sslverify&hl=en

Here is the screenshot (aborted because every last site returned "certificate mismatch"):

url to screenshot -> dumpt.com/img/viewer.php?file=s1tppuca9avpxtxqg50p.jpg

This is the 2nd phone from this vendor. 1st one wouldnt stay connected to the tower so I never had a chance to encounter this issue.

I am quite concerned about the possibility of these certificate chain errors reflecting intentional preloaded MITM capability.

I'm no newb to tech, security, or electronics, but my understanding of the CA chain is far from that of a developer. But one of the more paranoid of my friends, with equal or greater astuteness in the field of network security, had previously suggested that a lot of chinese phones come with pre-installed kernel vulnerabilities where certain syscalls run natively as root.

So needless to say, I'm posting this here in hopes that someone could offer an explanation for the output of SSL Verify that reflects a harmless, unintentional, and perhaps ubiquitous flaw in certain codebases (as has been suggested above) as opposed to, my worst fear, an imminent threat to whatever percentage of the android devices have this vulnerability.

EDIT:

I just tried creating a new APN (even though I am an AT&T customer the APN is WAP@CINGULARGPRS) with only the most minimal of parameters (both proxy fields blank etc.) when compared to the default which is presumably supplied by the tower/provider.

But regardless of whether this solves the SSL error 107 issue, running SSL Verify still shows the same list of certificates/signatures as mismatched as in the screenshot.

However I note, when watching the program run, that it is not ALL the domains that SSL verify checks - but it is at least half of them. If anyone has a rational explanation for this - or knows of another app I could install to attempt to verify the output - please let me know.
[HTC Sensation] pattmyn:
I just tested it and I'm good to go on LTE. Maybe check your ROM's modem to make sure they included the right bands for your model? I know I had to flash over an AT&T modem configuration on a ROM that said it worked flawlessly with the Canadian models.

I was having the same issue and the APN edit fixed it. Good work OP!

A fun quirk I had before was my longer texts being split 160 character bites when the phone should have been using the newer long SMS (which is a type of MSS lol). I worked on that for months. SIM was the issue and it didn't even know its own phone number lol. I finally got a replacement SIM this week after being dicked around for months.

Now if someone can just get SMS delivery reports working, all would be well in the world...
[HTC Sensation] hilroy97:
Recently loaded CM 10.1 on my Galaxy S3 (i747M) on Bell. Came across this issue and this thread helped me out.

Thanks to all.

Ed
[HTC Sensation] simboo:
Well,

Erasing Proxy and port saving and rebooting did not solve the problem for me.

Bell I747 running CM10.2 d2att (android 4.3.1)

Chrome beta 33.0.1750.70

After rebooting the phone, values in Proxy and Port come back to their old values.

My SSL problem happens when I try to do a search from the address bar directly. It loads a blank page, I hit refresh and then the SSL error is displayed.

When you do a search in chrome, it does it via h t t p s : / / ...

My Mobile network settings at a glance:

Network mode: GSM/WCDMA/LTE

Roaming mode: home only

CDMA subscription: NV

Access point name: pda.bell.ca

Proxy is getting its old value again and again: web.wireless.bell.ca

Port: 80

APN type: default, *

Bearer: unspecified

EDIT:

Changing "bearer" setting to LTE crashed the phone after I turned off the display and then back on again. Force rebooted (Power+Vol Down), crashed on reboot once, then came back to life and now it works normally. I don't have the SSL error anymore...

Go figure.
[HTC Sensation] Motorllica:
This thread fixed my Ssl issues. Cm11, Galaxy s4, on Bell.

Deleted port/proxy, also set bearer to lte (just incase).

Works flawless now. Signed up to xda to say thanks.
[HTC Sensation] superkev:
Thank you so much for figuring this out! It was bugging me on CM11 on my Nexus 4 and I thought I was just going to have to live with it!
[HTC Sensation] MorphlinQc:
Thank you, thank you, thank you, THANK YOU! Been trying to figure this out for 6 months, since I got Bell...
[HTC Sensation] MinisterPhobia:
I'm having this issue on a Nexus 6, stock OS, APN has no proxy or port set, by default. The odd thing is that this worked when I got the phone and in the last couple of weeks, stopped working.
[HTC Sensation] jcmascolo:
On the Bell network with HTC One M8 on Sense 6 and Android 5.0.1 and couldn't go to certain sites due to SSL error connection and recently also an app.

Removing Proxy value (web.wireless.bell.ca) and Port 80 fixed it for me so far! Thanks!
[HTC Sensation] ambusher2991:
Remove Proxy and Port from your access point

I don't think that there is a problem in CM codebase. Try removing the Port and Proxy from your mobile access point
[Member-Found Deals] tarryl:
GUNS! SEX! SECRET CULTS! AND MONSTERS! Nothing the BEST-SELLING and AWARD-WINNING creators of SLEEPER, CRIMINAL and INCOGNITO have done so far will prepare you for the explosive debut of FATALE! A reporter in 2012 stumbles on a secret that leads him down the darkest path imaginable to a seductive woman who's been on the run since 1935, a mobster who may be an immortal demon monster, and the stories of all the doomed men who've been caught in their decades-long struggle. FATALE blends noir and horror to tell a riveting epic unlike anything you've seen before.

Issue #1 of Fatale, a dark and gritty horror noir book, was recently made available for free get it now by visiting the link below. :good:

http://www.comixology.com/Fatale-1/digital-comic/NOV110354
[Member-Found Deals] grayfoxmg1:
Link is confirmed, though you have to create an account for their website.
[Samsung Galaxy Mini] sundaeproject:
Hello guys...i found this deep sleep widget in google play and i wanna share it so you can check whether your phone is in deep sleep or not and it shows in percentage. if it works then the percentage will increase.
[Samsung Galaxy Mini] Greatness_GH:
Cpu spy does a lot more! Try it
[Samsung Galaxy Mini] thealliens:
What is this app?
[Samsung Galaxy Mini] 4rif:
nice share :)
[Samsung Galaxy Mini] pratyush369:
Please for having post counts or thnxx please don't post rubbish........

P.S.= Don't Spam:mad:
[Asus Transformer TF700] psych2l:
If you're like me, you love floating apps. They're a killer feature that makes multi-tasking that much easier. Chainfire just released his latest app, PerfMon in the play store. It's a floating performance monitor that tells you how much free memory you have, cpu core usage, and disk I/O usage among other useful metrics. It definitely looks useful when troubleshooting games, and seeing whether a slowdown is due to bad I/O or RAM usage. You can find it here:

https://play.google.com/store/apps/...51bGwsMSwxLDMsImV1LmNoYWluZmlyZS5wZXJmbW9uIl0.
[Samsung Galaxy Nexus] wjsmaggle:
Hey all,

I've been trying to find information on this through various forum and Google searches and haven't been able to sort it out. Basically, from what I can tell, AVRCP and MAP were fully implemented in CM9 and AOKP ICS. Then when Jelly Bean was released, it took some time but now CM10 and AOKP are supposed to have these two bluetooth features. The problem is, in my 2011 Ford Fusion, I still cannot have text messages read to me (a feature dependent on MAP) and I can change the song from the radio but I cannot view track information (a feature dependent on AVRCP). Am I doing something wrong or are these features not implemented in these ROMs as I was expecting?

Thanks!

Wes
[Samsung Galaxy S (4G Model)] lexman098:
This is a pretty general question, but I couldn't find much on google about this. According to the task killers on the market, an app won't be able to stop a service like exchange or maps automatically (it can only kill the UI app). However, the exchange and map services have lots of alarms associated which increase my battery drain by at least a full %/hour. If I kill the services manually every time I use one of these apps then everything is fine. Does anyone have insight into whether an app or script called from tasker can accomplish this automatically?

FYI: I'm using the CM9 unofficial ROM.
[Samsung Galaxy S (4G Model)] th3controller:
You do not need to kill tasks. The system automatically purges non system apps. Just leave them be and always exit an app using the back button
[Samsung Galaxy S (4G Model)] jeffsf:
"App killers" aren't recommended past Froyo and can even harm performance.

Under ICS, you can "Disable" many apps using the Manage apps off the main-screen menu. Titanium Backup can also "freeze" apps.

Many of the Google services get pretty "greedy" depending on your settings. That would be a good place to start for "core" services like those.

If that doesn't work, there is the sledgehammer approach of removing the apk from /system/app -- If you do that, watch your logcat to provide some confidence that you haven't disabled something that you need for another app to work.
[Samsung Galaxy S (4G Model)] lexman098:
Le sigh.. didn't even read my post. Also I'm pretty sure the back button thing is a myth.

Anyway I'm not trying to kill the "apps" themselves. They can sit paused in memory. I want to end their back-end services without uninstalling the app. The exchange service, like I said, will drain the battery with its unnecessary alarms even if I disable sync and turn the sync frequency to "never" and uncheck all the boxes when deciding what to sync. Google screwed up majorly with exchange, but when I kill the service manually using the method you describe then everything is fine and I can still boot up the app like normal to check my email manually. I just want to automate killing the service.
[Samsung Galaxy S (4G Model)] lumin30:
Unrelated to your OP but related to your post - on CM9 based ROM's - if you go into Settings > Developer Options - scroll to the bottom and select kill app back button. It works well.
[Samsung Galaxy S (4G Model)] ReelFiles:
I am also interested in a solution to this. I was hoping to find a widget that displays services, daemons or whatever you wanna call them, in plain text on my home screen, similar to rainmeter for windows. Then you just tap it to manage them. There has to be something similar around.
[AT&T, Rogers HTC One X, Telstra One XL] robbieismyname:
I'm using the latest viper but seem to have lost the ability to connect to a pc. I have the usual menu boxes checked and debugging on and have tried a few pcs. The pull down notification does not come up. Any help appreciated
[AT&T, Rogers HTC One X, Telstra One XL] DvineLord:
i assume your on telstra. seems like .au has trouble using most roms. if you look in the viperx thread it shows how to get the build.prop setup on telstra. let us know if your problem was build.prop related.
[AT&T, Rogers HTC One X, Telstra One XL] robbieismyname:
Update...can you believe it was the usb cord that needed replacing. Rom great
[AT&T, Rogers HTC One X, Telstra One XL] DvineLord:
good thing it was still just your cord. you should still search for the build.prop mods in the viperxl thread if you are on telstra.
[AT&T, Rogers HTC One X, Telstra One XL] 18th.abn:
I had the same problem connecting mine too. Sobering up allowed the hand eye coordination I needed to get it plugged in:D
[Gen8 General] sungod88:
Hey all I'm getting is the Archos screen then it freezes...I think I may have bricked it. I went into Dev edition and tried to format the whole device but that didn't work. I was running a rooted rom then the Graphics started acting funny. I went in tried to reset the firmware and now it's not working. Anyone have a fix I can attempt
[Gen8 General] surdu_petru:
Hi !

What version of rom you had installed before !
[Gen8 General] sungod88:
It was actually 4.0.7 from.you haha. I installed a few apps then the graphics got funny so I tried to repair next thing I know it freezes on the opening screen. I imagine i.just have to reflash the image but how can I adb push it if i.can't get my system on.
[Gen8 General] kareeem:
Moved to general.
[Gen8 General] surdu_petru:
can you try to see if adb works ?

> adb devices

let me know if it works ...:good:
[Gen8 General] sungod88:
I thought of that to but no device shows up in the a80s screen and in the frozen screen no device either
[Gen8 General] surdu_petru:
Ok !

but how did you manage to install aRom for Gen9 in a Gen8 device ?
[Gen8 General] sungod88:
I'm using a g9 device Idk how we ended up.in g8 section.lol but it's the 80 g9 I tried everything I can think of :(
[Gen8 General] sungod88:
Anyone with some advice Also could a Mod please move this to G9 General. My device is the 80 G9. I can't push to ADB because the device won't boot. Is there anything else I can do?
[Gen8 General] sungod88:
GOT IT! Had the bright Idea to grab the small firmware from the Archos site and do the firmware update with it from the A80S menu! thank god lol