Hello
Will we see a Firefox OS port for the Desire Z?
+1 on this
Greets Vauvenal7
Sent from my myTouch 4G Slide
If you read up on Firefox os chances are that our phone isn't the best suited for it and being there are so few developers left here it is unlikely someone wants to pick up a project of this sort that will unlikely run well on the g2/dz
Sent from my Nexus 7 using xda premium
Firefox OS for Vision? Not so sure. It's not even commercial yet (I don't think, not in UK at least) so if we do see it on our device it won't be for a while. Unless you're willing to do it, of course, I'd definitely give it a go if that were the case. There are guides out there, and I'm certain the Vision is powerful enough to run it.
If you're anxious to try it, you can run it on your PC, either by emulating ARM or running the x86 OS.
If you're anxious to try it on your Desire Z, you're probably in for a long wait. You'll see it on Nexus before it comes to our device, and even that has yet to happen.
Patience, young padawan.
FYI, being a long time satisfied HTC Desire Z user and hacking on B2G for a while now (with Nexus S) I started working on running B2G on this device.
While it works not that bad, I limited myself to a quick hack thanks to the fosmaker tool. It needs a bit of help at Gecko and Gaia level :
- hwcomposer is not working, because it is an old version. This might result in some degraded graphic performances
- automatic brightness is gaia does not like the light sensor of this device, and sets the level too low when not facing light
- automatic network selection somehow is not enabled by default by the RIL, we need to force it on gecko side
- data call reply is incorrectly read by gecko, thus making him think the data call did not succeeded while it did
- physical keyboard events are correctly grabbed but do not make it to the destination, I have no ide why yet
- remapping the trackpad to the home button works, but you need to teach the keyboard input mapper layer of gecko/gonk about the Android keycodes for this (since the scancode it emulates is a mouse left click)
- placing calls/sms works, with the limitation that somehow main audio channel stays mute after a call is ended: no sound from keypad, videos, etc. But you can still call without any issue and it might be an issue I'm reproducing on other devices ...
- picture/video recording used to work last week, it got broke, but there's huge refactoring still happening on gfx layers, and gralloc is far from being correctly handled
- bluetooth works, I could pair with another Firefox OS phone (Nexus S) and exchange files
So to have something very perfect there is still some work to do, but nothing impossible if you want and have time. Anyone willing to hack and support this device is welcome to contribute !
This is more PoC patch than totally perfect (even if some part is waiting review to get into master), yet I added support (hackish) for forcing network automatic selection, support for the old ril so that SIM IO works and also data calls.
I don't have the time to ensure active support, but I can help someone who would like to.
Hello,
Those patches got a bit outdated, but current B2G master runs quite fine on Desire Z . Especially, thanks to Michael Wu's help, we have been able to test and acknowledge patches that makes the physical keyboard working, the bug being tracked at https://bugzilla.mozilla.org/show_bug.cgi?id=890186.
So if anyone is willing to jump in and help support B2G on this device, there is some nice and not too hard work to perform to enhance the support, please do not hesitate to ask me
FYI I've updated my branch with latest master and rebased some commits: BerTlvHelper just landed, and it processes FCP Template payload correctly, so I'm making use of it! So far I also fixed data call, the only thing I can't understand is why I have to force automatic mode by hand a couple of times to get RIL to register automatically on the correct network.
Some of the RIL related changes have finally been merged, thanks to a concurrent effort made by sku for supporting Fugu device. Having discussed with him, we are on good track to have the needed changes for Desire Z merged some day .
I still have a separate branch for: data call handling, home button hacking. Meanwhile, I'm stuck for building a complete image because of the lack of buildable sources for either 4.0.4 or 4.3 ROMs for this device. Hacking on prebuilt images has its limits when it comes to having nice and complete support ... If some of you can help me on this specific point any help is appreciated !
FTR, the master-HTC_Vision branch is available at https://github.com/lissyx/mozilla-central/tree/master-HTC_Vision
Just to summup since a couple of people asked me this by other channels: more or less most of the features are working. Major breakages are on Camera and Video decoding, which are broken.
My current setup to get B2G on this device is:
- follow the build steps that are documented on the Mozilla Wiki.
- configure (BRANCH=master) and build for an ICS-based device ; emulator should be fine, I'm re-using my Nexus S source tree.
- make sure to checkout my master-HTC_Vision branch for the gecko repository.
- flash an ICS ROM on the device, I'm using Andromads Audacity beta 5.
- extract boot.img, add a import init.b2g.rc line at the top, and add a init.b2g.rc file from the b2g gonk-misc repository, then flash back this new boot.img
- extract system.img, inject /system/bin/b2g.sh, /system/bin/rilproxy and /system/bin/fakeperm. Also inject /system/b2g/ and flash back this new system.img
- you can use the fosmaker (http://code.google.com/p/fosmaker/) project to perform those two steps: beware that fosmaker embeds an old version of b2g, so you'll have to search for its b2g/ subdirectory in the provided tarball and replace it with what you built.
On next reboot of the device, you should get B2G working.
Just a quick update to let you know that I rebased my master-HTC_Vision branch against uptodate master. Since there have been changes in the RIL worker, I hacked my code and finally fixed the automatic network selection by forcing automatic mode. So this is working not that bad, now
Another quick update with pics to show that I'm not bluffing . One pic of H264 playback on the device from within Browser app, and another of geolocation in HERE Maps.
View attachment 2548430
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I'm still pushing to this master-HTC_Vision branch.
FYI, I get camera working if I build Gecko re-using my Keon's source tree
Hello,
I'm still hacking this, even though I have a hard time with the Camera: on Gecko master built from Keon's tree, it partly works. When camera preview runs, if you take a picture, you get a photo taken but it's all scrambled. This does not reproduces with the same exact code except if you turn off the preview in the Camera app (by hacking it). So you can takes pictures, but blindly.
Apart from this, I've pushed rebased code to the master-HTC_Vision on top of current master, and took some time to fix network. I now get my MVNO SIM card with a PIN code detected, I can unlock it, it correctly automatically select network, and I can place calls, send/receive SMS, place data calls (HSDPA).
No big news, I'm still pushing regular updates for the gecko branch for this device, still the same issues
Hello!
Is there any news about this project? Does it build and run?
Thanks!
asp2010 said:
Hello!
Is there any news about this project? Does it build and run?
Thanks!
Click to expand...
Click to collapse
Well I'm still pushing Gecko to the branch and building it, so yes, it does work, but it's not off the shelf .
FYI I've been recently relying on Desire Z for hacking and testing a LED API in Gecko.
Hi !
I've tried to follow your intruction, and the one on mozilla's website, but I get stuck on the HTC*logo.
Are you planning on adding a new configuration tree for the Desire Z ? So, it would be easier to build a version.
Thanks
Lippen said:
Hi !
I've tried to follow your intruction, and the one on mozilla's website, but I get stuck on the HTC*logo.
Are you planning on adding a new configuration tree for the Desire Z ? So, it would be easier to build a version.
Thanks
Click to expand...
Click to collapse
No. Thanks for trying though, but I don't have a configuration tree even to build, it's a total hack and I cannot afford spending much time than this kind of hacking. If you are willing to, I can help you though
Related
All,
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First of all; apologies this has taken so long to release into the public domain. I wanted to get it right first prior to full release.
SuperHero started out as a very experimental ROM - the feedback from which has surprised me. I expected a few Vanilla fans to download it and like it, but a lot of people are using the ROM as a definite alternative to a Sense UI ROM. I'm really pleased about the feedback it's received.
DESCRIPTION
Essentially, it's a HIGHLY stripped down VillainROM, and is geared solely for absolute, 100% performance. It's quick, folks.
It's about 80% Vanilla, but there are some Sense apps & HTC frameworks in the build for now. This may change at a later date.
SO, THE ROM:
- The excellent ADW Launcher (Recommended settings are: [drawersettings] New Drawer - NO, Animated Drawer - NO, Fast Drawer - YES)
(Use SpareParts to further improve the visuals)
- OTA Updater software installed
- All streaming issues fixed
- Press Home on Home Screen for Sense style quick select view
- Completely customisable home screen
- SIM Contacts can be disabled (and groups are fixed)
- Incredible Live Wallpaper performance - They don't stick for long though. Nice to show off with, that's about it.
- Boot CONTROL Widget
- Vanilla Camera @ 5mp (green tint exists, although, we're working on this)
- Vanilla Keyboard
- Vanilla eMail (Multiple Exchange accounts) (includes corcal and corgal)
- Vanilla Music
- Vanilla & Sense Diallers (option)
- Apps2SD
- Friendstream App working - Widget obviously not as it's SENSE.
- Significantly improved performance over Villain (due to JIT + Removed SENSE limitations)
- Working Vanilla Alarm & Lockscreen
- Gallery 3D MULTITOUCH with rotate fix
- VERY Stable
- All Hardware working
- Perfect OpenGL performance for the build
REMOVE SIM PIN UNLOCK CODE BEFORE FLASHING (as it causes boot problems)
DOWNLOAD LINKS!
Thanks
http://forum.xda-developers.com/showpost.php?p=6541857&postcount=11
awesome. I like, love you man
Server Busy?
getting Timeouts...
Seems like there are lots of people downloading...
alternative link please !!!!!!!!!
The VillainROM site is currently down. They posted on tweeter they are doing their best to fix it and keep us posted.
But i agree, an alternative download link could be great, since i'll probably won't have the time to flash my phone this weekend.
( I don't know why, but female friends really don't understand why it's so much fun to flash a new ROM when your phone is already working fine. )
Tweedeldee said:
( I don't know why, but female friends really don't understand why it's so much fun to flash a new ROM when your phone is already working fine. )
Click to expand...
Click to collapse
Common problem man, lol
Tweedeldee said:
The VillainROM site is currently down. They posted on tweeter they are doing their best to fix it and keep us posted.
But i agree, an alternative download link could be great, since i'll probably won't have the time to flash my phone this weekend.
( I don't know why, but female friends really don't understand why it's so much fun to flash a new ROM when your phone is already working fine. )
Click to expand...
Click to collapse
Unfortunately, I can't do an alternative link
I don't have a copy of the file to even upload to the mirrors folks. Sorry. I will ask around though
Also, most of my FTP passwords are saved on that server, although I have some here on my PC.
Do the bluetooth work?
Alternative link plz
anon2122 said:
Unfortunately, I can't do an alternative link
I don't have a copy of the file to even upload to the mirrors folks. Sorry. I will ask around though
Also, most of my FTP passwords are saved on that server, although I have some here on my PC.
Click to expand...
Click to collapse
No worry, there is nothing to be done when the whole site is down. (except giving angry phone calls )
BTW, the nice clock-meteo and battery-space widgets we can see on the screens are already included in the ROM ?
If they are external applications, could you give us their names ? Finding something in the Market is already a nightmare
(I might be able to flash the ROM this weekend anyway: since the team is doing a great work, VillainROM are working out-of-the-box without issue, I take 1 hour max to flash / configure it... that's around the time she needs to take a shower. )
Tweedeldee said:
No worry, there is nothing to be done when the whole site is down. (except giving angry phone calls )
BTW, the nice clock-meteo and battery-space widgets we can see on the screens are already included in the ROM ?
If they are external applications, could you give us their names ? Finding something in the Market is already a nightmare
(I might be able to flash the ROM this weekend anyway: since the team is doing a great work, VillainROM are working out-of-the-box without issue, I take 1 hour max to flash / configure it... that's around the time she needs to take a shower. )
Click to expand...
Click to collapse
OK. We are in contact with the host. He got woken by the server alarms. So rebooting now...
hi folks, if it is ok for nathan I am uploading the Rom I downloaded 12 hours ago.
Just give me 30 minutes for uploading.
MIRROR - http://www.multiupload.com/DUB447BZR0
MD5 Checksum - 84e51671632f59bc756bb9a101ff40fa
i posted at the other thread too:
even if i deactived sim lock (so that i hadnt to type in the pin with legendroid) on first boot it says invalid sim card.
any idea?
xmaskx said:
i posted at the other thread too:
even if i deactived sim lock (so that i hadnt to type in the pin with legendroid) on first boot it says invalid sim card.
any idea?
Click to expand...
Click to collapse
I experience the same problem.
It says invalid SIM and get stuck by preparing SD Card.
Just a questions: SMS and Contact apps are still HTC ones, or you switched to vanillas?
ermacwins said:
Thanks
http://forum.xda-developers.com/showpost.php?p=6541857&postcount=11
Click to expand...
Click to collapse
There is also Vanillain (3.0 is Darchstar's CyanogenMod 5.0.7 popular CDMA rom ported to our GSM heroes).
That's a pure non-sense rom. But I doubt the wii-remote apps can't work with Sense bits in the rom though, they don't do (that much) to the bluetooth framework.
This ROM is multilanguange?
Original links up again
This is old. See this topic
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Banner thanks to SebianotiI've just noticed that this has made the XDA portal. It's been up on quite a few websites today that I've noticed, and I just wanted to say a big thank you to all the writers who have helped spread the word. If you are one of them, you're awesome!
This is a port of Jellybean, based off of the roms for the two nexus devices that were released yesterday. I'm working to add in all of the key features at the moment, and it's going pretty well, so you can probably expect to see some kind of Alpha release fairly soon.
It's based off the porting work done for CM9 for our phone in the topic here, with some help from randomblame in the #cyanogenmod-dev channel. (Thanks!)
Working
Core system with little to no crashes
Not working
Wifi
Radio
Audio
Camera
Ironically, the issue we've been trying to resolve with CM9 for this phone, the rotation bug, appears to be fixed here. Not sure whether to laugh or cry
Images
http://i.imgur.com/CgWMF.png
http://i.imgur.com/DLd2U.png
http://i.imgur.com/eQRbc.png
http://i.imgur.com/htOEO.png
http://i.imgur.com/ewQrl.png
http://i.imgur.com/y4R30.png
Video (Thanks to Vere850211)
http://www.youtube.com/watch?v=whavUiVkYq8
DOWNLOAD
Remember to flash the boot.img in the zip.
Progress log
Now based off of the Nexus 7 tegra rom. Things are running a lot smoother and with little to no crashes
Wifi firmware loaded, just need to get it talking with netd and we'll have wifi
I have been able to manually configure wpa_supplicant and it successfully scans for networks. The problem now is that the rest of Android seems to be having trouble communicating with wpa_supplicant.
To those PMing me asking about porting info: Don't expect there to be a simple cut and paste way to port. If you have no experience with porting or don't at least have an understanding of how android is structured, then I would advise you to read up before attempting this. I can provide targeted help if you have a specific issue, but I won't port it for you, and please don't be offended if I suggest you go do some reading.
If you still think you can do this, then here's a checklist of the major things you should look at to get it booting:
boot.img - Grab mine or any other jellybean boot.img, and pull the entire init.rc and init.traces.rc, and package it up with a cm9 boot.img
/system/lib/modules + /system/lib/hw - Modules must be brought across from a cm9 rom, and unless your device runs the same chipset as the base you're using (tegra for the n7, omap for the gn), you'll probably need to put all of the hw libs into there too
/system/etc/firmware + /system/vendor - You'll most probably need to pull both of these dirs into the rom
/system/lib/egl - You'll want all of the egl libs and egl.conf
Various /system/etc files - There's usually some configs, firmware, and other stuff in here
/system/lib - There's tons of files in here, a lot of which you'll need to bring over, and a lot of which you'll need to leave alone. Best advice I can give you is to find an open source cm9 tree for your device and check the proprietary-files.txt file
That's it. By now you should at least have it showing the boot animation. Now it's up to you and your debugging tools. strace is invaluable if you have a specific binary that doesn't want to load, it'll show you all of the system calls it makes and the errno if one gets set. Read through the logcat carefully and it'll probably tell you if you're missing any libraries or other files. Good luck.
Nice work so far! Can the 4.1 apps be ported back to 4.0.4?
This way we can use the new apps like the launcher and what not without using 4.1?
Holy S..t! That was fast .... Awesome work mate
can you take a screenshot on the multi-language keyboard please?
they said they have changed the way to switch between languages
thanks
i ported galaxy nexus dump
only bt, hw accel, sensors works for now.
need nexus7 system dump for fix others crap
thanks
wow that was fast! great work!
Woah, fast work there buddy, btw there is a proper stable Jellybean for Galaxy Nexus released now, would that help?
Sebianoti said:
Woah, fast work there buddy, btw there is a proper stable Jellybean for Galaxy Nexus released now, would that help?
Click to expand...
Click to collapse
It would, see mdeejay's post above, but like I said in the first post my interest basically stops here, I'm not really looking to maintain this rom.
tgascoigne said:
It would, see mdeejay's post above, but like I said in the first post my interest basically stops here, I'm not really looking to maintain this rom.
Click to expand...
Click to collapse
Understandable, no point continuing tbh until source is out
Sebianoti said:
Understandable, no point continuing tbh until source is out
Click to expand...
Click to collapse
Exactly, when the source is out we can have fully working builds rather than ugly cooked up things, and I'm willing to live with ICS until then.
I don't get it... there is no Blackscreen while roating bug...
Overall nice to see!
I also worked on that the whole night got it nearly bootet up, my ramdisk was fine, the bins of my sdk may where broken...
the|gamer said:
I don't get it... there is no Blackscreen while roating bug...
Overall nice to see!
I also worked on that the whole night got it nearly bootet up, my ramdisk was fine, the bins of my sdk may where broken...
Click to expand...
Click to collapse
Haha, you're right, there is no rotating bug! As I said, I probably couldn't have done it without help from the other SDK port that was done for another phone, if I'd known you were working on it too we could have worked together and had it done faster.
System dump here apparently
http://www.androidpolice.com/2012/0...ystem-dump-is-out-modders-start-your-engines/
Is that what you guys need or am I reading wrong?
Sent from my HTC One X using Tapatalk 2
The only System dump that is really helpful is the one for the Nexus 7 cause that is an Tegra 3 driven Device!
What we really want is the AOSP Sourcecode so we can build up a nice and clean build!
Ahh fair enough mate
Sent from my HTC One X using Tapatalk 2
the|gamer said:
The only System dump that is really helpful is the one for the Nexus 7 cause that is an Tegra 3 driven Device!
What we really want is the AOSP Sourcecode so we can build up a nice and clean build!
Click to expand...
Click to collapse
The 3.0 tegra kernel for the Nexus 7 is already in the AOSP repos as part of their legal obligation. The kernel is GPL licensed and the device was released today.
tgascoigne said:
The 3.0 tegra kernel for the Nexus 7 is already in the AOSP repos as part of their legal obligation. The kernel is GPL licensed and the device was released today.
Click to expand...
Click to collapse
So nvidia have released the source code for Tegra 3?
Cause i was reading a few weeks ago they had no intentions to do so, because it might release some code that's currently used as leverage against the competition.
Atrixx said:
So nvidia have released the source code for Tegra 3?
Cause i was reading a few weeks ago they had no intentions to do so, because it might release some code that's currently used as leverage against the competition.
Click to expand...
Click to collapse
Check out the kernel/tegra repo on aosp, theres a 3.1 (I believe) kernel source in there. Not sure on nvidia's stance.
Hmm... well there are some https://android.googlesource.com/kernel/tegra.git but they are from 15th of June...
I am checking them out and will look for a "nasaki" config file
good job .. great work! :cyclops:
Android 4.3 Jellybean for Motorola Bravo
Quarx Builds: http://quarx2k.ru/
Gapps: http://goo.im/gapps/
Minimal Gapps (Gmail,Market,Gtalk,Synchronisation): http://quarx2k.ru/gapps-jb-20120726-minimal.zip
Status:
30.07.13: First Build. Works almost all.
01.08.13: Fix "Unknown" bug. Fix 1% battery. Dialer included, VideoEditor removed.. Backup gapps disabled(to prevent reboots during install rom).
17.09.13: Focal Restored, Ability to OC GPU(without gui yet), added patch for Data, DefyParts, 720p rec(bugged), Support HWUI app, Minimum brightness 2, Wide poho added.
20.10.13: 720p rec, Fix HWUI app, use thoemy wpa_supplicant, Call Recording, LTO support, many fixes and improvements in kernel, gpu 266mhz by default, Fix arrows that indicate upload/download activitiy at Wifi and mobile connections.
30.10.13: Fixes in kernel, Added two new options for ril "emptycallchanges" and"skipdatareg" (disabled by default), journal on ext enabled by default, fix reboots in recovery(not tested), updated twrp.
Thanks a lot Quarx.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks, this is great to see!
Hopefully quarx or another crafty Defy dev pulls a rabbit out of a hat soon with a moto audio library.
Awesome. :highfive: Did you build from Quarx's Defy sources and added in the Defy Common changes? Just curious, I've thought about doing that but I'm busy with Salad Bar and soon Paranoid.
Oh, and long time no see -- good to see you're still around
Thanks a lot aleeyt! Are you going to be taking over the JB Bravo port from Quarx for good?
skeevy420 said:
Awesome. :highfive: Did you build from Quarx's Defy sources and added in the Defy Common changes? Just curious, I've thought about doing that but I'm busy with Salad Bar and soon Paranoid.
Oh, and long time no see -- good to see you're still around
Click to expand...
Click to collapse
This is a separate version for Bravo. While there are no changes in the repositories, but I think soon they update. The Quarx now little time, so I will be engaged in development under Bravo, of course not without his help so far, but all the same separately. I think the ports for Bravo will no longer be the personal own builds.
Sound now works
All thanks for help to maniac103 and Quarx.
aleeyt said:
This is a separate version for Bravo. While there are no changes in the repositories, but I think soon they update. The Quarx now little time, so I will be engaged in development under Bravo, of course not without his help so far, but all the same separately. I think the ports for Bravo will no longer be the personal own builds.
Click to expand...
Click to collapse
I've been doing the same with ICS and haven't had any problems. So far, my biggest issue is having to revert the camera libs after pulls and merges with Epsylon's repo.
Thank god our platforms are so similar, for the most part, all I've had to do was change Jordan to Kobe and mb525 to mb520; well there's a bit more than that, but you've messed with the source so ya know what I mean.
You're quick! I'll flash 7/18 and give some feedback over the next couple hours
wow quarx server is overloaded giving internal service error
and downloading from aleeyt's server, i'm sitting pretty at 1 hour till flash
inverted gapps for jellybean: http://forum.xda-developers.com/showpost.php?p=28947948&postcount=1
Flashing over CM9 got me stuck at the (new) boot animation.
Also, when I go into recovery there's a new error at the bottom: Error: cp not found!
sdrawkcab3 said:
Flashing over CM9 got me stuck at the (new) boot animation.
Also, when I go into recovery there's a new error at the bottom: Error: cp not found!
Click to expand...
Click to collapse
I didn't have that problem. I never wipe data, but do wipe cache+dalvik both before and after flashing any new rom...but you probably already wiped.
Quarx is currently fixing mp3 issues and apps2sd.
quick changelog:
camera, video, pano, chrome work (side note: can't make swipe to delete picture work, but the camera to gallery feature works great)
FC accesing settings->system
it's pretty fast, I would say maybe the same or a tad bit faster than the last ICS build
new 'safe headset volume' option in sound settings, oh and sound works
developer options has to be turned on (switch on top right corner of screen) in settings
CM performance options, and defy parts now included
no CM power widgets yet obviously or custom statusbar options
no CRT screen-off animation, even though option available in display settings
no boosted, smartass governors or sio scheduler obviously
weather, calendar on lockscreen work
google now works (with voice!) but kind of laggy
new HWA settings app so you can choose apps to blacklist
@Aleeyt
Do you have a github repo? I checked your old one and it didn't have a trace of JB on it. Only asking cause I can't get the compile to start when using Quarx's repos as a base, nothing changed; the Defy(+) compiles just fine.
I'd post my terminal output, but I closed that window a few hours ago and didn't plan on asking for help in the matter. It tells me that it can't find cm.mk at device/*/kobe and that file is clearly there...Perhaps I'll go over Quarx's commit history and find what he changed and add that in to my local JB repo (haven't pushed anything to github yet and won't until I get somewhere either).
skeevy420 said:
@Aleeyt
Do you have a github repo? I checked your old one and it didn't have a trace of JB on it. Only asking cause I can't get the compile to start when using Quarx's repos as a base, nothing changed; the Defy(+) compiles just fine.
I'd post my terminal output, but I closed that window a few hours ago and didn't plan on asking for help in the matter. It tells me that it can't find cm.mk at device/*/kobe and that file is clearly there...Perhaps I'll go over Quarx's commit history and find what he changed and add that in to my local JB repo (haven't pushed anything to github yet and won't until I get somewhere either).
Click to expand...
Click to collapse
I do everything locally. I have not updated the repo, as yet not understood how to do it) Once the sorting out, update the necessary.
aleeyt said:
I do everything locally. I have not updated the repo, as yet not understood how to do it) Once the sorting out, update the necessary.
Click to expand...
Click to collapse
I hear that....I'm still trying to get all that figured out. My hardest part is remembering to initialize my local repo before doing changes.
New build available.
a lot of people, including myself, have been giving credit to Quarx and the other defy devs for the breakneck speed of development for the defy and our device...and rightly so.
but aleeyt, you really have been the one that got everything started for the bravo in the first place, by taking the initiative to get our device to Quarx. Otherwise, we would've probably been stuck with miui and cm7 defy ports like before.
Thanks a lot man.
July 19 changelog:
no more FC on Settings--> system, however none of the options really work (i.e. battery percentage, power widgets on notification bar, etc.)
mp3 codec, youtube and endomondo issues, apps2sd fixed
notification LED and sound present, no charging LED yet
the build is definitely worthy of being a daily driver
if you're using the inverted gapps link I posted earlier, the inverted google now is pretty glitchy, here's the same zip with the non-inverted velvet that works fine: http://www.sendspace.com/file/qf6f5e
Thanks for keeping Bravo right up there with the bleeding edge, aleeyt We're enjoying these daily ports!
So is crt working and hwa? I want to experience the smoothness, lol
Having trouble with email exchange force closing. Other than that...we have 4.1.1 on our phones.
Sent from my MB520 using xda premium
BravoMotorola said:
So is crt working and hwa? I want to experience the smoothness, lol
Click to expand...
Click to collapse
CRT still does not work, but hwa does.
I also get the exchange FC. I wonder if it's system app related. There's two different exchange apk's in the directory.
Sent from my MB520
DO NOT post in this thread until you have read the first three posts and last two pages of this thread in their entirety!
"Me Too" posts for known issues with no useful debugging information WILL BE REPORTED.
This is the thread for Omni nightlies for the Oppo Find 7a and 7s
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://dl.omnirom.org/find7/
Also, the nightlies support LVM for partition remapping, which allows the two internal data partitions (/sdcard and /data) to be merged into one that uses emulated storage for /sdcard (Android's standard method for ICS and later). Details can be found at http://forum.xda-developers.com/showpost.php?p=55081626&postcount=546 . LVM is significantly safer than other partition remapping solutions as it does not actually alter the underlying partition table. As a result, switching layouts is MUCH faster than methods which remap the partition table, and switching layouts is more reliable and doesn't fail in strange and difficult-to-repair ways (such as the frequent failures of another solution that can be seen in the ColorOS 2.0.2i beta thread). There's a good chance Oppo will be switching over to this method with a future ColorOS release, especially after their experiences with 2.0.2
For historical reference, I will leave the pre-nightly test builds in the Downloads section of this thread. However, these are now obsolete.
Gapps:
http://forum.xda-developers.com/showthread.php?t=2397942
(this isn't a nexus, use the modular releases, not full)
Omni only supports TWRP recovery, use any alternate recovery at your own risk. Official TWRP for this device is:
http://forum.xda-developers.com/showthread.php?t=2717916
Anyone flashing this should know the usual installation drill... Flash in recovery, flash gapps, wipe data/factory reset. If you don't know how to do these things, this package is not yet ready for users like you.
Thanks go to the following people for their help during bringup:
Jake Whatley and Kristof Petho (Omni)
Max Weninger for polishing the device up and getting it up to nightly readiness after I kind of burned out
Andre Saddler and Hieu Nguyen of the Paranoid Android team
XDA:DevDB Information
Omni for Find 7a/7s, ROM for the Oppo Find 7
Contributors
Entropy512, maxwen, xplodwild, jerdog, jakew02
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Nightly
Created 2014-05-21
Last Updated 2014-09-02
Reserved
Kernel source:
https://github.com/omnirom/android_kernel_oppo_msm8974/ plus the following Gerrit items:
https://gerrit.omnirom.org/#/c/7373/
https://gerrit.omnirom.org/#/c/7374/
https://gerrit.omnirom.org/#/c/7423/
https://gerrit.omnirom.org/#/c/7651/
https://gerrit.omnirom.org/#/c/7649/
https://gerrit.omnirom.org/#/c/7650/
https://gerrit.omnirom.org/#/c/7648/
Device tree:
https://github.com/omnirom/android_device_oppo_find7a/ plus:
https://gerrit.omnirom.org/#/c/7336/
https://gerrit.omnirom.org/#/c/7645/
https://gerrit.omnirom.org/#/c/7434/
Other Gerrit items:
https://gerrit.omnirom.org/#/c/7652/
https://gerrit.omnirom.org/#/c/7460/
https://gerrit.omnirom.org/#/c/7465/
https://gerrit.omnirom.org/#/c/7103/
Also there are misc patches to increase debug logging in a number of places (the basic setting NDEBUG to 0)
Blobs: donkeycoyote
Reserved
Current status as of 05/20/2014:
GPS works
Wifi works
Cellular radio works (data and voice calls)
Basic camera/camcorder functions work
Bluetooth works (tested with Google Glass and an OBDKey)
Sensors work (except for Google Camera Photosphere - see below)
Audio is flaky - Mic does not work in speakerphone calls (earpiece only) and headsets with microphones cause the audio HAL to barf. There are probably a number of other use cases where audio doesn't work well. Confirmed working are Google Play Music, Google Maps, earpiece calls, Bluetooth calls via Google Glass (Mic in speakerphone/headphones may be fixed in the 5/30 build - won't test until tomorrow.)
Not yet implemented (need to get the basics done first, these shouldn't be too hard since maxwen did them all on N1)
Screen-off gestures for music
"Hey, Snapdragon" voice wakeup - gotta talk to xplodwild about this
Superzoom mode (I'm about halfway there, it's in the 5/30 build but crashes when you take a shot, so effectively isn't really there...)
Known issues:
Rare spontaneous reboots due to the WCNSS firmware crashing (1-2 times/week for me)
Magnetometer (compass) gets "Stuck" if you use Google Camera
LPM (charging when device is off) is broken - device may charge but screen gets stuck on at the Oppo logo. (may sometimes happen when rebooting on charger)
Woot!
Here we go!
Sent from my OnePlus 7a
Finally a good vanilla build
My camera lenses produce a clicking noise everytime a camera app is closed. It didn't happen with color OS before. ¿is there any issue with it?
If you want to have a OP more attractive, i know content is attractive but picture too, here it is a simply prez from me...
You can use it freely... or trash it quickly !
Does VOCC Charging works now?
Also, 3-ring headsets do not work (ie like the headset that came in the box).
Great work guys... Running super for an alpha.
There's a typo, it's build in may, not april :good:
lesscro said:
If you want to have a OP more attractive, i know content is attractive but picture too, here it is a simply prez from me...
You can use it freely... or trash it quickly !
Click to expand...
Click to collapse
I'm not a big fan of flashy posts with lots of graphics. Means more data for my browser to load.
hulicow said:
Does VOCC Charging works now?
Click to expand...
Click to collapse
It's in-kernel, it's pretty much impossible to get a device with working charging without VOOC.
kristofpetho said:
Also, 3-ring headsets do not work (ie like the headset that came in the box).
Click to expand...
Click to collapse
That's what I meant by headsets with mics barf. (although headsets with media controls might be in the same boat...)
xabierd said:
There's a typo, it's build in may, not april :good:
Click to expand...
Click to collapse
WHAT? It's not 4/20???
No problem... then trash it as i say...
cheers
It's begun. Glad to see you got it through entropy.
Once the initial hiccups are ironed out this phone can finally take it's place as the stylish and capable smartphone it should have had from the very start.
Gesendet von meinem One mit Tapatalk
Fix for 3-ring jack not working incoming.
Entropy512 said:
Not yet implemented (need to get the basics done first, these shouldn't be too hard since maxwen did them all on N1)
Doubletap to wake
Screen-off gestures
Click to expand...
Click to collapse
Since 7a also use F3 for double tap it should be as easy as adding
<bool name="config_offscreenGestureSupport">true</bool>
to framework overlay
whats also the same is circle -> F4
the rest (F5 - F9) is different to the other oppos - actually we might need to filter them
out at the moment until we add support in the framework for them
maxwen said:
Since 7a also use F3 for double tap it should be as easy as adding
<bool name="config_offscreenGestureSupport">true</bool>
to framework overlay
whats also the same is circle -> F4
the rest (F5 - F9) is different to the other oppos - actually we might need to filter them
out at the moment until we add support in the framework for them
Click to expand...
Click to collapse
Thanks!
BTW, what was the story behind https://github.com/omnirom/android_...mmit/0f6126a18e85e254d15421751abe78939beab1fd - were you getting a bunch of input event spam waking up the device during suspend? That's a problem I'm periodically seeing on this device.
Entropy512 said:
Thanks!
BTW, what was the story behind https://github.com/omnirom/android_...mmit/0f6126a18e85e254d15421751abe78939beab1fd - were you getting a bunch of input event spam waking up the device during suspend? That's a problem I'm periodically seeing on this device.
Click to expand...
Click to collapse
Thats a little help to the "ear opening notification bar on call problem"
on the F5 it can take up to 500ms from screen off because of proxy
sensor until TS suspend is done - this filters out events during that time.
Its kinda hacky and doesnt solve the issue all the time but
better then before and little effort and risk.
We dont have the issue on the N1
maxwen said:
Thats a little help to the "ear opening notification bar on call problem"
on the F5 it can take up to 500ms from screen off because of proxy
sensor until TS suspend is done - this filters out events during that time.
Its kinda hacky and doesnt solve the issue all the time but
better then before and little effort and risk.
We dont have the issue on the N1
Click to expand...
Click to collapse
Wasn't that a different patch?
I'm seeing a problem where the device gets stuck wakelocked processing lots of input event spam from somewhere, or it's not properly flushing the key event queue. It's intermittent - sometimes it's absolutely fine, other times it just goes nuts.
maxwen said:
Thats a little help to the "ear opening notification bar on call problem"
on the F5 it can take up to 500ms from screen off because of proxy
sensor until TS suspend is done - this filters out events during that time.
Its kinda hacky and doesnt solve the issue all the time but
better then before and little effort and risk.
We dont have the issue on the N1
Click to expand...
Click to collapse
ah - no
LOL I was to much ahead and imagined another change you might
also find at some point
This one is actually obsolete AFAIKS since there is a check
for is_tp_suspended on top of the function. Think this is a "leftover"
for our properitary S2W impl that has been obsoleted
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
For instructions about installing or building for maguro, see the CyanogenMod wiki page.
The latest builds are available at http://get.cm/?device=maguro.
Known Issues page for the Galaxy Nexus (GSM) (not updated yet)
Google Apps can be found at http://wiki.cyanogenmod.org/w/Google_Apps - beware that if you choose OpenGApps, only the pico version will fit, unless you change your partition sizes!
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
CyanogenMod 12.1, ROM for the Samsung Galaxy Nexus
Contributors
Ziyan, MWisBest, Everyone else who helped me: AOSP, Hashcode, ...
Source Code: https://github.com/CyanogenMod/
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Snapshot
Created 2014-12-01
Last Updated 2016-07-20
Build instructions
Update: as of 2016/01/03, everything needed is merged, so simply follow the official build guide.
If you don't want to or can't (ex. remote servers) use extract-files.sh, simply clone proprietary_vendor_samsung into vendor/samsung.
wow this is great @Ziyan truly appreciate your awesome work!
Testing it now.
It's actually running really really well! Posting this from the 1130 build now! One thing that did work on FML and just refuses to on cm12 is getting the APN to stick, it says "APN settings aren't available for this user" (which I think it also said in FML but still stuck after it was saved), otherwise everything else has been mentioned in the op as far as quirks are concerned
I'm getting much worse battery life than with the last CM11 nightly. Overnight battery drain was 3.7%/hour, compared to around 1%/hour with CM11. According to GSAM, the main issue was system(mediaserver) at about 94% of battery usage. No media was being served, so far as I can tell. EDIT: battery life often improves for me a day or two after installing a new generation, so I'll see if it gets better today.
I notice that the google bar at the top of the page always has: Say "OK Google." My Nexus 5 running stock doesn't have this.
It's also much laggier than CM11.
Video works with NuPlayer unchecked in Developer Options. Specifically, I could play video with MX player.
Possibly related to camera not working, the flashlight doesn't work. I only tried turning it on with quick settings.
No crashed so far and no app problems other than camera.
Tap and Go setup (against my N5), worked properly. It didn't work on FML.
I'm testing without a SIM at the moment, just wifi.
Thank you Ziyan
I had my SIM fried somehow after i flashed the rom yesterday, I had to replace the sim card today with a new one, the old one is toast.
It happened during "cellular network setup", it wanted my pin number, as soon as i entered it it was asking for my puk number.
Typed it in, things finished but without network connectivity, had the no sim card sign on the statusbar.
Could it be something connected to the rom or it was just my sim card time to go?
Cheers
Just want to say thanks!
Don't have enough posts to be allowed to post on the CM11 thread, so doing it here.
Ziyan,
Thank you so much for your work on this and I am looking forward to the first monthly CM12!
foosion said:
I'm getting much worse battery life than with the last CM11 nightly. Overnight battery drain was 3.7%/hour, compared to around 1%/hour with CM11. According to GSAM, the main issue was system(mediaserver) at about 94% of battery usage. No media was being served, so far as I can tell. EDIT: battery life often improves for me a day or two after installing a new generation, so I'll see if it gets better today.
I notice that the google bar at the top of the page always has: Say "OK Google." My Nexus 5 running stock doesn't have this.
It's also much laggier than CM11.
Click to expand...
Click to collapse
Try turning off ok google detection from the launcher settings - also, if you use the default launcher, set the app drawer animation to "none", because CM forgot to update that part of launcher to lollipop - they left in the animation from 4.4, so it's laggy and ugly. I just submitted the patch set to fix that, they merged it already so the next build will have this set by default.
Also, if you manage to break camera or video playback, I noticed it tends to leave the video processing part of the CPU active all the time until you reboot, so try that out too
As for the lag, it should improve over time.
flip360 said:
I had my SIM fried somehow after i flashed the rom yesterday, I had to replace the sim card today with a new one, the old one is toast.
It happened during "cellular network setup", it wanted my pin number, as soon as i entered it it was asking for my puk number.
Typed it in, things finished but without network connectivity, had the no sim card sign on the statusbar.
Could it be something connected to the rom or it was just my sim card time to go?
Cheers
Click to expand...
Click to collapse
There's no way a ROM could to that
is the camera wb (white balance) fixed?
Same problem here with PUK.
you could collaborate with @MWisBest to solve the basic problems
blacktomcat said:
you could collaborate with @MWisBest to solve the basic problems
Click to expand...
Click to collapse
They already collaborate I think
Ziyan said:
Try turning off ok google detection from the launcher settings - also, if you use the default launcher, set the app drawer animation to "none", because CM forgot to update that part of launcher to lollipop - they left in the animation from 4.4, so it's laggy and ugly. I just submitted the patch set to fix that, they merged it already so the next build will have this set by default.
Also, if you manage to break camera or video playback, I noticed it tends to leave the video processing part of the CPU active all the time until you reboot, so try that out too
As for the lag, it should improve over time.
Click to expand...
Click to collapse
I rebooted and recharged about two hours ago and battery is draining at 1.7%/hour (including listening to music, not just on idle). While it's usually a mistake to rely on short time periods, the prior drain could well have been due to breaking camera and video playback. I'll continue to monitor.
I'm using the google now launcher and like ok google detection. If I get down to similar idle battery drain as on CM11, I'll leave detection on, otherwise I'll test with it off.
I'd hope lag would improve as we go beyond early testing
Thanks
EDIT: battery drain on idle is going down a bit, suggesting your diagnosis of broken video leaving the CPU active was correct.
blacktomcat said:
you could collaborate with @MWisBest to solve the basic problems
Click to expand...
Click to collapse
For those who don't know, we are getting Lollipop on GN because of these 3 people: @Ziyan , @freshgiammi , and @MWisBest. Lollipop FML was only possible because of those 3 people. Same thing applies for CM 12. It's not like they were working separately. So all 3 are due equal credits for making it work for us.
of course thread subscribed and waiting for the amazing work I'm sure ziyan will do :fingers-crossed:
changelog
It would be possible to have a small changelog as they come out new beta?
@Ziyan thank you for your work!
xaifer said:
It would be possible to have a small changelog as they come out new beta?
@Ziyan thank you for your work!
Click to expand...
Click to collapse
look at his git and on review.cyanogenmod.org
Same bug with PUK
Ok, I don't know which information matters but:
I'm in Germany.
Steps before flashing new ROM from the 30th:
-> wipe cache
-> wipe system
-> wipe dalvic
-> flash rom (everything from cwm)
While trying to flash gapps i got error code 6 (Which i found out later was a buggy version of CWM (6.0.4.7)) but I didn't care and rebooted.
Everything seemed to work, but a few seconds later he asked for the PIN (like always).
Typed PIN correctly, after the FIRST try, the phone asked for the PUK.
Now, after flashing a newer CWM and the most recent cm-11 nightly + gapps ... at least everything works again, except for the SIM cause i can't find my PUK ... well, gonna buy a new prepaid tomorrow. Still an interesting bug ... does anybody know how this could happen? Would be nice to use Lollipop, even if it's bugged as hell ^^
edit: Without SIM, the ROM looked awesome. I had no lag and any app worked. BUT the home button did not. ^^
Is this running the newer GPU drivers?
Has anyone tried lollipop minimum gapps yet with these builds?
http://forum.xda-developers.com/showthread.php?t=2943330