yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 i9505 Original Android Development] chetasus:
Hi Guys,

Do we know what happening on that calls issue. I have been missing more then 40% of calls.

Please advise.

thanks
[Galaxy S 4 i9505 Original Android Development] kaalalto:
Yes, latest version of Philz recovery works also fine now, no Status 7 error :good:

EDIT : Philz Touch recovery works as long as you manually use it to update CM. However, with CM auto update feature, this recovery fails to open and find the update file.
[Galaxy S 4 i9505 Original Android Development] winwiz:
+1 Having lots of issues

I get silent calls when making or receiving calls. Both the parties can not hear each other, we have to dial 3 or 4 times to be able to hear each other
[Galaxy S 4 i9505 Original Android Development] chetasus:
Guys will really appreciate if you can give update on this...or just tell if can't be fixed???

Thanks
[Galaxy S 4 i9505 Original Android Development] fyre31:
just wait. it is a known issue (you would have known that if you've read or even just searched the thread). the team is doing the best they can to fix it.
[Galaxy S 4 i9505 Original Android Development] DanderMan:
I know, but this was the problem - the time was taken from option "sleep" not from Automatically lock. Never mind, I updated to a newer nightly an now it's working like a charm.

Thx!
[Galaxy S 4 i9505 Original Android Development] ZeizenKii:
I know this may not be the right place to post this. If you have the time to troll use that time to answer my question. It will only take a minute. Am i the only one having dungeon hunter 4 as incompatible here in playstore? I changed the dpi to 320. Can anybody confirm or enlighten me regarding this matter? I dont want to be rude posting here but feedbacks from this thread will certainly be the most helpful. Thanks.
[Galaxy S 4 i9505 Original Android Development] 3bs11:
I can't find the app in the play store in Ireland. Anyway its probably because you changed your DPI. It's pretty easy to change back so why not try that and see?
[Galaxy S 4 i9505 Original Android Development] SnoopyDog:
Omg, we really need a moderator for this thread....:rolleyes:
[Galaxy S 4 i9505 Original Android Development] mgear356:
2nd that.. having like out of 10 calls so far, 3-4 cannot be heard

on 2nd july nightlies
[Galaxy S 4 i9505 Original Android Development] Cederstrom:
Same here, also july 2'nd rom.
[Galaxy S 4 i9505 Original Android Development] mgear356:
Actually I though it was fixed.. No problems in 29 July build or 30 build.. Or perhapsbbecause i don't have any incoming calls?

For 2july build, it occurs in incoming calls.. If I call back straight away, no problems
[Galaxy S 4 i9505 Original Android Development] drnjstj:
Installed the nightly from 3rd of July and no issues with incoming calls.

Called my phone 6 times with an other phone.
[Galaxy S 4 i9505 Original Android Development] CaptnKernel:
I cant connect to any WLAN... I see the ssids, but when i try to connect nothing happens. No wifi symbol in status bar, nothing... I provided logs yesterday evening in #sgs4 .. [MENTION=2385005]invisiblek[/MENTION]
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
please tell me your basebands
[Galaxy S 4 i9505 Original Android Development] mabmed:
Same here! Call issue is back more in nightly 03-07! Base band MF8

Envoyé depuis mon GT-I9505 avec Tapatalk
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
im on MEA and i didnt have some for a long time, haevnt had much frequent calls
[Galaxy S 4 i9505 Original Android Development] drnjstj:
MF8
[Galaxy S 4 i9505 Original Android Development] winwiz:
ME2
[Galaxy S 4 i9505 Original Android Development] mgear356:
Mf8

Now that you mention it, I didn't have any issues with mea
[Galaxy S 4 i9505 Original Android Development] mabmed:
Will try MEA!

Envoyé depuis mon GT-I9505 avec Tapatalk
[Galaxy S 4 i9505 Original Android Development] egendomligt:
CM update to 20130703 gives a slight hiccup by throwing an error in recovery: "failed to verify whole-file signature", "signature verification failed". I got the option to install untrusted zip though, which worked fine. This was using invisiblek's fixed cwm recovery.
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
1+
[Galaxy S 4 i9505 Original Android Development] felek73:
Try IT , I'm also on MEA and don't have any problem with silent calls since month..
[Galaxy S 4 i9505 Original Android Development] winwiz:
No issues for me mate! works a charm

Are you using the recovery recommended by OP?
[Galaxy S 4 i9505 Original Android Development] Theshawty:
03 flashed beautifully for me and I use the latest official CWM Touch through ROM Manager.
[Galaxy S 4 i9505 Original Android Development] lexvandoef:
I encounterd it too, first time I rejected and downloaded de ROM again. Then it happened the 2nd time too. I backuped and just tried, seemed to work. But a bit strange.
[Galaxy S 4 i9505 Original Android Development] Jalfrezi:
best rom available got it on the ace, ainol novo samsung S3 S4 and nexus 4

simple easy and fast, reliable and a great team updating it nightly AWESOME :laugh:
[Galaxy S 4 i9505 Original Android Development] CaptnKernel:
I use invisiblek's recovery - works nice. However, i can't connect to any wifi - i am on 03/07 official nightly for the jfltexx. Logs are attached.

I would like to know if there is anyone else with wifi issues on the current nightlies... And does someone know what the cause might be?

Regards
[Galaxy S 4 i9505 Original Android Development] simondavies315:
Baseband MEA
[Galaxy S 4 i9505 Original Android Development] maikinho10:
Use wififix.zip from few (5-6)pages before...

After flashing this zip.. My wifi works :)

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] CaptnKernel:
YES!! I can confirm that the "WifiFix" works! Thank you very much!

