Develop Bugs

[ROM] AOSP rom from vibrant forum (by eugene373 et al.)

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.

[IDEA][ROM]WFS compatible|sonyEricsion Xperia stock|Acer Stock|windows mobile 7

hello developers,
i had an idea and a request
why not you guys work on other custom roms to make them compatible for WFS????
its a good idea coz there are many cool Roms out there...
like Xperia,walkman series rom,acer got a cool rom too....even Dell got a cool looking GUI
people have different tastes....CM7.2 is a simply great rom....but people may not like the GUI
sense GUI is faar better than CM7.2
why not developers work on custom roms from other android phones?? ))
that will be great ^___^
plz dont consider my post as spam..i just suggested this thing....starting a poll ...if people will like my idea they'll support it..
i dont know if i'm the only one to love the custom rom's GUi o.o
+
There is another request...
in market(public market not android market)
windows mobile 7 is quite popular these days...
why not developers work on windows mobile 7 OS compatible for WFS
since unlocking boot loader = we can install all the OS
being an WFS developer and WFs user we should have many options
like i said everyone have different tastes...who knows who likes what?
users should have many options in there hand like what to install.....

you cant because of different hardware configurations and kernel. its like porting sense to samsung which cant be done. next time post in general section.

If you're just looking for GUI. download launchers like launcher 7, go launcher ex.. something like that.

blackpearlisuchiha said:
hello developers,
i had an idea and a request
why not you guys work on other custom roms to make them compatible for WFS????
its a good idea coz there are many cool Roms out there...
like Xperia,walkman series rom,acer got a cool rom too....even Dell got a cool looking GUI
people have different tastes....CM7.2 is a simply great rom....but people may not like the GUI
sense GUI is faar better than CM7.2
why not developers work on custom roms from other android phones?? ))
that will be great ^___^
plz dont consider my post as spam..i just suggested this thing....starting a poll ...if people will like my idea they'll support it..
i dont know if i'm the only one to love the custom rom's GUi o.o
+
There is another request...
in market(public market not android market)
windows mobile 7 is quite popular these days...
why not developers work on windows mobile 7 OS compatible for WFS
since unlocking boot loader = we can install all the OS
being an WFS developer and WFs user we should have many options
like i said everyone have different tastes...who knows who likes what?
users should have many options in there hand like what to install.....
Click to expand...
Click to collapse
if possible u go ahead and start work don't give these types of ideas

Mindhexer is right. Good dream though. Get you a HD2 if you want a windows &/or android phone; although, porting to android may knock out your volume toggle :/ honestly very very hard to port to a new os, but you'd have a slightly easier time of it going from open source to open source [ie hp touchpad; and that's not easy by any means]. Basically you will have to find in many cases drivers that work or have a decompiler [thousands of $] and a lot of programming knowledge [and free time]. Simply not feasible for our device; even though, I love to say anything is possible; I'd bite my tongue, hope you were Richie Rich, and point you toward some brilliant dev teams; Again though, you'd probably have another device that started windows [definately closed sources] and got ported over. I have yet to see one go the other way and it would probably open the door to legal issues to attempt :S So, in short, nope.
Sent from my HTC Marvelc using Tapatalk

insink71 said:
Mindhexer is right. Good dream though. Get you a HD2 if you want a windows &/or android phone; although, porting to android may knock out your volume toggle :/ honestly very very hard to port to a new os, but you'd have a slightly easier time of it going from open source to open source [ie hp touchpad; and that's not easy by any means]. Basically you will have to find in many cases drivers that work or have a decompiler [thousands of $] and a lot of programming knowledge [and free time]. Simply not feasible for our device; even though, I love to say anything is possible; I'd bite my tongue, hope you were Richie Rich, and point you toward some brilliant dev teams; Again though, you'd probably have another device that started windows [definately closed sources] and got ported over. I have yet to see one go the other way and it would probably open the door to legal issues to attempt :S So, in short, nope.
Sent from my HTC Marvelc using Tapatalk
Click to expand...
Click to collapse
hmmmmmm...i just thought it would be a good ides coz i saw a video on youtube.....his Xperia X8 was running Htc sense......
o.o

