yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Original Android Development] andrescm:
Are you following the OP's exact instructions to flash CM14?. CM13 had an issue (latest snapshot), for some reason it would get stuck in a boot loop for no apparent reason and the only way out was to restore the most recent nandroid. But I haven't seen it yet in CM14. If you don't have a backup, don't dirty-flash, wipe system and do a clean flash. The media partition should not be affected, mine wasn't.
[Galaxy S III Original Android Development] McXred:
Multiple clean flashes and still nothing. I was following it step by step. Unfortunately i don't have nandroid backup. Idk why it restarted, when i'm in recovery everything seems to be ok (no errors or something)
[Galaxy S III Original Android Development] baltics:
For reasons I explained I flashed this on an S3 running stock Samsung.

All I flashed before installing this ROM & Open Gapps was TWRP 3.0.2.2 using the MacBook version of Odin.

One has to be patient during the boot up process. It takes a long time.

But it does flash
[Galaxy S III Original Android Development] McXred:
But i don't want to flash stock bc I'll loose all my data and it's not a option for me. And the booting process always was like 3-5 mins not like 20 and still nothing (actually im booting this bad boy 25 mins and still nothing)
[Galaxy S III Original Android Development] adam.ap:
CM 14.1 not working
[Galaxy S III Original Android Development] andrescm:
Are you wiping cache, dalvik/art, system and data when doing a clean flash?. Not wiping the cache is almost guaranteed to end up in a bootloop. Just avoid wiping the "media" partition which is where lies your photos and stuff. Also, which gapps are you flashing?. Try OpenGapps ARM 7.1 pico.
[Galaxy S III Original Android Development] vuut:
Me too.,.MTP has stopped working" error
[Galaxy S III Original Android Development] LuciferIII:
Already known buf,will get fixes
[Galaxy S III Original Android Development] lithoc:
Hi,

I'm currently on cm-14.1-20161214-NIGHTLY-i9300 , anyone having issues with poor animated gif viewing on gallery . And whatsapp will hang when trying to load animated gif

Not sure if its CM or whatsapp issues
[Galaxy S III Original Android Development] vuut:
Good for me... sometimes MTP bugs not working..
[Galaxy S III Original Android Development] Maxoobidou:
[MENTION=5405215]forkbomb444[/MENTION] : today's build failed. Can't try to add the line to solve the audio issue.
[Galaxy S III Original Android Development] forkbomb444:
oops, forgot to amend. should be ok tomorrow :)
[Galaxy S III Original Android Development] McXred:
Cache, dalvik cache, system, boot, data and even preload nothing helps. I don't even know why it turned off then, it was in standby on charger. Tried flash it many times. I flashed like for the first time without the gapps not worked. again clean flash but with mini gaaps (open Arm 7.1) still nothing
[Galaxy S III Original Android Development] mohand06:
Is your twrp version 3.0.2-1? Try flashing latest pesci2k's custom, after boot in this build, try updating to latest official nightly.
[Galaxy S III Original Android Development] McXred:
I'm using latest Philz touch CWM. But I'll try your advice :')
[Galaxy S III Original Android Development] baltics:
You actually want TWRP 3.0.2.2.
[Galaxy S III Original Android Development] McXred:
But why i now have problems and before everything worked as should?
[Galaxy S III Original Android Development] baltics:
Page 1 of this forum contains instructions on installing this ROM. Those instructions include ...
[Galaxy S III Original Android Development] andrescm:
CM Recovery should be ok, but it doesn't hurt to try TWRP given the current situation. I don't know about CM Recovery but TWRP also has a file manager. If you have an OTG pen drive, you could plug it to the phone and use that file manager to copy everything to the pen drive so you have a backup.
[Galaxy S III Original Android Development] McXred:
I haven't got CM recovery, I have Philz touch clockwork mod recovery which is different thing (just to make it clear).

Edit: Finally it worked, i just flashed some tw based rom on kitkat and then again cm14. Thanks for help
[Galaxy S III Original Android Development] andrescm:
Flash TWRP 3.0.2-2 with Odin and install ROM again. If you don't have any hardware issues you should be OK.
[Galaxy S III Original Android Development] VigneshS007:
plz can someone tell me the bugs in the latest nightly build u flashed?....
[Galaxy S III Original Android Development] xEmre66:
No bugs except robotic sound in calls (will be fixed in next nightly) and "MTP-host has stopped". It's stable enough for daily use.
[Galaxy S III Original Android Development] :
cm-14.1-20161218-NIGHTLY: Batter drain and slow charging (new battery), low audio levels from speaker (notifications, ringtone, alarm). Also robotic 3G call audio (potentialy getting fixed in the next build).
[Galaxy S III Original Android Development] McXred:
Clock not working but i think it's fault of my phone (keep crashing after entering) 16 december build
[Galaxy S III Original Android Development] dlcarvalho:
On cm-14.1-20161218-NIGHTLY:

- If automatic time zone is on and you switch on and off the airplane mode, the select time zone goes to GMT-00:00.

- In a call is not possible to decrease the volume (always high).
[Galaxy S III Original Android Development] magicmyth:
My i9300 with baseband I9300XXEMG4 has high in-call volume issue. Adjusting the volume using the physical buttons or software sliders has no affect.
[Galaxy S III Original Android Development] baltics:
There is going to be a fix in the next build.

To fix it now switch from 3G to 2G.

If you search this forum you will find many posts on this bug.
[Galaxy S III Original Android Development] magicmyth:
I saw some of those posts but I thought that was about the robotic in-call voices and not the high volume. I tried to see if I could test that out but Preferred network type is only allowing 3G as an options.

Thanks for the reply. I'll test out the next nightly and report back.
[Galaxy S III Original Android Development] baltics:
I think the issues are connected.
[Galaxy S III Original Android Development] xEmre66:
I think today's build failed. I always wake up at 5:05AM to check if there are any new nightlies. (Because forkbomb "always" uploads new nightlies at 5 A.M.) Is it right guys? Or will it be available at midnight? Sorry for those n00b questions but I want that fix for robotic voice. I know everyone wants that but.....:o
[Galaxy S III Original Android Development] baltics:
See post #8517 earlier today from forkbomb444.
[Galaxy S III Original Android Development] mohand06:
Hi [MENTION=5405215]forkbomb444[/MENTION], would you kindly tell what that means: [ 12-20 21:33:52.779 3987: 4089 D/s2com_uti ]

file_get: exists: false '/mnt/sdcard/s2/tnr_pof' in logcat. Is it rom related or some user apps installation? Regards
[Galaxy S III Original Android Development] cRaZy-bisCuiT:
What are the known bugs for 14.1 + i9300 atm? I don't feel like going through 854 pages just to find out about that. ;) Thank you in advance! :)

EDIT:

"E: failed to verify whole-file signature"
"E: signature verification failed"
"installation aborted."

Steps I did:

* copy latest nightly onto external SD

* copy latest nano gapps onto external SD

* Install twrp-3.0.2-2-i9300.img recovery via heimdall

* boot into recovery

* wipe data/factory reset

* install from SD -> CM 14.1 .... and the error appeared - any ideas? Do I need to be root in advance?

EDIT2: At least it seems to install with CWM - I thought CWM is depracted and we're better off with TWRP? Any ideas? Where to report bugs to TWRP?
[Galaxy S III Original Android Development] andrescm:
Easy answer: disable signature checking in TWRP. It's expecting a .md5 file and it stops because it doesn't find it.
[Galaxy S III Original Android Development] vuut:
Hi guys. ..Pl don't flashing build 1218........my s3 alway bugs "MTP host has stop" when into Internet to the network to read newspapers

it happens a lot of times whenever I visit any Web
[Galaxy S III Original Android Development] galen2:
So... no more cm13 builds? i still dont want to jump to cm14.1, i prefer to wait a few months because cm13 is fast and bug free for me.
[Galaxy S III Original Android Development] LuciferIII:
This is like the 3rd time i tell you,It is a known bug,it will get fixed,do not ask again!!!
[Galaxy S III Original Android Development] mpsoft:
How you resolve problem with camera in cm13? Im on cm11 and I want to install cm13 but I know for camera issue. Which snapshot cm13 you have?

Thanks!
[Galaxy S III Original Android Development] vuut:
I reported about this error, as more and more severe and appear that I can not use S3 to do anything

from 18/12,,,,,,, to day is 21/12

s3's current frequent crashes with errors that do nothing more careless ,,, and I also do not have a backup, so a bit anxious hurry sorry you asked many
[Galaxy S III Original Android Development] LuciferIII:
Only crash from that app?

Trg to use "mute untill restart" or something

Try to clear data from the app
[Galaxy S III Original Android Development] vuut:
have done everything above, but that
[Galaxy S III Original Android Development] xEmre66:
I do not have the error "MTP-host has stopped" if i click mute until restart. I'm very happy with the 18-12 build. The only bug is: Robotic sound, but forkbomb will fix it. I have installed cm14.1 on my uncles Galaxy S5 and it has the same bug (MTP-host has stopped). So [MENTION=4680299]vuut[/MENTION]: please don't ask I have "MTP-host has stopped error"... It will be fixed soon. Don't worry :D ;)

