yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Mini Q&A, Help & Troubleshooting] !D&L!:
when i bought it it was in the inscription but my phone clearly doesnt have it :mad:

i paid for something that i dont have

if there's some way to get it on my phone other battery of something else

let me now
[Galaxy S III Mini Q&A, Help & Troubleshooting] BelugaHval:
Doesnt help getting a batty with NFC since there are still only 3 pins on the actual phone...You would have to change the connector on the mainboard also. The phone is so cheap i hardly think its worth the hazzle...

---------- Post added at 10:06 PM ---------- Previous post was at 10:05 PM ----------

Other battery wont help. There are still only 3 connectors on the actual phone (need to be 4).

Im very dissapointed. I expected mine to have NFC.
[Galaxy S III Mini Q&A, Help & Troubleshooting] leenukes:
I'll test my wife's phone later but In sure I've sent things to her from my phone using NFC.
[Galaxy S III Mini Q&A, Help & Troubleshooting] luka_cro:
Wait, NFC chip is in battery or what?
[Galaxy S III Mini Q&A, Help & Troubleshooting] leenukes:
Just tested. Galaxy S3 Mini GT-I8190N (maybe the N is NFC?) And it works fine.
[Galaxy S III Mini Q&A, Help & Troubleshooting] luka_cro:
Yes, the N stays for NFC.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] khrystyan27:
Hi guys!

Here is yet another problem with my Galaxy Note...

Recently I've been changing/testing ROM's and after founding a good one, decided to put everything back, full charge and do a "wipe battery stats" in CWM.

I've found that wiping the battery stats is a bad thing... In the past, I've god 14-16 hours of power-on with 4-6 hours screen on time, and still got 5-10%. Now I've got a serious problem 12-14 hours power-on and only 3-3.5 hours screen on time and I'm already 1-3%.

Another problem is the phone that it's quite... possessed. After 3% battery the screen starts to flicker, the network goes from HSDPA+ to 3G or no signal and i've got a lot of LAG (i think that the processor is undervolted). Furthermore, when it drops below 1% it's instantly DEAD, no Samsung bye, bye sound, no vibration on close, NOTHING.

All those problems came after a "wipe battery stats"... What i am doing wrong? What's up with this annoying behavior?

1. I let it drain completely.

2. Charge it on the wall adapter, phone closed. (10-12 hours)

3. Boot CWM and wipe battery stats

4. Unplug charger and reboot android (normal use).

5. Let it drain completely and do another full charge.

What is wrong here? Is there any problem with my phone?

I've got an Galaxy S III, and have the same issues... after the "wipe battery stats" the battery lifetime got miserable.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Dsteppa:
What Rom are you using?

And it's not advised to completely drain your battery each time.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] baz77:
coincidence. Its not due to wiping battery stats.

http://xdaforums.com/showthread.php?t=2027505

same symptoms, see my post end of thread
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] khrystyan27:
But why both at the same time?

Before the wipe, had no such problems...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] baz77:
Coincidence. Unless you find more cases where this happens. According to pros, its a placebo anyway as it does nothing in itself.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] SpyderTracks:
Battery stats on these advanced batteries has no influence. The older batteries used purely software monitoring, the newer type has its own calibration control built in on a chip. Battery stats is only there for the older android handsets.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] khrystyan27:
I don't think this is a conincidence...

The battery was good before i wiped...
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] burtcom:
How long have you had this battery?
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] sitanshu91:
Actually this maybe correct

Because its only after i wiped my battery stats and few days later slowly battery began to bloat

This maybe a clear co incidence not sure about it
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] khrystyan27:
Phone purchase date xx.07.2012 (don't remember the exact day).

I am SURE that the "wipe battery stats" did this, but how to "RESTORE" back? Anything i did, no succes.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] 7raiden7:
No way to do that! Android just wipe battery stats every time it find out that battery is fully charged by looking at its voltage!

Anyhow, you can always let your phone discharge, turn it off and let it charge in CWM until it reaches 100%, then again wipe battery stats and you'll recalibrate the battery manually!

Inviato dal mio panetto di burro powered by JellyBAM 1.2.0 + SlimBean kernel
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] SpyderTracks:
Anytime you wipe battery stats, it'll take a couple of days to reconfigure off the batteries chips. That being said I've seen a lot of people with dud factory batteries and if it's under 6 months you can claim warranty with Samsung or whoever you bought it off.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] baz77:
also note, you probably wiped battery stats cause something was going on... anything happening after is more likely to be linked to the reason you wiped.

