yashsingh1/xdaforums huggingface dataset:
[8125, K-JAM, P4300, MDA Vario General] agentp:
one thing with the spb stuff, i found that a straight upgrade made the software worse, that only a clean install with the latest software worked. the newest version of pocket plus is very good btw
[8125, K-JAM, P4300, MDA Vario General] Giordano:
uhm :shock:

i have the same issue but after my Wiz leak 5 meg it stops to do it.

SPB pocket plus it works fine for me and as I said the leak is related only to 5 mega..after it, the leaking stops.
[8125, K-JAM, P4300, MDA Vario General] jeasbe:
y Wizard Runs pretty fast otherwise,

I dont have any extra Plugins other than SPB pocket Plus or Today Agenda.

When the Outlook is synched (contacts and appointments) I have around 3000 contacts Now.

The PIM file is 7 mb.

After the sync the device slows down a Lot.

Also there are two startup programs (system)

1 FILESYS.exe Takes around 1.8 MB at startup

2. GWES.exe . 1.28 MB(STARTUP)

As the device is used their size increases to ( 2-2.5 MB )this slows the device further.

Pls see pics attached <before and after>

using Oxios or any other memory closing app does not sort the problem out.

ONLY Rebooting sorts the problem.

Secondly, Is there any way I can shift my PIM.vol to the storage card?

coz I have noticed that when the Device memory is sufficient it also allocates sufficient Running memory to the Programs. I feel at least 20 Mb shold be there.

Or is there any Program which allows to MANUALLY ALLOCATE memory to <STORAGE> and <PROGRAMS>

Like in My O2 XDA..In wizard the slider does not move...

MY MAIN PURPOSE IS TO LEAVE MAXIMUM SPACE EMPTY on My C drive.(device)

thanx in advance.....

Regards,

______________________

GURJEET SINGH BAGGA

Microsoft Certified Proff.

[XDA2,O2MiniS,P900i,]

Say NO 2 Pirated S'Ware,Illegal Cracks

A BIG :"NO" TO WAREZ

Regardless of what others Preach & Practise.

Believe in urself And Just DO the Right Thing.
[8125, K-JAM, P4300, MDA Vario General] patrickem:
Only way to move the slider in the last pic would be if you were using WM2003se
[Nexus 7 Q&A, Help & Troubleshooting] or.shiny:
Hello! I got a 2012 Kot49h 4.4.2 with touchscreen issue.. I've tried flashing the ts10 from sfhub

Which helped for about a day or so.. Now I want to try the other ts but I am currently traveling and don't have acsses to a PC..

Any way to flash them without a PC?

Any help appreciated, +1 good karma.. =)
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
Hi, or.shiny...

You can use the

flashify app

to flash boot.img's or recovery .img's directly from the device itself.. however, you do need to be rooted.