---------- Post added at 09:14 AM ---------- Previous post was at 09:07 AM ----------

I thought CM13 will be moved to weekly but I was not right. But [MENTION=5405215]forkbomb444[/MENTION] is not working only on our device, so he is very busy and cannot do everything at the same time (building cm14 for s3, for nexus 7 2013 and for OnePlus One i think (bacon)) Maybe he will release a CM13 nightly but chances are very low. :svetius:
[Galaxy S III Original Android Development] stefan.slavici:
Just was released a new snapshot for CM13 !!!
[Galaxy S III Original Android Development] mpsoft:
Anybody try latest snapshot cm13?
[Galaxy S III Original Android Development] pesci2k:
Nightly and weekly are automated builds (not builded and uploaded by single developer). Actually cm14 is builded daily (nightly) and cm13 weekly. If a device has cm14 it will not get also cm13 (as in our case). Here you can find specific rules:

https://github.com/CyanogenMod/hudson/blob/master/cm-build-targets

If you want to stay on cm13 you can rely on stable snapshot (latest was released yesterday).

https://download.cyanogenmod.org/get/jenkins/189494/cm-13.0-20161220-SNAPSHOT-ZNH5YAO3XN-i9300.zip
[Galaxy S III Original Android Development] Psycho103:
Just download "Media server killer" from play store & whenever you get the camera error just kill mediaserver.
[Galaxy S III Original Android Development] xEmre66:
Oh. Didn't know about that. Thanks. Shall I delete my post?
[Galaxy S III Original Android Development] mpsoft:
When it came to the next snapshot do I have to re-install clean?
[Galaxy S III Original Android Development] Psycho103:
I'm not on CM13 so can't say anything but I'll suggest a clean flash as it's a snapshot.
[Galaxy S III Original Android Development] mpsoft:
Deleted
[Galaxy S III Original Android Development] andrescm:
Not necessarily but it's always best to do a clean flash rather than a dirty flash. I know it's a bit bothersome to do but there are some tricks to streamline and speed up the process:

1. Use Titanium Backup or similar to back up all the user apps (avoid backing up system apps).

2. If you use Whatsapp, sync chats with Google Drive.

3. Reboot to recovery and make a full nandroid.

4. Wipe system, data, dalvik/art and cache, then flash new ROM + gapps.

5. Enable root, reinstall Titanium Backup from the Play Store, set up the backups directory and restore user apps.

6. Do a clean install of Whatsapp and let it find the backup in the cloud (if you restore from Titanium Backup I found something is broken and the app won't receive messages until you unlock the phone).
[Galaxy S III Original Android Development] mohand06:
Hi, Pesci. Would you kindly have a look at these catlogs and tell me what are the errors. When you have time for that of course, thanks.
[Galaxy S III Original Android Development] xEmre66:
Deleted.
[Galaxy S III Original Android Development] pesci2k:
Today's build is out right now.
[Galaxy S III Original Android Development] xEmre66:
Hahahah ok. :D

---------- Post added at 06:18 PM ---------- Previous post was at 05:55 PM ----------

Just flashing it. Hope this fixes robotic sound.
[Galaxy S III Original Android Development] Logan:
I don't have any issue from first nightly from all issues that are been mentioned.

just noticed that battery icon while charging it's not clear like low quality if do you look closely, lol it's not that big deal anyway. xD
[Galaxy S III Original Android Development] ASTEK123:
Galaxy s3 echo problem

When making a phone call, it echoes to the other side. It does not work to reduce voice in applications such as skype, viper. So I can not talk to most people. There was no problem in cm-11-20160115-SNAPSHOT-XNH0E0O00N. The version I am currently using: cm-14.1-20161221-NIGHTLY-i9300. But in this version I compared echo problem. Please help me. Translated by google translated. sorry

Linux version: Enforcing TWRP:3.0.2.2
[Galaxy S III Original Android Development] dlcarvalho:
In cm-14.1-20161221-NIGHTLY-i9300, the problem with GMT-00:00 and Host MTP crash is still there. I didn't test the call volume level yet.
[Galaxy S III Original Android Development] djedjy:
I have problem with the 18122016 build.

I came from 4.4 rom, and in CM14 when I try to install app that I downloaded when I was on 4.4, it shows me 0 bytes. Or folder I made while I was om 4.4 it cant be open, and shows 0 bytes.

Or I cant restore apps with titanium backup, it shows me that I have backup, but cant restore it.

That didnt occured to me before, on earlier builds.

Anyone have same problem?
[Galaxy S III Original Android Development] minealex2244:
Reporting robotic sound it's not enough. It happens one time to 5 calls (in my case). But what is happening in "background", I mean with the system? If you what to help forkbomb, inspect this issue. I can't do this as the robotic sound is somehow rare but what I know is this: it can autofix, it happens in every signal strength case and it's not related to earpiece speaker as the speaker has this problem too. I first seen this on CM 13 and I think it's something wrong in the connection (linker) between soundserver and RIL code.
[Galaxy S III Original Android Development] pesci2k:
It's a crash on some viper4android file. So it's not something related to this rom.
[Galaxy S III Original Android Development] mohand06:
Thanks Pesci, really very kind of you. Good to know that it's not rom related. After each rom update, I have to flash again the sound mod I have been using for a good while now (can't do without) and it's true that V4A needs some manipulations (reinstall busybox somtimes, driver installation)
[Galaxy S III Original Android Development] baltics:
I added the build.prop edit which [MENTION=5405215]forkbomb444[/MENTION] invited us to test with the next build, it has not improved call sound. Still far too loud and robotic (metallic).
[Galaxy S III Original Android Development] Elezd:
Battery

