yashsingh1/xdaforums huggingface dataset:
[Galaxy S II General] fr3quency:
XILA2 with either SpeedMod K2-18/K2-19 test 5 or N.E.A.K. 1.3x I get awesome battery life and performance at the same time. Siyah wasn't so good for me, because it kept restarting my phone.

Also, you guys MUST install XILA2. Best GB ROM for S II. Fuken stable and fast as hell. And the new lockscreen isn't so bad. I've come to love it. <3
[Galaxy S II General] DirkTeur Velserbroncx:
Good idea so here's my setup:

Clean&Simple rom +latest siyah (2.6.7)

because i like my phone as close as stock as possible but

without all the unneeded bloatware that comes with samsung roms, most of the apps tend to drain

the battery (because of the many wakelocks) or use a lot of ram.

in combo with siyah kernel best battery time ive had was 72 hrs with lite usage

p.s. i'm thinking about trying out foxhound because of all the good things ive heard about this rom.
[Galaxy S II General] nrnbow:
Suggestion: please make a Google SpreadSheet (read only) where people can see all information in one place instead of going through endless pages of posts.

Than anyone cold submit the necessary information (ROM+ kernel+ ~battery life) through PM or posting here.

And no one could mess up your SpreadSheet :D
[Galaxy S II General] XDA mark:
Im using the exact same setup you are using. Used to have

VillainROM 3.0 + Siyah latest + KI3/KH3 modem.

Now I am on

Foxhound 3.0 + Siyah 2.6.7 + KL1 modem.

Had great resulta from both. So this is more a confirmation that your first post is true for me as well. I think this thread is a good idea, new people are really helped by threads like this.
[Galaxy S II General] CamoGeko:
Good choices. :p

You're using a different modem to me at the moment since at the moment I'm seeing what LP1 is like for battery life. So far so good, seems very similar to KL1.
[Galaxy S II General] ciprianruse:
I'm using CheckRom V4 with speedmode k2-18 kernel and KL1 modem and it is the best from many choices i've had done.Speedmode is much battery friendly than siyah and it gives me like 4700 point in quadrant advanced edition with stock settings :)
[Galaxy S II General] StefGou:
I'm using cyanogenmod 7 nightly compiled by Codeworkx available here: oh, not allowed to post links :(

I use this because it's easy (nearly noob proof). Great performance, highly customizable.

Can't wait for the official release of CM9.
[Galaxy S II General] B3311:
Krinyo's SlimRom - Very skinny (ca. 114 MB), lightning fast, great monochrome theme, great support. A keeper.

Siyah kernel. Works well, not much more to say. Was on Nimphetamine (still miss Hacre), and tried void echo, which has the best battery life for me, but staying with Siyah because of Voodoo Louder support.

KL1 modem. Again, just works.
[Galaxy S II General] lambik333:
hey there, i'm using Hyperdroid/Androidmeda v5.2.21 with the LP1 modem and the Phenomenal 2.2 balck extreme kernel. works very good for my, extreme batterylife :)
[Galaxy S II General] aranab:
Just thought ill add my 2 cents/pence

For me it would have to be Checkrom v4 with the ninphetamine kernel.

I chose Checkrom because it's close to stock but has so many great yet subtle extras. With siyah or dark knight I didn't feel the battery lasted too long but with ninphetamine I don't worry about it lol
[Galaxy S II General] GJ123:
For today I went back to Villainrom 3.0 with latest Speedmod, KI3 is a great modem and firmware.

XILA2 was not very stable for me.

I'm testing quite a lot and I think Speedmod is way better than Siyah,Siyah is in my opinion just crap.

Yeah you can UC/OC it and whatever,but without some extreme modifications it won't be as smooth and battery friendly.

Or could somebody give me some 'magical' settings?

For some people Siyah seems to be great.
[HTC Wildfire S] pat da punk:
HI,

Ever since installing CM 7.2 I cannot flash any other roms, I get constant HTC screen or staying on Android logo. I am not new to flashing custom roms .

I have done all wipes before an installation and after to see if that makes any difference (sadly not) The only rom that works is CM 7.2!

Anyone got any ideas what to do

thanx pp :confused:
[HTC Wildfire S] blackpearlisuchiha:
Try removing Battery and then again switch on the phone

then same

vol dwn + power

recovery

