yashsingh1/xdaforums huggingface dataset:
[G2 Q&A, Help & Troubleshooting] maydayind:
not an expert but lipo cells are charged individualy and needs to be in balance maby that's why. all lipo have this issue and have som time the need to be balanced don't know I f the phone do that automatically...

just a idé don't know if that's the issue
[G2 Q&A, Help & Troubleshooting] garywojdan81:
If you monitor the rate at which it's drawing charge once it nears 100%, you'll see it slows considerably but doesn't stop all at once. Its much more accurate to use the actual voltage to monitor charge. Gsam or android tuner do a pretty good job of that.
[JAM, MDA Compact, S100 General] ronski:
I posted this in the BT thread, but no response. Maybe this will do. Hope someone can help me out

I read the same in a couple of posts for the new BT stack: I got the patch, installed it, request comes where to install, tried several places, nothing seems to happend (also after reset).

Also, sound is gone now. No ringtone, voice and music playback. There was a thead that discussed the same problem, but no solution other than hard-reset.

bt stack: BCHS_FOR_POCKET_PC_OZONE[1].ARMV4

I got the 1.13WWE/1.12R ROMs

tanx!!
[JAM, MDA Compact, S100 General] derliebewolf:
Backup?

What about backups? the author recomended to backup your ppc bevor trying. I did so and was happy about that! This Stack did not work on my magician. nothing changes except the mentioned problems appeared...

But regarding your Question: I think there are two ways of getting rid of this porblem:

1) Hard Reset

2) Install a backup

I know this is not the answer you hoped to receive...but it is what i encountert :evil:
[JAM, MDA Compact, S100 General] ronski:
backups? what's that? :lol:

Yeah, I know, didnt make a recent one, so I'm the one to blame :cry: , but I read a post somewhere that restoring a registry backup did the job and the sound was back again. So, what's different between the faulty registry and the good one??
[JAM, MDA Compact, S100 General] xtian63:
TCPMP problem with BT stack