(I'm following this thread since day 1 and totally forgot that thing... sorry :good:)
[Galaxy S 4 i9505 Original Android Development] simondavies315:
Invisiblek said before that someone keeps removing his firmware blob which is causing the WiFi issues
[Galaxy S 4 i9505 Original Android Development] Cygnust:
Weird .. when I try to flash a modem from the modem collection topic, wifi is broken.

Neither wififix.zip is working neither a cid.info file is in /data

+ now I have a reboot every 30 seconds .. don't even have time to enter to check /proc/last_kmsg somehow

Glad I made a nandroid backup yesterday :/

[edit]

ok .. My phone has gone crazy .. no matter what I do, it's still rebooting .. :/

manage to copy the /proc/last_kmsg somehow

Kernel is stock CM, recovery is philz. Latest nightly.

What caused the bug was my attempt to flash the modem MEA with odin (came from MF5)

Thanks for you help
[Galaxy S 4 i9505 Original Android Development] wessel596:
I had that too after I over clocked my s4. Have you by any chance done that? I reverted to stock because i was not able to flash another kernel.

Hope this helps.

Sorry for a bit off topic guys.
[Galaxy S 4 i9505 Original Android Development] Cygnust:
Nope .. everything is stock else i would not have posted here.

When I check the system logs, it says wifi is broken because wpa_supplicant is not found in /system/bin which is totally weird because I tried to format system and install cm again and did not fix it ..

I also tried to restore only system from a nandroid backup working, still the same

I tried fix permissions, wipe dalvik, cache, same ..

nevermind I'm gonna restore the whole nandroid but I'm kind of frustrated to not being able to understand it.

+ the fact that anytime I try to change the modem, I have the same thing ..

[edit]

ok, the whole restore made it ..

I really don't understand. Wifi states being broken for something missing in /system after a modem flash, restoring system only doesn't work, restoring system + data works ..

[edit2]

reproduced the error by flashing it again.

Modem won't flash with PC odin, only with mobile Odin ..

actually the file missing is in /data/system/ so it makes sense .. But I'm still wondering why everyone here seems to be able to flash the modems as they want while I can't ..
[Galaxy S 4 i9505 Original Android Development] chetasus:
are we aware of this cpu issue with CM Kernel???

http://xdaforums.com/showthread.php?t=2349192
[Galaxy S 4 i9505 Original Android Development] live-evil:
am i missing something what is the issue?
[Galaxy S 4 i9505 Original Android Development] chetasus:
as per i understand its only using core0 instead of been quad core...correct me if am wrong..
[Galaxy S 4 i9505 Original Android Development] live-evil:
Its using hotplug which means it turns off unused cpus to save power. When it needs all four cores they should turn on again.
[Galaxy S 4 i9505 Original Android Development] harise100:
Start your music player in the background and check again. You will see that core1 is running just fine and so on.

Btw is the IR blaster now in every nightly build, or was it just a one time preview?

(can't check myself atm)
[Galaxy S 4 i9505 Original Android Development] winwiz:
nope, its not in todays build
[Galaxy S 4 i9505 Original Android Development] Langduscher:
Any possibility to back up (& restore) (custom) ROM settings?
[Galaxy S 4 i9505 Original Android Development] BillGoss:
You have two options:

- use TB

- backup/restore /data because settings are stored there.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] Langduscher:
Thanks man. Using TiBu backup system data I suppose?

Either way things van get messy that way right?

(AOKP had an app tot backup/ restore personalized settings)
[Galaxy S 4 i9505 Original Android Development] chetasus:
hi there,

did you managed to flash MEA on you phone yet???

i have tried flashing MEA from here http://xdaforums.com/show....php?t=2192025

via odin 3.07 but still on MDE as its doesn't flash it, say ok on both PC and mobile screen but when i check base back remains MDE....

will get latest Odin and try again ....any other suggestions please???
[Galaxy S 4 i9505 Original Android Development] mabmed:
The right method:

Link original:

http://xdaforums.com/showthread.php?t=2192025
[Galaxy S 4 i9505 Original Android Development] chetasus:
thanks mate, flashed MEA now and will report back if still any call issue....
[Galaxy S 4 i9505 Original Android Development] BillGoss:
I had a no sound phone call followed by a working phone call. Both were @14:24.

System and radio logcats plus dmesg are available here: http://db.tt/YHmrnBWn

FYI: on 0703 and MF8.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] CaptnKernel:
Total camera crash on current 04-07 nightly, requires reboot