then flash new rom
[HTC Wildfire S] intel007:
Try installing an official ruu then after that try another custom rom.
[HTC Wildfire S] pat da punk:
still no joy ! unrooted back to stock then rerooted and still the same :(
[HTC Wildfire S] Knut-PV11:
Perhaps you need a GoldCard to install a ruu official ROM.
[HTC Wildfire S] pat da punk:
seems my device cannot handle OC roms! any ideas why??
[HTC Wildfire S] Gloris:
I had the same problem, and even CM7 stopped working....don't think my phone likes overclocking either, even if i install the overclocking kernel on stock rom, the phone goes mad!

to get back to stock:-

-if you are able to get to CWM recovery, go to that first and clear all cashes, format all drives, just basically choose EVERY "clean", "clear" and "format" option to wipe everything from the phone.

-use the same directory you used for the htcdev unlock (usually c:\android)

-search this forum for a thread called "s-on gsm how to upgrade to 2.3.5" or something like that, and download the file "Gingerbread 2.3.5 (v2.13.401.2).zip".

-extract this file and find within it "rom.zip"

-extract rom.zip to the same folder you're using (e.g. c:\android)

-you should now have files called C:\android\boot.img, c:\android\recovery.img, and c:android\system.img.

-open up a command prompt window and navigate to c:\android\

-turn your phone on while holding down the -vol key to get to hboot menu

-choose "fastboot"

-connect your phone to your pc via usb, you should see it say on your phone screen "FASTBOOT USB" or something like that, in red letters.

-now, on your pc, use the following commands to flash everything back to stock

fastboot flash boot boot.img

fastboot flash recovery recovery.img

fastboot flash system system.img

after this is done (usually only a few minutes), exit the command prompt, power off the phone and restart.

you should now have a fully restored back to stock and working ROM (although you will have to set up all your contacts, all your home srceens, options, settings, and re-download all your apps etc.

-if it's confirmed working, i reccommend then IMMEDIATELY installing CWM recovery, and making a full backup, then next time things go drastically wrong, you should be able to wipe everything then just install this backup (remember to store the backup on your pc, don't just keep it on your mem card).

good luck, this method worked for me, so hopefully you will at least get a working phone again, and if you then want to try other custom roms, you can....but i think some phones are more picky when it comes to overclocking.....i can't run anything that overclocks without the phone freezing/crashing/needing battery pull and reset.
[HTC Wildfire S] pat da punk:
thanks. i will give it a try
[Android General] george1234567890:
As the title says:

I have 2 free adspots available at http://android-zone.tk

ROM'S/ Apps /Games its your choice!

All i need is a 125x 125 image and a link!
[Galaxy S II General] eddie2020:
ok i read mostly , or should be majority of SGS 2 with G version having camera failure problem..

i am one of the G version user having camera failure problem and its kinda frustrated :mad::mad:

how ever i solve my problem after google works and asking around.. :):mad:

the tricks to overcome camera failure issue is by replacing your phone camera.apk

the first thing you need to do is root (which give you power to modify your phone system)

here is the link for rooting your G version.

Declaimer

I'm NOT going to take any responsibility if you permanently bricked your phone or your girlfriend/boyfriend breakup with you because of this :D . My experience say only people who don't read and don't follow the step properly will brick your phone..

ok, after root then what? you can solve it by follow this few simple step.

1.download this root browser via android market in your phone

Link

or any browser you prefer, but must support root so it can modify data in your system..

2.download this

http://www.mediafire.com/?8x8z9tlw8f4xxox

3.Open your root browser and browse to /system/app, and move your 'Camera.apk' and 'Camera.odex' (for use as a backup) or you just delete it

(cz its rubbish that cause camera fail, it cant do the job so throw it to thrash bin :D

Don't worry, if you really deleted and want back here is the stock rubbish camera.apk

Stock Camera SGS2

4.Copy the camera.apk that you downloaded and place it in /system/app

5.Close your Root Browser and run the camera.

6.Tadaaa you are done :)

Try reboot if it don't works..

or

If the camera fails to run or shortcut is missing. Go back to /system/app with your root browser and try to install it. DO NOT DO SO IF YOU SUCCESS run the camera

updated 1march.. 3 of the old 1 there is 2 not working.. another 1 i dint try..

now i using from other rom camera apk.. uploaded..

simply click thanks if its work and solved..
[Galaxy S II General] chouzo:
Hi, is anyone tried this mod for the camera issue of i9100g? thanks for a feedback
[Galaxy S II General] samthegame:
well didnt work for me..still getting camera failed error...do i need the camera.odex file too?
[Galaxy S II General] eddie2020:
the old 1 some of those FC after used about a month..

now this 1 i jz uploaded haven fail me over 3 weeks.. try it out and give feed back
[Galaxy S II General] IndomitableIrk:
Not working on ICS

