yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S (4G Model)] RaverX3X:
Yes its in the wrong fourms but im going to answer your question anyways.

the reason you dont see cm7 for the sgs4g is lack of a asop kernel (sence we dont have access to gb sourcecode for the sgs4g kernel.. (and theres alot of diffrences between the sgs4g and your typical galaxy s series rom that makes porting it without the source cumbersome.....

krylon 360 has been working forever on cm7 for the sgs4g and has done well they need the kernel source from gb to finish the kernel and complete the work..

so once samsung cough goes final with the gb rom and gives us source for the kernel expect cm7 and other asop roms in there fully glory :P
[Samsung Galaxy S (4G Model)] Fluidification:
Man I feel exactly the same. So i open the page, and the first thing that shows up is cyanogenmod 7.1. My mind was partying until I saw [q] before it.
[Samsung Galaxy S (4G Model)] bbobarino:
SCARED THE LIVING **** OUTTA ME 2 LOL
[Samsung Galaxy S (4G Model)] Fluidification:
wish it was real.

---------- Post added at 02:48 AM ---------- Previous post was at 02:47 AM ----------

can we not ask cyanogen guy steve as he is an official dev for samsung, when official gb will be out?
[Samsung Galaxy S (4G Model)] mzangui:
what if samsung release the official gb after the KZ10 leak? :(
[Samsung Galaxy S (4G Model)] chris31jct:
KZ10? I was expecting a SGH-T959VMCNAQLIRJD1963804 leak!
[Samsung Galaxy S (4G Model)] nazcalito:
I have the CM7 rom for the 4g. The only problem is, the only things working are GPS and Buddies Now.
[Samsung Galaxy S (4G Model)] wizardslovak:
I got fb working without data or wifi ...
[Samsung Galaxy S (4G Model)] jager555:
You just ruined my night. It was like waking up on christmas...only to find you have no presents. Thanks.
[Samsung Galaxy S (4G Model)] mex911:
Lolz i know rite..
[Samsung Galaxy S (4G Model)] nailedtonothing:
I apologize for getting everyone too excited and posting in the wrong thread. I don't spend very much time on these forums and didn't realize there was a q&a section. Thanks for the explanations though, hopefully we'll see it develop eventually. To be honest, I think my time with SGS4G will be ending once the nexus prime or whatever they're calling it now arrives.
[Samsung Galaxy S (4G Model)] MrPapito429:
Word bro

Sent from My. Olympus on my SGH-T959VUVKD1
[EVO 4G Q&A, Help & Troubleshooting] phatl:
I have been using MikG 2.51 rom for weeks with no problems. Phone was fine before bed last night. As of this morning I can't make calls I get network busy error's. Texts won't go out or come in. I can access the Internet with 3g. I have rebooted, pulled the battery, turned airplane mode on and off. Any help would be appreciated.
[EVO 4G Q&A, Help & Troubleshooting] luisrod03:
Sounds like a tower issue....

Sent From My HTC EVO 3D ROOTED
[EVO 4G Q&A, Help & Troubleshooting] phatl:
Well I was going to do a wipe and reflash and in the middle of backing up my apps with titanium a flood of texts came through. I have no clue but everything is back to normal. Crazy.
[EVO 4G Q&A, Help & Troubleshooting] luisrod03:
Yeah probabaly a tower near u was in maintenance or something like that....

Sent From My HTC EVO 3D ROOTED
[XPERIA X10 Q&A, Help & Troubleshooting] crackednut:
Have an Xperia X10 with Android 2.1. Wanted to root my phone to upgrade to gingerbread. However i admit i got confused with the plethora of links and pages and 6 hours later i have a phone that only has "Sony Ericsson" written on it.

Here's how i started - based on DoomLord's instructions i installed Flashtool (from here) . HOwever I was unable to find xrecovery folders in the log messages.

Followed step by step procedure but realised that each time i upgraded the kernel, phone seemed to be going into some bootloop.

I realised that this may be due to my phone running on Android 2.1

SO i moved to another thread . Downloaded these files with the hope that they would work.

meanwhile was also following video through a similar page that was detailing the methods for installing custom ROMs. The reason i followed another source is only because the intsructions on all these pages seemed very confusing.

i believe i may have misled myself by following two different procedures here or the files i downloaded were incorrect.

After I upgraded the kernel as per doomlord's instructions, i went into xRecovery and formatted the data folders. I had already copied the ROM files provided by Doomlord in this thread onto my SD card under a new folder. However, xRecovery was asking for .Zip files while there were .7z .

Tl;dr - formatted data on xRecovery and did not have the correct updated files. phone is not functioning now

Tragically so, I am now left with an Xperia that only seems to be displaying the words "Sony Ericsson". I wish to learn from this experience but hope its not at the cost of a good phone! :(

Would the experts believe that this phone can be un-bricked now???
[XPERIA X10 Q&A, Help & Troubleshooting] fcb1:
your phone is not bricked so dont worry. just make sure you have the newest flashtool. dont upgrade the kernel if you are staying on 2.1. if youhavent downgaded the kernel then do so. if it doesnt work, just download your baseband and firmware you want. as for rooting on 2.1, you can use super one click. for 2.3, you hav to use the flashtool
[XPERIA X10 Q&A, Help & Troubleshooting] aR_ChRiS:
If you are on 2.1, then you don't have to go through all the downgrade/upgrade hassel.

Just turn on debugging and use flashtool/superoneclick to root.
[XPERIA X10 Q&A, Help & Troubleshooting] crackednut:
Wow... such a relief to know that. Was exasperated and down-beat to even look at my phone. :D

please help me in identifying the right version of softwares and protocols to follow. In the current state, i connected my phone and flashed it once using flash tool but there has been no progress. Am i missing out a few steps?

How do i upgrade to 2.3 eventually?

Thanks a lot for the support and motivation :)
[XPERIA X10 Q&A, Help & Troubleshooting] fcb1:
ok if you want to go to 2.3 download the firmware from here

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

flash it through the flashtool but you have to be in flash mode.
[XPERIA X10 Q&A, Help & Troubleshooting] crackednut:
Reading this from office now. Shall check in a few hours once i'm back home.
[Epic 4G Q&A, Help & Troubleshooting] kehlan:
I'm running RandomRom 2.3.4 on EH17, and this is the only issue I have noticed with this rom.

I am typing horrificly slow right now to avoid [further] frustration.

ANY input is appreciated. No pun intended.
[Epic 4G Q&A, Help & Troubleshooting] ugothakd:
Well, your kinda screwed. We can't have the keyfix on Gingerbread leaks. You have to use a froyo rom/kernel
[Epic 4G Q&A, Help & Troubleshooting] KennyG123:
Yeah...what he said ;-)
[Epic 4G Q&A, Help & Troubleshooting] xopher.hunter:
Actually if you use touchpal keyboard it makes it way better due to the spell check hardware key option in the settings
[Epic 4G Q&A, Help & Troubleshooting] ugothakd:
Or Swiftkey X. but thats not an excuse for samsung's crappy coding..
[Epic 4G Q&A, Help & Troubleshooting] socos25:
This is the reason I went back to Froyo. Running Srf 1.2 with K0nane's new kernel I get no missed keys at all.
[Epic 4G Q&A, Help & Troubleshooting] pvtjoker42:
Yup, I'm looking forward to running a GB rom daily, but won't happen until we get source so we can get the hw keyboard fix. for now i'm happy with Simply AOSP 4.x and revolted kernel. Pretty sure this is the fastest my phone has been.. ever.
[Epic 4G Q&A, Help & Troubleshooting] slartibartfast42:
This is sad I know. We have to get source to fix it.
[Epic 4G Q&A, Help & Troubleshooting] kehlan:
I ended up just switching to Simply AOSP to get away from the lag.

Pretty ****ty that this forced me to downgrade.
[Epic 4G Q&A, Help & Troubleshooting] pvtjoker42:
yup.. i've decided to stick with EC05 based roms till we get GB source (or a version of CM7 that doesn't include the hw keyboard lag issue)
[Epic 4G Q&A, Help & Troubleshooting] xopher.hunter:
aaaaaaand now we have GB kernel source thanks to mkasick
[Epic 4G Q&A, Help & Troubleshooting] RandomKing:
Blame Samsung! But if your solution is to "downgrade", I do offer an EC05 match to ThunderHawk... :p

Here's hoping this new source find brings together a new dawn for Epic Gingerbread!
[Epic 4G Q&A, Help & Troubleshooting] pvtjoker42:
Yup.. it's only a matter of time before we see some lovely GB kernels with the keyboard patches built in, and then we'll have some sweet GB action.
[Android Q&A, Help & Troubleshooting] howmydictate:
I wanna install the new cyanogen mod 7.1 on my samsung captivate but I have no clue where to begin.... Please help...
[Android Q&A, Help & Troubleshooting] baseballfanz:
Good place to start

http://wiki.cyanogenmod.com/wiki/Samsung_Captivate
[Android Q&A, Help & Troubleshooting] howmydictate:
See I am hesitant on doing that because I am on a different rom Serendipity VII Build 2... I am so new to the android world...
[GT540 Optimus General] USSVagrant:
Edit: Please Delete
[GT540 Optimus General] jhonnyx1000:
I've never found out a way to delete threads and posts :( Is it even possible with normal users?
[GT540 Optimus General] -Grift-:
We do have 1 moderator
[Fascinate Q&A, Help & Troubleshooting] weblexa:
I'm interested in learning how to port ROMs. I've done a lot of searching online and can't really figure out exactly what steps are needed. From what I've read, the porting process consists of replacing files in the ROM you're porting with files that are compatible with the Fascinate, but I don't understand which files need replaced. Also, information I've found on various websites don't explain what other steps are needed in order to successfully port a ROM. I'm sure there's more to it. Is anybody willing to take the time to explain what steps are involved in porting a ROM? Your help is appreciated!
[Fascinate Q&A, Help & Troubleshooting] imnuts:
It takes a significant amount of work, and if you've never done any ROM building in the past, you may want to start with that before worry about porting a new ROM.
[GT540 Optimus General] ErnuB:
So i know is not here yet for GT540, but what do you think about it anyway?

leave you the link to offical page

http://www.cyanogenmod.com/blog/cyanogenmod-7-1-released
[GT540 Optimus General] jhonnyx1000:
There's no official CyanogenMod for the LG GT540. Swiftdroid is based on CyanogenMod 7.1.0.
[Click Android Development] CyanogenMod:
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), 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.
*/

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.