Hi everyone,

a minute ago i unlocked the phone into camera mode by sliding into the according navring target on my lockscreen (hope you get what i mean).

I immediately had a "gallery crashed" FC. I pressed "ok", and the device says something like "camera error - can't establish connection to camera" (i get the message displayed in german, maybe the equivalent english error message deviates in wording).

Now i can't start the camera anymore until i completely restart the phone. I have my complete set of logs attached. Also, here is an additional link to the same set of logs: https://www.dropbox.com/s/bgkojeor5n89wse/jfltexx nightly 04-07 camera crash.zip

I experienced the problem at around 18:31.

However, logcat shows some strange entries already at 18:19:

Also, there is a huge number of modem.log entries between 18:17 and 18:31... 17688 lines, to be precise :eek:
[Galaxy S 4 i9505 Original Android Development] KEriksen:
Tried the nightly 0704 as the first rom on my 9505... Seems it removed root, restored stock recovery and can't recognize sd card... :mad:
[Galaxy S 4 i9505 Original Android Development] joelvn:
You can't even install cm without a custom recovery like cwm. So what do you mean? Nvm I read it wrong.

You should flash stock firmware back on your phone then root it, and try to flash it again. And is your sd card exfat by any chance?

Flowed from my GT-I9505 using xda-developers app
[Galaxy S 4 i9505 Original Android Development] realslicedbread:
coming back to CM10.1 after a month away I am very pleased to see a lot of the bugs I had before are fixed:

recoveries fixed, no more status 7 (big thanks to Dan!)

front facing camera aspect ratio fixed

calls using headset now working

operator/carrier names fixed - no more numbers showing instead of names

I still have a bug (others previously reported) - enabling bluetooth sometimes knocks my wifi out and then I can't enable either afterwards until a reboot. Sometimes disabling the (working) bluetooth it turns my wifi off (in this situation i can just re-enable wifi without reboot).

Other than that pretty stable and I am happy to use it as a daily driver.

(Running 20130704, Philz touch 5.07.5, MF8 baseband)
[Galaxy S 4 i9505 Original Android Development] DuckMcQUack:
Dunno what you did, but it has been the first rom for me too and it works flawlessly. The root is there too. Have u followed the instructions on the first post?
[Galaxy S 4 i9505 Original Android Development] kaalalto:
That's true ! Seems the CM development is really as great as expected from this great team ! :cowboy:

My Antutu score is now 24600 without OC...I had never obtained such as score before, even with TW stock rom ! :good:

Just waiting for IR blaster merge and fixing some issues with sensors (please see the attached screenshots) :o
[Galaxy S 4 i9505 Original Android Development] simondavies315:
Why is IR still in review when it's been tested by lots of people and verified working?
[Galaxy S 4 i9505 Original Android Development] kaalalto:
I've read before that the IR funcionality is still specific to GS4 and the CM team want to merge it as a generic capability fo all the IR enabled devices...maybe I'm wrong ! :confused:
[Galaxy S 4 i9505 Original Android Development] simondavies315:
If the code only works for our device shouldn't it be merged and then modified for other devices?
[Galaxy S 4 i9505 Original Android Development] wicki30:
Which sensors?
[Galaxy S 4 i9505 Original Android Development] kaalalto:
The four sensors with red circle in my post ! So strange ! They work with Samsung TW stock rom but not with CM !

Who can confirm this please ? :confused:
[Galaxy S 4 i9505 Original Android Development] dar74:
QUOTE=kaalalto;43276607]The four sensors with red circle in my post ! So strange ! They work with Samsung TW stock rom but not with CM !

