i have sony xperia s , rooted , unlocked bootloader , running android v4.1.1 AOKP_nozomi_unofficial_KXP_Sep-16-12
iam having trouble with the camera , i can't find it in apps drawer and if i try to access it through lockscreen shortcut it opens the camera app and it says can't access camera , is there camera modules to flash or something like that , about 1 month ago i had sony ericsson xperia x10 i flashed unofficial aokp rom and there was camera modules and they worked !
please i need help , and i love this rom the best . i don't want to change the rom only for this thing
Sources are not yet available for certain components, camera included. There's been no camera for unofficial ROMs since dinosaurs roamed this planet. I should also note that on the first post of the first page of the Xperia S AOKP thread, it does state that camera is not working.
Of course, that's not to say that it won't be available in the future. The camera features were probably removed because of this, just to avoid setting people up for disappointment.
AwesomeTurtle said:
Sources are not yet available for certain components, camera included. There's been no camera for unofficial ROMs since dinosaurs roamed this planet. I should also note that on the first post of the first page of the Xperia S AOKP thread, it does state that camera is not working.
Of course, that's not to say that it won't be available in the future. The camera features were probably removed because of this, just to avoid setting people up for disappointment.
Click to expand...
Click to collapse
Just to fix something: If it was exactly like you said, the X10 Mini/Pro, X8 would never have camera on JB. They ( Sony) finished updates with 2.1.
"A scattered dream is like a far off memory
A far off memory is like a scattered dream"
AwesomeTurtle said:
Sources are not yet available for certain components, camera included. There's been no camera for unofficial ROMs since dinosaurs roamed this planet. I should also note that on the first post of the first page of the Xperia S AOKP thread, it does state that camera is not working.
Of course, that's not to say that it won't be available in the future. The camera features were probably removed because of this, just to avoid setting people up for disappointment.
Click to expand...
Click to collapse
sadly to now , but cm9 (free xperia team ) unofficial rom have the camera working
and do you know the official website for AOKP , so i can see if there is an official rom ? i can't find it through google
If there were an official ROM, it'd have been posted here first, of all places.
AwesomeTurtle said:
If there were an official ROM, it'd have been posted here first, of all places.
Click to expand...
Click to collapse
We have unofficial version, by Championwinner and other by K900.
"I got my values. So you can keep yours, OK?"
Related
Before I start, I need to pay my respects to the developers for all the great effort trying to make our ACES one hell of a phone.
Ok, if we were to sum it up as far as cyanogenmod development goes for the Samsung Galaxy Ace we have the following:
1. BehradGH Rom stable but some bugs or apps that don't work. A bit heavier than the following
2. Grif_07 Rom which appears to be the most stable
3. CM7.2 BY J.A.F which is developed by Russians who made a very good job and this one seems to be the fastest so far and very stable. This based on Grif_07 if I am not wrong. A thread started for this one, I believe this one has minor bugs cause I am testing it.
...And of course lots of others that diserve recognition
So if there's going to be an official version on which version is going to be based on and who's deciding for that? How's the whole thing going? Cause as far as I can see we get new roms probably from different working groups quite often but what's the point if they all choose their own path? I mean someone should decide the path so all the developers can work it out and reach the destination --> The Official version of Cyanogen for Ace. I would appreciate and I believe not only me but a whole lotta bunch of people if we were told what's the plan. Just a few words.
I see many great ideas in here, for example jusada took the first two roms and modified them to barebones. Really nice move and quite impressive roms, fast and quite stable but again not bug free (oh man, why you stopped dealing with this???).
Anyway, a few words from the right people would be great. I love cyanogen and I would go donate if we ever get an official rom. Thanks!
Belongs to the general subforum.
The 3 roms has problem with Facebook login on 3rd party programs Like IM+ , Meebo, etc, the only way for me to get facebook chat on a third party was making a meebo account and adding all my accounts into my meebo account and then loging in with my meebo account on the meebo app for android rofl. also CM7.2 BY J.A.F has problem after flashing gapps and everytime my device start it force close gmail and doesn´t connect to Google server to add my google account in the device.
itasoulas said:
Before I start, I need to pay my respects to the developers for all the great effort trying to make our ACES one hell of a phone.
Ok, if we were to sum it up as far as cyanogenmod development goes for the Samsung Galaxy Ace we have the following:
1. BehradGH Rom stable but some bugs or apps that don't work. A bit heavier than the following
2. Grif_07 Rom which appears to be the most stable
3. CM7.2 BY J.A.F which is developed by Russians who made a very good job and this one seems to be the fastest so far and very stable. This based on Grif_07 if I am not wrong. A thread started for this one, I believe this one has minor bugs cause I am testing it.
...And of course lots of others that diserve recognition
So if there's going to be an official version on which version is going to be based on and who's deciding for that? How's the whole thing going? Cause as far as I can see we get new roms probably from different working groups quite often but what's the point if they all choose their own path? I mean someone should decide the path so all the developers can work it out and reach the destination --> The Official version of Cyanogen for Ace. I would appreciate and I believe not only me but a whole lotta bunch of people if we were told what's the plan. Just a few words.
I see many great ideas in here, for example jusada took the first two roms and modified them to barebones. Really nice move and quite impressive roms, fast and quite stable but again not bug free (oh man, why you stopped dealing with this???).
Anyway, a few words from the right people would be great. I love cyanogen and I would go donate if we ever get an official rom. Thanks!
Click to expand...
Click to collapse
Yeah, I understand what you're saying. All the devs work on one beast godlike rom. That would be pretty epic.
itasoulas said:
So if there's going to be an official version on which version is going to be based on and who's deciding for that? How's the whole thing going? Cause as far as I can see we get new roms probably from different working groups quite often but what's the point if they all choose their own path? I mean someone should decide the path so all the developers can work it out and reach the destination --> The Official version of Cyanogen for Ace. I would appreciate and I believe not only me but a whole lotta bunch of people if we were told what's the plan. Just a few words.
Click to expand...
Click to collapse
The Official CyanogenMod for Ace would be developed by official CyanogenMod developers, AFAIK (CMIIW). It wouldn't be based on either because the CM developers would use their own source code (if I'm not mistaken, Behrad's CM7 port was taken from Galaxy Mini's CM7 port, and only recently has it been identified as device "cooper").
I agree that things might be better if all those wicked devs worked together to get one demigod ROM, but we like variety. For me, between one universal ROM and hundreds of specialty ROMs, I'd choose the latter.
kurama72 said:
The 3 roms has problem with Facebook login on 3rd party programs Like IM+ , Meebo, etc, the only way for me to get facebook chat on a third party was making a meebo account and adding all my accounts into my meebo account and then loging in with my meebo account on the meebo app for android rofl. also CM7.2 BY J.A.F has problem after flashing gapps and everytime my device start it force close gmail and doesn´t connect to Google server to add my google account in the device.
Click to expand...
Click to collapse
For the gapps problem in 7.2 i think you have to reflash the rom and this time not flash the ICS theme + animation. I believe that is what causes the apps to crash.
I think we should unite efforts on this cause. Couple of weeks back, I tried to move the crowd a little by making a campaign. Then we received a notice saying that CM7 was coming to our SGA.
ALL DEVELOPERS STOPPED WORKING ON ANY CM7 PORT.
I suggested to keep up working on the roms, since we don't have the certainty that the port is coming for real, which it seems (now) really farfetched. What I'm trying to say is that maybe if kept our noses to the ground and continue developing ONE HUGE MASSIVE CM7 port, then we may finally caught up some attention.
adeklipse said:
The Official CyanogenMod for Ace would be developed by official CyanogenMod developers, AFAIK (CMIIW). It wouldn't be based on either because the CM developers would use their own source code (if I'm not mistaken, Behrad's CM7 port was taken from Galaxy Mini's CM7 port, and only recently has it been identified as device "cooper").
I agree that things might be better if all those wicked devs worked together to get one demigod ROM, but we like variety. For me, between one universal ROM and hundreds of specialty ROMs, I'd choose the latter.
Click to expand...
Click to collapse
I see, so every rom in here won't have anything to do with the official version that is if we ever get one....why then the CM7.1 Cooper is stated as UNOFFICIAL? And if it gets OFFICIAL again it won't be the real official cyanogen, is that what you're saying?
itasoulas said:
why then the CM7.1 Cooper is stated as UNOFFICIAL?
Click to expand...
Click to collapse
I believe it's UNOFFICIAL because it's not developed by CyanogenMod developers (Team Douche or related).
itasoulas said:
And if it gets OFFICIAL again it won't be the real official cyanogen, is that what you're saying?
Click to expand...
Click to collapse
If I'm not mistaken, unofficial ports of CM are called KANGs. Behrad's CM7 port (according to that definition) is also a KANG build.
If CyanogenMod developers roll out official support for the galaxy ace (as "cooper"), then that CM7 build would be official.
*did I understand & answer your question correctly?
As always, CMIIW. I'm no expert, I'm no developer, I'm just an extremely happy user.
As many of you might have noticed, I've been pushing lots of MiniCM sources the last days. ICS is done and JB is on its way.
I'd like to take this opportunity and invite other developers or members that would like to contribute patches to do so. We already have some people contributing code for MiniCM and I would like to see more joining in. The code is available at: https://github.com/MiniCM
Why do this now?
This arch is reaching its limit as far as android development is concerned and there is too much ROM fragmentation for an old phone like this.
I know that most of the ROMs around are already using MiniCM binaries or sources and I'm ok with that. However, now is the time to consider contributing back and helping this project.
MiniCM is a fork of CM dedicated for these old phones. Notice that we are never gonna have official CM support, this is actually the cause that MiniCM serves
Licensing
I decided to keep my modifications Apache licensed. This is what gave android such a rapid development and I'd say has proven successful so far
I'd like to see this thread being used for Development ideas and solutions. NOT by user spamming (which will get you banned soon anyway since this thread is mod-monitored - you've been warned).
Reserving for build instructions
I can try to do option for disable/enable display button, but i'm not sure that i can do it
Lets keep this thread clean and on topic, as the OP has requested
We (the mods) will have a close eye on things, so lets not have any nonsense :good:
AChep said:
I can try to do option for disable/enable display button, but i'm not sure that i can do it
Click to expand...
Click to collapse
You mean the navigation bar right?
See this: http://review.cyanogenmod.com/#/c/20726/
nobodyAtall said:
You mean the navigation bar right?
See this: http://review.cyanogenmod.com/#/c/20726/
Click to expand...
Click to collapse
Oooppss, hour of my time wasted Cyanogen guys are fast
FAQ of course
and remember, for each version (miniCM7,9 and 10) there is a dedicated FAQ
that you can find here
I have a little idea. Many users of X8 and X10 Mini/Mini Pro uses stock kernel and can't unlock bootloader. I tried to make an addon to boot MiniCM7 based ROM's on stock, but still without success. With your help, nobodyAtall and other users, we can make such addon. I'm too unexperienced yet to do this by myself. What are your thoughts?
eagleeyetom said:
I have a little idea. Many users of X8 and X10 Mini/Mini Pro uses stock kernel and can't unlock bootloader. I tried to make an addon to boot MiniCM7 based ROM's on stock, but still without success. With your help, nobodyAtall and other users, we can make such addon. I'm too unexperienced yet to do this by myself. What are your thoughts?
Click to expand...
Click to collapse
Hi eagleeyetom,
Unfortunately stock kernel is VERY outdated to be usable in modern ROMs (e.g. gingerbread onwards).
In essence, one would have to replace the kgsl system to get the graphics to work decently with latest adreno blobs. Also I'm not sure if usb would be working since this too is outdated.
Other things to note: RAM (175MB if I remember correctly) is desperately low for modern Android versions, performance would also not be good enough for daily use. Kernel-side, I'm doing my best to boost performance as much as possible by backporting almost all of the main components that android uses from later versions.
All in all, for gingerbread it would be possible with serious performance sacrifices which I'm not willing to accept (even as a user). For ICS/JB, just forget it.
Perhaps a good project would be to make bootloader unlocking work for recent devices...
I understand your concerns and also think that stock is utter piece of crap, but it's still worth a shot. Such universal patch would improve development to our old shakiras. Your MiniCM is way better than official CM - really great job. Even with these bugs you've mention it's better than spent cash to unlock bootloader. I really admire the work of Alf and you - it's amazing to have such modern kernels to over-two-years-old devices.
Worse performance is a fact, but the ability to use almost every CM7 ROM on stock is tempting. This would be a great contribution to our small community.
P.S. I also think that you should have Elite Recognized Developer title. Such good work should be appreciated.
eagleeyetom said:
I understand your concerns and also think that stock is utter piece of crap, but it's still worth a shot. Such universal patch would improve development to our old shakiras. Your MiniCM is way better than official CM - really great job. Even with these bugs you've mention it's better than spent cash to unlock bootloader. I really admire the work of Alf and you - it's amazing to have such modern kernels to over-two-years-old devices.
Worse performance is a fact, but the ability to use almost every CM7 ROM on stock is tempting. This would be a great contribution to our small community.
P.S. I also think that you should have Elite Recognized Developer title. Such good work should be appreciated.
Click to expand...
Click to collapse
I see what you mean. Gingerbread compatibility is feasible BUT is gonna be pretty slow - in fact REALLY slow compared to MiniCM7.
We try to give a top quality ROM, so if this would ever happen it would be like a flashable zip and totally unsupported
I hope a lot pf devs will join the development. Cause everybody is working alone and if you all work together, it will bbe better for you and all ROM users. You'll develop quicker and easier.
Envoyé depuis mon Sekiz avec Tapatalk
nAa, is there a chance we can have CWM 6.XX on our GB kernels ?
RohinZaraki said:
nAa, is there a chance we can have CWM 6.XX on our GB kernels ?
Click to expand...
Click to collapse
I think it is possible, you can try it yourself, because you are able to change the recovery of the Kernel
actually it's possible. you just need to change the recovery file in the ramdisk with the one from JBMiniProject kernel or with one you compiled.
Why do not use the "Camera ICS+" in the market to replace the default camera app instead of taking a lot of time to fix the camera ???
LEDelete said:
Why do not use the "Camera ICS+" in the market to replace the default camera app instead of taking a lot of time to fix the camera ???
Click to expand...
Click to collapse
nAa roms are pure CM roms custom built for our device. If you see there is no third party apps. Not in GB and ICS and neither in JB.
RohinZaraki said:
nAa, is there a chance we can have CWM 6.XX on our GB kernels ?
Click to expand...
Click to collapse
I was trying something similar last night but with FroyoPro25.. Trying to get usb tethering working in it..
Can you all focus on GB please?
Working on ICS and JB is useless because they will never work smoothly on these old phones
shvelo said:
Can you all focus on GB please?
Working on ICS and JB is useless because they will never work smoothly on these old phones
Click to expand...
Click to collapse
And what has left on GB to be developed? How can we improve it?
Sent from my X8 using xda app-developers app
So, theres this camera here I want to flash but gallery fc's when ever I open Camera, thus making it un-usable, anybody have a solution or maybe a link to a better or similar flashable camera? Heres the thread http://forum.xda-developers.com/showthread.php?t=2133327 , what I'm mainly looking for is macro focus, but the more features the better!
CorkedA said:
So, theres this camera here I want to flash but gallery fc's when ever I open Camera, thus making it un-usable, anybody have a solution or maybe a link to a better or similar flashable camera? Heres the thread http://forum.xda-developers.com/showthread.php?t=2133327 , what I'm mainly looking for is macro focus, but the more features the better!
Click to expand...
Click to collapse
Last i checked and tested, any 4.2 Camera port is for AOSP ROMs only. I have not found one nor gotten it to work on anything other than AOSP ROMs. I may be wrong, just stating my experiences.
elesbb said:
Last i checked and tested, any 4.2 Camera port is for AOSP ROMs only. I have not found one nor gotten it to work on anything other than AOSP ROMs. I may be wrong, just stating my experiences.
Click to expand...
Click to collapse
D'oh. Well I like to stay on Stock-Based roms because I like full functionality of the dock, but thats not too important I guess, but I'm using a 4.2 camera on Hydro 7.0 right now, and its working fine, would this be cause its specifically made for the TF300T?
I currently Using Custom Roms for the past 6 months.... I make my phone (Xperia Mini Pro (SK17i)) as the tester for every ROMs. I also use it for personal. Well... Im not hating the Stock rom from sony, but sometimes im really desperate about those latest ROMs like Android 4.1 - 4.3 (and Even ANDROID 4.4 KITKAT). So, I try to make my phone's bootloader unlock, by using the official method. the DRMs are lost but it's ok, because i dont buy any musics online.
After I unlocked the Bootloader, I try the other roms... Im always want to see every post in every thread about those roms, until I saw this LegayXperia which is kinda cool.
So... here is my Very First Impressions about the CM10.1 and CM10.2 by LegacyXperia.... The System UI is much similar to the stock google ROMs, but this is the best roms that i can get, because of some reasons:
1. I like the Stock UI (not the sony UI from ICS).
2. I want the Rom that has good memory management, no more no less.
3. And lastly, It updates constantly such as builds and realeases.
There are the Few bugs, but The developers really tried their best as much as they could do, as long as the Roms got the best performance, I expreimented the tweaks and bandwidths and stuff. I try to fix the issues of my phone such as overheat, the top part of the screen isnt responding, and the battery draining issues. I applied the tweaks from different thread and it works flawlessly, no battery drain issues (governor tweak), no touchscreen issues (touch screen fix), and the bandwidth is much stable(change bandwidth). I cant remember those links, but you have to try check it out on the other threads or seach at google, it might be help.
NOTE: im not judging other roms. I just sharing my thoughts about these ROMs.
You should post this kinda of stuff in the dedicated ROMs thread in the android development section. And please read:
http://forum.xda-developers.com/showthread.php?t=1969555
In addition to the post above, thread closed.
Any word out for Cyanogenmod for Moto Z?
TWRP Team has showed amazing support already building recovery for it
The Hardware is awesome, would be cool if CM 13 or 14 comes to this phone
I hope but I don't think so.
CM does have very few SD810/20 devices. We have to hope for an unofficial port.
I hope so too, the phone is still new to the market, lets wait until developers get their hands on it
The problem with Z phones is the mods and how easy/hard it will be to support mods in other than stock based mods. But I sure hope that simple mods like the battery mod will work eventually. All depends on the additional needed software. Are the "Moto stuff" downloadable and useable on other roms than stock? Or do other roms need to build the very own support all from scratch?
İ finally built working cm14.1
But so many things are not working
Like
Wifi
Brightness
Simcards
Camera
Mods(are you kidding me!)
And also drains battery so flawlessly
But other things working like:
Bluetooth
Fingerprint
Touch
...
I'm working on it until someone upload official stock firmware 7.1 but this device need more developer and I'm alone on this project
If someone can help me contact me to build more stuffs together
just registered to say i've got most things working (ish) here:
the github url slash motoz-2016/android_device_motorola_griffin (not going to spam a bunch of posts just to submit a link, derp)
only things broken in 14.1 are:
- weird battery life issues (it lasts quite a while, but sometimes certain tasks seem to drain it way down)
- radio doesn't recover if it loses signal (curse you elevators)
- no mods support
- camera (this was working in 14.0 and died when i moved to 14.1)
- generally odd little things.
I havn't had much time recently to work on it (hope to change that soon) but it's been a daily driver of mine for a few weeks.
on the mods side of things, all the kernel support for them is already released on moto's github. it's just a matter of us actually using it (my kernel actually builds the kernel modules but that's not quite enough)
if any devs want to help contribute feel free to contact. (sent you a PM @erfanoabdi)
erfanoabdi said:
İ finally built working cm14.1
But so many things are not working
Like
Wifi
Brightness
Simcards
Camera
Mods(are you kidding me!)
And also drains battery so flawlessly
But other things working like:
Bluetooth
Fingerprint
Touch
...
I'm working on it until someone upload official stock firmware 7.1 but this device need more developer and I'm alone on this project
If someone can help me contact me to build more stuffs together
Click to expand...
Click to collapse
can't wait to see that out
sebirdman said:
just registered to say i've got most things working (ish) here:
the github url slash motoz-2016/android_device_motorola_griffin (not going to spam a bunch of posts just to submit a link, derp)
only things broken in 14.1 are:
- weird battery life issues (it lasts quite a while, but sometimes certain tasks seem to drain it way down)
- radio doesn't recover if it loses signal (curse you elevators)
- no mods support
- camera (this was working in 14.0 and died when i moved to 14.1)
- generally odd little things.
I havn't had much time recently to work on it (hope to change that soon) but it's been a daily driver of mine for a few weeks.
on the mods side of things, all the kernel support for them is already released on moto's github. it's just a matter of us actually using it (my kernel actually builds the kernel modules but that's not quite enough)
if any devs want to help contribute feel free to contact. (sent you a PM @erfanoabdi)
Click to expand...
Click to collapse
Just to simplify things: https://github.com/motoz-2016/android_device_motorola_griffin
Not much of a developper, however I can host files and probably set up an automated build on some servers.
sebirdman said:
just registered to say i've got most things working (ish) here:
the github url slash motoz-2016/android_device_motorola_griffin (not going to spam a bunch of posts just to submit a link, derp)
only things broken in 14.1 are:
- weird battery life issues (it lasts quite a while, but sometimes certain tasks seem to drain it way down)
- radio doesn't recover if it loses signal (curse you elevators)
- no mods support
- camera (this was working in 14.0 and died when i moved to 14.1)
- generally odd little things.
I havn't had much time recently to work on it (hope to change that soon) but it's been a daily driver of mine for a few weeks.
on the mods side of things, all the kernel support for them is already released on moto's github. it's just a matter of us actually using it (my kernel actually builds the kernel modules but that's not quite enough)
if any devs want to help contribute feel free to contact. (sent you a PM @erfanoabdi)
Click to expand...
Click to collapse
oh thanks for your post, i'm ready, let's do it together
thanks again for your device tree :fingers-crossed:
Soon.
Sent from my XT1650 using Tapatalk
Any update guys..
Manish54 said:
Any update guys..
Click to expand...
Click to collapse
i was working on naught droid OTA porting. but no success
so came back to CM project
as @sebirdman shared his device tree that was big step on project now i made todo list on google docs : https://docs.google.com/document/d/14-SJ6NVgDSHSiGkqpWVkXCc6N79BydhMnnYJaA-Htqo
if i make it little more useful i'll share flashable zip in this forum :fingers-crossed:
erfanoabdi said:
i was working on naught droid OTA porting. but no success
so came back to CM project
as @sebirdman shared his device tree that was big step on project now i made todo list on google docs : https://docs.google.com/document/d/14-SJ6NVgDSHSiGkqpWVkXCc6N79BydhMnnYJaA-Htqo
if i make it little more useful i'll share flashable zip in this forum :fingers-crossed:
Click to expand...
Click to collapse
CM sounds a lot better than the OTA :laugh:
Many many thanks sirs!!!
CM 14.1 please!!
CM is on the way
(uploading rom to mega ...)
check this out :
sadly I have the droid version I can't use this I wish sunshine team would work on the moto z but they said they are not Is there any bugs on the cm14.1?
Can't wait to try it
erfanoabdi said:
CM is on the way
(uploading rom to mega ...)
check this out :
Click to expand...
Click to collapse
I thought CM would never come to this phone.... :crying:
hassanman1997 said:
Can't wait to try it
Click to expand...
Click to collapse
now you can try it :
http://forum.xda-developers.com/moto-z/development/rom-cyanogenmod14-1-moto-z-t3514432