yashsingh1/xdaforums huggingface dataset:
[Galaxy Note II Q&A, Help & Troubleshooting] sifat004:
Tried it also ..but not working.

Battery percentage stays same...its not increasing.
[Galaxy Note II Q&A, Help & Troubleshooting] sifat004:
Anyone to help me please......
[Galaxy Note II Q&A, Help & Troubleshooting] Simone:
Looks like a damaged USB port.
[Galaxy Note II Q&A, Help & Troubleshooting] Aumkar:
Take out the battery and put it back in. I hardly think your battery will be the same especially after you use the phone and it's idle for so long.
[Galaxy Note II Q&A, Help & Troubleshooting] sifat004:
tried everything but no help..

Should I take it to repair center?
[Sony Xperia S, Acro S, Ion] ReBorn1983:
I have installed the Trinity Vengeance RaptorXL™ Special Edition 1.5 ROM and got some issues with Adblock plus.

After every reboot adblock cant set the proxy rules.

Someone got a solution for this?

thx
[Sony Xperia S, Acro S, Ion] pharix:
And this goes to Q&A section brother :)
[Sony Xperia S, Acro S, Ion] cities516:
The easiest solution is to use another ad block service, such as AdAway.
[Sony Xperia S, Acro S, Ion] ReBorn1983:
it seems to be aproblem with superuser... adblock dont get the root permission and cant set the proxy. after killing and restarting the process its working.

maybe im going to try a nother blocking software
[One (M7) Q&A, Help & Troubleshooting] Lou_tzepher:
Has anyone ordered their unit from expansys? If so, how long did it take?

I find the service quite tricky: I placed an order for two ones (black for me, silver for my father) on 27th April, on 28th I got an email that the card I provided has expired (my typo) advising me to email them. I did, but received no response. After some time I called them to settle the issue by phone. It was only 2 weeks later, when I called to enquire about my order when I was told that orders above £1k must be paid for by a bank transfer rather than by card. I transfered the funds and keep waiting since the 7th. During that time, the "expected time" on the order page has frequently reached 1 day just to rise to 4 or 6 the following morning. There is no sign of me being closer to receiving my phones.

Is this typical for One, or am I just particularly unlucky?
[Xperia Z Q&A, Help & Troubleshooting] mr_negative16:
Hi,, i need some help to understand what iso does to photo

Can some one please explain

What does100, 200, 400, 800, 1600 iso do?

And what settings to use indoors and night

sent from my white xperia z
[Xperia Z Q&A, Help & Troubleshooting] mcapozzi:
ISO is the light sensitivity of the image sensor. The higher the number, the more light sensitive the image sensor becomes. In low light, you'll want the sensitivity to be higher so that the image can be captured faster, especially if the object is moving (otherwise the "shutter speed" is too long and all you'll get is a giant blur). The trade-off with increased sensor sensitivity is noise (in film terms, it would be called film grain). Pictures taken with high ISO will have less clarity and the color will not be as true. Ideally, an ISO of 100 will provide the best looking shots.

Simply put, leave it at 100 for an outdoor picture of a relatively still object. Increase ISO as the light decreases and the subject increases movement.

-Mike
[Xperia Z Q&A, Help & Troubleshooting] o0oP5:
to make it easier to understand,

ISO 100 = best quality, lowest noise, slowest shutter time, used in bright environment

ISO 1600 = worse quality, highest noise, fastest shutter time, used in low light environment

however you don't always have to use ISO 1600 when taking picture in low light environment,,

since you got flash to slightly enhance the shutter time.
[MDA, XDA, 1010 General] h0t_Sh0t:
Hi there,

this morning my phone didn't charge anymore....

I tried lots of things, many cables and cradles but still I don't get an Orange light when I put the cable in it, does anyone know what I can do?? cause it's battery is VERY low and nog getting any fuller...

plz help me

h0t_Sh0t
[MDA, XDA, 1010 General] cruisin-thru:
Sounds like a blown fuse on the motherboard, do a search on this forum for details of repair procedure.
[MDA, XDA, 1010 General] Nazzers:
How long you had the unit?