Who can confirm this please ? :confused:[/QUOTE]

I have the same issue
[Galaxy S 4 i9505 Original Android Development] kaalalto:
I have the same issue

Thanks for your answer !

[MENTION=3940262]wicki30[/MENTION] : do you use an alternative kernel on CyanogenMod ? :confused:
[Galaxy S 4 i9505 Original Android Development] I9000bramgmail:
they work just fine here...
[Galaxy S 4 i9505 Original Android Development] kaalalto:
Are you using last nightly ? :confused:
[Galaxy S 4 i9505 Original Android Development] chetasus:
Same issue with sensors, running pacman which is CM based....
[Galaxy S 4 i9505 Original Android Development] kaalalto:
Thanks for you answer...so it's a bug :rolleyes:

The problem is those sensors are used by many apps and 3D games (orientation and linear acceleration...) so it could be really annoying !

Do we have to open a dedicated thread or continue here as it's CM related ?
[Galaxy S 4 i9505 Original Android Development] kaalalto:
Just to be sure, I've reflashed back the last 4.2.2 stock ROM and sensors work well (see attachment).

So it's definitively an issue with CyanogenMod.

Hope it could help to make our favorite ROM better :good:
[Galaxy S 4 i9505 Original Android Development] realslicedbread:
Just did a dirty flash of 20130705 ontop of yesterday's version (but I did wipe cache and dalvik before installing).

A few bugs:

when the phone is turned on from cold, it connects to my wifi and cellular HSDPA normally. I enable bluetooth from the pulldown quick settings - it turns on normally. However when I go to disable the bluetooth (from the pulldown) it will disconnect my wifi. I need to disable and re-enable wifi before it reconnects.

The carrier/operator numbers-instead-of-name bug is back.

Finally in CPU-Z I get the same lack of sensors that [MENTION=5328013]kaalalto[/MENTION] is reporting.

Edit: from a cold boot with wifi/3g already on and connected, even just enabling bluetooth will drop the wifi connection after about 20s (doesn't have to be enable/disabling of bluetooth). Wifi can be recovered by disabling/re-enabling wifi.
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
Why do they bring back the carrier name bug?

This commit is

http://review.cyanogenmod.org/#/c/45130/

the reason why the bug is back.

Guess I'll skip the next nightly(ies)

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] realslicedbread:
No idea. Hope the maintainers see this and sort it out for tomorrow?
[Galaxy S 4 i9505 Original Android Development] IakobosJ:
Same! Its such a silly bug but it is so annoying :p
[Galaxy S 4 i9505 Original Android Development] BillGoss:
But not everybody has the problem. I, for one, have never had any problem with the sensors.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] SoLChoBo:
These are my sensors:

:crying:
[Galaxy S 4 i9505 Original Android Development] thengel:
Now it's OK.
[Galaxy S 4 i9505 Original Android Development] kaalalto:
So strange ! :eek:

Does sensors need specific drivers or they are natively supported by Android ?
[Galaxy S 4 i9505 Original Android Development] mabmed:
My sensors works good :good::
[Galaxy S 4 i9505 Original Android Development] BillGoss:
The 0705 nightly is missing the code to manage SIM card pins. It also doesn't enable the SIM so there is no phone connectivity.

I'm reverting to 0704.

Sent from my GT-I9505
[Galaxy S 4 i9505 Original Android Development] nerotix:
Which nightly u on? And also which kernel and baseband?
[Galaxy S 4 i9505 Original Android Development] I9000bramgmail:
You're saying that like its a fact, and there's no truth in it whatsoever, my sim card gets accepted, asks for pin and then connects just fine.
[Galaxy S 4 i9505 Original Android Development] mabmed:
Latest nightly 05.07, with official cm kernel, baseband: MEA

Envoyé depuis mon GT-I9505 avec Tapatalk
[Galaxy S 4 i9505 Original Android Development] cooldfuzion:
I am having issues installing this roms, in CWM it says "issue 7" and i cannot update to the latest build, and in the latest builds the contacts disappear...any clue?
[Galaxy S 4 i9505 Original Android Development] realslicedbread:
Which recovery (and which version) are you running? And how are you updating the rom?
[Galaxy S 4 i9505 Original Android Development] crnkoj:
mine work too, todays nightly (7.5.) i did flash the 4.3 GE first to test it, but than flashed cm over witha full wipe
[Galaxy S 4 i9505 Original Android Development] pitastrudl:
carrier name works here, haven't had problems with calls today. had some on yesterday's nightly.