wen u press the power button to go sandby mode the audio on tcpmp disappears
[JAM, MDA Compact, S100 General] heretic:
Go to the "Audio" tab in Bluetooth settings (manager) and uncheck the "Automute" checkbox. That should be enough.
[JAM, MDA Compact, S100 General] ronski:
I wish I could, but there isnt an extra tab which has that option :(
[JAM, MDA Compact, S100 General] heretic:
Then your installation is probably faulty... I guess, the only option is to unistall and reinstall, which I think cannot be done without a HR. Sorry...
[JAM, MDA Compact, S100 General] ronski:
I'm afraid that is the only option left, the problem occurd after the installation of the new BT stack: BCHS_FOR_POCKET_PC_OZONE[1].ARMV4

it asks for an installation target, but none seems to work, though files are installed and registry is changed (I see the new files in some entries), I see no new options in the BT menu
[JAM, MDA Compact, S100 General] ronski:
PROBLEM SOLVED!

I solved the problem!!!!

First, I used this in registry to disable the installation target request of the CAB file which does the BT stack installation:

http://www.pocketpctweaks.com/pocketpc_tweaks/force_install_location_prompt.html

Second, I installed the BT stack again

Third, I have al the options!!!!! disabled the Automute, but still no sound :(

Fourth, I use my labtop as a headset, connected, dailed, and got sound on my labtop!! Disconnected, turned up the volume, AND VOILA!!! SOUND!!!

:D happy I am, no hard reset needed :D
[JAM, MDA Compact, S100 General] rustoss:
& also see this

http://xdaforums.com/viewtopic.php?t=29219
[Upgrading, Modifying and Unlocking] Yves Laroche:
Hi all,

I've found that the file system.ext4.win can have a different size when saved to a subfolder when compare to the folder /storage/emulated/0/TWRP/BACKUPS. Here I'm talking about the Create Nandroid Backup feature. It seems that the pulling process don't work well or at least don't really compare the saved files. Sometime, the pulling process only retreive 9 files instead of 11. I'm using the latest 1.7.9 version.

BTW, I can retreive all files from my Nexus 4 via an FTP client (FileZilla) and all files are exactly the same size.

Thanks,

Yves
[Upgrading, Modifying and Unlocking] Yves Laroche:
Installed the latest version 1.8.0 but got the same problem. Only nine files were pulled instead of eleven. Using FileZilla FTP client retrieve eleven files from the phone.
[Nexus 5 Q&A, Help & Troubleshooting] kurtyyyyyy:
So far I have tried cyanogen and cataclysm.

Not happy with customisation options.

Any suggestions?

Edit:

Like to customize status bar heavily but most importantly the nav bar. I like to have menu at left, home in middle, and back at the right.
[Nexus 5 Q&A, Help & Troubleshooting] rlillard:
It might be a good idea to say what it is you want to customize.
[Nexus 5 Q&A, Help & Troubleshooting] Gormsen:
First of all: Does this really belong in the general section?

Second: Rom comparing threads are against the rules.

Third: Why don't you flash some of the Roms that offer a lot of customizations, there are a lot of them, both in development and original development. Don't get lazy just 'cause you've tries two Roms.

Fourth: Android 4.4 is still pretty new, and devs are working their asses of trying to bring you and I great and rich features, show them some respect in stead of acting like a spoiled little brat!

Sorry for outburst, but that's just my 2 cents..
[Eee Pad Transformer Q&A, Help & Troubleshooting] Deleted member 4463645:
I have a TF101 and am installing KatKiss on it, but I don't know if I should enable fsync or not. I read that it improves data integrity at the expense of a large speed drop. Is it enabled in the official Asus ROM, and most other custom ROMs for TF101, and ROMs in general?
[Eee Pad Transformer Q&A, Help & Troubleshooting] wn1ytw:
As stated in the OP fsync is off by default. if you want it flash fsync=on.zip - I believe after the ROM .. maybe after GAPPS. BTW I always flash it whenever I flash a ROM and I keep my overclock to 1200. I know others go to 1400 but I keep it down.

good luck whatever you decide.
[Eee Pad Transformer Q&A, Help & Troubleshooting] Deleted member 4463645:
asdf

So fsync is off by default in all roms, not just this one?
[Eee Pad Transformer Q&A, Help & Troubleshooting] mrg2003:
fsync

I tried it on / off.

I prefer off. No problems so far.
[Verizon Samsung Galaxy S 4] Surge1223:
Please

DO NOT flash a recovery, modem, or rom without backing up your current ones! There's no way to retrieve/restore those files. IF YOUR ON ANY BUILD OTHER THAN OYUAMDK PLEASE LET US KNOW!

Its come to my attention that OYUDMI1 and OYUEMJ7 builds are in the wild.

BACK UP SCRIPT

: Run in Terminal Emulator and zip the output

su
mkdir /mnt/sdcard/backup
dd if=/dev/block/mmcblk0p1 of=/mnt/sdcard/backup/NON-HLOS.bin
dd if=/dev/block/mmcblk0p2 of=/mnt/sdcard/backup/modem.bin
dd if=/dev/block/mmcblk0p3 of=/mnt/sdcard/backup/sbl1.mbn
dd if=/dev/block/mmcblk0p4 of=/mnt/sdcard/backup/sbl2.mbn
dd if=/dev/block/mmcblk0p5 of=/mnt/sdcard/backup/sbl3.mbn
dd if=/dev/block/mmcblk0p6 of=/mnt/sdcard/backup/aboot.mbn
dd if=/dev/block/mmcblk0p7 of=/mnt/sdcard/backup/rpm.mbn
dd if=/dev/block/mmcblk0p8 of=/mnt/sdcard/backup/tz.mbn
dd if=/dev/block/mmcblk0p20 of=/mnt/sdcard/backup/boot.img
dd if=/dev/block/mmcblk0p21 of=/mnt/sdcard/backup/recovery.img

HELP RAISE AWARENESS! Comment and +1 Bean's post here

Samsung and Verizon are intentionally screwing over Dev owners and Development in general, this needs to get out to the public!

http://www.reddit.com/r/Android/comments/1tl22o/samsung_officially_developer_unfriendly_witholds/
[Verizon Samsung Galaxy S 4] FernBch:
+1'd
[Verizon Samsung Galaxy S 4] Surge1223:
I know Samsung is ridiculous.
[Verizon Samsung Galaxy S 4] jamesd1085:
+1d...is this good news...dev version mj7 I mean
[Verizon Samsung Galaxy S 4] HTCluva:
Can't you just Odin that mj7 package?
[Verizon Samsung Galaxy S 4] Surge1223:
I wouldnt want to take the chance of locking bootloader
[Verizon Samsung Galaxy S 4] HTCluva:
I'm already on mj7 with the retail s4 on safestrap. Isn't that what you're talking about?
[Verizon Samsung Galaxy S 4] Surge1223:
This is directed toward dev owners but its important retail owners are aware because currently there is no backup of the OYUEMJ7 modem, who knows how well it might've worked?
[Verizon Samsung Galaxy S 4] markwebb:
So where are these build for us Dev owners? What can we do? Or with the script you are waiting for someone to come forth with them?
[Verizon Samsung Galaxy S 4] Surge1223:
Ive talked to some other devs, im pretty sure that I can maje you an odin tar for mj7 using the dev mj7 kernel, not sure if a mk2 tar would completely work or not
[Verizon Samsung Galaxy S 4] markwebb:
Cool am on the original Dev build. But I don't want to lock the boot loader like I did the first time around but luckily then was still in return window which is not the case 5 months later. :)
[Verizon Samsung Galaxy S 4] Surge1223:
No one said anything about updating the bootloaders :) just the kernel (to a newer kernel, plus its 4.3) , system and cache. Wouldnt touch aboot, sbls, or recovey
[Verizon Samsung Galaxy S 4] equake:
This would help to run safestrap on the device for mj7 and mk2.
[Verizon Samsung Galaxy S 4] Surge1223:
Are you asking or telling? lol
[Verizon Samsung Galaxy S 4] SamuriHL:
Wait...why not?? What do you mean there's no backup of the MJ7 modem? Do I need to come create a signed modem ODIN package for you guys? :D
[Verizon Samsung Galaxy S 4] equake:
Both the MJ7 and MK2 modems from the Consumer Edition have been posted. The Developer Edition has never seen its Images come up anywhere.

My 2 cents.
[Verizon Samsung Galaxy S 4] SamuriHL:
Yea, I read too quickly. There's no OTA for this MJ7 build. It seems to be shipping on new DE's. Come on, Samsung! Get with the damn program here. At least with an OTA I can make the signed modems and recovery. Although, what's the point of recovery if there's no OTA?!?! The DE's really got screwed here. :(
[Verizon Samsung Galaxy S 4] livinginkaos:
Ya think?
[Verizon Samsung Galaxy S 4] Chris123NT:
It's all part of the plan guys, Verizon is trying to get rid of developers and Samsung has become their lap dog. Lack of support for dev devices will eventually drive people like us to other carriers and brands. So Samsung will get what's coming to them in the end if they keep going down this road. Motorola learned the hard way and they did a 180 because they realized they NEED devs. Who does samsung think recommends their devices? People like us lol.
[Verizon Samsung Galaxy S 4] orlyowl11:
This came with the new S4 Verizon DE I ordered last week from Samsung and I provided the details to Surge. Unfortunately I had stupidly already tried to flash the OYUAMDK .tar originally compiled by him, and it overwrote the baseband version shown in that screenshot originally to I545OYUAMDK from the original I545OYUEMJ7 that it came with. This attempt, while succeeding for the baseband version, did not actually update other details of the phone to OYUAMDK, so it appears as of right now from what I know, it isn't possible to downgrade even a developer edition phones firmware from 4.3 OYUEMJ7 to 4.2 OYUAMDK...

The device came with 4.3 / Knox installed, as well as the flags seen on consumer versions when you do actually get into Download/Odin mode with KNOX WARRANTY VOID: 0x1 flagging now too after I originally flashed CWM via Odin.

Was unable to install any AOSP ROMs on it too, which was interesting and something I know Surge is looking into after I provided the remainder of the OYUAEMJ7 files with his script listed on post #1. This was even with trying to install a new kernel (tried KT) after flashing, and additionally trying to flash the original dev_modules.zip that is listed in that 60-70 page thread for all things related to the S4 Dev edition.

Because of that, I've since initiated a return to Samsung, as I thought with the DE I would have no issues getting an AOSP ROM installed and running with the unlocked bootloader. As that is now shown to not be the case, at least as of right now, I'm just sticking with the consumer Verizon S4 for right now. Am contemplating returning that too as I'm still within my 14 day return window and going with something easier to work with like the HTC One or LG G2.
[Verizon Samsung Galaxy S 4] SamuriHL:
I don't disagree. It's why I bailed on VZW earlier this year and went with a truly open S4 GPE. However, even that is somewhat of a red-headed step child. We at least get updates, but, ODIN images? Nope. Not a chance. Moto has realized a lot more than people understand and have stared to post their recovery images. Samsung could learn a LOT from what Moto has done in the past 2 months. Samsung needs to understand the value behind the dev community and how they can use it to drive sales. This kind of stuff doesn't help. I sincerely hope you're able to pull the images and get this onto older DE phones. But they won't be signed which will potentially cause problems down the road. UGH.
[Verizon Samsung Galaxy S 4] Chris123NT:
You couldn't get an AOSP rom to flash? Or it wouldn't boot?

Wondering if AOSP doesn't like the newer firmware.
[Verizon Samsung Galaxy S 4] orlyowl11:
It wouldn't boot. The ROM flashed through either CWM or PhilZ Touch (as it's a non-loki'd bootloader and such from what I've read, I tried through that as well) and PA gapps said it detected a 4.4 ROM when flashing too... Booted to the Samsung Custom (with unlocked lock) screen, and then after that, just black screen. No boot after that. Let it try though for a good 15 minutes once, and device got really warm, so was still on, but nothing showed up after that. Assuming it's similar to current setups with newer firmware and root + safestrap type access not being able to boot non-TW style ROMs from the limited guess... (I did not actually try any 4.2/4.3 AOSP ROMs either in case you were wondering--just latest 4.4.2 CM nightly version)