If you, like myself, are not as technically advanced as some others, and you haven't had the phone long, send it back to whomever the manufacturer was and they will likely fix it. I bought an Siemens SX56 from ebay a couple of months ago and had the exact same problem, told me to do a hard reset first, that did nothing, then I sent it in to get fixed, apparently it was easier and cheaper for them to just send me a new unit because in about a week and half, I had one at my door. Of course, the unit I sent in was unlocked, as I use cingular and the Siemens is an ATT phone, but the new unit was locked to ATT, that's how I found this site, I had it unlocked in 5 minutes. Anyway, if you have had the phone less than 60 days, I would send it in and get it fixed.
[MDA, XDA, 1010 General] h0t_Sh0t:
that's one problem,

I live in the netherlands, and i bought it from my uncle who lives in Singapore....and he bought it there....

But I'll check the forum to see what I can do about it....

thnx anyway

h0t_sh0t
[MDA, XDA, 1010 General] GoldenSands:
Dear h0t_Sh0t, I have few advices that might help..

1- Check if your device has International warrenty.

2- Check is the connector socket is loose from inside or not well connected, this is where the little thing goes inside the imate to connect. Mine got loose one month ago, and then was almost broke, then did not charge or make Sunc, I got it to be repaired at almost US $ 65.

Hope this helps.
[MDA, XDA, 1010 General] h0t_Sh0t:
i'm very sorry, but my english is not so good,

