yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] Venomusdragon:
Lol, no haha, if the problem isn't there when you switch to the stock battery but reappears when you put in the enhanced one, its gotta be the new battery

sent from my SGS2 running AOKP, eh...
[Samsung Epic 4G Touch] montana3:
ok, i get wht you saying but soemtimes it does it with thefactoy battery i have to take the battery out of the phone, becuase if not the message of charging paused, voltage too high...and it appear like the usb is connect , so that why i ahev to discconect the battery to.. the factory battery.....
[Samsung Epic 4G Touch] Venomusdragon:
OK sorry for misunderstanding friend, sounds to me like yes something is possibly causing your connections in your USB port connector to touch, I would take the phone to a retailer and have them check it out, sprint is usually pretty cool, they clean my phone for free every time I take it in, it may be as simple as that

sent from my SGS2 running AOKP, eh...
[Samsung Epic 4G Touch] montana3:
that will be great, but a huge problem lol, i have it flahshed to boost mobile...
[Samsung Epic 4G Touch] Venomusdragon:
Ah, well I'm not sure than, sprint still may clean it seeing as they own boost, unless I'm way outdated and that has changed?

sent from my SGS2 running AOKP, eh...
[Samsung Epic 4G Touch] vash469:
Yea i get the Charing paused voltage to high also

So your saying that sprint may clean it for me i dont wanna go in there and they cite me on water damage as some cases I seen on the net I know it's prolly corrosion cause its not a contact problem for me like right now it's fine but it will prolly happen after i take my phone off the charger in the morning
[Samsung Epic 4G Touch] timmetal6669:
I had this very problem myself. Its definitely the usb port going out. I called sprint ahead of time and made the complaint, then went to the sprint store and used my.insurance. They tested the phone and had a new phone to me within 2 days.
[Samsung Epic 4G Touch] vash469:
Did that getting..... my new phone on Friday
[Asus  Eee Pad Transformer Prime] wrunk:
So my EEE Pad Transformer TF101 died (a very sad day for me). The warranty I purchased with the Transformer gave me an instant replacement and as it happens an upgrade to the Transformer Prime 32GB TF300T with the dock.

I have observed 2 things.

1: when transferring files from my Patriot 16GB USB 2.0 thumb drive the files transfer quickly at the expected speeds (around 10mbs). This is consistent regardless of the file format on the USB drive.

2: When transferring files from my Corsair 64GB USB 3.0 thumb drive the files transfer painfully slow. It takes around 10 minutes to transfer 300mb. I have tried NTFS and exFAT for file formats and neither improve the performance.

My question is, is this common? Has anyone else come across this problem. Is there a compatibility issue with 64GB thumb drives?

Any thoughts would be appreciated.

Thanks
[Asus  Eee Pad Transformer Prime] briian_:
I don't know if this is relevant but my hard drive is also a USB 3.0, and I just tested by copying a 700mb movie file, and it did it in probably under a min or possibly a little bit over. But definitely no where near 10 min for sure.

I have unlocked my prime and flashed Custom roms on it. Not sure if the custom roms plays a part in that effect?

Hope that helps.
[Asus  Eee Pad Transformer Prime] Parastie:
I found copying files to/from USB drives to be very slow regardless of the drive. I have an 8GB sandisc drive that was ridiculously slow. The fix was (sadly) unlocking and going with Androwook rom. Now it's at least comparable to my windows tablet.

You can try unmounting/remounting the drive from settings. It appears to be related to the IO performance issues you can read alot about. The JB update for Prime should hopefully fix the issues by bringing in newer drivers from nvidia.
[Asus  Eee Pad Transformer Prime] wrunk:
Thanks for the information and tips. I guess I will use my old 16GB USB key for now and hope that JB solves my problem. It is strange to me that the 64GB USB Key worked fine in the original TF101 and dies in the newer TF300T.

