yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Mini] papei:
The rom feels faster and more stable than before. Although I am having to re-connect my wifi every I reboot.
[Samsung Galaxy Mini] Venkatesh:
[MENTION=3877378]psyke83[/MENTION] sir, as you said, i switched to ath6kl wifi drivers(cm10.1 branch wifi drivers) on ics-plus branch, and wifi is broken.

here is my logcat:

Sources used:

kernel source(kitkat branch)

libhardware legacy

framework base

atheros_ath6kl-compat

atheros_wifi_libs

wpa_supplicant_8

wpa_supplicant_8_lib common device

And started service in ramdisk using below command
[Samsung Galaxy Mini] Venkatesh:
[MENTION=3877378]psyke83[/MENTION] sir, any help on this??
[Samsung Galaxy Mini] williamlaw:
hi,

how to remove unused languages ?

thanks
[Samsung Galaxy Mini] Venkatesh:
sorry, this build isn't multilingual, only english. If you want to try on other builds, then search for a tool called minicygwin_goptimize and use it.
[Samsung Galaxy Mini] sevenfolds:
play store shows NO CONNECTION and RETRY below it

but i am connected thru wifi

that was my only problem
[Samsung Galaxy Mini] Venkatesh:
click retry a few times...if it doesn't work, flash any other 4.1.2 gapps.
[Samsung Galaxy Mini] williamlaw:
only 20140619 version is available to download ??

i couldn't find 0719.

thanks
[Samsung Galaxy Mini] Venkatesh:
It was built on 26-06 and uploaded it on 19-07...simple
[Samsung Galaxy Mini] Venkatesh:
Success

I had some success getting ath6kl driver work on ics-plus branch. But wifi is turning off while the device goes to sleep mode, reconnects after screen on.

Obviously wifi tethering is broken.
[Samsung Galaxy Mini] mahedi_aiub:
Gallery is not working

Hello Venkatesh,

When I try to open Gallery or Camera, it shows "Unfotunately, Gallery has stopped working". I reflashed two times more but still it is not working. Is there anything to do?. Please help.
[Samsung Galaxy Mini] Venkatesh:
It is working perfect here, even i edited pics yesterday. Seems to be a bad flash. Check your zip. And have you flashed any zip or something?
[Samsung Galaxy Mini] mahedi_aiub:
I was on Stock when flashed this ROM. I will download this ROM again.
[Samsung Galaxy Mini] Venkatesh:
[MENTION=3877378]psyke83[/MENTION], thank you. WIfi is now working with ath6kl driver(cm10.1 branch config). I know am asking too much of you. I have a problem with omx on jellybean. Some mp4 videos are playing fine but some other mp4 videos are causing hotreboots(everything is good like media codecs,profiles and omx implementation in framework_av). I can fix it by taking surfaceflinger binary and libsurfaceflinger.so from old jellaxy build, i can't seem to find what's wrong with surfaceflinger, i even checked androidarmv6 cm10.1 branch for any fix. Unfortunately nothing related to omx in surfaceflinger. Perhaps, you can throw some light on it, can you? please.

uploaded logcat, if you want to have a look. (I am sure, it is related to surfaceflinger.)
[Samsung Galaxy Mini] Venkatesh:
I have some good news and some bad news. ath6kl wifi driver is now working fully and wifi tethering is fixed too. The bad news is that, as soon as a device connected to wifi tethering(our hotspot device), the device goes power off. I can't debug it since kernel panic debugging is disabled(helpless on this, apanic may not be compatible with our device type?) in the androidarmv6 kernel. Removed some crap from source. Everything is too good(without gapps though).
[Samsung Galaxy Mini] Venkatesh:
Edit: deleted.
[Samsung Galaxy Mini] psyke83:
Where is your source? The links you've provided are for MMB which hasn't seen an update since 2013. The crash from wifi hotspot is probably due to you using an incorrect wifi firmware. I added code to the ath6kl driver that lets the driver accept older firmware when the module parameter samsung_firmware=1 is used. However, the older firmware doesn't work with wifi AP, which is why wifi AP needed the samsung_firmware=0 parameter.