Anyway its a good question, cause if it has its own chip why would it need to consort with battery stats and take days to recalibrate? Then there is a dependency. Where there is dependency, there is chance of bugs.

I guess op could then be right.

However by reading Entropy and his comments on gauge and battery stats I doubt my second paragraph comment on its validity.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] chasmodo:
Wiping battery stats killing off the battery?

About the same chance as me scratching my hairy posterior, thus causing a tectonic cataclysm on Saturn.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] azzledazzle:
Isn't that a ***** ! I hate it when that happens :silly:
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] khrystyan27:
No... no issue, i just wiped the battery stats after installing a new ROM (i read many times that is strongly recommended to do this after a flash).

Suddenly, the next day i saw that it has a poor life, MUCH poor than before i did the wiping.

I don't think that the battery is damaged, i think this is a kind of battery level bug (it miss reads the information from the internal voltmeter).

Same **** with my Galaxy S III (10-12 hours power up with 2 hours screen time)

For me... I'm starting to regret the turn from iOS to Android... :(
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] chasmodo:
We are starting to regret it, too...

Sent from Nexus 7
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] baz77:
lol.

actually that could very well be the case, as it takes couple of days to get more accurate readings again :)

something to do with gauge. Entropy had a post about that a while back explaining just what you are seeing.

lol I see what you did there :)
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] Wongkonka:
Gt-n7000/gt-s5670

Hey there, I've had the same problem with my N7000 battery. I've wipe battery stats and saw more devalued performance from the battery. Until finally I saw flickering of the screen before the phone "passed out"...without firstly powering down. Since then any attempt to charge or use the phone results in continual decreasing periods of use before passing out again, until finally nothing happens.

However when the phone is plugged in to charge. The battery icon comes one without and problem and proceeds to charge. The icon will say the phone is fully charged but it still cannot turn on, even to try to deplete the battery. I also attempted to put the phone in download or recovery mod and leave it there to try to use all the power after going back to check the phone after 15-30 minutes, I found that it either turned itself off by powering down, or simply turned off...I've since ordered some new batteries from Hong Kong, for only a few dollars...We'll see if they even work.

Thought I'd put in my scenario also.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] nokiamodeln91:
Yeah. It seems to be the the battery problem.
[Galaxy Note GT-N7000 Q&A, Help & Troubleshooting] capitansid:
This is what killed your battery

2. Charge it on the wall adapter, phone closed. (10-12 hours)

That's what killed your battery.. Now I know most people will dispute my statement on this.. But do some quick research on this (Dr. Google is your friend).. And I have verified it with my local Samsung Service Center..

Li-ion/Li-polymer or any other battery of that kind MUST NOT stay at full potential (full charge) for a long time because ion Migration will occur and that slowly kills your battery.. It is better to charge your battery more frequently between 20-85% approx and not keeping it above 90% for a long period.

I killed my battery this way.. I kept my phone plugged in overnight.. and in a matter of 4months, It just quit on me.. Wont even turn on when not plugged in!
[Eee Pad Transformer Android Development] fallenangel1978:
HI I JUST ROOT MY TF101 WITH 9.2.1.27 FIRMWARE

ok there are plenty hot to root asus stock firmware but not easy for everyone

so what we need

DOWNLOAD...

1.LATEST ASUS FIRMWARE

http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download

2.EasyFlasher

http://xdaforums.com/showthread.php?t=1688012

3.Harmony Kernel for stock asus ics (RaymanFX)

http://xdaforums.com/showthread.php?t=1693799&highlight=harmony

4.supersuser for CWM

5.APX Drivers

6.BusyBox Installer free from google play

https://play.google.com/store/apps/...DEsImNvbS5qcnVtbXkuYnVzeWJveC5pbnN0YWxsZXIiXQ..

put harmony kernel and superuser.zip in externel sd card

EXTRACT easyflasher in any directory(in PC) and put inside "EasyFlasher-0.8.3b-STABLE\asusupdate"

the latest asus firmware

(EasyFlasher-0.8.3b-STABLE\asusupdate\WW_epaduser9_2_1_27UpdateLauncher)

then put tf101 in apx mode(+button and shutdown)if asks for drivers use the APX drivers.

nvflash the firmware,then let it boot....shutdown the tf101 and put it again in nvflash mode.

install RogueXM Touch v1.5.0-R1 and reboot in cwm

flash harmony kernel and then the superuser.zip (no need to wipe anything)

reboot and download from google play the busybox installer and update superuser

