yashsingh1/xdaforums huggingface dataset:
[Galaxy S III Android Development] Scorpionea:
First of all rom boots for me as always

but now the hard part lol

Ive tried dirty flashing from 0413 to 0417 and all went ok no FC messages or anything like that,but yet again Play Store has disappeared from phone,then i tried booting back again to recovery again dirty flashing the rom and gapps and got constant FC of everything,coudn't do much only wipe everything again :eek::eek:

its my fault why i didint backup my data before dirty flashing,but ok

i really hope u will do something on next build for backlight buttons ,thats the only annoying thing besides dirty flashing issues:p:p
[Galaxy S III Android Development] fir1996:
[MENTION=5231921]Gokulbalram[/MENTION] could make flashable zip for android n status bar it will be very nice or at least can you tell me how to copy it from your previous build
[Galaxy S III Android Development] Gokulbalram:
I linked a layers theme for that a few posts ago
[Galaxy S III Android Development] Scorpionea:
when i try to add new contact i get Unfortunately,Contacts has stopped message every time

[MENTION=5231921]Gokulbalram[/MENTION]
[Galaxy S III Android Development] Gokulbalram:
Works here, how exactly did you add the contact?
[Galaxy S III Android Development] Scorpionea:
It seems it was theme issue,just tried different theme and its working now

Sorry for false info mate :)
[Galaxy S III Android Development] Gokulbalram:
That's alright :)
[Galaxy S III Android Development] Gokulbalram:
Advanced Display integration coming back
[Galaxy S III Android Development] cobrarx8:
I am on this rom for 4 days now. Jumped from 04-13 to 04-17 through clean install and have to say, that I am impressed no problems or FC's at all except at setup wizard with Google Play Service. Everything is running as it should.

Only thing I noticed is the battery life on 04-17 seems to be not as good as 04-13 or the official cm13. I bought a new Anker battery few days ago and had always up to 4 hours display on time with regular usage. On 04-17 version I could reach only 3 hours.

Can't wait for the next version

thx Gokulbalram
[Galaxy S III Android Development] Scorpionea:
Im using 4 year old battery and have pretty good battery 3,30 SOT

on stock firmware I can get above 4hours

And I agree with all u said, phone is running like butter no issues and no random reboots at all..

Only one thing I notice is phone is heating a bit more while just browsing Tapatalk or watching videos ect
[Galaxy S III Android Development] rp158:
I get with an 2year old battery (~15% loss in the meantime) up to 6.5h SOT. With a very slim system. Doesn't matter, whether SlimLP or HaxynoxMM or crDroidMM (even with Boeffla zzmoove batteryplus).

I noticed heating (bottom right) and immediately fewer SOT with LightningBrowser, probably by grewing data&cache. With NakedBrowser all fine now.
[Galaxy S III Android Development] Gokulbalram:
Even I noticed heating on the stock kernel. I'll probably change the kernel in order to avoid future problems :)

Meanwhile you guys could indeed use Agni like I say. No heating in Agni
[Galaxy S III Android Development] xpduyson:
Hi, could you add support for ext4 format sd card? I don't wanna switch to fat32 because I have some really big file in sd card.
[Galaxy S III Android Development] Scorpionea:
Its very confusing what AGNI kernel to choose really hah

Can u post zip name of AGNI kernel that u recommend to the letter please?
[Galaxy S III Android Development] Gokulbalram:
This should work: http://xdaforums.com/devdb/project/dl/?id=18070
[Galaxy S III Android Development] Scorpionea:
And works just fine

Thx Goku ! ����

edit: ok it worked just fine,but after flashing AGNI i lost root access so i had to flash back latest SuperSU beta that was working just fine and after flashing it and booted back to rom my wifi is now completly disabled and i cant turn it on at all...

