yashsingh1/xdaforums huggingface dataset:
[Samsung Epic 4G Touch] EL_G15:
Ok here are my screencapture for FD24.

I just updated to FD26 using NoData It looks like preserve all my settings so I'm gonna give it a shot tomorrow , I will report back.
[Samsung Epic 4G Touch] im0rtalz:
CM9 when you finally get phone to sleep nice and soundly :)
[Samsung Epic 4G Touch] LordLugard:
....or just stick with GB roms that work and stop suffering yourself these ICS leaks.
[Samsung Epic 4G Touch] Dudebowski:
Some of us have flash addiction. Some of us enjoy bring Guinea pigs for development. I for one just left my last phone running cm7 and couldn't bear the austerities of a stock ROM. The GB twiz hacks are alright, but it doesn't feel like home to me.
[Samsung Epic 4G Touch] JohnCorleone:
A few of us are actually doing better with battery on ICS. One problem is that we get so many leaks and ROMs that the battery might not be having a chance to settle

Sent from my SPH-D710 using Xparent Blue Tapatalk 2
[Samsung Epic 4G Touch] Dudebowski:
*fix'd.

w00t w00t!
[Samsung Epic 4G Touch] Zurginator:
I get pretty good battery on AOKP:
[Samsung Epic 4G Touch] Pheno.menon:
Good thread, thanks for the tips.

Transmission sent from my slim n trim Galaxy S II.
[Samsung Epic 4G Touch] ghostzyden:
Agree with just about everything. One thing that I disagree with is letting your battery die at all. It actually decreases the life of the battery in lithium ion batteries. Its an old school method for old batteries. Try never going under 15% if possible. Everything else is correct as far as I can tell. :D
[Samsung Epic 4G Touch] rmikulus:
On the topic of battery calibration, if you know how to run scripts, the creator of V6 Supercharger and 3G Turbocharger scripts has also created "Die Hard Battery Calibrator" which will calibrate your battery in only about 20 minutes (must be plugged in that entire time)

http://xdaforums.com/showpost.php?p=18703418&postcount=5021
[Samsung Epic 4G Touch] gatesmarch123:
What he said :p
[Samsung Epic 4G Touch] EmperorX:
Does this really work?
[Samsung Epic 4G Touch] Dudebowski:
I have yet to find the time to learn how to run i.nit.d scripts on this thing to try it myself. I defer to reports in the host thread. fixed the link in OP, my bad.
[Samsung Epic 4G Touch] DutchDogg54:
Thanks for mentioning this...I've heard so many threads talk about draining until death and then recharging...blah blah blah to get it completely topped off...but you're right, this is not a good idea. See here for really detailed tech on our type of battery: http://batteryuniversity.com/learn/article/how_to_prolong_lithium_based_batteries
[Samsung Epic 4G Touch] ghostzyden:
No problem :)

Just download the script from the site and use Script Manager from the play store. Run script manager as root browser, find the script you downloaded and click on it. Hit the su button and then run. Follow the instructions for whatever the script is. Easy as anything else in Android :D
[Samsung Epic 4G Touch] jordan2333:
How do you turn off the LED notifications?I can't find it.Nevermind i found it.
[Samsung Epic 4G Touch] bigrndahouse:
Wow how did you set it up for sleeping and such? Im such a noob.

---------- Post added at 03:17 AM ---------- Previous post was at 03:09 AM ----------

wow thats impressive. I wouldnt mind knowing how to get those times on ICS i can easily do it on EL29 rooted but nothing more.Any direction would be helpful.

thanks,
[Samsung Epic 4G Touch] Dudebowski:
Bump, just because there's sooooooo much whining in the dev threads about batteries still.
[Samsung Epic 4G Touch] im0rtalz:
bump haha
[Samsung Epic 4G Touch] EmperorX:
......

W. T. F.
[Samsung Epic 4G Touch] Dudebowski:
bumping again because now that the JB ROMs are chewing through batteries. Hoping to crowdsource some community input again.
[Samsung Epic 4G Touch] aaa12585:
How. In. The. Hell? I demand an explanation!! :eek:

Edit: Also, what are TN/TW Roms?
[Samsung Epic 4G Touch] PhAkEer:
I have an edit for you ;)

In Op you mention flashing modems through MobileOdin.