open busybox installer (give root rights) and from menu install latest busybox 1.20.2,sqlite3,zipalign etc

THATS IT :laugh::laugh::laugh:

it worked for me(WW version--SBK2 B80) but im not responsible if you brick your tf101

use at your own risk
[Galaxy Note II Android Development] Phil3759:
Main thread + features + install instructions + dev support

http://xdaforums.com/showthread.php?t=2201860

PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM

It is a well proven recovery for many phones

It also adds a full touch interface a completely configurable GUI

Please give your feedback, what works, and any bug you could encounter

Read the features, and check if you are missing something

Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut

Download links

Last version can be found here:

XDA:DevDB Information

[n710x/T889][CWM Advanced Edition] PhilZ Touch, Tool/Utility for the Samsung Galaxy Note II

Contributors

Phil3759, amit.bagaria

Version Information

Status: Stable

Current Stable Version: 6.46.3

Stable Release Date: 2014-06-18

Created 2014-06-11

Last Updated 2014-06-18
[Galaxy Note II Android Development] Phil3759:
Recovery (.zip) packages instructions

They come in the form of .zip files that can be flashed in cwm recovery

Download philz_touch_xxx.zip file

Put the previously downloaded philz_touch_xxx.zip file on your sd card

Boot into recovery (volume up+home+power)

Select "Install zip" and browser to your downloaded zip file.

Now select the philz_touch_xxx.zip fileyou copied in previous step

You will have PhilZ Touch Recovery flashed

Odin packages instructions

They come in the form of .tar.md5 file

boot into download mode

start odin3 and configure it as in picture below

connect phone in download mode to PC via USB

press start to flash the tar.md5 package

normally, phone should auto-reboot into recovery.

If it reboots into android and your recovery remains stock, repeat above steps and untick "autoreboot" in odin. Once flash is done, keep pressing power button until it reboots (normally will go to recovery)

when in recovery, if you choose option "reboot system now" and you get "yes - disable flash recovery", select that option to avoid stock recovery overwriting cwm

<< Root your phone and reset Yellow Triangle >>

Once in recovery, flash the attached Root_SuperSU.x.xx.Only-signed.zip file to root your phone

If you want root + busybox: flash Root_SuperSU.x.xx-Busybox.1.20.2-signed.zip file

to remove yellow triangle, use TriangleAway

Download links

Last version can be found here:

Older version:

v4.92.8

v4.91.2

v4.87.6

v4.87

v4.64

v4.63

v4.35

v4.31

v4.01

v3.99 (repacked with XXDLL7 Kernel, supposed to be SDS fixed)

v3.81

http://www.mediafire.com/file/tghwcf3i1d0hi31/philz_touch_3.81-n7100.tar.md5

http://www.mediafire.com/file/y24i2g784sw7cy1/philz_touch_3.81-n7100.zip

3.65R3

http://www.mediafire.com/file/1hx15fi9h5k7lex/philz_touch_3.65R3-n7100.tar.md5

http://www.mediafire.com/file/huv878rrikj41g7/philz_touch_3.65R3-n7100-XXALJ1.zip

v3.65 / 3.65R

special debugging versions, links removed

v3.43:

odin: http://www.mediafire.com/file/8dh3quut8te7pq2/philz_touch_3.43-n7100.tar.md5

cwm: http://www.mediafire.com/file/b1ahq1373q70d07/philz_touch_3.43-n7100.zip
[Galaxy Note II Android Development] Phil3759:
Before asking for support:

Request a build for a new device:
[Galaxy Note II Android Development] brolee93:
great after NOTE 7000 you have and port your best recovery to NOTE 7100 i like your work thanks very much my bro :)
[Galaxy Note II Android Development] Phil3759:
Thank you (out of my 8 thanks today)

You missed intermediate port to i9300: thanks to the feedback there, and dr.ketan for n7100, I could port it here final, no beta private testing first, and hopefully bug free

Waiting for any detailed feedback if some features are not working as supposed, or even if they do work properly, so we know it

dr.ketan tested nandroids and exfat support

I will add zip files to flash in cwm later
[Galaxy Note II Android Development] Nyto75:
Thanks a lot for this awesome work ! I miss touch recovery soo much :)

And thanks for the really clear thread
[Galaxy Note II Android Development] darni:
Where is the download for the flashable zip?
[Galaxy Note II Android Development] carcassudo:
x2
[Galaxy Note II Android Development] rs200z:
Does this work on the N7105 LTE model too?
[Galaxy Note II Android Development] Crash:
Welcome philz nice to see you here mate