I don't really get the first advice..... (i'm very sorry, maybe a dutch guy can translate it for me(or i'll ask my brother tonight))or can someone explain it a little bit...

and do you mean by your second advice or my XDA is well connected to the cradle???(cause i can sync it with the computer, but he isn't recarging)

I'll mail some peeps who might know something to....

thnx for your help

h0t_Sh0t
[Galaxy S II Q&A, Help & Troubleshooting] nickbw:
Please Help clear up confusion and problems about backing up restoring EMEI/EFS

Pone is i9100 rooted and unlocked but originally branded O2. I have changed the firmware many times without incident from GB to ICE and JB. I used to use an IBM Thinkpad T40 with Windows 7 Ultimate but as the HDD is only 30GB and has little free space I now use a Lenovo Thinkpad Edge 520 with Windows Pro 64bit and 4GBRAM.

Last month I decided to experiment with different JB ROMs having read the warnings about backing up the EFS, so I made a backup and stored a copy on the HDD of my laptop. I also found, with file manager, that the following files exist in GT19100\internal\storage:-

Efs image – modified 20/05/2013 8:07

IMG file 20.0GB

Efsbackup.tar – modified 10/05/2013 19:54

GZ file 28.0KB

All was well until sometime last week when I installed a nightly build of ROM, which had been the stable version of i900_PAC_JB_4.2.2 v22.1.0 20130411-091725, after which I noticed “mobile network state” = Disconnected.

I checked EFI with file explorer which said file was empty. This is confirmed by *#06# when IEMI is blank blue field with OK underneath! So, I thought, no problem I made a backup and its on my computer. So I tried restoring the EFI. I came up against multiple problems suggesting the phone was not now permanently rooted. So I reinstalled SuperSu Pro 1.00. I tried using EFS_Professional to backup/restore the EMI.

All seemed to be working until I received the error message: COULD NOT FINDC:\users\.....\EFS_Pro_20.0.33_Release\EFSPro\GT-19100.PIT.

I tried a second time this time receiving ‘EFS…partition location /dev/block/mmcb1k0p1 Re-mounting EFS folder read/write Okay, Repairing ownership of ‘efs/nv_data.bin’ Repiar NV data ownership completed. So I hoped I had restored the EMEI. Not a bit of it! File explorer confirms there is data in the EFS folder on \internal\storage but says the file is too big to display as a text file, and after rebooting and trying *#06# I still have no IMEI !

Where can I go from here please? :confused:

Kernel: 3.0.31_CM_ga034655

Kernel version: #1_SMP PREEMT Sun May 12 16:04:20 AST 2013

ROM Build: GT-19100-user4.0.3 (ML74K XXLPQ release-keys)

Android v.4.2.2

Busybox v.1.20.2-CM9

SuBinary9 com.android.settings
[Galaxy S II Q&A, Help & Troubleshooting] immortalneo:
Flash stock and try restoring EFS after that?

"To err is human, to forgive is divine"

Sent from my SGS II
[Galaxy S II Q&A, Help & Troubleshooting] nickbw:
Solved!

Thank you so much for suggesting I go back to a stock ROM. I really lost confidence and was fretting about brickbug too much to go that route before your post. I used a custom stock ROM "Eternity" Android 4.1.2 XWLS8 with Kernel 3.0.31-Jeboo and Baseband XXLS6 worked like a charm. So my IMEI file was good after all !:laugh:
[Galaxy S 4 Q&A, Help & Troubleshooting] bala_gamer:
Guys can any of you reproduce the below logcat error?? its there from day one and i thought some custom roms might resolve it, but the error pops out ever few seconds.

05-20 18:35:31.179: E/McDaemon(2455): *****************************
05-20 18:35:31.179: E/McDaemon(2455): *** ERROR: Cannot open /system/app/mcRegistry/ffffffffd00000000000000000000004.tlbin
05-20 18:35:31.179: E/McDaemon(2455): *** Detected in mcRegistryFileGetServiceBlob/817()
05-20 18:35:31.179: E/McDaemon(2455): *****************************
05-20 18:35:31.179: E/McClient(29224): *****************************
05-20 18:35:31.179: E/McClient(29224): *** ERROR: Daemon could not open session, responseId 16.
05-20 18:35:31.179: E/McClient(29224): *** Detected in mcOpenSession/387()
05-20 18:35:31.179: E/McClient(29224): *****************************
05-20 18:35:31.179: E/ss_tz_mobicore.c, ln. 915(29224): DrValidator opening session failed: 16
05-20 18:35:31.179: E/ss_tz_mobicore.c, ln. 853(29224): Error load DrValidator
05-20 18:35:31.179: E/ss_tz_mobicore.c, ln. 149(29224): Error opening session
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/McClient(29224): *** ERROR: Session 0 not found
05-20 18:35:31.184: E/McClient(29224): *** Detected in mcUnmap/1059()
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/ss_tz_mobicore.c, ln. 197(29224): Error during input memory unmapping: 8
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/McClient(29224): *** ERROR: Session 0 not found
05-20 18:35:31.184: E/McClient(29224): *** Detected in mcUnmap/1059()
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/ss_tz_mobicore.c, ln. 203(29224): Error during input memory unmapping: 8
05-20 18:35:31.184: E/McClient(29224): *****************************
05-20 18:35:31.184: E/McClient(29224): *** ERROR: Session 0 not found
05-20 18:35:31.184: E/McClient(29224): *** Detected in mcUnmap/1059()
05-20 18:35:31.189: E/McClient(29224): *****************************
05-20 18:35:31.189: E/ss_tz_mobicore.c, ln. 209(29224): Error during caches memory unmapping: 8
05-20 18:35:31.189: E/ss_tz_mobicore.c, ln. 214(29224): Error closing session
05-20 18:35:31.199: E/ss_daemon.c, ln. 148(29224): Error cannot connect to TA/driver!
[Galaxy S 4 Q&A, Help & Troubleshooting] bala_gamer:
bumping :)
[Galaxy S 4 Q&A, Help & Troubleshooting] bala_gamer:
bump
[Galaxy S 4 Q&A, Help & Troubleshooting] UpInTheAir:
No error.

Stock I9500 MDL with perseus kernel and CWM.
[Galaxy S 4 Q&A, Help & Troubleshooting] sebarkh:
Bump
[Galaxy S 4 Q&A, Help & Troubleshooting] OptimalKiller:
Hi bala.

Yep im getting the error message on bmea build rom.

I was going to delete the mcRegistry to see if the error went away. But just not had the time yet.

Optimal

Sent from my GT-I9505
[Galaxy S 4 Q&A, Help & Troubleshooting] clonednull:
get the same errors with FoxHound 0.6 (MF4) on Adam Kernel 1.4

would be cool if we could clarify it
[Galaxy S 4 Q&A, Help & Troubleshooting] clonednull:
i have investigated a little bit about the error messages.

as far as i can tell it is caused by the MobiCore Module wich is a Secured Mobile VPN for android.

i think it is used for all type of secure mobile payment options like nfc payment.

afaik there is a problem with nfc payment and custom roms (especially deodexed ones).

i dont have enough knowledge about the circumstances why it causes problems but i think it is something security related and that it is also the reason why the MobiCore Module does not load properly.

If this is the fact then someone with properly working nfc payment should not have this error messages in his logcat.

(it would be cool if someone could confirm this).

Maybe someone with more technical background can bring some light into this discussion. :confused:

sources:

MobiCore® Secured Mobile VPN for Android PDF

git googlesource of the mobicore module on the exynos platform with the code displaying the error ("Could not initialize MobiCore!")

MobiCoreDriverDaemon.cpp
[Galaxy S 4 Q&A, Help & Troubleshooting] OptimalKiller:
Hi clonednull.

See my previous post on nfc payment which relates to this. As I have been doing some investigation.

http://xdaforums.com/showthread.php?p=42825999

Nfc payment will not work on deodex rom because of signature checks and looking for particular odex files and odex framework files.

Optimal

Sent from my GT-I9505
[Galaxy S 4 Q&A, Help & Troubleshooting] clonednull:
Thanks Optimal for bringing this up. I could imagine the MobiCore module also fails to load because of such security circumstances. As a VPN for payment transactions it would make sense.
[Galaxy S 4 Q&A, Help & Troubleshooting] elesbb:
I too am getting a very similar error. However, mine is this

E/QcrilMsgTunnelSocket( 2677): IOExceptionjava.io.IOException: No such file or d
irectoryReason: No such file or directory
E/McDaemon( 6149): *****************************
E/McDaemon( 6149): *** ERROR: open failed with "Permission denied"(errno 13)
E/McDaemon( 6149): *** Detected in external/mobicore/daemon/Kernel/CKMod.cpp:7
9/open()
E/McDaemon( 6149): *****************************
E/McDaemon( 6149): *****************************
E/McDaemon( 6149): *** ERROR: Could not initialize MobiCore!
E/McDaemon( 6149): *** Detected in external/mobicore/daemon/Daemon/MobiCoreDri
verDaemon.cpp:133/run()
E/McDaemon( 6149): *****************************
E/McDaemon( 6149): *****************************
E/McDaemon( 6149): *** ERROR: Exiting MobiCoreDaemon
E/McDaemon( 6149): *** Detected in external/mobicore/daemon/Daemon/MobiCoreDri
verDaemon.cpp:951/main()
E/McDaemon( 6149): *****************************

Have we found a solution/fix yet?
[Galaxy S 4 Q&A, Help & Troubleshooting] bala_gamer:
the error is there on almost all roms custom/stock .
[Galaxy S 4 Q&A, Help & Troubleshooting] elesbb:
I was able to fix it. There is a service that is being ran from the kernel. Can be disabled from either the init.rc or deleting renaming,

Mobicore-presetup.sh

Mobicore-startup.sh

Under directory /system/bin
[Galaxy S 4 Q&A, Help & Troubleshooting] bala_gamer:
great to see a working solution finally, does it have any other impact?
[Galaxy S 4 Q&A, Help & Troubleshooting] elesbb:
Nothing that I can see. Everything is still fully functional!
[Galaxy S 4 Q&A, Help & Troubleshooting] OptimalKiller:
Ok folks.

Can someone test this if they have not deleted the .sh scripts.

Currently I am not getting any errors on my phone.

Can someone who is currently getting the errors go into the following folder /system/app/mcRegistry/

And let me know if they have any files inside that folder.

Optimal

Sent from my GT-I9505
[Galaxy S 4 Q&A, Help & Troubleshooting] clonednull:
i'm getting the error (running Foxhound 0.9) and this is the content of my "mcRegistry" folder:

shell@android:/system/app/mcRegistry # ls -l
ls -l
-rw-r--r-- 1 system system 9929 Aug 1 2008 07010000000000000000000000000000.tlbin
-rw-r--r-- 1 root root 5001 Aug 1 2008 FFFFFFFF000000000000000000000001.drbin
-rw-r--r-- 1 system system 17821 Aug 1 2008 ffffffff000000000000000000000004.tlbin
-rw-r--r-- 1 system system 48317 Aug 1 2008 ffffffff000000000000000000000005.tlbin
-rw-r--r-- 1 system system 42973 Aug 1 2008 ffffffff000000000000000000000008.tlbin
-rw-r--r-- 1 system system 109773 Aug 1 2008 ffffffff000000000000000000000009.tlbin
-rw-r--r-- 1 system system 50893 Aug 1 2008 ffffffffd00000000000000000000004.tlbin

this are the links generated by the .sh scripts
[Galaxy S 4 Q&A, Help & Troubleshooting] OptimalKiller:
Counts that idea out last time I remember getting those errors. My files was missing from that folder.

I thought it might have been those files causing that particular error.

Been trying to get the error again. But im defo not getting them at the moment.

Optimal

Sent from my GT-I9505
[Galaxy S 4 Q&A, Help & Troubleshooting] seanpr123:
Just noticed these errors as well on my I337 running FoxHound .9 and a quick Google search brought me back here.

My log cat is just continuously streaming data with that error mixed in.

Does everybody's log write so fast when phone is doing nothing else that you can't even keep up or read it without pausing? Makes me worried about how much is running in the background when I try to keep my phone as streamlined as possible as is.
[Galaxy S 4 Q&A, Help & Troubleshooting] bala_gamer:
just searched for those files and shockinly those files are not there in system/bin in wanam mf8 based rom
[Galaxy S 4 Q&A, Help & Troubleshooting] elesbb:
Can you upload or attach your kernel for me? I was able to find everything from the init.rc. yours might have a different name or something. Or maybe different location.
[Galaxy S 4 Q&A, Help & Troubleshooting] bala_gamer:
im using perseus latest kernel :)
[Galaxy S 4 Q&A, Help & Troubleshooting] starbucks2010:
How can you disable it from init.rc?