Unless there's been a big change recently MobileOdin does not successfully flash CDMA radios. (if memory serves)
[Samsung Epic 4G Touch] PanchoPlanet:
Just want to mention that the battery demons all went away after I replaced my year old battery on my epic. This was in Oct, the phone was a year old in Oct, running garwynn's stock fk23 since Nov with no problems , great GPS, great battery life and everything works.

If your epic is a year old or close to it consider a new stock battery, it makes a difference.

Pp.:)

sent from a jellybean filled epic touch.
[Samsung Epic 4G Touch] Dudebowski:
you sir, are absolutely right. I wrote this quite a while ago, thanks for catching it.

TW = Touchwiz ,

Touchwiz =Samsung Stock.

Sense= HTC stock ,

AOSP = (essentially) google stock ,

Android Open Source Project, the launchpad core of the Android OS that gives all the devs here a solid starting point to make great systems like Cyanogenmod, ParanoidAndroid, AOKP, etc.
[Galaxy S II Q&A, Help & Troubleshooting] pippofiori:
If i switch to an incoming call when I'm already having one I can't go back to the first one because the phone freezes. I receive anni error message saying that phone.apk gas stopped working. TO restore it I have TO reboot it or switch it in airplane mode and then back to phone.

Any solution?

Inviato dal mio GT-I9100 usando Tapatalk
[HTC One X] :
I have a question for the lucky ones that could put their hands on this cell... did it have a sim when you tried it? Did you noticed loss of signal when holding it in some ways? I've read something on the net about poor signal on HTC One X and I'm not very happy since I've just paid for my preorder..
[HTC One X] hermand:
"I've read something on the net..." is hardly a valid claim, is it now? Why don't you at least show us where you read this and people can make an informed argument.
[HTC One X] :
I'm sorry,I've read it on an Italian forum and there were no sources of information specified there, so i simply wanted to know if some of you have heard about such problems..
[HTC One X] hermand:
I'm not aware of anyone getting really hands on with the final release product, so I'd take any such grains with a pinch of salt until the real product starts getting out there and tested.
[HTC One X] HTC-Gunge:
Ah yes this is a problem... I've read about this on... er a Chinese forum... if you wrap both hands tightly round the phone and then pull it in close to your chest while hanging upside down then the signal drops to just one bar... I've cancelled my pre-order as this is unacceptable to me! :mad:
[HTC One X] Pointlol:
roflmao ;d
[HTC One X] :
:D Ok, let's wait until I'll receive mine :D
[HTC One X] hello00:
well that sucks..ill wait until they fix it I guess..good thing i waited
[HTC One X] :
Wait, nothing sucks until it is proved to suck ;-) Maybe they were false rumors... maybe they were good rumors but they were about pre-production samples..
[HTC One X] saqaw:
How is the GSM/3G reception on the phone?.

Does it suffer from any signal loss due to any death grip?.

I previously had a HTC Incredible S which suffered from Incredible signal loss when i used to type sms in portrait mode while my fingers covered the lower back of the phone.....also lost wifi signals in landscape mode...

Similar issues were also reported in the last flagship HTC sensation..

Is there any issue with this phone's signal strength GSM + Wifi(in landscape) when ur fingers are placed near the top of the phone?

This can be checked from the menu *#*#4636#*#*

Pl. post ur test results so that all can benefit...
[HTC One X] Aust S5:
RSSI: -79 before covering top of phone in normal way when holding in landscape. While covered went to -86... Not reallyuch of a problem
[HTC One X] Aust S5:
Signal strength went from -91 dBm 11 ASU uncovered to -89 dbm 12 asu covered as in when holding landscape mode...
[HTC One X] mahdibassam:
Hi guys,

After weeks of waiting, i finally got my HTC One x today.

But there is a problem.

When i put my Sim Card in , I get around 2 Bars of signal, and then it goes away and the cross comes over the bars, then the phone says ' Preparing Sim ... ' , then the 2bars appear again, then they go away and the the phone says ' Preparing Sim ... ' , and on and on and on and on again!

I am extremely sad and dissapointed. was really looking forward to this phone.

Can anyone help with this issue?

P.s. the phone is stock and untouched.
[HTC One X] wesleyrpg:
suspect some are leaving the factory with dodgy antenna's!

my telstra sim which usually has full reception is lucky to get 1 bar out of 5 on this phone. This handset will be going back on Tuesday! (after easter)

i know theres a problem with this handset as i can't see any other providers network in the network search!

