Variance in jvk installations - Galaxy S I9000 General

Bare with me as I'm pretty much a novice when it comes to tinkering with phones but can someone explain why there are so many variations in the results of flashing phones with, specifically, jvk gingerbread?
I flashed my phone a few weeks ago when jvk was initially leaked and I've had no issues. My battery lasts my 18 hour day from waking up to going back to bed with plenty to spare and pretty heavy usage, I've experienced no bugs, no issues with games, screen rotation problems, gps problems. Its been as good as, if not better than froyo (the battery life certainly is) but then other people experience all manner of issues with the same installation. Where does the inconsistency come from? Odin? The files? The phone? Why do bugs effect one phone but not another?

i think it has to do with the previous ROM and files on the phone what cause bugs (apart from the bugs stated in the actual ROM )
thats why people HIGHLY recommend a full factory reset along with formatting sd card / datadata/ cache partition / dalvik cache and so on.
to ensure a complete and empty phone before installing the new ROM

You probably have a point.
Mine was stock unmolested 2.2.1 which had, had a factory reset a couple of weeks before I installed jvk due to failing to start.

a lot more could be down to third party apps as well, and pulling the battery out without turning the device off.
this doesnt give the phone time to save open apps / files. this can cause issues in the long run.
you wouldnt just unplug your PC without shutting it down would ya so i guess the same thing goes for these modern day smartphones

Plus its a beta firmware .
jje

-Liam- said:
Bare with me as I'm pretty much a novice when it comes to tinkering with phones but can someone explain why there are so many variations in the results of flashing phones with, specifically, jvk gingerbread?
I flashed my phone a few weeks ago when jvk was initially leaked and I've had no issues. My battery lasts my 18 hour day from waking up to going back to bed with plenty to spare and pretty heavy usage, I've experienced no bugs, no issues with games, screen rotation problems, gps problems. Its been as good as, if not better than froyo (the battery life certainly is) but then other people experience all manner of issues with the same installation. Where does the inconsistency come from? Odin? The files? The phone? Why do bugs effect one phone but not another?
Click to expand...
Click to collapse
Actually this is a very good question. I too installed JVK ... one of the first as soon as it was uploaded on 26th March. Rooted it, modded icons and its running like a dream ever since, no FCs,,fast, smooth and nearly 2 days battery typically.
Strangely for JVK I parted from my normal policy of factory resetting, formatting SD, using PIT with re-partition etc, and despite having flashed many ROMs and kernels - from 2.1, 2.2, 2.2.1, JV1, Darky, Kitchen etc. etc its still purring away.
So for me at least, with the minimum of effort and preparation, JVK has proved an absolute winner.
I'm amazed at how much flack is flying around elsewhere against it...it is very strange to find such a range of experiences with the same hardware and the same firmware

mossy1963 said:
Actually this is a very good question. I too installed JVK ... one of the first as soon as it was uploaded on 26th March. Rooted it, modded icons and its running like a dream ever since, no FCs,,fast, smooth and nearly 2 days battery typically.
Strangely for JVK I parted from my normal policy of factory resetting, formatting SD, using PIT with re-partition etc, and despite having flashed many ROMs and kernels - from 2.1, 2.2, 2.2.1, JV1, Darky, Kitchen etc. etc its still purring away.
So for me at least, with the minimum of effort and preparation, JVK has proved an absolute winner.
I'm amazed at how much flack is flying around elsewhere against it...it is very strange to find such a range of experiences with the same hardware and the same firmware
Click to expand...
Click to collapse
Same here. I'd be seriously tempted to leave all as it is when a final version is released unless there was something specific that it offered that jvk doesn't. You see lots of people having all kinds of issues but it wouldn't help if I just posted that mine was fine and they must be doing something wrong, hence my question.

Related

Shifted back to eclair 2.1