If you're not rooted, then you're going to need a PC, unfortunately:(.

Rgrds,

Ged.
[Nexus 7 Q&A, Help & Troubleshooting] or.shiny:
Just so happen that I am rooted! Trying it now! Thanks a lot! =D
[Nexus 7 Q&A, Help & Troubleshooting] GedBlake:
No, problem... but just remembered that the free version of flashify limits you to just 3 flashes per day.

Rgrds,

Ged.
[Sprint HTC EVO 4G LTE] RedSSilent:
I am new to the whole phone rooting process and I followed qbkings instructions on youtube to root my evo 4g lte.

The whole rooting process went fine. Until I went to install busybox so I could run nandroid.

I have tried both the jrummy busybox installer and the busybox by stephen and they both result in failure.

I don't know what else to try. If this is something simple I am sorry. I tried searching google for the answer for about an hour and came up with nothing.

Thanks
[Sprint HTC EVO 4G LTE] Magnum_Enforcer:
Hit the "My Files" link in my sig, then click on the EVO 4G LTE folder. Download the Busybox file to your phone, then flash it in recovery.

Sent from my EVO LTE
[Sprint HTC EVO 4G LTE] RedSSilent:
You sir! are amazing!

Thank you
[T-Mobile Samsung Galaxy Note 3] rhetorician:
Hi Folks:

I'm afraid I rooted a couple of my devices via Kingo a couple weeks ago and only now am I learning of the various confirmed/potential consequences. Based on feedback from a couple programmers and developers, coupled with what I've seen in some of the forums, this application employs its exploit as a guise not only to obtain personal information on the device, but also the PC. Furthermore, from what I understand, it installs very questionable, unnecessary material on one's PC that enables KINGO to track a user indefinitely.

In any case, I want to ensure that I can verify the material that was installed on my PC/phone and to greatest extent possible, remove all traces off my PC. That's my first objective. Second, I'd like to address my device in much the same capacity. Unfortunately, I'm quite lay when it comes to technical matters of this nature and thus I reach out to the community for guidance.

Thanks!
[T-Mobile Samsung Galaxy Note 3] BACARDILIMON:
Your PC will have to be cleaned very well.

Your phone will wipe it go back to stock and root away

TWEAKED 2.0
[T-Mobile Samsung Galaxy Note 3] rhetorician:
Roger that. I feel pretty comfortable rescuing my devices. It's the PC I'm worried about. What, exactly, does "very well" entail? Do you recommend a particular program? So far, Microsoft, McAfee, and Iobit all fail to identify potential vulnerabilities.
[T-Mobile Samsung Galaxy Note 3] BACARDILIMON:
I am a security freak so you can't go by me. My step would be a full wipe on PC. But that is so extreme. I think is u use good virus protection and a reg checker/ cleaner you should be good. But I am not a pro. You might need to check in PC forums

TWEAKED 2.0
[T-Mobile Samsung Galaxy Note 3] str8killinya:
I had my PC checked by many friends who are in the security business and they found nothing after using it. Since I have wiped and installed Linux but they found nothing on my system after using it

Temasek CM11 & Yank Powered SM-N900T
[T-Mobile Samsung Galaxy Note 3] daneurysm:
I don't know if I'd go so far as to install Linux (unless, of course, that works for you and your needs...then I would recommend the idea highly)...but to guarantee any level of success I would absolutely insist on a complete repartition and reformat of your hard drive (and an ODIN flash of the complete factory restore image....bootloader, recovery and all)

If there is any residual risk of compromise I would expect virus scanners to pick it up (but not McAfee or Norton...they are the most popular therefore the most targeted for compromise)....AVG, Kaspersky, Avira....Just like Opera is the most secure browser or OSX and Linux are the most secure OSs. It's not that it's necessarily the most inherently secure options but they are also representative of the smallest fractions of the market therefore they are less attractive. The effort required to compromise them would be better spent on a more popular attack surface.

If your personal information and device performance means a goddamned thing to you WIPE EVERYTHING AS THOROUGHLY AS POSSIBLE. I am not kidding, I am not overstating the situation in the slightest. Do as I say.

To do anything less is to consider your personal information (top priority) and device performance (secondary priority) less than important.
[T-Mobile Samsung Galaxy Note 3] pete4k:
Seriously now, does anybody have shred of evidence Kingo is a virus, besides hears says? Don't anti virus companies have a place to submit suspicious programs for evaluation? Did anybody with proper tools run trace to see what exactly Kingo is doing? There are tools to see registry entries made by Kingo and what they mean, there are ways to trace program etc I really would like to see some hard evidence or at least link to it.
[T-Mobile Samsung Galaxy Note 3] str8killinya:
LOL wasn't recommending Linux but yes I only installed win 8 to use kingo then back to Linux which is all I have used for years

Tweaked & Lean SM-N900T
[T-Mobile Samsung Galaxy Note 3] Towle:
The only security concern was their collection of your IMEI number. However, they removed this shortly after being contacted about it. As it currently stands, there are no known risks of using this program.
[T-Mobile Samsung Galaxy Note 3] pete4k:
That and using some public chinese website to store all the software fixes for all different devices, at least as far as I know. This is not some kind of program that appeared from nowhere last night, this was published by Kingoapp technology, or something like that and the program works as advertised. They don't want to publish source code and I don't blame them, maybe they don't want other people to copy their work, maybe they don't want Samsung to patch security holes they found, or maybe they use other developers work, I don't care. I think I read somewhere that none of the 27 or so respectable antivirus programs flag Kingo as harmful and by now somebody should have found something if there was anything to find, especially that there was so much suspicion and controversy. There is always a risk when you download software from the web (whole websites could be fake and look official), but I have not seen one single proof Kingo was harmful in any way from anybody yet and I'm sure many people used it already.
[T-Mobile Samsung Galaxy Note 3] krelvinaz:
This is all a red herring. The IMEI collection was the really only issue and they stopped that fairly quickly.
[T-Mobile Samsung Galaxy Note 3] xile6:
So it's safe to use?

I was planing to root my note 3 and kingo seems good was just worried.
[T-Mobile Samsung Galaxy Note 3] drag&fly:
I have encountered 0 problems using it. Used on my note and both of my note 3's. No problems PC or device wise. And there is no proof of KingoApp doing anything malicious, just hearsay.
[Sprint Samsung Galaxy Note 3] idtheftvictim:
I was wondering if anyone has any issues playing audio from their note 3 to a vizio soundbar. I am running temasek v45 with lean kernel 1.2.

The audio plays, but skips like crazy, and I have to keep the phone right in front of the soundbar to make it NOT skip.

Any suggestions?
[Sprint Samsung Galaxy Note 3] w7excursion:
Try stock rooted rom and kernel.
[Sprint Samsung Galaxy Note 3] ifly4vamerica:
I had this problem when I was using a galaxy gear. I ultimately got rid of the gear and all the apps on the phone pertaning to it and had to flash the stock kernel. Now no more skipping even from another room. If it matters I use poweramp and viper for android. I am not sure if it is because of the low energy bluetooth used by the gear or what .... just my experience.
[Sprint Samsung Galaxy Note 3] JimSmith94:
I am stock rooted and don't have a Galaxy Gear. My audio plays just fine on my Vizio S4251W-B4.

I'm not a BT guru so maybe someone can explain this to me. When I have the soundbar paired as Media audio and my Plantronics Voyager Pro headset paired as Call audio only, the headset doesn't work and phone calls ring in the soundbar.
[Google Chromecast] The S3 Kid:
Check this out from the man who made the AllCast app.

https://plus.google.com/app/basic/stream/z12weptwssfqidk5a04ccxsypuevhtcwgao
[Google Chromecast] bungadudu:
This is the answer to all
[Google Chromecast] bubbleguuum:
Sending video to Chromecast will not be too difficult.

Sending video + synced audio, all of this with minimum latency so it is actually usable will be much more difficult. I doubt it will be possible to do a better job at it than Miracast whose it is the entire purpose.
[Google Chromecast] bkmaracas:
I have a miracast dongle and used it about three times with n10 and new n7. Some apps of interest block output (sky go etc) the delay is short but too long for most games, the pic quality is Inferior to hdmi, so what are you left to do with it? Photos/video? Which we can now do easily at hq .. My only use case idea was communal game watching, which is kind of dull really. I was excited to try it but seriously the reality is not that exciting. Still a nice feature to have I just dont fathom the idea its the best thing ever. After two minutes of pointing and going 'mirroring with android!!' You will likely be bored

If you have a killer use i've missed do say.

Sent from my Nexus 7
[Google Chromecast] The S3 Kid:
Why is it difficult for chromecast to mirror things? What's inside the miracast dongle that isn't inside chromecast? :confused:
[Google Chromecast] EarlyMon:
Completely different software, possibly different hardware such as more ram.

Miracast was designed for this - think of it as wireless HDMI over a peer to peer connection.

Chromecast was designed to receive content via the internet with control from any device on the same network, not peer to peer.
[Google Chromecast] styckx:
Chromecast mirroring is going to lag like hell. Why even waste your time with this? Ever send a 3MB jpeg to Chromecast? It loads like you are on a 56k modem..
[Google Chromecast] EarlyMon:
^^ This.

I've seen a lot of folks say that they want MX Player, MoboPlayer, etc etc, supported.

Others still can't figure out how to get their phone videos visible elsewhere.

If he's solved the expected audio syncing issue then this is going to make those camps very happy. I doubt they'd care about an initial delay.

PS - lest we forget: https://developers.google.com/cast/docs/media

The ASUS Miracast Dongle specs for that, for comparison -

For video to work, most cases are ultimately going to amount to transcoding.

I'd imagine that he's solving that by catching the streams at some common point, possibly in a framework, and encoding those.

And that makes sense if you're going to mirror homescreens and anything else.

If what I suspect is true, this is likely going to be a rooted-Android-device-only solution.
[Google Chromecast] ralphwiggum1:
He's probably going to take what he already has in the Mirror.apk (which does screen recording and mirring to AirPlay and also to a "computer").

The computer streaming sets up a web server on the phone where the stream is played. He will likely take this and display it in the Chromecast web container. Hopefully it will also be more reliable.
[Google Chromecast] EarlyMon:
I'd completely spaced that, many thanks.

https://plus.google.com/110558071969009568835/posts/Z9kB5vyGQtJ

As he said there on December 12th,

So, I haven't followed that since the announcement, hopefully the future has arrived and root won't be necessary.

If the 4.4.2 rev is still required, I predict some gnashing of teeth.

He also mentioned,

The web server is no surprise, that's a given for Chromecast.
[Google Chromecast] The S3 Kid:
Here it is. https://plus.google.com/110558071969009568835/posts/Z9kB5vyGQtJ
[Google Chromecast] bungadudu:
Doesn't work with chromecast.
[Google Chromecast] EarlyMon:
That's the old Mirror beta that [MENTION=1540557]ralphwiggum1[/MENTION] mentioned.
[Google Chromecast] mdamaged:
Dun dun duuuun!
[Google Chromecast] lazyn00b:
But, but, but... the doubters said it couldn't be done?! :laugh:
[Google Chromecast] bhiga:
Impressive! I'm curious to see how it does for actual video, and hopefully it will apply to Chromecast (right now it seems to be "playing" on Mac)
[Google Chromecast] Postal Psycho:
get 'r dun!! yeaaaa
[Google Chromecast] styckx:
And now on Chromecast.. The lag isn't as bad as I predicted, although at the end it gets pretty bad.

https://www.youtube.com/watch?v=oIhACF2mReY
[Google Chromecast] EarlyMon:
Count me in as happy to eat crow, I had a lot of doubts.

Now I'm curious about videos and what the final requirements will be.
[Google Chromecast] bhiga:
Same here. I'm curious about the Android 4.4.2 requirement (mainly because I don't have 4.4.anything), I wonder if it lets Koush hook into the display updates. That would be far more efficient than simple screen scraping like the Cast extension seems to do. Or maybe he's using the native Miracasting and redirecting it out to Chromecast.