Sent from my S4 GT-I9505
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
The people who had the carrier bug before it got fixed will have the bug with nightly 5.7.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] IakobosJ:
I had this when trying to install too.

It was strange for me, I deleted the file and re-copied it over (via adb) and then it installed fine.

Contacts are fine for me though.

I am one of the unlucky ones who has the Carrier name bug :( No silent calls today though :)
[Galaxy S 4 i9505 Original Android Development] zafu:
Hi,

Coming from jfltexx's UNOFFICIAL nightlies I tried installing the latest

OFFICIAL over the last several days but it fails with an error in the

update script.

I am wiping system, dalvik and cache.

Should I also wipe data even if coming from 20130626 UNOFFICIAL ?

Thanks,
[Galaxy S 4 i9505 Original Android Development] nerotix:
Let me guess.. status 7 error? If so, update the CWM which was released here on this thread, use the search function. This CWM recovery fixes the status 7 error.
[Galaxy S 4 i9505 Original Android Development] germinus:
Just tried to install this and got a status 7 install aborted message and now I cant get passed the default boot screen on Samsung Galaxy s4 GT-i9505...am I bricked?
[Galaxy S 4 i9505 Original Android Development] simondavies315:
Can we have IR merged in the nightlies please. It's been tested and works well why the hold up?
[Galaxy S 4 i9505 Original Android Development] nerotix:
please please please please f*cking please ... for the love of god.. look 1 post above yours.
[Galaxy S 4 i9505 Original Android Development] germinus:
lol sorry I had to laugh at your post, you sound like me with my pupils, I am searching but I find nothing when when I search CWM. Well i get loads of posts refering to the mystery post of an updated version but I can not find it anywhere! and in the mean time my phone is stuck in what you guys call "bootloop"
[Galaxy S 4 i9505 Original Android Development] IakobosJ:
Just to let you know, I have downloaded the WORKING recovery and I also got the Status 7 error. I had to transfer the file using adb to get it to flash!
[Galaxy S 4 i9505 Original Android Development] nerotix:
Show me which recovery your using? Cuz hundreds of people are using the latest version and NOONE had a status 7 error ever since, so i think you're still in the wrong here.
[Galaxy S 4 i9505 Original Android Development] 3bs11:
I had it before but don't now. Please stop posting stuff like this before you confirm.
[Galaxy S 4 i9505 Original Android Development] germinus:
ok so just downloaded cwm-07012013-jfltexx.img, I assume this is the right file your talking about, but how do I install it when I cant get passed the samsung screen, I cant get it to sd card as cant get past boot????
[Galaxy S 4 i9505 Original Android Development] iamnotkurtcobain:
I have the bug in build 5.7.

Gesendet von meinem GT-I9505 mit Tapatalk 2
[Galaxy S 4 i9505 Original Android Development] IakobosJ:
I was only reporting on my experience!!

At first I was using the latest CWMTouch from the clockwork website and got Status 7.

After it failed I thought it was the recovery, so I flashed this: http://invisiblek.org/gt-i9505/recoveries/cwm-07012013-jfltexx.img SAME thing.

Then flashed latest NON touch CWM, same thing.

I then sent the file using adb and WOW. It worked!!
[Galaxy S 4 i9505 Original Android Development] nerotix:
http://xdaforums.com/showpost.php?p=43154755&postcount=759

There's the current one atleast.

---------- Post added at 09:05 PM ---------- Previous post was at 09:03 PM ----------

Please leave a log file here then. What were u trying to flash? CM10.1 or something else?
[Galaxy S 4 i9505 Original Android Development] zafu:
No the error is:

set_perm: some changes failed

E: error executing binary in zip ...
[Galaxy S 4 i9505 Original Android Development] 3bs11:
That's fine I have no problem with that but you said the people who had it before will have it on the latest build which isn't true since I don't have it. No need to discuss this any further :p
[Galaxy S 4 i9505 Original Android Development] germinus:
How do I install this when I cant add it to SD card as I cant get passed the boot screen? Now I am starting to panic, am I bricked???
[Galaxy S 4 i9505 Original Android Development] nerotix:
Nah your's is easy to fix. Flash a different rom in recovery (u can mount USB in recovery) and copy a rom on ur sdcard.. or u can make the files i linked u a .tar file with 7zip and use odin to flash it,, then flash cm10.1 again.
[Galaxy S 4 i9505 Original Android Development] IakobosJ:
I was flashing the latest CM10.1 Nightly, unfortunately I panicked and thought my phone had died so didn't take a log file and thought it was something I had done, not a bug or anything.

I fixed it anyway by copying the file over using adb. If it happens again I'll be sure to pull a log :)