Signal Strength is -107dBm 3 asu
[HTC One X] justin0679@gmail.com:
Does that affect people living on the southern hemisphere? I live in London but I do sleep upside down.
[HTC One X] clintonmdu:
Same reception problem. my old nokia had all 4 bars but HTC one x had only 2 when both are at same place and axis.
[HTC One X] Porsche.V:
i had a htc evo 3d and i had excellent reception and now, with the one x, i only have 2 to 3 bars where i used to have 5 with the evo.. but, besides the number of bars, e never had a problem so far with reception or internet speed. so, i'll check this during the next days
[HTC One X] daveny80:
Phone Signal Strength

Hi i have just done a test on mine and i am coming up witht e same issues. I had a iPhone 4 and moved to this. I had full signal at work and now only 1 / 0 bars show now.

Signal Strength: -99 dBm to 7 asu
[HTC One X] fakeman:
No, I don't think it has anything to do with antenna. I have the "lost signal problem" as well, actually when my cell is "disconnected", the phone is telling me no SIM inside, and when it suddenly showed me "Preparing SIM...", I got signal again.
[HTC One X] shrubz:
I had the same problem with network search not showing any other operators until I entered this code *#*#4636#*#* then changed the "Set preferred network type" from WCDMA Preferred to GSM Only. Now I can see other operators in network search.
[AT&T Samsung Galaxy S II SGH-I777] atinm:
DEVELOPMENT THREAD

FOR DEVELOPERS ONLY​

DISCUSSION THREAD FOR USERS:

http://xdaforums.com/showthread.php?t=1568848​

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.0 (ICS), which is designed to increase performance and reliability over stock Android for your device.