After flashing, see backup. 14.1 with kernel boeflla, quickly sit down battery. Tried to put cm 13 the same effect. Can anyone suggest what to do before, he kept a day currently to 4% for 5 minutes of use. :(
[Galaxy S III Original Android Development] frudda:
I'm on

cm-14.1-20161221-NIGHTLY-i9300.zip

Notice flashlight works now disable enable

I havent had robotic sound yet, but I notice the first second when people speak it was robotic then it dissapeard, big improvement

When accepting a call and going into "lockscreen" mode phone turns crazy after goint out of "lockscreen" mode. It jumps to desktop, black screen. Makes it hard to controll speaker mode

Wireless still not waking up from hibernation

Cant control the volume when having a phonecall with someone
[Galaxy S III Original Android Development] vuut:
I've come back to Hyper's Rom..it's awesome and so much customization that there is no error

Gửi từ GT-I9300 của tôi bằng cách sử dụng Tapatalk
[Galaxy S III Original Android Development] rosel11078:
I install right now this version and I don't know why set wifi region code is missing from wifi advance setting and previus version has this option

please include this option
[Galaxy S III Original Android Development] gamerjim:
Why u quote the whole OP?? :eek:
[Galaxy S III Original Android Development] btud63:
i9300 white screen

Hello, I used Nightly-cm-14.1-20161218-i9300. It works perfectly without any problem. This morning I found the phone closed. I tried to restart, but has white screen. I came in download mode, I could not flash any rom with odin . I was in service and the boys say it is (EMMC) blocked by Samsung for using CM14.

Do you have a unlock solution? Or i need to replace the motherboard?

Thank you for your work. Again, your ROM work perfectly without any problem.
[Galaxy S III Original Android Development] xEmre66:
Is it right? I'm on the latest build. (21-12)
[Galaxy S III Original Android Development] naion:
For me the call audio volume control is fixed in cm-14.1-20161221-NIGHTLY-i9300. You can't expect something to be fixed if you don't provide more information how to reproduce the bug, logcat etc.
[Galaxy S III Original Android Development] baltics:
that is code ... it didn't fix it on mine, so I switched back to 2G, but it may work for others.
[Galaxy S III Original Android Development] Galaxy S III:
Latest nightly build (21.12) solved in-call sound problems for me. Volume can be adjusted and quality is perfect. Thanks a lot:good:
[Galaxy S III Original Android Development] xEmre66:
The robotic call sound is fixed for me. I can adjust volume in call and the quality is great. Thank you [MENTION=5405215]forkbomb444[/MENTION]. The "audio.force_wideband=true" code works perfectly fine.

---------- Post added at 11:40 AM ---------- Previous post was at 11:35 AM ----------

Now guys, the ROM is completely stable (except CM FC bugs like "MTP host has stopped"). The 21-12 nightly is completely stable and no robotic call sound with "audio.force_wideband=true" code enabled in system/build.prop

Thank you so much [MENTION=5405215]forkbomb444[/MENTION]. :o
[Galaxy S III Original Android Development] zarere:
The in call sound volume is fixed for me,too.Great job :good: [MENTION=5405215]forkbomb444[/MENTION]
[Galaxy S III Original Android Development] xEmre66:
Yes. All credits goes to forkbomb444 for fixing this error
[Galaxy S III Original Android Development] LuciferIII:
Rom is STABLE (ignore the mtp crash),only thing left is cm to add their stuff. Tiles,theme manager and stuff like that.

Btw any news on Theme manager,are they having problems with it?
[Galaxy S III Original Android Development] Maxoobidou:
I mean, there's still that WiFi connection issue, but apart from that it's pretty stable.

Can't wait for 3.10 kernel, and the battery improvements that's going to bring.

Can't believe a phone that old, using an undocumented Exynos CPU is running that well on the latest version of Android.

forkbomb444 is the bomb !
[Galaxy S III Original Android Development] magicmyth:
Add another confirmation that the high in-call volume (which can now be adjusted) is fixed. Now there are no practical issues with this ROM for me now. Big thank you to all the devs :good:
[Galaxy S III Original Android Development] andrescm:
That's the easy answer, they always blame custom ROMs , whether they are the culprit or not. I think your phone had a hardware failure but it's not related to CM14. Could have happened with stock ROM in my opinion. The fact that you can't flash a stock ROM back with Odin tells a lot. What error do you get?
[Galaxy S III Original Android Development] lepicane1:
For me the torch issue is still there (turns off 3 seconds after screen goes into standby) and 'android.process.media has stopped' every time I connect to PC via USB.
[Galaxy S III Original Android Development] xEmre66:
I don't have this issue when I connect my phone to the PC. The torch issue is still there but I don't use the torch in standby. The main thing is: torch does work. :D

---------- Post added at 01:53 PM ---------- Previous post was at 01:52 PM ----------

Guys there is a new nightly 22-12! When I flash this, will be the modded build.prop (edited with robotic call sound fix code) deleted and replaced by the stock one?
[Galaxy S III Original Android Development] Elton47:
Will be replaced with the stock one (that comes from 22-12)

47 Music - Enjoy Yourself ;]
[Galaxy S III Original Android Development] frudda:
Defenitly the best update released. Cause i had this problem with CM 13.