Additionally, something that was interesting, I was unable to actually flash TWRP as a recovery either (tried 2.5.0.2 "stable" as well as latest 2.6.3.0/1) after using that .img to .tar converter to be able to flash through Odin. This is how I was able to flash both CWM and PhilZ touch. Whenever I flashed TWRP though, it failed to boot at all and put me back into Download/Odin mode. I also tried the other route of installing via flashable .zip from both CWM and PhilZ Touch. Same thing happened when trying to boot back into recovery after flashing, failed to boot and put me in Download/Odin. I also tried it from GooManager app from the base 4.3 stock rom that comes on it. Said the recovery installed with the script, but after reboot, did not boot to recovery (device still would boot the stock 4.3 rom after all these attempts too--just not get to recovery)
[Verizon Samsung Galaxy S 4] Chris123NT:
It's not the bootloader blocking you, the kernel is more than likely puking because of the newer firmware, since CM has nothing newer than MDK to work with since MDK is the latest for VZW retail phones that can be "unlocked".

Tell samsung you want a dev phone with MDK on it.

If you still have the phone, try to see if you can get a log of the bootup or see if it's generating a kmsg that you can pull out via recovery, might give a clue as to why the kernel is tanking.
[Verizon Samsung Galaxy S 4] orlyowl11:
I tried that with support through Samsung yesterday after providing Surge with all of the backups of OYUEMJ7 that I did still have... They said that the firmware version I545OYUAMDK was "not yet approved for installation on this developer edition device, and that I545OYUEMJ7 was the latest firmware release". Tried explaining that MDK originally came with the developer edition devices--after a few minutes on hold--they then asked me if I was referring to I545VRUAMDK...sigh. After explaining the difference that that was a consumer edition firmware release, they then pulled the "you must contact your carrier for support" line.

