Disclaimer
I'm not responsible for anything that may happen to your device. I've tested this mod to the best of my abilities, but I can't guarantee anything. Make a complete backup before applying any of these changes. If you brick your device, boot loop, lose data, or etc...again, I'm not responsible.
CM12 - Working
- CM12S YNG1TAS0YL with stock kernel
- CM12 nightly with stock kernel
CM11 - Working
- CM11S XNPH30O, XNPH33R, XNPH38R, XNPH44S, and XNPH05Q with stock kernel
- CM11, PAC-man, crDroid with most recent kernels
- franco r35 kernel
CM12.1 - Not Working
- CM12.1 nightly (bootloop)
CM11 - Not Working
- LiquidSmooth ROM (mediaserver seg faults immediately)
- OmniROM
Also, I found a commit in the CM source that adds Voice Wakeup options to the Settings app. If the ROM doesn't have this code compiled into their Settings, the mod will probably not work. You'll still be able to go through the training process, however, I don't believe Google Now will launch because the intent action is never being set.
Instructions
1.) Backup any important data on your phone (files, pictures, etc.)
2.) Boot into recovery. I use and have only tested with TWRP
3.) Make a nandroid backup
4.) Flash the mod
5.) Reboot
Recovery
If you encounter any issues (e.g. bootloop) or just want to remove the mod, go into recovery and restore just the System partition from the backup you made earlier (this will preserve your Data partition).
After Installation
After installing, you'll get a notification to enable Voice Wakeup and to train your voice. You can do this now or skip it. It can always be setup later by going to:
CM11: Settings --> Voice Wakeup --> Retrain your voice
CM12: Settings --> Language & Input --> Voice Wakeup --> Retrain your voice
Also...
1.) Go into the Google Now settings and disable "OK Google" detection settings.
2.) Disable your lockscreen if on CM11S or CM12S...other CM11/CM12 based ROMs should work fine since the apk is signed correctly. Some users have reported being able to use a 3rd party lockscreen (e.g AcDisplay) as a work around for CM11S.
If something is not working for you, I need the following or I can't help...
- The ROM you're using (date/version too)
- The kernel you're using (date/version too)
- A description of the problem
- A logcat of the problem in action
Changelog
Code:
[I]4-14-2015[/I]
- New test version for CM12 based ROMs. I believe this should work with most kernels.
[I]Version 2.0[/I]
- CM11 based ROMs only
- Updated mixer_paths.xml with more recent version from CM11
- Deodexed, signed, and zip aligned VoiceWakeup.apk. The app can now bypass the lockscreen on CM11 based ROMs
Disabling the lockscreen is still necessary for CM11S ROMs because those keys aren't public
- Added a "loud" version. It increases the microphone volume levels to make it more sensitive
[I]Version 1.0[/I]
- Initial Release
Woow. It seems working flawlessly
me wanty. Hopefully you can post a how to in the near future
Added to OnePlus One index thread:
[INDEX] OnePlus One Resources Compilation Roll-Up
Transmitted via Bacon
jojo_whit3 said:
I bought the OnePlus One in August because I was interested in the always on listening feature that they showed off back in the Spring. So when I actually received the phone, I was pretty disappointed to learn that they took the feature out before shipping. Over the past couple weeks, I've been working on a way to get this feature back in the phone and I think I finally got it working pretty well. I've only tested it on the 25R and 33R builds, but it should work on most ROMs for this phone. The mod uses the always on low power core, so there's no significant drop in battery life. I know Qualcomm has some licenses for this IP, so I'm still trying to figure out if I can legally post the mod here. But in the meantime, here's a demo of it working...
Click to expand...
Click to collapse
Just curious, would this mod stop ota updates and if so is it easily reversible? Looks really nice.
Sent from my A0001 using Tapatalk
share it pls!
Overdose1986 said:
share it pls!
Click to expand...
Click to collapse
Did you read the OP?
I know Qualcomm has some licenses for this IP, so I'm still trying to figure out if I can legally post the mod here.
Click to expand...
Click to collapse
Transmitted via Bacon
looks cool, do keep us updated if you are able to share this "legally" or can you pm me the "not so legal" way? LOL
I didn't know I wanted this until now
That looks awesome
I've been trying to contact someone from the Cyanogen team to get some more information about posting this. If anyone has any contact info, either send me a PM or send them over to this thread.
To give a little more information about this mod, its essentially a port of the VoiceWakeup.apk I found here. If you use apktool to disassemble this file, it's easy to tell it came directly from Qualcomm. However, if the Cyanogen team intended to release this apk with the phone initially, then I'm assuming they already have some agreement in place with Qualcomm. So hopefully that also means it'll be ok for me to post this mod in the near future.
26.2man said:
Just curious, would this mod stop ota updates and if so is it easily reversible? Looks really nice.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
You would still be able to download the OTA updates, but you wouldn't be able to apply them since there would be changes to your file system. If you make a nandroid backup in recovery, then anything is easily reversible.
Thanks. Hope you can release this soon.
Sent from my A0001 using Tapatalk
Looks great, wonder if the cm team is working to make it work by choosing you own wake up command. Had it on my find 7a and saying snapdragon was strange
If it's already freely available then it's unlikely to cause any more issues, depends on what did you do to"port" it I guess.
All the cm11s apps have been made available, so if it came from an existing rom I can't really see much of an issue. But I'm not a lawyer
Alternative is to post a walkthrough of your changes to the original.
Sent from my A0001 using Tapatalk
Awesome work, hopefully you're and to post it up for us eventually.
Hi Everyone...I did a little thread cleaning. Please, lets not harass the OP about when this will be released. Like everything else on xda, it will be released when the developer is ready. Just as a reminder to everyone,
yes this is a hackers site, but certain things are not allowed. If the OP wants to make sure that he isn't violating CMs or Qualcomm's Intellectual Property then we should let him do this to his own satisfaction. Nobody
wants to see a modification removed because CM or Qualcomm complained.
Thanks!
This looks really good! Would love to have this feature, keep it up man
If you're worried about posting the modded APK and the IP issues, can you at least let us know what you modded so we can do it on our own?
had a quick play with it earlier,
Cm 11 nightly contains the background libs (except liblisten.so) but there's some java calls missing. Curious that cm have left most of the libs in place.
Related
Latest Downloads
CM10.1 http://d-h.st/i3V
CM10.2 https://drive.google.com/file/d/0B1V_hMyelDz0Rm1nenlqT2JKWkE/edit?usp=sharing AS OF 21.11.2013
UNOFFICIAL FAQ FOR CM10.1/10.2
DOWNLOAD AND INSTALLATION
Q: Where’s the download?A: The initial FXP release had an incorrect kernel – you can download a working version of ROM from here. http://d-h.st/TPT
This ROM has since been updated a download can be located here. http://d-h.st/i3V
If you wish to try a CM10.2 (that’s Jelly Bean 4.3 – have Sony actually released a 4.3 ROM yet?) one can be downloaded from the link above.You can also download the correct version of GAPPS for Jelly Bean 4.3 here. http://brintaylor.info/Android/CM/gapps/
For the CM10.2 build you should use this link to report bugs. https://docs.google.com/forms/d/185s...9UINQ/viewform
Uberlaggydarwin plans to take a 'light touch' approach to support via XDA, so don't necessarily expect an answer to a query if you post in this thread
It seems like FXP have delayed releasing for our device for now, but information about CM builds that are being actively supported and developed can be found in this thread for now.
Q: How do I install?
A: You need an unlocked bootloader and an installed recovery. BACK UP your current ROM to your external SD card. Put the ROM and GAPPS on your external SD card. Boot into your recovery, do the necessary wipes, flash the ROM, flash GAPPS, reboot, victory. Disclaimer: if it breaks your phone, it’s your fault.
Q: Do I need to install the supplied kernel before installing the ROM?
A: No, unlike older xperia models CWM is able to flash both the kernel and the ROM at the same time. There is no need to use fastboot or flashtools to flash the kernel first, just a working recovery and an unlocked bootloader on your phone.
Q: Can I use another kernel instead?
A: No, for now only the supplied kernel will work.
Q: I’ve installed the ROM but can’t find the play store?
A: Immediately after installing the ROM you should install the 4.2.2 version of GAPPS (Google Apps) – this installs the play store and several other applications that Google regard as essential to the Android experience. This can be found here – http://goo.im/gapps/gapps-jb-20130812-signed.zip
Q: How do I update to the latest version of the ROM?
A: Once you’ve downloaded the latest version to your SD card, boot into recovery. No need to wipe your data, though you probably should wipe cache and dalvik cache (I don’t know whether this is done automatically as part of the installation but it can’t do any harm). You don’t need to install GAPPS again as this is a firmware update, not a new installation.
However if you’re moving between versions i.e. 10.1 to 10.2 you should definitely do a factory reset – the ROM may well work fine without a data wipe, but it may not and any problems might not be immediately noticeable (making bug tracking difficult). I would advise you NOT to report bugs if you’ve moved between android versions without a factory reset.
Q: When will they release a version that works on a locked bootloader?
A: Never. Some the features of the ROM simply won’t work very well/at all on a stock kernel. If you are rooted you can simulate some of the features with apps and mods though.
POST-INSTALLATION QUESTIONS
Q: I’ve installed the ROM – I can use Titanium Backup to reinstall all my apps right?
A: Yes and no. They may work fine, they might not – you are better off letting Google’s back up service restore all your apps. If you restore an app using Titanium or similar software and it’s buggy, there’s no point reporting it – re-install the app instead, perhaps even the ROM.
Q: 4G isn’t working – what do I do?
A: It’s not enabled by default on CM10.1 so you must do the following.
Go to the dialpad/phone.
Dial in the this number: *#*#4636#*#* (This will bring up "Phone info").
Tap WCDMA from under "Set preferred network type".
Select "LTE/GSM/CDMA auto (PRL)".
The 4G LTE network should now be activated.
Q:Where’s USB mass storage?
A: After ICS Google stopped including it in their Android builds, as such mass storage mode is not a feature that was kept by CM for Jelly Bean. Individual manufacturers do what they want though, which is why Sony, Samsung and others still have it. Skilled modders may be able to add to ROMS based on this development, I reckon they might be able to patch this one to include it too
Q: This ROM is buggy as hell and drains my battery – how do I let the developers know?
A: Logcat and/or a kernel log - or it didn’t happen for bugs.
Better battery stats for battery drain.
There are lots of guides out there showing you how to take logs and how to record battery stats.
Anecdote – I activated Google+ yesterday as I like the auto-photo upload feature but wakelock detector revealed it was killing my battery (I think it’s dodgy on stock too). The choice was the app or the ROM, I chose the ROM.
Q: After installation something random doesn’t work – what do I do?
A: Check the thread to see if other users have mentioned the issue and to see if the developer has posted a solution. Also, you’re on XDA, you’re an advanced user, you have unlocked your bootloader, thrown out your warranty and accepted the consequences. So please try to resolve the issue yourself. In general if you are having a problem and no one else is, it will be a problem with your phone/download/installation.
Phone - obviously a hardware fault can't be foreseen by the developer and have you unlocked your bootloader!
Download - Most downloads are fine. But I've flashed enough ROMS to know that sometimes a file gets corrupted and sometimes they say they are complete when they are not. Sometimes I've been careless and clicked on the wrong download, sometimes the website hosting the site is haveing a a bad day, sometimes the developer puts the download in the wrong place too The first things to check are the name and size of the file - if these tally you're probably fine to install. If you want to be extra cautious you can check the MD5 hash to see if your download matches. Sometimes the file gets corrupted on upload - nothing anyone can do about that...
Installation - (Please back up your orignal ROM). Typically you'll be installing this ROM using a recovery from another ROM/kernel/MOD - so if you have problems installing , it might be that you have a bad recovery.
The wipes really need to be done to ensure the smooth running of your phone, but as you've backed up, the 15 seconds you spend properly wiping should not be much of a chore.
If you're one of the first downloaders, I guess there is some merit in saying you couldn't install, but if it's been out for a while and there are loads of posts saying 'what a great ROM' there's little point posting 'won't install'. Describe exactly what you've done and someone might help.
Bear in mind there are apps/hardware that the developers of this ROM won’t have heard of/care about - so if something doesn’t work properly on your phone it could be for numerous reasons. Either way, this may be something you have to live with. Alternatively, if the app is essential to you, you’ll have to return to a backup.
Remember this ROM is in development, there are no promises of perfection and no one is forcing you to use it. However, the right kind of feedback is always welcomed by the developers and may be acted on – the wrong kind will often be ignored.
Q: What does a perfect bug report look like?
A: Go here. http://forum.xda-developers.com/showpost.php?p=46935640&postcount=313
Q: What are the known bugs?
A: FM radio doesn’t work.
A: Attempts to offline charge cause the phone to boot.
A: 4G activation is not remembered between boots for CM10.1.
A: For 10.2 there is a known battery drain issue related to WiFi. See the solution here. http://forum.xda-developers.com/showpost.php?p=46923723&postcount=301
The following issues have been reported by some users, but others say it doesn’t affect them. They are regarded as hardware issues – anecdotal ‘me too’ posts will be ignored. However, supply a log and your phone’s date of manufacture and the developer may look into it (this might help you prove that your phone is faulty, so it’s a worthwhile exercise).
Erratic touch screen response.
Reading external SD Card in recovery and in use.
As others have said this is possibly the most stable first CM build they’ve encountered and I agree – it’s definitely suitable for daily use. I've been using it from release and haven't had a single reboot/app crash or freeze.
http://uploaded.net/f/q3au96
CM 10.1 released for huashan
Its cm for our phone right?!??
Sent from my ZTE Blade G using xda app-developers app
Thanks for sharing. I saw yesterday in the changelog that both 10.1 and 10.2 where announced on FXP 242 (10.1 in beta and 10.2 in alpha), but I can't find the 10.2 download anywhere.
Maybe they don't publish public download links for alpha versions ?
Parkside said:
...no announcements, I can't keep it to myself. You'd do the same right?
Click to expand...
Click to collapse
Its safe to download huanshan cm file for our phone.(know that huanshan is code name for our phone)????
Sent from my ZTE Blade G using xda app-developers app
Yes take a look
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Wooohooooo im so happy i cant wait to test itThanks to FXP team !
When i flash it im gonna make review wohoooooo
Sent from my ZTE Blade G using xda app-developers app
---------- Post added at 12:06 PM ---------- Previous post was at 11:58 AM ----------
karma123 said:
Yes take a look
Click to expand...
Click to collapse
Can you tell me what file to download??
Sent from my ZTE Blade G using xda app-developers app
Download this :- http://uploaded.net/file/7ntq0zp6/from/q3au96
Flashed and booted. Its nice. But some screen flickering while scrolling. Like in settings etc etc. But that can resolve with enable the " Disable Hardware Overlay" option from Developer Settings
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Are mirrors allowed? Can somebody mirror this file? Im sorry but uploaded has failed me several times already...
mmm273 said:
What about performance ? Can you run antutu bench ? how much is free / used RAM ? etc.
thanks
Click to expand...
Click to collapse
Now only i flashed this. I dont have any apps installed. So performance is awsom now. Free RAM is 509 and used 333
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Screen Flicker
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
I have the flickering too ! And the phone often soft freezes. Seems like the app isnt updated anymore on screen. It can also be just the keyboard for example. Hiting recent tasks unfreezes it but systemui sometimes freezes until reboot.
Sent from my C5303 using xda app-developers app
uberlaggydarwin said:
Hi @Rajeev
I didn't experience screen flickering at ALL in ANY test builds so I find this really difficult to believe but I'm happy to take a detailed look at it ..
Log's plus video(so I can see what you mean) would be useful so I can get this possible ?issue? and if it is an issue then I'll get it resolved.
None whatsoever for me so this is a really weird issue....
Thanks
Click to expand...
Click to collapse
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
mmm273 said:
ok, only for compare - what antutu score ? With stock ( fresh flash) i have 21 000...
Click to expand...
Click to collapse
I'd like to see a screen of that score. Seems a bit too high. Sure you have the SP ?
You're using V4 ofcourse, my bad.
Bootloader
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Hey, Make a backup, you need an unlocked bootloader for this. Then wipe all cache and data etc. then flash the rom on your phone
jakelooker said:
Just wondering if you are guys are using locked or unlocked bootloader? I'm locked with CWM and I'm wondering what the process would be of installing... (e.g. wiping /data...)
Click to expand...
Click to collapse
Well asfaik CM requires a custom kernel which can only be installed on a phone with unlocked bootloader. Hope ive helped.
Rajeev said:
Hi Bro @uberlaggydarwin
Yes i am saying truth only.
1) While Scrolling in settings Its flickering like waves. But its not coming after Click the " Disable Hardware Overlay" Function.
2) When i press the Reboot option its rebooting but its rebooting like something weird in Screen..
3) Soft reboots happens multiple Times...
I know its a Beta release. I am not complaining . But answering ur question...
Click to expand...
Click to collapse
LOG"S OR IT DIDN"T HAPPEN . I'm serious.
I'm downloading this release to test but I can't help much if you don't provide logs.
Are you sure its not auto-brightness being turned on as auto-brightness doesn't work very well in stock so the changes are probably more noticeable.
Reboots work perfectly fine for me..
On the recent test builds I haven't had a reboot issue but as you know the kernel is temporary so I'll redo it when 4.3 comes out....
WE NEED LOGS.
This is the thread for the T599x variants (not the S3 mini).
We have the following ROMs available:
Stock
The following have ceased development:
CM 10.1 (09/20) Build by Unjustified Dev
CM-10.2 by Unjustified Dev
Pac Rom by Unjustified Dev
BeanStalk 4.4 by Meticulus (Still good to try out!)
CM-11 by Unjustified Dev + Exothermic
The following have active development:
AOKP4.4 by dadacup
Carbon 4.4 by Meticulus
CM-11 by dadacup
Omni 4.4 by Exothermic
VanirAOSP 4.4 by Unjustified Dev
We also have the following recoveries available:
Stock
CWM Touch Recovery
TWRP Touch Recovery
Philz Recovery
Check the links of the 4.4 based roms for more current recoveries!
Also check out this guide on how to increase space (enables link2sd) : http://forum.xda-developers.com/showthread.php?t=2596290
All credits to tys0n (for index of stock roms) and Unjustified Dev (for CM10.1, CM10.2, CM11, VanirAOSP, and his initial work on our devicies), Meticulus for (CWM, BeanStalk and Carbon, and for his continued work on our device), dadacup (for his work on AOKP and CM11) and morepr for creating the guide to enable link2sd)
-------------------------------------------------------------------------------------------------------
Use this thread as a general discussion thread.
I'll help maybe this weekend. I am busy for the week.
So I installed CM 10.1 on my phone and now it says it can't find any contacts on my SIM card. Is this just an issue with CM 10.1, or did installing it delete the contacts?
ClaireVoyant94 said:
So I installed CM 10.1 on my phone and now it says it can't find any contacts on my SIM card. Is this just an issue with CM 10.1, or did installing it delete the contacts?
Click to expand...
Click to collapse
Apparently it's an issue with jellybean rather then CM0.1; some fixes might be try inserting your sim card into a spare phone that uses a lower version of android (gingerbread/froyo/ics) or a different os and save the contacts there, and send them over text or bluetooth.
So I found another problem with CM 10.1: I can't use my SD card. It gets recognized under Settings -> Storage, but I can't play music from it, and I can't view files in it from the file browser. Is this a known issue (one that other people are experiencing) with the 9/20 build of CM 10.1 for this phone, and if so, is there a later build that fixes it?
It's not a big deal since all of my music is on an iPod I carry with me (usually), and I don't do anything else on my phone that needs more than a few MBs of space, but it's annoying.
ClaireVoyant94 said:
So I found another problem with CM 10.1: I can't use my SD card. It gets recognized under Settings -> Storage, but I can't play music from it, and I can't view files in it from the file browser. Is this a known issue (one that other people are experiencing) with the 9/20 build of CM 10.1 for this phone, and if so, is there a later build that fixes it?
It's not a big deal since all of my music is on an iPod I carry with me (usually), and I don't do anything else on my phone that needs more than a few MBs of space, but it's annoying.
Click to expand...
Click to collapse
I'm on the 09/20 build and SD card works fine. Perhaps you need to format your sd card so that its compatible with android; I believe it should be formatted to FAT32, and try using Root browser (free from play store) and go to extSdCard and the files should be there given that the sd-card is working. There are more builds after 09/20 but since the original dev has not reuploaded them to goo (or goo has deleted them by accident) we're stuck with 09/20 until I can build a version of cm myself (I'm somewhat close to it).
I have a few of these phones and they are great, I cant believe we don't have more devs on these for a clean unbloated rom. Let us know if you come up with something. :_)
Just a quick update; I'm done exams which means I could start my attempts at porting over CM10.2 again. I had some issues applying a patch needed to enable STE Hardware, so I just manualIly downloaded the files to the correct places for the time being (which should get help me get past the build-error I was seeing before). I'm compiling a build now, and hopefully I don't run into any build errors and can test in on my phone.
Exothermic said:
Just a quick update; I'm done exams which means I could start my attempts at porting over CM10.2 again. I had some issues applying a patch needed to enable STE Hardware, so I just manualIly downloaded the files to the correct places for the time being (which should get help me get past the build-error I was seeing before). I'm compiling a build now, and hopefully I don't run into any build errors and can test in on my phone.
Click to expand...
Click to collapse
Cool! Looking forward! Thanks for the update.
Sent from my SGH-T599N using XDA Premium 4 mobile app
Is pac the only legit rom available for this phone? I'd really like to see a stock version of jelly bean...
DevilDogg said:
Is pac the only legit rom available for this phone? I'd really like to see a stock version of jelly bean...
Click to expand...
Click to collapse
There is stock firmware, unless you mean an AOSP version? I don't think any of the U8500 based phones have AOSP built, so porting it over would be difficult. There's also CM10.1 available for the phone with working camera (no video camera), issues with audio at times (which requires a reboot). I'm working on CM10.2, but running into some kernel issues, so I yet have to see to how that goes.
Exothermic said:
There is stock firmware, unless you mean an AOSP version? I don't think any of the U8500 based phones have AOSP built, so porting it over would be difficult. There's also CM10.1 available for the phone with working camera (no video camera), issues with audio at times (which requires a reboot). I'm working on CM10.2, but running into some kernel issues, so I yet have to see to how that goes.
Click to expand...
Click to collapse
I managed to find an odin flashable rom somewhere that includes su so that's what I'm running in the mean time. I tried both the roms in the o.p.
Pac was pretty close to what I like in a rom but it's abandoned so there's no chance of the bugs getting fixed.
This is such a great little phone and now that metro is giving them away for free I assumed xda would be blowing up with development but I guess not...
I'll be checking this thread everyday and I'll test out any thing you come up with. really looking forward to your rom.
I managed to compile CM10.2 and it did indeed boot. I'm not yet releasing it because camera is missing. But other then that everything seems fine, does require more testing, and I've been working non-stop for a couple of hours now (it's 4am here, lol).
Edit:
Changelog:
V.1.0.0
- initial build of CM10.2
- SmartAss v2 governor (should help with battery life) (unjust already had this there, and I could add in other governors in future)
List of Current Bugs:
- missing camera (have an idea on how to fix it )
- random boot logo appears (i believe this was on pac as well, will look into it)
- torch not working (dependent on camera working as well but since camera isn't working, torch isn't working as well)
- sound issues (like CM10.1 most likely)
I'll make a new thread for this rom, once camera is working, and we could start from there. I've yet to test out calling and bluetooth.
Just a reminder; I'm learning how to dev as I'm going so please don't expect nightlies (slow upload rate + lack of free time + lack of knowledge) and fixes to be posted suddenly.
Excellent. and thanks for not adding another half baked ROM to the list.
DevilDogg said:
Excellent. and thanks for not adding another half baked ROM to the list.
Click to expand...
Click to collapse
+1
SWisaiahAG said:
+1
Click to expand...
Click to collapse
nice job @Exothermic
Camera and what not is easy haha your missing more than you know
add me on hangouts [email protected]
I'll add you to teamcanjica they work on ste devices.
Unjustified Dev said:
nice job @Exothermic
Camera and what not is easy haha your missing more than you know
add me on hangouts [email protected]
I'll add you to teamcanjica they work on ste devices.
Click to expand...
Click to collapse
Thanks, and aha, yeah I figured. Originally one of the patches for multimedia didn't go through, so I figured that was the culprit, but now that I applied and recompiling, I'm running into more build errors, but I'll get through them.
I just messaged you,
Unjustified Dev said:
nice job @Exothermic
Camera and what not is easy haha your missing more than you know
add me on hangouts [email protected]
I'll add you to teamcanjica they work on ste devices.
Click to expand...
Click to collapse
@Unjustified Dev Thanks for helping @Exothermic. I'm sure he and the whole T599 community would highly appreciate your support on getting an updated CM ROM with less bugs. Thank you again. As always if you need help with testing I'm here for you.
Sent from my SGH-T599N using XDA Premium 4 mobile app
DJVargas said:
@Unjustified Dev Thanks for helping @Exothermic. I'm sure he and the whole T599 community would highly appreciate your support on getting an updated CM ROM with less bugs. Thank you again. As always if you need help with testing I'm here for you.
Sent from my SGH-T599N using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If anyone is interested: I still have a copy of the cm-10.1-20130925-UNOFFICIAL-codinamtrgapps-jb-20130812-signed.zip with gapps files. This wast the last build i believe unjustdev was working on before he moved to PAC...this build has a functioning camera, but no video and the sound issues. I would be happy to upload, let me know.
If u have the out of space issue I created this quick tutorial that it might help some of you guys if it does please click thanks
http://forum.xda-developers.com/showthread.php?t=2596290
Sent from my SGH-T599N using XDA Premium 4 mobile app
For those that don't know what evervolv is, Evervolv is an AOSP (Android Open Source Project) rom. We're fully open sourced and encourage it with no restrictions. The work put into this rom is community driven and and Evervolv Project is made up of numerous members and contributors.
Right now the current source we are working on is KITKAT(Android 4.4.4).
Current version: 4.0.0p1
Current Items not working/Buggy
Updated 4-4-14
Bluetooth working --Still a WIP as some devices don't connect
Camera working --Still a WIP as the camcorder records in blue and a few minor issues
home key doesn't turn device on need to use power button--FIXED in the next nightly should be 4-5-2014
Battery draw around 50mA in sleep
Some experience SOD when hotword detect is active
Location service has stopped with Googles update looking into now
You tell me what you find.
4G Models are not currently supported
Click to expand...
Click to collapse
Evervolv Github: https://github.com/Evervolv
Evervolv Gerrit: http://review.evervolv.com/
Evervolv website: http://www.evervolv.com/
(New Site is up Check it out)
Evervolv Bug Tracker: http://bugs.evervolv.com/
(Please have discretion when reporting issues, and be descriptive / helpful. Also understand that we'll have some growing pains with this. So don't expect everything to be perfect.)
Twitter: https://www.twitter.com/wbellavance
IRC: #evervolv
Click to expand...
Click to collapse
[GPL Compliance]
Kernel Source
Click to expand...
Click to collapse
[Download]
If you already have evervolv installed you should see this build under testing if you refresh and can download that way.
No more nightlies Moved to 5.0 Lollipop
ev_tenderloin-1-23-15 Last and final for 4.0 -> Fix netflix
FLINTMAN-TWRP-touch-data_media-SELINUX-2.7.1.0-6-7-2014.zip
--This is a flashing TWRP recovery with data/media and SELINUX support. I have tested 100% of the features and everything is working great as far as i can tell. Soo
with that being said. Use at your own risk 8). Make sure you save a backup from your current recovery just in case. BACKUP BACKUP BACKUP
--Broke Vibration as i updated kernel.
Click to expand...
Click to collapse
NOTE: Recommend a clean install if moving from a previous version and or another ROM.
Flashing from cm or any other ROM will require a clean install, dirty flashes can cause random reboots and random errors
[Disclaimer]
I am not responsible for bricked devices, lost data, etc, etc. You all know the drill. BACKUP BACKUP BACKUP
Click to expand...
Click to collapse
[Special Thanks]
i would like to thank Flemmard, Jcsullins, Dorregaray, Invisiblek, Milaq, and anyone else that helped to make this happen. More great work to come.
Mitchbaria --for a 4g model to start in on this
Colchiro-- For a spare Touchpad WIFI to be able to test on one and develop at the same time
Click to expand...
Click to collapse
GAPPS
---These are the gapps i use. You should be able to use any that are KitKat compatible
http://forum.xda-developers.com/showthread.php?t=2397942
Grabbing logcats and dmesg along with last_klog.
These are helpful in figuring out what is going on
Install the sdk in you PC http://developer.android.com/sdk/index.html
Logcat
"adb shell logcat >logcat.txt"
This will run until unplugged or ctrl c and all the content will go into that file
dmesg
"adb shell cat proc/kmsg >dmesg.txt"
This will run until unplugged or ctrl c and all the content will go into that file
Last_klog
"adb shell cat proc/last_klog >lastklog.txt"
This is for if you have a reboot run this right after the device starts back up and it will get me the last dmesg from before it reboot and will help determine the cause of the reboot.
This will help me and everyone that uses this ROM as i can determine the cause of issues.
Thanks
Thank you for the continued HP Touchpad Development and support Flintman.
Cheers:highfive:
Touchpad Toolbox By Jcsullins
[ROM GUIDE]How to use the TouchPad Toolbox to install Android "The Super Easy Way"
[GAPPS][4.4.x/4.3.x] OFFICIAL 0-Day PA-GOOGLE APPS (Use Mini or Micro packages)
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Moody66 said:
Thanks to both of you. For the roms and the video walk thru. I haven't tried art on the touchpad because it actually makes my Galaxy Nexus slower most of the time. And with some gapps it's even worse. Since it isn't listed as broken I am assuming you have tried it. If I may ask. What gapps did you use and what was performance like? It prevented my nexus from booting at times. Just wanna stick with what you have tried until I get use to the new data media and such. Thanks again.
Click to expand...
Click to collapse
I haven't tested as its still a wip from Google. I do have it as broken in the op. But good to know that it boots 8)
Sent from my SCH-I545 using xda app-developers app
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
flintman said:
Added another build see OP for what was changed. I also adding in a touch recovery TWRP with data/media and SELINUX support. This will also allow you access to your webOS media folder which is know in the new build as external_sd. I have tested out all the features and everything is working great but please save a full backup from your previous recovery if you decide to use this recovery as it's still in an Alpha state.
Enjoy
Click to expand...
Click to collapse
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
I have flashed with this recovery about 20 times now and only got the reboot to hang once. I'm looking into it.
Lyok0ne said:
Thanks a lot for this amazing ROM and the recovery I had few bug with the reboot ... The recovery freezed and i have to manually reboot to unfreeze it ... A part from that great job Can't wait to see what you are going to bring next
And just one little request ... I love having the clock center on the status bar ... Do you think you can add it to the Evervolv project ? That's would be a great feature
Click to expand...
Click to collapse
install xposed + gravitybox. it works like a charm and has this feature and many others.
Sent from my Nexus 4 using Tapatalk
Okay, I am doing something wrong. I have downloaded the recovery multiple times from multiple devices. I have tried installing via TWRP and manually extracting the image to /boot.
Each attempt, I get:
Checking uImage... Invalid Size
BOOT FAILED!
Please SELECT to continue
Any thoughts? I can still load my backup copy of TWRP without issue.
Update:
After purging the other copies of TWRP from /boot, the new version loads without issue. Thanks flintman!
Discovered that the TP 4G not compatible with the test 3.X Kernel yet
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
If we flash your twrp will it remove cwm or add another entry? I've never been able to have two recoveries working. I would much rather not have to use the power button and what not all the time in cwm but want to make sure I'm covered if something goes wrong. Thanks
Sent from my TouchPad using Tapatalk
Due to the limit of the boot directory it will remove all recoveries before installing this one.
Sent from my SCH-I545 using xda app-developers app
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
SteveoSupremo said:
Sorry for the Nube question I've searched and I'm sure it's been answered already....
So I got my touchpad with ClockworkMod Recovery version 6.0.1.9 can I flash the TWRP SE data/media recovery from there? Trying with the acme installer 5ET has failed.
I do have the original 4.4 Evervolv up and running and my partitions have been updated.
Thanks
Steve
Click to expand...
Click to collapse
So I replaced the ulimage in the boot directory and was able to install the 1/10/14 rom. So I guess I needed to search and just try a little more.
anyway -- I think it's a little slower than the first 4.4 version.... Maybe I need to reboot.... thoughts?
steve
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
I am curious. Have you tried turning the 4g off. Like airplane mode then just turning wifi back on? Was thinking of getting one of these models to tinker with.
Moody66 said:
Both using same cpu settings? Although with more things implemented it could seem slower.
---------- Post added at 01:11 AM ---------- Previous post was at 01:07 AM ----------
Click to expand...
Click to collapse
I think it was because of sync.... it's running smooth now. after I loaded a different set of GAPPS.
Now I have to figure out the camera apk. it would help if I RTFM.... Thanks Flintman for the awesome update!
Which version of gapps is recommended for 01-10-14 version?
New Test build up which fixes vibration
emph4tic said:
Hey Flintman just wanted to point out my findings after going crazy over the past couple weeks trying to figure what I was doing wrong when flashing the test Kit Kat ROMs w/3.X kernel.
Previously my TP 4G was working fine on shumash's SCHIZOID 4.2.2 ROM but I was extremely eager to try out the new 3.X kernels. I first tried out your non-data/media Evervolv 4.0.0p1 version and was unable to connect to WiFi despite repeated clean install methods and variations of cache wipes. I know that I had re-sized partitions with Tailor sufficiently for Kit Kat as warned so I then attempted to try out Invisblek's CM11 ROM. Not only was WiFi still not wanting to toggle on, but the rotation sensor was acting oppositely for landscape orientations and I was getting frequent crashing reboots just going through the UI. I then decided to try out JCSullins' updated CM10.1 ROM with his 3.0 kernel and then encountered the same behavior as Invisblek's CM11 ROM, but with even worse random touch driver issues that resulted in erratic automatic screen touches and ultimately soft-reboots.
Restoring a backup to SCHIZOID's 4.2.2 ROM worked fine to restore all functionality, but I couldn't help but think that I was still doing something wrong.
I got a hold of a normal TP (WiFi only model) and tried your latest 1-10-2014 Evervolv 4.0.0p1 ROM and was amazed to see that it was working great including WiFi (although 5GHz APs don't seem to scan as reliably as the past kernel) aside from the known issues. I tried the exact same install process on my TP 4G again just to see if anything changed, but unfortunately WiFi still wouldn't toggle and the orientation sensor behavior exhibited the same opposite landscape behavior as Invisiblek and JCSullins' ROMs.
I had thought that aside from the 3G HSPA modem in the TP 4G model chipset-wise it would be identical to the WiFi-only model so kernel 3.X developments would be complimentary across all TP devices. Unfortunately this doesn't appear to be the case and I hope with time you guys are able to work out any compatibility with the 4G model to benefit from the already terrific development that's going on with the 3.X kernel now.
I admire your guys' skills and look forward to all the improvements in store!
PS: I'd be more than happy to beta test anything you guys feel would address any compatibility issues on the TP 4G!
Click to expand...
Click to collapse
Do you think you can get me some dmesg and logcats??
In spite of the declining official and unofficial support and development of our device, there are several new and excellent ROMs available. However, for various reasons, they might not be easy to find, (a couple don't have their own threads on xda, and one is hidden in a q&a thread). I thought it would be helpful to make a Z1c MM resource thread.
1. Vanir - Team Vanir released the first MM ROM for Z1c, (AFAIK), and is currently developing 2 MM roms, Vanir and Commotio. There is no official xda thread for them. Both seem stable and smooth, but as of 5/4, Vanir ROM is still without camera. Update - 5/12 build with working camera, quality similar to other CM.
http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/amami/
http://www.emccann.net/dho/3-Vanir-mirror/4-nighties/
And gapps - http://www.emccann.net/dho/5-Gapps/
G+ page - https://www.google.com/url?q=https:...ggcMAA&usg=AFQjCNGnu0diBIp4Tq1K-8Bap0HCDxw_TQ
2. AOKP - Still no working official build, but may be coming. Meanwhile, @championswimmer has built one.
http://forum.xda-developers.com/son...ent/aokp-mm-6-0-1-unofficial-nightly-t3311699
3. Resurrection Remix - A well known favorite of many. All the customization you could want.
http://forum.xda-developers.com/son...resurrection-remix-marshmallow-amami-t3325195
Update by @david320te - http://forum.xda-developers.com/showpost.php?p=66899475&postcount=121
4. AOSP by @CLINTZ9 - Probably my personal favorite so far. Good camera, and RRO layers support. Latest build is update 4, which has issues in /system. I recommend flashing update 3, with boot IMG from update 4, (make sure to flash sim fix).
Thread also has a build by @munjeni in post #245, which he says shows serious errors in dmesg, and which has the same problems in /system as update 4, (at least non-working auto-rotate).
http://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/aosp-t3317511
5. AOSP by @freexperia - just found out about this, haven't tried yet. No xda thread. Download from fxpblog. Currently only hosted on uploaded.to, so expect 1-2 hour download time. They did finally get around to using AFH with their 5.1 builds, so maybe they'll do that with this one too at some point. Update- been using last build for a day, (5/4 I think), and very solid. Camera is good and everything seems working.
http://fxpblog.co/aosp/aosp-6-0/ (look for Amami).
I deodexed system folders, (7/17 build), if anyone wants - https://drive.google.com/file/d/0B1niPALD2vPedDlSUEs2bHhhUWM/view?usp=drivesdk
6. CM13 - @derf elot took the initiative in the middle of a q&a thread about the lack of CM13 for Z1c, and posted a build. So far so good, and he's working on an update.
http://forum.xda-developers.com/showpost.php?p=66506018&postcount=8
7. Omni by @erikcas - thanks for reminder from @alf-endy. An older build. I tried it when first released, but don't really remember much. Check post #73 here ...
http://forum.xda-developers.com/son...lopment/omnirom-5-1-unofficial-t3190451/page8
8. DU - just posted 5/11, haven't tried yet... Will update. Update 5/12 - ROM is nice and smooth with lots of customization. Camera seems buggy, even though seemed to be able to take good pictures. It just wouldn't yake them sometimes, or flash at the wrong time, etc. Update 5/19. New build, camera improved.
http://forum.xda-developers.com/son...pment/rom-dirty-unicorns-v10-2-amami-t3376938
9. AICP - Personal build by @SpiritCroc. Haven't tried it yet. Update 5/12 - Nice ROM. Everything working well as far as I can tell. Camera quality not so good, probably due to outdated CM camera files.
http://forum.xda-developers.com/showpost.php?p=66814852&postcount=30
Update 7/29 - AICP now has a thread - http://forum.xda-developers.com/son...lopment/rom-aicp-11-0-mm-6-0-1-amami-t3428288
10. CM 13 by @CLINTZ9 posted yesterday, haven't tried yet.
http://forum.xda-developers.com/sony-xperia-z1-compact/orig-development/cm-13-0-amami-t3377635
11. AOSPA by Paranoid Android. Official build just released - https://plus.google.com/+EvanAndersonA/posts/72TLZMj4K5S Flashed today and working well. Camera is good and 3rd-party cameras work. Built-in camera froze on me several times, but other apps didn't. Not much built-in customization options, pretty much straight AOSP, but with CM themes.
12. CM13 by @SouthernPacific - haven't tried it yet, but reports are that in-call echo found in some other custom Roms is fixed here. http://forum.xda-developers.com/sony-xperia-z1-compact/general/rom-cm-13-amami-t3459617
I think that's all I know of so far. Let me know if I missed anything, or other ideas, etc...
p.s. - if there's not a specific gapps link in the ROM thread, you can probably use Opengapps.
https://www.google.com/url?q=http:/...ggbMAA&usg=AFQjCNEV401XzT6BiV_vnUgQH9s9qdQybA
p.p.s. - Here's some links to useful mods/add-ons for AOSP and DU roms:
- Modified kernel and camera upgrade by @maz-1 - http://forum.xda-developers.com/son...kernel-exfat-support-mtkcamera-dirty-t3388396
- NFC files, (not included in AOSP for some reason) - http://forum.xda-developers.com/showpost.php?p=67128642&postcount=68
- There's an issue with gapps on MM, where, if you don't flash gapps with the original clean flash of the rom, Setup Wizard will fc at boot, and you'll be stuck there. If you do boot your rom without gapps, you can either: a) boot into recovery and use file manager to delete setupwizard apk from /system/priv-app, (which will probably work fine, but on one occasion I got bugs with Gplay services after doing that), or, b) just reflash system, (dirty), when flashing gapps, (this seems better, but you'll have to reflash any other system mods you may have made, like supersu or Xposed, etc.).
- to enable using 3rd-party camera apps on Vanir and DU, edit build prop according to this - http://forum.xda-developers.com/showpost.php?p=67783086&postcount=233 (by default, you will get only black screen). Note that this will remove camera api2 features
Great Idea!
Unfortunately the Camera for RR-M has stopped working for me (using at as a daily driver right now). Battery is great, but only after a few days...the first few days were horrible. (No idea why)
I couldn't get AOSP from @cliTNZ9 running, Maybe i'll try the one from @freeexperia
CM13 looks promising, but the Blobs are a few weeks behind, so the camera is also crap...
Haven't tried AOKP.
david320te said:
Great Idea!
I couldn't get AOSP from @CLINTZ9 running, Maybe i'll try the one from @freeexperia
.
Click to expand...
Click to collapse
Look here - http://forum.xda-developers.com/showpost.php?p=66177015&postcount=111 This should get it to boot. If you don't have new BL, you may need to use fastboot to temp-flash kernel and recovery for installing su, etc. With new recovery, just flash ROM, power off, boot into recovery and flash others.
Hi, just to let you'll know - I've been running the 4/24 build of MM from fxp, and it runs great! I haven't even gotten a reboot for a few days now (but it still happens randomly). Also, there's isn't any auto-rotation issue. The only thing not working from what I can tell is the NFC and FM radio chip. Camera is excellent for it not being official.
MicroClue said:
Hi, just to let you'll know - I've been running the 4/24 build of MM from fxp, and it runs great! I haven't even gotten a reboot for a few days now (but it still happens randomly). Also, there's isn't any auto-rotation issue. The only thing not working from what I can tell is the NFC and FM radio chip. Camera is excellent for it not being official.
Click to expand...
Click to collapse
Good to hear. Interesting about NFC - I haven't even seen it in settings options yet on AOSP, never mind working. I wondered if it was phasing out or something... I've also been impressed with current AOSP camera. Funny BC they never got anywhere with the camera on LP
Thanks for your instruction.
But you know how is instruction to flash vanir?
Need I the boot.img?
Thanks
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
Jesusnagler said:
Thanks for your instruction.
But you know how is instruction to flash vanir?
Need I the boot.img?
Thanks
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
Click to expand...
Click to collapse
Full wipe, flash ROM zip, flash gapps zip, reboot.
Thanks
Has any one test it
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
download from uploaded.to is a nightmare
Could anyone that is happy with their sound/volume upload the ’mixer_paths.xml’, please!! It can be found in '/system/etc
I've tried a couple MM roms now (currently testing aosp from fxp), but outgoing calls are always too low and the other person can hear their echo if I put them on speaker.
So please check this before posting anything..
Thanks a lot!
Thanks! Someone has tried Omni-6.0.1 by erikcas?
Jesusnagler said:
Thanks
Has any one test it
Sent from my Xperia Z1 Compact using XDA-Developers mobile app
Click to expand...
Click to collapse
As is stated, Vanir ROMs are very good but still no working camera. I've been in communication on G+, and dev has linked me a teat version. Going to try today.
alf-endy said:
Thanks! Someone has tried Omni-6.0.1 by erikcas?
Click to expand...
Click to collapse
Thanks for info. I loved his Omni 5.1, (he was also the first to get AOSP camera going on 5.1), but I haven't seen an update to the thread for quite a while. Have a link?
alf-endy said:
Thanks! Someone has tried Omni-6.0.1 by erikcas?
Click to expand...
Click to collapse
I got your pm. Funny thing - I actually did know about that, I even posted there after trying it out. I just forgot. I'll update op with your link.
Ænimal said:
Could anyone that is happy with their sound/volume upload the ’mixer_paths.xml’, please!! It can be found in '/system/etc
I've tried a couple MM roms now (currently testing aosp from fxp), but outgoing calls are always too low and the other person can hear their echo if I put them on speaker.
So please check this before posting anything..
Thanks a lot!
Click to expand...
Click to collapse
just tried FXP s AOSP_M_160502_amami
(i believe it is the latest)
and the problem with the other person hearing his echo still there.
if you do something with sound post it pls:good:
broky said:
just tried FXP s AOSP_M_160502_amami
(i believe it is the latest)
and the problem with the other person hearing his echo still there.
if you do something with sound post it pls:good:
Click to expand...
Click to collapse
That's the rom I'm on right now. Will try mixer_paths.xml's from lollipop roms as well, if I find an old backup.. Let's hope devs will look into it for future releases.
Currently testing AOSP from freexperia. So far so good. Camera is good and everybody working.
levone1 said:
Currently testing AOSP from freexperia. So far so good. Camera is good and everybody working.
Click to expand...
Click to collapse
I'm really interested. Please keep us posted how it goes and if there are any bugs or things not working, like Bluetooth, NFC etc.
Sent from my Xperia Z1 Compact with XDA app.
skyhirules said:
I'm really interested. Please keep us posted how it goes and if there are any bugs or things not working, like Bluetooth, NFC etc.
Sent from my Xperia Z1 Compact with XDA app.
Click to expand...
Click to collapse
So far, 1 random reboot, with no mods to system. Besides that, no problems. BT seems good, (screenshot). As far as NFC, I have not seen NFC option in settings on any AOSP MM build yet, not sure why.
levone1 said:
So far, 1 random reboot, with no mods to system. Besides that, no problems. BT seems good, (screenshot). As far as NFC, I have not seen NFC option in settings on any AOSP MM build yet, not sure why.
Click to expand...
Click to collapse
As others pointed it out specifically, how is call quality?
Hey guys!
To prevent the other CM14.1 thread from getting too crowded I'll be putting my own builds up here
These builds will be based on the official source except I'll keep adding in new features and fixes before they're officially merged, and I'll be putting in some other small changes along the way if I feel they improve the experience without compromising on anything else
Currently working:
//All battery status indicators are fixed
//Pocket mode
Modifications:
//'Unofficial' tag removed from CyanogenMod version. It just made me squirm with the lack of aesthetic. Of course this is still an unofficial version!
Updated (//): 16.11.03
Download link: https://drive.google.com/open?id=0B88aOagl9VcCV3YtNFpwRzR1akk
Credit of course goes to CyanogenMod and all of its contributors for all of their work!
Disclaimer:
This software is provided by me "as is" and "with all faults." I make no representations or warranties of any kind concerning the safety, suitability, lack of viruses, inaccuracies, typographical errors, or other harmful components of this software. There are inherent dangers in the use of any software, and you are solely responsible for determining whether this software is compatible with your equipment and other software installed on your equipment. You are also solely responsible for the protection of your equipment and backup of your data, and I will not be liable for any damages you may suffer in connection with using, modifying, or distributing this software.
XDA:DevDB Information
CyanogenMod14.1-cohaolain, ROM for the OnePlus 3
Contributors
cohaolain
Source Code: https://github.com/cohaolain
ROM OS Version: 7.x Nougat
Version Information
Status: No Longer Updated
Current Beta Version: 7.1 (CM14.1)
Beta Release Date: 2016-11-04
Created 2016-10-31
Last Updated 2016-11-12
First...!!
Will definitely try it out.
Peace
Call Echo and no audio in video chat apps fixed ?
Two things that not allowing me to return to 7.1
Thanks for building and sharing your builds.
Btw are you open to suggestions or requests?
Nice work!
Can you remove cm setup wizard? Cos I'm a Chinese, and if I flash gapps, I can't pass it. And set selinux to permissive?
Thinks a lot!
silentvisitor said:
Call Echo and no audio in video chat apps fixed ?
Two things that not allowing me to return to 7.1
Thanks for building and sharing your builds.
Btw are you open to suggestions or requests?
Click to expand...
Click to collapse
In my testing I haven't experienced any call echo. And I can't test video chat apps right now, so you'd have to check for that yourself mate, or wait for someone else to let you know here, sorry about that
No problem anyway mate, I'm only doing this on a learning curve. That said, I'm open to suggestions and requests, but they should be submitted without much expectation. This is my first ROM, and I'm pretty new to Android development. I can try my best, but I'm no expert. Although I do love a challenge, I can't make any guarantees
But for now I'm going to try and get Google Assistant working by default. We'll see after that
Great! When I have time I'll definitely give it a try.
Sent from my iPod touch using Tapatalk
revive111 said:
Nice work!
Can you remove cm setup wizard? Cos I'm a Chinese, and if I flash gapps, I can't pass it. And set selinux to permissive?
Thinks a lot!
Click to expand...
Click to collapse
Sorry mate, but I don't want to make such drastic changes, particularly ones that most people don't need
I think the setup wizard should stay, and that selinux is fine just the way it is.
Also, I'm not completely sure how to do either of these things anyway....
Can you include your personal Github sources such as device and kernel tree in the 1st post to actually see what changes you've done so far at the moment?
cohaolain said:
Sorry mate, but I don't want to make such drastic changes, particularly ones that most people don't need
I think the setup wizard should stay, and that selinux is fine just the way it is.
Also, I'm not completely sure how to do either of these things anyway....
Click to expand...
Click to collapse
OK,fine.
In cm13, I can pass it without anything, just wait cm to fix this bug.
Thanks for this! :good:
saayuj98 said:
Can you include your personal Github sources such as device and kernel tree in the 1st post to actually see what changes you've done so far at the moment?
Click to expand...
Click to collapse
As soon as I've learned how to do that, I will do that.
If somebody could help me with this it'd be appreciated:
When ro.product.model=Pixel XL is added, 'Device model' in settings>about phone changes to Pixel XL, but when it's removed completely, it reverts back to ONEPLUS A300*.
Question is, when building, how can I make it skip checking the build.prop for the device name and just make it select the device name it defaults to when it's not specified in the build.prop, and where is this check located in source?
Thanks,
Ciarán
cohaolain said:
If somebody could help me with this it'd be appreciated:
When ro.product.model=Pixel XL is added, 'Device model' in settings>about phone changes to Pixel XL, but when it's removed completely, it reverts back to ONEPLUS A300*.
Question is, when building, how can I make it skip checking the build.prop for the device name and just make it select the device name it defaults to when it's not specified in the build.prop, and where is this check located in source?
Thanks,
Ciarán
Click to expand...
Click to collapse
I think its not possible( maybe I'm wrong in here) to change device model when you're building as it might create errors during build process. You might need to create a separate bash script I believe, for users to change that afterwards while flashing the ROM. Or create an Aroma Installer to give user an option to do that if he/she wants to.
which gapps should i flash opengapps 7.1 nano or opengapps 7.1 pico ?
Ashish Bhalla said:
which gapps should i flash opengapps 7.1 nano or opengapps 7.1 pico ?
Click to expand...
Click to collapse
I use pico gapps everytime(I like my system being less bloated). Nano is a good option too.
I suggest you to go with Nano.
Ashish Bhalla said:
which gapps should i flash opengapps 7.1 nano or opengapps 7.1 pico ?
Click to expand...
Click to collapse
I recommend pico, but nano is fine if you don't want Google Now, or Now on Tap, or Assistant and stuff.
saayuj98 said:
I think its not possible( maybe I'm wrong in here) to change device model when you're building as it might create errors during build process. You might need to create a separate bash script I believe, for users to change that afterwards while flashing the ROM. Or create an Aroma Installer to give user an option to do that if he/she wants to.
Click to expand...
Click to collapse
Possibly yeah.
I ran a build that included the two lines to enable Google Assistant, it just ended up discarding the Pixel XL line like it had never been put in there at all.
Google Assistant ran fine for a while, until I cleared Google''s data. Assistant comes up straight after the wipe, but goes back to Now on Tap again afterwards.
Can i install aroma installer open gapps 7.1 on this? If yes how.. I flashed it on this rom but then on booting google services are crashing continuously play store is also not opening.. So some can help plz on this?
cohaolain said:
Possibly yeah.
I ran a build that included the two lines to enable Google Assistant, it just ended up discarding the Pixel XL line like it had never been put in there at all.
Google Assistant ran fine for a while, until I cleared Google''s data. Assistant comes up straight after the wipe, but goes back to Now on Tap again afterwards.
Click to expand...
Click to collapse
Maybe init.d
---------- Post added at 04:42 PM ---------- Previous post was at 04:40 PM ----------
cohaolain said:
In my testing I haven't experienced any call echo. And I can't test video chat apps right now, so you'd have to check for that yourself mate, or wait for someone else to let you know here, sorry about that
No problem anyway mate, I'm only doing this on a learning curve. That said, I'm open to suggestions and requests, but they should be submitted without much expectation. This is my first ROM, and I'm pretty new to Android development. I can try my best, but I'm no expert. Although I do love a challenge, I can't make any guarantees
But for now I'm going to try and get Google Assistant working by default. We'll see after that
Click to expand...
Click to collapse
Really impressed by your overall response.
You can be a great developer one day. Humility, curiosity and simplicity are hallmarks.
Good luck :good:
ankushgautam said:
Can i install aroma installer open gapps 7.1 on this? If yes how.. I flashed it on this rom but then on booting google services are crashing continuously play store is also not opening.. So some can help plz on this?
Click to expand...
Click to collapse
I've read abouyt some bugs with the Aroma installer in 14.1. I'm not even sure if this is a CM problem or a Gapps problem, but for now, stick with pico or something pre-packaged if you can
silentvisitor said:
Really impressed by your overall response.
You can be a great developer one day. Humility, curiosity and simplicity are hallmarks.
Good luck :good:
Click to expand...
Click to collapse
Thanks mate Maybe, maybe . Gotta finish school first!
init.d, hm. Mysterious to me. I've heard tell of it many times but never learned too much about it. Better start reading up