Thank you.
[Galaxy S 4 Q&A, Help & Troubleshooting] elesbb:
its different per kernel, but there are calls to system/bin services that are being ran which are responsible for the mcDaemon process.
[Galaxy S 4 Q&A, Help & Troubleshooting] starbucks2010:
I'm using Adam kernel 1.6. I searched inside init.rc and there is nothing related to mcDaemon. I'm not so good on this, so please tell me more preciselly how can I stop this service.

PS. I renamed those 2 files but I still get those error messages.

Thank you for your time and support.
[HTC Droid DNA] supertoast92:
Hi everyone, I've been searching for a considerable amount of time now for this, so I thought maybe someone else would have the answer readily available.

I'm looking for a simple battery percent mod to add to a stock 2.06 ROM, rooted of course. A simple mod that slaps the percentage over the stock battery even. I'm thinking the easiest solution at this point may be to go with a ROM that already includes it, but I figure I'd ask anyway :)

I've already tried various battery mods and ended up having to reflash the Rom to fix my mistakes.

Does anyone have a link to one that's hidden somewhere?

Thanks!
[AT&T, Rogers HTC One X, Telstra One XL] TonyStark R.I.P.:
Enjoy your OT conversation here regarding

[ROM][4.2.2][NIGHTLIES] CyanogenMod 10.1 for HTC One XL

