Related
Here is a flashable version of the full HTC Eris stock ROM - v 2.41.605.6.
March2011_OTA_ReferenceROM_v1.zip ( 99,606,802 Bytes; MD5: 770786915545a16f564a42e344ce7bb6 )
( 02/15/2012 - Re-hosted download link - thanks to XDA user doogald for providing a home for this ROM )
This is what you would get if you took the HTC 2.1 Leak-V3 PB00IMG.zip (same thing as the "Official 2.1 RUU") ROM, and then upgraded it twice - first with the July 2010 OTA, and then after that with the March 2011 OTA. (Using this ROM flash basically saves you that trouble.)
The ROM itself is completely stock, but unlike the "Flashback21" series of ROMs, this flash does not restore a stock recovery, nor flash any radio firmware - you can use it just like any other ROM.
(It is not meant to used for preparing a phone for resale or return - use the FlashBack21 ROM for that).
AGAIN, please note that this ROM is completely stock - it is not even rooted.
Feel free to use it as the basis for other 2.1 Sense ROMs.
If you want to have a "pure HTC stock ROM", but with the benefits of overclocking and rooting, I suggest you flash the "engtools3.zip" and Conap's "CFSv9" kernel immediately after flashing this. This would get you "stock+root+overclocking" - kind of like the original "PlainJane" ROM, but patched up to the current (3/2011) HTC software release.
One other note. Out of curiosity, I decided to run some benchmarks on a GB ROM vs. this HTC ROM, but using the same kernel (CFSv9), and clocked at a fixed rate (setCPU min = max = 748Mhz). So, I performed the kernel replacement and then ran a couple benchmarks.
This allows a crude comparison of what the improvements in the underlying dalvik engine have been between the Eclair release and the Gingerbread release - it is sort of "apples to apples" because the same kernel, scheduler, applications, and clock rates are used.
The numbers here are not the absolute benchmark values, but rather their RATIO - GB:Eclair. (In the cases where the benchmark value is "lower = better", or elapsed time, the value is inverted so that in all cases, a number greater than 1.0 indicates an improvement in Gingerbread). I used JIT = on, and compcache off for the GB ROM.
Code:
Ratio Benchmark
1.57 Quadrant Full
1.16 Elapsed Time (wall clock time) for Quadrant Full
1.10 setCPU "Long Bench"
0.96 setCPU "Native Bench" **
-.-- Linpack for Android - Skipped (not meaningful - too sensitive to JIT)
** This one should be very close to 1.0, as native code does not depend on the dalvik app engine.
In "real world" terms, Quadrant's raw score probably is not too meaningful - but notice that in elapsed time for the full benchmark, the GB ROM was consistently about 16% faster to completion. That measurement - wall clock time - is a "real world" metric. So, in addition to all the other goodness of Froyo/GB, you do seem to get a decent improvement - 10 to 15% - by switching to GB.
cheers,
bftb0
ah nice work man
Good work! I will definitely use this because I always keep falling back in love with stock HTC Sense xD
Sent from my Eris using XDA Premium App
nice! bftb0 always providing quality work/info for the Eris community! i was actually doing something similar! good to see you providing the Eris users even more choices!
thanks again!
Great work!!! This will definitely come in handy
Very nice!
This is great - thanks!
Thank you bftb0!
This saves a lot of time for all the base work on future updated versions of xtrROM and xtrSENSE! I really appreciate all you do for us in the Eris community.
Cheers
Sent from my Eris using XDA App
I think that the superlatives being tossed around here are causing the eyes of the real devs in this forum to roll backwards in their heads. I hope not!
There's not much skill in putting a stock ROM together - just a bunch of checking to make sure you've got all the symlinks, file modes, and permissions set up correctly. Then, zip it up and sign it!
( I did load it onto my phone and check everything to make sure nothing had gone horrible wrong; I suppose that counts for something - but that's not mad skilz, either. )
bftb0
bftb0 said:
I think that the superlatives being tossed around here are causing the eyes of the real devs in this forum to roll backwards in their heads. I hope not!
There's not much skill in putting a stock ROM together - just a bunch of checking to make sure you've got all the symlinks, file modes, and permissions set up correctly. Then, zip it up and sign it!
( I did load it onto my phone and check everything to make sure nothing had gone horrible wrong; I suppose that counts for something - but that's not mad skilz, either. )
bftb0
Click to expand...
Click to collapse
Oh stop being modest. You rock admit it.
Sent from my Eris using XDA App
So what's different in this new ota?
Sent from my CPCEris using XDA App
CPCookieMan said:
So what's different in this new ota?
Sent from my CPCEris using XDA App
Click to expand...
Click to collapse
Looks like it is mostly bug fixes with some enhancements in the Exchange client, MMS capabilities, and several other things.
Here is what Verizon had to say about it.
I did a "file differences analysis" (see this XDA post) that showed that 101 (out of ~127) different pre-installed apps had (.apk) changes, and 20 different framework libraries (.jar) showed changes too. Whether they were major or minor, I don't really know - just that it was apparent that a lot of stuff got "touched". The "system" image in both releases have a little north of 810 files in them - about 260 of those got changed.
I only had the ROM running for a short period of time (to do testing); the one thing that I noticed is that on my home WiFi (uses WPA), the association process was instantaneous - that was sort of rare for me in the past.
Was the radio changed at all in this update?
endoki said:
Was the radio changed at all in this update?
Click to expand...
Click to collapse
NO.
10char
semmtexx said:
Oh stop being modest. You rock admit it.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
Agree
bftb0 said:
I think that the superlatives being tossed around here are causing the eyes of the real devs in this forum to roll backwards in their heads. I hope not!
There's not much skill in putting a stock ROM together - just a bunch of checking to make sure you've got all the symlinks, file modes, and permissions set up correctly. Then, zip it up and sign it!
( I did load it onto my phone and check everything to make sure nothing had gone horrible wrong; I suppose that counts for something - but that's not mad skilz, either. )
bftb0
Click to expand...
Click to collapse
semmtexx said:
Oh stop being modest. You rock admit it.
Sent from my Eris using XDA App
Click to expand...
Click to collapse
zach.xtr said:
Agree
Click to expand...
Click to collapse
bftb0, the amount you help EVERYONE, no matter what ROM they are running or trying to run, is extraordinary. You may feel that you're "just doing your thing", but you deserve the praise that you get.
bftb0 said:
I only had the ROM running for a short period of time (to do testing); the one thing that I noticed is that on my home WiFi (uses WPA), the association process was instantaneous - that was sort of rare for me in the past.
Click to expand...
Click to collapse
I never had problem with WiFi and stock, but I do for sure with CM ROMs running CFS when I turn on WiFi from a widget. However, just to test, I flashed CFS v9 over this last night, turned off WiFi for a while, then turned it back on from the widget, and it also associated right away for me.
I have themed this ROM and am about 80% done with it. Thanks for this runs really well on the stock kernal. I am just wondering how popular 2.1 is now with Froyo and GB out. If there was a base of people that like sense eclair I would consider releasing it once it was finished.
jonathanphx1 said:
I have themed this ROM and am about 80% done with it. Thanks for this runs really well on the stock kernal. I am just wondering how popular 2.1 is now with Froyo and GB out. If there was a base of people that like sense eclair I would consider releasing it once it was finished.
Click to expand...
Click to collapse
I would love a theme with a blue battery and themed dialer! Would it be similar to the "Sensibility for Sense 2.2" theme you were working on?
No offense to anyone, but I would likely only even try the March OTA in the form of an updated ROM from zach.xtr, or if I modified it myself.
Nothing against you, it's just that whenever I want to go back to near stock, xtr's ROMs are just too well established for me to experiment with anything else.
As stated in this thread (0 credit to me) for the inspire 4G:
http://forum.xda-developers.com/showthread.php?t=982082
Editing the following build.prop values will increase the data speed:
ro.ril.gprsclass=12
ro.ril.hsdpa.category=14
ro.ril.hsupa.category=7
ro.ril.hsxpa=3
Reboot twice.
Could be only coincidental but I went from D1.4MB/U1mb up to 3.8/1.7 MB up In the same place I always test.
If you try this don't forget to backup (device might not boot/loose connectivity) and write down the original values (I didn't haha), and don't forget also to post your experience. thanks
I'm using Typhoon CM7 2.5.4
Thanks Rob... This is really awesome... Worked great for me.. I went form around 1.5DL to 3.5DL
will this work for the hd2 or is it only for the inspire 4g?
lsmosdef said:
will this work for the hd2 or is it only for the inspire 4g?
Click to expand...
Click to collapse
Seems to work on my Tmo HD2, I'm running CM7.
yea i attempted this.... dkno how much of a difference it made for me, but before i did this i was averaging 2mbps downloads speed and uploading i was averaging 600 to 800kbps ..very consistently
after, im averaging from 1.6mbps upwards to 3.8mbps so it did something i guess but its not very consistent from what ive been seeing on my phone.. but ive only tested it for an hr or so...ill keep testing it for another day or two, go back to my original setup and see if it was a big difference or not.
let me know how it goes with anybody else that has attempted this
Great informations for a newb like me. Thanks
So how do we get to the point to change these values?
akapaul26 said:
So how do we get to the point to change these values?
Click to expand...
Click to collapse
use root explorer and open up build.prop in /system/
okay so i was taking a look on the link for inspire 4g post 3 and the guy provides great info -links- http://forum.xda-developers.com/showpost.php?p=11884971&postcount=3
Should we adjust the values for our non hspda+ device? the values oy 1st post(inspire 4g) did the trick for me. but probably we should adjust them to our hd2
robrob777 said:
As stated in this thread (0 credit to me) for the inspire 4G:
http://forum.xda-developers.com/showthread.php?t=982082
Editing the following build.prop values will increase the data speed:
ro.ril.gprsclass=12
ro.ril.hsdpa.category=14
ro.ril.hsupa.category=7
ro.ril.hsxpa=3
Reboot twice.
Could be only coincidental but I went from D1.4MB/U1mb up to 3.8/1.7 MB up In the same place I always test.
If you try this don't forget to backup (device might not boot/loose connectivity) and write down the original values (I didn't haha), and don't forget also to post your experience. thanks
I'm using Typhoon CM7 2.5.4
Click to expand...
Click to collapse
Tried that my download speed remains on 44-45 kb/s no matter what ...
i'm on T-Mobile uk, checked apn settings and they're fine ...
someone please help ...
raziel123 said:
Tried that my download speed remains on 44-45 kb/s no matter what ...
i'm on T-Mobile uk, checked apn settings and they're fine ...
someone please help ...
Click to expand...
Click to collapse
I've posted about this on your own thead, take a look see
johnerz said:
I've posted about this on your own thead, take a look see
Click to expand...
Click to collapse
thanks mate, i'll have a look
regards
Confirm improvement on HD2 CoreDroid DHD V1.5
Having now D3.5 U1.4
no good for me
I've lost the GPRS data connection after mod. And I need it cos in area where i live is not a good 3G/HSDPA coverage so most of the time I'm on GPRS.
So moding back to the original settings
thnx
Sent from my HTC HD2 using XDA Premium App
HD2 class should dictate the build prop config. Speed tests have far too many variables to be reliable.
Gprs 12
Hspda 8
Hsupa 5
Hsxpa 2
Don't shoot me if I got the abbrevs wrong.
I get 3-4mb down 1.2-1.6 up connecting to servers 4000 miles away.
Sent from my HyperDroid powered HD2
Confirmed as working. On NexusHD2, I had to add the HSPDA and HSUPA lines, but all works as advertised after rebooting.
NOT WORKING FOR MY HD 2.
GPRS - 12
HSUPA - 10
HSDPA - 10
HSXPA - 2
That's my setting. The 12/8/5/2 or 12/14/7/3 just dont work for me and I've actually gotten worse data speed. I think it's location/cell tower/carrier dependent, so it might not yield the best result for all.
raziel123 said:
Tried that my download speed remains on 44-45 kb/s no matter what ...
i'm on T-Mobile uk, checked apn settings and they're fine ...
someone please help ...
Click to expand...
Click to collapse
did you get the settings sorted... on tmobile uk. im in the same boat pal..
hope you can help
Hi all,
I'm in interest about android for hd mini.
I tested the R175 and my battery is going empty in about 1-2hours.
however, i see a strange logcat:
Code:
D/WifiService( 287): ACTION_BATTERY_CHANGED pluggedType: 2
I/global ( 287): Default buffer size used in BufferedReader constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
I/global ( 287): Default buffer size used in BufferedReader constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
D/BatteryService( 287): isUsbConnected() = true
D/BatteryService( 287): mPlugType = 2
E/Tethering( 287): active iface (usb0) reported as added, ignoring
D/UsbConnectedReceiver( 465): action = psclient.intent.action.usb_status
D/UsbConnectedReceiver( 465): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 465): usbCurrentType = 2
D/UsbConnectedReceiver( 465): Current type is same as previous, return!
D/dalvikvm( 404): GC_EXPLICIT freed 43 objects / 1784 bytes in 168ms
V/KeyguardViewMediator( 287): password timeout now
D/WifiService( 287): ACTION_BATTERY_CHANGED pluggedType: 2
I/global ( 287): Default buffer size used in BufferedReader constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
I/global ( 287): Default buffer size used in BufferedReader constructor. It wo
uld be better to be explicit if an 8k-char buffer is required.
D/BatteryService( 287): isUsbConnected() = true
D/BatteryService( 287): mPlugType = 2
E/Tethering( 287): active iface (usb0) reported as added, ignoring
D/UsbConnectedReceiver( 465): action = psclient.intent.action.usb_status
D/UsbConnectedReceiver( 465): ACTION_BATTERY_CHANGED
D/UsbConnectedReceiver( 465): usbCurrentType = 2
D/UsbConnectedReceiver( 465): Current type is same as previous, return!
Theses messages repeat every 2 seconds...
Any idea ?
I think this could help to kill battery drain issue.
I fixed it in my kernel and diffs in battery driver is:
schlund/r0bin kernel:
Code:
void notify_cable_status(int status)
{
printk("%s, VBUS IRQ triggered, VBUS=%d)\n", __func__,status);
//activate VBUS for usb driver
msm_hsusb_set_vbus_state(status);
//queue work to avoid blocking irq
queue_work(g_vbus_notifier_work_queue, &g_vbus_notifier_work);
}
my kernel:
Code:
int usb_disabled;
void notify_cable_status(int status)
{
printk("%s, VBUS IRQ triggered, VBUS=%d)\n", __func__,status);
//activate VBUS for usb driver
msm_hsusb_set_vbus_state(status);
if (status)
usb_disabled = 0;
//queue work to avoid blocking irq
queue_work(g_vbus_notifier_work_queue, &g_vbus_notifier_work);
}
schlund/r0bin:
Code:
//r0bin: fix battery drain issue & keep usb connection stable!
if(!((source==CHARGER_USB) || (source==CHARGER_AC)))
msm_hsusb_set_vbus_state(0);
my kernel:
Code:
//r0bin: fix battery drain issue & keep usb connection stable
//cardsharing-x: fix double call bug!
if (!((source==CHARGER_USB) || (source==CHARGER_AC))) {
if (!usb_disabled)
usb_disabled = 1;
}
if (usb_disabled == 1) {
msm_hsusb_set_vbus_state(0);
usb_disabled = 2;
}
I think schlund will implement it in his kernel?
munjeni said:
I think schlund will implement it in his kernel?
Click to expand...
Click to collapse
yes, and no, for my next project i am currently rewriting a whole new kernel, step by step, already fixed many issues, but actually battery driver is what i am working on. i am not using the old one.
however, i have to make a brake now with development, the screen got broken.
Okay thank you
But, it could be a source of problem or not ?
If i let this message appear, what could be the consequences ?
schlund said:
however, i have to make a brake now with development, the screen got broken.
Click to expand...
Click to collapse
I was hoping so much in two 2 / 3 weeks as announced ............... Do you think we do for Christmas a welcome gift?
thanks and good job
schlund said:
yes, and no, for my next project i am currently rewriting a whole new kernel, step by step, already fixed many issues, but actually battery driver is what i am working on. i am not using the old one.
however, i have to make a brake now with development, the screen got broken.
Click to expand...
Click to collapse
Huh, so remaing developer is only derefas?
i talked to my chinese dealer today because of the replacement part, seems it will take some weeks to get a new one (thank christmas), so
yes, i decided to give you a half christmas present:
originally i wanted to present you a cyanogenmod 7 for photon, codename "photonic" including a brand new 2.6.35 kernel, very fast, very clean, new battery driver, repaired mmc driver (copying files via usb), build in overclocking feature, repaired clock driver (time&alarm issue w/o workaround) etc etc...
because of the things happened to my phone yesterday i will present you this:
"photonic" cm 7.2.0 (gingerbread 2.3.7) with modified 2.6.32 kernel with at least the things working like previous releases. sorry for that.
as a special gift i will also offer a easy development environment with all sources for those that are interested. (btw this environment will be compatible with future lkbootloader )
EDIT: i can say it will be released ~ next 3 days
Great news Thank you schlund
I'm sorry for your broken screen...
good news! thanks a lot
can anyone test the last chainfire 3d ?
it seems that before i install chainfire i had more that 170 mah in sleep in flight mode
now i have 13 mah in flight mode
Sent from my Touchpad using xda premium
schlund said:
EDIT: i can say it will be released ~ next 3 days
Click to expand...
Click to collapse
Schlund hello, how are you .... there is nothing for us?
If we do not feel for Christmas, happy holidays
baggino said:
Schlund hello, how are you .... there is nothing for us?
If we do not feel for Christmas, happy holidays
Click to expand...
Click to collapse
I thought about that very thoroughly..
I am still very sad of my sources being leaked, i think you can understand that. I spend so much time -hours, days and nights- on CM 7.2, also on teaching others how to make the fixes. Finally its very disapointing to see it published (unfinished) by someone else.
I thought about giving up on the project, only to be used by myself. But I know lots of you are waiting for it. I still don't know how to handle my work (sources). If i open them again, someone will come and copy it, but on the other hand its stupid to hide them, they should be shared so that everybody can work on them.
Is it that bad to expect some respect on your work ?
I will make a Roadmap of my future plans and let you know
You have all my sympathy for the time you're going through, unfortunately the world is full of mediocre and cowardly. I refuse to believe that we are left with your ambitious project for our mini so I'm confident and ready for a restart. I unfortunately do not have the skills to help our merit, but I know that I respect.
I renew my best wishes for a Merry Christmas
schlund said:
I thought about that very thoroughly..
I am still very sad of my sources being leaked, i think you can understand that. I spend so much time -hours, days and nights- on CM 7.2, also on teaching others how to make the fixes. Finally its very disapointing to see it published (unfinished) by someone else.
I thought about giving up on the project, only to be used by myself. But I know lots of you are waiting for it. I still don't know how to handle my work (sources). If i open them again, someone will come and copy it, but on the other hand its stupid to hide them, they should be shared so that everybody can work on them.
Is it that bad to expect some respect on your work ?
I will make a Roadmap of my future plans and let you know
Click to expand...
Click to collapse
As I say before and allway say that, I always demanded that all work need to be accessible to all (one brain can not be smarter than a set of brains, and it is a fact!)... I understand you (but not all time) and I'm sorry about that, but that's why this project will never be completed because of hiding sources, hiding opinions... etc. Final fact is: this project is dead and tousands of the peoples sold his phone! I sold my phone from that reason becouse here no teamwork! Who understands me will understand what I say, who does not understand, I'm sorry, the fact is that everyone has different ideas and that each job with a new idea === the job is always better. I think that even if all errors come repaired, I think it's too late now to make someone happy!
munjeni said:
I think it's too late now to make someone happy!
Click to expand...
Click to collapse
No it's never too late for some of us... I live in Greece and recently i got fired from my job So i don't have enough money to buy another device. I'm stuck with my hd mini. A good release would make me very happy
Sadly Thing...
I thought everything here.. must be Open-Source Codes (that everyone can share together )
Anyway, We're Happiness and Very Thankfully for a Stable Android of Developers.
Well, I believe working together is not the same as sharing all sources. It is also needed to have agreement on a common goal and path. I hope that will still happen
Sent from my HTC Liberty using XDA App
schlund said:
I will make a Roadmap of my future plans and let you know
Click to expand...
Click to collapse
ops.........I have posted the new display of the mini? I hope to read you soon
ciao
Hello all,
Looks like I have managed to fix this bug. Here is the code.
//android/packages/apps/Contacts/src/com/android/contacts/datepicker/DatePicker.java
if (months[0].startsWith("1")) {
for (int i = 0; i < months.length; i++) {
months = String.valueOf(i + 1);
}
//mMonthPicker.setMinValue(1); //-----------------------------------------------------------> setMinValue should be 0
mMonthPicker.setMinValue(0);
mMonthPicker.setMaxValue(12);
} else {
//mMonthPicker.setMinValue(1); //-----------------------------------------------------------> setMinValue should be 0
mMonthPicker.setMinValue(0);
mMonthPicker.setMaxValue(12);
mMonthPicker.setDisplayedValues(months);
}
mMonthPicker.setOnLongPressUpdateInterval(200);
mMonthPicker.setOnValueChangedListener(new OnValueChangeListener() {
@Override
public void onValueChange(NumberPicker picker, int oldVal, int newVal) {
/* We display the month 1-12 but store it 0-11 so always
* subtract by one to ensure our internal state is always 0-11
*/
//mMonth = newVal - 1; //----------------------------------------> Should be newVal
mMonth = newVal;
// Adjust max day of the month
adjustMaxDay();
notifyDateChanged();
updateDaySpinner();
}
});
You can test the apk attached
still not perfect, just an immediate solution so that you do not miss the Christmas!!!
-Adarsh
what is the problem ??i cant understand ..
leap_ahead said:
what is the problem ??i cant understand ..
Click to expand...
Click to collapse
December disappeared in JOP03C, 4.2
leap_ahead said:
what is the problem ??i cant understand ..
Click to expand...
Click to collapse
How's life under that rock of yours? ^^
J/k, it's a 4.2-bug. Google forgot December in contacts-app (when making an appointment), it's fine in calendar-app.
The Contacts app in 4.2 missed Dec when adding events related to a contact.
To me the problem looks like, Google guys changed the way to check the limits in the code. for example instead of using for(i=0;i<=length;++i),
they used for(i=0;i<length;++i). So one value was missed this time.
reason could be beyond this also.
december missed because google thinks it's the end of the world
mMonthPicker.setMinValue(0);
mMonthPicker.setMaxValue(12);
Click to expand...
Click to collapse
This doesn't seem to be a proper fix. Now the possible values are 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 = 13 values.
Thanks.
FloHimself said:
This doesn't seem to be a proper fix. Now the possible values are 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12 = 13 values.
Click to expand...
Click to collapse
Commit from Cyanogenmod!
http://review.cyanogenmod.org/#/c/26856/
Sent from my Nexus S using Tapatalk 2
Articudos said:
Commit from Cyanogenmod!
http://review.cyanogenmod.org/#/c/26856/
Click to expand...
Click to collapse
Yes, the CyanogenMod version differs from this one.
adarshahd said:
The Contacts app in 4.2 missed Dec when adding events related to a contact.
To me the problem looks like, Google guys changed the way to check the limits in the code. for example instead of using for(i=0;i<=length;++i),
they used for(i=0;i<length;++i). So one value was missed this time.
reason could be beyond this also.
Click to expand...
Click to collapse
I think for(i=0;i<length;i++) its the right one. Dont forget that the "i" variabel is going to be the position, and it starts in 0 and goes to 11. 12 values, as it should be.
am i wrong?
Articudos said:
Commit from Cyanogenmod!
http://review.cyanogenmod.org/#/c/26856/
Sent from my Nexus S using Tapatalk 2
Click to expand...
Click to collapse
Solved in 4.2.1!!
AT&T:
T-Mobile:
Discuss.
Download the app on f droid:
https://f-droid.org/repository/brow...did=org.projectvoodoo.simplecarrieriqdetector
https://f-droid.org/repo/org.projectvoodoo.simplecarrieriqdetector_16.apk
catzilla said:
AT&T: https://i.imgur.com/HVe2ALY.png
T-Mobile: https://i.imgur.com/j0bmgOp.jpg
Discuss.
Click to expand...
Click to collapse
Maybe I'm misreading those reports? But it looks like the stuff that triggered it is lower down. All of what's displayed says "Not Found." Could you scroll down to the problematic bits and show them as well?
This comes as no surprise. Another reason why the end goal of any phone is to obtain root.
DaBunny said:
Maybe I'm misreading those reports? But it looks like the stuff that triggered it is lower down. All of what's displayed says "Not Found." Could you scroll down to the problematic bits and show them as well?
Click to expand...
Click to collapse
Full log:
Voodoo Carrier IQ Detector report:
Build fingerprint:
lge/p1_att_us/p1:5.1/LMY47D/151421018d413:user/release-keys
Carrier IQ has been found and is active
Detection score: 270
Test for: Linux kernel dmesg log
(DMESG, weight 100)
nothing found
Test for: Suspicious classes
(SUSPICIOUS_CLASSES, weight 0)
found: com.carrieriq.iqagent.service.receivers.BootCompletedReceiver
Test for: Android logcat debugging log
(LOGCAT, weight 100)
nothing found
Test for: Linux kernel interfaces
(KERNEL_INTERFACES, weight 50)
nothing found
Test for: Packages
(PACKAGES, weight 70)
nothing found
Test for: Running processes
(RUNNING_PROCESSES, weight 200)
found: system 4633 510 1626028 13308 ffffffff 00000000 S diagandroid.iqd
Test for: ROM configs
(ETC_CONFIG, weight 0)
nothing found
Test for: Linux kernel drivers
(KERNEL_DRIVERS, weight 50)
nothing found
Test for: ROM binaries and daemons
(SYSTEM_BINARIES, weight 70)
found: /system/lib/libiq_client.so
found: /system/lib/libiq_service.so
Test for: System services
(SERVICES, weight 70)
nothing found
Snakecharmed said:
This comes as no surprise. Another reason why the end goal of any phone is to obtain root.
Click to expand...
Click to collapse
2x on this, it should be no surprise that CIQ is on any carrier's standard phone build - especially T-Mobile. Correct me if I'm wrong, but I believe parts of CIQ are packaged in the My T-Mobile app, for the purpose of "diagnostics." That app even asks for permission to collect diagnostic data and send it back to the mothership.
BigJohn89 said:
2x on this, it should be no surprise that CIQ is on any carrier's standard phone build - especially T-Mobile. Correct me if I'm wrong, but I believe parts of CIQ are packaged in the My T-Mobile app, for the purpose of "diagnostics." That app even asks for permission to collect diagnostic data and send it back to the mothership.
Click to expand...
Click to collapse
It is for diagnostics. I'm in T-Mobile tech and its the most helpful thing ever.
you wanna talk scary.... my first G4 came with a buggy SD card slot, sometimes detected, sometimes not.... Anyway, I called T-mobile support and the tech I spoke with on the phone KNEW when my SD Card was inserted and when it was not. WTF is THATTTTT??!?!?!
Who cares about CarrierIQ now, NSA got you all even without carrierIQ. So what's the matter about removing it.......
FWIW, I checked my Verizon G4 with 3 different CIQ apps (Lookout, Bit Defender, Trend Micro) and it came up clean. I remember a few years ago that they said they wouldn't use CIQ, but I'm sure they have the same capabilities, under a different name.
So what exactly does CIQ do/why is it important to be aware of it? I have a VS986 and would like to know just how much data is being collected about me and what I do/where I go.
nineeightyone said:
So what exactly does CIQ do/why is it important to be aware of it? I have a VS986 and would like to know just how much data is being collected about me and what I do/where I go.
Click to expand...
Click to collapse
I'd like to know, too. I'm on T-Mobile, but why should I care? Other than paranoia that people have, how does it affect me?
Omg carrierIQ!!
Sent from my SM-G920T
Can't you just turn off diagnostics (on the H811 at least) and CI is disabled?