Xperia is overrated man. [IMHO]
Use your lovely phone while you can, like the other hundreds of us.

Its not possible to do any of those ports. End of story

I do wanted WP7 on my WFS but our phone doesnt clear few minimum specs..........we could use the WP7 port of the HD2 but because of the difference in the processor(and the shipped OS)....only an EXTREMELY TALENTED dev can accomplish this feat
BTW,we can try ubuntu can we???

djpc said:
Its not possible to do any of those ports. End of story
Click to expand...
Click to collapse
yes correct, end of story.
Possibility to use launchers themes looks like WP or Xperia.

If its just the looks, just use some launcher, there are many themes/skins... or make them yourself, its far easier than doing what u suggested, and it would be too much job for something that is not that big from my point of view.

m1ndh4x8r said:
you cant because of different hardware configurations and kernel. its like porting sense to samsung which cant be done. next time post in general section.
Click to expand...
Click to collapse
Pretty sure they ported Android 2.2 to the Samsung Omnia II (Windows 7 mobile)...

Maybe i'm going to make a CyanUX for the WFS ;-) (CyanogenMOD / Sony mix)

I will maybe make MIUI for WFS (based on CM7, fully themed, debloated and lots of MIUI apps).

Anything is possible, but porting one rom to a different phone is a never ending battle. Beside the the only real benefit would be a performance port, gui can be accomplish as mentioned in above post. If you really want to see this happen pick your favorite dev and put him or her on payroll, truthfully they should be getting paid for the work their doing now.

djpbx said:
Maybe i'm going to make a CyanUX for the WFS ;-) (CyanogenMOD / Sony mix)
Click to expand...
Click to collapse
please do...and must make it look cool .....atleast the GUI
and functionally better,...dint liked the look and way of working of CM as compared to sense...o_o

All the things you need
blackpearlisuchiha said:
please do...and must make it look cool .....atleast the GUI
and functionally better,...dint liked the look and way of working of CM as compared to sense...o_o
Click to expand...
Click to collapse
For Xperia Sony style, you dont need a whole new rom.
Two things, and cm7 will look totally different:
Xperia Launcher
Xperia Theme, install and choose it from the theme chooser app
Hope this helps, click thanks!

Henry_01 said:
I will maybe make MIUI for WFS (based on CM7, fully themed, debloated and lots of MIUI apps).
Click to expand...
Click to collapse
MIUI will take a lot of GUI resize work, I think. But can be done.
Best to wait for latest MIUI release with ICS after CM9 is ported by the WFSDEV guys.

No resizing needed for miui, I use cm7 and theme it and add miui apps which are ported and confirmed working.
For CM9, I'm part of the devteam, and it will take some time for a working cm9.
The "real" MIUI will never come to WFS, due to hardware (screen and cpu).
I have to say it isn't that great in all the aspects either.
There aren't many languages supported, you dont have the cyanogenmod settings and its sometimes slow and battery hungry.
The best I think is to combine the power of cm7 with the beauty of MIUI.

Henry_01 said:
No resizing needed for miui, I use cm7 and theme it and add miui apps which are ported and confirmed working.
For CM9, I'm part of the devteam, and it will take some time for a working cm9.
The "real" MIUI will never come to WFS, due to hardware (screen and cpu).
I have to say it isn't that great in all the aspects either.
There aren't many languages supported, you dont have the cyanogenmod settings and its sometimes slow and battery hungry.
The best I think is to combine the power of cm7 with the beauty of MIUI.
Click to expand...
Click to collapse
Yeah, guess you are right.
BUT, I CAN'T GET THE DAMN STATUSBAR TO BE TRANSPARENT. I've tried everything.

