Showing posts with label really. Show all posts
Showing posts with label really. Show all posts

Friday, 16 October 2015

[Q] System really small Help!!



Hello!
Today I installed Unikernel on my S6 to root it. Everything worked fine, and looked normal, but I restarted my phone and after that everything looks really tiny... I have no idea how to change it to normal and I hope for your help. I didn't change a thing since rooted, only greenify.



Thursday, 15 October 2015

How bad is S-Voice really? Why?



Hi guys, I want to know just how bad the s-voice on the gear s2 really is before I make a final decision. Many reviewers keep saying that the s-voice is one of the only bad things about the gear but they never go in to much detail about why exactly.

Is the S-voice technology the same as the ones already on Samsung phones?? I have been playing around with the one on my S6 Edge and it seems quite satisfactory.



HELP I REALLY NEED YOU GUYS RIGHT NOW THIS IS FOR MY HTC ONE M9 error code 21



So long story short: i tried to flash the stock rom to my htc one m9 and then this error 21 appeared and i cant find anything on xda to solve it so please all you htc one software gurus out there help me on this one and i would be really greatfull here is my fill report from what i got from fastboot


C:\Android\com>htc_fastboot flash zip 0PJAIMG.zip
htc_fastboot v3.0.7 (2015-03-30)
target rom version: 2.10.401.1
found large-zip header, file count: 7
processing file 1/7...
sending 'zip' (126441 KB)...
OKAY [ 7.019s]
writing 'zip'...
(bootloader) HOSD CL#576582
(bootloader) GPT is up-to-dated. [17408]
(bootloader) start@23
(bootloader) aboot_signed.img@100%
(bootloader) rcdata.img@100%
(bootloader) splash1.nb0@100%
(bootloader) adsp.img@100%
(bootloader) modem_st1.img@100%
(bootloader) modem_st2.img@100%
(bootloader) pg2fs_ship_signkey.img@100%
(bootloader) sensor_hub.img@BYPASS
(bootloader) apppreload.img@22%
(bootloader) apppreload.img@45%
(bootloader) apppreload.img@68%
(bootloader) apppreload.img@90%
(bootloader) apppreload.img@100%
(bootloader) cota.img@100%
(bootloader) sdi.img@100%
(bootloader) sbl1-8994-1.img@100%
(bootloader) pmic-8994-1.img@100%
(bootloader) cpe.img@100%
(bootloader) rpm-8994-1.img@100%
(bootloader) tz-8994-1.img@100%
(bootloader) hyp-8994-1.img@100%
(bootloader) recovery_signed.img@100%
(bootloader) tp_MXM11876.img@BYPASS
(bootloader) tp_SYN3351.img@BYPASS
(bootloader) hosd_signed.img@100%
(bootloader) boot_signed.img@100%
(bootloader) radio.img@100%
(bootloader) Update zip file OK
(bootloader) end@Done
OKAY [ 13.058s]
finished. total time: 20.077s
processing file 2/7...
sending 'zip' (399971 KB)...
OKAY [ 24.006s]
writing 'zip'...
(bootloader) HOSD CL#576582
(bootloader) start@1
(bootloader) system.img_00@9%
(bootloader) ERR SPARSE data size=-1
(bootloader) system.img_00@FAIL
(bootloader) system.img_00@FAIL
(bootloader) system.img_00@FAIL
(bootloader) system.img_00@FAIL
(bootloader) system.img_00@FAIL
(bootloader) system.img_00@FAIL
(bootloader) ERR inflate fail: uncompressed size(753989696) is not equal
(bootloader) total out size(753989682)
(bootloader) ERR inflate fail, zerr=-3, total_out=753989682
(bootloader) ERR zerr=-3, Z_STREAM_END=1, total_out=753989682
(bootloader) ERR [SD_UPDATE_ERR] unzip_and_update_partition: failed to u
(bootloader) nzip image or update partition[system][err 21]
(bootloader) system.img_00@FAIL
(bootloader) ERR [SD_UPDATE_ERR] do_update_zip_buf: unzip_and_flash_imag
(bootloader) es fail, err 21
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 21
(bootloader) ERR Update zip file failed.
(bootloader) system.img_00@FAIL
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 21
(bootloader) end@Done
FAILED (remote: 21: fail to flash via downloadzip)
finished. total time: 32.941s
htc_fastboot finished. total time: 55.635s