#include <std_disclaimer.h>
/*
* 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.

General:

http://github.com/CyanogenMod

Device (you need both):

http://github.com/CyanogenMod/android_device_samsung_galaxys2

http://github.com/CyanogenMod/android_device_samsung_i777

Kernel:

https://github.com/teamhacksung/android_kernel_samsung_smdk4210

Build:

http://teamhacksung.org/wiki/index.php/CyanogenMod9:SGH-I777:How_to_build

Getting Started:

http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit

Example:

- cd ~/android/system

- repo start branchname CyanogenMod/android_device_samsung_i777 (or android_device_galaxys2 depending on whether your work is in common galaxys2 or i777)

-- Make your changes at device/samsung/i777 (or galaxys2)

- cd device/samsung/i777 (or galaxys2)

- git add -A

- git commit -a

- cd ~/android/system

- repo upload CyanogenMod/android_device_samsung_i777 (or android_device_samsung_galaxys2 if your changes are to galaxys2)

Many of your changes will actually be in the android_device_samsung_galaxys2 repo as well as the code is shared between the galaxys2 and i777 so you will also need to work in that repo.

Navigate to http://review.cyanogenmod.com , click your commit and add atinm for i777, atinm, codeworkx and xplodwild for galaxys2, as reviewers.
[AT&T Samsung Galaxy S II SGH-I777] Red5:
Alright, this thread has been cleaned up to here. All other non-dev members can discuss this here in the designated discussion thread in the General forum.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
atinm - don't know if you saw, but there's a pending gerrit submission for an updated kernel.

The current set of kernels has ondemand as default but interactive governor enabled - this combo can cause hung task freezes in LPM and recovery.

http://review.cyanogenmod.com/#change,14072

(I tried to add you as a reviewer but I'm not sure if that's the correct atinm. The system is full of "use the other atinm" users. :) )
[AT&T Samsung Galaxy S II SGH-I777] atinm:
Saw this too late - I pushed the same kernel plus an added assert for galaxys2 so people using the bad ported galaxys2 builds can get to i777. I'll take out the galaxys2 assert in a couple of days after people are on i777. Building a new nightly.

Will look at the GPS you have on gerrit in a little bit - have to be out for a few hours.
[AT&T Samsung Galaxy S II SGH-I777] Dzmitry:
Building from source

I am trying to build it locally with following error:

dzmitry@dzmitry-desktop:~/android/system$ brunch i777

---//some skipped output///---

build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/i777/cm.mk]]: "vendor/samsung/i777/i777-vendor-blobs.mk" does not exist. Stop.

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

My manifest:

<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="CyanogenMod/android_device_samsung_galaxys2" path="device/samsung/galaxys2" remote="github" />
<project name="CyanogenMod/android_device_samsung_i777" path="device/samsung/i777" remote="github" />
<project name="teamhacksung/android_kernel_samsung_smdk4210" path="kernel/samsung/smdk4210" remote="github" revision="ics" />
<project name="teamhacksung/buildscripts" path="buildscripts" remote="github" revision="ics">
<copyfile dest="build.sh" src="samsung/build.sh" />
</project>
<project name="CyanogenMod/android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="github" />
</manifest>

Any help is greatly appreciated!
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
you didn't do extract-files

Not sure if looking for galaxys2 will cut it... Most likely a bunch of people are coming from Touchwiz-based firmwares.

I admit I am partially at fault - I didn't implement sed scripts in Hellraiser to change the model, partly to minimize the chances that something would break. (The rule was to change as little as possible to make things work in order to maximize compatibility.)
[AT&T Samsung Galaxy S II SGH-I777] atinm:
The issue is that the proprietary files that the i777 is using are from the galaxys2 and it just pulls them from there. But the .mk files that are generated need to go into the i777 directory. I've updated extract-files.sh to try to get around it, but need someone to test.
[AT&T Samsung Galaxy S II SGH-I777] 5942marine:
I tried to run extract-files.sh and got:

remote object '/system/lib/libGLESv2_dbg.so' does not exist

Which gave me this during compile:

make: *** No rule to make target `vendor/samsung/galaxys2-common/proprietary/libGLESv2_dbg.so', needed by `out/target/product/i777/system/lib/libGLESv2_dbg.so'. Stop.

I have the latest repo as describe in the op. Anyone else run into this issue? Ran the extract on cm7.
[AT&T Samsung Galaxy S II SGH-I777] halfsoul:
Did you enable root for adb before running extract-files.sh? And what ROM do you have now?
[AT&T Samsung Galaxy S II SGH-I777] 5942marine:
I had cm7 on it when I ran the extract, I just did it on that phone bricker build as well, only ended up missing one *.so, cant remember which exact file it was, had to step away. Will get back in the am.

Update: Just flashed atinm's nightly of CM9, ran extract_files.sh and no errors at all.
[AT&T Samsung Galaxy S II SGH-I777] halfsoul:
Confirmed, /system/lib/libGLESv2_dbg.so does not exist in CM7 so of course it can't be extracted. Screencap of partial file list from my last nandroid on CM7 before upgrading attached.
[AT&T Samsung Galaxy S II SGH-I777] Red5:
All non-dev related posts have been moved over to the General CM9 thread.

I guess the giant red bolded DEV tag at the top isnt obvious enough. :rolleyes:
[AT&T Samsung Galaxy S II SGH-I777] 5942marine:
Just an update... I was compiling the latest build, and got the following error:

make: *** No rule to make target `vendor/samsung/galaxys2-common/proprietary/hwcomposer/lib/libfimc.so', needed by `out/target/product/i777/obj/lib/libfimc.so'. Stop.

Now, when i ran ./extract-files, I didn't recieve any errors while it was pulling the files.

I can see that the file is in the galaxy2-common directory, under the proprietary folder.

There is not folder under proprietary /hwcomposer/lib
[AT&T Samsung Galaxy S II SGH-I777] sam3000:
This is the fix for the same issue that was present in galaxys2:

http://review.cyanogenmod.com/#change,13935
[AT&T Samsung Galaxy S II SGH-I777] Red5:
Posts cleaned out again. Im only going to say this one last time...

THIS THREAD IS FOR DEVELOPMENT ONLY. IF YOU ARE NOT HELPING DEVELOP FOR CM9 THEN YOU SHOULD POST IN THE GENERAL THREAD, NOT THIS THREAD. ANY FURTHER NON-DEV RELATED POSTS WILL RECEIVE AN AUTOMATIC INFRACTION AND THEIR POST WILL BE DELETED.
[AT&T Samsung Galaxy S II SGH-I777] 5942marine:
Thanks, got it working.
[AT&T Samsung Galaxy S II SGH-I777] atinm:
http://review.cyanogenmod.com/#change,14155 fixes the same thing for i777.
[AT&T Samsung Galaxy S II SGH-I777] atinm:
Any extract-files.sh fixes you make - please gerrit them, or just send them to me directly via email if you don't know gerrit (learn Gerrit if you intend to develop for CM!).
[AT&T Samsung Galaxy S II SGH-I777] sam3000:
Can you clarify - I take it discussion about build issues that are because script fixups are necessary in github sources is also off-limits ? ie where the root issue is in the repo not the person trying to compile. (Previous post removal implies this.)

If someone can't massage whatever comes out of github in order to get it to compile then it's unlikely they would be posting patches even if the build worked. However, on the other hand, I would argue it's also useful to identify, discuss and fix any build related issues for the benefit of all (separate thread perhaps?)
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
See atinm's previous post - if you find that the build scripts are wrong and fix them, please either post a patch here or (even better) read up on gerrit and submit. :)

http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit
[AT&T Samsung Galaxy S II SGH-I777] atinm:
Anything source/github/gerrit related is fine here -- basically if there is something a developer can use, it should go here. This includes things like logcat output etc for bugs too. Questions, asking for help etc that can be done by other users is for the discussion thread.
[AT&T Samsung Galaxy S II SGH-I777] sam3000:
Si4709_driver.ko is not necessary in i777, right ?

If atin / entropy can confirm this is the case I'll gerrit changes to tidy this up.

It was removed from kernel config a while ago but is still in github sources so nothing complains (unless you explicitly clean things out). Fixes I think necessary are to i777 i777.mk and kernel build.sh. I was thinking of refactoring "MODULES" in the kernel build.sh to allow a per target module list (targets are currently galaxys2 galaxynote and i777).

Ok, I lie. I have the aforementioned fixes / refactoring already done in my tree. Does this approach sound sensible ?
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
You are correct - that's the driver for the FM radio which we don't have.

Sounds good - that's been a minor annoyance I let go, but cleaning it up is good. :)
[AT&T Samsung Galaxy S II SGH-I777] iXNyNe:
ok, so im following this guide

http://teamhacksung.org/wiki/index.php/CyanogenMod9:SGH-I777:How_to_build

to try and get started, and im on the "repo sync -j16" command

just wondering, is this supposed to take bloody ages? it seems like im downloading ALL cm sources for ALL devices and ALL versions (and ALL... ALL... ALL... etc)

just wondering if all of this is necessary or if i'm doing something wrong?

side note

im wondering how much data this is downloading, i'm trying to beat a tethering record of 77gb lol
[AT&T Samsung Galaxy S II SGH-I777] tmckenn2:
there is a number for aosp. If i remember correctly its 10gb source? Its a lot more than gb thats for sure. Anuways the cm9 source will take ages. im not sure that -j16 helps in this instance bc there is very little compression being done. Just downloading.

generally it takes a few hours to download.

And it might be pulling tools and pre compiled tool chains from the other branches but i cant say for sure. The -b ics should make it download only the ics branch

Here are the specs:

http://www.androidpolice.com/2011/10/21/want-to-build-ice-cream-sandwich-from-aosp-bring-out-the-heavy-artillery-this-is-what-it-will-take/

6gb source

25gb to compile... As it is i have 50gb set aside for ccache...

My own side note. Im aware that brunch is the preferred way of building noe instead of lunch, make. Does brunch also add -j16 inherently because this is one thing that could benefit from more processing power.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
CM recently reworked things so you don't download all of the device-specific trees until you request one (such as device/samsung/i777) - but 90%+ of Cyanogenmod is common code, and the AOSP source tree is pushing on the order of 10GB.
[AT&T Samsung Galaxy S II SGH-I777] Entropy512:
atinm or anyone else with high familiarity with CM's build system - Any ideas on why nfc.exynos4.so won't build after trying to implement NFC changes?

http://review.cyanogenmod.com/#change,14470
[AT&T Samsung Galaxy S II SGH-I777] sam3000:
This is an interesting exercise in understanding the CM build system.

It builds with this small change to i777/Android.mk:

diff --git a/Android.mk b/Android.mk

index 262dbfc..d59ce4c 100644

--- a/Android.mk

+++ b/Android.mk

@@ -54,12 +54,12 @@ $(LOCAL_BUILT_MODULE):

# ) \

# )

+include $(call all-makefiles-under,$(LOCAL_PATH))

+

include device/samsung/galaxys2/camera/Android.mk

include device/samsung/galaxys2/DeviceSettings/Android.mk

include device/samsung/galaxys2/gpswrapper/Android.mk

include device/samsung/galaxys2/tvout/Android.mk

include device/samsung/galaxys2/tvouthack/Android.mk

-include $(call all-makefiles-under,$(LOCAL_PATH))

-

endif

I'm sufficiently clueless at this point to know what the most appropriate fix is but you are probably already several steps ahead :-)

(I'm assuming that the galaxys2 includes are stomping LOCAL_PATH.)