good work forkbomb444 :good:
[Galaxy S III Original Android Development] Logan:
Torch works here but If it doesn't work just restart mediaserver and it will work again noticed in social media apps like snapchat flash controlled by the app itself so somehow crashes.

To restart camera in terminal type:

Su

Killall cameraserver
[Galaxy S III Original Android Development] btud63:
CM13, CM14 works perfectly for my phone. Service boys are not from samsung. They say: there are many phones in service with this problem, EMMC was remote locked by SAMSUNG. Only phones with custom roms. Same problem that happen with iphones, remote emmc lock.

odin

<ID:0/023> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> BOOTLOADER_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CODE_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> MODEM_I9300XXUGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> CSC_I9300OXAGMJ9_1902166_REV00_user_low_ship.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/023> Odin v.3 engine (ID:23)..

<ID:0/023> File analysis..

<ID:0/023> SetupConnection..

<ID:0/023> Initialzation..

<ID:0/023> Erase...

<ID:0/023>

<ID:0/023> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

other try only with pit

<ID:0/023> Added!!

<ID:0/023> Odin v.3 engine (ID:23)..

<ID:0/023> File analysis..

<ID:0/023> SetupConnection..

<ID:0/023> Initialzation..

<ID:0/023> Set PIT file..

<ID:0/023> DO NOT TURN OFF TARGET!!

<ID:0/023> Get PIT for mapping..

and here frozen
[Galaxy S III Original Android Development] andrescm:
Mmmm there's a lot of documentation about restoring a PIT file. It's a very delicate process but I think you can recover your phone. I wish you good luck. I'm not buying the "remote locking by Samsung" story tough.
[Galaxy S III Original Android Development] baltics:
Unless it is stolen.
[Galaxy S III Original Android Development] dlcarvalho:
I tested the call volume only today and everything is fine in cm-14.1-20161222-NIGHTLY-i9300. Thanks a lot for all developers!!!

This ROM is so stable and fast for my daily use (I9300UBUGNK1).

Thanks again!!!
[Galaxy S III Original Android Development] amit.rooteds3:
I am on latest cm 13 snapshot... rom works fine... only problem i am facing is that some wallpaper apps cannot store images on internal as well on external sdcard. All camera apps fail to store images only open camerawrks which has inbuilt framewrk.... Is there any work around so that apps can read and write on internal and external sdcard....