C:\Android\com>



Sunday, 11 October 2015

Battery drain. Really fast.



My battery on my phone is draining really fast! See photos. Can anyone help me figure out why?

Sent from my SM-G928F using xda-developers.com, powered by appyet.com



Friday, 9 October 2015

Really Confused Can Anbody Help???



Hi guys I have a Sony Xperia Z3 I had to have a new battery installed so I got it done had my sim card and memory card removed. When I got my phone back it had kitkat 4.4.4 installed which I thought was strange as I had lollipop installed onit before hand. I have tried the sony pc companion repair option and still its on kitkat the sony software is saying its upto date? Now here's the strange part I have no access to google services it doesn't exist on my phone anymore and neither does google chrome! Im really confused I can still get onto my google account online via pc just not on my z3 can anybody please help as my phone seems pretty much useless now as everything was backed up to google. Any help would be much appreciated. Thanks.



Thursday, 8 October 2015

Really weird bluetooth behavior since 6.0 upgrade



So I'm not sure if this is an issue in the Doggcatcher app or not. So here's my setup and details.

Nexus 5 completely stock 6.0. Phone has never been rooted, bought new from Play store. Bootloader is locked.
I am using an LG HBS-730 bluetooth stereo headset
I have 2 numbers on this phone, one is the carrier number (T-Mobile), the other is a Google Voice number that is managed by the most recent version of Hangouts with the Hangouts dialer.

Twice today, I have been listening to a podcast using the Doggcatcher app when an incoming call from my Google Voice number happens through Hangouts. The Doggcatcher app will pause, I will push the call answer button on the headset, and the phone call will begin but the podcast will resume playback at the same time. I can pause the podcast via the app controls on the phone and the call will continue as normal. The caller can hear the podcast as well.

Not sure if it's the app or the OS/bluetooth causing this but it's really confusing. I reported the issue with the developers of the Doggcatcher app, but I haven't posted it to Google yet.

Any ideas?



Wednesday, 7 October 2015

jfltecan: Is that really impossible to downgrade from KK to JB? Can someone confirm?



Hi,

I have experience with the Canadian S4 I337M, currently running custom Validus ROM 5.1.1, originally was on TouchWiz 4.4.2;
I have altough a question that seems quite.. debated, did looked around I can't find a definitive answer and know who I should trust. I wonder if options changed in 2015 rather than 2013 when KNOX was still new.

Out of simple curiosity (I will not attempt it, risky, probably useless and I'm running 5.1.1 anyway): I keep reading that it's impossible to downgrade the S4 to 4.2.2, due to the KNOX bootloader on 4.3 / 4.4, I understand that you cannot downgrade below 4.3 which is the "new" KNOX bootloader.

1. I'm simply curious: On the I337M, what happens if you grab the stock 4.2.2 firmware and flash it with Odin anyway, considering I'm on 4.4 ? My guess, if I'm correct, Odin detect the bootloader version right away and says "FAIL". Correct?

2. I used to think it was possible to downgrade from 4.4 to 4.3, since 4.3 has the KNOX bootloader as well. Is this possible anyway, or will Odin fail (Not going to try it, not worth it)? Considering what I've read just today, 4.4 is also a new bootloader. In any case, since that 4.4 bootloader cannot be downgraded (I guess?), there is no way to downgrade from 4.4 to stock 4.3 either? Odin will show "FAIL" ?

3. Is there any other way to downgrade it anyway? I understand that KNOX 0x1 remain irreversible yet, and to my knowledge, it's impossible to dowgrade to 4.2.2 (Or even 4.3?), but I've been reading that it was possible to downgrade if the bootloader is excluded from the TAR archive, make sense to me, but is that true, was that patched? Should I recompile an ODIN package excluding the bootloader, is that how it's done (Too dangerous, not trying it)? Or maybe by using Mobile Odin / FlashFire, downgrading from 4.4 to 4.3 / 4.2 can be acheived, if the bootloader is left untouched? What happens if we try it anyways? Odin fail, or device does boot but doesn't get past Samsung boot logo?

I'm just wondering, and quite confused by the different opinions that were shared. Remember this is for the Canadian I337M variant.

Thanks for confirming, appreciate!