Is anyone running the newest version of LiquidSmooth for i9300? There isnt an official thread for this ROM anymore. I have posted on their facebook page but I havent had any success at getting a reply. I downloaded the new version of the ROM and cannot get it to flash properly. I have been running RC1 for a while now and that is 4.2.2 so I guess it cant be an issues between 4.2.2 and Siyah Kernel. Does anyone have any ideas or solid help for me and any other potential users of this ROM. Thankyou anyone who can help
Try Google for an alternative location for that rom .
The roms thread is active today in development so no idea what you are saying .
The dev is not updating his page he may no longer wish to post on XDA is one possible reason .
Page one
e are an open source project feel free to look at our code on LiquidSmooth GitHub
Also feel free to let us know your thoughts or just hang out and talk in our IRC chat.
Server: irc.freenode.net Channel: #liquids
jje
I have searched other variants of the Galaxy s3 as well as people with this version and they seem to have it working but none of them are helping me get it working, it could maybe be a kernel issue but on the official website for the rom there is nothing about kernels that do or dont work.
Could you please copy the link to the page as i have looked in both Original and normal and cant see one for v2.1 only the older closed threads for 4.1.2 Thanks
I'm also looking for this, can only ever find RC 1.
Sent from my GT-I9300 using Tapatalk 2
It's pretty easy to find.
http://goo.im/devs/liquidsmooth/i9300/
RC2 and Stable have new GPU drivers.
Siyah Kernel has NOT been updated to support this.
DON"T use Siyah.
jemz0r said:
It's pretty easy to find.
http://goo.im/devs/liquidsmooth/i9300/
RC2 and Stable have new GPU drivers.
Siyah Kernel has NOT been updated to support this.
DON"T use Siyah.
Click to expand...
Click to collapse
The latest OFFICIAL liquidsmooth release for hte i9300 is totally broken and the stable version link has been removed.
Siyah has now updated his kernel for cm10.1 and works wonderfully.
danielk0302 said:
Is anyone running the newest version of LiquidSmooth for i9300? There isnt an official thread for this ROM anymore. I have posted on their facebook page but I havent had any success at getting a reply. I downloaded the new version of the ROM and cannot get it to flash properly. I have been running RC1 for a while now and that is 4.2.2 so I guess it cant be an issues between 4.2.2 and Siyah Kernel. Does anyone have any ideas or solid help for me and any other potential users of this ROM. Thankyou anyone who can help
Click to expand...
Click to collapse
I'm running JB-v2.1-Stable (4.2.2). Works great, however you need the latest Siyah kernel 1.9.1 (available from his website/blog) (if you want to use Siyah). However this kernel will no longer work for JB 4.1 versions of roms. Need Siyah 1.8.9 for anything before JB 4.2 (bit of a catch 22).
i9300
Siyah 1.9.1
Liquidsmooth v2.1 Stable 4.2.2
2nd Rom - Ever Changing
Related
Hi guys, i'm using KI8 stock with siyah 1.8 right now, and it looks like one of the best configuration for galaxy S2.
Anyway, i'm very interested about trying the famous cyanogenmod 7.1 stable, and i just want to have some judgement about it...it's faster and more battery safe than a stock? it's the best?
[NIGHTLY][ROM][GWK74] CyanogenMod 7 (w/ Gingerbread 2.3.7) for Galaxy SII Q&A contains 6,602 posts relating to CyanogenMod, or since you mention 7.1 "stable" (it was later changed to RC1), [ROM] CyanogenMod 7 for the Samsung Galaxy S II :: V7.1.0 RC1 (9 Oct 2011).
There is no stable release. There is a lot of issues and you should really wait and go with MIUI or one of the modded samsung roms for now
RicoonDK said:
There is no stable release. There is a lot of issues and you should really wait and go with MIUI or one of the modded samsung roms for now
Click to expand...
Click to collapse
Wrong. There is a stable release, and you can download it from the link posted above. Also, it's not full of bugs, but if you're going to try it, I suggest you go for the latest nightly; it should have more fixes than the stable build. However, it's an experimental build, so be prepared for weird things. I'm using it since a long time, and it's really stable on my phone.
Also, learn to f***ing post in the right thread
RicoonDK said:
There is no stable release. There is a lot of issues and you should really wait and go with MIUI
Click to expand...
Click to collapse
Which is based on CM7 and therefore would contain most if not all of the same "issues".
in the cyanogenmod official page the rom it's called "stable"...and anyway i think MIUI has more issues than CGM...
Could anyone provide me with a link to the latest CyanogenMod cm10 (stable or nightly) for the AT&T Galaxy S3?
I have spent all day trying to get DirectoryBind to play nice with the newest nightlies based on 4.2.1 with no success. I have posted a plea for help in response to another user experiencing similar DirectoryBind woes at this link:
http://forum.xda-developers.com/showthread.php?t=1410262&page=126
However, until someone comes along with a solution for this issue, I want to get the latest version of cm10 based on 4.1.2 on my Galaxy S3 but can't find a link for it anywhere. CyanogenMod update on the phone only lists versions on cm-10.1, even with "All versions (incl. Nightlies)" selected.
I am currently running 10-20121127-NIGHTLY-d2att on my S3. While it is fairly stable, there are a few issues I was hoping would be ironed out before the team made the jump to 4.2.1, namely the fact that the home button won't wake the device a majority of the time.
If anyone could help me out, I would be immensely grateful!!!
NinjaBurg3r said:
Could anyone provide me with a link to the latest CyanogenMod cm10 (stable or nightly) for the AT&T Galaxy S3?
I have spent all day trying to get DirectoryBind to play nice with the newest nightlies based on 4.2.1 with no success. I have posted a plea for help in response to another user experiencing similar DirectoryBind woes at this link:
http://forum.xda-developers.com/showthread.php?t=1410262&page=126
However, until someone comes along with a solution for this issue, I want to get the latest version of cm10 based on 4.1.2 on my Galaxy S3 but can't find a link for it anywhere. CyanogenMod update on the phone only lists versions on cm-10.1, even with "All versions (incl. Nightlies)" selected.
I am currently running 10-20121127-NIGHTLY-d2att on my S3. While it is fairly stable, there are a few issues I was hoping would be ironed out before the team made the jump to 4.2.1, namely the fact that the home button won't wake the device a majority of the time.
If anyone could help me out, I would be immensely grateful!!!
Click to expand...
Click to collapse
Here is the link to Cyanogenmod 10.0 stable for the AT&T Galaxy S3 http://get.cm/get/jenkins/12630/cm-10.0.0-d2att.zip.
Sent from my SCH-I535 using xda premium
Hi everyone
My issue is somehow strange, I performed a clean install (full wipe, etc..) with Dorimanx Kernel 7.43 of Neat ROM 4.0 (XXLSJ) as primary ROM
When I install secondary ROM, Neat ROM boot loops and get stuck on the first Samsung bootanimation (where the logo is being drawn again and again)
I fixed permissions for secondary ROM, but still no boot, neither primary, nor secondary
I thought that ROMs are independent but seems like I'm wrong
Now I'm hesitating to retest the same with 7.44 kernel and 4.1 ROM (XWLS8)
What Have I messed ?
PS:
I reflashed my ROM and my phone is working fine, this thread is not about solving bootloop (with hundreds of threads dedicated here), it's about dual booting
Dorimanx doesn't support dual boot with any Samsung jelly bean roms currently
So it's kernel related, I did not notice this detail when flying over the changelog or the infinite number of replies :silly:
Thank you for the quick answer...
Try this Siyah MCM Kernel ver 3.0.60
http://sourceforge.net/projects/cm10i9100vsync/files/kernel/
I believe it is smoother than the Dorimanx Kernel and it supports dualboot.
Tha'ts the Kernels XDA thread:
http://forum.xda-developers.com/showthread.php?t=1891222
Not exactly sure what Conny has posted, but just incase you didn't know dual boot can't work with any siyah or dorimanx kernel till the dev fixes it, and only siyah 6 beta 1 or above and dorimanx v3.37 or above work with samsung jelly bean
1Chef said:
Not exactly sure what Conny has posted, but just incase you didn't know dual boot can't work with any siyah or dorimanx kernel till the dev fixes it, and only siyah 6 beta 1 or above and dorimanx v3.37 or above work with samsung jelly bean
Click to expand...
Click to collapse
1Chef is right, I thought Neatrom published a 4.2.1 release
Considering neatrom is based on stock Samsung and not aosp then it can't have released 4.2.1
Got another bootloop while trying (hopfully) the new setup (7.44 + 4.1.2 XWLS8), nothing happened
I think that siyah will give the same result as Dorimanx is forked from, maybe with latest stable future release of Siyah, it could be fixed.
Now, I got tired from re-re-re-re-reflashing my phone :silly:
I'd better wait
Newbie Takes The Plunge to Custom Rom and Kernel: Any Suggestions?
I'm still fairly a newbie, but have rooted two phones so far, thanks to the great information, tutorials, guides, resources, and videos posted here on XDA. I have a Samsung Galaxy S2 GT-I9100 and my daughter's Samsung Epic 4G.
I rooted my I9100 successfully a few months ago, but have never flashed a rom. I'm going to try out Neat Rom Lite tonight. I've finally gotten up the nerve!
QUESTION: Does anyone have any suggestion of which kernel I should flash along with it? I need better battery life. I would love to be able to watch videos and use the phone regularly and make it through the whole day without charging. Is this possible? Can a kernel and Neat Rom Lite do this for me?
Also, I rooted the Samsung Epic 4G yesterday. Any suggestions on what rom and kernel to put on it and how would be greatly appreciated.
Thanks a bunch for any assistance and comments.
Hello,
I've been away from the SGS2 development thread for quite a while now, so forgive me. I got a few questions:
- Why isn't official (sammy based) MIUI v5 based on 4.2.2?
- Is the current version official build MIUI v3.10.18?
- OTA is supported from official rom?
Many thanks
1) Because there is no official Samsung based 4.2.2 at all.
2) If you look at miuiandroid.com, you will find the last version(s).
3) I believe so. Didn't try it when I used MIUI, but it should be working.
Donnie Sins said:
2) If you look at miuiandroid.com, you will find the last version(s).
Click to expand...
Click to collapse
Edit: Never mind, found it, many thanks!
Hi folks,
I can't post at the end of this thread, http://forum.xda-developers.com/showthread.php?t=1822447&page=46, so I have to create one here... sorry...
Has anyone got NFC working on original vanilla CM10.1.3 (4.2.2)? I've tried plain old 10.1.3 and RC2, with the V8 patch from the thread, but although I have a menu option, it won't read any tags. I've also tried with the Dorimanx 9.43 kernel and still nothing is doing.
It used to work fine with my original Orange 4.1.2 ROMs - but I got fed up of the bloatware.
Does anyone have any idea what I'm doing wrong?
Thanks in advance.
say170 said:
Hi folks,
I can't post at the end of this thread, http://forum.xda-developers.com/showthread.php?t=1822447&page=46, so I have to create one here... sorry...
Has anyone got NFC working on original vanilla CM10.1.3 (4.2.2)? I've tried plain old 10.1.3 and RC2, with the V8 patch from the thread, but although I have a menu option, it won't read any tags. I've also tried with the Dorimanx 9.43 kernel and still nothing is doing.
It used to work fine with my original Orange 4.1.2 ROMs - but I got fed up of the bloatware.
Does anyone have any idea what I'm doing wrong?
Thanks in advance.
Click to expand...
Click to collapse
It is working on 4.1.2 only not with 4.2.2 IMO.
Sent from my iPhone using Tapatalk.com/m?id=1]Tapatalk[/URL]
per the first post in that thread, there's a version for 4.3 and 4.2.2. i've tried both and I have the same problem. I don't really want to revert back to stock rom, but I may have to