Hey all!
Brief introduction, just got myself a galaxy s a month ago....and shifted out from being a diehard hardcore winmo fan for the last 8 years! Android seems to be just brilliant and am totally loving it! Its a whole new OS compared to what ive been used to (winmo) for all these years - so yep, still exploring and figuring how things work on the internals
I've been trying froyo for the last month and it seemed nice in terms of the subtle refinements all across the os. However it still seems very unstable....overloading the ram causes the device to freeze, and then later it failed to boot...forcing me to restore factory settings. Finally, decided to roll back and give 2.1 a shot....and holy hell!!! its fasttttttt! Compared to our beta 2.2 build 2.1 is a world of difference! a lot more free ram available on the 2.1 build compared to 2.2 (almost a 100 megs more on 2.1!).
Anyway, I guess we'll have to just wait for samsung to clean it up and give us a stock 2.2 rom
same here... currently switching back to 2.1 ... 2.2 is nice, had JPC installed... has some cool new features and possibilities... but its still too buggy for me... today phone won't boot and i had to do a hard reset... this is annoying ... so waiting for the official realease of 2.2 and still looking forward to it
greetings from austria
aigolf
same here, switch back to eclair.
Although the 2.2 is a such pleasing experience over 2.1, it certainly is falling short on a lot of things for a daily phone. It also is being quite a pain in the rear while developing apps and trying them on the phone.
I quite agree with the fact that it would be much better to wait it out for Samsung to provide a proper 2.2 version.
Cheers....
Been using 2.2, now back using XWJM7. I have a good feeling about final version of 2.2 for SGS. I saw demos of Galaxy Tab using 2.2 on youtube, runs very smooth (almost same identical hardware with SGS). Expecting the same performance with SGS.
Samfirmware has just published their own package for JPC under the european FWs section. Do you think this could mean that all product code, IMEI, and other related issues with the KIES "leaked" JPC could be avoided and we can safely give it a try this time?
Since i got the phone one month ago i sticked with Eclair, trying several FWs for lag and battery draining aspect. Trying JM7 right now. Still have to find something fully satisfying.
Same here, I had JPC and Doc's modded Rom installed but still had a lot of FC's and it seems to me that the battery life is a tad worse than 2.1. Come on already Samsung! let's have the official Froyo!
Dont you just hate it when that happens
Seriously ?
I have had minimal problems with JPC.
Battery life has been massively improved, lag has been minimal.
The only real niggles i have had is the keyboard locking up a couple of times in the google search box.
Weird Huh ?
Exact same boat. Tried out Froyo and it was far too buggy so went back to Eclair. Waiting on Samsung to push out an official Froyo update.
lordjubblydave said:
Seriously ?
I have had minimal problems with JPC.
Battery life has been massively improved, lag has been minimal.
The only real niggles i have had is the keyboard locking up a couple of times in the google search box.
Weird Huh ?
Click to expand...
Click to collapse
Some people seem to be lucky but I've had hard-lockups regularly - my first install failed to boot after a couple days of use, I re-flashed and today had a crash/lockup, pulled battery, another one within 5 minutes of use, pulled battery, another one within 10 minutes of use. Only seems to happen when I'm doing certain things though, mainly web browsing / apps that render HTML, I played music on it for 2 hours straight with no trouble and games were fine.
Flashing back to eclair as soon as I can figure out which rom to use (I was on stock until JPC because I was happy enough with it and sick of buggy alpha ROMs from trying to make my 32B Magic more usable).
i have now jpc on my phone and works smootly
How to downgread back to 2.1, and where to get stock 2.1 firmware ???
wow!! this is by far the most active community ever i guess we have a lot of galaxy s users....and thats just awesome ;o)
im sure stock 2.2 from samsung should be really quick in comparison. 2.1 that im currently running works flawlessly and is also really really quick! I consistently have over 120megs of free ram...and when i clear ram it diligently goes back to 200megs free ram....always!
I think 2.2 has a load of memory leaks or perhaps a mismatched kernel...but seriously guys, its about time samsung gave us the stock rom!
They provide the source code, but they probably don't provide a fully stock rom because they don't want to encourage people to flash their phone unsafely.
JPC was terrible compared to JM7.
There are a few things I liked - the browser was making improvements, and high res cover art on the music player, and one or two other minor things, but otherwise, slow, buggy and annoying.
JM7 is the best I've used yet, WAY better than JPC.
I don't know about anyone else, but mine is staying that way now until a STABLE, FAST 2.2 firmware is out. Given how the 2.1 firmwares have progressed since it came out, I think I wont be flashing again for 2 - 3 months... I simply cannot be bothered with all this any more, all I ever wanted was for it to work properly in the first place. It is only because of this forum I've kept the phone as long as I have. I respect those who like to experiment, but I can't be bothered any more.
i'm staying with a clean install of jpc (SF Vers)
quadrant 1098
linpack 14.1
feels good to me
Tried 2.2 JP3 & JPC but 2.1 DDJG4 is far more better .. just rolled back to 2.1 its nice now..
Major problem with JPC for me was Exchnage mail reply block ... well repplied some official mails but recipients dint recd them ....
2.2 not ready yet for Galaxy .. We'll wait for Final release.
i have problems with zsjp2 and xxjpc, and both times i had used titanium to restore my apps. Even selectively restoring the apps, i do encounter problems of FCs, laggy, etc.
i did not roll back to eclair but did a fresh flash of jpc and discarded all the titanium backups. i did a fresh install of all the apps, and right now it is pretty good and smooth, and minimum lag encountered even without any lagfix.
of course eclair right now is a very much more stable rom, especially right now with the voodoo fix, it is indeed very tempting. however, after much deliberation, i decided to stick to jpc, until a new version comes.
p/s: my recovery had been downgraded to 2e and it does not require any signature verification at all, and all this is made possible by Leshak.
G00ndu
Do you sync with exchange?
Sent from my GT-I9000 using XDA App

