I am opening this thread to get as much help as possible, after posting on various porting groups on facebook and on various forums I hope the thread appears on Google.
This is an EMUI 3.1 rom based on lollipop 5.1, I have been trying to cross port it since it was released.
It can be ported for chipset: mt6580, mt6592. Mt6582 ( 32 bit mtk devices with the same GPU).
Device Huawei Y5II 3G
Android version: 5.1 lollipop
kernel version: 3.10.72
chipset mt6582
Download link:
https://mega.nz/#!OxgyADYa!huTy9bppk4EvCcJNFoqr63CCpaxXXdc7x2roXnBZgME
The problem is that the rom almost booted but it keeps bootlooping, it never pass the boot animation, I think audio prevents it from booting.
Here is the logcat:
Code:
AudioPolicyService not published, waiting...
AudioFilger not published, waiting...
Waiting for service media.audio_policy...
Waiting for service media.audio_flinger...
Also those errors apperas in logcat:
HWDrmDialogsService errorListener = [email protected]
Error processing intial volume state: volume == null
-----------------------------------
Full logcat:
http://forum.xda-developers.com/attachment.php?attachmentid=3926437&d=1478296595
I ported EMUI 3.0 from Y3II chipset mt6582, and it booted, but is is buggy due to low DPI and has a major issue which is I can't receive sms.
Update:
Progress in cross porting Huawei Y5 II rom:
I have successfully booted rom from Y5 II on my hot 2.
Fixed bootloop due to audio...
But there is a serious problem, and I can't find the reason for it; systemUI and on screen buttons never appear and after first boot if you rebooted the rom it will show black screen.
It was hard to test stuff on this rom, but I used my OTG keyboard to navigate and tested camera, audio, video, ril by calling my phone from another phone and they were working.
Logcat shows nothing related to the issue.
What is different in this rom from my previous cross-ported rom from Y6 pro
http://forum.xda-developers.com/hot-2/development/rom-emui-3-1-lite-t3517681/page1
is that it is full EMUI 3.1 and not a lite version.
Screen shots for the progress:
Everything is working, like ril, audio, video, camera, GPS, Bluetooth, wifi... Etc
However...
There is a serious bug, it seems to be related to GPU (Graphics) where SystemUI and navigation bar do not appear, there are graphic glitches in Huawei home launcher causing it to force close and after reboot a black screen might appear so you can see nothing on the rom except power menu and when someone calls.
Unfortunately, I couldn't find a fix
The rom is very nice and has an awesome sound and pretty good features.
Fixed all major issues by myself, it is really when you want to get things done you should depend on yourself
For reference, if any rom porter is stuck on a similar problem and found this
1- bootloop due to audio flinger and other media doesn't work - fix in drm
2- SystemUI and navigation bar - fix in xml folder (etc/xml)
3- Black screen issue caused by themes - reapply default theme with magazine before you reboot and after first boot.
uploading rom soon
Regards
Great work bro, I wish I was still using the device.
waiting
Mysteryagr said:
I am opening this thread to get as much help as possible, after posting on various porting groups on facebook and on various forums I hope the thread appears on Google.
This is an EMUI 3.1 rom based on lollipop 5.1, I have been trying to cross port it since it was released.
It can be ported for chipset: mt6580, mt6592. Mt6582 ( 32 bit mtk devices with the same GPU).
Device Huawei Y5II 3G
Android version: 5.1 lollipop
kernel version: 3.10.72
chipset mt6582
Download link:
https://mega.nz/#!OxgyADYa!huTy9bppk4EvCcJNFoqr63CCpaxXXdc7x2roXnBZgME
The problem is that the rom almost booted but it keeps bootlooping, it never pass the boot animation, I think audio prevents it from booting.
Here is the logcat:
Code:
AudioPolicyService not published, waiting...
AudioFilger not published, waiting...
Waiting for service media.audio_policy...
Waiting for service media.audio_flinger...
Also those errors apperas in logcat:
HWDrmDialogsService errorListener = [email protected]
Error processing intial volume state: volume == null
-----------------------------------
Full logcat:
http://forum.xda-developers.com/attachment.php?attachmentid=3926437&d=1478296595
I ported EMUI 3.0 from Y3II chipset mt6582, and it booted, but is is buggy due to low DPI and has a major issue which is I can't receive sms.
Click to expand...
Click to collapse
Hi. Can we port this for honor 3c Mt6582 with different kernel?our kernel version is 3.4.x
@hatefkm
Probably no due to selinux changes in stock kernel (unless you have a custom kernel)
Mysteryagr said:
@hatefkm
Probably no due to selinux changes in stock kernel (unless you have a custom kernel)
Click to expand...
Click to collapse
thanks for your answer
Any possibility of nougat
Got this EMUI V3 MT6592 but always bootloop when I port kernel V3.7 hoping on using ur fix method if it will help me boot
Mysteryagr said:
Here is the logcat:
Code:
AudioPolicyService not published, waiting...
AudioFilger not published, waiting...
Waiting for service media.audio_policy...
Waiting for service media.audio_flinger...
Also those errors apperas in logcat:
HWDrmDialogsService errorListener = [email protected]
Error processing intial volume state: volume == null
Click to expand...
Click to collapse
I cross porting firmware and I have this same problem
please help (((
Related
What is NamelessROM ?
Simple - NamelessRom is opportunity.
An opportunity to have a voice to the development team of the after-market firmware that you run on your device.
The main goal of NamelessRom is to provide quality development for android devices, phones and tablets alike.
NamelessRom developers are available nearly 24/7 and respond to bug reports and feature requests almost instantly.
This availability will allow you, the end-user, to have direct input into exactly what features and functions are included on the firmware that YOU run.
NamelessRom == endless possibilities. Unless you have an iPhone, then you're out of luck.
Click to expand...
Click to collapse
This is an unofficial port of NamelessRom for the Samsung Galaxy Music
Device Tree: https://github.com/Alonso1398/android_device_samsung_ivoryss/tree/nameless-4.4
Kernel Source: https://github.com/Alonso1398/muZic_kernel_ivoryss/tree/cm-11.0
Vendor Files: https://github.com/Alonso1398/proprietary_vendor_samsung_ivoryss
Patches:
Patch to hardware/broadcom/libbt for bluetooth to work: https://gist.github.com/pawitp/7891380.
Patch to frameworks/native to workaround hwc issues: https://gist.github.com/pawitp/7891444 and https://github.com/PAC-man/android_frameworks_native/commit/0c81fda74f6e7f9dc5f48bd00e4dbeaef12fdbc2.
Patch to frameworks/av to fix audio/video issues: https://gist.github.com/pawitp/7945188
Patch to hardware/libhardware/include/hardware/audio.h for microphone to work: https://gist.github.com/dhinesh77/7206ec7900bee32e4c51/revisions
Dual SIM Patches: https://gist.github.com/pawitp/9433442
Credits
Dhinesh77
Pawitp
NamelessRom Team
CyanogenMod Team
XDA Forum
Requirements
-Updated CWM 6.0.5.0
-Have Stock 4.1 or CM
-Make sure the device's name of build.prop matches the one in the updater-cript
Installation
-Make a backup
-Wipe data/factory reset
-Install the rom
-Install gapps
Bugs/What's not working?
-Multisim (don't try to enable it or it will cause problems)
-Some games like Clash of Clans will close itself when opening
Download Links
Dropbox: https://www.dropbox.com/s/dpiaaa0qsfpm9zh/Nameless 4.4 ivoryss RC 4.zip?dl=0
MEGA: https://mega.co.nz/#!wNxnmRpJ!NY_b9-9ulG9UO2FZ9feZTgHF73bvVCyIMuCa9hWzvQg
Changelog
RC 4
-Correct some pawitp's patches (fixes black screen during rotation)
-Some ramdisk cleaning (remove stock's zram)
-Use prebuilt older camera without scene change bug
-Correct CIFS on kernel, now itn is used as a module.
-Remove torch apk and screencast apk (since it doesn't work) and some blobs
RC 3
-Fix Wi-Fi Tethering
-Add Wi-Fi direct
-Update nameless source?
RC 2
-Fixed manual network search
-Enabled low ram mode but keeped transparent status bar
-Added soft reboot option on advanced reboot menu
-More compressed kernel
RC 1
-Add flag to make dhinesh patch to work
*It fixes audio and video recording
-Add features to kernel
*KSM (can be enabled on Device Control extras)
*CIFS...
Beta 1
-Initial release
Hello, I bringed this rom because it had many interesting features and was based on cm 11 so could be easy to port, however I saw about another rom named AOSB that also caught my attention so I don't know what to do Will add a poll
Also I'm not 100% sure that I can bring AOSB but it is based on CM and the device tree structure is pretty similar so there could be high chances
New ROM??
How good is this ROM??
Watching it's demo on youtube..
Still need your opinion..
Which GAPPS to install??
edit:
Installed Nameless ROM..
It is awesome!!
Although here are some reports from Music Duos Variant
Not Working
*Bluetooth
Needed Stuff
*Radio App??
aqiben10 said:
How good is this ROM??
Watching it's demo on youtube..
Still need your opinion..
Which GAPPS to install??
edit:
Installed Nameless ROM..
It is awesome!!
Although here are some reports from Music Duos Variant
Not Working
*Bluetooth
Needed Stuff
*Radio App??
Click to expand...
Click to collapse
Does at least bluetooth turn on or it didn't work 100%?
You can choose the gapps that suits you better. It depends on how many gapps you want.
Also I'm not the creator of this rom, just downloaded it's source. I don't know yet if FM is working but could add a radio app if it works. Also don't know why a Torch app was included lol
Does dual sim work??
Sent from my GT-S6012 using XDA Free mobile app
siddarthsmallya said:
Does dual sim work??
Sent from my GT-S6012 using XDA Free mobile app
Click to expand...
Click to collapse
I'm afraid not. When I made the first version, I already applied pawitp's patches, it booted but then I think it crashed so I had to disable dual sim before releasing it. I will compile it later without the patches to see if that was the problem, so please don't try enabling dual sim mode on the current version
Alonso1398 said:
I'm afraid not. When I made the first version, I already applied pawitp's patches, it booted but then I think it crashed so I had to disable dual sim before releasing it. I will compile it later without the patches to see if that was the problem, so please don't try enabling dual sim mode on the current version
Click to expand...
Click to collapse
Removing torch app then..
Dual s is the main thing missing in my phone..
Same error as in cm10.. for Bluetooth..
Herathon theme doesn't install at all..
Although the ROM is great..
Add a bit of kernel tweaks for the next release..
Upload a dual sim enabled version paralleled to nightly release..
Is CM11 better than this ROM?? jus a question..
Enjoying the ROM for now..
aqiben10 said:
Removing torch app then..
Dual s is the main thing missing in my phone..
Same error as in cm10.. for Bluetooth..
Herathon theme doesn't install at all..
Although the ROM is great..
Add a bit of kernel tweaks for the next release..
Upload a dual sim enabled version paralleled to nightly release..
Is CM11 better than this ROM?? jus a question..
Enjoying the ROM for now..
Click to expand...
Click to collapse
I don't know why bluetooth give so much trouble, the fix for galaxy grand duos and pocket neo make our phone to freeze when turning bluetooth on
I will have to make experiments about dual sim, however I don't even know if dual sim is working on cm 11
Also I made some recent changes to kernel but are not too many optimizations, only updates about SELinux, better kernel and compression
I haven't tested nameless so I couldn't tell wich is better. I think that nameless use more ram so that's why I've been using more cm 11, however, discovered a way to enable the low ram mode without disabling the transparent status bar so next releases of nameless and cm 11 will have more free ram
Edit: Uploaded RC 2 with a few changes for new year
RC1 has problems with games.. Clash of Clans and Marvel Champions crash after loading screen..
The odd thing is that they flicker before they crash..
Any idea why?? Is it ram issue?? Or processor??
edit: MTP doesn't work..
edit2: It worked after several tries..
aqiben10 said:
RC1 has problems with games.. Clash of Clans and Marvel Champions crash after loading screen..
The odd thing is that they flicker before they crash..
Any idea why?? Is it ram issue?? Or processor??
edit: MTP doesn't work..
edit2: It worked after several tries..
Click to expand...
Click to collapse
MTP working fine for me however didn't know the game bug managed to get some logs with clash of clans but don't really know what to do
Code:
W/InputDispatcher( 1710): channel '42013e40 com.supercell.clashofclans/com.supercell.clashofclans.GameApp (server)' ~ Consumer closed input channel or an error occurred. events=0x9
E/InputDispatcher( 1710): channel '42013e40 com.supercell.clashofclans/com.supercell.clashofclans.GameApp (server)' ~ Channel is unrecoverably broken and will be disposed!
I/ActivityManager( 1710): Process com.supercell.clashofclans (pid 5553) has died.
W/InputDispatcher( 1710): Attempted to unregister already unregistered input channel '42013e40 com.supercell.clashofclans/com.supercell.clashofclans.GameApp (server)'
I/WindowState( 1710): WIN DEATH: Window{42013e40 u0 com.supercell.clashofclans/com.supercell.clashofclans.GameApp}
W/WindowManager( 1710): Force-removing child win Window{41f48510 u0 SurfaceView} from container Window{42013e40 u0 com.supercell.clashofclans/com.supercell.clashofclans.GameApp}
W/ActivityManager( 1710): Force removing ActivityRecord{41e68290 u0 com.supercell.clashofclans/.GameApp t16}: app died, no saved state
Also released a new TWRP version, just in case http://forum.xda-developers.com/showthread.php?p=52424432 .I tested it and flashed nameless with no problems only with root but just updated supersu and everything went fine
Edit: Hmmm I think that bug doesn't happens on CM 11
Alonso1398 said:
MTP working fine for me however didn't know the game bug managed to get some logs with clash of clans but don't really know what to do
Code:
W/InputDispatcher( 1710): channel '42013e40 com.supercell.clashofclans/com.supercell.clashofclans.GameApp (server)' ~ Consumer closed input channel or an error occurred. events=0x9
E/InputDispatcher( 1710): channel '42013e40 com.supercell.clashofclans/com.supercell.clashofclans.GameApp (server)' ~ Channel is unrecoverably broken and will be disposed!
I/ActivityManager( 1710): Process com.supercell.clashofclans (pid 5553) has died.
W/InputDispatcher( 1710): Attempted to unregister already unregistered input channel '42013e40 com.supercell.clashofclans/com.supercell.clashofclans.GameApp (server)'
I/WindowState( 1710): WIN DEATH: Window{42013e40 u0 com.supercell.clashofclans/com.supercell.clashofclans.GameApp}
W/WindowManager( 1710): Force-removing child win Window{41f48510 u0 SurfaceView} from container Window{42013e40 u0 com.supercell.clashofclans/com.supercell.clashofclans.GameApp}
W/ActivityManager( 1710): Force removing ActivityRecord{41e68290 u0 com.supercell.clashofclans/.GameApp t16}: app died, no saved state
Also released a new TWRP version, just in case http://forum.xda-developers.com/showthread.php?p=52424432 .I tested it and flashed nameless with no problems only with root but just updated supersu and everything went fine
Edit: Hmmm I think that bug doesn't happens on CM 11
Click to expand...
Click to collapse
Tried out RC2..
Better and Smoother..
Although MARVEL doesn't work still..
Phone functions better otherwise..
Tethering and bluetooth still problem as i use this for local multiplayer..
New RC2 news
After more than one weeks use..
Still 1gb internal left..
My phone hangs a lot..
And now games crash before they even start..
And when the system opens after booting up 300+ ram is already in use..
Any idea what is happening??
I think I'll switch back to cm10.1 although I will miss KitKat due to ram problems..
Especially due to ram problems..
Fix when you are free..
aqiben10 said:
After more than one weeks use..
Still 1gb internal left..
My phone hangs a lot..
And now games crash before they even start..
And when the system opens after booting up 300+ ram is already in use..
Any idea what is happening??
I think I'll switch back to cm10.1 although I will miss KitKat due to ram problems..
Especially due to ram problems..
Fix when you are free..
Click to expand...
Click to collapse
Hmm I understand however my experience with cm 11 hasn't been so bad yet, maybe you should try cm 11 when I release the next version, it will have wifi tethering fixed. And don't know what could have caused all your problems...
Nameless has been the best ROM I've used in my phone..
Only problem is 3d.. Clash of clans is one of the major problems I face..
@alonso: is there any fix for graphical errors??
As ram and CPU are well available when I play the game..
CM11 dual working??
Nameless WiFi teathering also on next update??
edit: which cm11 version you used??
aqiben10 said:
Nameless has been the best ROM I've used in my phone..
Only problem is 3d.. Clash of clans is one of the major problems I face..
@alonso: is there any fix for graphical errors??
As ram and CPU are well available when I play the game..
CM11 dual working??
Nameless WiFi teathering also on next update??
edit: which cm11 version you used??
Click to expand...
Click to collapse
Hmm I'm not pretty sure about a fix for it, I'm not a pretty skilled developers as others
I tested clash of clans on cm 11 rc 2.1 and worked fine for me, also released today RC 3 of cm 11 with dual sim and wifi tethering fixed (however bluetooth still not fixed), maybe you should test it. And I will release another namelessrom soon, however dual sim may still not work on nameless
Ok released today RC 3, sorry got late. Only fixed wifi-tethering and added wifi direct. I hope I will release AOSB soon tough it has some bugs too and dual sim won't work there too. What's wrong with CM based roms? another recommendation? how is liquid smooth?
I'm using liquid smooth on my main phone and I can vouch that is awesome (link in my signature)! Definitely worth a shot
rahimali said:
I'm using liquid smooth on my main phone and I can vouch that is awesome (link in my signature)! Definitely worth a shot
Click to expand...
Click to collapse
well there are like infinite kind of roms out there, I would wish there were more developers for this phone :-/
Anyway here is AOSB. However I think people won't used too much. Probably I won't give too much support to it
Alonso1398 said:
well there are like infinite kind of roms out there, I would wish there were more developers for this phone :-/
Anyway here is AOSB. However I think people won't used too much. Probably I won't give too much support to it
Click to expand...
Click to collapse
I wish i could help out although due to me not having a pc at where i am staying(in a hostel)..
Although I can bugtest for you..
Cheers..
aqiben10 said:
I wish i could help out although due to me not having a pc at where i am staying(in a hostel)..
Although I can bugtest for you..
Cheers..
Click to expand...
Click to collapse
It's ok and thanks but there's no need for bugtest, I don't have programming knowledge so even if you report a bug, I wouldn't know how to fix it
Also I'll release another nameless release with latest cm 11 changes but I'm considering discontinuing it since it has weird game bugs and lacks dual sim, a feature needed by most users. Also I'll give a try to Carbon rom to see how it works, I hop it has working dual sim:fingers-crossed:
Disclaimer
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 the products you find here before flashing it! YOU are choosing to make these modifications.
Prerequisites for Installation
- Must have an unlocked bootloader
- Must have working TWRP
Known Issues
- MINOR - On Apollo there is a small glitch in rotation animation when screen transitions between on->off state
- MEDIUM - Bluetooth, GPS and LTE need to be debugged
Tips
- For ROOT ACCESS see Question 1 on the Frequently asked questions
Fresh Installation
- Factory Reset
- Flash the ROM File
- Flash any 5.1, arm 32-bit version Open GAPPS of your choice.
- Reboot
- On first boot it will take about 15-30 seconds before the boot animation appears
Upgrading to new Version
- Flash the ROM File
- Reboot
Downloads
- APOLLO rom
- THOR rom
- GAPPS
Source Code
- Kernel Source and Device Trees are here.
Credits
- Cyanogenmod
- CodeAurora
- Hashcode
- Cpasjuste
- dpeddi
XDA:DevDB Information
SlimLP, ROM for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
ggow
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader Only
Based On: Slimroms
Version Information
Status: Beta
Created 2015-09-04
Last Updated 2019-10-02
Release Notes / Changelog
2015-09-04
- Initial Release
- Kernel:
Based off Amazon Stock 4.5.5 for which we don't have the commit history so I have manually by hand done all the updates.
Rebased MDSS MDP Driver from CAF branch LA.BF.1.1.1.c4-03300-8x74.0
Upgraded a lot of code from the same CAF branch
More features coming soon
2015-09-05
Temporary Fix for Thor screen not coming out of standby correctly
Still a tiny bit more work needed in kernel for mdss mdsp driver
2015-09-15
Rebased mdss driver now fully working on Thor
Kernel has had a lot of work, see bitbucket page for changes
RRO Layers 2.1 have not been merged yet
Tried to cherry pick RRO Layers commits but received bad object errors
Updated to latest Slim 0.7 BETA code
Bluetooth is under investigation, sees devices but doesn't seem to pair
Switched bluetooth libs to been built from source
GPS is untested
LTE is untested
Battery Stats still needs to be fixed, needs investigation
2015-09-21
Update SlimLP code
Enable Sim Toolkit
Made changes based on provided logs to try to enable LTE
Recommended Gapps is now Open Gapps, linked in the OP.
2015-10-27
Update SlimLP Code
2015-11-07
Update SlimLP Code
2016-05-02
Updated kernel to the lastest CAF branch
Updated to latest SlimLP Code
Build bluetooth stack from source
Still working on Bluetooth - passkey pairing seems to be broken
Frequently Asked Questions
Question 1:
How do I get ROOT access?
Answer:
- Unlock developer options: "Settings" ➜ "About phone" ➜ Tap the build number 7 times
- Go back to "Settings" ➜ "Developer options" ➜ "root access" ➜ choose your desired option
Thank you so much for your and other developers hard work!
Will try this rom and give you a feedback ...
Hi, I wanna give you a quick feedback after 1 hour on the thor rom...
1) after the installation (did a factory reset) it comes with a bluethoot error and the service doesnt work.
I did a restart and switched it on ... off ... on ...off the first and secound time bluethooth seems to work (but did'nt make a link) but after that the service didnt come back.
2) After I switch off the display I have to reboot to get it back. So I only get a blackscreen with backlight.
3) Rotation works well but a few apps rotate in the wrong direction. But this is not a big thing!
4) Batteryusage didnt show apps and the graphic locks buggy
this are my first impressions
cocoon
cocoon4u said:
Hi, I wanna give you a quick feedback after 1 hour on the thor rom...
1) after the installation (did a factory reset) it comes with a bluethoot error and the service doesnt work.
I did a restart and switched it on ... off ... on ...off the first and secound time bluethooth seems to work (but did'nt make a link) but after that the service didnt come back.
2) After I switch off the display I have to reboot to get it back. So I only get a blackscreen with backlight.
3) Rotation works well but a few apps rotate in the wrong direction. But this is not a big thing!
4) Batteryusage didnt show apps and the graphic locks buggy
this are my first impressions
cocoon
Click to expand...
Click to collapse
- To be honest I developed this on apollo
- Didn't really test much on thor so probably problems in the kernel causing blackscreen for thor
- seems to work flawlessly on apollo
- will look into thor issues before next build
- thanks for the early feedback
- updated op known issues
Sent from my Fire Phone using Tapatalk
Thanks!
Excellent work @ggow, I just dirty flashed Apollo version, and must say I am pretty impressed, everything vent smoothly, the only FC I get was from clock app, but that was expected... :good:
Is there any recommended xposed version working with this ROM?
So far I found one small graphic glitch, you can see it on attached picture (you can see only half of the first notification)...
OK that's all for now, going to test how fast this can burn through hdx battery, so far every LP ROM I tested on my phones was really power hungry...
I've tried this ROM.. smooth as hell...
but if I not geting wrong, no LTE...( I am on Apollo)
Is that right? Or I made something wrong...
jeryll said:
Excellent work @ggow, I just dirty flashed Apollo version, and must say I am pretty impressed, everything vent smoothly, the only FC I get was from clock app, but that was expected... :good:
Is there any recommended xposed version working with this ROM?
So far I found one small graphic glitch, you can see it on attached picture (you can see only half of the first notification)...
OK that's all for now, going to test how fast this can burn through hdx battery, so far every LP ROM I tested on my phones was really power hungry...
Click to expand...
Click to collapse
- thanks, glad you like it
- I wouldn't recommend xposed with this rom. May not play nice as aosp
ka_putt said:
I've tried this ROM.. smooth as hell...
but if I not geting wrong, no LTE...( I am on Apollo)
Is that right? Or I made something wrong...
Click to expand...
Click to collapse
- I didn't think LTE would work
- that's gonna be a separate debugging exercise
How's Bluetooth? I know CM12 has some issues.
EncryptedCurse said:
How's Bluetooth? I know CM12 has some issues.
Click to expand...
Click to collapse
- Bluetooth will probably also need a bit work
ggow said:
- I didn't think LTE would work
- that's gonna be a separate debugging exercise
Click to expand...
Click to collapse
Ah OK. Good to know..
:good:
New Build For Thor
- This temporarily patches the problem on Thor with the screen not coming out of standby properly
What is the difference between this and the CM12 one that was updated the 15th of August?
DarkenedMatter said:
What is the difference between this and the CM12 one that was updated the 15th of August?
Click to expand...
Click to collapse
- Best to try it and find out.
- New kernel based on and modified from Stock 4.5.5 and latest MSM8974 CAF branch
- Rebased MDSS kernel driver is fully functional on Apollo Devices
Does the Apollo support otg? I just plugged my USB otg from my nexus 6, but stick mount says there isn't anything that needs mounted,
holeshot77 said:
Does the Apollo support otg? I just plugged my USB otg from my nexus 6, but stick mount says there isn't anything that needs mounted,
Click to expand...
Click to collapse
- OTG support isn't available at least at the moment.
- Not completely certain what the story is with OTG on Apollo and Thor
- I have seen various comments about this
- Some have said it might be a limitation of the hardware or a limitation imposed from the bootloader.
- Needs investigating to be sure of what can be done.
well xposed for LP actually works
ggow said:
...
- I wouldn't recommend xposed with this rom. May not play nice as aosp
Click to expand...
Click to collapse
I just had to try it and it's working! :laugh:
So if anyone wants to try xposed for lollipop, go for it (make sure you don't have any "xposed leftovers" from KitKat like me (gravity box i. e.) and uninstall them first)
be sure you did nandroid backup in TWRP before you flash xposed for lollipop in TWRP (yes, framework needs to be flashed)
I used xposed-v73-sdk22-arm.zip
Reboot into ROM and install XposedInstaller_3.0_alpha4.apk
That's it, happy hacking...
YouTube in FullHD
And I don't know what magic @ggow did this time, but we finally have here YouTube app where we can choose 1080p streaming ! Yay! This just made my day!
Or Google finally allowed this for every mobile users in latest YouTube app? Anyone on CM11 or Nexus 4 can check if its there too?
We've moved!
Downloads (for posterity)
Gapps - use any ARM (not ARM64) 6.0 variant. Do not boot the ROM before flashing these, or you will have to factory reset. For Now on Tap, use mini or higher
Build 7 - 2015-12-12
Build 6 - 2015-12-10
Build 5 - 2015-12-09
Build 4 - 2015-12-06
Build 3 - 2015-12-05
Build 2 - 2015-12-04
Build 1 - 2015-12-03
XDA:DevDB Information
EOL - Unofficial CyanogenMod 13 for i9300, ROM for the Samsung Galaxy S III I9300
Contributors
forkbomb444, Haxynox team, Nameless team, JustArchi
Source Code: https://github.com/CyanogenMod
ROM OS Version: 6.0.x Marshmallow
Version Information
Status: No Longer Updated
Created 2015-12-03
Last Updated 2015-12-20
Changelog
Build 7
Fix init.d (should fix camera for the most part, etc.)
Fix 2G/3G toggle
Enforcing SELinux
Older builds
Build 6
Fix GPS
Fix DRM
Fix some sepolicy denials
Build 5
Android 6.0.1 ("MMB29M") + December security patches
720p front-facing camera recording
fix p2p wifi (screen mirroring should work now)
fix network dropouts on hang up
Build 4
Fix 'optmising apps' on every boot
Merge screen mirroring fixes (hopefully it'll work, I can't test)
Build 3
Fix RIL brokenness from last build
Maybe fix sim lock - hopefully someone who knows their PUK can confirm
Enable uid_cputime in the kernel
Build 2
Fix video playback in most apps - DRM'd content is still broken, so apps like Play Movies won't work.
Fix video recording
FAQ
Root?
CM ships with root, enable developer options and look in Settings -> Developer options -> root access
Doze?
Doze needs a "significant motion" sensor (which uses the accelerometer) to function. The S3 doesn't have this at the moment, and its accelerometer is probably not low-power enough to implement it. At the moment, doze doesn't work, but I might investigate it at some point(tm)
Stock browser crashes when downloading?
You need to grant it permission to access storage in Settings -> Apps -> Browser -> Permissions
Google camera crashes?
Use Google Camera from the play store, not from gapps
Bootloop?
Try wiping data, cache, dalvik, system and re-installing. Some people have reported that dirty flashing over CM 12.1 works.
noones said nothing im going to give it a go. currently on 12.1 and will be doing a full wipe... fingers crossed:silly:
EDIT: Smooth 258MB via mega ( gapps took twice as long to download arm 6.0 mini 3 December 2015
Size: 245.49 MiB )
Let me be the first to thank you for bringing this to us s3 users
And for other members who doesn't know this member is also new maintainer who is trying to build official cm13 (correct me if im wrong)
Sent from my GT-I9300
Finally !!!
Thanks @forkbomb444.
Let me try it. :3
Sent from my GT-I9300 using Tapatalk
ASOP keyboard FC constantly
EDIT: flashed without gapps and works ok so far
No SD's show in windows
Omg so this is finally happening!!!! I've been patiently waiting for MM since the day CM confirmed they had a new maintainer for the i9300 ?.
Also constantly keyboard fc but fix it by installing Google keyboard via apk and disabling aosp one
Also YouTube videos are black but with sound
Flashed with no issues with open gapps
For a first build its pretty impressive
Sent from my GT-I9300
Scorpionea said:
Also constantly keyboard fc but fix it by installing Google keyboard via apk and disabling aosp one
Also YouTube videos are black but with sound
Flashed with no issues with open gapps
For a first build its pretty impressive
Sent from my GT-I9300
Click to expand...
Click to collapse
Could you please provide a logcat? @forkbomb444 stated that he won't fix any bugs unless logcats are provided.
Romflasher69 said:
Could you please provide a logcat? @forkbomb444 stated that he won't fix any bugs unless logcats are provided.
Click to expand...
Click to collapse
I think he already knows all or almost all bugs,no point in logcat as rom is way to early in development
But for sure will provide logcat if needed
Sent from my GT-I9300
Yes! Finally! The moment I have been waiting for. @forkbomb444 And with the kind of passion the developer has I am pretty sure the bugs will be fixed pretty soon!
@forkbomb444
Here is the logcat for YouTube app black screen on video but sound works
http://pastebin.com/jBndJ5Yx
YouTube videos works fine via chrome browser tho
Sent from my GT-I9300
Amazing !!
The animation while opening dialer and clear all task on recent app is very smooth. Wich isn't happen on LP.
Sent from my GT-I9300 using Tapatalk
nice work!
Hello,
Can anybody give me the download link of the latest Version of twrp please.
Edit: now o found the link. But how can i install the img File?
Thanks in advanced
@forkbomb444
Very much thanks for the release of marshmellow
Warning
this is warning to all .
I have flash the rom successful with latest TWRP .
clean flash.
bootloop at samsung logo. So I think why not dirty flash it over cm12.1 so i try and it booted successfully the bugs are the one which known.
then I make reset option in the setting to make it as clean as possible it end with bootloop at twrp logo.
please forkbomb any suggestion .
Note: I restore my phone with odin flash stuck rom.
important note : I have found my internal sd card formatted whyyyyyy???.:crying:
Thanks for the release any way.:good:
Hi, you SD internal was format Because you have flash your stock with odin
Thank u for bringing this up. I'll be waiting for a stable version though, but still very happy to see the news.
Hi,
I did factory reset installed the rom and gapps pico.
I got into endless loop of Galaxy i9300 logo.
Any clue what I did wrong?
We are really close to official support.
Our device mostly works fine now if you do a build form the official sources.
Only bugs are the known ones.
We are working on fixes for these, but they are hard, because we don't have the rare variants to do the needed tests.
Please don't forget we are not paid, we do it in our free time.
These are the bugs that we know about:
- SIM Slot 1 mobile data bug (You can find the workaround below.)
- headphones are noisey when the amp not gets signal from the soc but still turned on.
- goodix fingerprint is not suppoted yet (Need testers, who can send back to me logs, because I don't own this kinda hardware to debug.)
- Magnetic flip cover is not supported on CM side. (The kernel has driver for it.)
- ???
You don't have mobile data on sim slot 1?
There is a workaround until we don't have a proper fix:
- Put your sim into slot 2.
- Power on your phone
- Wait until it not connects up and get mobile data
- Now turn off your phone
- Put back your sim to slot 1
- Done
Old post:
Hello everyone!
I want you present the CyanogenMod 13 ROM that has the least bugs.
This rom uses kernel that built form source code.
Supports fingerprint and every camera sensor. (This is the only rom that can do that as of now!)
Known bugs: (They are on my TODO list.)
- Weird noise form the headphone jack
- Bluetooth mac address is not read form nvram.
- Infrared is also shown as input device while its only output.
- Some Selinux permissions are missing.
Bugs form Xiaomi: (If you use 6.0 based miui rom you will also have these issues.)
- At some areas com.android.phone may crash. This is a blob issue. We are waiting for Xiaomi to fix it.
- At some areas GPS may not works. This is a blob issue. We are waiting for Xiaomi to fix it.
You found a bug?
Let me know!
What is my plan?
Fix all the bugs then get official CyanogenMod support.
Download:
V8: cm-13.0-20160617-UNOFFICIAL-kenzo.zip
Changelog:
V8:
- Fixed keylayouts
- Added updated blobs
- Update build fingerprint to 6.6.16
- Fixed board name in props
- Updated audio configs
- Updated more props
- Fix power derp (No more only performance mode)
V7:
- Updated firmwares to 6.6.16 6.0
- Added modem form 6.6.16 6.0
- Updated key layouts
- Updated charger driver and settings
V6:
- Update blobs to 6.6.16 6.0 (fixes GPS)
- Update ramdisk
- Enable Quick Charge
V5:
- Fixed 80% charge issue.
V4:
- Fixed LEDs.
V3:
- Fixed FM Radio (Thanks to @danielpinto8zz6 for the help.)
V2:
- Fixed bootloader relock issue.
- Enabled cont splash
- Fixed splash in fastboot
V1:
- First release
Old versions:
V7: cm-13.0-20160616-UNOFFICIAL-kenzo.zip
V6: cm-13.0-20160615-UNOFFICIAL-kenzo.zip
V5: cm-13.0-20160615-UNOFFICIAL-kenzo.zip
V4: cm-13.0-20160615-UNOFFICIAL-kenzo.zip
V3: cm-13.0-20160615-UNOFFICIAL-kenzo.zip
V2: cm-13.0-20160614-UNOFFICIAL-kenzo.zip
V1: cm-13.0-20160614-UNOFFICIAL-kenzo.zip
XDA:DevDB Information
CyanogenMod 13, ROM for the Xiaomi Redmi Note 3
Contributors
banmeifyouwant, TheStrix
Kernel Source Code: https://github.com/balika011/android_kernel_xiaomi_kenzo
Device Tree: https://github.com/balika011/android_device_xiaomi_kenzo
Vendor Files: https://github.com/balika011/android_vendor_xiaomi_kenzo
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
ROM Firmware Required: Unlocked Bootloader
Based On: CyanogenMod 13
Version Information
Status: Nightly
Are you the developer?
SkinCoffin said:
Are you the developer?
Click to expand...
Click to collapse
yes he is the developer, and he is a genious too
danielpinto8zz6 said:
yes he is the developer, and he is a genious too
Click to expand...
Click to collapse
Why is that?
SkinCoffin said:
Why is that?
Click to expand...
Click to collapse
Because he is the only one that fixed fingerprint with source kernel and the only one that fixed camera with source kernel
danielpinto8zz6 said:
Because he is the only one that fixed fingerprint with source kernel and the only one that fixed camera with source kernel
Click to expand...
Click to collapse
Sounds promising! Does this mean that flashing this ROM doesn't mess with the bootloader?
What are the main advantages of that?
SkinCoffin said:
Sounds promising! Does this mean that flashing this ROM doesn't mess with the bootloader?
What are the main advantages of that?
Click to expand...
Click to collapse
yes this means that,
the advantages? faster, safier, stable...
I'm currently on Resurrection Remix which you know it uses leaked Marshmallow firmware. Do I need to downgrade to stock Lollipop firmware first before flashing this ROM?
Sent from my Redmi Note 3 using XDA-Developers mobile app
MOVZX said:
I'm currently on Resurrection Remix which you know it uses leaked Marshmallow firmware. Do I need to downgrade to stock Lollipop firmware first before flashing this ROM?
Sent from my Redmi Note 3 using XDA-Developers mobile app
Click to expand...
Click to collapse
No, but your bootloader will be re-locked.
See post #1 how to re-unlock.
ATM I'm working on auto-re-unlock.
Whit the next build noone's device will be locked again.
Same issue as any other cyanogenmod-13 based ROMs, LTE connection/detection issue (Indonesia). AOSP and several MIUI version (7.3.2) has no such issue. Other than that, everything works as advertised.
franksn said:
Same issue as any other cyanogenmod-13 based ROMs, LTE connection/detection issue (Indonesia). AOSP and several MIUI version (7.3.2) has no such issue. Other than that, everything works as advertised.
Click to expand...
Click to collapse
Send me a contact in pm.
Skype, Hangouts, etc.
I'll try to fix, but i need someone who can test it.
banmeifyouwant said:
No, but your bootloader will be re-locked.
See post #1 how to re-unlock.
ATM I'm working on auto-re-unlock.
Whit the next build noone's device will be locked again.
Click to expand...
Click to collapse
Does unlocking work with MiUnlock as well?
How's the battery life compared to other ROMs?
Xposed, Viper, Dolby Atmos working?
Does your build at the moment still re-locks the bootloader? Not that is a big deal, just wondering.
this rom is bettery than http://forum.xda-developers.com/red...cyanogenmod-13-0-xiaomi-redmi-note-3-t3350656 ?
fast?stable?
SkinCoffin said:
Does unlocking work with MiUnlock as well?
How's the battery life compared to other ROMs?
Xposed, Viper, Dolby Atmos working?
Does your build at the moment still re-locks the bootloader? Not that is a big deal, just wondering.
Click to expand...
Click to collapse
See changelog at post #1
Battery life is always depends on usage, and this is a just built rom. Noone tested jet. You can be the one of the first users!
Xposed should work just fine. (It's a CM13 rom...) I never used the others.
Thank you for your hard work!
I have test that I can't find fingerprint in lockscreen,maybe the problem of hal or driver?
Here are the screenshots.
babaqpqp said:
Thank you for your hard work!
I have test that I can't find fingerprint in lockscreen,maybe the problem of hal or driver?
Here are the screenshots.
Click to expand...
Click to collapse
Turn on Pin unlocking first and then it will appear in the Lockscreen menu. (I think.)
---------- Post added at 11:39 ---------- Previous post was at 11:37 ----------
banmeifyouwant said:
- Bluetooth mac address is not readed form nvram.
Click to expand...
Click to collapse
What does this mean? I can still pair to a headset / Fitbit / car Bluetooth without the MAC address ?
Thank you for your reply.
I have tried but it still not work.
if I'm on an official MIUI Rom, will this re-lock my bootloader?
fingerprint working. but why do we have to check the hardware input for the keyboard to show up? its kinda confusing + theres no hint on want to do. maybe you can add to OP post about this?
BUGS:
- LED isnt working.
- charging stops at 81% (then its just discharge)
Thank you
Great! thank you for your hard work :good: .
PixN Rom** Theme friendly ** Better Camera ** exFAT ** Optimized kernel ** Substratum ** Clang ** Custom Settings **
This is my daily driver which I update occasionally depending on weather I need/want new features. There won't be any OTA's because of work. Do please also check the Credits section, and the Screenshots tab.
I do not have a single sim device, however I have compiled kernels for the single sim and dual sim variant both.
The kernel thread has now been split to be here since the kernel gets more updates than the rom (for now atleast).
This project has been renamed to show the my first forays into more *real* development.
Please use the Feature Request tab for feature inclusion requests.
It's also very hard to keep track of bugs reported here in the comments so please, again, use the bug reports tab...
I'm very thankful to everyone commenting, it's just hard to keep track sometimes, and seeing as DevDB has all the features required...
Since I also use XDA Labs which has no DevDB support it'd be best to comment AND add the comment in the required DevDB tab..
Features Implemented
Release 1
SonyAosp Based
OMS Substratum Support with Masquerade (from CarbonROM)
Thermal-engine (CarbonROM)
Gapps Inbuilt (OpenGapps)
Supports Assistant Activation
Increased Call Log History
Working Advance Reboot Menu (SonyAosp)
Commit history in Changelog (SonyAosp)
Screen dimmer. (Elementalx Kernel)
Release 1.99
This is a beta release which sort of currently BREAKS BLUETOOTH. (will be fixed in Release 2)
Working Camera (The google camera crashes but open camera and whatsapp camera work usually, some crashes are still there but the pictures are clear (front camera colors are a bit washed out) and no inversion or anything)
Sdcarfs (should fix exfat)
Fixed the wakelock issue (IPA and others)
Fixed substratum for the e6653
Stability Tweaks
Release 1.999
Please extract the zip and fastboot flash both the system and the kernel..
Working Camera (Works for me)
Built with CLANG
Fixed the slow charging
Native ntfs and exFAT
More Stability Tweaks
Built with newer external libraries
Added Vanilla Music Player
More features coming soon, framework buildup.
Release 3
Please extract the zip and fastboot flash both the system and the kernel.. This is a deodexed build and has a slow FIRST boot.
Status Bar swipe to increase brightness
Customize Nav Bar
Fixed Substratum
Double Tap status bar to sleep
Music Controls
Close foreground app with long press
Screen Record
Native Screenshot edit options
All other OmniGears features as of 7.0
Busybox built in (toybox is too limited)
Some new bugs which will be fixed. Report them asap!
Release 3.1
Minor Bugfix release.
Squashed that damn irritating power button reboot
Also has a new minor kernel update
Release 4
Major release. Name change, fixes... the full changelog is HUGE
Fixed LEDs
Fixed Power reboot issues
Added my own custom settings based off Benzo and Flash Roms
Ambient display
NETWORK TRAFFIC MONITOR!!
LED Control (Cyanogenmod)
Default pixel coloring
Added substratum and superuser tiles in settings
Double tap to sleep anywhere
Adblock from the MoaAB Project
Navigation bar edits
Pulse
Smartbar
Fling
Toast icons
Fixes and stuff check changelog.
Sdclang and Clang build
Release 5
Major release. Android version upgrade. I can't remember the whole changelog.
Rebased to Android 7.1.1
Therefore all 7.1.1 features, most notably, automatic background update handling and faster UI
Built with GCC 6.x as well as Clang 3.9 for speed and battery
All the features made it through intact including themes
Introducing Moves, which are quick shortcuts
All the libraries have been optimized and rebuilt mostly
Uses a Relatime Thread for the UI
Release 5.5
Bugfixes. Everyone should get this.
Fixed all the Settings
Added charging current and voltage
Release 6
More fixes and features.
Fixed all the Settings (again)
Added memory bar option
QS Header Icon settings
Date and time for header modifications
Auto launch music player
Release 7
Major fixes
Updated externals
Fixed fingerprint thanks to @Myself5
Working
Almost everything.
Originally based on the test data over here.
Single Sim Support
Dual Sim Support
GPS
Bluetooth
SMS
SD Card
Fingerprint
Partially Working / Buggy
Camera (Mostly working)
PicoTTS sometimes crashes (reported by @Azrael6947 ) Not an issue from 1.99
Sometimes these wakelocks prevent deepsleep. Disable the services and use suggested apps to fix. (as reported by @Sh4douw)
Release 3
Sorry but these are mostly due to a rushed release. ALL of these WILL be fixed asap.... All done!
The LED won't turn on while charging, but it still charges and shows the animation. (Fixed in 4)
The power button sometimes causes random reboots (Fixed in 4)
Power menu isn't themed yet (Fixed in 4)
The omnigears settings look like they don't stick (checkboxes) but they actually do (My settings do stick in 4)
Release 5
These are to be removed in the next release
The statusbar battery in the icon doesn't work. Everything else does. (Fixed in 6)
Lockscreen shortcuts don't work yet (Fixed in 5.5)
Lockscreen voltage and charging current doesn't work yet (Fixed in 5.5)
Weirdly I managed to get the advanced reboot menu to turn up while using the Power Off option too so for now to really turn it off you'll need to choose bootloader
Not Working
Inbuilt Recovery (Weirdly) (Use the one in the suggested extras)
Fingerprint Manager (Asks for it in settings but never works) (Fixed from 7 onwards)
Bluetooth for E6683 (Fixed)
Suggested Extras
Recovery
SuperSU (suhide causes bootloops)
Magisk with phh's Superuser (New root interface with persist options)
AutoMagisk for hiding root
Assistant Enabler Zip Or App
Substratum
Substratum Pixel Theme
Naptime & Doze for better standby drain.
If the brightness is too dim you can turn the dimmer on and off by the following
You can echo 0 to disable and echo 1 to enable it via the sys path /sys/module/mdss_fb/parameters/backlight_dimmer
Click to expand...
Click to collapse
Please feel free to report more bugs, or even request more features but I'm not a dev so, no guarantees.
Installation Instructions
Eventually these will be flashable zips, however right now they're causing an error (IOError: [Errno 28] No space left on device)
So for now install by fastboot
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery_3.0.2.img
I don't recommend wiping userdata via fastboot so if you want you can always factory reset or clear Data, Cache, Dalvik and System from TWRP.
EDIT:- People having trouble flashing the system.img should try with mfastboot (fix found by @katibehi)
Downloads
The DevDB downloads are for the system.img and boot.img files only. They're in 7z cuz otherwise I can't upload them.
Get the latest kernel from the PixN kernel thread here.
Beta Release 1.999
This is in the DevDB download. The changelog is incorporated into the feature list.
The .7z is NOT FLASHABLE.
Extract it and fastboot flash the file as fastboot flash system filename.img
Click to expand...
Click to collapse
Beta Release 3
MAJOR RELEASE. Go get it.
Beta Release 3.1
Bugs squashed. Notably the reboot.
Beta Release 4
Biggest YET!! Most feature complete rom around.
Beta Release 5
Bigger than ever (feature wise). First and only 7.1.1 build for our devices. Happy New Year!
Sadly this release is not on DevDB.. Since DevDB won't finish attaching files as of 1st Jan and I don't even know if it'll be back. I'm really hoping for a basketbuild account, cuz then I'll be able to serve OTA's. Anyway.
For now due to popular demand this release, Release 5 is uploaded to MEGA.
Beta Release 5.5
Still on MEGA.
The link to the folder is here
Beta Release6, 7
Mega again... Until DevDB is back up assume all future releases to be on MEGA for now.
The link to the folder is here
For mobile users to get to the downloads section just hit the big DOWNLOADS button.
FAQ/Frequent Statements
Q0: When ${THING}?
A0: No ETAs. Don't ask.
Q1: You list my phone above but there isn't a build uploaded, why not?
A1: Haven't gotten around to it yet.
Q2: But when will you get to building it?
A2: Damn it, see Q0/A0.
Q3: How often will builds be produced?
A3: Whenever I get to them and feel like uploading.
Q4: But ${THING} isn't working for me. I cannot live without ${THING}.
A4: Not surprising, nougat is still young. Some features aren't ported and some may still be buggy. Maybe this isn't ready for you yet. And don't cry.
Q5: Xposed?
A5: Don't know. Maybe, maybe not. I'll ignore you if you complain about something and are using Xposed. Not out for nougat yet.
Q6: Can I complain about something?
A6: I'd prefer not, but be prepared for me to ignore you.
Q7: Can I report a bug?
A7: Absolutely. Please mention the kernel version and any additional files you flashed. Create a logcat.
Q8: When will you fix ${THING} that I just reported?
A8: Damn it, see Q0/A0. And if your ${THING} isn't something that bothered me, it probably just got shuffled to the back of the line.
Q9: Can I donate?
A9: Sure! Whatever you can. This takes a lot of time. Apparently not.
Q10: What is this "sdclang" thing?
A10: CM is using a optimized version of the clang/llvm compiler for official builds of Qualcomm devices. I'm using it for my own builds. See these links here and here.
I've depreciated this to move to Clang 3.9 (newer).
Click to expand...
Click to collapse
Full Changelog
These were clogging up my XDA Labs view of the thread. I'll make a github repo for them soon.
Credits
@The Flash for his kernel and rom. (Disputed)
[*] @JerryLaiHMmmmmm for showing the community AOSP was possible.
[*] @zacharias.maladroit for the recovery and his excellent kernel.
[*] @RyTekk also for his kernel source and inputs.
[*] @Myself5 for setting me straight about the E6683 kernel issues and for all the work done on sony devices.
[*]@frap129 for his excellent MapleAOSP
[*] @pollob666 for the call log fix.
[*] @haggertk for the FAQ.
[*]@BSDgeek_Jake for MoaAB.
[*] Sonyxperiadev Team.
[*] SonyAOSP Team.
[*]OmniRom Team.
[*]DirtyUnicorns Team.
[*]PureNexus Team.
[*]BenzoRoms Team.
[*] CarbonROM Team (Best gerrit ever).
[*] Substratum Team.
[*] AOSP providers.
[*] Everyone testing this.
If I've forgotten anyone I'll add them later, especially if someone reminds me...
Sources
All of them are up on github now... here!
The kernel is given here.
XDA:DevDB Information
PixN Rom, ROM for the Sony Xperia Z5
Contributors
HaoZeke
Source Code: https://github.com/PixN-ROM
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.10.x
Based On: AOSP
Version Information
Status: Beta
Current Beta Version: 5.5
Beta Release Date: 2017-01-03
Created 2016-11-10
Last Updated 2017-01-11
I just tried it on my E6633
Everything works except the camera which didn't want to work, even after some reboots.
Sh4douw said:
I just tried it on my E6633
Everything works except the camera which didn't want to work, even after some reboots.
Click to expand...
Click to collapse
Well.... I'd suggest you wait for a while after the reboot.. Then try the internal camera in WhatsApp... That works for me..
Though the camera problem is basically across all aosp builds until Sony or cyanogenmod or someone fixes it...
First of all thanks for your great effort! this rom is amazing.
Well time to report.
First, battery life is quite amazing, over 5 hours of sot. (around 3 in stock rom)
Second, the 64gb sd card won't get recognized... but on the other hands 32 gb one works well.
Regards,
Jerry
P.s. if you would like to solve the camera issue try to dig into @infected_'s repo... His roms had solved the camera problem.
JerryLaiHMmmmmm said:
First of all thanks for your great effort! this rom is amazing.
Well time to report.
First, battery life is quite amazing, over 5 hours of sot. (around 3 in stock rom)
Second, the 64gb sd card won't get recognized... but on the other hands 32 gb one works well.
Regards,
Jerry
P.s. if you would like to solve the camera issue try to dig into @infected_'s repo... His roms had solved the camera problem.
Click to expand...
Click to collapse
Thanks for the heads up I'll definitely look into it
I'm not sure why the 64 gb cards don't work...
I'm not having issues with my 128gb sd card but it did format it before it would work..
Has it offered to format the sd card?
EDIT: @infected_ also seems to have used the same sonyAOSP repositories for his aosp build...
It's unlikely but maybe a different tool chain might help... I'll check. Also they seem to be all marshmallow builds... That might also be behind their camera working better...
camera isnt working yet on AOSP, on the kitakami/msm8994 family and all others. with some hacks msm8974 was taking pictures, but nothing stable.
regards.
What about the battery life during the night for you ?
It started from 82% at 2:00 AM, and now it's at 65%...
Sh4douw said:
What about the battery life during the night for you ?
It started from 82% at 2:00 AM, and now it's at 65%...
Click to expand...
Click to collapse
Yikes, that seems really awful. I'd suggest you use naptime for aggressive doze.
You could also try the doze app which stops background data for chosen apps...
With naptime installed you should get much better battery life...
Did you clean flash this?
HaoZeke said:
Yikes, that seems really awful. I'd suggest you use naptime for aggressive doze.
You could also try the doze app which stops background data for chosen apps...
With naptime installed you should get much better battery life...
Did you clean flash this?
Click to expand...
Click to collapse
I'll try Naptime and Doze app secondly.
Thanks for your tricks. I will tell you if it resolved my issue
And yup, I did a clean install
I can't flash system.img, fastboot shows this error
(load_file: could not allocate -1585037392 bytes
error: cannot load 'system.img')
I downloaded system.img two times but same error.
katibehi said:
I can't flash system.img, fastboot shows this error
(load_file: could not allocate -1585037392 bytes
error: cannot load 'system.img')
I downloaded system.img two times but same error.
Click to expand...
Click to collapse
Which system are you coming from?
I think that error probably has to do with the larger size of the system image because of gapps being included..
Are you trying a full wipe?
finly i flashed it every think is good but camera dosent work. for now i come back to stock.camera important for me.thanks for your work
Is it possible to make this compatible with the E6653 device? The rom loads perfectly on my phone, only thing not working is my SIM card because I dont have a DSDS phone.
Azrael6947 said:
Is it possible to make this compatible with the E6653 device? The rom loads perfectly on my phone, only thing not working is my SIM card because I dont have a DSDS phone.
Click to expand...
Click to collapse
Yup it is possible and I'll release a working boot.img for the e6653 with the next release (hopefully today itself)
Actually the delay is because I'm compiling with uber but my first build was laggy as hell.
Azrael6947 said:
Is it possible to make this compatible with the E6653 device? The rom loads perfectly on my phone, only thing not working is my SIM card because I dont have a DSDS phone.
Click to expand...
Click to collapse
Why you don't flash this(http://forum.xda-developers.com/xperia-z5/development/cyanogenmod-14-1-xperia-z5-e6553-t3493283) on your e6653?
katibehi said:
Why you don't flash this(http://forum.xda-developers.com/xperia-z5/development/cyanogenmod-14-1-xperia-z5-e6553-t3493283) on your e6653?
Click to expand...
Click to collapse
Actually trying that one now, funnily enough it's not detecting my SIM card either. Never had this issue before, might be because I am in Australia.
---------- Post added at 10:26 PM ---------- Previous post was at 10:07 PM ----------
HaoZeke said:
Yup it is possible and I'll release a working boot.img for the e6653 with the next release (hopefully today itself)
Actually the delay is because I'm compiling with uber but my first build was laggy as hell.
Click to expand...
Click to collapse
Haha, you have no idea how excited I am right now. Eagerly awaiting that upload. Soon as it's up, I'll load it up and if all works well I'll use it for a while and give you some feedback.
Unfortunately the CM 14.1 ROM that was posted (which is for the E6653) cant detect my SIM either, lot of other people are having that issue too. Hopefully yours will be that stock experience I'm looking for.
Sh4douw said:
I'll try Naptime and Doze app secondly.
Thanks for your tricks. I will tell you if it resolved my issue
And yup, I did a clean install
Click to expand...
Click to collapse
Ok, so I installed Doze, Greenify (without Xposed, hope that it will be compatible with Android Nougat soon ), and NapTime. Without effect, always 2-3% drain per hour.
I realized that my device won't deep sleep, it was always in activity even when I wasn't using it.
I searched for wakelocks, and noticed that Google services were faulty. I disabled some of them after searched online, and it's better
I think without camera, the rom isn't complete. I am waiting for that.
Azrael6947 said:
Actually trying that one now, funnily enough it's not detecting my SIM card either. Never had this issue before, might be because I am in Australia.
---------- Post added at 10:26 PM ---------- Previous post was at 10:07 PM ----------
Haha, you have no idea how excited I am right now. Eagerly awaiting that upload. Soon as it's up, I'll load it up and if all works well I'll use it for a while and give you some feedback.
Unfortunately the CM 14.1 ROM that was posted (which is for the E6653) cant detect my SIM either, lot of other people are having that issue too. Hopefully yours will be that stock experience I'm looking for.
Click to expand...
Click to collapse
I believe the sim detection in @fergy's rom has been fixed by him.. check the last posts in that thread...
I do honestly believe aosp is doing better than cm-14.1 at the moment, mostly because CMTE hasn't been doing well on the newer CM roms while Substratum is working really well...
I'm uploading a single sim kernel to release 1. Since the Uber builds are being more trouble than help...
Test it and tell me how it goes...
katibehi said:
I think without camera, the rom isn't complete. I am waiting for that.
Click to expand...
Click to collapse
On release 2 (testing) with the Uber toolchain, Open Camera works... however the rom is overall very laggy using uber...
So I'll be looking into other opportunities...
By the way, have you found any non-stock rom (AOSP,CM etc) here or elsewhere with a working msm8994 camera?
If yes please link the repos here, I'll gladly try to incorporate it.