Keep it clean and friendly.
[AT&T, Rogers HTC One X, Telstra One XL] buradd:
First
[AT&T, Rogers HTC One X, Telstra One XL] Misterowl:
^wow

Was there conflict on the thread?

Why was this thread created?
[AT&T, Rogers HTC One X, Telstra One XL] angramenyu:
The official CM development for the HOX is nearly at a stop, so in order to keep the original CM treat clean (talking CM and just CM) they have opened this one.
[AT&T, Rogers HTC One X, Telstra One XL] mayhem85:
So, I tried ViperXL today....

Wait.. Nevermind.
[AT&T, Rogers HTC One X, Telstra One XL] panda_mode:
Yeah people were starting to argue in the CM thread about small things. I think we are just really anxious lol. We will see some action eventually though. I see things are being merged in the changelong site. For now, let's sit back and relax.

Btw, it's almost Summer Break! :cool:
[AT&T, Rogers HTC One X, Telstra One XL] Arrow44:
The word there is "almost" and teachers are going nuts trying to teach us
[AT&T, Rogers HTC One X, Telstra One XL] panda_mode:
That statement is very true. I have a 2,000 word college English paper to finish by tomorrow about MSM blood donors and two tests lol. After that it'll be Summer Break for me, and hopefully some CM goodness to flash
[AT&T, Rogers HTC One X, Telstra One XL] buradd:
Ninth
[AT&T, Rogers HTC One X, Telstra One XL] PeshZgamE:
The only thing that bothers me about this ROM is the screen tearing. That's it. I know its such a small thing to care about but it bugs the crap out of me. Lol.