Instructions:

First time flashing CyanogenMod 7 to the HTC Tattoo, or coming from another ROM?

Root the device and install ClockworkMod Recovery. Instructions are available here.

Perform a NANDroid backup of your current ROM.

Format the system, data & cache partitions of your device.

Perform a factory reset.

Flash CyanogenMod.

Optional: Install the Google Apps addon package.

Upgrading from earlier version of CyanogenMod 7?

Perform a NANDroid backup of your current ROM.

Flash CyanogenMod (your Google Apps will be backed up & restored automatically).

Issues?

Experience issues? Please provide the following info:

If the device was hard reboot, please provide the file "/proc/last_kmsg".

If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.

Please use Pastebin when possible.

Download Links:

Official post​

CyanogenMod:

Latest version: update-cm-7.1.0.1-click

Download: link

Mirror: link

MD5sum: 4ec7cdcdd5ef19c6884a55dd917b39fa​

Google Apps addon:

Version: gapps-gb-20110828

Mirror: link

Mirror: link

Version: Google Talk with video addon

Mirror: link

Mirror: link​

The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
[Click Android Development] sunitknandi:
hey cyanogen, why this post, eh? our maintainer kalim already updated his post about the new update.
[Click Android Development] potattoo:
i wonder too, allthough i like that this post is more clearly structured
[Click Android Development] Hanisa:
I like this post too, but i noticed that you didn't link to nightly rom so they'll not updated anymore?