will try something if not will wait for your next release and wipe all again :(
[Galaxy S III Android Development] Gokulbalram:
That's absolutely weird behavior. Could you explain how exactly you flashed everything step-wise?
[Galaxy S III Android Development] Scorpionea:
downloaded AGNI kernel from the link,booted to recovery flashed AGNI booted back to rom,everything was okey but SuperSu binary was missing so i booted back to recovery and flashed again beta 2.71 SuperSU got back root access but wifi is dead
[Galaxy S III Android Development] Gokulbalram:
Try this one then: http://xdaforums.com/devdb/project/dl/?id=16884
[Galaxy S III Android Development] Scorpionea:
I've just setup everything as before ,I think will pass on this one

Don't wanna mess things up again ,at least not twice per day :)

Thx anyway [emoji14]
[Galaxy S III Android Development] cobrarx8:
I flashed exactly the same kernel, no root loss. Everything alright. Didn't know, what happened there to you Scorpionea ;)
[Galaxy S III Android Development] rp158:
I tried Agni 5.9.9 and 5.10.1, with the same behaviour as [MENTION=799933]Skorpione[/MENTION]a :( and AgniApp hangs after asking SU-rights. Restored my backup and am on stock-kernel again.

May be related to TWRP? I use 3.0.1.0.

Clock ..settings FC's still (the app, not any widget)
[Galaxy S III Android Development] Gokulbalram:
What is going on :? Probably Chipset related stuff acting up again. Also if I'm not wrong, SuperSU 2.6+ is system-less root isn't it? I use 2.52

Also [MENTION=5040297]rp158[/MENTION], you tagged the wrong person :P
[Galaxy S III Android Development] Scorpionea:
As long stock kernel don't have any issue it's fine with me

Just wanted to test Agni cuz of heating the phone on normal usage

I'm glad it works for some,but since same thing happen to [MENTION=5040297]rp158[/MENTION] then there is a real issue

It could be issue with supersu version that I've installed or with agni kernel dunno..
[Galaxy S III Android Development] rp158:
Found a solution: flashed ROM clean, then Agni 5.10.1 and SU 2.65, wiped cashes and boot. All fine, clock-settings included :) witchy.
[Galaxy S III Android Development] Scorpionea:
did u boot into the rom after clean wipe? or u just flashed agni later on ? and u flashed stable SuperSu 2.65 right? all in one flash or one by one? :D
[Galaxy S III Android Development] rp158:
[MENTION=5606779]Scorpionea[/MENTION]: flash ROM, kernel, SU in this order whitout boot between.
[Galaxy S III Android Development] Gokulbalram:
I've seen how you redownload apps one-by-one, why don't you use Titanium Backup?
[Galaxy S III Android Development] Gokulbalram:
Anyway, new build is up, grab it here

Changes:

-Bluetooth was broken last build. It's fixed now :)

-Advanced Settings is back

-Keypress backlight now has a timeout, default is 3 second. (I'll port it to Advanced Settings later)
[Galaxy S III Android Development] Mr.RooT:
[MENTION=5231921]Gokulbalram[/MENTION], I want to ask. Exfat still not working?
[Galaxy S III Android Development] Gokulbalram:
I did bring about some exfat changes, could you test it? Thanks
[Galaxy S III Android Development] Scorpionea:
All working good in 0421 build,as always

But I don't like what u did on backlight button, now whenever I press on screen they are turned on and since we all constantly touching screen lights are also turned on

It was ok in previous builds where they would light up only if u touch them

Tried few things including gravitybox to disable it but no luck so far

Other then that amazing job so far ! ;)
[Galaxy S III Android Development] Gokulbalram:
That's weird, I'll try looking into it
[Galaxy S III Android Development] Android-Banjarmasin:
Bootloop fixed?
[Galaxy S III Android Development] Mr.RooT:
[MENTION=5231921]Gokulbalram[/MENTION], unfortunately exfat still not working :(

Also exfat binaries missing too (make_exfat and fsck_exfat).
[Galaxy S III Android Development] Gokulbalram:
I'll further look into this :)

Thing is, exfat isn't open source so I'm not sure how to work around this. But I'll still look at my options :)
[Galaxy S III Android Development] Mr.RooT:
You can try look into cm sources. In cm exfat fully working ;)

EDIT: Here it is (I hope) https://github.com/CyanogenMod/android_external_exfat/tree/cm-13.0
[Galaxy S III Android Development] rp158:
[MENTION=5606779]Scorpionea[/MENTION]: switch navkey-lights off in AgniSettings
[Galaxy S III Android Development] Scorpionea:
Well I haven't flashed Agni yet on new build,still using stock kernel but will think about it

Thx

Edit: flashed AGNi kernel again but this time I used SuperSu 2.52 unlike the previous one (system less root) and all is working OK

Didn't lost anything and this time everything works great,no more issues with backlight buttons [emoji6] [emoji9]

Edit 2: can anyone confirm if stock camera works ? I have no clue if it worked before flashing AGNI,but other camera apps works fine only stock one gives Camera has stopped message
[Galaxy S III Android Development] blackaxeV1.2225:
Anyone try this on murata?

Team Flare S4 Deluxe?
[Galaxy S III Android Development] Gokulbalram:
What on earth is this behaviour :(

Tried the Stock cam?
[Galaxy S III Android Development] Gokulbalram:
(XDA One derp)
[Galaxy S III Android Development] Scorpionea:
yes that is the main point of my edit2 post lol

stock camera gives error message all other camera apps from store works like snap camera ect:p
[Galaxy S III Android Development] Gokulbalram:
Oh I misread the that. Stock Cam works fine here though
[Galaxy S III Android Development] Scorpionea:
Are u on stock or AGNI kernel? It's no biggie really as camera works with other apps

Just downloaded Google camera and works fine too
[Galaxy S III Android Development] Gokulbalram:
AGNi, it has certain settings I really need to keep the device on considering I don't use it much
[Galaxy S III Android Development] Gokulbalram:
I read that you've got Snap. Could you link me to a zip? I've one but it doesn't work lol :P
[Galaxy S III Android Development] Scorpionea:
will send u a PM :)
[Galaxy S III Android Development] yoahmad1995:
I'm willing to switch from cm13

But got 2 questions.

1st: will it work on murata? I cant test unless it worth it I'm on a trip and using my 3g so limited bandwidth. :(

2nd: if I backup CM's camera... Will it work on this ROM?
[Galaxy S III Android Development] sunny1234590:
Yes, it will work on Murata Chipset.

As far the snap camera is considered I guess you gotta contact [MENTION=5606779]Scorpionea[/MENTION]
[Galaxy S III Android Development] yoahmad1995:
This ROM is a keeper only one bug tho... It could read my exfat SD Card so restoring my CM13 backup and will use this again when exfat is working. :)
[Galaxy S III Android Development] Scorpionea:
Why me lol[emoji14]