I get a "Camera has stopped working" error when I try run it. I am running an ICS rom so that might be the reason. I also don't have a camera.odex file in my system apps.
[Galaxy S II General] eddie2020:
what rom you using?
[Galaxy S II General] ad_ek:
mine was sorted right after rooting superatmos 2.1, no more camera problems
[Galaxy S II General] selvakumar69:
Sgs2 i9100g camera problem resolved

Guys, I think I have got to the root of the problem. I too was getting the "Camera Failed" problem on my SGS2 I9100G for quite some time. I tried everything to no avail. Then I uninstalled all applications which were sharing the resources with camera, those were the Flashlight apps. I rebooted the phone & since then I have not been getting the problem. I hope this solution should work for most of us. Anyhow guys please try this & let us know ur experiences.
[Galaxy S II General] ifred:
Link to stock camera is dead. Could someone re-upload it?

Thanks in advance!

P.S.

I'm looking for stock camera from German firmware (I9100GXXLA1).

P.P.S.

Also, what is original source for whose 3 cameras in top post?
[Galaxy S II General] androidfanboy93:
great guide~ :)
[Galaxy S II General] hasmis:
my galaxy s2 got same problem ( camera failed )..but my versiom is gt-i9100 can i use this step also
[Galaxy S II General] ifred:
Maybe, but you'll need to get camera app for I91000, not G.

Also, did you try to install camera firmware update? To get it search for "camera firmware" in Samsung Apps on your phone.
[Galaxy S II General] kenovi:
No camera firmware in Samsung App

I was not able to find this update on camera firmware. Has anyone updated their camera with this before? The camera app on my I9100G is version 1.0
[Galaxy S II General] blveice:
my galaxy s2 also got same problem camera has stopped...

and how to check my camera apps version???
[Galaxy S II General] rosti93:
Now the Camera is crushes and not responding :/

When I try to install it says Application not installed
[Nexus S Q&A, Help & Troubleshooting] yoavdavid:
Hello everyone Ill try to explain as best as I can.

The Problem:

recently my nexus s 2.3.4 stopped loading every time I reset it, at first I didn't put any thought for it just plugged my battery out and in again until it got on.

than it got more frequently and I had tried to a couple of roms thinking it that can do the trick, but it didn't

What I tried to do

I followed a guide of restore to "Stock-GRH78-Nandroid"

yet the problem stand still, the only thing I just figured recently is that my phone never did actually made a correct "wipe data/factory reset" (more details at the attachment), and that runing that function is necessary for fresh restore.

the only posts that I found for that kind of problems (factory wipe) was for different types of phone and the solution were using the "Odin" however as my understanding Odin doesn't work with nexus s.

I did my best trying to google a solution and search the forums with no success.

Im adding a picture of the errors while trying to run factory reset.

any help will be much appreciated, thanks!
[TouchPad General] sahhar1993:
guys the best hp touchpad dpi is 155

just try it. no crash in the trebuchet launcher and its very goog

i just calculate this

10.1 --------------------- 149 dpi

9.7 ----------------------- 155 dpi

evrything working very well .icons are amazing:D

Using cm9 nightly build from darckdroid team
[TouchPad General] sean is here.:
Thanks for the info, I'm sure I could do a bit of research to find out but...

Where did you set this? CM settings somewhere?

EDIT: build.prop?

Thanks!
[TouchPad General] sahhar1993:
yes just edit build.prop
[TouchPad General] sean is here.:
done. dropped down to 155. But it was initially set @ 160.

Isn't more better, here...or is it a question of the hardware not being able to render 160?
[TouchPad General] nguyenhonganh:
Edit build.prop use "Root Explore" .

set line: ro.sf.lcd_density
[TouchPad General] sahhar1993:
icons and launcher much better using 155 than 160

yes change 160 to 155
[TouchPad General] psp888:
thanks for the tip, was using 140 but 155 does look a lot better
[TouchPad General] sahhar1993:
View attachment 864596
[TouchPad General] rogabean:
I'm feeling 132 on mine and haven't had any problems... it's the native dpi of the device. 155 seems too big to me.

/shrug

But I also like an icon/widget free desktop - so at 132 - you may not be happy with how those look, but apps look great :)
[TouchPad General] marios96:
I m also using 132 and its great. I have even installed the cracked market from rootzwiki and that works great as well.
[TouchPad General] dijonemon:
+1 for 132dpi. It looks great, the launcher gets a little finicky with icon placement but once I'd got all my icons in place its really worked well. Tablet apps in particular look really good.
[TouchPad General] danknee:
I prefer 145. On the homescreen it fits 9 icons horizontally, right to the edges. Also the top and bottom margins are tight.