Regardless how it works, waiting to see it working for Chromecast.

Sent from a device with no keyboard. Please forgive typos, they may not be my own.
[Google Chromecast] EarlyMon:
I spent several hours last year discussing what happens with MHL output and (resolution) scaling with one of the better known CM team members (who asked for no name dropping) going over what happens in hardware vs software (those who have heard of me are familiar with the fact that I've been a good source of chip datasheets in the past), so I had a number of conceptions (probably all misconceptions now).

Anyway, I got the impression that a lot happens in the display layers (more than I expected).

I've obviously no idea what Koush has done but I think that the tell was when he said he said he had to replace the virtual display layer with his own (among other things making it more DRM friendly) but that root wouldn't be required in the future.

Root not required, if true, suggests strongly to me that the allocations for the display layer(s) have been redone by Google (not unusual for layers to change allocations on any system software).

I root but don't often run AOSP on my Android because I've lost MHL on my device doing that in the past.

And I rely on MHL from time to time.

So, what this means to me is that I might have access to more roms and substituting casting for MHL rather than losing that capability. It's going to have to be pretty forgiving for me. I'm running a 2012 S4 Pro, far less horsepower than that available today and no burning desire to go buy a new phone. So this might widen my options in the future. Today, I'm curious.
[Google Chromecast] Asphyx:
It was never a matter of if the Hardware could do it...

The holdup has always been the software and the Whitelist that is required to let software work. Software can be changed only hardware limitations are problematical.

Miracast will NEVER to what CCast can do...

But a CCast can easily do anything a Miracast can va software.

EarlyMon - This is why I couldn't understand your point regarding APIs, APIs are nothing more than code that can be easily changed, Bypassed, even lifted and added to to get the result you desire. I'm an engineer and in my book Software has no limitations at all only the programmers limit what they are capable of. The Hardware if designed properly can almost always do much more than it's designer ever intended and if not the Hardware designer wasn't very good!

The CCast has everything that Miracast does and more....

Has Network access to get data

Even has a way to directly connect via Wireless if you had to.

Has a way to display that data to a screen

And while it does not have the proprietary means to connect to a device that isalso connected to an AP it doesn't need it because you can talk to it on the very same network VIA the AP your all connected to.

As for the 4.4.2 requirement I think it has to do with the 4.4.2 support for mirroring devices (Miracast specifically) built into that version of Android. It Exposes the Display for capture and re-transmission. Earlier versions with Miracast support may be supported as well in time with a bit of coding to fool the system into thinking a CCast is a Miracast device.

But older versions (pre-Miracast enabled) of Android may never get Mirroring due to the way the Display driver is written in those versions.

While you could code it externally using some system similar to screen capping, it would function like a pig, have a very low frame rate and slow the device you are trying to mirror to a crawl.

So I don't expect anyone stuck on an early version of Jelly Bean, and any version of ICS or Gingerbread to ever see Mirroring anytime in the future.

The Display driver probably has no exposure points to get the data to Mirror.
[Google Chromecast] bhiga:
True, though more and more these days things are designed or optimized to be super-lean. Usually the first-rev units have a bit more headroom, then future revisions get optimized more and more. A friend once designed motherboards and they always came back from production missing parts. He's a good engineer and would complain because he put those parts there for a reason, but manufacturing said "It works okay without them" so that's how they got made... Only strict companies and those with strict testing can maintain high-quality builds that include headroom nowadays.

Yeah, looks like it has to do with how the sinks, surfaces and buffers are handled. Well, Samsung promised KitKat for GS3, so we'll see if/when it arrives.
[Google Chromecast] EarlyMon:
I was an R&D director in the semiconductor industry for over a decade, have co-authored a complete SMP OS, have software flying in deep space, am listed as sole and joint inventor on a slew of hardware and software patents and fwiw, was a member of a rom team here, as a tester.

I think I'm fairly close to understanding some things about Android and mobile phone hardware platforms.

I've already been happy to eat crow for my initial doubts, but as for this becoming available for any recent revision without root and being supportable for all popular hardware, I'll maintain my opinion that we'll see soon enough.

I understand that the beta is available to test from other threads so I'm sure much more information will be forthcoming.
[Google Chromecast] bungadudu:
Yay for mirroring video + audio from android to Chromecast!

https://www.youtube.com/watch?v=CIwZB9fnoC4

Thing is koush also said his chromecast got pretty hot a few days ago so he had to buy a new one..
[Google Chromecast] EarlyMon:
https://plus.google.com/app/basic/1...ic/stream/z13dynigcn2ci3ay004ccxsypuevhtcwgao

In chronological order for those who don't want to go to g+...

5 hours ago, casting Spotify shown.

So let's review -

* Still using webrtc, not a new casting methodology added by Google for 4.4.2.

* Might be better if Google changed the Chromecast firmware.

* Private, undocumented, or missing APIs prevent developers from being able to do all that they can imagine.

By the way, pretty sure that display drivers, the code specific to each Android display by manufacturer, have nothing to do with any of this. Koush said that he's working at the virtual display level, not the specific display level.

This is still true -

Looking at Android source code > Guessing.

And it always will be.

Edit/PS - API stands for application program interface and specifies how to call a method built-in to a software library. There's no such thing as a private API - everything available to application programs is published, so APIs are public by default. But "private API" (to indicate that a method exists but isn't available for public use) and similar terms are thrown about nowadays, especially by Java programmers, and when in Rome, etc etc. Substitute "method" for "API" if it bothers you. ;)
[Google Chromecast] EarlyMon:
Please see How Miracast Works on Android (XDA thread).

Throw an MKV container at Miracast, watch it work, it's supported.

Do the same with a Chromecast with the latest 15250 firmware, watch it fail, it's not supported. (edit - bubbleguuum says it is and does it)

After the fact, everything looks easy. During engagement, not so much.

Cheers. ;) :)
[Google Chromecast] rkirmeier:
Miracast does not connect to a WAP, only Wifi Direct so I don't see how it could ever work like a Chromecast (stream from Internet)...
[Google Chromecast] EarlyMon:
I think we all agree on that. :)

Unless bridged from 4G, which - is hardly the point.
[Google Chromecast] bhiga:
Always. It's the intersection of Moore's Law and Murphy's Law.

From http://www.nextpowerup.com/news/2199/google-chromecast-powered-by-marvell-armada-1500-mini-cpu.html

The Armada 1500-mini platform seems to support a bit more than has been officially published, so to some degree Google does seem to be taking a conservative approach - perhaps due to the heat issue that Koush ran into. Just because the platform supports something, it doesn't mean the packaging or environment will. It's like fanless PCs that are purposely underclocked.
[Google Chromecast] EarlyMon:
Exactly why I'm always saying "supportable," which is far different from doable.