You should just stop using the old firmware (which I also did for CM11 recently) and use the newer firmware for both regular wifi and wifi AP.
[Samsung Galaxy Mini] Venkatesh:
I'll upload my source sometime later(slow connection). And thank you very much, wifi tethering is working now.
[Samsung Galaxy Mini] Venkatesh:
New version is on the way. Master key vulnerablity, fake id vulnerability, wifi tethering are fixed. Will post link and remaining changelog tomorrow.
[Samsung Galaxy Mini] Venkatesh:
New big update posted.

Changelog:

Switched to ath6kl wifi drivers.

Wifi tethering is fixed

Master key vulnerability, fake id vulnerability fixed. No need to install rekey app, master key and fake id apps from xposed candy shop.

Hardware accelaration added. You can activate it in performance settings-> hardware rendering.

Kernel changes. Fast charge supported. Install fast charge app from alin.p kernel thread. Thnx [MENTION=4525074]alin.p[/MENTION]

Forgot more changes.

Full wipe recommended. Use greenify, if want to flash gapps. A big thanks to [MENTION=3877378]psyke83[/MENTION] for helping me, all this while.

You must flash both packages. First flash rom and then flash surfaceflinger update
[Samsung Galaxy Mini] Venkatesh:
Any feedback?
[Samsung Galaxy Mini] alexanderq:
Well i tried it it was ok good speed no lag two random reboots but i'm using cm7 (void) for long time so i'm used to the speed of cm7 compare to cm10.I tried your rom because i like you work and to me your previous rom was smoother.
[Samsung Galaxy Mini] Venkatesh:
Random reboots? You flashed gapps? Is it complete system reboot or framework restart(hot reboot)? Because i have been using it from the day i compiled it and i had only one reboot at first day, no more reboots now a days.
[Samsung Galaxy Mini] sushil888:
using fm yesterday , didnt format system ,

no reboots yet, will report IF any issues.

THANKS
[Samsung Galaxy Mini] kyooby:
Hi. Tested for about 2 hours. Only fc close gallery 2 or 3 times . I was amazed by music sound quality -powerful and clear like diamond. keep up this good work.
[Samsung Galaxy Mini] Venkatesh:
If you can reproduce that issue and random reboots(if any), please try to take logcat and post here.

Thank you.
[Samsung Galaxy Mini] Venkatesh:
Note:

Hello everyone. You people must flash rom along with that surfaceflinger_update. If you don't flash surfaceflinger update, then you'll have soft reboots on some videos. I have seen download count of rom and surfaceflinger update, they are not same/equal. So, that means some users are not downloading surfaceflinger update. Please do flash both packages to avoid soft reboots on video playback.
[Samsung Galaxy Mini] OJ:
Which kernel, mods, scripts should I use with this ROM?
[Samsung Galaxy Mini] Venkatesh:
Don't use any other kernel as it'll break wifi. And i don't use any mods, scripts except int2ext. So, don't know about any scripts.

Just use greenify, don't flash gapps if you don't use them very often.
[Samsung Galaxy Mini] Alex_Gamer:
This rom is more faster and stable than cm9?
[Samsung Galaxy Mini] Venkatesh:
Anyone facing battery drain? Or is it me?

I had to revert charging logic commit to stop heavy battery drain in my case.
[Samsung Galaxy Mini] force_close:
I think battery is normal for me in this one day, but sometimes I have random reboots, it's very random, so no logcat for now, I think it's happen when device is using much resources(RAM/CPU)
[Samsung Galaxy Mini] Venkatesh:
Is it complete reboot or just framework restart? I had hot reboots(just framework restart) and it's very random here too. I don't know how to debug these random reboots. I hope this issue isn't present in slimbean.
[Samsung Galaxy Mini] force_close:
it went straight back to bootanimation, so framework restart?
[Samsung Galaxy Mini] Venkatesh:
yes, a hot reboot.
[Samsung Galaxy Mini] ZidanBlaster:
Wait a minute if i want install like script pure audio and pure graphic it can break wifi
[Samsung Galaxy Mini] Venkatesh:
No. It won't.
[Samsung Galaxy Mini] ZidanBlaster:
Waiting for final version good job:fingers-crossed:
[Samsung Galaxy Mini] Venkatesh:
Changelog later.
[Samsung Galaxy Mini] Venkatesh:
New version uploaded.
[Samsung Galaxy Mini] Venkatesh:
Use gapps this way:

1. Install gapps

2. Install playservices from a previous backup.

3. Freeze google apks like playservices, backup transport, contact sync, network location, picasa uploader etc except "playstore, google account manager, market update and google services framework" (basically freeze every google apk except these)

4. Add google a/c and use playstore normally.

5. If you don't have a playservices backup, let market download it and freeze it after that.
[Samsung Galaxy Mini] Venkatesh:
Updated Thread. Please do read thread carefully before asking/posting/reporting anything. Thank you.
[Samsung Galaxy Mini] ZidanBlaster:
What the changelog you changes
[Samsung Galaxy Mini] Venkatesh:
Random reboot fixes. And removed a few things from kernel and sources.
[Samsung Galaxy Mini] streambinder:
Hey [MENTION=4523093]Venkatesh[/MENTION], I'm streambinder, from MoltenMotherBoard team.

What about WiFi Tethering patch? I'm reworking CM10 sources, and would be glad to fix that feature as you already did.
[Samsung Galaxy Mini] Venkatesh:
Check your pm.
[Samsung Galaxy Mini] Venkatesh:
kernel 3 boots

[MENTION=3877378]psyke83[/MENTION] sir, as you said, i ported all required tls changes to jellybean(aokp-jb4.1.2) and the kernel is booting however display is not working(all black, i can receive calls etc). I think the problem is with gralloc. Logcat says

W/gralloc ( 118): MSMFB_METADATA_SET failed to configure alpha mode

And this happened when i used your resurrect the 3.0 kernel commit but it gave some compilation errors here and i fixed it by importing some code from msm_mdp.h(2.6 kernel header)

the code that i imported is

#define MSMFB_OVERLAY_COMMIT _IOW(MSMFB_IOCTL_MAGIC, 163, unsigned int)
#define MSMFB_METADATA_SET _IOW(MSMFB_IOCTL_MAGIC, 162, struct msmfb_metadata)

enum {
metadata_op_none,
metadata_op_base_blend,
metadata_op_max
};

struct mdp_blend_cfg {
uint32_t is_premultiplied;
};

struct msmfb_metadata {
uint32_t op;
uint32_t flags;
union {
struct mdp_blend_cfg blend_cfg;
} data;
};

And it got compiled fine and build completed.

With 2.6 kernel and setting "TARGET_NO_HW_VSYNC := true" gives no display problems.

The display source is here.

My boardconfig.mk(working tree with 2.6 kernel) is

## Qualcomm, display
TARGET_DISABLE_TRIPLE_BUFFERING := true
BOARD_USES_QCOM_HARDWARE := true
BOARD_NEEDS_MEMORYHEAPPMEM := true
USE_OPENGL_RENDERER := true
BOARD_EGL_CFG := device/samsung/msm7x27-common/prebuilt/lib/egl/egl.cfg
BOARD_USES_QCOM_LIBS := true
BOARD_ADRENO_DECIDE_TEXTURE_TARGET := true
TARGET_NO_HW_VSYNC := true

COMMON_GLOBAL_CFLAGS += -DQCOM_LEGACY_OMX -DQCOM_ICS_DECODERS
COMMON_GLOBAL_CFLAGS += -DQCOM_HARDWARE -DREFRESH_RATE=60
COMMON_GLOBAL_CFLAGS += -DQCOM_NO_SECURE_PLAYBACK -DBINDER_COMPAT
COMMON_GLOBAL_CFLAGS += -DFORCE_CPU_UPLOAD -DQCOM_ICS_COMPAT
#COMMON_GLOBAL_CFLAGS += -DMISSING_EGL_PIXEL_FORMAT_YV12 -DMISSING_EGL_EXTERNAL_IMAGE
#COMMON_GLOBAL_CFLAGS += -DMISSING_GRALLOC_BUFFERS

## Platform
TARGET_BOARD_PLATFORM := msm7x27
TARGET_ARCH := arm
TARGET_ARCH_VARIANT := armv6-vfp
TARGET_CPU_ABI := armeabi-v6l
TARGET_CPU_ABI2 := armeabi
TARGET_CPU_VARIANT := arm11
TARGET_BOARD_PLATFORM_GPU := qcom-adreno200
TARGET_SPECIFIC_HEADER_PATH := device/samsung/msm7x27-common/include
COMMON_GLOBAL_CFLAGS += -DTARGET_MSM7x27