I tried a kernel that is supposed to help with HW Overlays disabled.. And while this fixed the tearing, I now experience freezing while on calls. Its random when it does it. But it does it enough to warrant switching back to the stock kernel. Irritating to the highest degree.

Can't wait til h8 gets everything sorted out!
[AT&T, Rogers HTC One X, Telstra One XL] darthvince:
I also cannot stand the screen tearing, and disabling hardware overlays was making my phone hot. Sticking with viper until the new kernel is ready, but I can't wait. I love AOSP way more than sense-based roms. I like it to match my Nexus 7.
[AT&T, Rogers HTC One X, Telstra One XL] jacobas92:
Same here. 'Sept I ain't got a n7. Soon as that finished 3.4 kernel drops I'm trying every 4.2 ROM we got.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
I'm not experiencing any screen tearing at all on Carbon. It's super smooth and stable. Been my daily driver for a while now.
[AT&T, Rogers HTC One X, Telstra One XL] jacobas92:
Is that with overlays disabled? If not I'll have to try it, thanks.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
No, stock standard out of the box, but underclocked to 1242mhz and super smooth :D
[AT&T, Rogers HTC One X, Telstra One XL] Arrow44:
I shall second that! No screen tearing at all and smooth for being under clocked to 1024
[AT&T, Rogers HTC One X, Telstra One XL] jacobas92:
So is this with the stock kernel? Want to try but I NEED s2w lol.
[AT&T, Rogers HTC One X, Telstra One XL] Heisenberg:
Yes that's with the stock kernel. I don't use s2w, I liked the novelty at first but the power button is good enough for me.
[AT&T, Rogers HTC One X, Telstra One XL] jacobas92:
Oh. I have a Speck case and the power & volume buttons are UBER stiff.
[AT&T, Rogers HTC One X, Telstra One XL] edditnyc:
I stopped using a case... I'm surprised I haven't cracked it but maybe that speaks to it's outstanding build quality. I might have dropped it maybe 5 times without a case? No scuffs or sign of damage at all. Just scratches on the glass but nothing major. It's also insured so you know... whatever. :)

But I'm a fan of the power button. I didn't think I would be but it's held up pretty well and isn't stiff or too worn out over the course of 11 months.
[AT&T, Rogers HTC One X, Telstra One XL] exad:
I was trying to compile cm10.1 before my motherboard died, its a bit of a mess.. Some errors in the scripts. H8 is doing a great job leaving comments and reporting fixes but the repositories don't seem to be getting fixed up.
[AT&T, Rogers HTC One X, Telstra One XL] mayhem85:
Anybody have any updates on this yet? I can't tell much from looking at the changelog for evita.
[AT&T, Rogers HTC One X, Telstra One XL] jfphotox:
Me too! It drives me up the wall haha.
[AT&T, Rogers HTC One X, Telstra One XL] mayhem85:
+1

Can't wait to see 3.4 kernel on CM10.1

Also, one question - Will the HTC One with stock android that was announced today (http://www.theverge.com/2013/5/30/4379796/htc-one-google-edition-announced-stock-android) help cyanogenmod to work around the kernel issues to run stock android on all HTC's? Does my question make sense? I have been wondering about it.
[AT&T, Rogers HTC One X, Telstra One XL] kinosness:
My radio crashes once a day, is anyone else experiencing this?

The signal icon will suddenly turn black with an outline, and nothing short of a reboot will fix it.

I've tried different radios and a full wipe but no joy.

Any ideas?

I'm on a recent Cory build and on Telstra.