I've talked about snap camera from playstore and he is asking for cm camera ,completely different camera app but similar name
[Galaxy S III Android Development] sunny1234590:
Ohh... My mistake then. Sorry for the wrong info.

---------- Post added at 02:27 PM ---------- Previous post was at 02:20 PM ----------

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

See if this works for you.
[Galaxy S III Android Development] sunny1234590:
http://xdaforums.com/showthread.php?t=3362920

See if this works for you.

---------- Post added at 02:28 PM ---------- Previous post was at 02:27 PM ----------

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

See if this Snap Camera works.
[Galaxy S III Android Development] yoahmad1995:
I can't I reverted back to cm13 as this ROM not yet support exfat.

Things I noticed so far..... This is the first ever ROM on S3 that not lags when moving while zoomed out in clash of clans.

But its performance in Clash of Clans same as CM13 on agni kernel so I hope the dev will stick to current kernel as its the smoothest at least for me.

Only one bug tho I noticed the device heat up a little bit on normal useage.

Not sending videos via snapchat. Also colors are blue. So i had to use HW and OMX from Nameless but still blue.

Otherwise, best ROM you could ever get on S3.
[Galaxy S III Android Development] Gokulbalram:
I did include everything necessary for exfat but apparently it still isn't enough. I'll keep looking
[Galaxy S III Android Development] sunny1234590:
Why is the QS drawer like that of Lollipop style and not of Marshmallow style? [MENTION=5231921]Gokulbalram[/MENTION]
[Galaxy S III Android Development] Gokulbalram:
That's the stock MM SystemUI
[Galaxy S III Android Development] sunny1234590:
Wait, what? That's MM system ui but why is CM13 QS drawer different from CM12 QS dialer?