One row open beneath my bottom row of folders:
[TouchPad General] thekillingtree:
oh man, that's exactly the change i wanted to make. bought build prop editor from the market. thanks for the tip for screen size ^
[TouchPad General] touchpadtester:
I tried 155, 145, 132 personally i stick with 132 looks good.
[TouchPad General] Jotokun:
132 looks amazing. Which makes sense when you consider that's what the display was designed for, and what webOS uses (as well as the same size and resolution iPad).
[TouchPad General] drt054:
I am liking 120 so far..
[TouchPad General] pen.suhl:
APPLY AT YOUR OWN RISK

132 is best, but it breaks the market.

https://twitter.com/#!/dalingrin/status/159553612597563392

There is a fix available here http://rootzwiki.com/topic/15568-rel-market-fix-dpi-compatibility/

And there is no need to pay for build.prop editors, this does the job just fine http://tinyurl.com/7xoup64
[TouchPad General] jayb222:
I just use the free app: DPI Changer. No build prop editing needed. :)
[TouchPad General] Unrealwolf:
For me, everything except default 160 (which is too big) looks like crap: fonts are ugly, icons are low quality, etc.
[TouchPad General] Smac7:
i tried 132 and i thought the text in some apps was too small. I dont think our screen is good enough to use that dpi. The text is blurry.
[TouchPad General] peachpuff:
Ya in root explorer its pretty bad, the lines separating the files don't even show up some times.
[TouchPad General] sean is here.:
Then I think it would be a software issue. According to gsmarena.com and others, the Touchpad is specced at 132dpi. Or maybe I misunderstood you.:D
[TouchPad General] knives of ice:
Darlingrin posted on rootz that it's not wise to change the dpi
[TouchPad General] sean is here.:
I think I'll leave mine, then. That dude is certainly an authority on the subject.
[TouchPad General] Smac7:
Because of he instability it causes with the market. If you also install the market fix, it works fine.
[TouchPad General] Smac7:
Okay.I think I found a good balance. 142 has readable non blurry text, and its not too big. Also, if you do your doing lower, ics does have a font size option in the display options.
[TouchPad General] TouchpadBOSS:
I honestly believe that 160 is the best dpi. Based on y testing. But then again everyone has different opinions. I like the look of large icons with 160. And have yet to not find any apps that didn't work with 160. Just my two cents. 8)
[TouchPad General] iamsamsamiam:
132 can be abused for more real estate.

You can even stick a widget between the search and drawer buttons at the top.

It works better for portrait mode. And yes, I like to know what time it is.

And technically there's spaces between the app stacks. So you can fit 9 apps across the screen nicely. You "can" try to fit 11 apps, but they get cut off.
[TouchPad General] The Jack of Clubs:
my only problem with 160 is the launcher has an extra icon column on the right in portait that it does in landscape. i wish i could just get rid of that column space. i tried 132 but everything is really small and blurry and the launcher behaves even worse. i tried 155 and while it fixes the launcher issue by adding a column, a few of the icons and ui elements are blurry.
[TouchPad General] Sincitybronze:
Does anyone know how I can set density to 240 without losing softkeys or half of the keyboard? I used 240 on cm7 and everything worked great for me. Is a lower dpi just something I'll have to get used to with ics or is it a matter of waiting for later releases from the cyanogen team when certain bugs are worked out?
[TouchPad General] sean is here.:
I can't help you, sorry for that, but can you explain what advantage this would have on device hardware which only supports 132dpi?
[TouchPad General] Sincitybronze:
The only advantage is that icons and widgets appear larger
[TouchPad General] _Motoki_:
I haven't tried it myself but it might be worth looking into other alternate keyboards available in the market.

If that doesn't work as a last resort you could always use an external bluetooth keyboard. The HP one does work under Android, but also any bluetooth keyboard device should work really.
[TouchPad General] iamsamsamiam:
When I hear 240dpi on a tablet I hear "giant phone".

Samsung Galaxy Captivate ICS CM9, Glitch Kernel | HP TouchPad CM9
[TouchPad General] Sincitybronze:
Yeah I guess I like giant phones :)
[TouchPad General] CarbolDroid:
Since changing to 132 DPI I've noticed a marked decrease in performance, anyone else?

admittedly I didn't have much time to play with it before the change, but my little experience with it did seem to be much smoother. since the change from 160 to 132 I've had 2 trebuchet FCs, 2 browser FC, 1 random reboot and countless re-draws and general sluggish malaise throughout.