So...just returning it entirely, as I'm still within original 14 day window to return for whatever reason I want.

edit* Also--I do still have the phone, but honestly wouldn't know how to actually get a log of that bootup. I'm savvy enough to be able to root, unlock, flash, recover from soft bricks, and generally understand what is going on, but had to be walked through the other steps by Surge to get what he needed. Additionally, ever since I flashed the OYUAMDK .tar Surge posted, the baseband version is stuck at I545OYUAMDK, and won't update even when trying to flash I545VRUEMK2 or any other released modems... WiFi doesn't work on it in its current state with that baseband version. So...yeah...thinking it's best to just return it at this point. Tried and failed.
[Verizon Samsung Galaxy S 4] equake:
I don't believe any of the TWRP or Philz or other Custom Recoveries are built with the stock 4.3 Kernels in mind so one does not expect it to boot correctly. I'm surprised Philz even worked (maybe partially). That is why Hashcode only recently have Safestrap in Beta for MJ7.

My 2 cents.
[Verizon Samsung Galaxy S 4] Chris123NT:
Ah ok, hopefully they don't give you any crap about tripping the knox fuse.
[Verizon Samsung Galaxy S 4] orlyowl11:
I hope not as well... Although I indicated when I returned it that the reason for returning was the firmware/it coming already with Knox, we'll just have to wait and see. I wouldn't be surprised if they tried to drag their feet and say that knox fuse was tripped that because of that the warranty was voided or whatnot, in which case I'll just try the charge back route. Is what it is for right now.
[Verizon Samsung Galaxy S 4] Skeetch79:
If I can be of any assistance I would love to help. I had a clean I545OYUEMJ7 Device which I rooted with VRoot, then replaced the Chinese superuser with SuperSu. I proceeded to pull anything and everything from it
[Verizon Samsung Galaxy S 4] orlyowl11:
I think Surge would probably be the one who would want those...especially the modem See post #1 for what he had asked for and scripts to backup (although it appears you already did that), so can you upload anywhere to share?