Thanks again.
[Samsung Galaxy Nexus] netslum:
Is there any mods for a dual booted nexus? like safestrap for bionic.
[Samsung Galaxy Nexus] brettofamerica:
The only thing I know of is bootmanager but I personally have never tried it. Would be very interested in hearing if anyone else has because I would also like to try dual booting!
[Samsung Galaxy Nexus] GldRush98:
Not sure what safestrap is, but you know Android has a safe mode boot, don't you?

Hold the power button to get the shut down menu. Tap & Hold on Power Off. It will prompt you if you want to reboot in safe mode.
[Samsung Galaxy Nexus] netslum:
I came from a bionic. They developed a dual boot feature into a bootstrap since the boot loader is locked. I'm going to talk to the guys at Droid hive and see if they can make one for the gnex. I'm not quite sure how that would impact kernal flashing and radios, but I will present the idea to them
[Samsung Galaxy Nexus] Zepius:
You want to use boot manager. It will do what you want
[Samsung Galaxy Nexus] netslum:
Soon, I tried using boot manager. Its slow and unresponsive at times. I couldn't get a from to load once. I did it as suggested by the FAQs and waited 30 minutes. Nothing. The sgs2 has a dual boot partition using cwm recovery. Gonna put out a request or try to mod the source code.
[EVO 4G Q&A, Help & Troubleshooting] KSUJedi:
Saw that the 3D now has a CM9 port with working wimax. As far as I know, they use the same wimax chip. I'm a total newb, and probably know know nothing about how this works, but any chance that might breath new life into the possibility of OG Evo with working wimax on CM9/10?
[EVO 4G Q&A, Help & Troubleshooting] SSD4130:
Bump for support.
[EVO 4G Q&A, Help & Troubleshooting] Notorious:
jmztaylor is already trying to port wimax since toast and the team released the code. But toast said it might not work on MTD devices
[Android Q&A, Help & Troubleshooting] flamebo:
I have a Star A3 running 2.3.4

The question is more of a general question to the android platform, I don't suspect the hardware matters.

I am running Ttorrent Pro on the phone, and the speeds are less than impressive (everyone else says the same thing) I am on a very fast connection, using speed guide I literally max out the speedtest servers in my local area (20Mb up/down which is the max they let you go to, I would get 100/100 if my speedtest server would allow it) and I have a port forwarded correctly.

but anyways, what I have noticed is, when wake the phone, and open the torrent application the speeds are down to around 3Kbps if I leave it open the speeds immediately start ramping up to 200-300Kbps if I keep it awake.

So this makes me think, when the phone is sleeping a lot of the connections are being closed, or when the phone is asleep it won't try and open new connections to new peers (and the current peer list may go stale while its asleep)

this is with all torrents, now the exact same torrent on another PC with a DSL connection (3Mb down 300Kb up) is downloading faster than the phone.

Are there any developers out there than can explain what processes are going to sleep that may be useful to keep awake for downloading, and also what are the tcp limits on the phone, ie. max open connections, max half open etc?
[Android Q&A, Help & Troubleshooting] kuisma:
When the phone clocks down its CPU, of course it'll make your apps run slower. Is that so strange? Leaving it connected to the power seems to keep the CPU at high speed on my devices at least, but I guess that may vary from phone to phone.

A torrent client have a quite intelligent algorithm choosing the numbers of peers it connects to depending on several parameter such as effective bandwidth and so, and if your device lower its CPU frequency, the bandwidth will suffer.

There's also another possibility. Running the task in the background, i.e. without its main window visible, and Android may kill the app. More than 15 hidden apps (e.g. background running), and Android begin to kill the oldest. This is quite invisible to you, because Android must restart them as well. The problem with a torrent app, is that setting up the torrent, connecting to pears etc takes a while, and if the app gets killed and restarted once up running, you'll never achieve great speed. If this is the case, leaving the main activity visible prevents Android killing/restarting it.
[Samsung Epic 4G Touch] tvar2005:
My phone keeps showing that it is charging even though it is not. When I run touchwiz roms it says charging paused voltage is too high. On AOSP roms however it just shows the icon as if it is charging but the battery is not on a charger nor is anything charged into the usb port. Also this kills my battery fast bc it doesn't allow my phone to sleep properly. Anyway I can fix this myself or do I need to bring it to a Sprint Store?
[Samsung Epic 4G Touch] MoHoGalore:
From what I've read, it's either a dirty or defective charging port. Try cleaning but you may have to take it in.
[Samsung Epic 4G Touch] Venomusdragon:
I'll agree with this, seems to be the common theme