I mean, there's two different system ui, no?
[Galaxy S III Android Development] Gokulbalram:
Could you send me a comparison of what exactly you mean
[Galaxy S III Android Development] sunny1234590:
Will send a PM
[Galaxy S III Android Development] Scorpionea:
U will need to flash AGNI kernel and then in AGNi control app u can disable it backlight keys

Search for Agni in this thread
[Galaxy S III Android Development] lyamine:
Hola :)

always bootloop here :(

Juste out of curiosity !! can someone explain to me why it works for some and not in the other, we have the same smartphone, right? !!
[Galaxy S III Android Development] Scorpionea:
Same smartphone yes,but hardware inside the phone is not the same(different wifi chip,camera module ect)..that is why it works for some and don't for others

I'm sure goku will find a fix for bootloop soon
[Galaxy S III Android Development] lyamine:
thank you, I finally have the answer to this question which I have to say my time digging head

(Y)
[Galaxy S III Android Development] sunny1234590:
[MENTION=5231921]Gokulbalram[/MENTION] The SlimLP ROM worked on all S3 (murata or semcosh chipset). It was also an AOSP ROM right? If Yes, you think you can find the bootloop fix from there?

I don't know whether the thing I am saying even makes sense or not. Just trying to help you.
[OnePlus 2 Q&A, Help & Troubleshooting] devveda:
can someone help me please, i have tried to install cm13, and i did a clean wipe, now it is saying no os installed, and i couldnt even find the restore package !!! how can i load os into my oneplus two, as yo all knw we dont have a external memory card, am nt sure how to load os into phone now !!! some please help !!
[OnePlus 2 Q&A, Help & Troubleshooting] WhyOrean:
Are you on TWRP 3.0.x.x?

If yes, then go to Mount Section, enable MTP.

Connect to your PC, transfer desired ROM.zip and flash.

If no TWRP, then reboot to BootLoader/Fastboot

Download latest TWRP from official website, then flash it using command:

fastboot flash recovery twrp.img

fastboot reboot (keep holding vol- to enter TWRP)

where "twrp.img" is name of the recovery file.
[OnePlus 2 Q&A, Help & Troubleshooting] devveda:
yes i tried to enable mtp, but nothing was shown in computer to transfer !!!
[OnePlus 2 Q&A, Help & Troubleshooting] devveda:
thank god :D used sideload and installed stock rom, its fine and all set nw !!!!
[OnePlus 2 Q&A, Help & Troubleshooting] WhyOrean:
Try with Latest TWRP build.

And at worst case scenario use Qualcomm Recovery Tool to go back to OOS 2.1.1, as already you have lost all your data.

---------- Post added at 12:19 PM ---------- Previous post was at 12:18 PM ----------

Oki Good, Enjoy!
[OnePlus 2 Q&A, Help & Troubleshooting] devveda:
Can you help me with something? When I again try to reboot my device in recovery I couldn't find the twrp recovery or any type of recovery, after installing the twrp, it's not rebooting, am getting a message saying "booting.... Failed <remote: dth not found>, I couldn't install twrp recovery :( can u help me with this?
[Galaxy S6 Q&A, Help & Troubleshooting] xDroidZz:
I just got this phone 2 days ago.

While i was flashing around. i tried to flash from 5.1.1 (noble rom) to 6.0.1 S7 edge port also noble. but it seems i'm stuck at Boot logo.

Flashing "G920FXXU3DPB6_G920FDRE3DPB1_G920FXXU3DPB6_HOME.tar (6.0.1)" gives me an error as well. it fails to flash in odin.

but lucky i got twrp backups from my previous roms lol.

Thanks for helping :D :)

