yashsingh1/xdaforums huggingface dataset:
[Samsung Captivate Glide] Viktor0610:
Problems while copying files to the device :/

I have problems while I try to transfer files to the device in mass storage mode.

It connects to my laptop, but after a while, the yellow android logo become green, and I lost the connection with the device. I have to press the "Turn on USB storage" button again. But it loses the connection very often.

I tried a clean install, but the problem persists... :(

One more thing. I tried to copy the same files in recovery, after I mounted the USB storages. It worked fine, no interruptions, and the speed was extremely fast -5-12 MB/s. :D
[Samsung Captivate Glide] bubor:
what recovery/version do you use?
[Samsung Captivate Glide] Viktor0610:
This one: http://xdaforums.com/showthread.php?t=2007198
[Samsung Captivate Glide] bubor:
could you upload 2-3giga at once? as I see it stop after a while to write down.
[Samsung Captivate Glide] Viktor0610:
I uploaded 1.6 GB in both cases
[Samsung Captivate Glide] bubor:
Put new release:

http://dualhoki.vim.hu/bubor/dev/10.2/M1/cm-10.2-20131109-UNOFFICIAL-i927.zip

I could increase storage performance, I've tested with "dd" command, I think you will see difference in apps ( for example: take photo ). Please report back.

I dont know why usb storage is slow. Your recovery has kernel 2.6, I wont use with 4.3 android.
[Samsung Captivate Glide] germa89:
It's necessary to wipe all system? Or only cache? Thanks a lot!
[Samsung Captivate Glide] Viktor0610:
No, you don't have to. ;)
[Samsung Captivate Glide] Viktor0610:
There is no change with the mass storage connection losing problem. I will test the other fnctions.
[Samsung Captivate Glide] bubor:
I wrote full my internal/external sd card, and not storage break.

Could you send me dmesg and logcat?
[Samsung Captivate Glide] Viktor0610:
I think it will be (mine :D ) user error or one of my installed programs causing the problem. :D

I am copying 1.6 gig's of files right now (after a full wipe) without any problems . :)

Sorry for the "fals" alarm. :o
[Samsung Captivate Glide] hazard1nc:
My only question is does anyone notice any errors with tethering. I wanna tether WiFi but worry it won't work. Could someone confirm that it works :) thank you.

---------- Post added at 11:53 AM ---------- Previous post was at 11:25 AM ----------

Gapps needed? First install so I just wanted to ask.
[Samsung Captivate Glide] Neuntoter:
I have tethered many times with all versions since it was fixed many months ago. Never had an issue.

It is a bit slow to connect, you may have to wait a few minutes even before your laptop/whatever will register that it has internet connectivity, but it does and will eventually work.
[Samsung Captivate Glide] Viktor0610:
I never had any issues with tethering.
[Samsung Captivate Glide] ll81702:
Will this also fix textnow voip calls?

Or, VOIP calls in general?

Tried to install this in recovery and it gave an error that my phone is not a sgh-i927 and it is a sgh-i927

Did I do something wrong?
[Samsung Captivate Glide] bubor:
wrong recovery.
[Samsung Captivate Glide] ll81702:
Can you explain? What recovery should I use?
[Samsung Captivate Glide] bubor:
Use other, I think it would work with TWRP.
[Samsung Captivate Glide] ll81702:
I use textnow and this fix did not work for that application, I assume this is skype specific?

I loaded skype and this file - also tried removing the file also

Skype just loops - opens and closes

Trying to call or text crashes skype.

With the file installed textnow audio doesn't work at all.
[Samsung Captivate Glide] PghSportsGuy:
Bubor, I have an issue that I hope you can help me with. Everytime I attempt to flash this ROM I cannot get to connect my WiFi. I get a brief notification showing available WiFi networks available and that's it. Normally there would be a notice in my notification tray that I would click and my browser would open allowing me to enter the necessary login info. That does not happen and when I try to click the browser icon with WiFi on I get the page is unavailable. Any insight as to what I need to do? I always do a clean wipe/install using CWMR. I have been using your 9/13 PAC build and really want to use your CM build. Thank you.
[Samsung Captivate Glide] AndyYan:
[MENTION=5112223]bubor[/MENTION] Yup, glad to report that the network traffic indicator is fixed! Thanks for your patience, good day :)

Sent from Samsung Captivate Glide @ CM10.2
[Samsung Captivate Glide] bubor:
I dont know you can do that in CM. Does Connect to wifi from settings work?
[Samsung Captivate Glide] AndyYan:
Our school happens to use the same login procedure, and I can confirm that it works on the latest build. Could be some problem with the WiFi you're connecting to.