Gone full circle

ok. So over the last 18 months I've tried just about most roms.
Most are nice to look at, some come with lots of bits added on, some stripped bare.
I've done the "trying to get the highest benchmark score possible" despite it making no difference at all in practical terms.
I've sweated while flashing my phone after semi bricking it on more than one occasion and can now get myself out of trouble with my eyes shut.
I flashed the early gingerbread roms when we was all still on froyo.
I flashed the early ics builds.
But.
Due to sky-Go (uk only) not working on rooted handsets, I am now back on a stock, unrooted jvt gingerbread rom.
You know what ?
It works better than just about every custom rom available. Don't get me wrong, I'm not knocking the hard work of the many developers that have worked on improving things over the last couple of years, and I'm sure Samsung devs have taken some of their ideas on and passed them onto stock roms, but, it just does. It doesnt lag. Games work fine. All cameras work. Radio works. Battery last me 2 days. Gallery doesnt force close when you try to open it, all storage works out of the box, No Force closures. Bluetooth and wireless are solid and the gps works exactly as it should.
Try finding me a modified rom that checks all of those boxes.
Don't bother. I know there aint many!!
So perhaps they actually know what they are doing ?

GB to ICS and back - mini review

My month with a factory unlocked Galaxy S2​
Bought this in mint condition from a friend for about half price with only 1 hour of use, an unwanted upgrade. Came with 2.3.4 as expected, so hooked up to Kies; no update at the time. As is my wont, I used the phone for a few days to get to grips with TouchWiz (TW) and the phone generally. All quite reasonable, no stability issues and TW is not bad by any means.
My thoughts and trials so far then:
Hardware
Well made, light and thin. Slippery, so a black rubbery skin bought and fitted and I popped a spare 8GB microSD card in, not that the phone needs it for my purposes.
Only criticism is the OLED screen, I'm used to higher resolution (Moto and Sony) and 800x480 looks rather "cheapo" in terms of detail on a screen this large, but no deal breaker. What I do find somewhat at odds with the price of the phone is the slight but noticeable shading and colour tints across the screen at low brightness levels and on some backgrounds. Plus, the screen's legibility outside on a bright day is no better than more run of the mill LCD screens. (I mean cheaper!)
My first GB update
I generally root phones straight after flashing a new firmware version, if it isn't already. I had already successfully rooted the original stock 2.3.4 firmware with Zergrush 4 and debloated that ROM.
I was keen to try a later GB version before trying ICS, and I found 2.3.6 for "Open Europe" on Sammobile and downloaded it. I had already tried Kies, so the USB drivers were present and working. I uninstalled Kies on the PC but left the USB drivers alone. Kies and Odin are not good bedfellows. I did a full factory reset on the phone and erased everything, allowed it to reboot and then powered off, got in to download mode and flashed XXKL1 (which is an engineering version and deodexed it seems). Rooted it via Zergrush 4, deleted known bloat and renamed possible bloat to xxx.bak to clean the ROM for my own usage, and deleted that very annoying start-up sound. Downloaded all the apps I normally use (about 22 of them), including the excellent CPU Spy to check for deep sleep.
I used/charged the phone over the next couple of days to let the OS bed in. No problems encountered at all, and a very pleasing battery life of 30+ hours of light use, with syncing and GPS, 3G, WiFi always on and occasional BT. Magic! Only thing I did is change the Modem to LPR - the KI3 Modem that came with the ROM is not quite as good at holding weak signals. Only just though...
My first ICS update
So, good phone, stable and very usable ROM in 2.3.6. Time had come to try this new ICS thing. Downloaded the LPQ version and installed it, after a full wipe, via Odin. Not impressed by all the automatic installation rubbish at first boot... Rooted via a hot boot CWM and SU/Busybox successfully and did all the same debloating and app installation as GB 2.3.6. Spent some time getting orientated and used to the new menus and so on.
Over the next day or so, I let the ROM settle and began using the ROM - I changed the Modem to LPR as LPQ was not as good, perception wise. ROM was stable and usable, didn't really look or feel much different from 2.3.6 and was worse on battery - I would say 18 hours at best with the same usage pattern.
Absolutely hate the new Exchange thing for live.com email.... real pain usability wise and battery unfriendly.
My second ICS update
So, not overly impressed with LPQ, although it was usable, I decided to try LP7, the UK generic one. Went through the same process as above, and again swapped the Modem from LPS (awful!) to LPR.
No obvious differences at all. Battery life was as poor, but it was usable.
My first CM trial - CM9
So, somewhat disillusioned by Samsung's ICS implementation, I decide to look around for another "mature" ROM. CM9 fitted the bill (I have used CM6 before on another phone) and was smack bang up to date in terms of kernel, AOSP and G Apps. After my usual clean deck start, installed fine, 23/04 build.
At first, I was quite impressed as I could configure more and to my liking. The ROM was stable and I set the phone up with the usual Apps and deleted some useless stuff (like GenieWidget).
Swapped Modem out to LPR - bit of a theme going on here...
I liked the fact that the Spirit FM radio worked (so bought the Pro version as it is that good). The ROM is very usable and never got bogged down, BUT, for reasons I never fully determined, the battery life would start OK and then decline faster during the day. I never saw more than 12 hours life, again using as per my normal pattern and after a few days to settle. There appeared to be various background activities going on that were preventing deep sleep sometimes, but BBS was not really showing me what. Note that I only use BBS as a last resort as it can increase battery use...
No other real problems, but the soft key backlights wouldn't play with NoLED and were somewhat counter-intuitive. A bit trivial, but a mess.
My second CM trial - CM7
I like GB, it is mature and well understood, so CM7 RC 2 was therefore of some appeal. It had been developed over months and must therefore be fairly sorted. Surely.
Installed without issue on a cleaned platform as usual, including G Apps. Did the usual debloat and installed the usual Apps from the Market/Play, and some that were missing, like GMail. LPR modem was already there, Hooray! Spent rather longer fiddling with the settings in CM7 than CM9 since they were less obvious at first, to me anyway.
Switched off and put the phone on wall charge overnight and was rather shocked to find the phone was noticeably warm and displaying "Kernel Panic" in the morning. The phone had only charged by about 5% in total (to 64%). Worry Worry. I put the phone on USB charge until 100% without incident.
Started to use the phone as normal, the phone UI and operation was very good, fluid even. But, first problem I had was in the car. I paired BT fine, as usual, and made a phone call. After the call, I couldn't end the call on the car or phone - it had locked up. Oh dear.
Later, I tried the FM Radio during my daily walk - doesn't work, so why is it there? I tried Spirit FM - no way would it work. Oh dear.
The following day, I noticed that the battery life was amazing! I had never seen this phone sip juice like this. Deep sleep was always easily achieved. That was until the afternoon. I noticed that the battery level was declining at a much higher rate than earlier. I hadn't done anything different, so BBS was called in again. Nothing obvious shown but I kept seeing the GPS icon winking at me from the Notification bar, and continually. I always keep GPS on, but for some reason on this ROM, no GPS signal meant the ROM just kept trying. I played with various settings like Location etc. and managed to stop this odd behaviour, but this was too silly. I use a Smartphone for all the smart features. This wasn't very smart at all.
CM7 was my biggest disappointment of all the above ROM trials. It was the lightest and most promising, and yet the least reliable or functional. Which is a huge shame...
Today...
I'm now back on KL1 2.3.6, and it just works fine - day after day.
The future for me?
I would really like to use CM9 (or CM7 for that matter). They represent a number of ideals for me, including the open nature of development, the collaboration, a pioneering spirit and giving users a choice and a superb base to build on. I am no developer - I can split and modify kernels to a point, I can rehash ROMs with or without adb, I can amend frameworks. But little more.
Reserved for "tips and hints"
Avoiding problems
Always data reset and wipe before doing anything major from one ROM to another, or follow the installation guide for any specific differences in approach.
Avoid Titanium Backup like the plague - it invariably leads to functional issues later if you cross flash. Use Google and/or airdroid for everything, it all just works. So many friends and other forums I contribute to have had too many backup issues to count. Go clean. Forget about Google paranoia.
ES File Explorer is very useful and recommended.
Don't bother "calibrating" the battery - it's an outdated practice and useless. Just use the phone normally, and anyone who claims the battery life is "great" 1 hour after flashing a newly announced ROM is a fool. Likewise NEVER fully discharge a Li-Ion battery. Just keep topping it up. See here: http://batteryuniversity.com/learn/article/how_to_charge_when_to_charge_table
Thoughts
Newer ROMs are rarely better ROMs. Better means different things to different folk of course.
ICS ROM core LPQ to LP8 are largely all the same, just variants of the same thing for different markets. Some users believe they perform differently.
Custom kernels and ROMs are always work in progress and should be treated as such. Check out the number of revisions. Some kernel cookers are (welcome) enthusiastic amateurs that assume more is better and cram "fixes" in that the professional salaried software engineers have mysteriously missed. If you only need your stock kernel to be insecure, learn how to make it so. You are running Linux on your box, right?
Deodexing is not a means to improve performance, on the contrary.
Undervolting is a mythical beast
I bought a phone with an FM radio because I want to use it!
And I totally agree. to all of it. Tried all iterations of almost all roms available. For some reason keep going to my VR 3.0 nandroid back up.
Except CM9, I don't really think there is any real development going on. Most are just cooked up roms OR stuff taken from the CM9 tree and implemented OR so called fixes that have actually broken something else OR just debloated rooted official firmware (that AFAIK is pretty easy to do with the fantastic dsixda's kitchen or on a rooted rom).
Now fanboy's may flame as much as they wish to, but seriously a stable CM9 (hopefully..!) or a VR 4.0 is all I am willing to wait for.
Till such time VR 3.0 it is.
LenAsh said:
Reserved for "tips and hints"
Newer ROMs are rarely better ROMs. Better means different things to different folk of course.
ICS ROM core LPQ to LP8 are largely all the same, just variants of the same thing for different markets. Some users believe they perform differently.
Click to expand...
Click to collapse
I don't agree with your final thought. Different ics rooms have really different feels. E.g. Look at scrolling from lpq to lp7.....and there are numerous others as well. If u want more specific thoughts and feedback, just browse through different ics threads in this section..
omeryounos said:
I don't agree with your final thought. Different ics rooms have really different feels. E.g. Look at scrolling from lpq to lp7.....and there are numerous others as well. If u want more specific thoughts and feedback, just browse through different ics threads in this section..
Click to expand...
Click to collapse
Hmm... I have browsed through the sections, and tried various "revisions" or versions of Samsung ICS today while jotting this lot down, and my view, honestly, is there is no real difference. That isn't to say there isn't, I just can't see or feel it. I do accept that playing with 3 ROMs in a few hours is less than ideal. And a drag!
I suppose if someone could deconstruct the ROMs properly and thoroughly...
Anyway, thanks for your thoughts, appreciated.
Very nice review! +1
Keep up the good work
I broadly agree with the OP.
ICS/AOSP/AOKP/CM9 have improved over the last few weeks, but I'm back on GB, and will probably stay with it until I get the SGS3.
May be subjective, but for me the GB stock browser, camera and dialler are streets ahead of what the rest can offer. Scrolling is smoother too. And I like/need a radio.
B3311 said:
I broadly agree with the OP.
ICS/AOSP/AOKP/CM9 have improved over the last few weeks, but I'm back on GB, and will probably stay with it until I get the SGS3.
May be subjective, but for me the GB stock browser, camera and dialler are streets ahead of what the rest can offer. Scrolling is smoother too. And I like/need a radio.
Click to expand...
Click to collapse
Seems like you and the OP only tried the AOSP/AOKP roms? Give the roms based on the latest official a try.
The dialer is still as good as always (unchanged), camera is actually improved with higher bitrate recording and the ics stock browser...is untouchable at the moment in my opinion. (Granted I use "ICS Browser+" from the market which uses the best ui in a browser I've encountered)
I currently use Dynamic's ICS rom and it would be extremely difficult for me to go back to GB at this point.
Sigurd02 said:
Seems like you and the OP only tried the AOSP/AOKP roms? Give the roms based on the latest official a try.
The dialer is still as good as always (unchanged), camera is actually improved with higher bitrate recording and the ics stock browser...is untouchable at the moment in my opinion. (Granted I use "ICS Browser+" from the market which uses the best ui in a browser I've encountered)
I currently use Dynamic's ICS rom and it would be extremely difficult for me to go back to GB at this point.
Click to expand...
Click to collapse
While I agree that in terms of loading websites, ics default browser is a little bit faster, scrolling and pinch and zooming is much smoother with stock gb browser. Also the dialer is worse on ics as it has removed the contacts section which means I have to put both the dialer and contacts shortcut on the dock.
I'm using Wanamlite v11.1, Siyahkernel v3.1, and Apex Launcher.
A winning combination in my opinion, that is now at least as good as the best GB ROMs in terms of battery life. 7 hours standby with 30 minutes screen time and i'm still on 87%.
In terms of fluidity and performance I think ICS /w Apex beats GB handsdown.
Thanks for the recommendation, but I avoid ROM mix ups, I can do that myself. The ones I have looked at have had some very dubious scripts and additions. I usually look at build.prop first, and generally find all sorts of hybrid attempts at adding stuff that is completely wrong. Lines taken from websites, other phones and so on.
LenAsh said:
Thanks for the recommendation, but I avoid ROM mix ups, I can do that myself. The ones I have looked at have had some very dubious scripts and additions. I usually look at build.prop first, and generally find all sorts of hybrid attempts at adding stuff that is completely wrong. Lines taken from websites, other phones and so on.
Click to expand...
Click to collapse
Depends, it was like you say in Gingerbread days, not with ICS WanamLite nor Dynamic, only tried these + CM9
I am using Dynamic 1.4 LP9, it is as smooth and fast as CM9, but everything working because it is Samsung based
I tried the included NEAK and Speedmod kernels, similar performance and very good battery life, only 3% drain overnight, I dont play with processor tweaking
Sigurd02 said:
Seems like you and the OP only tried the AOSP/AOKP roms? Give the roms based on the latest official a try.
The dialer is still as good as always (unchanged), camera is actually improved with higher bitrate recording and the ics stock browser...is untouchable at the moment in my opinion. (Granted I use "ICS Browser+" from the market which uses the best ui in a browser I've encountered)
I currently use Dynamic's ICS rom and it would be extremely difficult for me to go back to GB at this point.
Click to expand...
Click to collapse
Dialer is laggy if you compare it with GB. CM9 variants have slightly more response dialers but overall, GB dialer is way more responsive. There is a small but noticeable lag when pressing a key and the time it takes to register on ICS (CM9 & stock).
Camera recording with stereo voice recording...! Seriously how many people do shoot video with a phone's camera? For facebook uploads mono audio is just fine..
Browser is a definitive improvement yes, and the desktop mode is welcome but browser mods have been available on GB since long.
It is not that ICS is bad. It is actually very good, but the way it has been implemented on S2 is downright ridiculous...! And not one stable vanilla build isn't really helping..
kranti2064 said:
For some reason keep going to my VR 3.0 nandroid back up.
Click to expand...
Click to collapse
This is something I have been contemplating for quite some time now, quite possibly the last month. The only real thing stopping me is that for some reason alot of games (eg dead space and modern combat 3) don't seem to like it when i change roms, and even though all the ingame data is there, sometimes it decides I have to re-download.
I do miss it alot though.. and also red pill kernel
I might end up doing a backup of current my CM9 and take the plunge sometime soon. I've been using CM9 since around feb and lately I think my interest has plateaued and now I'm just beginning to get frustrated with little lags that are popping up more frequently (probably due for a wipe mind you!). The only thing about villiam rom is the bloody touch wiz launcher.. I just don't like messing with the launcher roms were made for either.
kranti2064 said:
Camera recording with stereo voice recording...! Seriously how many people do shoot video with a phone's camera? For facebook uploads mono audio is just fine..
Click to expand...
Click to collapse
Mass lols to be had at the fact that a majority of the time they would be played on the device through the mono loudspeaker too
I also go back for GB..becoz i feel that ics so laggy at dialer,and PES2012 freeze and cant play on ics..but in GB all working great..
Daripada galaxy s2 non-G
melorib said:
Depends, it was like you say in Gingerbread days, not with ICS WanamLite nor Dynamic, only tried these + CM9
I am using Dynamic 1.4 LP9, it is as smooth and fast as CM9, but everything working because it is Samsung based
I tried the included NEAK and Speedmod kernels, similar performance and very good battery life, only 3% drain overnight, I dont play with processor tweaking
Click to expand...
Click to collapse
kranti2064 said:
And I totally agree. to all of it. Tried all iterations of almost all roms available. For some reason keep going to my VR 3.0 nandroid back up.
Except CM9, I don't really think there is any real development going on. Most are just cooked up roms OR stuff taken from the CM9 tree and implemented OR so called fixes that have actually broken something else OR just debloated rooted official firmware (that AFAIK is pretty easy to do with the fantastic dsixda's kitchen or on a rooted rom).
Now fanboy's may flame as much as they wish to, but seriously a stable CM9 (hopefully..!) or a VR 4.0 is all I am willing to wait for.
Till such time VR 3.0 it is.
Click to expand...
Click to collapse
Currently trying ninphetamine kernel (as per VR3 - thanks for the heads up) on my fave stock KL1 more for interest than anything. Seems OK, no obvious difference from stock running as is apart from it being insecure, need a couple of days to evaluate in real life use.
Bloody good post. I've been using CM9 since the video recording bug was solved, and thats probably the longest I've used any ROM on the SGS2, I really like AOSP but the problem is it does still have quite a few bugs, and isn't quite as fast or as battery friendly as I remember the likes of Hyperdroid v6 being.
This makes me tempted to go back to GB. For me, it is still the ultimate for a daily driver. But I'm lazy so I'll probably stick with CM9.
kranti2064 said:
Dialer is laggy if you compare it with GB. CM9 variants have slightly more response dialers but overall, GB dialer is way more responsive. There is a small but noticeable lag when pressing a key and the time it takes to register on ICS (CM9 & stock).
Camera recording with stereo voice recording...! Seriously how many people do shoot video with a phone's camera? For facebook uploads mono audio is just fine..
Click to expand...
Click to collapse
ICS dialer laggy , doesn't happen to me on stock LP9 or Dynamic based on LP9 and CM9 is as smooth as they come. Whilst mono audio is fine for you I quite like having stereo audio. Choice, not limitations my friend
tameracingdriver said:
Bloody good post. I've been using CM9 since the video recording bug was solved, and thats probably the longest I've used any ROM on the SGS2, I really like AOSP but the problem is it does still have quite a few bugs, and isn't quite as fast or as battery friendly as I remember the likes of Hyperdroid v6 being.
This makes me tempted to go back to GB. For me, it is still the ultimate for a daily driver. But I'm lazy so I'll probably stick with CM9.
Click to expand...
Click to collapse
Cheers for that - I would definitely recommend the 2.3.6 KL1 off Sammobile if you want a solid GB.
Dude, if you have not tried CheckRom RevoHD V6, then you have not tried the BEST gingerbread rom for sgs2.
This is why I can not use ICS (yet). Checkrom is just too perfect of a Rom.
Try it, tweak it to your liking, use it for a week or 3 then try and go back to stock.
CheckRom XDA thread

Favorite Jellybean ROMS

Which ROM do you feel works the best for your Vibrant? Of course this is a matter of opinion, which is exactly what I want to hear. I'm running CM 10.1.3 right now and enjoying it. At times it can feel a little bit sluggish but I don't know if it's the ROM or my phone. I'd also be interested in hearing about your experiences with battery life in each ROM. I've been thinking of trying CyanAOSP because it's less cluttered and I have a hunch it would be more snappy.
Hopefully I'm not breaking any rules, I just wanted a really recent thread comparing the strengths and weaknesses of all the recent Jellybean ROMs. This isn't a question thread, it's more of an opinion thread.
I'm using CM10.2 build date - 10/15 for a day now. Have no problems. Everything works fine, including GPS after ds. Battery drain is normal.
selmandeli said:
I'm using CM10.2 build date - 10/15 for a day now. Have no problems. Everything works fine, including GPS after ds. Battery drain is normal.
Click to expand...
Click to collapse
What's DS? Also, have you tried 10.1.3?
oneupe1even said:
What's DS? Also, have you tried 10.1.3?
Click to expand...
Click to collapse
DS is DeepSleep. Its a state in which the phone uses minimal battery and thus the battery is saved.
oneupe1even said:
What's DS? Also, have you tried 10.1.3?
Click to expand...
Click to collapse
If you mean the official CM 10.1.3, yes I tried it. It is stable and smooth. You can use it as a daily driver.
selmandeli said:
I'm using CM10.2 build date - 10/15 for a day now. Have no problems. Everything works fine, including GPS after ds. Battery drain is normal.
Click to expand...
Click to collapse
I just saw that you were using CyanAOSP. How would you compare it to CM 10.1.3 and 10.2?
Also, do you know where I can get the 1.75 ROM? I've heard the 2.0 has problems.
been running cyanaosp 2.0 since its release and its been fine beside a few random reboots, but im sure it was cause i had my device oc'd to high. this rom is perfect for me as i play alot of games.
Hi all,
New member of the forums, but I've been reading as much as I can about my Vibrant (Fascinate?) and I'm still kind of confused as to which model my phone really is. It's a Telus model sgh-t959d, but after flashing CyanAOSP 3.0.0 for the i9000, my phone info shows model GT-i9000. I understand there are similarities between these devices, but I was a little nervous about bricking my phone by flashing the wrong ROM. Well, it was a painless process that took less than 2 minutes! I upgraded from PassionICS, which was a good ROM, but kind of laggy. After a day of use, I can say CyanAOSP is much quicker, more refined and more fun to use. The customizations offered by Nova launcher are quite extensive and make it feel like a new phone. I highly recommend this ROM! Many thanks to the hard working devs!
Anybody have kernel recommendations to get more battery life out of CM 10.1 or 2?
CM
Im using CM 10.1.3 stable, think this is a best and stable ROM
I was using one of the CM 10.2 nightlies (10/25 specifically) for about a week before giving up on some serious battery drain and background android OS data usage issues... First time I ever exceeded my 5gig threshold pushing me down to slower speeds. Also USB data transfer simply stopped working after about a week... couldn't even mount via recovery.
Ultimately had to get new ROM files into my phone via the microSD/USB adapter and internally transferring to the internal directory.
That said, CM 10.2 itself is a very pleasant experience if you can avoid such issues - In hindsight I'd strongly suggest giving it a try but with a build that's known to be stable and without any such major issues if you intend to use it as a daily driver (the 10/15 build has been recommended more than once in my forum trawling). Lesson learned!
I made the switch last Saturday (6 days ago) to SlimBean Build 2 however, which is also based on 4.3.1. By comparison to my last experience, this has zero issues falling back to deep sleep, even after loading it down with all my favorite apps and sync settings. I've had one random reset to recovery in the middle of a phone call, and gps performance has been hit or miss so far, but otherwise there's a lot to like! Battery is back to respectable charging intervals and background data is in check. ROM itself is very zippy. Lock screen by comparison to CM 10.2 seems slightly sluggish to respond. I'll likely be sticking with this for a while.

Nexus 6p MHC19I high RAM usage?

Hey Everyone,
So I eagerly flashed the MHC19I image on my 6p, since I'm always wanting the latest and greatest, even if the phone was basically perfect for me anyways with the Feb factory image.
I've noticed though after this update the phone seems to manage RAM much differently. Before, after a fresh boot, my "free memory" would usually be 1.4 GB. This has been pretty consistent across several updates (had phone since December). After using the phone for a while, opening closing apps, going through the day, etc. the memory usage would generally be around the same, with usually 1.4 or so free.
With this build however, when I first boot up the free memory is higher, 1.6 GB, which is great. However, after just a few minutes using a few apps, the free memory drops to 1.2 or 1.3, with "system" showing around 1 GB. I definitely never saw system memory usage this high before.
Anybody else seeing this? I know Nexus 5x users have been reporting lower memory usage with MHC19I, which is great since the 5x had some performance issues. I guess this build has changed the way the phones manage their memory. I'm not saying this is a bad thing necessarily, more of an observation. Just curious if others are seeing the same or if there's some random glitch with my phone / apps.
EDIT: I am stock, not rooted.
Interesting find. I'm still on Feb factory image just as you were. Phone is running great and I'm torn between flashing to the "latest and greatest" or sticking with what has been working wonderfully. Knowing me......I'll flash it tonight and report back my findings. I didn't get this phone to NOT experiment lol.
Also, I've read a lot of people having issues flashing to that newest build. A lot of users reported TWRP issues which scares me. I did find a thread that posted an experimental release of TWRP 3.0.1 (I think) that resolved the initial issues. Guess I'll give it a go...
Alex338 said:
Hey Everyone,
So I eagerly flashed the MHC19I image on my 6p, since I'm always wanting the latest and greatest, even if the phone was basically perfect for me anyways with the Feb factory image.
I've noticed though after this update the phone seems to manage RAM much differently. Before, after a fresh boot, my "free memory" would usually be 1.4 GB. This has been pretty consistent across several updates (had phone since December). After using the phone for a while, opening closing apps, going through the day, etc. the memory usage would generally be around the same, with usually 1.4 or so free.
With this build however, when I first boot up the free memory is higher, 1.6 GB, which is great. However, after just a few minutes using a few apps, the free memory drops to 1.2 or 1.3, with "system" showing around 1 GB. I definitely never saw system memory usage this high before.
Anybody else seeing this? I know Nexus 5x users have been reporting lower memory usage with MHC19I, which is great since the 5x had some performance issues. I guess this build has changed the way the phones manage their memory. I'm not saying this is a bad thing necessarily, more of an observation. Just curious if others are seeing the same or if there's some random glitch with my phone / apps.
EDIT: I am stock, not rooted.
Click to expand...
Click to collapse
That's so odd for someone on the bleeding edge to have issues. Give it time
do remember that our device has 2762896kB of available RAM.. and if you're not using 100% of that the extra space is going to waste.
..don't get me wrong, I love having some comfort room..but I also know a few ppl whos' laptop is less powerful than our 6Ps ;]
Sent from my angler using XDA Labs
dontbeweakvato said:
That's so odd for someone on the bleeding edge to have issues. Give it time
Click to expand...
Click to collapse
I'm impatient. They've had a whole day to work out the bugs
Pain-N-Panic said:
Interesting find. I'm still on Feb factory image just as you were. Phone is running great and I'm torn between flashing to the "latest and greatest" or sticking with what has been working wonderfully. Knowing me......I'll flash it tonight and report back my findings. I didn't get this phone to NOT experiment lol.
Also, I've read a lot of people having issues flashing to that newest build. A lot of users reported TWRP issues which scares me. I did find a thread that posted an experimental release of TWRP 3.0.1 (I think) that resolved the initial issues. Guess I'll give it a go...
Click to expand...
Click to collapse
Yeah Feb factory image was basically perfect for me. I don't use Bluetooth much so didn't have any of those issues. I had no issues flashing, but like I said I'm stock with no root, so no twrp to worry about. And yes we buy these phones to experiment!
Update: Had the phone completely freeze on me. First it lagged like crazy and wouldn't respond to touch, then screen went blank. Had to hold down power until finally it shut off. Seems to be fine after a reboot. I definitely never had anything like that happen since I got the phone. Hopefully it was some random one off bug!
quantumqweef said:
do remember that our device has 2762896kB of available RAM.. and if you're not using 100% of that the extra space is going to waste.
..don't get me wrong, I love having some comfort room..but I also know a few ppl whos' laptop is less powerful than our 6Ps ;]
Sent from my angler using XDA Labs
Click to expand...
Click to collapse
Yep I'm aware of all that. Like I said, not really a complaint, more of an observation.

Categories

Resources