Also a question. is Lollipop performing better than Marshmallow? :good: Specially the battery here is the question.
[Galaxy S6 Q&A, Help & Troubleshooting] forumber2:
Marsmallow is better than Lollipop on S6.

Can you post the Odin error log here?
[Galaxy S6 Q&A, Help & Troubleshooting] xDroidZz:
<ID:0/006> Odin engine v(ID:3.1005)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

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

<ID:0/006> Firmware update start..

<ID:0/006> SingleDownload.

<ID:0/006> boot.img

<ID:0/006> NAND Write Start!!

<ID:0/006> cache.img

<ID:0/006> cm.bin

<ID:0/006> hidden.img

<ID:0/006> FAIL!

<ID:0/006>

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

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

This shows up actually...... thanks for your reply mate
[Galaxy S6 Q&A, Help & Troubleshooting] forumber2:
If your phone is G920F, then flash this ROM.

Make sure you selected PIT file on Odin

(PIT file included in ROM zip)

https://docs.google.com/uc?id=0B3U72O5ZZ8z-STJiWWJmR2hPM1U&export=download

After you've flashed it, flash the Marsmallow ROM via Odin (without PIT file).

Aftery you've flashed Marsmallow ROM, make factory reset via recovery.

Done!
[Galaxy S6 Q&A, Help & Troubleshooting] xDroidZz:
I've managed to flash it.

Downloaded a firmware from samfirmware. included were (AP,PDA,BL, etc) which worked as it should.

Thanks for your help anyway!
[Galaxy S 4 Q&A, Help & Troubleshooting] yioulas:
I've read many posts by i9500 owners on the echo issue. The problem is that the person calling can hear an echo of him/her self issue. I couldn't find a solution. I find it really strange that an issue as serious as this one hasn't been dealt with yet. What's the point of releasing new custom roms for the i9500 with this issue unresolved.

The only custom roms that don't have this problem are stock based roms which suck bigtime.

I really love cyanogenmod and other aosp roms and would love to be able to use them. Any developers out there. We really need your help. This is an issue that all i9500 owners have . I've installed cyanogenmod on 3 i9500 phones just to make sure it's not just my phone. The echo is always there

Please help
[Galaxy S 4 Q&A, Help & Troubleshooting] yioulas:
I finally found a way to fix the echo. This works on cyanogen based roms which have the same mixer paths xml file as cyanogen mod. However on many roms the mixer paths file looks different and I haven't figured out how to do the same thing.

So for anyone who has the same problem. Find this line

ctl name="Earpiece", "Builtin Mic", "Back Mic" /> remove "Back Mic" from the line so it looks like this ctl name="Earpiece", "Builtin Mic" />

Find this line <ctl name="Noise Gate Threshold Volume" value="3" /> and change the value from 0 to 3

Now delete the following lines

<!-- Route all mics via LHPF1 -->

<!-- need to move modifier field -->

<ctl name="LHPF1 Mode" value="High-pass" />

<ctl name="LHPF2 Mode" value="High-pass" />

I'm not sure which one fixed the problem and I didn't have time to check yet.

So for anyone with the i9500 echo problem try it.

I've installed slim rom 5.0.2 for i9500 on which the mixer paths file looks exactly like cyanogenmod. For some reason on 12.1 cyanogenmod nightly builds my bluetooth doesn't work. My phone pairs with the bluetooth device but there is sound only for a couple of seconds and then it goes off. Any idea why? Anyone else with this problem? I tried it with the original unmodified mixer paths to make sure it doesn't have anything to do with the changes I made. I also tried different modems.

Bluetooth works fine on other cyanogenmod based roms like GearCM

Any developers out there can you take a look at what I did and explain why it fixes the issue? Why haven't they fixed it on cyanogenmod nightly builds.

Also many roms like GearCM for example, mixer paths looks completely different. The microphones are not named build in mic, back mic etc... I can just see a bunch of inputs and I have no idea which ones correspond to which microphones. Also I can't find the "<!-- Route all mics via LHPF1 -->" section. Can someone explain how to do the same thing on these roms?