Give nova launcher a try? or change dpi to 155/160? suggestions?
[TouchPad General] CarbolDroid:
For what its worth, changing back to 160 solved all my woes. 132 looks better but its not worth the performance issues I seemed to be having. At 160 everything is buttery.

Guess I'll just deal with senior citizen sized icons until a more eloquent fix is available.
[TouchPad General] scrizz:
I haven't had any problems at all on 132.

I've been using 132 since the beginning.

The only problem is the market, and that can be fixed.

;) :D
[TouchPad General] galaxykeks:
How can you guys say best is 132 if the icons are completely misplaced?

The left icon row is cutted by 3/4 for me at 132 dpi.

I agree, the rest is looking quite good, but this is kind of annoying...
[TouchPad General] nitens:
Not too sure I follow what's going on here. Just set 132 and everything looks OK, including the market.

What are the market symptoms I should be looking for?
[TouchPad General] galaxykeks:
Can anyone of you post a screenshot which icons in each corner?

I will do it too as soon I can.

With TouchWiz it works fine, but with Trebuchet the last rows on the left and right are almost not visible... for me...
[TouchPad General] Silenus21:
Nova Launcher and 132 looks great.
[TouchPad General] Royvin:
From what I have read purchasing and updating apps. I know when I had it at 132 I couldnt download Dolphin HD said device was not compatible. When I went back to 160 worked like a champ. Yes 132 looks great but I will wait till someone has it fixed and working properly with 132.:)
[TouchPad General] cvcduty:
I am using 132 and hacked Market. I just checked and Dolphin HD is showing up as available.
[TouchPad General] galaxykeks:
Here is what I ment.

Its with the CM9 Alpha 0.5

Nobody of you experienced this on 132 dpi?
[TouchPad General] sdho:
is it possible that you had your DPI to 120 before? or are you using NOVA to set your rows and columns?
[TouchPad General] galaxykeks:
No, everything is stock -> Trebuchet is used

I edited the DPI with the Root explorer from 155 to 132

Any ideas? Is it different for you guys on 132 DPI?
[TouchPad General] iamsamsamiam:
Yeah, that happens. Because technically in 132 DPI I think there are actually 11 columns, but there are 9 centered, fully visible columns. If you're smart about it you can abuse the screen's real estate. The entire space between the top buttons are accessible.

My suggestion is to just move the icons to fully visible parts of the screen.

Samsung Galaxy S Captivate ICS CM9, Glitch Kernel | HP TouchPad CM9
[TouchPad General] scrizz:
idk if people realize that you can change lcd density at any time.

I set mine to 160 if i need to buy an app or something, and later set it to 132 to enjoy the awesomeness.
[TouchPad General] Smac7:
Or use the market fix and leave it at 132 (i prefer 142 though)
[TouchPad General] The Jack of Clubs:
Do any other devices change the LCD density property in build.prop to coincide with screen dpi? 160 just looks the best to me. There's no slight blur or anything. Just the launcher icon grid not behaving. 155 fixes the launcher and doesn't break the market but at the cost of a few ui elements looking out of place. And while 132 is the screens actual dpi everything looks horrible. Typically phones are set to 240 regardless of screen size.
[TouchPad General] iamsamsamiam:
Not true.

The Samsung Galaxy S has 233ppi screen but it set natively to 200dpi.

The Samsung Galaxy SII has 218ppi screen but it set natively to 240dpi.

I thought they are set to adhere to whatever screen type they are, whether ldpi, mdpi or hdpi. You can still have a mdpi phone that has a 3inch~ screen, however, it will just have a horrible resolution.
[TouchPad General] YOUCANNOTDENY:
There is still some inaccuracy in that statement. The Galaxy S does not have a true 233ppi screen due to its PenTile subconfiguration, so the Galaxy S II (RGB) actually has a greater ppi.
[TouchPad General] iamsamsamiam:
Well I took the information from Wikipedia. Both screens are the same resolution, 800x480, but the SII's screen size is obviously bigger. Because the i9000 has a 4.3inch screen size I guess its matter of straight math that gets the 218ppi number. While I'm not going to argue the PenTile thing as we assume sub pixels work like actual pixels when in an array even when they're incomplete when individualized.

A Motorola Droid Bionic has a higher ppi than the SII because it simply has a higher resolution with the same sized screen. 960x540 has more ppi than 800x480 at the same size.

So I'm going to say there was nothing wrong with what I said. And I don't know how you can say the SII has a high ppi, Samsung screens have been notorious for sacrificing resolution for screen vibrancy.

Samsung Captivate CM9 - Glitch Kernel | HP TouchPad CM9 - Bricked Kernel