Code:
#include
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at us for messing up your device, we will laugh at you.
*
*/
When coming from any other ROM, you must do a factory reset / clean flash.
The first boot can take a very long time. Don't assume that it is a bad flash, boot loop, etc. until it has sat for at least 5 minutes.
Links
ROM: http://download.cyanogenmod.org/?device=victara
Changelog: http://www.cmxlog.com/12.1/victara
GAPPS: http://d-h.st/users/dhacker29/?fld_id=27426 (pick the latest gapps-lpmr1*)
Known Issues
* AudioFX doesn't work.
GPS Issues?
* Asked and answered, search the thread for more info. As of the 2015-06-07 build, there should be no remaining issues so please try a new version before posting about it!
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Device Specific Functionality
Device Specific Functionality
Victara has some unique hardware and this allows us to have some special functionality which mimics some of Motorola's custom software.
User-aware display
The sensors on the phone allow it to recognize if someone (or something) is in front of the screen. In Settings >> Gestures >> User-aware display, you can enable this feature (disabled by default) that will always keep the screen on when an object is in front of it. The object detection starts as soon as the phone is unlocked and stops as soon as the
display is turned off. That is, it will not stay on on the lock screen, only when unlocked. If the phone is stowed (e.g. put in your pocket), it also detects that and doesn't force the display to stay on while it is stowed.
Personally, I set my screen timeout to 15 seconds and enable this feature. This lets me comfortably read anything that I want without the screen timing out and avoids it staying
on too long when unused.
Ambient display
If you have "Ambient Display" enabled in Settings >> Display then:
* the stow sensor and flat up sensor will pulse the display when the phone is picked up
* the IR sensors will pulse the display when you wave your hand over the phone
These can be toggled on or off in Settings >> Gestures >> Ambient display.
Actions
The sensors recognize two gesture:
* The "doorknob" gesture (hold your phone and twist it back and forth a couple of times quickly in a manner similar to twisting a doorknob). By default this will launch the camera.
* The chop-chop gesture (hold on to your phone, tightly, and make two hard karate chopping swings with it). By default this will toggle the torch.
You can customize both of these gestures in Settings >> Gestures >> Actions and you can also configure the amount of haptic feedback for these gestures.
Finally, you can wave your hand over the phone to silence an incoming call. Currently, this functionality only silences calls and not other alarms and notifications.
Camera actions
When the camera is launched by either (or both) of the gestures, different intents are triggered depending on whether or not the phone is locked.
If the phone is unlocked, an intent is sent to start a camera for a still shot. If you have multiple cameras and haven't picked a default for the intent, it will give you the normal app picker and allow you to pick a camera as a default.
If the phone is locked, a different intent is sent to take a still picture in a secure mode. This allows the camera to be used without having to unlock the screen. However, since the screen is still locked, it's not possible to offer an app picker to select the app to use. To make this more usable, the software will try to use the same app as the default app that would have been used if the phone was unlocked. Some apps, though, do not support a secure mode (e.g. snapchat) . If that happens, the system will automatically pick a "best" camera app and there's no way to customize that.
In other words, you can pick the camera app by unlocking the phone and making the gesture and this app wlil then be used (if possible) for both cases.
Hopefully this thread will not be very long lived and we'll be able to get to official nightlies soon. But, in the mean time, I've been doing so much work in 12.1 that it's sad that you guys haven't gotten to use it in CM 12.1.
I just installed and tested last night's build and it seems like it built fine so we should be good to go for unofficial nightlies.
@crpalmer Tnx a lot mate!!!!I will try this now!!!Only one question....when this build will be official,it will be fine a dirty flash from unoff to official one?And this is already based on r5 build?Tnx a lot!!!
Flamehell said:
@crpalmer Tnx a lot mate!!!!I will try this now!!!Only one question....when this build will be official,it will be fine a dirty flash from unoff to official one?And this is already based on r5 build?Tnx a lot!!!
Click to expand...
Click to collapse
Dirty will be fine. No idea if the tag was merged before or after the auto build ran last night. I don't know the time for the build or for the merge.
crpalmer said:
Dirty will be fine. No idea if the tag was merged before or after the auto build ran last night. I don't know the time for the build or for the merge.
Click to expand...
Click to collapse
Tnx a lot mate,the important thing is that i can dirty flash....finally we have cm 12.1!!!Tnx for your amazing work
Flashed it this morning. So far everything is running perfectly. Haven't encountered any bugs and the performance is great, a thousand times better than the stock 5.0 ROM I came from.
@crpalmer this rom is soooo fast!!!Amazing job buddy!!!!Really really nice rom...
Can't see the changelog! The webpage is unable to load!
Flamehell said:
@crpalmer Tnx a lot mate!!!!I will try this now!!!Only one question....when this build will be official,it will be fine a dirty flash from unoff to official one?And this is already based on r5 build?Tnx a lot!!!
Click to expand...
Click to collapse
Have you ever read the rules of xda? If so you should know that YOU NEVER ASK FOR ETA'S. I have had to watch you do this and have ignored it but now I have ignored it for too long. I'm not the first one to tell you to stop asking and follow the rules. Do you realize how annoying you are when you ask this every single day. You could have learned how to build yourself cm with all the time you've spent asking the same damn question. STOP ASKING FOR ETAS! You'll know by reading and stop talking
Also you say "only one question", but you asked 3 questions in that post. Believe me when I tell you it's not just me that it bothers. I am just the one that had finally said something because this has gotten way out of control. Not trying to be a ****, that's not my personality but it is time that someone needs to let you know
skulldreamz said:
Have you ever read the rules of xda? If so you should know that YOU NEVER ASK FOR ETA'S. I have had to watch you do this and have ignored it but now I have ignored it for too long. I'm not the first one to tell you to stop asking and follow the rules. Do you realize how annoying you are when you ask this every single day. You could have learned how to build yourself cm with all the time you've spent asking the same damn question. STOP ASKING FOR ETAS! You'll know by reading and stop talking
Click to expand...
Click to collapse
1 I was not asking for ETA(when this build will be official,it will be fine a dirty flash from unoff to official one?)but if will be fine dirty flash.....anyway...sorry ...
Anyone dirty flashed this from Official CM12?
EvilEvo said:
Anyone dirty flashed this from Official CM12?
Click to expand...
Click to collapse
Crpalmer said it is not recommended since changes have occurred in cm12.1
sent from my Moto X Pure Edition
0.0 said:
Crpalmer said it is not recommended since changes have occurred in cm12.1
sent from my Moto X Pure Edition
Click to expand...
Click to collapse
Too late. Did it already. [emoji23] Everything seems to be running fine though. If I have issues I'll clean flash though.
GPS doesn't seem to be working. What's required for this to work?
skulldreamz said:
Have you ever read the rules of xda? If so you should know that YOU NEVER ASK FOR ETA'S. I have had to watch you do this and have ignored it but now I have ignored it for too long. I'm not the first one to tell you to stop asking and follow the rules. Do you realize how annoying you are when you ask this every single day. You could have learned how to build yourself cm with all the time you've spent asking the same damn question. STOP ASKING FOR ETAS! You'll know by reading and stop talking
Also you say "only one question", but you asked 3 questions in that post. Believe me when I tell you it's not just me that it bothers. I am just the one that had finally said something because this has gotten way out of control. Not trying to be a ****, that's not my personality but it is time that someone needs to let you know
Click to expand...
Click to collapse
Lol but you did actually read his post correctly, didn't you? All he was asking for was if he could dirty flash official builds over the unofficial ones once they are released. Not for an ETA.
Bl4ckX said:
Lol but you did actually read his post correctly, didn't you? All he was asking for was if he could dirty flash official builds over the unofficial ones once they are released. Not for an ETA.
Click to expand...
Click to collapse
I did see the user ask multiple times here http://forum.xda-developers.com/mot...cm-12-0-lp-unofficial-nightly-builds-t2987466
---------- Post added at 10:59 AM ---------- Previous post was at 10:57 AM ----------
floepie said:
GPS doesn't seem to be working. What's required for this to work?
Click to expand...
Click to collapse
Go back to stock, get a GPS lock, then restore CM backup. Preferably the 5.1 leaked soak or 5.0. I wouldn't recommend KitKat
0.0 said:
Go back to stock, get a GPS lock, then restore CM backup. Preferably the 5.1 leaked soak or 5.0. I wouldn't recommend KitKat
Click to expand...
Click to collapse
While this undoubtedly would work, what's the theory behind this? What is a GPS lock? It just seems like a strange problem with a stranger solution. Presumably all the libs are there to make it work, so you would think the GPS could be just kick-started with a utility of some sort.
floepie said:
While this undoubtedly would work, what's the theory behind this? What is a GPS lock? It just seems like a strange problem with a stranger solution. Presumably all the libs are there to make it work, so you would think the GPS could be just kick-started with a utility of some sort.
Click to expand...
Click to collapse
The firmware read and write data from persistent (not your normal data partition). Whether or not it is locked persists across a format of the sdcard.
Does this mean official cm12.1 nightlies will be built for our device today onwards
http://www.cyanogenmod.org/blog/microsoft-and-cm12-1-nightlies
Edit : looks like they are indeed coming for victara
http://review.cyanogenmod.org/#/c/94693/
Related
PLEASE DO NOT POLLUTE THE DEV THREAD
Ok so we all know that all questions belong in the Q+A section right?... And bug reports, logcats and any useful additional information belongs in the Development thread... A developer needs to be able to read his/her thread to find out the real bugs and faults in the latest build without sifting through people telling us about their inability to flash a rom.. especially before they've even bothered to search the thread, forums or even Google!
Here you can talk about what ever you want to.. ask questions about anything Cyanogen related!
Another way you can help yourself and the developer is to read this quote from the Cyanogenmod team (20 Feb 2013):
"Some folks have seemingly forgotten (or were never fully aware) what nightly builds are for.
Nightlies are not released as an end product.
What does this mean? It means they are built, automatically and periodically, with no human intervention and no audience in mind whatsoever. They are not verified before being published, and their principal purpose is to compile code and see if it builds on a per device basis. Build failed? That’s a positive result. Build completed? That’s a positive result.
What’s happening is we are getting JIRA reports, tweets, messages, pm’s, emails, you name it, complaining about failed builds or ‘bugs’ on nightlies; on widespread (popular or all devices) problems, we’re downright overrun with complaints. Quite frankly, we close them, delete them or otherwise ignore them. But even those actions divert our attention and time. There is a better way.
Let’s be honest, if we didn’t want you to use nightlies, we would just stop making them public. And truth be told, you guys flashing them and keeping track of issues does have an upside, but only if it’s done in a constructive manner.
How you can help:
# If you have a bug that can be reproduced, flash the most recent M-series or stable build, reproduce it and open a JIRA ticket with a log.
# Flash a recent nightly and see if you can recreate it. Post your result as a comment to the issue created in the step above.
# Wait. We make an active effort to engage folks and assign out JIRA tickets. We don’t need updates on this for every nightly; and we don’t need “me too” comments, as long as the original ticket has all the requested information. If its not fixed in the next M-release or stable, add another comment to your issue saying so".
DOWNLOAD: http://www.get.cm/?device=i9305
CHANGELOG: http://changelog.bbqdroid.org/#i9305/cm10.1/next
DEVELOPMENT THREAD: http://forum.xda-developers.com/showthread.php?t=2157651
Finally a thread for me to ask a issue i been facing ever since i start using cm.
Is it me or its normal for current nightly version to be unable to pull down the status bar at all when in any full screen games/app? I try swiping from top no matter how i tried nothing works.
Beside this, everything else seems great, even much better battery improvement compare to stock.
Just want to check if it is anything i am missing out.
ljhsquall said:
Finally a thread for me to ask a issue i been facing ever since i start using cm.
Is it me or its normal to be unable to pull down the status bar at all when in any full screen games/app? I try swiping from top no matter how i tried nothing works.
Click to expand...
Click to collapse
I'm pretty sure that has always been the way when playing full screen games/apps. I noticed that when watching 'TVCatchup' in full screen.
But because we have 2GB of RAM if you pause the game then press the home button, most games will stay running in the memory so that you can check notifications and even run more apps and still be able to resume back to the game.
Silly question but I'm not sure of the answer, but are we meant to have photosphere with this camera?
I have the latest nightly but my camera doesn't have the option :S
Sv: [DISCUSSION][GT-I9305][JB][4.2.2] CyanogenMod 10.1 official nightlies
I have low mic volume in standard headset and max volume on speaker is also a bit low. Biggest problem is the mic problem. These are the only problems I have with this rom.
Thanks
Edit: should posts like this be in this or in the nightly thread?
Skickat från min GT-I9305 via Tapatalk 2
vyper91 said:
Silly question but I'm not sure of the answer, but are we meant to have photosphere with this camera?
I have the latest nightly but my camera doesn't have the option :S
Click to expand...
Click to collapse
No Cyanogenmod doesn't include PHOTOSPERE... yet...
But try this: http://forum.xda-developers.com/showthread.php?t=1746611
This modded app includes PHOTOSPERE and even the option to save to external.
Good initiative mate, can't wait to run this rom, unfortunately because of problems documented elsewhere on this forum I cannot at the moment, but I will be getting a new I9305 soon (won one in a promotion Samsung had a while back in my city!), and that will be running CM10.1!
Does smart view work with the official version of cm 10.1?
I tryed on the cm-10.1-20130305-UNOFFICIAL-i9305 it doesn´t worked.
Thanks for your answers :fingers-crossed:
Kernelponik said:
Does smart view work with the official version of cm 10.1?
I tryed on the cm-10.1-20130305-UNOFFICIAL-i9305 it doesn´t worked.
Thanks for your answers :fingers-crossed:
Click to expand...
Click to collapse
Do you mean Smart Stay? If so then no sadly not. But if you search the PlayStore you will find alternatives
Guys - has the ability to use lockscreen shortcuts not been implemented yet?
I've selected some shortcuts but they don't appear...
winwiz said:
Guys - has the ability to use lockscreen shortcuts not been implemented yet?
I've selected some shortcuts but they don't appear...
Click to expand...
Click to collapse
And you pressed save?
matthewgwilt said:
And you pressed save?
Click to expand...
Click to collapse
yup
on messing around with it further, just noticed that the shortcuts dont work with a pattern lock?
winwiz said:
yup
on messing around with it further, just noticed that the shortcuts dont work with a pattern lock?
Click to expand...
Click to collapse
Shortcuts are meant for the unscure swipe unlock method although I think you can opt to have swipelock after pattern
Lost all my internal storage content
Hi guys, I recently installed the latest CyanogenMod 10.1 Nightly for my i9305;
I used the TWRP recover, did a factory reset first, cleared cache and dalvik cache, installed the rom, and suddenly all of my data has been lost but it appears as "System Data" in the app "DiskUsage" (I used this to see where my storage was being used), please see the attached screenshot.
Where would this content have possibly been moved to? I'm talking about the folders like DCIM, Downloads, etc
kanecharles92 said:
Hi guys, I recently installed the latest CyanogenMod 10.1 Nightly for my i9305;
I used the TWRP recover, did a factory reset first, cleared cache and dalvik cache, installed the rom, and suddenly all of my data has been lost but it appears as "System Data" in the app "DiskUsage" (I used this to see where my storage was being used), please see the attached screenshot.
Where would this content have possibly been moved to? I'm talking about the folders like DCIM, Downloads, etc
Click to expand...
Click to collapse
Sure it isn't just in the "0" folder in the sdcard folder? Also, I hate to be that guy but TWRP isn't supported by the CyanogenMod team.
Is this an external SD card? If so the problem is likely that your card was formatted as exFAT prior to installing CyanogenMod. exFAT isn't an open filesystem, and CyanogenMod are not licensed to redistribute the filesystem, so it can't read it.
Rekoil said:
Sure it isn't just in the "0" folder in the sdcard folder? Also, I hate to be that guy but TWRP isn't supported by the CyanogenMod team.
Is this an external SD card? If so the problem is likely that your card was formatted as exFAT prior to installing CyanogenMod. exFAT isn't an open filesystem, and CyanogenMod are not licensed to redistribute the filesystem, so it can't read it.
Click to expand...
Click to collapse
It is the internal storage, and by the "0" folder do you mean /storage/emulated/0/ ? It doesn't appear to be in there either. Yea I used to use CWM Recovery but I thought I'd give TWRP a try.
---------- Post added at 11:28 AM ---------- Previous post was at 11:04 AM ----------
I found it all, it had been moved to /data/media
Sent from my GT-I9305 using xda app-developers app
Another question,
I have the iBolt Galaxy s3 car dock; a lot of the kernels I've tried don't detect the dock, the same is true for the included kernel with CM 10.1 when I flashed it. I used to use Perseus kernel with RipperROM, when I flashed it with the new CM 10.1 it wouldn't even boot, I had to go into recovery and reflash the CM 10.1 ROM over the top to get the CM kernel again; are there any known compatible kernels I can use that will have support for my car dock? Cheers, Kane.
No signal bar on status bar
Hi.
This is my first foray into ROM flashing and it was a hell of a lot simpler than I thought it would be (the horror stories on here almost put me off ).
It really is a lovely ROM. Smooth and clean.
I'm working from the 17/03/13 Nightly and the only real problems I have are
Sometimes I get Unfortunately,the process com.android.phone has stopped working on my screen and the data cuts out. Not a huge issue as I just go to quick settings, turn the data off and back on again and its back working fine.
I have lost the mobile signal bar from the status bar at the top of the screen. I've got the time, battery, Wi-fi, alarm and sound icons. Just not the carrier signal bars. I've tried rebooting the phone but its still not there. Again not a huge deal breaker as I'm still getting a signal (I can still make calls, texts, mobile data etc). I'm just not seeing the icon on my status bar.
I notice that the battery light pulse length and speed is not working. Always default to custom, only can choose the color.
Notification light is working fine though.
ljhsquall said:
I notice that the battery light pulse length and speed is not working. Always default to custom, only can choose the color.
Notification light is working fine though.
Click to expand...
Click to collapse
Yeah noticed this too. I like it flashing green whilst charging, so I can use yellow for exchange email. But can't do it when green won't flash for charging.
Also, I know it's a long shot, but I've heard mixed reports of MHL for the i9300 version. Is there any chance if it for this version? I LOVE Cyanogen Mod, but MHL/TV out is a function I use a bit.
CyanogenMod is a free, community built distribution of Android 4.2 (Jelly Bean) which greatly extends the capabilities of your phone.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
XDA:DevDB Information
{V}[DEVELOPMENT] - CM10.2 - Android 4.3 - FreeXperia Project, a ROM for the Sony Xperia V
Contributors
FXP, kali
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.4.x
Version Information
Status: Testing
Created 2013-11-04
Last Updated 2013-11-04
HOWTO
Install instructions:
first time
- power off the phone:
- hold vol+ and plug usb to boot into fastboot (blu led)
- fastboot flash boot boot.img (from cm10 zip)
- fastboot reboot
- enter recovery, on boot led will be violet for 3'', during this period press vol+
- flash rom zip
- flash gapps zip
- wipe
- reboot
for update just flash rom zip from recovery
Google Apps are not included in this ROM. You'll need to find those yourself if you want them.
ENJOY AN UNOFFICIAL CM10 RELEASE BROUGHT TO YOU BY FreeXperia Team
PLEASE DONT MIRROR OUR ROMS
DOWNLOAD
http://unrestrict.li/FXP
thanks to all who made this possible supporting us
contributing with code, donations or even trusting us
thanks to SONY that made all this possible !
FXP244 released
I'm surprised that there's no replies. Anyways, anyone tried the latest nightly?
Sent from my LT25i using Tapatalk
BloodLust012 said:
I'm surprised that there's no replies. Anyways, anyone tried the latest nightly?
Sent from my LT25i using Tapatalk
Click to expand...
Click to collapse
I'm replying Will test when I get home tonight
I am on the latest CM nighty and soo far soo good. I haven't found any bug.
Only battery consuption is maybe higher than on stock.
Only think what I don't like is the size of navbar. I would prefer much smaller size.
Hi all,
does anyone have the following issue:
If I open the Dialer and select the third page/tab, where "Frequently called" and "All contacts with phone numbers" is placed, it takes about 1 minute until the contacts with phone numbers appear. My first thought was, ok, the system scans them one time and after this everything is fine. But no, nearly every time I open the Dialer, this happens. Additional, within this "scan time", my call log is empty and if I call someone (part of my contacts list), his name doesn't appear.
Does anyone know something about this behavior?
This issue occurred first time, after installing the nightly from 13/11/04 and the google apps (full wipe was done). Before, with the same nightly(!), everything was ok. The following nightlies hasn't fixed it (05/07). Also my battery life is much shorter since that, round about 50% to 75% percent compared to before.
Best regards
Imk82
imk82 said:
Hi all,
does anyone have the following issue:
If I open the Dialer and select the third page/tab, where "Frequently called" and "All contacts with phone numbers" is placed, it takes about 1 minute until the contacts with phone numbers appear. My first thought was, ok, the system scans them one time and after this everything is fine. But no, nearly every time I open the Dialer, this happens. Additional, within this "scan time", my call log is empty and if I call someone (part of my contacts list), his name doesn't appear.
Does anyone know something about this behavior?
This issue occurred first time, after installing the nightly from 13/11/04 and the google apps (full wipe was done). Before, with the same nightly(!), everything was ok. The following nightlies hasn't fixed it (05/07). Also my battery life is much shorter since that, round about 50% to 75% percent compared to before.
Best regards
Imk82
Click to expand...
Click to collapse
I don't have any issue with my dialler on the yesterdays second nighty. Battery life is quite short as I mentioned before and sometimes phone gets really hot.
I really wish to compile CM on my device by myself but I haven't succeded yet.
Well, if you look at the changelog (http://mobile.10.2.cmxlog.com/?device=tsubasa ), there must have been some issues with the contacts app. Could be related to your issue. Should be fixed by now though.
- Overheating issue happen only on 3G connection, If yo switch on 2g the phone cool down immediately.
- In video recording there are some audio pops and clicks, sometimes the framerate goes down.
- Sometimes the phone doesn't wake up pushing the power button
Sent from my LT25i using xda app-developers app
Great, new nightly
tulen_kobi said:
Great, new nightly
Click to expand...
Click to collapse
Hi tulen_kobi,
what are the concrete great things / improvements?
---------- Post added at 05:39 PM ---------- Previous post was at 05:28 PM ----------
[/COLOR]
imk82 said:
Hi all,
does anyone have the following issue:
If I open the Dialer and select the third page/tab, where "Frequently called" and "All contacts with phone numbers" is placed, it takes about 1 minute until the contacts with phone numbers appear. My first thought was, ok, the system scans them one time and after this everything is fine. But no, nearly every time I open the Dialer, this happens. Additional, within this "scan time", my call log is empty and if I call someone (part of my contacts list), his name doesn't appear.
Does anyone know something about this behavior?
This issue occurred first time, after installing the nightly from 13/11/04 and the google apps (full wipe was done). Before, with the same nightly(!), everything was ok. The following nightlies hasn't fixed it (05/07). Also my battery life is much shorter since that, round about 50% to 75% percent compared to before.
Best regards
Imk82
Click to expand...
Click to collapse
The issue / problem is gone now. I thinke the root cause was not a bug, rather a combination of the things I did after the full wipe:
First I installed "CalDAV-sync" and "CardDAV-sync" from the market. After this I configured the CardDAV Account, whereupon my contacts appeared in the contacts app. Now the CardDAV Account was added, but no calendar entries were synced. After some time of investigation I found out, that the privacy guard function of Cyanogenmod (accidentally activated by me) was the problem, so I disabled it for both apps, which fixed the problem with the calendar.
In summary it was just necessary to remove the CalDAV Account again and to add it again with disabled privacy guard.
Best regards
Imk82
imk82 said:
Hi tulen_kobi,
what are the concrete great things / improvements?
Click to expand...
Click to collapse
Personally I haven't noticed any difference between this and previos nighty, everything works for me.
But battery life is still shorter than on stock based roms.
tulen_kobi said:
Personally I haven't noticed any difference between this and previos nighty, everything works for me.
But battery life is still shorter than on stock based roms.
Click to expand...
Click to collapse
Phone: Honor the "Rejected calls as missed" option
When the type of a call is set, either for the purposes of call logging or to
display a notification for a missed call, the value of the "Rejected calls as
missed" option should be checked as well. However, in CM 10.2 this check is
missing, and thus the option has no effect. This patch reintroduces the check.
UPCOMING FIXES AND CHANGES IN NEXT NIGHTLY:
camera: Improve UX consistency (android_packages_apps_Gallery2)
tsubasa: add sysmon config (android_device_sony_tsubasa)
alsa_sound: Fix for AV Sync related issues (android_hardware_qcom_audio-caf)
alsa_sound: Usb headset support for VOIP call (android_hardware_qcom_audio-caf)
alsa_sound: Configure the USB and PROXY device with proper sample rates (android_hardware_qcom_audio-caf)
alsa_sound: Start proxy when external output is enabled (android_hardware_qcom_audio-caf)
alsa_sound: Fix mExtOutMutex related lock issue (android_hardware_qcom_audio-caf)
Camera: Skip switch camera command when camera state is busy (android_packages_apps_Gallery2)
Gallery2: not enable video pause feature for Timelapse recording (android_packages_apps_Gallery2)
Camera: use send command to main handler to avoid race condition (android_packages_apps_Gallery2)
tsubasa: remote duplicate blob (android_device_sony_tsubasa)
Does anyone else have a problem with photos using LED?
For me it seems the phone shutters a bit too late after the LED has flashed - consequence: quite dark photos although LED theoretically could make them look better.
A solution is to touch the manual focus (LED starts) and then immediately taking a photo. Then the photo is brighter. But this is quite uncomfortable.
Could anyone please test this with his phone?
dyfk3l said:
Does anyone else have a problem with photos using LED?
For me it seems the phone shutters a bit too late after the LED has flashed - consequence: quite dark photos although LED theoretically could make them look better.
A solution is to touch the manual focus (LED starts) and then immediately taking a photo. Then the photo is brighter. But this is quite uncomfortable.
Could anyone please test this with his phone?
Click to expand...
Click to collapse
Hey! I cannot confirm this...
Only problem is battery life and video recording, also sometimes its not as snappy as some previous builds.
nightly-20131112
The latest nightly (20131115) causes my device to not boot. There's a brief vibrate when it's turned on but then the screen just stays black. Fortunately booting to fastboot mode and applying boot.img from the previous nightly seems to revive it.
apcd2 said:
The latest nightly (20131115) causes my device to not boot. There's a brief vibrate when it's turned on but then the screen just stays black. Fortunately booting to fastboot mode and applying boot.img from the previous nightly seems to revive it.
Click to expand...
Click to collapse
Same here. Even i had to solve it by flashing boot.img from the previous nightly.
FXP245
CM10.0
- latest cm 10.0
CM10.1
- latest cm 10.1
CM10.2
- latest cm 10.2
- Add missing thermal configuration (V)
Upcoming Fixes for Overheathing Issue?
Code:
#include warranty.h
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
New Builds will be uploaded to my Dropbox
Please dont mirror my builds!!
Do NOT expect daily builds. I'll build when I'm free.
Do NOT use this unofficial build and ask for support at the official threads.
Do NOT be rude.
Respect all users
If u see a NOOB question and u don't feel like replying, DON'T, just ignore that post. If u do reply, good for u.....and be nice in your reply.
Don't use the dual recovery since its based on the Xperia Z1. You'll get an error while flashing the build.
Known Bugs:
Camera app doesnt capture photo's
Video recorder shows black screen
NFC doesn't work
Download:
Dropbox
Google Drive
Github
Dont forget to hit that thanks button!
Credits:
@Abhinav2 For helping me out many times
CyanogenMod for sharing their sources
The community for supporting and testing!
So far the camera preview works but does not capture pictures
It's here!! Finally.
Sent from my D6503 using Tapatalk
Great to see CM on Z2
Also, if sat for a while, the touchscreen stops working and i cannot unlock the phone
Is anyone else experiencing the issue mentioned above? I have my screen of for long times now but its restoring my apps from Play store so it doesnt go in to sleep. The rom feels so damn smooth and im so pleased its finally here. Have had my Z2 since release but havent used it, I stayed with my Nexus 5 waiting for CM/AOSP to release for Z2. Thank you OP
skitty said:
Also, if sat for a while, the touchscreen stops working and i cannot unlock the phone
Click to expand...
Click to collapse
Isn't it working at all or sometimes? Can someone confirm this??
nickwarn said:
Is anyone else experiencing the issue mentioned above? I have my screen of for long times now but its restoring my apps from Play store so it doesnt go in to sleep. The rom feels so damn smooth and im so pleased its finally here. Have had my Z2 since release but havent used it, I stayed with my Nexus 5 waiting for CM/AOSP to release for Z2. Thank you OP
Click to expand...
Click to collapse
Well you could go and change your signature now) I don't have the Z2 so I cant confirm any bugs or something! Glad you like it
QuickS_NL said:
Well you could go and change your signature now) I don't have the Z2 so I cant confirm any bugs or something! Glad you like it
Click to expand...
Click to collapse
I can now confirm the lockscreen bug. When the screen times out and i wake it up again the screen isnt responding to touch. I can see the system downloadin updates and my lockscreen time widget keeps changing so its not frozen, it just doesnt respond to touches.
Glad to see CM finally on Z2. Great job mate. I have contacted Mods to move your thread to the Original Development Section, As it should be there... Hope that is fine.
Yes!
When it goes Nightly, i will flash it on my Z2. Without the Camera and Video it´s a little bit anoying
stanley08 said:
Glad to see CM finally on Z2. Great job mate. I have contacted Mods to move your thread to the Original Development Section, As it should be there... Hope that is fine.
Click to expand...
Click to collapse
Yeah ofc! It's fine!
nickwarn said:
I can now confirm the lockscreen bug. When the screen times out and i wake it up again the screen isnt responding to touch. I can see the system downloadin updates and my lockscreen time widget keeps changing so its not frozen, it just doesnt respond to touches.
Click to expand...
Click to collapse
Is it sometimes or can't you use your device at all?
QuickS_NL said:
Is it sometimes or can't you use your device at all?
Click to expand...
Click to collapse
No, its not usable. Every time the screen times out and i wake it it happens. Didnt happen at first boot, but ever since I rebooted first time it happens every time.
I'm so happy
Big thanks Bro
For me it working fine so far
I flash it with twrp and for now (2hours) no bugs accepted the know one
Sorry for bad English
t0pstar said:
I'm so happy
Big thanks Bro
For me it working fine so far
I flash it with twrp and for now (2hours) no bugs accepted the know one
Sorry for bad English
Click to expand...
Click to collapse
Have you rebooted your device since first boot?
I can look into camera problems. Can anyone explain bug and submit suitable logs?
Cheers,
AJ
Abhinav2 said:
I can look into camera problems. Can anyone explain bug and submit suitable logs?
Cheers,
AJ
Click to expand...
Click to collapse
Nice to see you here AJ.
QuickS_NL said:
Yeah ofc! It's fine!
Click to expand...
Click to collapse
They will move it if they wish.
Abhinav2 said:
I can look into camera problems. Can anyone explain bug and submit suitable logs?
Cheers,
AJ
Click to expand...
Click to collapse
Hmm, the photo app doesn't focus in photo mode. It just takes a photo (without focusing) when pushing the button or refuses to do anything if you try to select a focus point in the picture.
In video mode, only a blank screen is displayed. You can start recording but can't stop it, the app seems to hang (a video file with mp4.tmp is created but the file is corrupted)
Sorry, alogcat doesn't provide any details...
Been rocking this most of the day, battery seems to be just as good as if stamina mode was enabled on stock. Runs smooth and only issue I can find besides the camera as previously stated is WiFi hotspot says error when I try and enable it.
I haven't got the unresponsive touch that has been mentioned, wakes up just fine for me.
Next step after I've set everything up how I like it is to check what kinda kernel options are available, maybe see if @DooMLoRD is up for making a compatible kernel maybe ☺
Sent from my Xperia Z2 using Tapatalk
I'm not responsible for any damage to your device of any sort.
By flashing this you take responsibility of anything that happens.
Process at your own risk!
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community
Requirements:
- twrp 3.2.0+
- backup everything before install
- wipe data before upgrading from LineageOS 14.1 or stock rom
Install:
- Flash zip in TWRP
- Don't forget about gapps (arm 8.1)
Google apps should be installed via recovery immediately after installing ROM.
If you reboot into ROM before installing Google apps, you must factory reset and then install them, otherwise expect crashes.
Known issues:
unstable fingerprint
stuff, I haven't checked
Download:
T810: https://drive.google.com/open?id=1LlC7jBfq3H9FuPKZeKdQ3KyuiglgJTYv
T815: https://drive.google.com/open?id=1ZXg6Oy_aSfYL4XoXovfPzQ9pZqD1XVmw
Device sources:
https://github.com/bonuzzz
Yeah! Thanks for all the work.
I flashed the rom (t810) but the orientation is upside-down: not easy to press the right buttons :laugh:
So I couldn't really test it further.
halloarno said:
Yeah! Thanks for all the work.
I flashed the rom (t810) but the orientation is upside-down: not easy to press the right buttons :laugh:
So I couldn't really test it further.
Click to expand...
Click to collapse
do you mean the orientation of touch sensor?
bonuzzz said:
do you mean the orientation of touch sensor?
Click to expand...
Click to collapse
Screen is upside-down (orientation sensors are OK). And screen touch sensitivity is normal. So I see a button in left up corner and have to touch in right down corner where it actually has to be.
halloarno said:
Screen is upside-down (orientation sensors are OK). And screen touch sensitivity is normal. So I see a button in left up corner and have to touch in right down corner where it actually has to be.
Click to expand...
Click to collapse
I will upload proper build tomorrow. Thanks for bug report!
Boom. Been waiting for 8.1 for 815 for ages. Thanks for your work can't wait to see how this progresses!! ?
bonuzzz said:
I will upload proper build tomorrow. Thanks for bug report!
Click to expand...
Click to collapse
Congratulations bonuzz very happy to hear your success thanks a lot for your work
Ok one more thing can I use your work to build a different os please man?
( seem to be blind (or stupid) - Can someone please point me to a working TWRP 3.2 for the T810 so I am ready when the new build drops? Thanks a bunch!)
Edit: Sorry, found it. Stupid indeed.
I fixed drm stuff, so netflix is working now. I want to fix some small things before uploading new build, but I'm not sure I finish and make new builds today. @Androbots feel free to use all code from github
I suspect that the display is rotated 180 degrees because there are one too many hwrotation=270 entries between the gts2-common and gts210 device trees. I'm running my own build right now with all those extra ones removed, including having taken out the system_prop.mk file from the gts210wifi repo, since it's identical to the system.prop file already there. Out of respect for bonuzzz, I won't post my own build in this thread.
For those wondering, the official 3.2.1 TWRP works perfectly fine.
bonuzzz, I haven't tested your build yet, but if you managed to fix wifi and bluetooth, I take my hat off to you sir
ripee said:
I suspect that the display is rotated 180 degrees because there are one too many hwrotation=270 entries between the gts2-common and gts210 device trees. I'm running my own build right now with all those extra ones removed, including having taken out the system_prop.mk file from the gts210wifi repo, since it's identical to the system.prop file already there. Out of respect for bonuzzz, I won't post my own build in this thread.
For those wondering, the official 3.2.1 TWRP works perfectly fine.
bonuzzz, I haven't tested your build yet, but if you managed to fix wifi and bluetooth, I take my hat off to you sir
Click to expand...
Click to collapse
Only t810 and t815 require rotation, so this parameter is in device specific config only. And if you have several strings it doesn't mean the image on display will rotate each time. It is just duplicate string.
Why not you finally create your own thread for your builds? I think it will be good idea:good: You have link to your builds in your signature, but you don't have any place where your users can ask you for help...
Nice to see U back @bonuzzz, especially with such amazing things ?
As always, I keep my fingers crossed for U and Ur great things for Android community. Keep on and NEVER give up! Thx for all ur efforts ?
bonuzzz said:
Only t810 and t815 require rotation, so this parameter is in device specific config only. And if you have several strings it doesn't mean the image on display will rotate each time. It is just duplicate string.
Why not you finally create your own thread for your builds? I think it will be good idea:good: You have link to your builds in your signature, but you don't have any place where your users can ask you for help...
Click to expand...
Click to collapse
Because right now my builds are in worse shape than yours, assuming you fixed wifi, bluetooth, the 180 degree display rotation, and everything else in your OP.
Edit: If the gts210vewifi is anything to go by, Oreo requires an hwrotation of 90, not 270 as in Nougat, for the proper orientation, courtesy of luk1337.
Voytec83 said:
Nice to see U back @bonuzzz, especially with such amazing things
As always, I keep my fingers crossed for U and Ur great things for Android community. Keep on and NEVER give up! Thx for all ur efforts ?
Click to expand...
Click to collapse
Go away, spammer
ripee said:
Because right now my builds are in worse shape than yours, assuming you fixed wifi, bluetooth, the 180 degree display rotation, and everything else in your OP.
Edit: If the gts210vewifi is anything to go by, Oreo requires an hwrotation of 90, not 270 as in Nougat, for the proper orientation, courtesy of luk1337.
Click to expand...
Click to collapse
I have the same behaviour in tab s3, but I thought it is because of libs from another device. But it's very funny, in oreo rotation is in another side)
PS: I mean not only oreo builds...
Yup, setting hwrotation to 90 instead of 270 fixes the display being flipped. As for wifi and bluetooth, I will patiently wait for your expertise, bonuzzz
ripee said:
Yup, setting hwrotation to 90 instead of 270 fixes the display being flipped. As for wifi and bluetooth, I will patiently wait for your expertise, bonuzzz
Click to expand...
Click to collapse
bt issue is just permission issue net_bt_stack --> bluetooth in init scripts
for wifi fix you will wait very very long time...
To be honest, I don't want to collect again the guys, who just "patiently waiting" for new commits from my side and fully depended from my work. Users will have cloned roms with same issues.
bonuzzz said:
bt issue is just permission issue net_bt_stack --> bluetooth in init scripts
for wifi fix you will wait very very long time...
To be honest, I don't want to collect again the guys, who just "patiently waiting" for new commits from my side and fully depended from my work. Users will have cloned roms with same issues.
Click to expand...
Click to collapse
So why make the effort to build again? This is the same old story with you. One day, you are helpful and generous with your builds; the next day, you complain about not wanting to make any more effort than you had already made.
Please make a decision and stick with it: either do your best to fix the most basic functions and let someone like me help you the best way I can by building from your code often, and giving you full credit, so that we can all give you frequent feedback, or don't create any more threads and abandon the 2015 Tab S2.
widevine L1 support added. we dont need patched netflix apks anymore
@ripee I make roms for myself and share them with others. What's wrong with that? And yes, I'm helpful and generous when you write me pm. Just curious, nobody asked for help in public. And yes, everything is depends on my spare time.
Nougat builds are really abandoned. You don't believe me or what? Or I should to write anything else there when people ask for update builds?
I see you worry about my git. Calm down, please. Why do you think I upload sources for you? I uploaded sources for you and you published your builds just right after that without understanding what exactly changed and instead of help to fix remain bugs. I told you few months ago to choose one author and try to fix something. You didn't hear me. I don't need any credits. But I don't like liars, if we talk about one person here. And I don't want more "we don't care" teams here. I don't need any daily public builds. It will be disorganized development. At least no one else haven't tried to fix anything in my (nougat) sources...
So, in short, I will do what I want. I will upload builds when I want. I will add/fix/change in builds what I want and in my own priority. I spend my own time for that. Don't like? Don't use. Make something yourself. Stop depend from me and let me do my work. Thanks in advance.
I just saw Shiny thread here ^-^ . I look twice to make sure it is 815 not anything else.
Thank you very much. We all appreciated your work and effort.
If you want any help test, logcat or even setup machine for build I'm ready for that ^-*
bonuzzz said:
I fixed drm stuff, so netflix is working now. I want to fix some small things before uploading new build, but I'm not sure I finish and make new builds today. @Androbots feel free to use all code from github
Click to expand...
Click to collapse
Thanks a lot. Appreciate your work for our Tab S2. Have a good day mate?
Hi,
I just double checked the RR homepage if there is any Update regarding a new Mi5 Rom. And yes: Since a couple of days there seems to be a new ROM "RR-P-v7.0.0-20190220-gemini-Official" available. I can't found it within the Rom section on XDA.
Do you have any experience with the ROM? Battery, bugs?!
I know: It's very easy to flash and discover on my on. But maybe you can give some feedback or create a Thread within the XDA Rom section (not sure if only the dev's are allowed to).
https://get.resurrectionremix.com/?dir=gemini
Regards
I'm currently using it.
Only issue so far is ambient display that doesn't work.
Other than that it's really really fast
Its blazingly fast and give 7 hours of screen on time
Does ambient display work for you?
Or at least does the screen light up when you receive notifications?
j4472 said:
Its blazingly fast and give 7 hours of screen on time
Click to expand...
Click to collapse
Is battery life better than jdc nougat revived ?
rmrbpt said:
Does ambient display work for you?
Or at least does the screen light up when you receive notifications?
Click to expand...
Click to collapse
I finally managed to flash the latest Version (20190307) with Firmware version 8.11.22. Ambient light is not working - Screen stays dark. Only LED showing up.
About battery usage I can tell u more soon - Right now it says up to 2 more days.
Performance is really incredible. How fast the apps are coming up after touching them - Nice.
Another thing: I somehow can't manged to set vibration only for the HW keys - Not the onscreen Keyboard. Anybody any idea?
sarnz said:
Is battery life better than jdc nougat revived ?
Click to expand...
Click to collapse
Yes battery life as similar to JDC nougat revived
But the ROM is not stable
2019.03.16 have a goog battery life?
respeckt said:
[...] or create a Thread within the XDA Rom section (not sure if only the dev's are allowed to).
Click to expand...
Click to collapse
Well, technically everyone is allowed to create threads, but what is expected always is that you use common sense and respect the work of others.
With that in mind, creating a thread for a ROM should only be done by its developer or maintainer or at least always only when politely asking the creators for allowance beforehand.
Review based on 16.03 build
Hi,
the 16.03 introduced new issues like random reboots 1-2 times per day.
The Spotify App isnot working properly as if you press buttons to open a sub-menu it lead into a App crash (Like "More from this artist"/ "More from this Album"/"Add to playlist"). I tried Beta/Alpha/stable App version but always the same.
I had lot of issues with push notifications. They came up like 20-30min after received something.
The battery drain and performance is still incredible. Better than on HAVOC OS on which I'm right now.
Ambient display still not working - Screen show nothing after receiving a notification.
Automatic brightness is not working properly from my perspective - It is much to "aggressiv" switching the screen brightness to high and toggling a lot.
Used firmware: fw_gemini_miui_MI5Global_8.11.22_c5d7ee6745_8.0
Right now I'm struggling with super low mobile data rate around 0,03MB/s. But I have the same issue with HAVOC Rom - So nothing to do with that rom.
(ROM was dirty flashed over 09.03 RR build. I switched now to HAVOC Rom which is much more stable)
Phil_Smith said:
Well, technically everyone is allowed to create threads, but what is expected always is that you use common sense and respect the work of others.
With that in mind, creating a thread for a ROM should only be done by its developer or maintainer or at least always only when politely asking the creators for allowance beforehand.
Click to expand...
Click to collapse
Why there is no forum for resurrection remix
j4472 said:
Why there is no forum for resurrection remix
Click to expand...
Click to collapse
Some prefer certain channels.
Some only release on telegram, some only on xda, some on both or more.
If you ask the creator, there might be one, if you want one to be there and feel up for maintaining it.
On Mi5Arsenal telegram a new version of this romm appeared. 20190414.
Has anyone tried it?
Can you check if ambient display works on this new version?
More importantly are random reboots gone in new bulid?