Anyway, now my phone finally works without an echo even at full volume, but I would love to be able to tweak GearCM 5.1.1 or 6.0.1 version in the same way but like I said the file looks completely different. Any help appreciated.
[Galaxy S 4 Q&A, Help & Troubleshooting] AzizbekN1:
Is there anyway to fix cm13

I have echo only speakerphone mode

Earpeace is ok without echo

---------- Post added at 04:58 PM ---------- Previous post was at 04:09 PM ----------

I think you disabled back mic

Thats way you dont have echo

Only buildin mic works

---------- Post added at 05:00 PM ---------- Previous post was at 04:58 PM ----------

I have idea with cm13

Can you test it ?
[Galaxy S 4 Q&A, Help & Troubleshooting] yioulas:
never tried cm13. I still get some echo at high volume but its really soft. tmyou said you have an idea? I can test it. maybe disable some mic for speakerphone mode

which build of cm13 are you refering to. gearcm 13?
[Galaxy S 4 Q&A, Help & Troubleshooting] yioulas:
there is also something called AEC which stands for acoustic echo cancellation. Maybe thats what we need to enable but dont know how. audio_effects.conf has some lines which refer to aec, agc automatic gain control and ns noise suppression. They are commented out by default but just removing the comments doesnt seem to work
[Galaxy S 4 Q&A, Help & Troubleshooting] AzizbekN1:
I already tested cm13

No luck

I edited audio_effects.conf file

Disabled backmic but nothing

I dont know What to do

Could you look cm13 mixerpath.xml file ?
[Galaxy S 4 Q&A, Help & Troubleshooting] yioulas:
are you on cm13 now? when i installed gearcm 13 mixer path looked different and I couldnt figure it out
[Galaxy S 4 Q&A, Help & Troubleshooting] AzizbekN1:
Im on gearcm13

I changed all values in mixerpath

Not helped

Only alberto knows how to fix

But he isnt answering
[Galaxy S 4 Q&A, Help & Troubleshooting] AzizbekN1:
So lets help eachother this mixerpath with disabled dualmic speakerphone

You know what to do

Plz test it

Btw its for gearcm13

I know you like me want to use Marshmalow
[Galaxy S 4 Q&A, Help & Troubleshooting] AzizbekN1:
Could you give a link for that thread that you found solution for echo fix
[Galaxy S 4 Q&A, Help & Troubleshooting] yioulas:
I didn't find a solution in any thread. I found possible solution but nothing that works. I just played around with mixer paths xml until I found something that works. Btw I downgraded to cm 12.1

Can you test it yourself and let us know? You can just back it up to your external sdcard and place your modified file in /etc with root explorer overwriting the original. Reboot and if it doesn't work just replace it with the original again that you've backed up on the external sdcard.

If you can't do it I can try backup my cm12.1 and install cm13 just to test it. Btw my camera didn't work with gearcm13 and some other stuff I don't remember. Does it work for you? Which is the latest build of gearcm13?

I've read somewhere about an application called Samsung Noise Reduction that allows you to enable or disable noise reduction on cyanogenmod based roms. Some people say it made a difference for them but it didn't make any difference for me. Give it a shot maybe it works for you.

To install it you have to download amazon underground. It's an amazon app similar to google play store that you can download apps from. Then find an application called "Samsung Noise Reduction"

Make sure you select "Apps and Games" category when searching for it. Install the free version and try to enable/disable noise reduction to see if it makes a difference.

What did you change?
[Galaxy S 4 Q&A, Help & Troubleshooting] AzizbekN1:
OK then I'll try & report

Thank you for ideas
[Galaxy S 4 Q&A, Help & Troubleshooting] yioulas:
Looking forward to it
[Galaxy S 4 Q&A, Help & Troubleshooting] AzizbekN1:
The app is not working

Plz search "how to turn off noise reduction for cm13" or advice something

I'll search too

I have 99.9% stable cm12.1 but I want cm13

It is most coolest& fastest rom I have ever used