sent from my SGS2 running AOKP, eh...
[Samsung Epic 4G Touch] az18zz:
Does your rom has cwm recovery? If so just go in it &clear the battery status
[Samsung Epic 4G Touch] tvar2005:
I cleared the battery stats a long time ago I took it in today and they are replacing it. I had to revert it back to stock and unroot my phone but now Im excited to root the replacement when it gets here lol! Thanks guys
[Galaxy S II Original Android Development] codeworkx:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.1 (JB), which is designed to increase performance and reliability over stock Android for your device.

#include
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*
* Submitting bug reports on nightly builds is the leading
* cause of male impotence.
*/

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Device: https://github.com/CyanogenMod/android_device_samsung_i9100

Common: https://github.com/CyanogenMod/android_device_samsung_galaxys2-common

Kernel: https://github.com/CyanogenMod/android_kernel_samsung_smdk4210

CyanogenMod: http://github.com/CyanogenMod

http://teamhacksung.org/wiki/index.php/CyanogenMod10:How_to_build

If you're going to reuse our work, which we're doing for free, be fair and give proper credits.

This is the only payment we're really demanding and we deserve it to be mentioned because of the countless hours we've put into this project.

Open-Source doesn't meant Out-of-Respect!!!

http://xdaforums.com/showthread.php?p=29280423

To be clear, posts without detailed instructions on how to reproduce a problem and without attached logs will be ignored.

Always provide android (adb logcat) and kernel logs (adb shell dmesg).

If it's a RIL problem we would need a radio log (adb logcat -b radio), too.
[Galaxy S II Original Android Development] hillbeast:
When will the Team Hacksung repo be sent upstream to CMs repo?
[Galaxy S II Original Android Development] thracemerin:
When its ready.
[Galaxy S II Original Android Development] hillbeast:
I was more asking 'what state does the system need to be in before it is able to be included in the CM repo', not an ETA.
[Galaxy S II Original Android Development] Znuf:
Thx for your post, a lot.

I had download the source code but, i'm not able to find

~/android/system/device/samsung/i9100.

In

~/android/system/device

i just have :

common generic google sample ti

I make something wrong?
[Galaxy S II Original Android Development] hiepgia:
Check your local_manifest.xml. Do you add it right?
[Galaxy S II Original Android Development] Znuf:
i use this one.

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
</manifest>
[Galaxy S II Original Android Development] PieR:
I added I9100 projects by hand :)

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="jellybean">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
<project name="teamhacksung/android_device_samsung_i9100" path="device/samsung/i9100" remote="github" revision="jellybean" />
<project name="teamhacksung/android_device_samsung_galaxys2-common" path="device/samsung/galaxys2-common" remote="github" revision="jellybean" />
<project name="teamhacksung/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" remote="github" revision="jellybean" />
<project name="TheMuppets/proprietary_vendor_samsung" path="vendor/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_hardware_samsung" path="hardware/samsung" remote="github" revision="jellybean" />
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" revision="ics" />
</manifest>

I dont know if it's enought since I'm still compiling.

Inviato dal mio GT-I9100 con Tapatalk 2
[Galaxy S II Original Android Development] hiepgia:
. /build/vendorsetup.sh

lunch cm_i9100-userdebug

mka bacon recoveryzip recoveryimage checkapi

It will do the rest

Or do in this guide

http://teamhacksung.org/wiki/index.php/CyanogenMod10:How_to_build
[Galaxy S II Original Android Development] Znuf:
Thank's i'll try :P
[Galaxy S II Original Android Development] PieR:
it's called i9100 now :)
[Galaxy S II Original Android Development] pulser_g2:
Try this commit: http://review.cyanogenmod.com/#/c/20065/
[Galaxy S II Original Android Development] pulser_g2:
It's merged now anyway, just repo sync :)
[Galaxy S II Original Android Development] Znuf:
Thank's a lot. It's working great :highfive:
[Galaxy S II Original Android Development] golcheck:
Recent update to android_frameworks_native breaks the build...