Sent from my GT-N7100
[Galaxy Note II Android Development] Nyto75:
Phil just told 2 post above that he will post it later :)
[Galaxy Note II Android Development] dr.ketan:
Here on Note2 Flashable zip have no extra benefit, as counter will raise once you have custom recovery.

Still in case if you dont have PC availibility, you can use Mobile odin and flash it for recovery tab in mobile odin.
[Galaxy Note II Android Development] The_Steph:
dr.ketan,

Your answer is true for the first time you flash custom recovery but once you have done it (and you can do it without incrementing the counter as I did it with the toolbox), it soooo easy to put a file on your note and flash with CWM feature.

And I assure it would not be so difficult to have his wopnderful recovery presented under this format.
[Galaxy Note II Android Development] Phil3759:
As answered above, I will add this later, when back to home
[Galaxy Note II Android Development] dr.ketan:
And Phill it is not good idea to include SuperSu and busybox in same package of .tar rather thn flashing it separately?
[Galaxy Note II Android Development] mzakirh:
Welcome to Note 2 Phil:D
[Galaxy Note II Android Development] Phil3759:
Here's the zip version, you can flash in cwm

http://www.mediafire.com/file/b1ahq1373q70d07/philz_touch_3.43-n7100.zip

Check PM
[Galaxy Note II Android Development] mariuano:
Welcome king ;)

Philz cwm. Zip?

Edit thanks!!!!

Inviato dal mio GT-N7100 con Tapatalk 2
[Galaxy Note II Android Development] dr.ketan:
Got it

Thanks
[Galaxy Note II Android Development] Phil3759:
Have a question for you:

Do you like the bottom virtual buttons or you find them a bit flat from top to height? I can fix this and gives them the proper size if needed
[Galaxy Note II Android Development] mijnie:
Nice work again. I've been waiting for this one. Thanks!!!
[Galaxy Note II Android Development] jitin02:
My last nandroid (on internal card) was approx 1Gb with all needed apps installed. how much more space it needs???

and btw, do backup to extnl sdcard works??
[Galaxy Note II Android Development] Phil3759:
Of course it works. Blobs can use a lot of space at start. Try tar, get free space and report back after that
[Galaxy Note II Android Development] jitin02:
Just got me 32gb class 10 last night.

Will try today and will report bak

Swiped from my Beast Gnote2
[Galaxy Note II Android Development] hayabusa08:
Hi. Can i flash the odin file using mobile odin pro?
[Galaxy Note II Android Development] dingokevin:
I tried with mobile and it did not flash I reset my phone and was stuck in a boot loop had to flash a recovery with the desktop Odin

This PSA was sent Flow style from my Note 2 N-7100
[Galaxy Note II Android Development] viruz82:
Thanks for the update, Phil - no more /preload errors. :D