Anyway thanks alot for all the hard work of CyanogenMod crew... :)
[Click Android Development] finnk:
Nightlies are here:

http://download.cyanogenmod.com/?device=click
[Click Android Development] Hanisa:
I know, but maybe if they didn't put it on the main post, there aren't new update, this is my point of view that's why i ask it...
[Click Android Development] sunitknandi:
This is now the official CM thread

Kalim is closing his thread. All discussions will be here from now onwards, it seems.
[Click Android Development] niruzz:
100%working camera now

i notice batt take long time to charge and drain

thanks kalim
[Click Android Development] bladez:
I have a question.

Are latest nightly's deodex or odex?
[Click Android Development] sunitknandi:
They are de-odexed.
[Click Android Development] Hanisa:
For anybody who want to take a look to Nightly CHANGELOG here's the link : http://cm-nightlies.appspot.com/?device=click
[Click Android Development] thacen:
Accidental touching the volume key while picking up calls always hangup the call. Is there any setting to avoid this??
[Click Android Development] McJosephs:
I have 7.1.0.1 and made a clean install and am very happy with that rom! Really, really good work!

I want to report one curiosity:

I put my contacts from LG KP500 Cookie over Bluetooth to my Tattoo and everything worked fine - with one exception: The telefon-numbers have the wrong format.