...
frameworks/native/libs/ui/GraphicBuffer.cpp:132:67: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
target thumb C++: libui <= frameworks/native/libs/ui/PixelFormat.cpp
target thumb C++: libui <= frameworks/native/libs/ui/Rect.cpp
target thumb C++: libui <= frameworks/native/libs/ui/Region.cpp
target thumb C++: libicuuc <= external/icu4c/common/bmpset.cpp
frameworks/native/libs/ui/FramebufferNativeWindow.cpp: In constructor 'android::FramebufferNativeWindow::FramebufferNativeWindow()':
frameworks/native/libs/ui/FramebufferNativeWindow.cpp:100:19: error: 'framebuffer_device_t' has no member named 'numFramebuffers'
frameworks/native/libs/ui/FramebufferNativeWindow.cpp:101:19: error: 'framebuffer_device_t' has no member named 'numFramebuffers'
frameworks/native/libs/ui/FramebufferNativeWindow.cpp:102:34: error: 'framebuffer_device_t' has no member named 'numFramebuffers'
make: *** [out/target/product/i9100/obj/SHARED_LIBRARIES/libui_intermediates/FramebufferNativeWindow.o] Error 1
make: *** Waiting for unfinished jobs....
Elapsed: 4 min(s) 45 sec(s)
[Galaxy S II Original Android Development] Doopliss:
I am having trouble building. I've followed the instructions up to syncing the repo but on the next step (lunch cm_i9100-userdebug) at first I got "No such file: cm_i9100-userdebug", then after doing . build/envsetup.sh I get:

build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/i9100/cm.mk]]: "device/*/i9100/cm.mk" does not exist. Stop.
Device i9100 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for i9100 not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifest.xml.
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/i9100/cm.mk]]: "device/*/i9100/cm.mk" does not exist. Stop.

** Don't have a product spec for: 'cm_i9100'
** Do you have the right repo manifest?

There is no /build/vendorsetup.sh (which someone suggested earlier). I tried . ./vendor/cm/vendorsetup.sh but that didn't seem to do anything (and I tried adding a i9100 line but still nothing).

Anyone know what I'm actually supposed to do?

Edit: Am I meant to add that extra stuff to the local manifest which someone posted earlier?
[Galaxy S II Original Android Development] golcheck:
Yes, use that extra stuff. Should work then

To build:

./build.sh i9100
[Galaxy S II Original Android Development] Doopliss:
Bleh, now I'm getting "fatal: The remote end hung up unexpectedly" when I try to sync. Guess I must have reached some usage limit...

Thanks for the answer, anyway.
[Galaxy S II Original Android Development] marcellocord:
Guys, I've done something wrong while editing some apk sources. I've compiled CM10, took freaking 111 minutes, and realised that I've forgot something while editing one java file. How can I compile only the apk? I tried "make "apk"", but came up with odex and the apk was missing a lot of resources.
[Galaxy S II Original Android Development] Testraindrop:
This is most likely because of this commit;

http://review.cyanogenmod.com/#/c/21925/

Either exclude it in your build or use the revert mentioned in the comments. ;)
[Galaxy S II Original Android Development] MrMarques01:
Hey, I just tried to build the ROM on my ubuntu machine, unfortunately without any luck.

I followed the non-experimental instructions of the link in OP, and after executing ./buid.sh i9100 I got this:

http://pastebin.com/AsMWsn3K
[Galaxy S II Original Android Development] codeworkx:
look at your error messages.

gcc can't be executed. check if the files at prebuilt exists. probably a bad or incomplete sync.
[Galaxy S II Original Android Development] madquack:
This is off topic most likely and definitely not dev related but was something changed recently to where the source files are stored? New server perhaps or more bandwidth available? I have been able to download entire CM10 source in a few hours now compared to a few days ago where it would take at minimum 3 days.