Also--I see though that you used VRoot to actually root the device. I was able to root mine originally by just flashing the SuperSU.zip in CWM after flashing CWM via Odin and it worked fine on 4.3-I545OYUEMJ7/stuck through reboots. Have you attempted to flash any other ROM that is AOSP based and actually get it to work? Or have you flashed a custom recovery like cwm/philz touch/twrp at all?
[Verizon Samsung Galaxy S 4] Skeetch79:
I can surely contact Surge.

I used VRoot (now I would use saferoot) but I was skeptical about the whole Chinese Superuser thing. I wanted stock recovery intact. By flashing CWM then SuperSu I wouldn't be able to grab the stock recovery partition in case I needed it. I tried flashing TWRP but my phone would only boot to download mode, never back to 4.3 - hence proof why capturing the stock recovery was a good idea. I flashed the stock recovery back then used the latest Philz Touch (6.00.8 or something like that). Philz seemed to work. I have not loaded any ROMs yet, but I do have CM 11.0 ready to go. If I need to recover my device I have all partitions to do so. I made an ODIN flashable tar file using boot, recovery, modem and system as a basic emergency restore. I could always create a more robust ODIN tar if, god forbid, I really needed it.
[Verizon Samsung Galaxy S 4] orlyowl11:
I sent him an update with your post too. Glad you did the route you did though to get everything stock intact hopefully. Do you have a link for that ODIN flashable tar file for a basic emergency restore hosted anywhere? I'd certainly like to try on mine...as again...my modems are now OYUAMDK. Let me know how CM 11 goes for you though...I never got it to boot and had the same issue with twrp only booting to download mode after flashing as well. Only CWM + PhilZ worked for me.
[Verizon Samsung Galaxy S 4] Skeetch79:
I am not hosting that ODIN image yet for certain personal reasons. But I can create an ODIN flashable file for you using my Modem files. Give me a little bit to create it then I will get back to you.
[Verizon Samsung Galaxy S 4] Chris123NT:
If you could try to flash a CM based ROM and see if it boots that would be helpful to see if it's a widespread MJ7 firmware issue.
[Verizon Samsung Galaxy S 4] orlyowl11:
Yeah modem at very least would be great. Asked for the others because when I flashed Surge's OYUAMDK .tar I honestly am not sure what else may have been overwritten. Thanks in advance!
[Verizon Samsung Galaxy S 4] equake:
Isn't the Consumer Ed MJ7 Modem the same as the Dev Edition? My Dev Ed is now on MJ7 Modem and no issue. Mind you I'm on stock OYUAMDK.
[Verizon Samsung Galaxy S 4] orlyowl11:
No the baseband version for consumer is I545VRUEMJ7 , different from the developer edition I545OYUEMJ7 , as far as I know.