In Germany telefon-numbers look like: *0(2-4 numbers)*-*(3-8 numbers)*, e.g. 02234-7654322.

Mobile-numbers always look like: *0(3-4 numbers)*-*(7-8 numbers)*, e.g. 0159-7654322.

But the Tattoo made every contact-number I saved myself on the Cookie this format: 012-345-67891, except the pre-set service-numbers. This is quite unusual. On the Cookie my contact-numers have the format: 01234567891, which is acceptable ;). There was even no possibility to put a "-" into a number.

Don't know where the mistake is... Maybe there is a solution? ;)
[Click Android Development] BilboPC:
Download Server Problem!

I can not download nothing from server:

http://download.cyanogenmod.com/?type=nightly&device=click

It says only: Internal server error :mad:

What is happend?

EDIT: Server is now OK :-)
[Click Android Development] pipko:
work ok for me
[Click Android Development] theslime:
I've been trying to download this for a couple of days now, both through this page and through ROM Manager. No luck. Server issues?
[Click Android Development] potattoo:
i shortly did set 'keep launcher in memory', 'remove unused images' (translated from german) and 'use 16bit for transparency' in cyanogen settings, to tweak it a bit. since then i got only reboots and freezes, shortly after booting.

did those freezes/reboots before occasionaly, but now it got insane!

version 7.0.1.1 and nb221

i made a logcat after a freeze, its full of errors. ill send it on request!

managed to disable that stuff during reboots (seems like it was possible since the PIN requester didnt pop up) now it was working longer. But on first display timeout it froze again. something is seriously bugged with the latest versions. :(

EDIT: still reboots and freezes... only thing that seem to have stopped it again was to remove sdcard. so i guess .android_secure is faulty again. But this must have happened during use, not from flashing the ROM, since after flashing it was fine. It only happened after yesterday.

And no, i didnt touch CPU settings. Just moved some more apps to sdcard and changed the above settings (which i reverted as i wrote).

So my conclusion: there is a bug that breaks the .android_secure !
[Click Android Development] andynroid:
Next NB ChangeLog is MASSIVE :)

http://cm-nightlies.appspot.com/?device=click
[Click Android Development] fra87:
Hi

I have a small problem with the message app. If i set "Use send timestamp" (i don't know if it's called like this, but it's the feature that allows you to see the time the message was sent instead of the time you received it) the messages have no "GMT offset" (i mean the times are shown in GMT time and not in my time - which is GMT+1 or +2 if there is "legal time").

If i enable the feature "GMT Timestamp", which i think is made to solve this problem, nothing changes.

I'm using NB199; do you think it is fixed now?

Regards
[Click Android Development] bladez:
Since the old thread got closed and nobody answered my problem, here I go again.

Ever since I clean-installed 220 nightly (wiped everything, /system, dalvik-cache, cache, factory reset, SD) my phone after starting up totally freezes in 5 minutes or so. Rebooting it 2-3 times usually helps until the next reboot when I AGAIN have to reboot it 2-3 times before it's stable again. I tried updating to 226, but this changed NOTHING.

Please help as this is a serious problem.

Here is the logcat when it has crashed: http://pastebin.com/AT5U5nag
[Click Android Development] enriquettoo:
Working perfectly for 2 days.
[Click Android Development] Okluzhion:
I tried flashing the version from the first post, but it showed some error with " (Status 7) " at the end. Tried flashing the RC1, though, and it's working.
[Click Android Development] george.baskharon:
seems that the battery drain like there's a hole in it, in 10 min it drained 10% standby wifi on
[Click Android Development] potattoo:
i dont see a difference to earlier versions. WIFI allways pulls a lot of power, especially on low signal strength...
[Click Android Development] enriquettoo:
Same battery drain as with 7.1

Remember to perform battery calibration

My Tattoo works for more than 1 day with wifi on (moderate use)

---------- Post added at 02:55 PM ---------- Previous post was at 02:49 PM ----------

Status 7 error is usually related to Recovery version (wrong Recovery version).

Are you flashing an HTC Tattoo (aka Click) or an Xperia ;)?
[Click Android Development] george.baskharon:
enriquettoo

