RROS for moto e5 is here and this is what you need to know
bugs
- no
Download
GKart_builds - Browse /nora/ResurrectionRemixOS at SourceForge.net
builds by GKart
sourceforge.net
credits
- thanks to resurrection remix OS team for the sources of the ROM
- thanks to @whodat711 for the vendor and common sources
Sources
- ROM https://github.com/ResurrectionRemix
- Kernel https://github.com/motoe5/android_kernel_motorola_msm8937 (twerk-X)
- vendor https://gitlab.com/the-flash/proprietary_vendor_motorola
greetings and enjoy
Thank you. I found it works great. Now we have one option other than LOS for nora. nora was not abandoned (lol)! Where is android_device_motorola_nora? I cannot find it.
Edit: What I noticed is about data connection. Phone and SMS seems okay but internet access via SIM does not work. Is it my personal issue?
Korin67 said:
Thank you. I found it works great. Now we have one option other than LOS for nora. nora was not abandoned (lol)! Where is android_device_motorola_nora? I cannot find it.
Edit: What I noticed is about data connection. Phone and SMS seems okay but internet access via SIM does not work. Is it my personal issue?
Click to expand...
Click to collapse
on the device tree search in google
I will confirm your problem with the mobile network later.
have patience
I flashed the ROM on my device today and most things seem to be working fine, inclidung mobile internet. However I'm having the exact same video/audio recording issues that I had with the LineageOS ROM for Nora. (see here https://forum.xda-developers.com/t/...-e5-nora-recovery-64bit.4235721/post-85658449 )
I have noticed both ROMs use the same kernel. Could that be the issue and does anybody know who to contact to make the issue known?
froggeroo said:
I flashed the ROM on my device today and most things seem to be working fine, inclidung mobile internet. However I'm having the exact same video/audio recording issues that I had with the LineageOS ROM for Nora. (see here https://forum.xda-developers.com/t/...-e5-nora-recovery-64bit.4235721/post-85658449 )
I have noticed both ROMs use the same kernel. Could that be the issue and does anybody know who to contact to make the issue known?
Click to expand...
Click to collapse
Did you try to change the camera application that comes by default for another?
G.Kart said:
on the device tree search in google
I will confirm your problem with the mobile network later.
have patience
Click to expand...
Click to collapse
works perfect for me
what you can do is check the APN
G.Kart said:
Did you try to change the camera application that comes by default for another?
Click to expand...
Click to collapse
Yes, I checked both the default app and used Open Camera. The problem is exactly the same in both cases. I have also found that the problem only seems to start appearing after you turn off the phone for the first time. Still worked fine on the very first boot up and generally I think the phone might have to be running for a while (15 mins or so) for the problem to appear.
I also took a quick look at the gitlab link for the vendor files and as the most recent commit it mentions "Nuke useless camera blobs". Any chance those blobs might not have been all that useless after all?
Edit: the gitlab also says something like "Lineage 17.1" at the top, so I assume those vendor files are also shared between both ROMs?
froggeroo said:
Yes, I checked both the default app and used Open Camera. The problem is exactly the same in both cases. I have also found that the problem only seems to start appearing after you turn off the phone for the first time. Still worked fine on the very first boot up and generally I think the phone might have to be running for a while (15 mins or so) for the problem to appear.
I also took a quick look at the gitlab link for the vendor files and as the most recent commit it mentions "Nuke useless camera blobs". Any chance those blobs might not have been all that useless after all?
Edit: the gitlab also says something like "Lineage 17.1" at the top, so I assume those vendor files are also shared between both ROMs?
Click to expand...
Click to collapse
Nora xt1944-4?
G.Kart said:
Nora xt1944-4?
Click to expand...
Click to collapse
My device is XT1944-2
@G.Kart or anyone else who might know: Do you think the missing camera blobs innthe vendor files might be a probable or at least possible explanation of the issue? If so, is it possible to just flash an older version of the vendor files on the current device or would that require a reset or recompiling of the whole ROM?
froggeroo said:
@G.Kart or anyone else who might know: Do you think the missing camera blobs innthe vendor files might be a probable or at least possible explanation of the issue? If so, is it possible to just flash an older version of the vendor files on the current device or would that require a reset or recompiling of the whole ROM?
Click to expand...
Click to collapse
try this camera
https://t.me/MotoE5Roms/77365
G.Kart said:
try this camera
https://t.me/MotoE5Roms/77365
Click to expand...
Click to collapse
This one produces completely broken videos (photos are fine). I can only find them in the gallery app (not in VLC) and play them in neither.
froggeroo said:
This one produces completely broken videos (photos are fine). I can only find them in the gallery app (not in VLC) and play them in neither.
Click to expand...
Click to collapse
The camera in devices where it usually fails with that camera is fixed but in your case I do not know what is happening
for other models the camera works so the blobs are not the problem (or at least I don't think so)
G.Kart said:
for other models the camera works so the blobs are not the problem (or at least I don't think so)
Click to expand...
Click to collapse
If I'm reading the gitlab correctly, it's only nora that seems to have some camera blobs removed. The commit is only mentioned in the nora folder.
If it's easy to put in the old vendor files, I'm willing to give it a shot either way, but I'm not sure what would be the correct way to do that.
froggeroo said:
If I'm reading the gitlab correctly, it's only nora that seems to have some camera blobs removed. The commit is only mentioned in the nora folder.
If it's easy to put in the old vendor files, I'm willing to give it a shot either way, but I'm not sure what would be the correct way to do that.
Click to expand...
Click to collapse
Need rebuild
That's unfortunate. I did manage to narrow down the problem quite a bit more though which might also help with reproducing it. The problem actually doesn't occur with the first reboot, as I first suspected, but rather it occurs after you turn off the screen/put the phone to sleep.
So immediately after you boot up the phone the camera still records video fine (sometimes the app crashes after reboot though and cannot be opened, another reboot fixes it). But after you put the phone to sleep by pressing the power button (probably also if it goes to sleep automatically) the discrepancy starts showing up. So if you put your phone to sleep for five minutes and record a two second video, the resulting video will be 5:02 with the sound at the beginning and video at the end. If you put the phone to sleep again, the video length of the next video increases by about the same amount.
So the video length = actual video length + (time phone has been asleep since last reboot - 10 seconds or so). If you only put the phone to sleep for a few seconds, the discrepancy doesn't start yet, it has to be asleep for ~10 seconds or more.
So if anyone has the same device, they can try reproducing it by booting up the phone, taking a 5 second video, putting the phone to sleep for a few mins and then taking another 5 second video. The second video should then be of excess length.
So my guess would be that either the audio recording and video recording functionalities use different variables for timekeeping in the first place (time active vs time turned on) or that putting the phone to sleep kills some sort of time keeping functionality (maybe to conserve battery?) that the audio recording relies on while leaving the video equivalent untouched or vice versa.
Additional information: This is the crash report I got when the camers app crashed on me before I even opened it the first time (usually doesn't happen). Not sure if it's related to the other bug or whether there's a pattern behind the crashing:
Hastebin: Send and Save Text or Code Snippets for Free | Toptal®
Hastebin is a free web-based pastebin service for storing and sharing text and code snippets with anyone. Get started now.
hastebin.com
These are some error reports I got when trying to record a video with "Simple Camera App" from.the F-Droid store. Also not sure if it's related because that app doesnt even work for taking pictures.
{
"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"
}
The default app, Open Camera and Focal all record photos and videos, but the videos all have the length/timekeeping problems. The app you that was linked here also crashed when trying to take a video.
froggeroo said:
That's unfortunate. I did manage to narrow down the problem quite a bit more though which might also help with reproducing it. The problem actually doesn't occur with the first reboot, as I first suspected, but rather it occurs after you turn off the screen/put the phone to sleep.
So immediately after you boot up the phone the camera still records video fine (sometimes the app crashes after reboot though and cannot be opened, another reboot fixes it). But after you put the phone to sleep by pressing the power button (probably also if it goes to sleep automatically) the discrepancy starts showing up. So if you put your phone to sleep for five minutes and record a two second video, the resulting video will be 5:02 with the sound at the beginning and video at the end. If you put the phone to sleep again, the video length of the next video increases by about the same amount.
So the video length = actual video length + (time phone has been asleep since last reboot - 10 seconds or so). If you only put the phone to sleep for a few seconds, the discrepancy doesn't start yet, it has to be asleep for ~10 seconds or more.
So if anyone has the same device, they can try reproducing it by booting up the phone, taking a 5 second video, putting the phone to sleep for a few mins and then taking another 5 second video. The second video should then be of excess length.
So my guess would be that either the audio recording and video recording functionalities use different variables for timekeeping in the first place (time active vs time turned on) or that putting the phone to sleep kills some sort of time keeping functionality (maybe to conserve battery?) that the audio recording relies on while leaving the video equivalent untouched or vice versa
Click to expand...
Click to collapse
try using other gapps
G.Kart said:
try using other gapps
Click to expand...
Click to collapse
Which apps specifically? Not sure I understand how that's supposed to change anything.
Gapps needed?
Related
GALAXY NEXUS PHONE MODS
This is all part of the Galaxy Nexus ToolKit but I have made a new Thread for people who may not have noticed it, people who didnt need the ToolKit but may find some of the Mods useful or just people who want to talk about the Phone Mods specifically.
FUNCTIONS OF THE PHONE MODS SECTION V1.4 [GSM + LTE][13TH MARCH 2012]
Change the Screen Density (DPI)
CWM Recovery, Only 1 No in the Confirmation Screen
Camera Sounds (Disable/Enable Camera Shutter, Video Camera Shutter, Focus)
Camera Enhancements (Increase Video Bitrate, Sound Bitrate, Photo Quality)
Change WiFi Scan Interval (Time between scanning for new Wifi Access Points)
Startup Boot Animation Screen (Disable/Enable which affects Boot Time)
Screen Colour Control (Change Gamma Offset and Colour Multiplier)
--------------------------------------------------------------
DOWNLOAD
The Phone Mods are part of the Galaxy Nexus ToolKit. You can download the latest version *HERE* (no need to install drivers if you already have adb/fastboot drivers installed) and select option 18 in the Main Menu to enter the Phone Mods Section.
{
"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"
}
--------------------------------------------------------------
USAGE
STOCK ROM users will need to enter the Mods Section via the Galaxy Nexus ToolKit as most functions need an insecure boot image which is set up from the Model Selection Screen of the ToolKit. If you are running a CUSTOM ROM (with insecure boot image) then you can run the ModsSection.exe directly if you wish.
ALL Mods Section functions require you to be booted into Android and connected to the PC via usb with adb/fastboot drivers installed. If you havent done this already then refer to the Galaxy Nexus ToolKit Thread for setup instructions.
The Galaxy Nexus ToolKit and Mods Section are very tightly integrated and so is impossible to seperate the 2 parts unless I want to cut out Stock Rom users (which I dont) so please dont ask if I can split them up. I could but its just not worth it.
Lastly if you have any ideas for functions that can be added to the Mods Section or just want to discuss a particular function then feel free.
--------------------------------------------------------------
*DISCLAIMER*
I take no responsibility for any fault or damage caused by any procedures within this guide. No warranties of any kind are given.
*reserved for future use*
Already used your tool kit to root, unlock, and flash recovery!!! Awesome work you've done, it's too easy Glad to see you made a separate thread for this, I agree it got kind of lost in the original thread.
Sent from my Galaxy Nexus using Tapatalk
Hmm, I like the idea of being able to disable the boot animation, and I'll give the camera improvements a go and report back.
I've always tried to beat something into my geeks when I'm teaching IT classes, and that's the idea of "Do it right, make it easy". You sir, have done a great job at putting together this toolkit in a way that makes things simple, and with great documentation. Nice work!
graymulligan said:
Hmm, I like the idea of being able to disable the boot animation, and I'll give the camera improvements a go and report back.
I've always tried to beat something into my geeks when I'm teaching IT classes, and that's the idea of "Do it right, make it easy". You sir, have done a great job at putting together this toolkit in a way that makes things simple, and with great documentation. Nice work!
Click to expand...
Click to collapse
Thank you im sure your geeks learn alot from you lol
Disabling the boot animation knocks about 5 seconds off the bootup time and there are a few Roms with not very desirable graphics lol.
Please do report back I always welcome any feedback and ideas for additions.
I get an error when trying to backup the xml file...Any ideas?
Looks great . You don't happen to have a unix version?
If anybody is having problems... Or if your using francos kernel you need to disable fast usb charge.... Hey thanks for your great work
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
MysticDeth said:
I get an error when trying to backup the xml file...Any ideas?
Click to expand...
Click to collapse
Are you using Franco kernel? Disable the fast usb charge.... Your good to go
MysticDeth said:
I get an error when trying to backup the xml file...Any ideas?
Click to expand...
Click to collapse
What Rom and kernel are you using?
Are you booted into Android and connected via usb cable before starting?
I dont know where the fast usb charge option is but as the previous user posted you can try to disable that and try again.
Also if you go back into the main ToolKit are you seeing the serial number under adb at the top?
Mark.
yyz71 said:
If anybody is having problems... Or if your using francos kernel you need to disable fast usb charge.... Hey thanks for your great work
---------- Post added at 02:58 PM ---------- Previous post was at 02:56 PM ----------
Are you using Franco kernel? Disable the fast usb charge.... Your good to go
Click to expand...
Click to collapse
I didn't disable fast usb charge but I did reboot and everything worked fine after the reboot
MysticDeth said:
I didn't disable fast usb charge but I did reboot and everything worked fine after the reboot
Click to expand...
Click to collapse
Glad it went well after the reboot
Mark.
io53 said:
Looks great . You don't happen to have a unix version?
Click to expand...
Click to collapse
I do want to have versions of the ToolKit for Mac and Linux if I can get some testers and/or people who can help me convert the scripts. Im guessing most of the scripts should work fine as they are just adb/fastboot commands but there may be differences with pauses and some search replace routines.
Do linux bash scripts work on unix?
Mark.
Wow.. that's more handy..
Thanks for the nee options being included in your tool..
What exactly does the camera enhancements option do?
Any news on the camera enhancement and weather it works?
bemymonkey said:
What exactly does the camera enhancements option do?
Click to expand...
Click to collapse
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)
frenccw said:
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)
Click to expand...
Click to collapse
I second this question, but on the other hand, we all have seen mskips dev work before this. A Nand backup/restore would solve everything, so don't fear a try..
bemymonkey said:
What exactly does the camera enhancements option do?
Click to expand...
Click to collapse
The enhancement does exactly what it states on the screen when you select option 4 in the phone mods section:
This mod focuses on the media_profiles.xml file in the /etc/ folder on your phone.
The x2 Quality Settings doubles the standard camcorder bitrate for 480P, 720P and 1080P [8M, 16M, 24M] as well as change the quality settings for the camera to 100, 85, 75 [from 95, 80, 70] and the memcap setting to 25000000.
The Medium Quality Settings push the camcorder bitrate up even more for 480P, 720P and 1080P [10M, 20M, 35M] as well as change the quality settings for the camera to 100, 85, 75 [from 95, 80, 70] and the memcap setting to 30000000.
The High Quality Settings push the camcorder bitrate up to the max for 480P, 720P and 1080P [14M, 30M, 50M] as well increase the Audio bitrate up to 128k and increase the Audio channels to 2. The duration setting has also been changed to 60 from 30 for the above formats. All the quality settings for the camera have been forced to 100 and the memcap setting has been pushed up to 40000000.
These 3 profiles are for testing and I hope you get improvements using them but if you want to you can customize either of them from the mods folder and push them back to your phone.
Click to expand...
Click to collapse
As for proof that the mod works I havent taken tests shots/videos with each mod but the stock bitrates for the camcorder are a bit low so increasing it can only benefit the quality of the captured image. Whether the highest setting is neccessary or not doesnt really matter as it is upto the end user to decide if they prefer it but I would definitely recommend applying at least the 2x setting .
frenccw said:
I also would like to know this. Very intriguing. Also, what are the chances of it screwing up the camera app? (Considering custom roms have modified versions)
Click to expand...
Click to collapse
I put a compulsory backup step in every mod section so that even on custom roms the original file can be saved to your computer before it is altered and pushed back if you dont like the changes. There is absolutely no chance of screwing up the camera app as only bitrates and quality settings are altered.
MuayThaiFighter8 said:
I second this question, but on the other hand, we all have seen mskips dev work before this. A Nand backup/restore would solve everything, so don't fear a try..
Click to expand...
Click to collapse
A NAND backup isnt needed as the file to be altered has to be backed up by the ToolKit in order to proceed so it can be easily and safely restored if the user wants to.
Mark.
Ah okay, so stills aren't affected at all?
bemymonkey said:
Ah okay, so stills aren't affected at all?
Click to expand...
Click to collapse
Does noone bother reading my posts properly lol
If you read my above post the camera quality (stills) is pushed up by pushing the modded settings.
The 2x and medium profiles pushes the 3 quality values of stills upto 100, 85 and 75 (instead of 95, 80, 70). The high quality profile pushes all 3 values upto 100 (meaning there is no compression in the images taken).
Mark.
Good news, everyone! CM 11 is running
So far, everything except ANT+ seems to be working, but I couldn't test all of it. So you be the judge. If you have any problems, fix them. Help each other, I might even try to help, but I don't have the time to fully maintain this build. Device trees and everything needed to build this will come shortly and I'm sure someone capable will take over maintenance, soon!
As with every CyanogenMod rom, you will need an unlocked bootloader and a custom recovery. Gapps are not included.
I am not responsible for any bricking or data loss or whatsoever!
Download: cm-11-20140313 (Updated Build!, md5: 1a5062071cde1c8a1d8d5d7466a0f445)
Changelog:
20140312: Initial Build
20140313: Sensors fixed
Known Issues:
Transitions lag some times
First Camera start takes a couple of seconds (Known bug on the Z1, too)
ANT+ isn't working
Massive thanks to Bumble-Bee and xkonni! I am somehow unable to link them as contributors, god knows why..
XDA:DevDB Information
Unofficial CM11, a ROM for the Sony Xperia Z1 Compact
Contributors
crytic, intervigil
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2014-03-12
Last Updated 2014-03-14
<>
ok, those are the repos this is built from:
https://github.com/xkonni/android_device_sony_amami
https://github.com/xkonni/android_kernel_sony_msm8974
+ CyanogenMod repos for honami
use extract files for proprietary stuff
have fun
AWESOME!
xkonni said:
ok, those are the repos this is built from:
https://github.com/xkonni/android_device_sony_amami
https://github.com/xkonni/android_kernel_sony_msm8974
+ CyanogenMod repos for honami
use extract files for proprietary stuff
have fun
Click to expand...
Click to collapse
Here we go! Thank you!
Does it have all the features from stock rom??
tania247260 said:
Does it have all the features from stock rom??
Click to expand...
Click to collapse
This rom has nothing to do with stock.. Apart from a couple of proprietary firmware files.
I'm testing the rom and will report back as soon as I find anything interesting. I'm really excited!
Yay! Great news!
(Shouldn't it go to Original Development section for Z1C? )
Sent from my D5503 using Tapatalk
Works great, but has a few bugs
First off, thank you so much for putting this together.
I'll be able to pull logs later when I get home, but quickly:
Animations run very slowly. I've disabled them for the time being.
I've had some issues waking from sleep. Will try to isolate.
The camera launches very slowly, but this is also the case on the Z1 CM11 build.
orrorin said:
First off, thank you so much for putting this together.
I'll be able to pull logs later when I get home, but quickly:
Animations run very slowly. I've disabled them for the time being.
I've had some issues waking from sleep. Will try to isolate.
The camera launches very slowly, but this is also the case on the Z1 CM11 build.
Click to expand...
Click to collapse
I've found the following issues so far:
Proximity sensor does not work (ANT+ related, I assume)
Photosphere does not show up at all, no matter what camera version you install. I have a 4.3 camera whose Photosphere worked fine on the stock rom. I tested others and none worked on CM 11
Yes, animations/transitions are slow in certain situations, but not always
I'm not sure the battery level is being measured correctly. Either this thing is amazingly more optimized or the reading is wrong. I'll be able to test that fully tomorrow when I start the day with a full charge
I'm really glad this came out. These issues are not gonna stop me from using the crap out of this rom! Thank you, OP and other contributors! :good:
orrorin said:
First off, thank you so much for putting this together.
I'll be able to pull logs later when I get home, but quickly:
Animations run very slowly. I've disabled them for the time being.
I've had some issues waking from sleep. Will try to isolate.
The camera launches very slowly, but this is also the case on the Z1 CM11 build.
Click to expand...
Click to collapse
Yeah they do some times for me, too. OpenGL etc are working perfectly, no idea why that happens so far. It's smooth most of the time though. Will try to debug
Never had that, could you try to replicate that error and produce logs?
It launched very slowly the first time, for me, too. But now its almost instantaneously
Gaúcho comedor said:
I've found the following issues so far:
Proximity sensor does not work (ANT+ related, I assume)
Photosphere does not show up at all, no matter what camera version you install. I have a 4.3 camera whose Photosphere worked fine on the stock rom. I tested others and none worked on CM 11
Yes, animations/transitions are slow in certain situations, but not always
I'm not sure the battery level is being measured correctly. Either this thing is amazingly more optimized or the reading is wrong. I'll be able to test that fully tomorrow when I start the day with a full charge
I'm really glad this came out. These issues are not gonna stop me from using the crap out of this rom! Thank you, OP and other contributors! :good:
Click to expand...
Click to collapse
Don't think its ANT+ related, but yeah, I can confirm that. Will debug later
Isn't Photosphere a Nexus exclusive feature? I always thought so. But then, I only used Nexus devices in the past..
Transitions, yeah, what I wrote earlier
For now, battery seems normal for me, it has been pretty amazing on stock, too. But I haven't gotten this ROM running nearly long enough to say if battery life is longer or not.
Thanks for the reports!
Awesome work thanks !
Poweramp and DSP manager crashes
Sent from my Xperia Z1 Compact using XDA Premium 4 mobile app
Sensors are fixed, so is ANT+ probably. As soon as I checked whether ANT really works or not, I'll upload another build.
crytic said:
Sensors are fixed, so is ANT+ probably. As soon as I checked whether ANT really works or not, I'll upload another build.
Click to expand...
Click to collapse
I'm downloading the new version now and will report later. Thank you again for your contribution. That's really amazing.
When I try to install this rom via Phils Recovery, then the installation always cancels with the message: This package is for "D5503, amami, anami" devices, this is a "honami". How can I install CM?
Hadschi92 said:
When I try to install this rom via Phils Recovery, then the installation always cancels with the message: This package is for "D5503, amami, anami" devices, this is a "honami". How can I install CM?
Click to expand...
Click to collapse
By using CWM recovery or by asking Phil to set the proper product name
Honami = Z1, anami = Z1c
crytic said:
By using CWM recovery or by asking Phil to set the proper product name
Honami = Z1, anami = Z1c
Click to expand...
Click to collapse
Problem solved, I installed wrong Recovery Version from Phil. I installed the version for Z1 instead of Z1C
Playing a little bit around with CM I found some things out:
1. When I charge my phone with magnetic cable, CM thinks my phone is in docking station. As effect the sound is disabled because the phone tries to route it through the docking station port.
2. In standby, camera app should be startet if camera button is pressed. There is only an option to turn on screen and to unlock phone with camera button. So two clicks on camera button are needed to start camera, which is uncomfortable.
3. On my motorola defy, cyanogenmod supported to save apps on the sd card. Is it possible to include this feature also in this cm version?
And as already mentioned:
Camera is slow and animations are laggy.
1. Well the charging pin should only be used on docks so I think that's normal.
2. Would need some modifications for that probably.
3. Motorola defy has an outdated OS of android... apps on sdcard has been removed since android 4.0 ice cream sandwich.
Hadschi92 said:
Playing a little bit around with CM I found some things out:
1. When I charge my phone with magnetic cable, CM thinks my phone is in docking station. As effect the sound is disabled because the phone tries to route it through the docking station port.
2. In standby, camera app should be startet if camera button is pressed. There is only an option to turn on screen and to unlock phone with camera button. So two clicks on camera button are needed to start camera, which is uncomfortable.
3. On my motorola defy, cyanogenmod supported to save apps on the sd card. Is it possible to include this feature also in this cm version?
And as already mentioned:
Camera is slow and animations are laggy.
Click to expand...
Click to collapse
Hadschi92 said:
Playing a little bit around with CM I found some things out:
1. When I charge my phone with magnetic cable, CM thinks my phone is in docking station. As effect the sound is disabled because the phone tries to route it through the docking station port.
2. In standby, camera app should be startet if camera button is pressed. There is only an option to turn on screen and to unlock phone with camera button. So two clicks on camera button are needed to start camera, which is uncomfortable.
3. On my motorola defy, cyanogenmod supported to save apps on the sd card. Is it possible to include this feature also in this cm version?
And as already mentioned:
Camera is slow and animations are laggy.
Click to expand...
Click to collapse
1. Yeah, originally the magnetic port was just intended for docking stations, so the behaviour is kind of wanted. Not sure if the Z1(c) actually is able to route audio through the port, so maybe this actually should be disabled. There definitely should be a quick fix to make this adjustable at least.
2. Same thing, should be an option for that in the future.
3. Apps2SD is not officially supported anymore. There are hacks afaik, but I won't do and support that.
Slow camera is a known bug, even for the Z1. As for the animations, I have no idea on how to debug them. Benchmarks and games suggest that OpenGL is working just fine. Any ideas anyone?
https://developers.google.com/glass/tools-downloads/system#factory_images said:
Warning: Rooting, unlocking, or flashing your Glass voids your warranty and can leave your device in an irrecoverable state. Proceed at your own risk.
Click to expand...
Click to collapse
This is the Android Open Source Project for Google Glass. The current version is 5.1.1 Lollipop. Thanks to the OMAP4-AOSP project, development for Glass has been rapid and stable. The blobs that are not provided by OMAP4-AOSP are pulled from XE22, and the XRX13B kernel is compiled from source.
This is not the OS you would expect to run on Glass. This is stock Android, and it is difficult to use. If you enjoy using your Glass on a day-to-day basis, please do not flash this ROM.
{
"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"
}
Why did you do this?
I wanted to create a base platform for developers, like myself, who like to experiment. We shouldn't be bound to the GDK.
I wanted to revive community interest in Google Glass. It is an incredibly interesting device that seemed to disappear before its peak.
Above all else, I just wanted to see if I could.
Installation Instructions
Your Glass will be wiped if you follow these instructions.
1) Download and extract the zip containing the boot.img and system.img files:
aosp_glass-1_5.1.1_042016.zip
MD5: 595c4e0b50fa191f42eb5609cfbf92fd
2) Boot Glass into fastboot mode:
From Glass, enter the Settings menu.
Scroll to the Device Info card and select it.
Scroll to the "Turn on debug" card and select it.
Once debugging is enabled, connect Glass to your computer and enter:
Code:
$ adb reboot-bootloader
https://developers.google.com/glass/tools-downloads/system#factory_images said:
You can also enter fastboot mode by holding down the camera button, pressing the power button (Glass must be off before doing this), and waiting about 10-15 seconds. Glass does not indicate that it is in fastboot mode (display is off), but you can run fastboot devices to check.
Click to expand...
Click to collapse
3) If you have not already, unlock your Glass:
Code:
$ fastboot oem unlock
4)
Code:
$ fastboot flash system system.img
$ fastboot flash boot boot.img
$ fastboot erase cache
$ fastboot erase userdata
$ fastboot reboot
The first boot may take some time as partitions are created and firmware versions are checked. You may also experience a reboot during the initial boot. To revert back to the stock Glass ROM, simply follow the instructions at https://developers.google.com/glass/tools-downloads/system#factory_images.
Working:
WiFi
Bluetooth pairing
GPS
Touchpad
Audio (kind of)
Camera (see below)
Known Issues:
Audio currently outputs either the left or right signal
Bluetooth connections cannot be made to various devices
Backlight control does not work
Powered off charging indicator is flakey
Camera gamma is sketchy in low light
Screenshots are glitchy
You tell me
Tips and Tricks:
Enable "Show touches" in the Developer options to navigate easier
Use ADB input commands for text or DPAD input: see http://stackoverflow.com/questions/7789826/adb-shell-input-events#answer-8483797
XDA:DevDB Information
AOSP for Google Glass, ROM for the Google Glass
Contributors
jtxdriggers, http://omap4-aosp.github.io/
Source Code: https://github.com/justindriggers/android_device_glass_glass-1
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: AOSP
Version Information
Status: Testing
Created 2016-04-11
Last Updated 2016-04-20
Awesome!
Thank you! That's awesome! I'll Flash it later this day
[edit]
installed it and its working I have also installed the pulled XE7 APKs from zhuowei . So far it is working. A real custom rom for Glass, with an easy to use launcher and glass-friendly apps would be fantastic. I think your Work is a perfect base for it. I am really looking forward on upcoming developments. Thank you again!
fuekiin said:
A real custom rom for Glass, with an easy to use launcher and glass-friendly apps would be fantastic. I think your Work is a perfect base for it. I am really looking forward on upcoming developments. Thank you again!
Click to expand...
Click to collapse
That's the long-term goal. Hopefully we can focus on getting Marshmallow working first, then we can start work on a new application layer. I am glad to hear that it's working for you. If you don't mind me asking, which version of Glass do you have (1GB or 2GB)? I personally have the 1GB model but I'd like to make sure the 2GB model works as well.
jtxdriggers said:
That's the long-term goal. Hopefully we can focus on getting Marshmallow working first, then we can start work on a new application layer. I am glad to hear that it's working for you. If you don't mind me asking, which version of Glass do you have (1GB or 2GB)? I personally have the 1GB model but I'd like to make sure the 2GB model works as well.
Click to expand...
Click to collapse
It's the newer Version with 2GB of RAM :good:
Where are you tracking bugs? Github?
fuekiin said:
It's the newer Version with 2GB of RAM :good:
Click to expand...
Click to collapse
Excellent!
fuekiin said:
Where are you tracking bugs? Github?
Click to expand...
Click to collapse
Report them in this thread for now. If this actually gains any popularity then perhaps I'll open an issue tracker.
Glad to see you've picked your glass up again. Does this rom support mouse functionality? If so it might be just what I am looking for. I will test this out later and let you know what I find.
exseus said:
Glad to see you've picked your glass up again. Does this rom support mouse functionality? If so it might be just what I am looking for. I will test this out later and let you know what I find.
Click to expand...
Click to collapse
Honestly not sure, let me know if it works!
jtxdriggers said:
Honestly not sure, let me know if it works!
Click to expand...
Click to collapse
For me it isn't working with my BT mouse.
Sent from my Nexus 6 using XDA-Developers mobile app
fuekiin said:
For me it isn't working with my BT mouse.
Sent from my Nexus 6 using XDA-Developers mobile app
Click to expand...
Click to collapse
Do you still get a cursor and all that? That is a shame.
fuekiin said:
For me it isn't working with my BT mouse.
Click to expand...
Click to collapse
That's disappointing. I'll have to go grab one and see what I can do. It may be a limitation of the bluetooth controller on the device.
jtxdriggers said:
That's disappointing. I'll have to go grab one and see what I can do. It may be a limitation of the bluetooth controller on the device.
Click to expand...
Click to collapse
Tomorrow i will maybe do some more testing. Also with an wired Mouse.
Beside this Problem, have you thought about mirroring the touch pad? For me it's very confusing right now [emoji1]
Sent from my Nexus 6 using XDA-Developers mobile app
fuekiin said:
Tomorrow i will maybe do some more testing. Also with an wired Mouse.
Beside this Problem, have you thought about mirroring the touch pad? For me it's very confusing right now [emoji1]
Click to expand...
Click to collapse
It makes sense as it is to me. Have you tried enabling "Show touches" in the Input section of the Developer options?
jtxdriggers said:
It makes sense as it is to me. Have you tried enabling "Show touches" in the Input section of the Developer options?
Click to expand...
Click to collapse
Yeah, it's enabled [emoji106]
Do you see any possibility to get Android Wear working, like biktor_gj did it for the gear 2?
fuekiin said:
Do you see any possibility to get Android Wear working, like biktor_gj did it for the gear 2?
Click to expand...
Click to collapse
Unfortunately it's still too early to tell. I got 5.1.1 "booting" last night (I use that term loosely, as all that really works is ADB), so I'd say there's a chance. But honestly, I don't know enough about Android Wear (yet) to say anything confidently. We'll see!
Forgive my ignorance, but will this rom allow for installing regular android apps on the glass? What are the advantages of having this custom rom? Also where can I donate?
kevkid said:
Forgive my ignorance, but will this rom allow for installing regular android apps on the glass? What are the advantages of having this custom rom? Also where can I donate?
Click to expand...
Click to collapse
That is correct, I've had reports of people installing GApps successfully and everything - just be aware that using the device is pretty difficult. Not really the "at a glance" mentality that Google was going for.
Long term, I'm looking to get Lollipop and Marshmallow working, and eventually develop a Glass-friendly UI on top of those based off of what the community thinks Glass should have been. Only a handful of people seem to be interested, but it's a really great side project for me.
That said, I'm not currently accepting donations. If the cost of my build box gets too high then I may reconsider, but I honestly don't want people investing in something that I actually have very little time to work on.
jtxdriggers said:
That is correct, I've had reports of people installing GApps successfully and everything - just be aware that using the device is pretty difficult. Not really the "at a glance" mentality that Google was going for.
Long term, I'm looking to get Lollipop and Marshmallow working, and eventually develop a Glass-friendly UI on top of those based off of what the community thinks Glass should have been. Only a handful of people seem to be interested, but it's a really great side project for me.
That said, I'm not currently accepting donations. If the cost of my build box gets too high then I may reconsider, but I honestly don't want people investing in something that I actually have very little time to work on.
Click to expand...
Click to collapse
I believe you have opened the flood gates. It may reinvigorate the community and get some great stuff out there. Thanks!
kevkid said:
I believe you have opened the flood gates. It may reinvigorate the community and get some great stuff out there. Thanks!
Click to expand...
Click to collapse
I certainly hope so! Show me something cool!
The first Lollipop build has been uploaded and the OP has been updated to reflect the changes. During development, I stumbled upon a project whose focus is to maintain AOSP for OMAP4 CPUs (which Glass happens to use). Coincidentally, their development started only a few months ago, and is ready for us to use! I commend the developers of OMAP4-AOSP - without them, our progress would take much longer.
The newly uploaded image is based on their project. Don't worry, it's still very much AOSP. Up next - Marshmallow.
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Edit:
Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?
Sources: Android Source
0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
Yes... This is the case on every device and every custom rom.. We are missing the after processing that OOS does.. So that is why we do not get the same quality..
Puddi_Puddin said:
Yes... This is the case on every device and every custom rom.. We are missing the after processing that OOS does.. So that is why we do not get the same quality..
Click to expand...
Click to collapse
Yes, that's what I'm asking. Why are we not able to produce same post processing that oos does?
0xelectron said:
Yes, that's what I'm asking. Why are we not able to produce same post processing that oos does?
Click to expand...
Click to collapse
Maybe because it is a **** ton off work? Or noone has the knowledge?
Puddi_Puddin said:
Maybe because it is a **** ton off work? Or noone has the knowledge?
Click to expand...
Click to collapse
Isn't developing custom roms ton of work too?
P. S. Not trying to argue, just curious.
0xelectron said:
Isn't developing custom roms ton of work too?
P. S. Not trying to argue, just curious.
Click to expand...
Click to collapse
Yes.. Maybe a proper after processing is more work? I have no clue how you need to do those things.. But if it was easy I'm pretty sure someone would've done it already.
0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.
Iqbal Ansari said:
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.
Click to expand...
Click to collapse
Was not the case for the OnePlus One, all Nexus devices and the Pixel.
Even though they all use closedsource-postprocessing, all it takes is to install the correct camera app and your are good to go on custom-roms.
It only depends on how the OEM implements it. OnePlus, as a so called "community friendly" company, decided to link their postprocessing not only to their camera app, but also to their own OxygenOS framework,
which is completely against the community.
This makes it harder to use it on custom-roms, as the framework needs to be modified specifically for each rom.
Why? They say the camera+postprocessing is supposed to be quicker this way.
Maybe they are right (for their own implementation), maybe they don't know better (probably, seeing other shenanigans they pull on OOS).
Iqbal Ansari said:
This is the case for every custom rom and for every phone.
Maybe because the camera code is not open source and companies do not provide them to the dev community.
Click to expand...
Click to collapse
I get that they want protect their camera code to stay ahead in the game. But, I still don't understand why, we(community) are missing that, we are not able to produce the same quality as theirs. I think either its too hard, or, maybe we don't have required information about the camera module or something like that.
AcmE85 said:
Was not the case for the OnePlus One, all Nexus devices and the Pixel.
Even though they all use closedsource-postprocessing, all it takes is to install the correct camera app and your are good to go on custom-roms.
It only depends on how the OEM implements it. OnePlus, as a so called "community friendly" company, decided to link their postprocessing not only to their camera app, but also to their own OxygenOS framework,
which is completely against the community.
This makes it harder to use it on custom-roms, as the framework needs to be modified specifically for each rom.
Why? They say the camera+postprocessing is supposed to be quicker this way.
Maybe they are right (for their own implementation), maybe they don't know better (probably, seeing other shenanigans they pull on OOS).
Click to expand...
Click to collapse
Ok, it's difficult to port or implement their camera app in custom rom. But, why are we (community) not able to utilize the camera module as them? I mean they have great post processing, fast capture times, 60fps videos, etc. Why we are not able to implement those features? Are we missing something?
0xelectron said:
Ok, it's difficult to port or implement their camera app in custom rom. But, why are we (community) not able to utilize the camera module as them? I mean they have great post processing, fast capture times, 60fps videos, etc. Why we are not able to implement those features? Are we missing something?
Click to expand...
Click to collapse
You quoted the reason, what more do you need?
LineageOS uses the exact same drivers and system files for the camera which can be found in OxygenOS.
It is missing the links to the postprocessing which have to be integrated into the framework.
There is no documentation for this by OnePlus, so this is a painful job.
We have a port for the camera app which somehow provides similar or at least nearly the same quality:
https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
If someone can give you a more detailed explanation it is most definitely @siankatabg
0xelectron said:
I don't understand why are we not able to produce the same post processing capabilities as oneplus? Are we missing something? If anyone can explain, I'll be really thankful!
Click to expand...
Click to collapse
Do you have an example of aosp vs stock processing. I think it maybe possible if you could show me the difference I'd know where to start
Sent from my NX503A using XDA Free mobile app
Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?
defcomg said:
Do you have an example of aosp vs stock processing. I think it maybe possible if you could show me the difference I'd know where to start
Sent from my NX503A using XDA Free mobile app
Click to expand...
Click to collapse
I don't have examples currently, but, I've noticed that the post processing of aosp is generally inferior compared to stock. Also, it doesn't have features such as 60fps video recording and proper EIS/OIS.
AcmE85 said:
You quoted the reason, what more do you need?
LineageOS uses the exact same drivers and system files for the camera which can be found in OxygenOS.
It is missing the links to the postprocessing which have to be integrated into the framework.
There is no documentation for this by OnePlus, so this is a painful job.
We have a port for the camera app which somehow provides similar or at least nearly the same quality:
https://forum.xda-developers.com/oneplus-3/themes/port-oxygenos-stock-camera-cm-t3451721
If someone can give you a more detailed explanation it is most definitely @siankatabg
Click to expand...
Click to collapse
I think I'm not explaining myself properly. What I'm trying to ask is that why the the quality/features of the the camera in custom roms a little inferior compared to stock OOS? I did some digging and found out that most of the capabilities are included in the hal api, and it's implementation, I think is provided by Oneplus. I can be totally wrong (correct me, if I'm).
0xelectron said:
Ok! So, I did some digging and (anyone correct me If I'm wrong) here's the general flow of camera workings. Camera Application --> HAL(Hardware Application Layer) API --> Kernel --> Drivers --> Hardware Module. Now, "only Interface" for HAL is provided by Android, but each manufacturer has to implement this interface. So, Doesn't Oneplus provide us with the hal implementation? if, so, doesn't it include the post processing algorithms and methods already? I still am very confused. @siankatabg Can you please explain?
Click to expand...
Click to collapse
Yes The flow is Camera App > Android Java Framework > Android Framework Native (libcamera_client/service) | libhardware loads the hal > hal camera.msm8***.so that uses libmmcamera_interface to hook up with the vendor libs via MCT liboemcamera/libmmcamera_mct.so > libmmcamera2_sensor_modules.so > libmmcamera_imx298.so > loads calibration via chromatix as well as eeprom
what weird about one plus they seem to have multiple chromatix blobs for diff camera modes my theory the problem with calibration lies here because it shouldn't matter weather the rom is aosp or stock, the camera calibration should be same unless the behavior is changed on purpose its the way its worked with qualcomm devices
thats why i asked for a comparison between aosp and stock so i could see if say the noise reduction was heavy in aosp then we would know to look at the chromatix cpp files ive mapped the chromatix cpp hex offsets on hex workshop so you can copy entire calibation blocks from for example clear shot cpp chromatix libs. hell you could copy noise calibration from any device with same chromatix version ie lg v20 / mi5.
if its overexposure/underexposure dropped fps etc the the chromatix 3a lib is what you need to be looking at
defcomg said:
Yes The flow is Camera App > Android Java Framework > Android Framework Native (libcamera_client/service) | libhardware loads the hal > hal camera.msm8***.so that uses libmmcamera_interface to hook up with the vendor libs via MCT liboemcamera/libmmcamera_mct.so > libmmcamera2_sensor_modules.so > libmmcamera_imx298.so > loads calibration via chromatix as well as eeprom
what weird about one plus they seem to have multiple chromatix blobs for diff camera modes my theory the problem with calibration lies here because it shouldn't matter weather the rom is aosp or stock, the camera calibration should be same unless the behavior is changed on purpose its the way its worked with qualcomm devices
thats why i asked for a comparison between aosp and stock so i could see if say the noise reduction was heavy in aosp then we would know to look at the chromatix cpp files ive mapped the chromatix cpp hex offsets on hex workshop so you can copy entire calibation blocks from for example clear shot cpp chromatix libs. hell you could copy noise calibration from any device with same chromatix version ie lg v20 / mi5.
if its overexposure/underexposure dropped fps etc the the chromatix 3a lib is what you need to be looking at
Click to expand...
Click to collapse
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!
0xelectron said:
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!
Click to expand...
Click to collapse
Hex Workshop CPP Bookmark
{
"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"
}
attached the offset bookmark as well as the chromatix source if youd like to check it out
0xelectron said:
Whoa! That's a lot of information. I've to study more. I'll definitely look into it. Thanks!
Click to expand...
Click to collapse
You asked a question to which someone kindly gave you a simple answer and you weren't satisfied.... Then someone gave you a complex answer and you didn't understand...Smh and Lmfao!!
Sent from my ONEPLUS A3000 using Tapatalk
fcisco13 said:
You asked a question to which someone kindly gave you a simple answer and you weren't satisfied.... Then someone gave you a complex answer and you didn't understand...Smh and Lmfao!!
Click to expand...
Click to collapse
You're right. I didn't understand. But, that's a good thing. I'm learning. I'm digging. I'm doing something I would've not done, normally. For example, the first simple answer didn't satisfy me, so, I started learning the inner workings of the android camera. Second complex answer gave me more in-depth knowledge then I leaned, and it is making me study more to understand. So, say what you want, but, I'm thankful for both the answers. Thank you everyone!
This is not my creation, but it took me a long time to find this and it actually works, so I am going to post a link to the other XDA thread to make it easy to locate.
https://www.google.ca/amp/s/forum.x...neageos-15-1-note-5-android-8-1-t3737405/amp/
My WiFi and calls work. The camera was glitchy but if that bothers you, remove it with a system app uninstaller and replace it with one you prefer. I also did not care for lawnchair or trebuchet launcher so I replaced them with pixel launcher(also here on XDA).
I have not noticed any other bugs so far in the past 24 hours I've been using the ROM. Make sure you flash all the zips, there are a couple of zips with the ROM that fix things. Also take a moment to give the developer a thank you, its a fully functional oreo on s6 edge +!
Thanks for reading, enjoy the upgrade to Oreo
Zenlte moddified lineage 15.1/nexusOS for s6e+ done by myself. I did some stuff to get the camera going a bit better. Lower res to 1080p. The full thread is in the s6e+ t mobile forum under android development the original rom and kernel are in the link above at the top.
https://mega.nz/#F!aaIDmT5D!FG9QpMYPcNCjlDiIkGCX4g
godkingofcanada said:
This is not my creation, but it took me a long time to find this and it actually works, so I am going to post a link to the other XDA thread to make it easy to locate.
https://www.google.ca/amp/s/forum.x...neageos-15-1-note-5-android-8-1-t3737405/amp/
My WiFi and calls work. The camera was glitchy but if that bothers you, remove it with a system app uninstaller and replace it with one you prefer. I also did not care for lawnchair or trebuchet launcher so I replaced them with pixel launcher(also here on XDA).
I have not noticed any other bugs so far in the past 24 hours I've been using the ROM. Make sure you flash all the zips, there are a couple of zips with the ROM that fix things. Also take a moment to give the developer a thank you, its a fully functional nougat on s6 edge +!
Thanks for reading, enjoy the upgrade to Oreo
Click to expand...
Click to collapse
Forgot to mention pixel has an app you can get that allows you to install icon packs and change names of apps.
A peek at the about.
That rom is still not stable enough.
El Solido said:
That rom is still not stable enough.
Click to expand...
Click to collapse
I haven't had anything crash or anything serious go wrong yet.
godkingofcanada said:
I haven't had anything crash or anything serious go wrong yet.
Click to expand...
Click to collapse
Well i tried it, rom was little laggy for me, camera is unstable, high definition videos lags, batter life is bad and other minor things, but can be used no crashes or anything
El Solido said:
Well i tried it, rom was little laggy for me, camera is unstable, high definition videos lags, batter life is bad and other minor things, but can be used no crashes or anything
Click to expand...
Click to collapse
I fixed the battery life with kernel auditor and replaced the video/camera with s different one. Then I removed the init.d and reinstalled it to get proper access, also used a different super user then the one provided. I've got xposed running with busybox and amplify. I'm not a dev but I am in college studying computer programming. My take on this ROM is if you know your way around your droid well and can invest some time any bug in it is fixable. The battery could be improved more by using a different kernel or editing the one contained in this ROM to add more governor settings and tweeks. I reached out to the ROM developer on that subject, with any luck they will look into it.
godkingofcanada said:
I fixed the battery life with kernel auditor and replaced the video/camera with s different one. Then I removed the init.d and reinstalled it to get proper access, also used a different super user then the one provided. I've got xposed running with busybox and amplify. I'm not a dev but I am in college studying computer programming. My take on this ROM is if you know your way around your droid well and can invest some time any bug in it is fixable. The battery could be improved more by using a different kernel or editing the one contained in this ROM to add more governor settings and tweeks. I reached out to the ROM developer on that subject, with any luck they will look into it.
Click to expand...
Click to collapse
I know i tried other camera again unstable camera, sometimes works without issues, sometimes its ****, i got also xposed running, bluetooth music play was little stuttering, and you cant fix high definition lag yet, so not worth for me
El Solido said:
I know i tried other camera again unstable camera, sometimes works without issues, sometimes its ****, i got also xposed running, bluetooth music play was little stuttering, and you cant fix high definition lag yet, so not worth for me
Click to expand...
Click to collapse
Mine stutters a bit but not too bad. I removed the camera and then flashed the s6 edge camera instead of the s6 and it improved a fair bit. Luckily I do not use Bluetooth audio so in my case only recording videos has a bug still and its not a deal breaker as I walk around with my s6 e+ as my surfing and calls device and my s7 is my music and gaming device. So for me I just record with s7 if I need video while I try to fix it. Once I figure it out I will share the details.
godkingofcanada said:
Mine stutters a bit but not too bad. I removed the camera and then flashed the s6 edge camera instead of the s6 and it improved a fair bit. Luckily I do not use Bluetooth audio so in my case only recording videos has a bug still and its not a deal breaker as I walk around with my s6 e+ as my surfing and calls device and my s7 is my music and gaming device. So for me I just record with s7 if I need video while I try to fix it. Once I figure it out I will share the details.
Click to expand...
Click to collapse
If its your second device then it can be used, but as primary device rom is not stable enough.
Error logs for camera.
Logs
I'm not an expert but this seems to be a Java runtime error. I have to really get down to the core and look now. The only time I encounter an error with parsing an int is when the syntax is wrong, like trying to parse an invalid type to an int. I'm starting to believe I'm going to need to remove all traces of the camera from the droid 100% and try flashing zips from different models until it works. Or sit down with eclipse and go through line by line and solve the exceptions Java is throwing.
El Solido said:
If its your second device then it can be used, but as primary device rom is not stable enough.
Click to expand...
Click to collapse
I got HD working for photos and videos but now the video frame freezes like its a photo and only audio records. Argh
OK I got it. If you edit the settings in the native app and drop video recording from 4k to 1080 it improves a lot. And open camera from the play store looks / sounds a bit better for video. I can now record videos in HD and its not choppy or laggy. VoIP is also working. Besides the Bluetooth issue that you mentioned which I can not test to troubleshoot I don't know of any remaining issues. Have you tried removing Bluetooth drives and files reinstalling it?
Bluetooth-audio doesn't work on my SM-G928F. NFC, WiFi-Direct and AndroidBeam are also not working.
DGB100 said:
Bluetooth-audio doesn't work on my SM-G928F. NFC, WiFi-Direct and AndroidBeam are also not working.
Click to expand...
Click to collapse
Yeah because you install remove nfc zip so ofcourse, and who use nfc anyway
DGB100 said:
Bluetooth-audio doesn't work on my SM-G928F. NFC, WiFi-Direct and AndroidBeam are also not working.
Click to expand...
Click to collapse
Have you tried not removing the NFC and seeing if it boots?
So the pre installed camera works on and off due to runtime errors and conflicts stemming from Exynos camera3. The files are named camera 2 but logcat shows camera 3. I tried cyanogen but I get the error that it can't find media recorder. I'm going to try installing media recorder and seeing if it works with the cyanogen camera. Fingers crossed
El Solido said:
If its your second device then it can be used, but as primary device rom is not stable enough.
Click to expand...
Click to collapse
I'm hearing camera 2 API is not fully supported on the s6 devices. This could be the issue. However if I am correct that sucks. Because I can not just swap API. I would have to talk to the dev and he or I would have to reduild the ROM using media recorder API if that's possible in Oreo. I assume it would still work despite being depreciated by Google and it's java.