Attempting development for Gingerbread. (Long post/discussion)

Hello everyone...I'm planning on trying to develop a gingerbread kernel for AOSP because we don't really have support anymore and everyone has moved onto developing for ICS (not that this is a bad thing). I figure in my spare time I might as well try to learn and develop for our phone. Let me start by saying I was never really into phones/smartphones/rooting, or software development, but I've always been fascinated by Linux in general. I've played around using a number of Linux distros, but I've never really done anything intensive with them (modified their kernels, etc.) but I am vaguely familiar with terminal usage.
Anyways that was just my introduction. I've been running an ICS kernel on my AOSP GB system (specs/stuff in my signature) and while most advised against it, I find it to run pretty well. I'm not sure why it seems to run so well on my phone, but it's basically solved most of my problems (or at least it appears to have done that), but I know the kernel isn't "optimized" for my phone. Some major things people have said are that the ramdisking operations/system is totally different when comparing ICS and GB. This kernel that I'm using is running pretty well, even knowing this fact. What I was wondering is if I could basically get the ICS kernel, then "merge it" with a GB kernel's parameters that pertain to the ramdisk/other major options of GB. That would probably make it better. Also, people stated that multitouch issues for the DINC2 occured on Aeroevan's 0.8 kernel, but not on the 0.7 kernel. This was the changelog stated by aeroevan:
v0.8: Upstream CyanogenMod changes + small touchscreen driver update from HTC. Only tested on my CM7.2 Kang build.
Click to expand...
Click to collapse
So maybe this "small touchscreen driver update" is the thing that caused it, but I'm assuming many other kernels applied this update too? Maybe there is a way to roll back to whatever was in 0.7 in this sense to get rid of the multitouch bug that plagues some people.
I have a pretty powerful laptop, so development shouldn't be too bad. I plan on running Ubuntu 11.10 (or whatever people find suitable these days) in a Virtual Machine and I plan on compiling stuff from there. I am not claiming I know everything or that these things are correct....I am simply just throwing out some brainstorming to get some ideas out there. I know GB is "old", but I (and some others as well) enjoy it's stability and that it generally functions perfectly. Maybe this thread will get a look from popular devs, or maybe it'll get a look from people who just know this stuff. Thanks for reading, and sorry for the length of the post.

Looking forward to your progress on this.
Sent from my ADR6350 using xda premium

It would be nice to have another kernal for AOSP other than aero.