Isn't there some sort of variable to prevent people from hogging up bandwidth meaning it'll block some people from downloading too much stuff or does that depend on what repo I am syncing from? Does the "owner" of the report delegate how much bandwidth is available to end users like me who are downloading? I have changed nothing on my end and my ISP hasn't involuntarily bumped up my download speeds for free haha.

This brings me to my next question for those of us who are able to make changes to the source (gerrit patches) when suitable and deemed necessary, who decides what gets ultimately approved or denied do the device maintainers of cyanogenmod take of vote to decide on a case by case basis or are all submissions approved?

Blah blah blah, Just trying to better myself in order to benefit the community and not be one of the leeches like 99% of the people on here.
[Galaxy S II Original Android Development] codeworkx:
1) github.com. ask them.

2) device maintainers care about device specific changes, cm lead devs about everything else
[Galaxy S II Original Android Development] E:V:A:
I'm very curious to know why TV out doesn't work and probably will never be supported??

I think we have what we need to get that working, we know how the hardware works, so what's the problem??
[Galaxy S II Original Android Development] bluefa1con:
This was answered in the discussion thread

Use search on that thread
[Galaxy S II Original Android Development] golcheck:
compiling breakes during kernel build without error message....

make[1]: Leaving directory `/root/cm10/kernel/samsung/smdk4210'
make -C kernel/samsung/smdk4210 O=/root/cm10/out/target/product/i9100/obj/KERNEL_OBJ INSTALL_MOD_PATH=../../system ARCH=arm CROSS_COMPILE="/root/cm10/prebuilts/misc/linux-x86/ccache/ccache /root/cm10/prebuilts/gcc/linux-x86/arm/arm-eabi-4.6/bin/arm-eabi-" modules_install
make[1]: Entering directory `/root/cm10/kernel/samsung/smdk4210'
INSTALL drivers/cpufreq/cpufreq_smartass2.ko
INSTALL drivers/net/wireless/bcmdhd/dhd.ko
INSTALL drivers/samsung/fm_si4709/Si4709_driver.ko
INSTALL drivers/samsung/j4fs/j4fs.ko
INSTALL drivers/scsi/scsi_wait_scan.ko
INSTALL fs/cifs/cifs.ko
DEPMOD 3.0.36-CM-gd654360
make[1]: Leaving directory `/root/cm10/kernel/samsung/smdk4210'
mdpath=`find out/target/product/i9100/system/lib/modules -type f -name modules.order`; if [ "$mdpath" != "" ];then mpath=`dirname $mdpath`; ko=`find $mpath/kernel -type f -name *.ko`; for i in $ko; do mv $i out/target/product/i9100/system/lib/modules/; done; fi
mdpath=`find out/target/product/i9100/system/lib/modules -type f -name modules.order`; if [ "$mdpath" != "" ];then mpath=`dirname $mdpath`; rm -rf $mpath; fi
Elapsed: 53 min(s) 2 sec(s)
[Galaxy S II Original Android Development] kalgecin:
Error message should be higher up. This happens because of several threads running. If first thread crashes, and prints error, the other threads continue to print stuff to the screen so you need to find it.
[Galaxy S II Original Android Development] thracemerin:
Technical blockers? Samsung, period, end of story.

Want more details? There are pages and pages of why in the various CM threads around this very forum that explain why when an OEM has no interest in supporting AOSP or the open source community and are only interested in developing for their architecture with their bugs, their workarounds, their incompatible drivers, this should give your a good start as to why it won't and can't work. When you send code into a driver that you don't really know what inputs to send, and even if by some random chance you magically send the right info into this abyss of proprietary code you still have the fun challenge in getting something out the other side that is remotely comprehensible, let alone usable with any of the other code necessary for it to function usefully.

My take, you neither have the ability or desire to help, you simply came here to flame the developers in some veiled attempt to pretend you are superior to them in any way, why? My guess, probably they rejected your amazing (at least to you) submissions on gerrit and you took this personally. You may want to argue this with me, but doing so proves me right, so consider carefully before doing it.