Ive been reading on this and was curious. I know infuse and skyfire have this on there system. Looks Like WE HAVE SOME evidence that we do have this installed.
CHECK SECOND POST
Here is OG posted and what it doeshttp://forum.xda-developers.com/showpost.php?p=11763089
http://forum.xda-developers.com/showthread.php?t=1122569
Here is more info on it really starts on post 55 http://forum.xda-developers.com/showthread.php?t=1338733&highlight=Carrier+IQ&page=6
HERE IS HOW TO CHECK (CAPPY DOES HAVE SOME)
DOWNLOAD Supercurio Voodoo Carrier IQ detector at the market here is link(THIS IS MORE FOR OUR DEVICE) and what I used to find on my and my wife cappy
https://market.android.com/details?id=org.projectvoodoo.simplecarrieriqdetector
This one doesn't show any detected on our device
http://forum.xda-developers.com/showpost.php?p=17612559&postcount=110
HERE IS GOOD READING ABOUT
http://lifehacker.com/5863895/carri...everything-on-your-phone-and-how-to-remove-it
http://www.xda-developers.com/android/the-rootkit-of-all-evil-ciq/
http://androidsecuritytest.com/features/logs-and-services/loggers/carrieriq/
twolostminds said:
By now anyone who has an Android phone has heard about CarrierIQ, CIQ or IQAgent. Business Wire in London announced on June 8th:
For the few who may be scratching their heads wondering what CarrierIQ is...
Steve Topletz, a member of an international group of hackers, human rights workers, lawyers and artists that fights internet censorship and promotes the right to privacy has described it as follows:
Information on CarrierIQ can also be found in the ACS SFR Epic4G ROM discussion thread and a thread I started requesting information from Epic4G Dev's here.
References to CIQ have been found deeply embedded Epic4G
Code:
Provided by chris41g
to be effectively removed you only need to remove it from 4 files. it is referenced elsewhere scattered throughout... but the four main files are
DialerTabActivity.apk
ext.jar
framework.jar
services.jar
then in the kernels initramfs, you have to disable the service in the init.rc
Provided by mkasick
Here's all the files that reference "CIQ", "carrieriq", or "libiq" with instances unrelated to Carrier IQ removed:
/ (initramfs):
- init: /dev/ttyCIQ0 UART, presumably to communicate with radio.
- init.rc: Start iqmsd service if property:service.iq.active=1.
- lib/modules/dpram.ko: Implements ttyCIQ UARTs.
/system:
- app/DialerTabActivity.odex
- app/FactoryTest.odex
- bin/iqmsd
- framework/ext.odex
- framework/framework.odex
- framework/sec_feature.odex
- framework/services.odex
- lib/libiq_client.so
- lib/libiq_service.so
Of these, bin/iqmsd is a purpose-unknown daemon, and libiq_client.so & libiq_service.so the client & service native code. The client & service managed code is implemented in framework/ext.odex & framework/framework.odex respectively.
In addition, the following framework classes reference Carrier IQ in some fashion:
framework/ext.odex:
- org.apache.http.impl.client.DefaultRequestDirector
framework.framework.odex:
- android.inputmethodservice.InputMethodService
- android.net.http.Request
- android.webkit.{BrowserFrame,CallbackProxy,LoadLis tener,WebViewCore}
- com.android.internal.telephony.SMSDispatcher
framework.services.odex:
- com.android.server.BatteryService
- com.android.server.WindowManagerService
- com.android.server.am.UsageStatsService
Finally, libiq_service.so is used exclusively by framework/framework.odex (com.carrieriq.iqagent.client.NativeClient), and libiq_client.so is used by:
- bin/iqmsd
- framework/ext.odex (com.carrieriq.iqagent.service.IQService)
- lib/libopencore_player.so
Makes you wonder what might be in the closed source.
The Android platform, like Linux, is based on openness. I am calling on all Android developers, programmers, hackers and users to band together as a community and come forward with any information you may have on CarrierIQ.
I am asking all those with the knowledge and resources to delve deeper into this issue to please do so and help spread the truth.
For anyone who wishes to contribute confidentially and anonymously please email:
CIQINVESTIGATION @ VERIZON dot NET
Click to expand...
Click to collapse
I am going to start adding what ROMS have it and locations so that way we have handle on this thing for future reference. I need your guys help on what roms you are running and locations
These DO NOT have any CIQ
Andromeda3 (2.2 ) Froyo
Nothing found here. Not even empty libraries.
Serendipity VII (I9000XXJVO 2.3 Gingerbread)
Stock Froyo UCKB1
MIUI
ANY AOSP ROM
IF You find files under XBIN
I have and others have deleted or renamed the /system/xbin/iqbridged file and so far no adverse effects. Im not responsible if you do and bad thing happen.
FOR THOSE GETTING FILES UNDER
Test for: Android logcat debugging log
(LOGCAT, confidence 100)
just delete after each startup by doing this with Terminal Emulator
su
mount -o remount rw /dev/
rm /dev/log/*
OR
You could also try deleting the folder /dev/log (delete "log")
Do NOT delete /dev/
FOUND THESE *Using Supercurio Voodoo Carirer IQ DETECTOR
Cog 4.5.3 (I897UCKB1 2.2) Froyo
/system/xbin/iqbridged
Stock (I897UCKK4 2.3.5) Gingerbread
Stock (I897UCKF1 2.3.3) Gingerbread
/system/xbin/iqbridged
Serenity 6/6.1(I897UCKK4 2.3.5) Gingerbread
/system/xbin/iqbridged
FUSION XII (I897UCKK4 2.3.5) Gingerbread
Roms bineraries and daemons
/system/xbin/iqbridged
Pinnacle 1.3 (I897UCKH3 2.3.4) Gingerbread
Roms bineraries and daemons
/system/xbin/iqbridged
Andriod logcat debugging log
D/IQClient( 232): new IQClent()
Cognition 5 v2(I897UCKF1 2.3.3) Gingerbread
/system/bin/iqmsd
/system/lib/libiq_client.so
/system/lib/libiq_service.so
FASTY 3 KK4
/system/xbin/iqbridged
MaxQ/Sparko KK4
/system/xbin/iqbridged
It says that it's very difficult to turn off with Samsung devices but that there is an off switch. Where is it?
As I understand it, all Samsung android devices have it deeply embedded, so much so that removing the binaries will cause boot to fail. Sign me up for a removal tool. I'm not a dev, but this kind of garbage makes me wish I was. I wonder how much CIQ charges the NSA for their 'services'? Somebody call 60 Minutes....
OwenW71 said:
As I understand it, all Samsung android devices have it deeply embedded, so much so that removing the binaries will cause boot to fail. Sign me up for a removal tool. I'm not a dev, but this kind of garbage makes me wish I was. I wonder how much CIQ charges the NSA for their 'services'? Somebody call 60 Minutes....
Click to expand...
Click to collapse
+2
9CHAR
I just flashed stock froyo to my phone from gingerbread and did not see any libiq service or libiq client in the system/lib folder
Sent from my SAMSUNG-SGH-I897 using Tapatalk
bump for a true answer
sfernandez said:
bump for a true answer
Click to expand...
Click to collapse
Our phone does not have CIQ on it.
Sent from my Captivate
miztaken1312 said:
Our phone does not have CIQ on it.
Sent from my Captivate
Click to expand...
Click to collapse
Can you please elaborate on how you know this and what did you check to verify that we dont have it?
logging test app.by trevE
for the purpose of testing ciq
and by talking to the the other devs when i offered to help...
and by just reading and trying the things it says in the things you are reading...
TRusselo said:
logging test app.by trevE
for the purpose of testing ciq
and by talking to the the other devs when i offered to help...
and by just reading and trying the things it says in the things you are reading...
Click to expand...
Click to collapse
So thats everything u did? sorry Im hella slow this morning mind not working for SH**T
no prob.. no point doing what others have done. and cant know without asking.
TRusselo said:
logging test app.by trevE
for the purpose of testing ciq
and by talking to the the other devs when i offered to help...
and by just reading and trying the things it says in the things you are reading...
Click to expand...
Click to collapse
Thank you I added in OP trevE post about removing it so it others have concerns and some more reading..THANX AGAIN
This thread was reported, and I agree, I think this belongs in General, not Q&A.
Cognition
My Captivate is running Cognition 5.2. I ran the CIQ checks in the Logging Checker apk. The CIQ File List returns with three entries:
/system/bin/iqmsd exists!
/system/lib/libiq_client.so exists!
/system/lib/libiq_service.so exists!
Am I interpreting it right that my phone has CIQ? I have a screenshot, but it seems I need more posts before I can post it.
Max Tempest said:
My Captivate is running Cognition 5.2. I ran the CIQ checks in the Logging Checker apk. The CIQ File List returns with three entries:
/system/bin/iqmsd exists!
/system/lib/libiq_client.so exists!
/system/lib/libiq_service.so exists!
Am I interpreting it right that my phone has CIQ? I have a screenshot, but it seems I need more posts before I can post it.
Click to expand...
Click to collapse
Two CIQ libraries and a binary daemon - I'd say that's a pretty strong indicator that you do
Running Team Hacksung ICS.. Looks like it's clean, as nothing opened.
Is this for firmware 2.2 or just original stock?
Cognition 5 is based on the official release of 2.2 KB1
My Captivate is running Stock Samsung Froyo 2.2 KB1, I have a running application called Mobile Tracker Settings in my list that when I press force close does nothing but highlight the button blue. DOES NOT FORCE CLOSE. are you going to tell that's not odd?
Most people are running 2.3.3+ builds BASED OFF OF CYANOGENMOD 7's Kernel, which in turn if you read the articles would indicate that the CM Kernel's have the CIQ hooks removed already so CIQ is not present on ROM's based on Recent CyanogenMod updates.
Just because your phone doesn't have it doesn't mean it doesn't exist...
Stinking stuff this CIQ !
Of course, the concept itself already exists on every PC running windows - it is called error reporting. Every time you have a crash or software error, you get a pop-up that asks whether you want to send an error report. Ever see that?
The one BIG difference is that it GIVES YOU THE OPTION of not sending. I never send error reports. The situation here is a little more sneaky, because on the phones there is no pop-up that allows you to choose "Don't Send". Malware like keyloggers etc. use this to "evil" ends. So the problem is not that it may be for innocuous error collecting, but someone with savvy can actually use the CIQ via an app you download to collect this info.
Manufacturers need to stop this or provide ABSOULTE GUARANTEES that it will not be misused or cannot be hacked in form another app. And that is where my beef is with this S^&t peice of software. Unfortunately, this stuff is so rampant in everything any device collects data - including browsers like Chrome and PCs and iPads - we need an "OCCUPY S*^T DATA COLLECTION" movement to make this prominent.
Related
Hey all.
Sony Ericsson have stated quite clearly.. "No Flash on X10". Despite being quite categorical, there is much more to the story... so sit back with a coffee, and allow me to explain;
{disclaimer: i've only had an Android smartphone (Nexus One) since about June, so my experience had been exclusively using Froyo until now}
As far as i'm aware, Flash-Lite ran on certain HTC devices with Android Eclair (2.1) but this was done thru the device's default browser using webkit's plugin permission.
Flash 10.1 on the other hand is designed to run on Froyo (2.2) using a more direct Google plugin to the browser. (possibly an API not reliant on webkit as default, thus allowing other browsers to gain plugin access)
Anyway.. Sony Ericsson, for whatever reason, hasn't included either of these methods in this Eclair release. Conspiracy theorists may point to the coming PSP-phone as one reason to omit Flash.. ie. free multiplayer web-games.
So anyway, that's the bad news! No browser-based Flash unless it gets hacked into X10 by someone, or the bootloader get cracked, etc etc.
Ok, now the good news;
Hardware performance isn't a factor, as X10's Arm7 CPU IS supported by Adobe Flash + Air when running Froyo, as it clearly states X10's compatibility on their developer page.
Even better news for flash aficionados;
Lucky for us, Adobe made an early version of Air (ie. Flash outside the browser) for Android which runs just fine on Eclair. Although it's no longer under development (hasn't been since June) it's therefore unsupported by Adobe, and missing the odd feature such as GPU acceleration.
However, my early tests show it runs pretty well, comparing it to my Nexus One at least.
There are some limitations such as only running newer Actionscript3, (and no multi-touch, ha-ha ;O) ..but i can still see a great opportunity promoting and supporting Air on the X10. More so since every Air app or game i've seen so far only runs on Froyo.
As i see it, there's now a distinct niche supporting Air for Eclair userbase, so i hope some of you will consider helping me to exploit it. I'm here to help however i can, like porting as much stuff as possible to run on our Eclair devices, and ask anyone who's interested to offer support such as testing, designing, coding, or whatever. (PM or post here if interested to help out) I also propose a unique identifier; 'EPX'. The meaning will become obvious later.
To kick things off, i've attached a splash image, the Air Runtime for Eclair, and a sample game to test it. Here are the details about the game;
-------------------------------------
- Called "Code Bummer" made by Jesse Freeman, Dan Wolfe, Sean McCracken. (renamed "Hobo" with new icon, and recompiled to run on Eclair)
- Source code; http://github.com/jessefreeman/codebummer (a very clean example of a flash game for Android!)
- Description; http://www.appbrain.com/app/code-bummer/air.com.gamecook.CodeBummer (members will notice it says "Your device has Android 2.1. However this app is for Android version 2.2 and higher")
- Performance Tip: I find that after starting the game, the responsiveness is a bit slow, so i press back button (out of the game) then reload back into the game, and performance is much more playable.
-------------------------------------
Enjoy!
[UPDATE]
Anyone interested in developing Air for Eclair apps or games (that will also work on the latest Air for Froyo runtime) should stick to ONLY using the June 3rd SDK here...
(AIR25_win_sdk_20100603.zip)
http://www.mediafire.com/?m19cetvay9xqx38
Or the June 3rd CS5 Air Extension here...
(AIRforAndroid_FlashCS5_060310.zxp)
http://www.mediafire.com/?22hewf5kg98u3sd
Both of ^these are for Windows developers only.
We are also looking for the existing Linux and Mac SDK's dated the 3rd of June. If you have one of these, then please let us know, so that we may share it with everyone who needs it.
Cheers!
hi
that`s really good news(?) for us
unfortunately I have no knowledge in these areas but no doubt that I make available to serve as guinea pigs (?)
just hope this idea don`t die young and devs who had the knowlage will help you on this
Air for Android Developer Links
Thanks. It's a big catchup being couple of years behind the java devs, but strength in numbers helps.
Useful links for anyone getting started with Air development on Android;
"Using AIR for Mobile Development" (slideshow) *new*
"How to Add a Splash Screen to Your Air for Android App"
"How to Import MovieClips into a Flash Builder ActionScript Project"
"Optimization Techniques for Air for Android Apps"
"Sample Employee Directory Application using Flex and AIR for Android"
Using The Accelerometer Sensor in ActionScript 3
...
All my knowledge goes to AS3 and that is it. No Java or anything else. But testing wise, I am all here to help.
Is it not possible to port the Plugin from 2.2 to 2.1 or to install HTC Browser?
great it works quite laggy but a great start!
cuddles100 said:
great it works quite laggy but a great start!
Click to expand...
Click to collapse
Glad to hear it.
If you follow the performance tip (written above in red) then it runs as smooth as the original 80's coin arcade classic that it's based on.
http://en.wikipedia.org/wiki/Frogger
Nimche said:
All my knowledge goes to AS3 and that is it. No Java or anything else. But testing wise, I am all here to help.
Click to expand...
Click to collapse
Ahh.. that type of "flash junkie" haha. I thought you meant flashing roms.
Anyway, Air on Android is pure AS3 development, unlike the desktop version which could run Html or Javascript seamlessly...
http://en.wikipedia.org/wiki/Adobe_Integrated_Runtime#JavaScript_frameworks
In fact, coming from Actionscript background, i was impressed enough with it's implementation to switch almost entirely to Javascript coding in the early versions of Adobe Air which were codenamed "Apollo".
So although the desktop version of AIR includes the WebKit HTML rendering engine, this is not supported in Air for Android. (i'm guessing the overhead of running webkit alongside AS3 engine was too heavy for general smartphone use)
However something called "StageWebView" appears to be supported, so i'll look into how that works.
Wolfbreak said:
Is it not possible to port the Plugin from 2.2 to 2.1 or to install HTC Browser?
Click to expand...
Click to collapse
An attempt was made...
http://forum.xda-developers.com/showpost.php?p=6569529&postcount=16
^That whole thread makes excellent reading if you're deep into webkit hacking!
Air for Eclair Source Code
Keeping to the same theme as Code Bummer.. here's a bitmap side-scroller sample by 'theflashbum'...
https://github.com/theflashbum/BitmapScroller/downloads
The size is 9mb cos it includes 29 images. The images are truely funny for any hardcore flash coders, but the side scrolling to way too jumpy to be of any use as is. (...unless you want a migrane as an excuse not to go to work today! lol)
I7redd said:
Glad to hear it.
If you follow the performance tip (written above in red) then it runs as smooth as the original 80's coin arcade classic that it's based on.
Click to expand...
Click to collapse
Didnt read that bit. lol. Yeh the lag pretty much disapears when u do that awesome!
cuddles100 said:
Didnt read that bit. lol. Yeh the lag pretty much disapears when u do that awesome!
Click to expand...
Click to collapse
Thanks for the confirmation. (tip now highlighted)
It does the same on my Nexus running Froyo, so not sure yet what's causing that to happen. We need a few more sample games to see if it happens on Air generally, but for now it's quick fix that works.
I7redd said:
Ahh.. that type of "flash junkie" haha. I thought you meant flashing roms.
Click to expand...
Click to collapse
I did mean both of them. Flash phone and development for AS3. Hope to make something out of this.
Cheers,
Edit> That was nice. OT, how do you pack an apk off flash?
> how do you back an apk off flash?
Not quite sure i understand.
To "back out of flash" means pressing hardware back button. The game suspends, so when you go in again (pressing game icon) it continues where you were, but also plays smoother.
To back up an apk can use normal backup app like Titanium.
I7redd said:
> how do you back an apk off flash?
Not quite sure i understand.
To "back out of flash" means pressing hardware back button. The game suspends, so when you go in again (pressing game icon) it continues where you were, but also plays smoother.
To back up an apk can use normal backup app like Titanium.
Click to expand...
Click to collapse
I fixed it 4 minutes before your post anyways I meant pack an apk. How do you turn air application into android app?
Nimche said:
...development for AS3. Hope to make something out of this.
Click to expand...
Click to collapse
Cool.
These XDA forums have developer sections, thou to me at least, they seems slanted towards rom development, not apps, so I thought i'd start off a topic about testing Air, and see how the response is.
If there are people who are also keen to develop using Air for Eclair, then i'm happy to help get them started, or organize a group project. Will see how it goes.
For myself, i'm using Flash Builder 4, so switching between Froyo or Eclair involves overcopying the respective SDKs in Flash Builder folder..
C:\Program Files\Adobe\Adobe Flash Builder 4\sdks\4.0.A
For Froyo we use latest build [09/30/10] ...but for Eclair we have to use the older SDK dated the same as the Eclair Runtime [06/03/10] that i attached on the first post. I've uploaded (18mb zip) the older "Eclair SDK" for those who want to try compiling something...
http://www.mediafire.com/?m19cetvay9xqx38
Any issues, let me know.
Nimche said:
I fixed it 4 minutes before your post
Click to expand...
Click to collapse
Heh. I didn't reload the page before answering. (also a bit slow typing with a cat on my lap)
Nimche said:
How do you turn air application into android app?
Click to expand...
Click to collapse
After building your SWF file.. use (windows) dos command something like..
adt -package -target apk -storetype pkcs12 -keystore cert.p12 -storepass password my_app.apk my_app.xml my_app.swf
Quick way is to put ^that into a make.bat file.
Then put "adb install -r my_app.apk" into an install.bat file.
Then put "call make.bat & call install.bat" into a run.bat file.
Then double-click run.bat and it's all done in 1 step.
very good stuff! I will glady test stuff for you's
Sent from my X10i using XDA App
I7redd said:
After building your SWF file.. use (windows) dos command something like..
adt -package -target apk -storetype pkcs12 -keystore cert.p12 -storepass password my_app.apk my_app.xml my_app.swf
Quick way is to put ^that into a make.bat file.
Then put "adb install -r my_app.apk" into an install.bat file.
Then put "call make.bat & call install.bat" into a run.bat file.
Then double-click run.bat and it's all done in 1 step.
Click to expand...
Click to collapse
Cool sh*t. I will make some stuff for testing. Happy that AIR works here and I was going to be disappointed but now I have more purpose for using 2.1//
ROM modders/developers!
I'm the developer behind ROM Updater. It's meant to be an universal ROM updater (which means, it doesn't really care if you're on CyanogenMod or you're on the "whitelist"-free of ROM Manager). There is even a PHP script (on the website) which will automatically create incremental updates, cool feature of my app which lets both you and users save a lot of bandwidth. Please consider "adopting" it, it's free ^^
elegos said:
ROM modders/developers!
I'm the developer behind ROM Updater. It's meant to be an universal ROM updater (which means, it doesn't really care if you're on CyanogenMod or you're on the "whitelist"-free of ROM Manager). There is even a PHP script (on the website) which will automatically create incremental updates, cool feature of my app which lets both you and users save a lot of bandwidth. Please consider "adopting" it, it's free ^^
Click to expand...
Click to collapse
Nice work Elegos
Fantastic, consider me a supporter.
I think u have delivered it pretty well
Update: I've released incremental.jar and relative sources. Go to the website and check
New in version 1.8 (from version 1.7):
- Tried to fix a Null exception error, received via Market (thanks for reporting!) (please test)
- Added incremental.php and incremental.jar (plus sources) in the git repository to easily create incremental updates
- Moved common variables in a singleton (SharedData class) and more comments for easier understanding of the code and less variables around
PLEASE NOTE:
You don't have to mess up with the ROM name anymore, the program will check for the ro.build.display.id (MOD name) and ro.build.version.incremental (!!!INTEGER!!! version number), as well as ro.product.model (for future releases, in our case be sure is "Nexus One"). The repository main.json file has a new variable, "model" which is, indeed, the same of ro.product.model. Future versions of the app will make impossible to download updates not for your phone.
DEVELOPERS:
You have no excuses now ! I've talked with some other modders who say, for example, their updates are changing rather all the files, and I say you it's not true. Making some tests I saw that using incremental updates make the update 50~75% smaller, even with MIUI weekly releases. This means "bye bye" to the bandwidth problems, both for hosters and users.
Just added your page as my favorite. Will study and use it later, hehe ,need some time to know about it~~~~
So how do I set up repository for. CM7 nightlies? Do I have to enter it manually?
Sent from my Nexus One using XDA App
I'll give it a go. I have been using ROM Manager and it works very well but I was getting concerned with the bandwidth used for the CM7 nighties.
This does support CM7 nighties right?
Also, what about getting notifications when there is a new build for ClockworkMod Recovery and backup/restore options for ROMs that I keep on my phone?
Wow, as a themer, I would have to say that the idea behind this is amazing. I would love to see it adopted by everyone. I would like to be able to see what exactly has changed between updates, it would save me a lot of time personally. I commend you for your work on this. Woot
@apratomo: you need someone who sets up a CM7 nightly repo. I can't, as it would mean I should support every ROM out there, and my bandwidth is limited (I can host one ROM if you want, not 1000 ). By the way you should edit the build.prop file in order to edit the incremental value and make sure the ROM name is allways the same (display.id).
@pfran42: it supports any ROM you want, this is why I made it
It actually don't check for new recovery images, as it relies on external repositories only, I may create a different application for that though. As of backup/restore, it currently has an option to backup the current ROM wherever you want (see options). When I discover how to restore a nandroid backup via command line, I'll add that feature too.
This is a great idea, however adoption may be slow. Even though its an AWESOME idea, it may be a good idea for you host a popular ROM elegos to get the ball rolling. I'd hate to see this die...
Ok so I have to launch a poll. Problem is that:
1. In the generic Android Development forums (where this really thread should stay) is overcrowed with posts, most of them are just publicity for apps on the market.
2. I'd love to have the attention of all the android people to partecipate to the poll. Of course I MAY create a CM7 nightly repo, but it would mean daily work for me (and a lot of space on my host).
I'm working on a system that should keep a list of repositories automatically updated every time you download a ROM with the app (accepting to send anonymous data). It's ready in the git repository, I'm waiting to push it live 'cause I want to create an interface to grab that data too (a sort of list ordered by phone model).
I think that just for starting I'd love to host a Nexus One Gingerbread AOSP, just like MicroMod777's one (TBH I already have that repo online, but it's frozen at version 20 as MicroMod is focusing on CM 7 custom builds, which I dislike for its too many customizations (both CM itself and MicroMod's)). Alternatively an AOSP 2.3 with no apparent changes (i.e. maybe CM with standard launcher). Any idea?
Sometimes you just have to prove how good your ideas are, because people are lazy... good luck my friend.
Sounds interesting.
I'm going to release a "major" update: all the times a user downloads a ROM and accepted to send anonymous data, the repository, ROM name & version and phone model will be sent to a database, which will return back a list of repositories directly in the settings menu!
I've released version 1.9 and made a Enomther Nexus One repository. Enjoy!
Version 1.9.1
- Fixed an untranslated italian string
- Fixed the import of a repository URL via the repositories list (new line at end of repository)
- Made the application more solid when there are connectivity problems / no internet available (no crash anymore)
awesome work!!
have tagged the link shall go thru it...gr8 job elegos ..!! ..PeacE
Awesome ^-^
Attached is a kernel source patch that fixes the EB13 camera video lag and "Sports" scene mode force-close. It's actually the same kernel bug that's responsible for both.
Also attached is an Odin/redbend-flashable, otherwise stock EB13 kernel with this patch applied. It's intended for anyone who wishes to further test the fix and who is familiar with Odin and/or redbend_ua. For others, I'd recommend waiting until one of the custom kernels integrates the patch or until Sprint releases an official update.
I'll update this post in the morning with a workup of the bug (done, see below), since it's a bit interesting/illustrative. And yes, it's very simple and very silly. One of those things that really never should've happened. Thanks to everyone in the solutions thread for providing clues that were instrumental in locating it.
Bug details:
Shortly after the release of EB13 folks reported lag when recording videos, particularly in low light. Although not obviously related at the time, folks also reported that switching to "Sports" scene mode results in a force-closed (and in my experience, renders the screen inoperable as well, sigh). Folks in the solutions thread also reported that (i) these problems are new to EB13, they weren't present in DK28; and (ii) replacing the user-space camera components (app, libraries, etc.) with DK28 versions did not resolve the problems, implying they were likely due to one or more kernel bugs.
Unfortunately we do not have the DK28 source code to compare EB13 against, but at least knowing that these problems weren't present in DK28 helps narrow down the possible bug locations quite dramatically. Furthermore, it's quite likely that this bug was introduced rather recently, as I imagine it would've been caught by internal testing had it been present in say, December.
So with that in mind, I sorted the kernel source files by modification time and started looking for the most recently-changed files that might be relevant to the camera driver. "include/linux/videodev2_samsung.h" was the first hit with a modification date of 2/8, and indeed it's used by the camera driver ("drivers/media/video/victory/ce147.c", itself last modified on 12/1). Again, we don't have DK28 sources for comparison, but fortunately header files typically don't change too significantly and a comparison (diff) against the DI18 version was rather easy to follow.
And yes, a snippet of code stood out right away as rather strange, especially given the cirumstances of the problem:
Code:
enum v4l2_iso_mode {
ISO_AUTO = 0,
ISO_50,
ISO_100,
ISO_200,
ISO_400,
ISO_800,
ISO_1600,
ISO_FIREWORKS, // Added since DI18.
ISO_SPORTS,
ISO_NIGHT,
ISO_MOVIE,
ISO_MAX,
};
For folks less-familiar with C, this code defines an enumerated type, basically a mapping of "descriptive labels" to numeric values; in this case: ISO_AUTO=0 ISO_50=1, ISO_100=2, etc. This enables kernel code to contain descriptive statements like "iso_mode = ISO_200;" instead of the more arbitrary "iso_mode = 3;".
Now, as the above comment (which I added, but the diff points it out) suggests, ISO_FIREWORKS is a new speed that was added to the middle of the enum since DI18. Seasoned C programmers will recognize that, this is often something that leads to trouble. To understand why, compare the "before" and "after" enum mappings:
Code:
Before: After:
ISO_AUTO: 0 ISO_AUTO: 0
ISO_50: 1 ISO_50: 1
ISO_100: 2 ISO_100: 2
ISO_200: 3 ISO_200: 3
ISO_400: 4 ISO_400: 4
ISO_800: 5 ISO_800: 5
ISO_1600: 6 ISO_1600: 6
ISO_SPORTS: 7 ISO_FIREWORKS: 7
ISO_NIGHT: 8 ISO_SPORTS: 8
ISO_MOVIE: 9 ISO_NIGHT: 9
ISO_MOVIE: 10
The addition of ISO_FIREWORDS to the middle of the enum shifts the mapping of any labels below it, in this case ISO_SPORTS, ISO_NIGHT, and ISO_MOVIE. This isn't fatal, but it does mean that all code that uses the enum needs to be recompiled to reflect the new mapping. Often, kernel header files contain data types that are exclusive to the kernel, so any relevant code gets recompiled as part of the process of compiling a kernel.
But as it turns out, the entries in this enum are used in exactly one location (on the Epic anyways) in the kernel: as a case in a switch statement in the camera driver that sets the ISO mode in a camera hardware register. This means, assuming these values are used at all, they must be provided by a user-space library. In other words, the enum mapping is an integral part of the driver API, and not something that can be altered willy-nilly.
So basically, on EB13 when the Camera app goes to record a movie, it sets mode ISO_MOVIE (9), which the kernel interprets as ISO_NIGHT and sends to the camera hardware. Presumably ISO_NIGHT biases picture quality over shutter speed, hence the blurry laggy video when recording. Similarly, ISO_NIGHT => 8 => ISO_SPORTS (which no one noticed), and ISO_SPORTS => 7 => ISO_FIREWORKS. Except ISO_FIREWORKS isn't implemented, so the driver call fails which results in the force close. Oops!
The fix is fairly simple, just remove ISO_FIREWORKS from the enum. This allows the kernel and the user-space libraries to agree on the mapping. And since ISO_FIREWORKS isn't even implemented in the kernel, no harm can possibly come from it.
Finally, as I stated earlier, this is a bug that never should've happened, for two reasons. First, it was introduced into the Epic kernel source tree after DK28. Now, keep in mind that DK28 was effectively a Froyo "release candidate", especially given that it was packaged up as an OTA update and accidentally pushed to some handsets. Any changes made to the kernel post-DK28 should be limited to strict bug fixes only. The addition of ISO_FIREWORKS to the enum is not part of any bug fix (indeed it introduces one), rather one would consider it a "new feature". But "new features" shouldn't creep into stable code trees. This suggests poor code management.
Second, this alteration would've been a non-issue had ISO_FIREWORKS been appended to the end of the enum, just before ISO_MAX (which, presumably just reports the numer of entries in the enum as opposed to describing a particular mode). This would've assiged ISO_FIREWORKS to an unused value, instead of remapping existing values. Adding ISO_FIREWORKS to the middle of the enum is a particularly short-sighted choice, as it immediately renders any code that uses it unnecessarilly incompatible with new kernels. Adding ISO_FIREWORKS to the end preserves backwards compatibility, for free, with absolutely no downsides--why not do that instead?
So, in short, the failure to properly consider both of these issues, as well as the neglect to notice the change, bespeaks of an incompetent moment on the part of Samsung. If the change really was made on 2/8, one can't really blame Sprint for failing to pick it up during last-minute testing. I'm not sure how much this particular bug was a factor in Sprint pulling the EB13 update, but it's pretty embarassing that it made it out there in the first place.
Mirror links (does not require forum login):
epic_camera_fix-EB13.diff
epic_camera_fix-EB13.tar
epic_stock-EB13.tar (for flashing back to the stock EB13 kernel)
Thank you! This will be in the ACS kernel team's kernel.
Excellent, patching up as we speak.
Sent from my SPH-D700 using XDA App
Just wanted to be 3rd
Sent from my SPH-D700 using Tapatalk
Cool, looks good.
Sent from my SPH-D700 using Tapatalk
patching myself too thx will be in Genocide Kernel 0.3a
THANKS! leave it up to xda to do a better job then Samsung lol
Sent from my SPH-D700 using XDA App
Sweet,
tested working perfect. the LSD trails in video are gone and no FC in sports mode. TY so much.
fix worked great! i just released genocide 0.3a with this patch included! thanks again!
Gotta love 1 line fixes
Would like to try this but only have mac os so odin...
Awesome, thanks man!
Sent from my SPH-D700 using XDA App
Noob question.
Do you put this in PDA? Also no need for PIT or modem file right?
Via TapaTalk on Nook Tablet
-Edit-
Okay, used Odin, put patch in PDA with nothing else set. Worked perfectly! Thanks to all!
You sir a genius....thx for this fix!!!
What is sports mode? I can't find it.
Silent25r said:
What is sports mode? I can't find it.
Click to expand...
Click to collapse
Still camera, settings (gear button)>Scene Mode> Sports Before the fix it's an automatic FC
Can't wait to hear the details behind the bug.
Sent from my SPH-D700 using XDA App
This patched worked perfectly on the genocide kernal!! Thanks For Your Hard Work!!
Now Just Waiting For Bonsai!!
The geniuses at XDA strike again! Brilliant! Thanks!
MoCoTerp said:
Noob question.
Do you put this in PDA? Also no need for PIT or modem file right?
Via TapaTalk on Nook Tablet
Click to expand...
Click to collapse
Help please? I've flashed lots of roms but never a kernal like this. i'd like to stay with the stock ROM. Can't find anything on a search. Can someone either post a link or instructions.
AGPS Patch Sensation 3.1 & 2.2 | GET BACK TO RAPID GPS LOCK, CAN LOCK ONTO MORE SATS
AGPS PATCH
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
List of officially supported devices is at the bottom of this post.
Use this if you're having GPS issues (unreliability, no functionality, etc.)
This patch provides a worldwide solution to GPS issue for multiple devices. Using a general ROM without this has resulted in 10+ minutes of GPS delay. Also, GPS lock kept being lost. By using this patch, most people experience a GPS lock within 10 seconds (2 - 20 seconds range can be expected). Typically, a device using this patch will lock onto 7 - 9 satellites. Users have reported up to 11 satellites being locked at once. Without this patch, the average satellite count is 4.
HOWTO INSTALL: (Remember to make a backup. See Notes section for what this patch does.)
Method 1:
1. Download the "ADB Push Installer". This contains all versions for the latest build and old v1.3 versions.
2. Extract the files into a specific folder.
3. Plug your device into the computer and get it ready for adb pushing. Nothing out of the ordinary required.
4. Open the batch file called "ADB Installation Script - RUN THIS" if you use Windows. Otherwise, run the Linux SH script if you use Linux.
5. Select the version you want from the list.
6. Follow the prompts to reboot. You're done.
4. Review the NOTES section.
Method 2:
1. Download the patch
2. Copy all file(s)* into /etc/ of the system (not sd-card) using ES File Explorer, Root Explorer, or some other form. You must have SYSTEM set to Mounted and Root enabled. Check your explorer app's SETTINGS to do this.
**Files will be: gps.conf & SUPLROOTCERT -OR- only gps.conf for NO-SSL builds.**
3. Reboot the device
4. Review the NOTES section.
*Files are located in the /system/ folder of the ZIP. Do not copy the other directories or folders.
Method 3 (easiest if you use a compatible version of CWR or CWM)*:
1. Download the patch
2. Boot into CWR (Clockwork Recovery)
3. Mount /system/ partition (on the main menu, select the "Mounts and storage" option, then "mount /system")
4. Flash the patch (on the main menu, select "Install zip from sdcard," then "choose zip from sdcard," and find the zip and select it)
If you receive "(Status 0) Installation aborted" this Method will not work for you. Use one of the other methods.
5. Reboot the device
6. Review the NOTES section.
*This was built for and works on Inspire 4G and DesireHD versions of Clockwork Recovery. The Google CWM Flashable Build has binaries known to work with CWM on the X8. It may work on other devices. Please message me your success if you try and flash with recovery version and phone model as part of the message.
Downloads:
SEE THE NOTES SECTION (PARTICULARLY NOTES 1,2, & 3) FOR ALL SORTS OF INFORMATION AND FACTS ABOUT THIS PATCH, WHAT EACH BUILD IS FOR, VERSION DIFFERENCES, AND KNOWN ISSUES WITH SOLUTIONS.
Recommended Builds (pick either):
Download the Google Specific No-SSL v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific v3.1 build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Confused with all the options below? As the Notes section dictates: I recommend the GOOGLE BUILD of all devices. Other builds have changes in their SUPL server information and/or other variables pertinent to that manufacturer. These builds do not appear to operate as fast as Google build's but are available for your enjoyment.
3.x trunk Alternative Options (currently v3.1)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL TWRP build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
2.x trunk Alternative Options (currently v2.2)
Download the ADB Push Installer here. (contains all current builds and v1.3 builds) (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific NO-SSL build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Google Specific CWM Flashable build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the AT&T Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the T-Mobile Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the LG Phone Specific Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the Sony Ericsson Specific build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
Download the GPS.CONF only Alternate* build here. (Like it? Don't forget to click on "Thanks" and to rate the thread)
*The alternate patch removes a variable that some GPS hardware on older models cannot handle. Try this if you have problems with the standard patch.
Changelog: (I'll try to keep this correct and current)
Code:
v3.1 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v3.1(HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
introduced my own NTP pools
repaired the LG Alternate build (was same as standard build, compilation error)
v3.0 (HELP WITH THE MAINTANENCE COSTS - DONATE A FEW BUCKS)
based on v2.2 configuration
has my own XTRA/AGPS server instead of Qualcomm
re-added two AGPS variables from v1.3 (two beta-testers saw instant results with these re-added)
re-added on USE SUPL variable from v1.3 (two beta-testers saw instant results with these re-added)
variables are now divided into sections and sections have descriptions
Code:
v2.2 update - New Version
introduced the NO SSL version for Google build. Shows faster performance times.
v2.2 (additional builds added)
added a new SUPL version using data from Sony Ericsson
added an alternate release using LG SUPL servers
added an alternate release using Google SUPL servers
updated the ADB PUSH to include new versions
fixed broken download links for the patch
v2.2
removed local AGPS variable
removed local XTRA_SERVER variable
created LG Build with LG SUPL servers (some LG ROMs fail to work with non-LG SUPL servers)
reduced redundancy in NTP and XTRA (unnecessary entries)
added newly located SUPL server to T-Mobile build
v2.1 (encompassing changes between 1.3 to 2.1)
removed two NTP server pools
removed xtra1 server
removed multiple SUPL_HOST entries
aligned SUPL_HOST with SUPLROOTCERT in each package
increased QOS timeout from 89 to 100
removed QOS standalone timeout variable
removed extra AGPS variables
Old Versions:
3.x Trunk:
v3.0 ADB Push Installer
v3.0 Google Build
v3.0 Google Alternate Build
v3.0 Google CWM Build
v3.0 AT&T Build
v3.0 T-Mobile Build
v3.0 LG Build
v3.0 LG Alternate Build
v3.0 Sony Ericsson Build
v3.0 GPS Only Build
v3.0 GPS Only Alternate Build
2.x Trunk:
v2.1 Google Generic Build
v2.1 AT&T Specific Build
v2.1 T-Mobile Specific Build
v2.1 GPS.Conf Only Build
v2.1 GPS.Conf Only Build (alternate)
v2.0 Google Generic Build
v2.0 AT&T Specific Build
v2.0 T-Mobile Specific Build
v2.0 GPS.Conf Only Build
v2.0 GPS.Conf Only Build (alternate)
1.x Trunk:
Worldwide 1.3
Worldwide 1.3n (alternate)
North America 1.2
Worldwide 1.2
Worldwide 1.2n (alternate)
North America 1.1
Worldwide 1.1
Worldwide 1.0 (not recommended)
North America 1.0 (not recommended)
Rules For Posting Questions:
Read the Notes Section first. I will refuse to answer questions that can be answered by some reading. If it is based upon something in the Notes Section, REFER TO THE NOTE when asking.
Answer the following questions: What ROM you are using?, What kernel are you using?, What GPS apps you have installed?, Where is your general location?, Are you using a case?, Has your GPS worked fine before?, Does it work fine with some apps and not others?, What else happened around the time your GPS stopped working? -AND- Have you reviewed the Notes Section?
DO NOT criticize the user of custom third-party NTP pools and xtra.bin data as dangerous. You obviously HAVE NOT read the Notes section OR reviewed the concurrent branch 2.x to discover it offers the standard NTP pool and Qualcomm-based xtra.bin server.
Don't indulge yourself in ignornat posts. Provide information that may be relevant to helping. Simply stating "this stopped working" or "I can't get it to work" helps nothing and only annoys other readers AND those who may be willing to help you just will not do it.
NOTES Section:
This patch will work with virtually all Qualcomm, Android phones and has been reported to work with other chipsets as well. That means hundreds of devices could see a benefit to GPS performance from this patch.
This patch has various objectives to ensure stability and efficacy with GPS. Locally, the patch will replace your /system/etc/gps.conf and your /system/etc/suplrootcert if you have this file. You can compare the difference in what you have to this one to get an idea of all the changes. V3.1, onward, contains section descriptions for variables in use. Most notably, starting with v3.1 the aGPS Patch uses my own central NTP DNS pool and my own central xtra.bin server by default. The xtra.bin does have fallback servers should mine fail. But, that is very, VERY much an unlikely scenario. These two imperatives allow for better stability and speed by providing top-rated NTP servers and prime-routed network access to transmit the xtra.bin to your phone.
I recommend the GOOGLE BUILD of all trunks. However, you can use any build with any phone. You may have good luck with specific builds that do not fit your phone or carrier criteria. If you're curious, test it and see.
This works with ANY ROM unless the ROM has aGPS and/or GPS disabled in the code. This happens with CMx nightlies and some betas! I cannot fix this, neither can you.
Remember, this has to be reflashed when you update or change ROMs.
Short patch history: The 1.x trunk only flashed a modified gps.conf file which relied solely on Qualcomm and NTP.ORG. Starting with 2.x, a gps.conf and a matching SUPLROOTCERT file for SUPL server authentication is included. The 3.x trunk offers the same as v2.x but adds better sourcing for NTP data and for the xtra.bin file; it utilizes my own server to do so.
Why toss out SSL?Whether or not you have a current SUPL certificate is questionable. Some have expired. Some will expire soon. Either way, the servers may provide SSL access without proper certificates depending upon configuration. That aside, I have found that SSL and secure communications over data networks slows the response times. I see no reason to use SSL for location information. If someone has a logger to obtain your location, SSL will not assist in stopping it. The bad app will continue to obtain your information by "stealing" it and you have more problems than a simple SSL-SUPL communications leak.
NO-SSL Builds will not have a SUPLROOTCERT because these builds do not use SSL. The SUPLROOTCERT is a certificate used for authentication of SSL connections. There is no need for this file for the GPS at this point.
IF you have issues with v2.x or v3.x, your ROM might require more variables. Try the old worldwide v1.3 version in this instance.
IF you still are facing issues, it might be that your GPS hardware is very much outdated. Try any "Alternate" build to see if this helps.
CMx ROM users may not experience benefits from this patch. However, we have had good reports from CM users with one negative one. Remember to do all of the steps when flashing and the following notes are important too!
Reports indicate that this patch DOES WORK with the next iteration of Android, Jelly Bean. This patch has worked from Android 2.2 (Froyo) up through Android 4.1 (Jelly Bean). Therefore, it works with all iterations on the market. I will remove support as soon as it is confirmed to NOT work with a new version of Android.
Reports show that certain ROM's including some CM builds require a modification in the build.prop. You need to change "ro.ril.def.agps.mode = 2" or "ro.ril.def.agps.mode = 0" to be "ro.ril.def.agps.mode = 1" in order for aGPS to properly function. Only do this IF YOU ARE HAVING PROBLEMS after attempting the standard patch.
Your phone "learns" about the individual GPS satellites. This is part of the aGPS design. Don't be surprised if the first time you use GPS Status that it takes 20+ seconds to "lock".
I have read a lot that indicates that it is best to let your GPS run using any application for a while to "learn" aGPS information. I let GPS Status run for about 10 minutes (it has an option to disable the screen timeout, which I do) each "first time" to learn. I say each because I test a lot of tweaks and fully reset/delete GPS cached information to start retesting.
Remember, this has to be reflashed when you update or change ROMs. Each ROM will have its own gps.conf, normally not suited to all devices.
I use GPS Status to test my signal strength. It isn't 100% accurate, but it gives a very good sense of how the GPS is performing.
If you're wondering why GPS is slow on certain apps? Or, you show up as on a street when you're 6 meters away from it? Well, those apps process GPS data differently which is out of anyone's control except the app developer. Certain apps will force your location to a street until you pass the app error threshold. Food for thought.
DO NOT USE ANY OTHER GPS FIXING APPS with this patch. If you do, and you still have problems, I cannot help you. A number of these Apps will overwrite what my patch does dynamically.
Variables are described starting in v3.0. Open up gps.conf in a text editor to read about what variable sections are for. It isn't in-depth, but should be enough to help you get a general understanding.
Still having weak GPS reception? Take your case off. Cases have been known to affect signal, though some argue against it. Personally, I get 3 more sat's when I remove my case.
There is a reported variable that can cause some GPS units not to work as well as it should with this patch. This is very odd as it's hit-and-miss and only seems to cause problems on less than 10% of handsets. This doesn't mean it screws up anything! It's possibly an older piece of GPS hardware incompatible with this variable. Have no fear, v1.2 will remove this variable for the worldwide version. This issue is more prone to occur in DHD.
Tried taking the battery out for 30 seconds? Some have reported that their phone required the battery to be removed. First, power off the device. Second, remove the battery for 30 seconds. Third, put it back in and give it a try. I cannot explain this except for possible cache clearing.
Some Inspire 4G and DHD devices have hardware problems. There is a known problem that the spring connectors to the GPS antenna sometimes are out of place or quit touching. http://forum.xda-developers.com/showthread.php?t=1101066 provides a video on self-repair.
An error in flashing this patch means that this method will not work for you. Use one of the other methods for flashing this patch. Don't ask why or for a fix. There are hundreds of variations of recovery systems and update binaries. I do not have the time or desire to support them all. This is why I describe other install methods. Reference error: E:Error in /sdcard/android apps/agps.patch.google.build.nossl.v3.1.zip (Status 0) Installation aborted.
Location is way off? Like, not near you at all? This means your GPS is not actually being used. Try the following to resolve it: Goto Settings -> Locations and disable ALL options. Reboot into recovery. Clear Cache and Dalvik Cache. Reboot normally. Go back to Settings -> Locations and only enable GPS. Reboot once more and try your GPS again. If this didn't work, did you read all of the Notes such as the one about the battery or RIL?
Donations: If you wonder why I asked for donations, it's simple. Users of v3.x are gaining extra, noticeable benefit over v2.x. This comes at a cost to someone. I pay the bills to provide a reliable data setup to transmit the xtra.bin data file and to provide the top NTP SERVERS in one DNS pool. To help keep this going, I just ask for the user to consider a donation. Nothing more, nothing less. Thank you for your consideration.
AGPS Patch Officially Supported Devices:
Acer Iconia
Asus Transformer Prime
Asus Transformer (TF101)
Asus Transformer TF300T
HTC Inspire 4G
HTC Desire HD
HTC Sensation
HTC Incredible S
HTC Salsa
HTC Flyer
HTC Evo 3D
HTC Desire S
HTC Wildfire
HTC Wildfire S
HTC Droid Incredible 2
HTC Thunderbolt
HTC Desire
HTC Desire Z
HTC One X
LG GT-540 OPTIMUS
LG Optimus One
Motorola Triumph
Motorola Droid X2
Samsung Galaxy S II Skyrocket (SGH-I727)
Samsung Galaxy S II (I9100)
Samsung Galaxy S II (SGH-T989)
Samsung Galaxy S Plus I9000
Samsung Galaxy Nexus
Samssung Galaxy S III (AT&T, Rogers, Bell, Telus)
Samsung Galaxy S III I9300, I9305
Samsung Galaxy S 4G
Sony Ericcson XPERIA X8
* I do not officially support all devices that this patch is known to work on at this time. You may private message me your success story for official support considerations.
Thanks Section
While this has gone a long distance since its inception, I want to still send thanks to Angeldeath for permitting me to take his early work and start tweaking it for HTC Inspire 4G users. This inevitably led to what we have here today.
Thank you to all those who joined and participate in the testing community. Without their help, I couldn't get enough data to know how well this works on different devices and in various regions of this planet we call Earth.
Thank you eagleeyetom, husky69, and tamagotono for their work in building an ADB pushing environment for Windows and for Linux respectively.
If you are happy with the patch and find this thread useful, please consider pressing the "Thanks" button on any of my posts on this thread. You may also consider rating this thread with five stars if you're satisfied. You may do so just below "Search This Thread" on the right-side at the top of this post. Donations are appreciated (See last NOTE)
REVIEW THE WHOLE THREAD BEFORE POSTING QUESTIONS.
Holding this post open. I consolidated this into the top post to make it easier to update across all threads.
Is there a patch for ASIA?
Oh sorry if you need this space in reserve....Please delete mod
rockmaster said:
Is there a patch for ASIA?
Oh sorry if you need this space in reserve....Please delete mod
Click to expand...
Click to collapse
It will be worldwide. If you want to test the v1.3, send me a private message and I'll give you a link.
Awesome, looking forward to this!
Chris19145 said:
Awesome, looking forward to this!
Click to expand...
Click to collapse
If you want to test it, send me a private message.
I think I solved the problem with flashing ZIP files via CWR. Otherwise, it will require abd push or root explorer.
Im running cm7 alpha with a good 10+ minutes to lock on GPS. I'll give the patch a shot and report back the results. link me. ( please)
Wow definitely can not wait for this..my gps takes forever and/or doesn't connect nd always gets lost..hope this is the light at the end of the tunnel
Sent from my HTC Sensation Z710e using XDA App
sheetmetalninja said:
Im running cm7 alpha with a good 10+ minutes to lock on GPS. I'll give the patch a shot and report back the results. link me. ( please)
Click to expand...
Click to collapse
Ahh, I was wonder why anyone would need this, its not a Galaxy S
With a Sense based rom I get 5-9 bird locks in about 5-10 seconds. Highest I've seen is 10 satellites.
tissimo said:
Ahh, I was wonder why anyone would need this, its not a Galaxy S
With a Sense based rom I get 5-9 bird locks in about 5-10 seconds. Highest I've seen is 10 satellites.
Click to expand...
Click to collapse
I really don't get your point.
---------- Post added at 11:29 PM ---------- Previous post was at 11:27 PM ----------
For those interested, you could use v1.2 for either Inspire/Desire. It ought to work just fine.
I'll have v1.3 out by the middle of next week.
This looks good! No ROM I've tried works nearly as well with GPS as stock did for me. Hopefully this does the trick. When should the Sensation version arrive?
Well ... I've been playing with the file and created my own..
My theory ... less is more.
I have posted the files and you can try for yourself.
http://www.arvida1.com
Credit to crypted for original modded file.
steve841 said:
Well ... I've been playing with the file and created my own..
My theory ... less is more.
I have posted the files and you can try for yourself.
http://www.arvida1.com
Credit to crypted for original modded file.
Click to expand...
Click to collapse
Hijacking threads ain't cool. And as I told you on another thread, less isn't always more. There are a lot of factors including physical hardware (GPS unit on the phone), software (kernel: modded vs stock), and drivers. And, I gave you access to my upcoming release to test it. Not to build something for you to post on my thread before I even had a chance to release it.... Testers are requested for testing.
Each var has a purpose. It's a matter of will that purpose be supported from what I said above. Yes, dropping a bunch of them can work just fine for one schema. But, contextually it might not be so great for many other flavors of flashing.
I have a standard release schedule. v1.3 comes out next week. Sensation will be kicked up for official support at that time.
crypted said:
Hijacking threads ain't cool.
Click to expand...
Click to collapse
Don't hate...
Just trying to help everyone.
Wow steve,
I agree with helping everyone, but you should have kept your own edits to yourself and should have stated if anyone wanted to test your version out they should PM you and not to detract this thread.
Moving on now...let's just get this patch going from the OP, he was nice enough to let us test his script.
---------- Post added at 10:44 AM ---------- Previous post was at 10:42 AM ----------
Bsketball said:
This looks good! No ROM I've tried works nearly as well with GPS as stock did for me. Hopefully this does the trick. When should the Sensation version arrive?
Click to expand...
Click to collapse
Just extract the 1.2 file from post 2-depending where you are, of course. Push the gps.conf file to your phone which is /system/etc.
kpjimmy said:
Wow steve,
I agree with helping everyone, but you should have kept your own edits to yourself and should have stated if anyone wanted to test your version out they should PM you and not to detract this thread.
Click to expand...
Click to collapse
I must really be on another planet ... I just edit a file from the OP and give to everyone to try (after I made sure it worked for me) ... and I get flamed for it.
Im not asking for donations, fame or "thanks".. just a working GPS.
Crypted ... pm me and I will remove all my posts and create a new thread if that makes everyone happy.
No worries. I will release it as planned. Just realize I have put over 50 hours of time into this project. Many ROM devs and APP devs have requested and have been granted permission to use this in their stuff. Just let me know what you want to do with it and talk to me via private message. No one expects to wake up and see someone using their work unexpectedly and posting it on XDA.
And remember: everything was done for a reason and will go through a major revision on V1.4.
V1.2 WILL work on Sensation as mentioned above. You can find it in Note #2. However, you MIGHT have problems flashing it with CWR. If you do, copy the file using root explorer or abd push.
V1.3 will provide CWR support for sure. I revised the update script to use more universal procedures that are compatible across many devices. It will bring some important NTP and XTRA updates. It removes one variable.
V1.4 will be a major revision.
V1.5 will have a great surprise for people. ROM dev's are excited about this one.
Would like to try it when it comes out. My problem is that my GPS locks, but my location is wrong, say off by about 1000 meters or so. It'll show be down the street from the location, maybe it's a hardware problem. But navigation works great, I used it in California few weeks ago, went from Hollywood to Santa Monica and no problems. It's just the actual location in maps itself doesn't show exactly where I am.
quierotacobell said:
Would like to try it when it comes out. My problem is that my GPS locks, but my location is wrong, say off by about 1000 meters or so. It'll show be down the street from the location, maybe it's a hardware problem. But navigation works great, I used it in California few weeks ago, went from Hollywood to Santa Monica and no problems. It's just the actual location in maps itself doesn't show exactly where I am.
Click to expand...
Click to collapse
Yes, that sounds like it is not using your GPS at all. Typically, Maps and other apps will show you in a generic location based upon the tower(s) your phone is using for data transmission. It's a backup general location method when GPS isn't catching a signal.
quierotacobell said:
Would like to try it when it comes out. My problem is that my GPS locks, but my location is wrong, say off by about 1000 meters or so. It'll show be down the street from the location, maybe it's a hardware problem. But navigation works great, I used it in California few weeks ago, went from Hollywood to Santa Monica and no problems. It's just the actual location in maps itself doesn't show exactly where I am.
Click to expand...
Click to collapse
Are you in Long Island, NY? I grew up in Huntington worked in Melville for a number of years.
Back to this thread...have you tried the 1.2 file yet? Don't flash it, extract the file and get the gps.conf out and push the file onto your device. Or you can use root explorer to overwrite the file. But remember to have a gps.conf backup to revert to if you run into any problems.
Mods please move this post if in the wrong place. OK, I couldn't find it ANYWHERE on XDA but, I did find it by doing extensive baidu (China's Equivalent of Google Search engine) searches and translations. So I give to you all QPST 2.7 build 402. I have the newest and latest QXDM and QCAT also. They were uploaded to the Chinese site on February 13, 2013. QXDM requires activation so I wont post it. I will post QCAT if anyone requests it though, as it does not require activation and neither does this version of QPST. I have seen numerous posts over the net where people wanted QPST 2.7 build 385 but this one surpasses that version. Annoyingly enough though, I still cant write settings to my girlfriends LGL55CV3 Straight Talk android phone with it . So if anyone here can help me out on this, please feel free to do so. So enjoy and hit thanks if I've helped you out.:good: http://www.mediafire.com/?yya85byog8kqtxn
:good:
solcam said:
Mods please move this post if in the wrong place. OK, I couldn't find it ANYWHERE on XDA but, I did find it by doing extensive baidu (China's Equivalent of Google Search engine) searches and translations. So I give to you all QPST 2.7 build 402. I have the newest and latest QXDM and QCAT also. They were uploaded to the Chinese site on February 13, 2013. QXDM requires activation so I wont post it. I will post QCAT if anyone requests it though, as it does not require activation and neither does this version of QPST. I have seen numerous posts over the net where people wanted QPST 2.7 build 385 but this one surpasses that version. Annoyingly enough though, I still cant write settings to my girlfriends LGL55CV3 Straight Talk android phone with it . So if anyone here can help me out on this, please feel free to do so. So enjoy and hit thanks if I've helped you out.:good: http://www.mediafire.com/?yya85byog8kqtxn
Click to expand...
Click to collapse
---------- Post added at 04:36 PM ---------- Previous post was at 03:44 PM ----------
:good:
solcam said:
Mods please move this post if in the wrong place. OK, I couldn't find it ANYWHERE on XDA but, I did find it by doing extensive baidu (China's Equivalent of Google Search engine) searches and translations. So I give to you all QPST 2.7 build 402. I have the newest and latest QXDM and QCAT also. They were uploaded to the Chinese site on February 13, 2013. QXDM requires activation so I wont post it. I will post QCAT if anyone requests it though, as it does not require activation and neither does this version of QPST. I have seen numerous posts over the net where people wanted QPST 2.7 build 385 but this one surpasses that version. Annoyingly enough though, I still cant write settings to my girlfriends LGL55CV3 Straight Talk android phone with it . So if anyone here can help me out on this, please feel free to do so. So enjoy and hit thanks if I've helped you out.:good: http://www.mediafire.com/?yya85byog8kqtxn
Click to expand...
Click to collapse
Ummmm...Yeah. If you say so.
solcam said:
Ummmm...Yeah. If you say so.
Click to expand...
Click to collapse
Anyone managed to download this?
No. It says that it belongs to an unvalidated account. I know that 418 is now out too if anyone might have this one.
cezar1 said:
This file infected by troyan. Thanks a lot
Click to expand...
Click to collapse
I had no issues with it... and still use it. I will look into it. I did not upload it, I just posted the link.
---------- Post added at 10:56 PM ---------- Previous post was at 10:32 PM ----------
cezar1 said:
This file infected by troyan. Thanks a lot
Click to expand...
Click to collapse
I did some checking and a few people DID have issues with this. Thank you for bringing it to my attention...
If you install this via "setup.exe" it will put a backdoor on your system. It lives at "C:\Users\Admin\AppData\Roaming\Qualcomm". It will also add itself to the "HKCU/Software/Microsoft/Windows/Current Version/Run" key in the registry. There is no virus in the MSI file.
You should be able to detect it, remove it and use build 422. Again, I am using it without issue.
rekamyenom said:
I had no issues with it... and still use it. I will look into it. I did not upload it, I just posted the link.
Click to expand...
Click to collapse
Hello, fellow QPST users.
QPST 2.7 Build 4.2.2 is a fake version with keylogger.
Some a$$hole downloaded latest public QPST build (4.0.2) and decompiled MSI installer package, then edited all "4.0.2" to "4.2.2", added "fake changelog", added keylogger (qualcomm.exe), then repackaged and spread around web!
Everyone who downloaded QPST build "4.2.2" should change all his passwords.
More info about malware from fake 4.2.2 build (QPST.2.7.422.msi)
MSI package (QPST.2.7.422.msi) was embedded/tampered with qualcomm.exe which is a .NET based malware that logs your keystrokes and sends it to attacker's server.
How to delete the actual malware from your system?
Look at the startup from msconfig or CCleaner, there should be a file called qualcomm.exe thats set to start everytime system starts. Delete both registry and file.
If you wanted to see what data thief was stolen from you. Just open the .dc file (in "dclogs" folder) with Notepad and see for yourself.
In XP, dc file is located here!
C:\Documents and Settings\Administrator\Application Data\dclogs
there should be a file called "201X-XX-XX-X.dc
if you open that DC files with Notepad, you'll see all your keystrokes.
Here is mine. I've intentionally entered paypal site with fake info.
:: Run (3:01:51 AM)
Script kiddie. NET Based malware, huh?[ESC]
:: Program Manager (3:02:14 AM)
e
:: Firefox (3:02:18 AM)
www.paypal.com
[email protected][TAB]
mypaypalpass
[ENTER]
:: Documents and Settings (3:02:19 AM)
[UP]
:: Administrator (3:02:28 AM)
[DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN]
[DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN][DOWN]
d
:: (3:02:34 AM)
:: Administrator (3:02:34 AM)
d
:: (3:03:11 AM)
mmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmmm
:: [Release] QPST 2.7 BUILD 422 - Download Here - Enjoy - Mozilla Firefox (3:03:57 AM)
crap
How to delete?d
:: Clipboard Change : size = 16 Bytes (3:03:57 AM)
QPST.2.7.422.msi
:: (3:04:23 AM)
cccccc
Click to expand...
Click to collapse
Keylogger sends the logs from keylogger to "qpst.hopto.me"
So please report about this incident where and when you encounter QPST 4.2.2 somewhere (forums, posts, sharing-sites, etc)
Copy my whole post and paste it where you see 4.2.2 mentioned.
Bonus: Fake Changelog
If you've installed this 422 build, then open the Readme.txt in C:\Program Files\Qualcomm\QPST\Documents
Scroll down and see the "6/12/13 QPST 2.7.422 changelog"
6/12/13 QPST 2.7.422
1) EFS Hello commands will not be sent unless the device is in a compatible mode. Sending this command when the
device is in download mode can cause a "server busy" message for a few seconds because of command retries.
2) Support for the Sahara device protocol (see 80-N1008-1 or equivalent) is now built in to the QPST server process.
This protocol is only supported by USB Serial ports, not TCP/IP connections. In QPST Configuration a device in
this mode will display as "Q/QCP-XXX (Sahara Download)". This mode can only be detected (1) when the QPST server
process starts or a COM port in this mode added to QPST, or (2) when a device enters Sahara mode on a port assigned
to QPST. This is because the device only sends its Hello message once, as soon as the COM port is opened.
Click to expand...
Click to collapse
Changelog above is actually cloned from QPST 2.7.394 Just scroll down and see Build 2.7.394 changelog. Its same!
So forget about Build 422. It doesn't exist.
Use QPST 2.7 Build 402. It's the latest public build
Sorry about my english
Best Regards
AnycallMongolia
can somebody give proper qpst latest version.
pl provide dropbox link
madroamer said:
can somebody give proper qpst latest version.
pl provide dropbox link
Click to expand...
Click to collapse
Okey, someone (HuaweiDevices.ru) leaked QPST v2.7.411 to the public. I've installed it myself and confirmed that its legit build.
Here is original link of the leak..
Here is my link.
http://d-h.st/qAy
Thread cleaned, potentially unsafe file and posts are gone. All members are to be reminded that whenever you flash anything, regardless of what it is, you take chances.
Thanks for the report, and thanks for not being disrespectful regarding the matter.
Now, back to development.
Thanks for your sharing this.
solcam said:
Mods please move this post if in the wrong place. OK, I couldn't find it ANYWHERE on XDA but, I did find it by doing extensive baidu (China's Equivalent of Google Search engine) searches and translations. So I give to you all QPST 2.7 build 402. I have the newest and latest QXDM and QCAT also. They were uploaded to the Chinese site on February 13, 2013. QXDM requires activation so I wont post it. I will post QCAT if anyone requests it though, as it does not require activation and neither does this version of QPST. I have seen numerous posts over the net where people wanted QPST 2.7 build 385 but this one surpasses that version. Annoyingly enough though, I still cant write settings to my girlfriends LGL55CV3 Straight Talk android phone with it . So if anyone here can help me out on this, please feel free to do so. So enjoy and hit thanks if I've helped you out.:good: http://www.mediafire.com/?yya85byog8kqtxn
Click to expand...
Click to collapse
anycallmongolia said:
Okey, someone (HuaweiDevices.ru) leaked QPST v2.7.411 to the public. I've installed it myself and confirmed that its legit build.
Here is original link of the leak..
Here is my link.
http://d-h.st/qAy
Click to expand...
Click to collapse
Link works. Thank you.
Hello guys, i have a LG G2 with 3g issue , it works just in 2g, somebody can upload his QCN file so i try to replace mine with it? Thank you so much
!!!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!
!!! TROJAN AGAIN !!!
Some time ago in Feb 2014 man named anycallmongolia posted a link to QPST 2.7 build 411
Link points to the site HuaweiDevices.ru
h_t_t_p_://_huaweidevices._ru/ROMS/QPST_2.7.411.rar
Later I'd personally downloaded this version from this topic a few times in 2014 and this was normal non fake QPST which i'd installed on a few PC's. (Can't remember particular link now). Today I would like to install QPST to a new NB PC, so assumed this topic as the best source. Being a recovery/data structures expert I always inspect code (mostly by viewing in text/hex). As most of members I've very high trust level to xda (certainly it's much higher then one related to the "famous and respectable" corps like Google/MS/Apple/etc, who aren't on my side, I'm sure).
I've installed QPST got from this topic a few times, so I'd almost pressed Enter (I use FAR most of time and advice you to do the same) over the DL'd file "qpst 2 7 411.exe".... What??? - EXE??? And it's just about 500Kb long... But QPST installer occupies about 16Mb.
I've explored body - I's typical malware with slightly "encoded" (to prevent direct reading) data inside. QXDM offered on the neighbor page is the same malware of the same size.
If you'll try to dl QPST from above link you'll got 404 error in the center of normal html page with site menu etc... What normal man would think in this case? He'll think page/product have moved (e.g. due to overload protection) and what he'll do next? He'll try to find where page have moved and... will got link in menu just at the bottom of 404 page. It's just trivial (but very good working!) "social engineering" - publish real app in trusted place and when it will pass checks replace it with malware. (Or may be domain was sold to the criminals as it often occures in Russia for a few latest years). Even if you will check DL url in the status bar it will show link to the .RAR archive, but ASAY click the link it will be redirected to .exe!
PLEASE PUBLISH BIG WARNING on TOPIC START and remove links to HUAWEIDEVICES.RU!!!
Furthermore. Situation is much worse because huaweidevices shows 1ST position in search request "QPST 2.7.411" by Yandex.ru (#1 search engine in Russia) and 2ND position in Google results with the same request!!! It's VERY DANGEROUS situation! Thousands if not millions of peoples are at risk of infection.
I'm going to write abuses to Google and Yandex NOW!
Please spread info on such a new attack manner/technique around your friends, collegues and internet.!
Always check what you run!!!
QPST 2.7 build 425 (The REAL Thing!)
It is so irritating to see all of the jerks who are trying to spread viruses and malware nowadays.
Here is the REAL build 425:
http://www.mediafire.com/download/neeapht51ub2333/QPST.WIN.2.7_Installer-00425.1.zip
drkcobra said:
It is so irritating to see all of the jerks who are trying to spread viruses and malware nowadays.
Here is the REAL build 425:
h_t_t_p_://_w_w_w.mediafire.com/download/neeapht51ub2333/QPST.WIN.2.7_Installer-00425.1.zip
Click to expand...
Click to collapse
Very very very BIG Thank you!!!
That's really new one and it contains new very promising QFIL util. Didn't explored much yet!
God bless on you man!
BTW does anybody know how to descramble (decrypt)/scramble (encrypt) back EFS/NVRAM partitions (in most cases modemst*). I'd like to be able to patch/change every byte in EFS (not just locks etc bull****, my phones are always free of any contracts). Full modem FW reversing seems too difficult to me (i'm 'not so strong' in ARM assembly and there is too much code in modem FW). I'm sure for a such long period (over decade) of EFS life there should be methods around to manipulate it independently of mfr/commercial products, but I can't find them for a long time. Trust me, it's fully idiotic situation I'm (you're) not able to do with my (yours) computer (PDA is computer, not the "phone") all I want to do being "restricted" to access only data some f...n mfr "allowed" me to access. It's my device, I'd paid for it and I will decide what me to do with it.
Furthermore, modern public licenses don't allow to hide parts of object (device) code, where GNU/GPL code is the main part. Is anybody here who think that Linux/Unix value in ALL there f...n "modern" Android devices less than 90%? Most router mfrs have already forced by requirements GNU/GPL to publish full compilable code of their firmware. I shouldn't have clue what all they want to hide related to their "commercial" and manipulating interests. Using 30years of thousands people's free labor in their commercial products , they're obligated to publish full sources and should DO IT.
Apple is today wealthiest corp on this planet, but If you'll look into the Apple's internals you'll find tons of MODERN Linux code (protected by modern GNU/GPL) simply stolen from open source depositories, then adopted to MacOS/iOS then closed and sold as commercial product . Is it fair game?
TheDrive said:
Very very very BIG Thank you!!!
That's really new one and it contains new very promising QFIL util. Didn't explored much yet!
God bless on you man!
BTW does anybody know how to descramble (decrypt)/scramble (encrypt) back EFS/NVRAM partitions (in most cases modemst*). I'd like to be able to patch/change every byte in EFS (not just locks etc ...................
Click to expand...
Click to collapse
I use EFS Pro for BackUp and Restore.... Sadly its windows only, but works great with VirtualBox on Linux Mint Cinnamon/MATE 17.1 x64.
Hosted on the wonderful XDA:
http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546
FWIW
I hear you about Apple, used to be a hardcore fan, when they were nearly bankrupt. I still swear by OS X, but not the iTard line of devices. I tell my nieces and nephews to get an Android cause they are not ignorant! lol There should be more of an effort to make people understand that Apple is using allot of *BSD (Linux) source. The GUI is closed, but some of the other source is available in the dev program site they host.
unimatrix725 said:
I use EFS Pro for BackUp and Restore.... Sadly its windows only, but works great with VirtualBox on Linux Mint Cinnamon/MATE 17.1 x64.
Hosted on the wonderful XDA:
http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546
Click to expand...
Click to collapse
Thank you! Certainly I know this good product. It can manipulate NVRAM through COM-port, just the way QPST does it communicating w/modem FW. Is has many advanced options but seems not to be reliable enough (too many OEM customizations around, it's difficult to reverse all) As you stated it can also backup some partitions (like EFS). but you can do this yourself just by simple ADB/Unix shell commands (e.g. "dd if=/dev/block/mmcblk0p?? of=/sdcard/mmcblk0p??.img")
You can write simple scripts and perform such backups directly from device (to SD). Furthermore, you can customize CWM/TWRP for your device to perform such backups from recovery.
To do it you should know which partition numbers to backup/restore (to backup/restore what data you want).
There are methods/commands available to get needed info to build full device partition map (e.g. some devices contains "folders" named "by-names" deeper in /dev/block/... (where partitions are named), but in some cases (e.g. some 2013 MSM7227 based Samsung phones like GT-S756x) there is no names associated with particular proprietary partitions in the device, (at all) so the only way to find what data reside there is to backup and look (hex) with your own "experienced" eyes what these data seems to be (or search what others found on the theme). EFSPro "from the box" also knows only a few device's partition maps so, in most cases you should build configuration for your device manually with full knowledge of it.
There is no problem to locate and backup encrypted modem data partitions (modemst*/efs/etc...) if your device is rooted. Moreover, if your device has standard Qualcomm bootloader (not OEM's cut) you can switch device to the standard Qualcom DM (download mode) when all your eMMC contents will be exposed to USB bus as mass storage device (just like UFD or SDCard) and you can backup/restore whole drive contents or particular partitions just like PC's own partitions (try some "chnese" stuff (made of quality parts) instead of "branded" ones and you'll see superiority of the "open world".
But main question is how to decrypt modem data to explore and change them as I want at any time. Mfrs (i.e. Qualcomm and OEMs hide serials, locks etc BS there, but there is a lot of other interesting stuff related to modem configuration which is also closed and encrypted. This drives me wild because it's my device and my serials/locks and other stuff too, so it's my option to do with is what I want and no one else. I'm definitely know and sure modem FW/config and even mask ROM (which we most probably never will be able to explore) contains many hidden features that may lead to remotely force device to collect info about user and perform actions without his knowledge and consent. I have no matter what all these sec... services planned to do with all these exploits they forced OEMs/chipmakers to implement., but (sic!) they allowed information about these exploits to leak wild! So some "generic" engineers who simply have job and low level access to cellular provider's equipment (which able to broadcast custom service packets) to make "what they want with user's phones (e.g. switch it on or request GPS data) just "for fun". F them all, but most idiotic is fact that being an 25y experienced "lowest level" service engineer I can't get access and control over my own devices (i.e. computers). It's incorrect. It would be difficult but we should pay more attention to explore internals and get clue what goes on.
unimatrix725 said:
FWIW
I hear you about Apple, used to be a hardcore fan, when they were nearly bankrupt. I still swear by OS X, but not the iTard line of devices. I tell my nieces and nephews to get an Android cause they are not ignorant! lol There should be more of an effort to make people understand that Apple is using allot of *BSD (Linux) source. The GUI is closed, but some of the other source is available in the dev program site they host.
Click to expand...
Click to collapse
I've personally explored OSX files and partitions and seen much modern Linux code inside. They even don't hide "copyrights". Nobody will explore anyway and nobody cares. Old 80x-90x versions of public licenses allowed to do "anything" with free open sources (including to make changes, then close sources and sell product). After some smartasses like Apple used this hole to sell free labor of thousands of peoples, public license had changed. Modern licenses allows you to sell derived product, but obligate you to open sources (with same license) so anyone else can use them to and sell too. You can't close your part of sources if free code is most valuable part of your product. E.g. router mfr can't close part his own sources to make firmware sources "uncompilable" because Linux definitely is most valuable part of router FW. This warrant later development of free open source programs and free community n whole. Apple stated that they used only old 80x code in their OS'es and then developed it separately and thus they are not obligated to open sources to everyone. They would be right unless they didn''t used a lot of modern code protected by modern public license's requirements. I didn't explored deeply. May be they publish all derived code for free. Today we can't say accurately if some modern Linux components they adopt for Mac/iOS are most valuable part of their systems or not. We should explore all the code to make decision. but anyway it's not fair to use a lot of thousand's people's free labor just to make money. Google's position here is not ideal but much more fair. They publish most of sources and support open source community. They don't try to make system "unbreakable" and they don't force you to use their accounts too much. I've NO Google "phone" account AT ALL. I've no need in any "markets", "clouds" ect BS., which lead absolutely no problem to me to effectively use Android devices. There are lots of free APK's around
It practice, I have 2-3 old iPhones just for experiments. Yes we have Jailbreaks and some other stuff, but even if you break and get access to your device it's very uncomfortable to work with it at low level. On my sight just one ADB interface costs more then all "jingles and bells" of iOS's GUI. All these "tethered-untethered", "unbreakable" bootloaders in Mask ROM, lack of normal tools to explore and manage data on any level, total control and extraction of my data by mfr via strongly encrypted obfuscated protocols and hidden services make these devices useless for me in practice.
Windows Phone is even far more closed OS then iOS. You have no control over your data at all. You can't do a thing with WP device unless you sign up with MS account. You can't get access to your own data (except MM files) unless you sync it with MS cloud, i.e. you will be forced to send all your private data to MS and MS will decide whether to give piece of it back to you or not. Matrix in action. I've absolutely no clue what thought MS bosses when they decided to close ALL in OS that have had less than 1% of market. Their 1st goal was to attract developers to write apps for their OS and there was no better way to kick them than "close All". There is no matter does it perform GUI actions good or not when devs and users have no effective way to collect and use "useful" results of device's work.
drkcobra said:
It is so irritating to see all of the jerks who are trying to spread viruses and malware nowadays.
Here is the REAL build 425:
http://www.mediafire.com/download/neeapht51ub2333/QPST.WIN.2.7_Installer-00425.1.zip
Click to expand...
Click to collapse
The new versions got rid of QXDM and RF NV Manager.
Build 415
etirkca said:
The new versions got rid of QXDM and RF NV Manager.
Click to expand...
Click to collapse
I have not used this version, so do not know if it has been removed from this one or not, but here is a legitimate copy of build 415:
http://www.mediafire.com/download/ac6yh57yye363mx/QPSTWIN2700415.rar