But now I have the problem that flashing raubkatze's theme runs in a timeout. I'm unable to flash it with your v3.8.1 recovery. :(

Flashing it with Chenglu's it works fine...
[Galaxy Note II Android Development] Phil3759:
That's strange as even early releases did work fine under mobile odin. And for me it does work but I use the older revisions as I got many issues with new versions (not sure if they are fixed by this time as I quiet never use mobile odin). There is also a zip version you can flash in recovery. Also, if you were on some other recoveries, mobile odin can fail. But since mine is rather a stock cwm based, it should work

Well, I looked at his script. First, the unpack is in /sdcard

show_progress(1, 15);
run_program("/sbin/busybox", "mount", "/system");
package_extract_dir("vrtheme", "/sdcard/vrtheme");
set_perm(0, 0, 0755, "/sdcard/vrtheme/installtheme.sh");
set_perm(0, 0, 0755, "/sdcard/vrtheme/zip");
set_perm(0, 0, 0755, "/sdcard/vrtheme/cleanup.sh");
set_perm(0, 0, 0755, "/sdcard/vrtheme/zipalign");
ui_print("modding files...");
run_program("/sdcard/vrtheme/installtheme.sh");
run_program("/sdcard/vrtheme/cleanup.sh");
run_program("/sbin/busybox", "umount", "/system");
run_program("/sbin/busybox", "umount", "/sdcard");
ui_print("mod complete");

But as you see, it doesn't mount /data or /sdcard. My recovery acts as stock and /data is not mount at start, neither /sdcard I think

What I would need to look at it:

- in recovery, manually mount /sdcard and /data through recovery mount menu

- install your zip

- if it fails, give me the exact screen output before and at failure point

- In advanced menu, use the report error menu which copies log files to your /sdcard/clockworkmod folder

- post log files here
[Galaxy Note II Android Development] hayabusa08:
Well thanks for the fast reply but i just have to test it while waiting for the reply. Lol. Hanged while attempt to reboot into recovery. Did a battery pull with no issues but still on stock recovery. I guess i have to use a pc shortly when i reach home. Thx again.
[Galaxy Note II Android Development] sunwee:
so far so good, exfat mounts alright and aroma works.

but i notice that booting into recovery takes quite a bit. since i am on redpill kernel, i asked pongster about this and this is his comments

http://xdaforums.com/showpost.php?p=35678802&postcount=1198

extract: "Ask Recovery makers to stop flashing a new sensorhub version. I use TWRP and can boot into recovery much faster than any other available at the moment."

perhaps you can have a look at this, Phil?
[Galaxy Note II Android Development] Phil3759:
Asked him there what does he mean. I do not flash any thing special. This is stock cwm
[Galaxy Note II Android Development] Phil3759:
Well,

Maybe I won't get an answer it seems. In any case, my recovery is stock base cwm. That is cm10/aokp compliant and also with stock Samsung kernels and ROMs. Many are getting that issue with cwm even Chenglu build which is even more close to stock than mine. All reports concern third party kernels.

Now, up to a dev to chose: fix his kernel to make it compatible with cwm (major part of custom recoveries) and TWRP (great recovery but lower target) or to live with bugs making it incompatible with one of them.

As you know, I am open to fix reported bugs and revise my code/changes for that, but won't do for other kernels. Either the dev fix their kernels or you decide to live with the issue, or leave one of the 2 conflicting elements. Now if a kernel comes with an embedded recovery, it could be better you live with the embedded one if you really like the kernel especially if kernel dev added custom changes to the recovery like Siyah does
[Galaxy Note II Android Development] pongster:
I just saw this. Please check AndreiLux github and see the sensorhub commit he made way back. The long boot time is probably due to the Sensor hub firmware being flashed every time you boot into recovery. If you're using stock kernel as base, they may have that enabled.
[Galaxy Note II Android Development] Phil3759:
Thank you. In that case I cannot do anything as I do not plan to compile kernels from source. Using cm10 or other kernels will break exfat and aroma. I am tempted to look at twrp sources to see how they did add native exfat support without extra modules
[Galaxy Note II Android Development] Phil3759:
Discussion continues here

http://xdaforums.com/showthread.php?p=35721387#post35721387

Hopefully we could debug it
[Galaxy Note II Android Development] Gillion:
I told you recovery took long to boot... but you ignored ... sigh.
[Galaxy Note II Android Development] nyarnon:
Phil is doing a great job really.

--

Sent from my N7100 with

Kernel: Perseus 29.1 ARHD

Rom: Android Revolution HD 6.0

CWM: philz_touch_3.81

Thanks too the devs and teams.
[Galaxy Note II Android Development] Phil3759:
Yes, but for custom kernels, so not all related to me... any way, if people give feedback and support, I will to look at it. Can people on the new stock 4.1.2 DLL2 say if it is slow at boot or normal?
[Galaxy Note II Android Development] shoey63:
Is it hot booting? Cold boot takes ages :(
[Galaxy Note II Android Development] Phil3759:
Yes need more info:

- Boot from stock kernel is slow or normal?

- Exact kernel version on all is normal and on which is bad

- Is it only slow on 4.1.2 kernels?

- is it ok on new DLL2 stock?

Nice to see you here. Hope you got an n7100 as you are one of my star testers :)
[Galaxy Note II Android Development] simplelife:
T889 4.1.2 rom with Note2 core kennel , boot into CWM normal ( no slow) , flash , backup ..etc fine but when try to restore pop up mismatch MD5.

I change to stock T889 kennel with same base 4.1.2 rom then try to backup and restore go through.

All test did with Ex Fat32 sdcard , will test with Exfat 64 when I'm home.

Awesome job, Phil.
[Galaxy Note II Android Development] Phil3759:
Thank you for the feedback. At least a custom 4.1.2 kernel being fast, but seems they have broken exfat support as pongster suggested. It seems many 4.1.2 custom kernels are failing. Maybe because of them not having yet the needed sources from Samsung. I will repack the recovery with other stock kernels, mainly new LL2 . I would appreciate a feedback and comparative tests under redpill and other kernels having issues