Have no idea performance wise if they're the same or even similar, but definitely show as different in About phone details.

Additionally, I've tried flashing I545VRUEMK2 without success. Stuck at I545OYUAMDK w/ an I545OYUEMJ7 overall device.
[Verizon Samsung Galaxy S 4] Surge1223:
Sorry just woke up, ill see if I can grab that modem from sketch, and build you guys an odin image. I already edited the firmware to be signed. (So signed in fact, that now im on the dev kernel :) see image below)
[Verizon Samsung Galaxy S 4] equake:
I understand the Cons. Ed build is *VRUxxxx and the Dev Ed is *OYUxxxx but its no point in getting the Dev Ed MJ7 Modem other than to recreate a partial backup of all Dev Ed partitions.

The ODIN image that Surge created is commendable but its still only half baked.

More important is the stock bootloader and the recovery images from the the latest Dev Ed. MJ7.

My 2 cents.
[Verizon Samsung Galaxy S 4] Skeetch79:
I have both the stock bootloader (boot.img) and recovery (recovery.img) from the latest Dev Ed MJ7 build. I have all partitions actually. The only partition that is compromised is the system - compromised in that it has Su/busybox/SuperSu installed. That is the only modification.
[Verizon Samsung Galaxy S 4] SamuriHL:
I'd love to learn how you did that if you're willing to teach. AFAIK it involves figuring out the correct number of bytes to extract if I'm not mistaken.
[Verizon Samsung Galaxy S 4] Skeetch79:
I am going to install CM 11.0 nightly. I am going to leave GApps out. I will report back. I simply did a Wipe Data/Cache - Factory reset within Philz Touch Recovery version 6.00.8.

Edit: Rebooted phone. Saw custom/lock screen boot screen. Screen then went blank. Pulled battery. Booted into Recovery. Wipe Data/Cach - Factory Reset. Restored I545OYUEMJ7 NANDROID which I had created before flashing the ROM. Everything is fine now.
[Verizon Samsung Galaxy S 4] Surge1223:
Sure, in the OP of this post ( http://xdaforums.com/showthread.php?t=2500826) I described how its done at the end. Also you can pm me if you needed more detail

P.S. anyone interested in examining the oyuemj7 firmware, ive posted the boatloader tar.md5 below, but the modem is oyuamdk (DON'T FLASH, prob works but its more for research)

http://www.androidfilehost.com/?fid=23269279319198454
[Verizon Samsung Galaxy S 4] SamuriHL:
Thanks man. That was one of the guesses I had when I was playing around with the S4 GPE modems back in the early days. Without them being signed, even on an unlocked phone, bad bad things happen with updates. I'll play around with this and see if I can match the results using that technique that I got from the technique I used on the GPE. (Basically in an update zip you can find the correct size for the modem it's patching and just extract that number of bytes to get the signed file that you can then use for patching in future updates.) This is great info to have!
[Verizon Samsung Galaxy S 4] equake:
I appreciate your hardwork in getting us back to stock.

Note 3 Dev Ed Stock F/W Request

Above is a link on the Samsung Developer Forum requesting the Stock Dev Ed Note 3 F/W.

Add your 2 cents worth.