Sent from Google Nexus 4 @ Android 4.4 KRT16M
[Samsung Captivate Glide] LaizureBoy:
I have wifi issues as well. After flashing the ROM, I connected to my google account and cyanogen mod account with no problems, but them when I go to the play store or browser, it says no connection or proxy connection didn't work. I too, am at school.

Then, I rebooted, and got a bootloop, with the Samsung logo
[Samsung Captivate Glide] ll81702:
voip w/fix still not working

voip with the fix properly installed still does not solve the voip issue for me
[Samsung Captivate Glide] S-trace:
Use Skype 4.3, latest 4.4 version don't work on this ROM
[Samsung Captivate Glide] santimaster2000:
Wait wait wait, this voip fix doesn't break gsm calls ?
[Samsung Captivate Glide] AndyYan:
Can anyone tell me about their experience with GPS? On all CM10.2 builds I've tried including the latest, GPS finds many reliable satellites but rarely locks onto any of them, and even if it locks, it takes about 5 minutes to do so and only locks onto a small amount of available sats. Under the same configuration (same gps.conf, same network, also no AGPS), CM10.1 locks onto ALL sats in 10 seconds. Had to switch back to CM10.1 because of this. I'm not sure if it's something on my end... :(

Sent from Samsung Captivate Glide @ CM10.1.3
[Samsung Captivate Glide] bubor:
read this: http://xdaforums.com/showthread.php?t=2451609

There are many GPS "fix" in market, what makes faster lock.
[Samsung Captivate Glide] AndyYan:
If you mean adjusting gps.conf to local values (for me, Asia), yes I've done that on both CM10.1 and 10.2 (I even directly copied 10.1's localized gps.conf to 10.2). If the "fix" in the market are all about gps.conf then I doubt if they'll be of any help...

Sent from Samsung Captivate Glide @ CM10.1.3
[Samsung Captivate Glide] otoinsa:
The BOOT LOOP issue disappeared for me after I used a different CWM recovery version.

Maybe most people are stuck on old CWM (I had something like 5.0.2.7 before), thats why they get the boot loop?

It would be a good idea to put a note on the thread beginning, maybe it works for someone else as well.

:cyclops:
[Samsung Captivate Glide] bubor:
I put recovery ( find in OP).

edit: its broken :(
[Samsung Captivate Glide] mrk2815:
bubor, i clicked on the link that you gave in op for recovery. there is no recovery file when i clicked on the link. Maybe you forgot to update the directory to include the recovery. i dont see it there. i see all the new updated roms but no updated recovery. Can you plese uploade the new updated recovery or give a link to grab the recovery.
[Samsung Captivate Glide] bubor:
lol, you are too lazy to read back even one post.

Aye, its empy, thats whay its "strike" out.
[Samsung Captivate Glide] mrk2815:
what isthe version of clock work mod recovery. i dont se a link ot grab. Can you please uploade it again or give a link to grab it please. i appreciate all of the development on the glide. keep up the great work.

---------- Post added at 02:47 PM ---------- Previous post was at 02:21 PM ----------

I'm sorry, not lazy. I did not see it. Until I went back through the threas from the few days which I had not read, sorry I won't assume from now I will read all the posts before asking eh question. I'm truely sorry about. I would like to report no boot loop issues. I followed all of your instructions and its working flawlessly. One issue I have noticed is with the clock when its at 11 am and when it goes to 12 pm on the clock instead of reportin 12pm its reporting 12 am. So i'm not sure if this is a bug or how can I fix this one. I tried to look in the date and time settings to uncheck an check the automatic date and time from network . I will wait to se if the Cm 10.2 rom from 11-13-2013 does the same thing or not then I will report it again. But this is one of the fastest rom for the glide. I have ran all the rom from the past none of them is as fast as this one. Keep up the great work on this one.
[Samsung Captivate Glide] kdrumwork:
I try this rom and workink all ok guys
[Samsung Captivate Glide] santimaster2000:
Bubor, please send me the sources you used to build this ROM, I have a few ideas on how to fix the BT and VOIP Audio.
[Samsung Captivate Glide] bubor:
you can found github.

.repo/local_manifests/roomservice.xml

<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="cm-10.2" />

<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="cm-10.2" />

<project name="buborh/android_device_samsung_i927" path="device/samsung/i927" remote="github" revision="cm-10.2" />

<project name="buborh/kernel_samsung_i927" path="kernel/samsung/i927" remote="github" revision="stock" />

<project name="buborh/android_vendor_samsung_i927" path="vendor/samsung/i927" remote="github" revision="master" />

<project name="buborh/android_vendor_google" path="vendor/google" remote="github" revision="cm-10.2" />

</manifest>
[Samsung Captivate Glide] santimaster2000:
OK, thanks for the info, I'll finish to sep up my build enviroment, and then I'll get started with the testing, but, for now, I must go to sleep, because, it's 8 AM and I'm STILL AWAKE.

PD: One last thing, before anybody gets their hopes up, this will be my first approach to android, I'm a technician, not a developer, so, I might get everything fixed or I might be unable to even get the device to boot.
[Samsung Captivate Glide] xtacb4:
kernel

Hi bubor, what kernel sources are you using with this builds, could you post the link please? Thank you :D
[Samsung Captivate Glide] bubor:
Just read one or two post back.
[Samsung Captivate Glide] otoinsa:
There is a mistake in physical keyboard mapping.

The alt + sym key should offer a smiley/emoticon chooser, just like the sym key pressed alone, but only with smileys.

Instead it produces a single character.

That said, the latest build works great :) This rom is my daily now.
[Samsung Captivate Glide] bubor:
can you try cm-10.2-20131118-UNOFFICIAL-i927.zip ? http://dualhoki.vim.hu/bubor/dev/10.2/cm-10.2-20131118-UNOFFICIAL-i927.zip
[Samsung Captivate Glide] Androide3:
This rom work great but my wifi conexion works very slow i dont know if it is a issue or maybe i only have a trouble with my internet...i very happy with this rom thanks to bubbor ...and sorry for my bad english
[Samsung Captivate Glide] Viktor0610:
Is it normal to get that "script succeeded: result was [/system]" message after the installation? :confused:

As far as I remember I didn't see this after the previous installations...
[Samsung Captivate Glide] Androide3:
Screenshot capture is available in ths rom? I cant found the option
[Samsung Captivate Glide] AndyYan:
Settings-Buttons-Power menu-Screenshot. After that, long press POWER key and screenshot option will come up.

---------- Post added at 02:51 PM ---------- Previous post was at 02:46 PM ----------

*sigh* The GPS issue is back. Days ago I heavily tweaked my gps.conf so that it could lock in 20 seconds, but as of today it went back to the previous state - a lot of satellites with good signal, but not a single one gets locked on. What's more worrying is that when I tried to update AGPS data via 3rd-party apps, XtraData Downloader said that "XtraData Injection is not supported", and A-GPS Injector Free even said that "Unable to request A-GPS data upload (not supported)". Both seem to indicate that this ROM doesn't support AGPS... What the hell... I'm starting to wanna sell my Captivate Glide because frankly, GPS is one of the only uses for it, yet I have to give up the latest Android OS to make it functional :(
[Samsung Captivate Glide] xtacb4:
There is also other way, press POWER and VOLUME - at the same time, instant screenshot.
[Samsung Captivate Glide] otoinsa:
Sorry for the late reply,

I just tried it with full wipe, the issue is still present.

I tried remapping the button myself, but to no avail.

Seems like any major changes to .kl and .kcm files disable the SMTP keybard and make it fall back to another.
[Samsung Captivate Glide] AndyYan:
[MENTION=5112223]bubor[/MENTION] could you spare a minute and take a look at this GPS issue...:

I've done extensive experiments today about the performance of GPS on CM10.1 and 10.2 (both are the latest build), and results are confusing...

1. CM10.1, clean wiped, totally untouched (no gapps) - locks in about 30 seconds.

2. CM10.1, clean wiped, unnecessary system apps deleted - same as above.

3. CM10.1, all personal apps installed, unnecessary system apps deleted - same as above.

4. CM10.1, clean wiped, GPS.conf localized and optimized - 15 seconds.

5. CM10.2, clean wiped, totally untouched (gapps are there by default) - no lock in 5 minutes.

6. CM10.2, clean wiped, unnecessary system apps deleted (no gapps) - same as above.

7. CM10.2, all personal apps installed, unnecessary system apps deleted (no gapps) - same as above.

8. CM10.2, clean wiped, GPS.conf localized and optimized - same as above.