Your help in developing AOSP kernels would be fantastic.
Thanks given. Because I am hard of hearing I cannot use any of the kernels (even Evan's) and have to stick to Sense

[Q] What's everybody running on their cdma play?

Hey guys, just wondering what everyone is running on their verizon play? I am setting on fxp cm 9.1 but the lost features from stock are making me regret the change to ics (don't get me wrong the devs did a great job). I know we don't have much to choose from but I was wondering if I missed a gem somewhere. It's be awesome if you guys could give me some info,

Dudeness83 said:
Hey guys, just wondering what everyone is running on their verizon play? I am setting on fxp cm 9.1 but the lost features from stock are making me regret the change to ics (don't get me wrong the devs did a great job). I know we don't have much to choose from but I was wondering if I missed a gem somewhere. It's be awesome if you guys could give me some info,
Click to expand...
Click to collapse
I am using the UK 2.3.3 GB rom that was ported from the GSM xperia play. Everything works with touchpads what more do you want? Otherwise stock GB is the way to go. Oh yeah I tend to avoid fxp or cm based roms because they do not want to fix the touchpads. Even if there were a fix for the touchpads neither fxp or cm would add it to their builds.

COLA ROM
330MB of free space on internal memory.
290-250MB of free ram.

chery2k said:
I am using the UK 2.3.3 GB rom that was ported from the GSM xperia play. Everything works with touchpads what more do you want? Otherwise stock GB is the way to go. Oh yeah I tend to avoid fxp or cm based roms because they do not want to fix the touchpads. Even if there were a fix for the touchpads neither fxp or cm would add it to their builds.
Click to expand...
Click to collapse
Let me make this clear. FXP does the ENTIRE 2011 xperia line of phones, so sorry if a few build.prop lines get overlooked. 99% of "the touchpads" not working is due to the game itself and how it has them implemented and guess what..They use close source. So how can there be a "fix" when they can't see the source? Do not speak about which you know nothing about, as a developer who worked for cm a few years back, I find your comment insulting. It was cm that started custom roms in the first place.

agraceful said:
Let me make this clear. FXP does the ENTIRE 2011 xperia line of phones, so sorry if a few build.prop lines get overlooked. 99% of "the touchpads" not working is due to the game itself and how it has them implemented and guess what..They use close source. So how can there be a "fix" when they can't see the source? Do not speak about which you know nothing about, as a developer who worked for cm a few years back, I find your comment insulting. It was cm that started custom roms in the first place.
Click to expand...
Click to collapse
Hey now, I am sure it reads alot worse than he meant it, lets not start getting insulted by some internet goobieness. Like I said in my opening post, fxp did a great job with what the had to work with. The problem lies with Sony Ericsson we can all agree with that right?
I used to run the UK build but the draw of ICS made me leave it. Imma look into COLA this weekend!
Thanks guys and keep the responses coming.

If only all gsm rom can be tweaked to work on cdma then there won't be any problem about ics..
Too bad most dev don't even have R800x
Sent from my R800x using xda app-developers app

I'm running AOKP/milestone 6- supervenoms rom. Freshly installed last night. Trying to figure out what governors best for me.
Sent from my R800x using xda app-developers app

Just flashed FXP138 (was on CM9 stable, but FXP claims that touchpads are fixed)

agraceful said:
Let me make this clear. FXP does the ENTIRE 2011 xperia line of phones, so sorry if a few build.prop lines get overlooked. 99% of "the touchpads" not working is due to the game itself and how it has them implemented and guess what..They use close source. So how can there be a "fix" when they can't see the source? Do not speak about which you know nothing about, as a developer who worked for cm a few years back, I find your comment insulting. It was cm that started custom roms in the first place.
Click to expand...
Click to collapse
Sorry Agraceful I disregard my earlier comment and I didnt mean to spark a argument. Your right I dont know anything about developing roms or what not however having a half functional Xperia play is another thing leaving a sour taste in my mouth. As soon as i installed the latest FXP it had working touchpads however there is still the circle button issue but I am convinced were getting one step closer for a fully functional Xperia play. My faith is restored Cyanogenmod/FXP and I do apologize for my remark.

Bugs/Issus with CM Based ROMs

Hello Xperia Z1C people
I'd like to have a list of bugs/issues that appear on CM/AOSP based custom ROMs for this device.
I'm also searching for that on the forum, but it'd be really great if someone can sum it up. I have this great deal on a used Xperia Z1C, and I have to decide quickly!
Thanks in advance

Yeah CM for our Z1C seems to have small attention from developers and community.
I use it for some time now and could not find any bugs.
Currently (since build cm-11-20140521-NIGHTLY-amami) the hardware video decoding is broken. So you can not play any videos in youtube or webbrowser. If you use MX Player you can switch to software decoding which helps out for some videos.

This is what I saw in the last weeks
ANT is not working at all
Phone Encryption Breaks Gyroscope
It would be really great if these issues could be resolved.

Great! Thanks for the answer
So can I reasonably assume, that I can use a CM based ROM as a daily driver?
Please answer quickly, because I have to meet the guy in an hour

oshmoun said:
Great! Thanks for the answer
So can I reasonably assume, that I can use a CM based ROM as a daily driver?
Please answer quickly, because I have to meet the guy in an hour
Click to expand...
Click to collapse
I use the CM based RR ROM app. 2 or 3 weeks ago, without reboot, freeze or blue screen. In ART mode...

loud bug