This config works fine for 2.6 kernel. And removing "TARGET_NO_HW_VSYNC := true" for kernel 3.x is giving display problem. I don't know how it worked for kitkat display sources. I am attaching logcat and dmesgs.
[Samsung Galaxy Mini] psyke83:
Yes, most likely. Building the userspace libraries (such as gralloc) with headers that don't match the current kernel is causing your problem.

You should remove all kernel headers from the device include folder. This will result in the proper headers from the kernel source being utilized (via the integrated kernel building scripting). If for some reason it doesn't work (considering that it's an older branch), then a messy workaround is to manually update all headers in your device config to the 3.0x versions.
[Samsung Galaxy Mini] Venkatesh:
Yes sir. I did that. Manually placed all required kernel 3.x headers inside include folder. I just used a piece of code from kernel 2.6 msm_mdp.h header to fix compilation error. Where can i get legacy display drivers for jellybean? Is it possible to disable tls completely from kernel?
[Samsung Galaxy Mini] Venkatesh:
Hey, [MENTION=5889675]streambinder[/MENTION], i uploaded my tether patches here
[Samsung Galaxy Mini] Venkatesh:
Aokp 4.1.2 with kernel 3.0x is booting

Never mind. Got it working. Now aokp jellybean 4.1.2 is booting with kernel 3.0x.
[MENTION=5400898]HandyMenny[/MENTION], and [MENTION=3877378]psyke83[/MENTION], I don't see any micro-shutters when playing songs and i get some distortion(or shutter) when playing video. And the good thing is that the data transfer speeds are good in usb mass storage mode(transferred 800mb data in 3mins) as well as mtp. You want me to check anything?
[MENTION=3877378]psyke83[/MENTION] sir, is it necessary to delete ccache and clobber out folder, when there is any change in boardconfig.mk and some other makefiles:? Can you give some tips regarding this?
[Samsung Galaxy Mini] streambinder:
Thank you, mate. :)
[Samsung Galaxy Mini] vampelle:
where is the file
[Samsung Galaxy Mini] Venkatesh:
See post#2. Click cm_tass.
[Samsung Galaxy Mini] otosayam:
Flashed it using CWM from this link https://xdaforums.com/showthread.php?t=1342190&page=2 but installation always aborted after installing update. Any solution? Im new on this kinda thing :eek:
[Samsung Galaxy Mini] Venkatesh:
Try latest recovery for tass.
[Samsung Galaxy Mini] otosayam:
Latest CWM cannot be flashed from stock ROM, yet I can't flash this ROM from CWM version 4 & 5, any solution? :confused:
[Samsung Galaxy Mini] Venkatesh:
Flash below recovery from cwm 5.

https://xdaforums.com/showthread.php?t=2229411
[Samsung Galaxy Mini] otosayam:
When I click download it direct to Site can't be reached, expired maybe? :(
[Samsung Galaxy Mini] Venkatesh:
Let me check my external hdd for this. Please wait till tomorrow.
[Samsung Galaxy Mini] otosayam:
Do you find it?
[Samsung Galaxy Mini] Venkatesh:
Here you go.
[Samsung Galaxy Mini] otosayam:
Thanks for the twrp file. I've installed it, but when i flash your ROM it failed after "Updating partition details"

Here's the step I did:

1. reboot to twrp

2. wipe (factory reset)

3. install zip

Any suggestion?
[Samsung Galaxy Mini] Venkatesh:
Use cwm 5.0.2.8
[Samsung Galaxy Mini] otosayam:
Hey I've tried to redownload the cm10 file from mediafire, because the previous file I tried to delete the assert line on update-script. And I can flash the zip successfully using the newly download cm10 zip.