9. CM10.2, all personal apps installed, unnecessary system apps deleted (no gapps), GPS.conf localized and optimized (I've tried everything to make it work...) - ...still, same as above.

Even under the same environment and settings as CM10.1, 10.2 wouldn't lock onto anything. Additionally, many GPS testing softwares told me that the phone "doesn't support Xtra Data Injection" or even "doesn't support AGPS by hardware". I'm really starting to doubt that there are fundamental bugs in this ROM that prevents GPS from working correctly.

Sent from Samsung Captivate Glide @ CM10.1.3
[Samsung Captivate Glide] bubor:
would you try another hal?

http://dualhoki.vim.hu/dev/gps.tegra.so-2.3.6 and https://github.com/TheMuppets/propr.../i9103/proprietary/system/lib/hw/gps.tegra.so

put device /system/lib/hw/gps.tegra.so

GPS doesnt work my phone at all ;(

I'm not sure its relevent, but I dont use apn config anymore, try this https://github.com/spyke555/android_device_samsung_i927/blob/master/configs/apns-conf.xml
[Samsung Captivate Glide] AndyYan:
Thank you sir for the response! I immediately did more experiments with the HALs (CM10.2's, CM10.1's, the 2.3.6 one and the i9103 one), all done with a cleanly wiped CM10.2 build.

The result... the i9103 one picks up satellites relatively faster than all others, but other from that, none managed to do a stable lock in 5 minutes.

Will experiment more with CM10.1 and maybe stock ROM and report back later.

EDIT: Tested the HALs on a clean CM10.1. The original HAL that comes with CM10.1 managed to lock in 15 secs. 2.3.6 HAL in 1 minute and locked onto less satellites than the CM10.1 one. i9103's HAL never locked. Looks like HAL swapping isn't that effective :(

Oh, and what's the deal with apns-conf.xml? I'm sure my APN is properly configured with "supl" type. Plus, as I last investigated, AGPS isn't available on my carrier (maybe I'm wrong).

Sent from Google Nexus 4 @ CM11
[Samsung Captivate Glide] mara-:
Hi,

These are probably a noob question, but I hope someone can help me.

Currently I'm running stock Android 4.0.4 +LiteKernel 4.0-20130121. According to Got Brickbug ? v1.2 application, my phone has a bad chip.

1. Am I safe on current kernel, so I can flash CM10.2? And can I do whipping cache, davlik and factory reset in CWM?

2. Does CM10.2 contains some other kernel?

3. If I do a nandroid backup with my current setup mentioned above, can I safely restore without brickbug kicking in?

Thanks in advance for replies.
[Samsung Captivate Glide] Padillla:
ROM is awesome and battery last for almost 2 days, however, I can't get tethering to work. Just grays out on settings when I activate it... and WiFi tether app shows errors starting AP, besides GPS not locking.

Is it possible just to push tethering libs and GPS libs from other ROMs (like PA, AOSP 4.1.2 tethering on that ROM is very efficient).
[Samsung Captivate Glide] sb56637:
Hmmm, I just tried the WiFI hotspot and the USB tether feature with 20131113-m1 and they both worked like a dream.
[Samsung Captivate Glide] shimbob:
My phone has a "probably" bad chip (type valoom) but that hasnt prevented me from installing this rom.
[Samsung Captivate Glide] mara-:
What about kernel? which kernel do you run?
[Samsung Captivate Glide] sb56637:
I think I found a bug. Yesterday I was using the GPS, but turned it off before going to bed. The next morning it has lost over 20% of the battery (normally it's about 3% during that same time period) and according the battery stats the GPS was still active and consuming power. I verified that the GPS was indeed disabled both in the pulldown toggles and in the main system settings.
[Samsung Captivate Glide] mara-:
[MENTION=5112223]bubor[/MENTION]

I would appreciate your reply about the things I asked. I did some additional searching, and if I figured correctly, CM rom has CM kernel. But is it safe from brick bug? What about TRIM? It can also cause brick bug, so is the fix for that included in this CM?
[Samsung Captivate Glide] bubor:
Kernel has MMC_CAP_ERASE removed, and rom has BOARD_SUPPRESS_EMMC_WIPE := true

I think that you asked for, but I dont know too much about it.
[Samsung Captivate Glide] mara-:
Thanks, that answer some of my questions. It should be safe to flash, but this leaves TRIM. Can you check out this page:

http://wiki.cyanogenmod.org/w/EMMC_Bugs

A quote from page:

So I think there should be something else in kernel or ROM to make sure trim does not trigger brick bug, maybe you can figure out what?

Thanks again.

EDIT: Maybe the patch is what is mentioned under MAG2GA TRIM bug in the link above? Can you verify if the patch is included?
[Samsung Captivate Glide] bubor:
Mine is http://wiki.cyanogenmod.org/w/EMMC_Bugs#Samsung_eMMC_secure_erase_bug

cat name

VAL00M

/sys/devices/platform/sdhci-tegra.3/mmc_host/mmc0/mmc0:0001 # cat manfid

0x000015

/sys/dev

https://github.com/Kick-Buttowski/s...mmit/e8a245b89bcb2729d871a2216f6b8bdbba2a1e76

and

BOARD_SUPPRESS_EMMC_WIPE is true.

As I see VAL00M isnt affected with trim bug.
[Samsung Captivate Glide] mara-:
Thanks for checking this out. I just checked my phone, and I also have VAL00M, so I should be safe.

Greetings,

mara-
[Samsung Captivate Glide] mara-:
[MENTION=5112223]bubor[/MENTION]

I just flashed this, and I must say wow! I'm really impressed. Thank you very much for your efforts and I hope you continue to work on this. One question. With LiteKernel I had ability to change CPU voltage and now I can't. Previously I overclocked my Glide to 1.2 and lowered voltage to keep it cool and it worked fantastic. So, would it be possible to add support for changing CPU voltage in CM?
[Samsung Captivate Glide] Androide3:
You can do that in this rom, cpu up to 1.4
[Samsung Captivate Glide] mara-:
I know I can overclock, but I can't lower the voltage.
[Samsung Captivate Glide] bubor:
try this: 20131124 version.

What app do you use for voltage control?
[Samsung Captivate Glide] mara-:
I use system tuner, there was an option for it while I was on ICS + LiteKernel, but now option does not appear. I'll try the new build as soon as possible.
[Samsung Captivate Glide] Krllo:
Bubor, the log you asked for

the log is attached. i tried turn it on on charger, isnt worked. now im sending the log
[Samsung Captivate Glide] roothorick:
If this is the issue I think it is...

Our phone is physically incapable of charging while CPU-OFF; the SoC is inextricably involved in the charging process. The normal "off" charging process with the official ROM would start the full-fledged TouchWiz kernel, which would, instead of booting the Android system, start a minimal system that simply shows a battery icon. The phone is NOT off when in this mode; the entire SoC inclding CPU and GPU is fully operational and only the radios are offline.

It's currently believed that the bootloader plays an important part in radio initialization, but it only does its part during a "full" boot (showing Samsung logo) and not a "charge only" boot (showing battery with static spinner). With official kernel this wouldn't be an issue, as its response to the power button while in "off and charging" mode is to simply reset the device, restarting the bootloader in "full" mode and initializing the radio properly.

AOSP kernels don't check the "charge only" flag, and go into the OS regardless; since the bootloader never initialized the radio, you're stuck without service.

It probably won't ever be fixed, as this phone is now officially End-of-Life even for Cyanogenmod (thanks to our very dated and proprietary Tegra 2 SoC). So, do one of the following workarounds:

1) Power on the phone while unplugged even if the battery is 0%/"dead". Plug in the phone once you see the Samsung logo (signifying a "full" boot).

2) Just reboot the phone. The bootloader will come up in "full" mode and your radio will be back.

If you actually care that much, you can approximate the TouchWiz "charging while off" behavior by simply turning on airplane mode. If there isn't much CPU activity, it's effectively the same thing.
[Samsung Captivate Glide] bubor:
what is your problem?

What exactly do you do?

What do you expect to get?
[Samsung Captivate Glide] sb56637:
Can I upgrade CM10.2 M1 to the newest current build without doing a full wipe? Just format /system and wipe caches and flash the newest version? Thanks!
[Samsung Captivate Glide] bubor:
yes, just flash enought.
[Samsung Captivate Glide] dEhiN:
Superuser pin problems

Hi bubor (or anyone else who might know the answer to my question); I've upgraded to CM10.2 M1. But in my previous installation I had created a PIN for Superuser access and I now don't remember it! When I upgraded, I did a format/system wipe (including cache and dalvik cache) - I backed up everything before this. After upgrading I restored just data. But that also restored the Superuser PIN. Is there a way to bypass this? To selectively restore all 3rd party apps + data and not CM preferences? Or even better, to not restore the Superuser PIN? Thanks.
[Samsung Captivate Glide] bubor:
You can always change settings in recovery.

I would start delete superuser* from /data/data/com.android.settings/databases from recovery.

Mount data, use file manager to browse there, click on the file, delete it.
[Samsung Captivate Glide] dEhiN:
I don't see an option in CWMR to use the cmd to browse files. Any other suggestions? I suppose I can use File Manager in CM but I'm not sure if File Manager has superuser permissions. If it doesn't, I can't give it permission because of the PIN issue. What do you think I should do?
[Samsung Captivate Glide] Krllo:
I dont understand.

you always says: i cant do anything without log, bla bla bla...

and now you ask what i expect...

i dont understand anything about developing ROMs.

i just tried to help. if you cant do anything, just ignore it.
[Samsung Captivate Glide] AndyYan:
TWRP recovery has a built-in file manager. Flash it via Odin, mount /system in it, go to the built-in file manager and delete that file, PROFIT ;)

Sent from Google Nexus 4 @ CM11