Related
hi! like many of you i have been waiting for a clean aosp rom and it looks like we get some first taste of the forbidden fruit there. i found the following in the vibrant forums:
http://forum.xda-developers.com/showthread.php?t=757000
remember it's for the vibrant and it's alpha (no radio & other things) but i guess it should work for the i9000 as well. it's just a start but finally things are happening . i will give it a try shortly
thanks to eugene, barak and possible others i don't know of!
just flashed it and played a little bit and here is my report:
* wlan works but is slower than stock
* calling works but 3g-data doesn't
* camera doesn't work
i didn't test:
* bluetooth
* gps
everything else seems to work and is quite smooth!
quadrant-score: 859, 875, 845
very nice work for an alpha version! i'm quite excited for what's to come
edit:
* after sync and reboot wlan seems to be as fast as normal...maybe my isp f***** up (again).
* after moving /data/data to /dbdata/data (dbdata is not used by this rom) this thing is FLYING!
* everything seems stable so far
i think i will keep this for now even if data is not working. awesome experience to have stock android (again)!
Very nice to see a asop on the way. Lets hope some I9000 dev have the time to adapt this for galaxy
DocRambone said:
Very nice to see a asop on the way. Lets hope some I9000 dev have the time to adapt this for galaxy
Click to expand...
Click to collapse
after playing around with this i think there won't be a lot we have to change! just the kernel and the modules (i still use the JM2 kernel/zImage) and that's easy to adapt...
jodue said:
after playing around with this i think there won't be a lot we have to change! just the kernel and the modules (i still use the JM2 kernel/zImage) and that's easy to adapt...
Click to expand...
Click to collapse
How did you install this asop rom?
I guess some files mods are needed? Build.prop etc?
DocRambone said:
How did you install this asop rom?
I guess some files mods are needed? Build.prop etc?
Click to expand...
Click to collapse
nope. just flash the zip with clockwork over an existing firmware (in my case JM2). first boot will take a littel longer because of odex-ing.
Great to see some work on AOSP for the Galaxy S series. I've been surprised that no-one's done anything on it before, but confident that if the right people turned their minds to it they'd be able to get it running (even if all the drivers aren't sorted at first).
I don't really have a problem with TouchWiz, considering that I'm actually using LauncherPro and like the notification bar toggles etc. However, AOSP builds make me confident we'll see Gingerbread (and beyond?) because we won't have to depend on Samsung.
Wow, this is good news! I'm looking forward to having a stock Android. Although I want to try Sense more!
Im guessing once this becomes more stable, Sense is not far off?
wow, very good news.... when 3g-data will be fixed, surely i'll try this, even if i like touchwiz, i think that the sgs will be smoother without it....
hoping also in a AOSP FROYO ROM
report after ~17h use:
* gps doesn't work
* wlan works well and fast (i had 18-19mbit before with speedtest.net, same as my pc) but the driver seems to have some stability problems when it's idle for some time...
* short radio problem before, restart fixed it so radio probably is a little instable in the long run as well
quadrant scores of ~950 but linpack of only ~6.5MFLOPS? strange! everything is running very very fast and responsive (only fix aplied is: moved /data/data on /dbdata/data) and it boots faster. both definitely better than stock!
i am wondering why almost nobody seems to be interested in this. i had the feeling that more people wanted an aosp rom since we had a thread about that almost ever 2-3 days ...
I tried this asop for few hours: slower than best sgs rom's , no data connection, wifi slow, some app errors. Still not good enough for daily use but a very promising start.
Sounds really great, but I'm on JP3 right now and it seems to have less bugs than this :-/
This is only an alpha. I'll be more inclined to test when its in beta, as will many others I think. Especially as there are some troubles with core drivers.
Does this already run on a different file system (instead of RFS)? If not, will it be possible in the future to do so?
nrg said:
Does this already run on a different file system (instead of RFS)? If not, will it be possible in the future to do so?
Click to expand...
Click to collapse
no, it does not repartition anything.
yes, if you repartition the nand and have a kernel with e.g. yaffs2 support.
should both be possible atm with some effort...
i'm really interested,although Wiz notification bar is handy (but i could manage with standard power control widget)...i'm not able to program or do other too technical stuff,but i'd be happy to check for bugs (when it'll become a little more usable,i'm on h3g and i absolutely need 3g )
yeah, they are working on it and will soon release the source on github. i use it for almost 2 days now and except the missing data it's working fine for me. really fast and sleek. i guess that we will soon have a beta version with most of the stuff working....i think it's just amazing that this rom is only about half the size of the samsung firmware even with gapps!
although i like stock android more 2 things i already miss are the notification bar and the movie player which can play so many more formats than the stock one, but thats a small price to pay.
Can't the .apk's be ripped and installed anyway? I'm looking forward to try this when data is working!
Is this 2.1 or 2.2?
khsbenny said:
Can't the .apk's be ripped and installed anyway? I'm looking forward to try this when data is working!
Is this 2.1 or 2.2?
Click to expand...
Click to collapse
it's 2.1
hm. the apps could probably be ported but it would be more complicated than installing the apk. they rely on libraries, the custom ui stuff and probably other apps like content providers etc. the only thing i REALLY want is the movie player! it's just very comfortable to just copy some movies/series onto the device before a train ride without the need to transcode
jodue said:
i am wondering why almost nobody seems to be interested in this. i had the feeling that more people wanted an aosp rom since we had a thread about that almost ever 2-3 days ...
Click to expand...
Click to collapse
Interested, yea. As in "interesting to follow and see if it becomes functional." At the moment it's an alpha with no 3g data, wifi issues, bluetooth issues, no camera, and no GPS.
What more do you expect with it in its current state? Sheesh.
I really would like to go back to an AOSP Rom but I refuse until GPS is fixed since I rely heavily on it. We have a reason why AOSP speaker volume is so low but does anyone know WHY the GPS is still backwards. Its been months and and I'm just curious if any of the AOSP developers have given a reason why this hasn't been fixed yet. To me, it seems like this would be top priority but I guess not. Now I totally understand these developers do this stuff on their free time, I just want an explanation. Can't wait for the day I can go back to AOSP. For now, Gingerbangvanilla will have to do..
Joe_mustang said:
I really would like to go back to an AOSP Rom but I refuse until GPS is fixed since I rely heavily on it. We have a reason why AOSP speaker volume is so low but does anyone know WHY the GPS is still backwards. Its been months and and I'm just curious if any of the AOSP developers have given a reason why this hasn't been fixed yet. To me, it seems like this would be top priority but I guess not. Now I totally understand these developers do this stuff on their free time, I just want an explanation. Can't wait for the day I can go back to AOSP. For now, Gingerbangvanilla will have to do..
Click to expand...
Click to collapse
Maybe it's something they just can't fix so they are working on other issues :/ wish I knew, I'm a Sense guy myself.
Sorry for not being able to be more specific in the title, but my question is this: What exactly is the outcome of this kernel ****storm? With the CM team doing something which makes it hard for kernel developers to adapt?
Let's say one flashes CM9 and some custom kernel which has an app for controlling its settings, say GLaDOS, Trinity or Franco. Now, using these three kernels takes away the ability to modify kernel settings through the CM menus, but if one is using said kernel control app, then what difference does it make if the settings aren't available in the CM menus?
Also, I get it that no nug reports are accepted if one is using this mix, but since when did the CM team ever accept bug reports for nightly builds? I don't think I've ever had a single problem running a custom kernel with CM9 seeing as how I've always utilized some sort of kernel control app (and a few bucks for it isn't much of a hassle)
Can anyone shed some light on this? What are your experiences?
I would love to hear some answers on this as well. I kind-of have a love affair with franco.Kernel right now.
Its the same as carriers do it "If you dont use the software they gave you, you get no warranty". They don't know what you did with the phone, or what you flashed, or what could possibly be broken in the rom, so if you don't have the software the way they intended, they can't/won't help you.
Same applies with CM9, if you don't use the kernel they made/gave you, then they don't know if the issues you might have are because of a bug in the rom, or a bug in th kernel. Its hard work as it is to develop roms, tracking down bugs due to user choice/error is far harder and time consuming.
Basically, if you want to submit bug reports/make sure all the features of CM9 (any custom rom really), then use what you are given. No one forces you to use their rom, nor use a different kernel. With freedom of use, come other restrictions.
theking_13 said:
Its the same as carriers do it "If you dont use the software they gave you, you get no warranty". They don't know what you did with the phone, or what you flashed, or what could possibly be broken in the rom, so if you don't have the software the way they intended, they can't/won't help you.
Same applies with CM9, if you don't use the kernel they made/gave you, then they don't know if the issues you might have are because of a bug in the rom, or a bug in th kernel. Its hard work as it is to develop roms, tracking down bugs due to user choice/error is far harder and time consuming.
Basically, if you want to submit bug reports/make sure all the features of CM9 (any custom rom really), then use what you are given. No one forces you to use their rom, nor use a different kernel. With freedom of use, come other restrictions.
Click to expand...
Click to collapse
Thank you, but that doesn't really answer my question.
Sent from my Galaxy Nexus using Tapatalk 2
http://forum.xda-developers.com/showthread.php?p=26457711
Ezekeel brought it to everyone's attention with this thread.
title says it all
extremetempz said:
title says it all
Click to expand...
Click to collapse
Id be interested in cm10 as long as its possible to.port to cdma
Sent from my r800x using xda developers app
Im looking for any super stable AOSP Rom, CM10 Would be great, If it had no bugs and if it was smooth and if it had full working touchpads.
Super stable AOSP CM10 Would be Awesome, with no bugs was smooth and had full working touchpads
CyberScopes said:
Im looking for any super stable AOSP Rom, CM10 Would be great, If it had no bugs and if it was smooth and if it had full working touchpads.
Click to expand...
Click to collapse
Lotta if. I'd be interested in cm10 too. But with the same "if" like cyberscopes.
Regards,
Sdojoin
Yep, but would most likely not be possible
Yeah, but i think this's what this thread is for. To know & to ask us what we want. If not, then just close this thread.
Regards,
Sdojoin
Cm 10 forsure
Slimed, debloated, working touchpads, video, camera and panorama lol
Cdma/gsm.
Is that to much to ask lol
sdojoin said:
Yeah, but i think this's what this thread is for. To know & to ask us what we want. If not, then just close this thread.
Regards,
Sdojoin
Click to expand...
Click to collapse
This thread should actually be put into general... not into Q&A...
I've recently started building/using CM10 following these instructions: http://wiki.cyanogenmod.org/w/Build_for_zeus
(only instead of ics on the repo init line, I used jellybean)
I'm assuming that should be roughly equivalent to what the FXP team produces (considering they're the ones that submit the source to CM). It seems to work fine for me.
I don't honestly use my camera very much, but what is wrong with it? I seem to be able to take pictures and they seem to be the right resolution (though I haven't done any quality comparisons) I haven't actually tried video or panorama.
I'm mainly interested in trying to add some tweaks, some of which may be Xperia Play-specific, and CM seemed like the best developer/community open source ROM to work with (though if someone else has other suggestions let me know)
The touchpads actually work, though not in the way that games expect them to is the problem - so it's really more a matter of game compatibility than functionality (and some of the others have made great strides in this area, but still not compatible with all games). I'd honestly like to try to get the Xperia Play's gamepad to be exposed to applications the same way a Bluetooth HID controller would be - I honestly think that needs to be the future - games shouldn't be written for Xperia Play or MOGA or whatever special controllers people come up with, just write it for HID controllers.
I've also thought about custom unlock methods, one of which could be entering codes on your gamepad to unlock.
A more ambitious project unless I can actually get the Android Transporter's guys' attention would be hardware accelerated Wifi screen-mirroring, which is what the Android Transporter guys did to stream from phone to phone or phone to tablet or phone to raspberry pi (they've open-sourced their raspberry pi receiver and as I understand it have plans to open source the android platform mods to be able to screencast). Basically the idea is to pull composited images from the surfaceflinger and put them through the hardware encoder (similar to what the camera does for encoding video), and stream them over Wifi according to RFC standards.
What else is wrong with CM10 that ya'll would like to see fixed? Any new feature ideas?
I'm not promising to implement anything though, I haven't been able to devote much time to android development, but thought I'd go ahead and try to share and inspire ideas and hopefully I'll be able to find more time to contribute soon.
~Troop
Not really in any of those options if gaming is not as fast as in gingerbread.
Yes, I want something like yours ExtremeRom but with better performace. But I know that ICS is crap for gaming so it's just a dream
For those who tried them, which works better overall?
Do both have the Stagefright fix?
Does compass work on any of them?
Anything else that doesn't work on CM?
BTW, I have a GT-I9195
monitorer said:
For those who tried them, which works better overall?
Do both have the Stagefright fix?
Does compass work on any of them?
Anything else that doesn't work on CM?
BTW, I have a GT-I9195
Click to expand...
Click to collapse
Both work pretty much the same, though CM11 is probably that tiny bit more stable, bit faster, but more battery friendly. Lollipop has its bugs but "some" people don't seem to suffer the same bugs as others. It's still heavily in development but may work fine for you.
Compass was supposedly fixed in the latest build CM11 and also has latest stage fright fix. Think Lollipops compass works as I haven't seen any complaints, and as long as your using one of the latest builds should also have stage fright fixes.
Personally I'm a fan of CM11 but I use debloated stock as it has the original camera drivers. Just don't like the camera quality on custom builds. Though it's not terrible on either of them. Also some apps for me work better on stock.
In the mean time I installed 12.1.
Compass does not work.
The rest seems to work alright, but it's too early to say. I did have a couple of crashes, but not of the system itself. When I played music from two apps at once AudioFX crashed. And "Trebuchet" crashed once, don't remember how.
GPS might be taking a bit longer to get a fix than with stock, but I'm not sure.
Well, at least I hope to avoid the idle battery drain that I got on stock.
Overall the system seems fast enough, but the "fade to dark" effect after some idle time (and back to bright) is pretty choppy/slow. Not sure if that's intended or not.
Have you tried the kernel by SilviuMik for stock ROMS? Is meant to have battery fixes for standby. Though I have never suffered bad standby times, I do like this kernel.
Hi !
Yes...in reality ,objectively , there are only cm11(last release on 01/09/2015) and stocks who work fine .
At this time ,all Lollipop customs are not stable at all for daily use because umpredictables behaviors (maybe it work fine for some members but thes roms may have dysfunctions suddently with "majors big buggs)
With news big security problems ,all JB & KK customs roms are totaly "obsolete" (it's a pity because kk slim , pacman... work fine!) ,they are unusable because not secure...
-The best choice for a good daily use is a stock rom (or STE by ploiki ! Great buid !) with alexax's 0.9 kernel !!! Lighten by own debloating ...:good:
Good baterry life and good choice of parameters with "aduitor kernel"
And stock camera is good..
N5 foyr mini &S6 lollipop project seem good according to some members but i personnaly have had some problem...
-Second choice with cm11 but it's necessary to love customs and it need to replace some "poor" cm stock apps (camera...etc...)
I test the last release now but with recomended parameters , i generaly have found that the battery life is not as good as stock firmware kk&alexax kernel
I found cm11 more stable