And it's on cyanogen mod boot animation now. How long does it take to boot? It's been 15 minutes I supposed
[Samsung Galaxy Mini] Venkatesh:
5-10 mins. Did you flash anything other than os zip?
[Samsung Galaxy Mini] otosayam:
at 1st i only flash the os zip, after 15 min without progress and stuck on boot animation, I reboot to recovery then flash gapps.
[Samsung Galaxy Mini] otosayam:
Thanks for the suggestion, made it work to flash it with CWM 5.0.2.8 , but the keyboard is missing somehow. :confused:
[Samsung Galaxy Mini] Venkatesh:
Yes. There's samsung keyboard somewhere here in this section. Download n flash it. You're good to go then.
[Xperia Z Q&A, Help & Troubleshooting] ekosus99:
:( guys.. I was update my c6603 to fw 101.. but why if I activated my wifi it's not working on play store.. it's normal for browsing.. but no connection if I wanna use play store.. would you like to help me guys...
[Xperia Z Q&A, Help & Troubleshooting] Ben Ling:
clear data of play store & google services
[AT&T Galaxy Note 3 General] altrikdout21:
Nope, I looked in and my 'leaf' pins were all properly shaped. I even slightly bent it to look more like yours, and still having GPS issues.
[AT&T Galaxy Note 3 General] SchecterRocker:
Sorry to hear that didn't fix it for you. Thanks for posting your results though.

If someone is feeling ambitious (and somehow doesn't care about their warranty), the other thing I was thinking is to clean off / polish the contacts that the leaf pins touch, but that's almost certainly a warranty-voider. Not to mention it could possibly damage or ruin the contacts.
[AT&T Galaxy Note 3 General] altrikdout21:
Switched my rom back to stock NB4 rooted, having no gps issues now (if I remember, it worked just fine on NB4 before). Bent pins may be a problem for others though.
[AT&T Galaxy Note 3 General] SchecterRocker:
Interesting, well at least it's working again.

I'd be stoked if someone else fixed their GPS because of a bent leaf pin, since it's such an easy and decisive fix.
[AT&T Galaxy Note 3 General] jay185:
wish i had seen this earlier. I had mine done just like what you did plus the pins from the backside of the motherboard. mine wont lock unless i am outside and had clear view of the sky (no signal if inside the car). and had to conclude that its the hardware and not the software. after doing all of those pins. i got lock in less than 3 secs!

damn note 3.

also, i had to spray those pins with an electronic contact cleaner before I put them back together :)
[AT&T Galaxy Note 3 General] SchecterRocker:
Fantastic, glad to hear it worked :good: Thanks for posting your results.
[AT&T Galaxy Note 3 General] hp79:
Is there a fix for the compass not working correctly? Sometimes when I'm driving, it makes it look like I'm traveling sideways. This is on GoogleMap. My GPS has been working fine since the first day.
[AT&T Galaxy Note 3 General] SchecterRocker:
My guess is that this fix should work for any subsystem that uses one of the leaf pins (of course only if said subsystem has a bent leaf pin).

We'd have to determine where the compass is located and if it uses the pins. Otherwise, I'm not aware of a compass fix. Mine has exhibited that behavior too. I'll report back if I find anything.
[AT&T Galaxy Note 3 General] evilpotatoman:
Thanks!

I was suffering from little to no GPS fix. Opened it up per your instructions to find that my gps pin wasn't bent, but the terminal to which it contacts was oxidized. I bent the pin up to ensure a tight fit and I marred the terminal with a razor to remove the oxidation. My GPS works flawlessly now.
[AT&T Galaxy Note 3 General] jay185:
would anyone know among those pins, where exactly is the gps antenna connected to?

ok nevermind. i figured it out. its the 2 pin at the top right (where the volume keys are)
[AT&T Galaxy Note 3 General] K-alz:
Where did you go? To an AT&T store or bestbuy?

My phone had no GPS issues at all until a couple of days ago after I dropped it flat on its back (with a thin cover on it) and picked it up with no scratch on it. Now I have NO GPS at all (I'm not sure it is because of the fall or something else. It fell several times before and it didn't mess my GPS). I tried every single GPS fix app in the Play Store that used to actually solve my GPS issues and nothing. I downgraded from KK to JB thinking it might have been KK that was causing the problem and also nothing. Now when I try to use my GPS, it hangs on "searching for GPS" forever. I'm thinking of re-flashing stock and un-rooting to take It back to them (I need your advice on where I should go, please). I don't want to start disassembling my phone first.

Thanks man.

from my 3rd beast of a phone..!!
[AT&T Galaxy Note 3 General] SchecterRocker:
I'm genuinely glad to hear this has helped at least 2 or 3 others! It was such an annoying issue for me that I hoped it would help someone else.

Great news! Let's just say that your MJ5 restoration thread has saved me more than once, so I'm glad if I can pay it forward in any way. :good: I'll modify the instructions to suggest checking for oxidized contacts like yours were. Thanks!

Thanks for reporting this. I actually bent the top left pin (where the power key is) to fix mine, so it would appear that either the top right or left pins could be causing issues for people.

I shipped my Note 3 to be repaired by Samsung Warranty Repair somewhere in Texas (free of charge, since it's still under warranty) (if that's what you're asking - I didn't get it repaired at AT&T or BestBuy). I am by no means an expert on this, but from what you've described my first guess is one of your pins got dislodged somehow (presumably from the fall). Honestly this procedure isn't overly difficult, but I understand if you don't want to crack open your phone. Until I did open my phone though, I was having nearly identical issues as you are (hanging on "searching for GPS" , the GPS Status app could only find 2 or 3 satellites instead of the usual 12-19, etc, etc, etc).

Samsung Warranty Repair bent my GPS pin, causing it to malfunction. While I sincerely want to recommend that you send it to Samsung to fix, just be aware that things can go wrong - I speak from experience.

Thanks again for everyone's responses!
[AT&T Galaxy Note 3 General] K-alz:
I appreciate it, man. I heard from some friends that it could be this http://www.androidpolice.com/2014/0...-services-are-experiencing-outages-right-now/

So before shipping my phone, I'm going to wait a little bit longer to see if this is the issue. I still have a long while on the warranty ;)
[AT&T Galaxy Note 3 General] AlCalavicci:
I would like to say this fixed my GPS on my AT&T Note 3.

I didn't have to un-clip the complete back, just the top left section enough to see the two antennas.

Now my GPS works normally.

Funny thing is my Note 1 had the same problem, which I fixed in the same way over 2 years ago..

What I am guessing is that when we put pressure on the phone we squish the antennas down so when the pressure is relieved they are no longer in contact.

Seems to be a design flaw in all generations of the Note phone.

Samsung should change how this connection is made, as the flaw will continue to occur.

thank you for the post!
[AT&T Galaxy Note 3 General] ko9pora:
Itworked but only for a few minutes

Unfortunately it didn't work... I also found that my note 3 is a little different to your photos where the two leaf-pins are mounted side by side.

I followed your procedure, found what I think must be the same leaf pins you refer to, but they didn't seem to be bent or misshaped. I bent them up slightly anyway,since I'd gone to so much trouble to tear it down, before reassembling the device.

When I first switched it on I thought I'd had a win: Using the 'GPS Status' app I quickly acquired 4/ 23 satellites, where normally I see 0/23 (or 0/xx) the xx number varies.

That soon increased to 11/ 19 and I thought yes its fixed AT LAST!!

For once I was even able to locate my device in Google Android Device Manager too - it rarely ever works. The only one that does is 'Where's My Droid' as it can find it using the WLAN and the mobile phone towers that my SIM is connected to. It appears that Google's ADM MUST use GPS only, because whenever Where's My Droid finds it via GPS (which isn't too often), Android Device Manager also works (finds it ok)... It was this constant failing of ADM which eventually brought me to the conclusion that the problem is to do with GPS (I've tried EVERYTHING to fix this over several months) and how I eventually found your post, which unfortunately doesn't seem to have helped me.

It does seem a bit odd though, that it worked for a few minutes after firing up the phone. :confused:

I just wonder if some component is failing once it reaches a certain temperature?

If so, I might was well forget it (warranty void - had to remove a sticker that was over screw # 12) and buy a new phone, but NOT a note 3! :mad:
[AT&T Galaxy Note 3 General] superdookie67:
I checked this with the recent gps trouble I've had with my tmobile version. I noticed mine were smashed down as low as they could be. Pulling them back up a bit, my gps does seem to be better now. I was wondering, would sticking some stock paper or anything under them help to keep them raised and connected to the other side?

And thanks so much for this post, I had been working on this problem forever.