how do u do a battery calibration ?
[Click Android Development] kemoba:
Fully charge your battery, go to clockworkmod (if you use it, i dont know does this option exist in amon-ra), then go to advanced, wipe battery stats, after that do a full drain and then a full charge again
[Click Android Development] Okluzhion:
Lol, are you kidding me? My phone is Xperia arc, Tattoo is my boyfriend's old phone. He wanted to sell it, but the call speaker is dead. We thought it might got something to do with the firmware or whatever because a friend of his messed around with it, but it seems it's a hardware fault.

Anyway, I couldn't install this stable 7.1 version, but could flash 7.2 RC1 without a problem. So I don't know how that could be related to wrong recovery version.

Sent from my LT15i (Xperia arc) on KA ICSony
[Click Android Development] enriquettoo:
Thanks kemoba.

An other way is using an app: Battery Calibration, see this thead

Once you have 100% charged, just clicing a button, and voila!

No need to reboot, but recomended a full drain an a full charge again.
[Click Android Development] rallapag:
battery calibration apps (which remove battery stats or removing battery stats), may not have much impact on battery life

Check my earlier post and the link there in for the reason

http://xdaforums.com/showpost.php?p=23394736&postcount=55

main discussion link

https://plus.google.com/u/0/105051985738280261832/posts/FV3LVtdVxPT
[Click Android Development] enriquettoo:
The point is that, after flashing a new ROM, or just after a hang out, the battery stats may show that you have 80% of battery when actually you have 30% (is an example), and then, the problems come (phone shutdown with no advice, problems with signal, ...), you can charge till 100%, but the battery is not fully charged (I think).

It is recomended to perform a battery calibration (that is: delete wrong information of batterystats.bin file, wait, ...delete this file) so after a full charge, the stats becomes reliable.

You DO NOT improve the capacity of the battery, nor battery life, but after a calibration and a full cicle (charging and discarging) it works better, ....under my experience, of course.

Edit: rallapag, you are a master on Click, so Do I have to undertand that it is better to perform two full cicles (complete discharge - complete recharge - complete discharge- complete recharge) than using the app or deleting batterystats.bin manually?
[Click Android Development] rallapag:
batterystats.bin is in /data/system folder,

so if you install a new ROM, you wipe data folder, therefore you wipe batterystats.bin as well

and it gets created at the next boot.

and the fact in words of google dev, is that it is for battery usage display settings

some people claim to see improvement by wiping batterystats.bin, but what i think happening here is, they probably flashing the new ROM, when the device is fully charged or near full charge

(this is one recommendation you get when you flash a RUU, it asks you to fully charge the device before starting the installation). so ROM power usage is near realistic for battery to remember.

most of the latest batteries have inbuilt power gauge (do not remember exact name they are called). So by going through couple of discharge and recharge cycles like macbook battery calibration, you make batter gauge realistic.

I am no expert than you on this, At least that is what i think i understood about battery calibration.

================================================

EDIT:

I think we are taking this bit of the topic of the forum, so may be can stop at this,

if more discussion is needed, some one can open a new thread.
[Click Android Development] enriquettoo:
Nomore on that.

Thanks for your explanation, rallapag.

I'm reading lots of threaths about battery....:rolleyes:

Final recomendation: full discharge and recharge cycles
[Click Android Development] rallapag:
one last point

Best practice to flash a new ROM would be after full charge (or around 90% charge) of the battery.

It is safer than calibrating the battery too often (drain and charge cycle).
[Click Android Development] :
There is a new nightly...but I don't found the changelog...what's the difference between the previous version and the new of april 21th 2012?
[Click Android Development] potattoo:
is the video camera working for anyone else?

here it still allways crashes after some time (like 30 seconds recording)

I get a tiny picture in a frozen picture and then the camera does not respond anymore and i gotta reboot my tattoo. also the video file is corrupted. :(
[Click Android Development] jakonicki93:
Everything is working for me like a charm. Fast and fluid/smooth ROM. The best ROM for Tattoo.
[Click Android Development] kemoba:
While I was on CM7 that same thing happened. But now im on CM9 so I dont have camera in the first place :D