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.
Related
I successfully installed a rom called USBWOOT.zip (thanks to all the hard work of the developers here, thanks so much guys!) however after doing a little more research I saw someone say the cm9 rom was better (latest one is here I think: http://forum.xda-developers.com/showthread.php?t=1411895&page=210)
I've also seen a MIUI version.
Is there some kind of chart showing the pros and cons of each?
I also have some other noob questions:
Can I flash a new rom (like an updated version, or a different rom?) without losing all my settings, accounts, apps, etc? Or do I have to do a factory reset every time and start over?
Why I ask is I flashed the USBWOOT.zip originally, but it looks like the latest version (in that post I linked to) cm9-02-19.zip has some updates that sound really nice (especially the 200ms to 80ms wait time on screen change)
Since I flashed USBWOOT.zip originally do I need to do a factory reset first or can I just flash cm9-02-19.zip? If I have to do a factory reset will I lose all the accounts, apps, etc?
Thanks for all the help!
That cm9-02-1* roms are follow ups to USBWOOT.zip, they are build from the same source, it just uses a different name coding. Usually all build in that thread are very similar, even if they are build from different people and are named differently since our development is open source.
I would try it first without a total wipe, if you have any unkown problems then do a total wipe. (But a total wipe from time to time isn't a bad thing, since these days many things may change between versions)
MIUI uses a different launcher & other stuff.
I just updated to the latest build of CM9 as well. So far so good. Here is the link too. http://www.mediafire.com/?tnoxgzcgop46odm
Sent from my Amazon Kindle Fire using xda premium
zacpac2020 said:
Install the ROM from this post. It's the most mature. CM9, by the way. http://www.mediafire.com/?tnoxgzcgop46odm
Thank me if I've helped PLEASE!!!!
Click to expand...
Click to collapse
Can you link us to the thread of the developer who compiled this Rom? Someone may want to read the discussion before blindly flashing an unknown zip file.
if its the same rom but just an update, you should get away with just flashing it on top and wiping dalvik cache. as always BACKUP FIRST and then resore and wipe if its not working like it should.
dont go with MIUI yet as its had way less work done and it doesnt even have USB ready.
It Worked
Thanks guys! I was able to flash the latest version without having to do any wipe or factory reset.
I am loving my new and improved Kindle Fire.
Kapurnicus said:
Can you link us to the thread of the developer who compiled this Rom? Someone may want to read the discussion before blindly flashing an unknown zip file.
Click to expand...
Click to collapse
looks like it comes from this thread: http://forum.xda-developers.com/showthread.php?t=1411895
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).
Current version: 4.0.0p1
Current Items not working/Buggy
Updated 4-4-14
No Bluetooth ** FIXED WIP but a majority of items work
Camera ** FIXED WIP camcorder recordes with a blue tint
Battery draw around 50mA in sleep
You tell me what you find.
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.
05-03-2014 Test Build
-- Updates that were in the data/media build since 4-24-204 plus a few more misc fixes.
04-21-2014 Test Build
--some audio fixes for the random SOD along with adding in OTG its not 100% but working well with USB stick, keyboard, and mouse. Activate OTG before plugging in device.
Netflix 1.8.1 -- Don't upgrade Netflix to the latest if you did download here and downgrade and uncheck auto update in the Play Store this is temp until I figure out what changed again.
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
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.
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.
Click to expand...
Click to collapse
Reserved
Awesome thx flint man! Any changes from the Nov 10 test build?
Way to go Flintman, this is great!
Sent from my Touchpad using XDA Premium HD app
flintman said:
Reserved
Click to expand...
Click to collapse
Minor for now
Sent from my SCH-I545 using xda app-developers app
You might want to change the 2nd line down in the OP to KitKat 4.4 and not Jellybean.
theechap said:
You might want to change the 2nd line down in the OP to KitKat 4.4 and not Jellybean.
Click to expand...
Click to collapse
I am using Nexus 5 and was wondering if TP will get Kitkat or not...this is awesome....will flash tonight
Anyone that had lost data can you give me some information. Which acmeinstaller version did you use? Are you still on the smaller partition or did you upgrade? Im still on the i believe it's 400mb system part and haven't upgraded to the larger partition and still yet to loose data. It also could be the way kitkat mounts the partition now. After the inital loose of data did you experience it again? I'm trying to boil this down and having issues pinpoint it as i have yet to loose anything. The more information I can gather the quicker i can fix this issue. Thanks all for testing and helping me out getting this great device updated to the latest OS.
Thanks for this ROM - I have standard partition size and CWM and had no data loss, clean installed. Running well ☺
Sent from my Touchpad using Tapatalk
I tested it briefly and came from datamedia build of 10.2. I did system wipe and install using milaq's datamedia version of CWM. I had no major problems with the install and no lost media as far as I know. Looking forward to testing it again, when it gets a little more stable.
Is everyone just using the 4.3 gapps or is there a 4.4 gapps?
SDcard files
flintman said:
Anyone that had lost data can you give me some information. Which acmeinstaller version did you use? Are you still on the smaller partition or did you upgrade? Im still on the i believe it's 400mb system part and haven't upgraded to the larger partition and still yet to loose data. It also could be the way kitkat mounts the partition now. After the inital loose of data did you experience it again? I'm trying to boil this down and having issues pinpoint it as i have yet to loose anything. The more information I can gather the quicker i can fix this issue. Thanks all for testing and helping me out getting this great device updated to the latest OS.
Click to expand...
Click to collapse
Hey Flintman,
I only lost the data just once so far, if you want I could test out a reinstall. I installed Kitkat by wiping system data and cache and flashing the Rom and gapps through recovery. I already had a 600MB partition but was monitoring the free space left. I should also note that I used CWM to advance restore my data partition from my Evervolv 4.3.1 backup. This seems to be working fine.
Because I use my tablet to test mods and games I had a lot of extra folders that disappeared. These were all added by me like, Dos Games folders about a dozen, image files, Beta apks and the Rom and gapps, that were placed in the internal memory ect. All these files vanished, however files I added that were already in system folders stayed, like music, downloads and shows. It seems to just delete things that the user added into non system or app related folders.
Thanks for letting us take this fun test drive, I was all backed up before I started
DemonicHawk said:
Is everyone just using the 4.3 gapps or is there a 4.4 gapps?
Click to expand...
Click to collapse
Here ya go. You should add that to your OP Flintman
flintman said:
Interesting on the SD card i have yet to experience it. I have a new one that will be going up soon fixed wifi but browser is broken. Firefox works though. Oh BTW still able to keep the stock partition size even with install gapps. KK Gapps i'm using from HERE. Might want to start downloading as it takes a while 8)
Click to expand...
Click to collapse
This was the info I compiled about Flintmans fantastic Test Build. I had a few notes and warnings for users, I will need to update it with a link to this new thread.
Edit: I updated the video for the newer build
Download 4.4 Kitkat Gapps here:
Notes:Low to Medium battery drain(-4mA to -30mA) h/w video, Test Build Make a Backup!, Automated Updater, Audio plays with the screen off, Camera, No Bluetooth.
Note: Windows users may need to do the following in order to attach the Touchpad with the USB cable.
1. Go into the Device manager. You will see "MTP USB Device" under portable devices.
2. Right Click it and select update driver software
3. Select Browse my computer for driver software.
4. Select Let me pick from a list of device drivers on my computer
5. Select USB Mass Storage Device then click next.
and/or
6.To transfer files to PC, turn on USB mass Storage from the USB connection notification on the Android device.
Note(Important): (This might be fixed now) Backup and transfer all your SDcard files to PC. This is a testing build and could wipe files from your SDcard data.
[Note(Important): I would recommend increasing the size of your System Partition for this build. After my install I had 398/400MB free, so Flash the 512MB zip below or use Tailor to adjust the size.
Note(Important): This is an Android Open Source Project (AOSP) rom not a CyanogenMod (CM) rom. Dirty flashing an AOSP rom over a CM rom can causes errors and rebooting issues. Always do a clean install when moving from CM to AOSP and vise versa.
Flash through recovery to change the partition size to 512MB(Gradular&codycoyote)
Flintmans Posts about the new Pre-Beta Build here:
I did a clean install with the standard CWM recovery and had no loss of data or files that i can find. I also restored my apps with TiBU and everything came back good.
The Quadrant score came in a lot lower than the first test build, 1500 (first test build was 2350). The CPU portion is what suffered the most, the other portions seemed normal. It doesn't seem slower than normal though.
I haven't found any problems with any apps.
Great job, thanks!
Sent from my Touchpad using XDA Premium HD app
Sweet, glad to see this. I think we should wait for Android 4.4.1. Which the UI will be fixed for the Nexus 10.
Sent from my Galaxy Nexus using xda app-developers app
Hey Flintman,
Would you clear up some confusion about this build. I've seen a post over in the Evervolv 4.3 thread and also over in Rootzwiki. Is this build of 4.4 a traditional build like your 4.3 build or a data-media build that is going to require the data-media version of CWM and resizing partitions like the Milaq 4.3? Thanks
nevertells2 said:
Hey Flintman,
Would you clear up some confusion about this build. I've seen a post over in the Evervolv 4.3 thread and also over in Rootzwiki. Is this build of 4.4 a traditional build like your 4.3 build or a data-media build that is going to require the data-media version of CWM and resizing partitions like the Milaq 4.3? Thanks
Click to expand...
Click to collapse
I use the normal twrp recovery. This ROM doesn't require the data-media version of cwm. I hope that answers your question.
Sent from my SCH-I545 using xda app-developers app
I want to go back to CM10.1 but everytime I flash it back bootloader defaults to evervolv despite having an option for Cyanogenmod but the bootloader fails when I select cm10.1 after flashing... I only wanted to test it out a little too unstable for a daily driver but now it seems like I am stuck on this rom
Very cool looking forward to flashing this as soon as some of the major bugs are worked out
Sent from my Nexus 4 using Tapatalk
flintman said:
Anyone that had lost data can you give me some information. Which acmeinstaller version did you use? Are you still on the smaller partition or did you upgrade? Im still on the i believe it's 400mb system part and haven't upgraded to the larger partition and still yet to loose data. It also could be the way kitkat mounts the partition now. After the inital loose of data did you experience it again? I'm trying to boil this down and having issues pinpoint it as i have yet to loose anything. The more information I can gather the quicker i can fix this issue. Thanks all for testing and helping me out getting this great device updated to the latest OS.
Click to expand...
Click to collapse
Hi,
I experienced loss of data, much like as reported another member here, I only lost the folders that were added by me, it also removed the TWRP back up folder, however folders that are the usual like Music, Download remained as they were, however, the gallery app refused to load any images.
In between the reboots, I connected the TouchPad to PC and noticed something peculiar, after the very first boot, it showed about 9GB free, the same was on TWRP too, even though my folders were all gone, and after the next reboot on being connected to PC it showed me about 17GB free.
My install method was using TWRP, system wipe and flashing the zips,
I have extended the system and data partitions using the Tailor method to 512mb and 2.5gb respectively.
For now, I am back on 4.3 but would like to be able to help test out if there are any fixes that you are trying. Once again, thanks for the all the good work on these ROMs :good:
You know I think TWRP is the cause if data loss just reading peoples experiences in this thread. CWM FTW!
Sent from my Nexus 4 using Tapatalk
The development thread can be found here: http://forum.xda-developers.com/showthread.php?t=2516933
DOWNLOADS
Latest nightlies: http://dl.omnirom.org/n7000/
Kernel with Selinux support for flashing: http://asylumrom.com/Asylum/Asylum-Roms/KitKat-4.4/N7000/kerner/
SuperSU flashable zip for root access: http://download.chainfire.eu/supersu/
PA Gapps: http://goo.im/devs/paranoidandroid/roms/gapps
Banks Gapps (if PA Gapps doesnt work for you): http://forum.xda-developers.com/showthread.php?t=2012857
Click to expand...
Click to collapse
Click to expand...
Click to collapse
USEFUL LINKS
Official OmniROM Wiki: http://docs.omnirom.org
Changelog: https://changelog.omnirom.org/#/n7000/next
Click to expand...
Click to collapse
Click to expand...
Click to collapse
KNOWN ISSUES FOR N7000
- Wifi tethering doesn't work Fixed!
- Screen recording doesn't work (but camera recording works just fine!)
- Opendelta sometimes freezes when checking/downloading update (see FAQ)
- Charging while power off doesn't work. Fixed!
- Music playback sometimes stops randomly when using a wired headset. (we need more info on this issue, please report here in this thread if you experience it!)
- MHL Doesn't work (and probably never will).
Click to expand...
Click to collapse
Click to expand...
Click to collapse
FAQ
For those questions that pops up all the time, this will be updated often.
Also, remember to thank those who provides the answers!
Q: How does OpenDelta auto updater work?
AA1973 said:
At first, OpenDelta will check if a Rom Zip is available on your device. If OpenDelta doesn't find it, it will download a Rom. (~170mb) From then, it will only download the difference (delta) and patches the initial Rom zip within internal SD /OpenDelta. Then, after the patch, the Rom zip will be around 280mb, as it is uncompressed.
Click to expand...
Click to collapse
Q: Why does OpenDelta freeze from time to time when trying to update the ROM?
@Chainfire is still working on it:
Chainfire said:
FYI, people still suffering from the OTA updater freezing mid-verify, mid-download or mid-patch, we've found a lot of way how it didn't get fixed Putting the sdcard handling code in debug mode gets rid of the problem, but obviously we don't want to do that in production, eh!
Click to expand...
Click to collapse
Q: I pressed "flash now" but TWRP recovery says "status failed". What do I do now?
AA1973 said:
How about switching your pointer from external storage to *internal storage* within TWRP > INSTALL option?
Click to expand...
Click to collapse
Q: What's the "Flash after update" folder in the OpenDelta folder?
se1988 said:
It's for .zip files you want the openrecoveryscript to flash automatically after flashing a nightly. Take a look at this thread for examples.
Click to expand...
Click to collapse
Q: How do I keep root after flashing nightlies?
se1988 said:
After rooting, open SuperSU app - settings - Install SuperSU backup script.
Click to expand...
Click to collapse
Q: Does this ROM come with call recording?
se1988 said:
No, and it won't. However, this app has been confirmed working for some users: https://play.google.com/store/apps/details?id=polis.app.callrecorder
Click to expand...
Click to collapse
Q: How can I get FM radio on this ROM?
se1988 said:
The only solution is the Spirit FM app: http://forum.xda-developers.com/showthread.php?t=1059296
Click to expand...
Click to collapse
Q: How can I get Samsung stock apps like S-note?
se1988 said:
Go back to Stock ROM or search play store for whatever your needs are. You'll probably find something that's better than Samsung apps anyway. If you're still wondering - OmniRom will not and can never support Samsung stock apps.
Click to expand...
Click to collapse
Q: How can I get soft keys / navigation bar?
AA1973 said:
Soft keys aka navigation bar
Edit build.prop (use preferred ROM Toolbox lite/pro or a suitable root file explorer)
Add the following line at the end:
Code:
qemu.hw.mainkeys=0
You'll get navigation bar / soft keys and the desired layout of lockscreen.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
HOW TO INSTALL
XpLoDWilD said:
First time installing OmniROM to your Galaxy Note, or coming from another ROM:
- Read known issues and FAQs
- Make sure you're running a proper working ClockworkMod-Recovery - WITH SELINUX SUPPORT!
- Copy GApps and OmniROM ZIPs to your SDCard
- Boot into Recovery
- Flash OmniROM zip from SDCard
- Flash GApps zip from SDCard
- DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
- Reboot
- Don't restore system data using Titanium Backup!
- Restoring Apps + Data might cause problems and is not recommended, avoid it if possible!
Upgrading from earlier version of OmniROM:
- Copy the OmniROM ZIP to your SDCard
- Boot into Recovery
- Flash the OmniROM zip from SDCard
- Reboot
Click to expand...
Click to collapse
se1988 said:
Also, remember to flash this after flashing ROM for root access: http://download.chainfire.eu/supersu/
Click to expand...
Click to collapse
Click to expand...
Click to collapse
I hope so
General probs I have with Rom
_
I would love to use this rom as my daily driver but due to some issues I have reverted to my previous setup slimsabre.
Phone gets very hot whilst charging - but charges at acceptable rate. I have replaced battery but still same.
Sometimes phone gets very hot even when not in use - I could not find any reason even looking at better batt stats and cpu spy - tried reinstalling rom and gapps only and this still happened - Phone would just become very hot to hold at some random time.
Any help on this appreciated as I do not know what is causing this.
Ingott
_
having really bad battery drain.. using latest raw kernel.. any suggestions? maybe another supported kernel with better batterylife?
ingott77 said:
_
I would love to use this rom as my daily driver but due to some issues I have reverted to my previous setup slimsabre.
Phone gets very hot whilst charging - but charges at acceptable rate. I have replaced battery but still same.
Sometimes phone gets very hot even when not in use - I could not find any reason even looking at better batt stats and cpu spy - tried reinstalling rom and gapps only and this still happened - Phone would just become very hot to hold at some random time.
Any help on this appreciated as I do not know what is causing this.
Ingott
_
Click to expand...
Click to collapse
If you got the new battery cheap off eBay or similar it's a good chance that it's fake. I've had a couple of those, heating up to the point where you're afraid of damages.
Sent from my phone using some app
When I first installed Omni my phone stayed hot for ages. It turned out that Google+, which normally I do not use and have frozen on previous ROMs, was going absolutely nuts doing some sort of background sync and downloading truckloads of data. The app was running in the background for over an hour with the CPU cores pretty much maxed out. Maybe your problem is the same. Maybe not. Eventually G+ finished its evil work and the phone performance and temperature returned to normal.
I ran with the ROM for a few days and it seemed stable, but I've actually reverted to Samsung's latest stock ROM as KitKat really wasn't doing it for me. Basically I saw no tangible benefits but did lose some convenient features and interface changes were definitely a backward step with Omni. Maybe when it's matured and ART is working fully I'll take another run at it.
mosheg91 said:
having really bad battery drain.. using latest raw kernel.. any suggestions? maybe another supported kernel with better batterylife?
Click to expand...
Click to collapse
Why not use omni kernel?
ozgurgundogan said:
Why not use omni kernel?
Click to expand...
Click to collapse
where can i find omni kernel? i didn't know that it exists..
mosheg91 said:
where can i find omni kernel? i didn't know that it exists..
Click to expand...
Click to collapse
When you install omnirom it contains omni kernel too.
ozgurgundogan said:
When you install omnirom it contains omni kernel too.
Click to expand...
Click to collapse
so.. been using that and didn't know that.. any other good kernel which is battery friendly and with good performance as well?
gesture typing is not working for me on aosp keyboard, currently on 15/12/2013 nightly with 14/12/2013 mini modular pa gapps. is it the same for others?? or is it a known bug?
thank you
"Nothing is true" "Everything is permitted"
---------- Post added at 03:50 AM ---------- Previous post was at 03:38 AM ----------
mosheg91 said:
so.. been using that and didn't know that.. any other good kernel which is battery friendly and with good performance as well?
Click to expand...
Click to collapse
Try raw kernel ?
don't know how its performance is but its the only 4.4 kernel for aosp now.
go here http://forum.xda-developers.com/showthread.php?t=2397000
"Nothing is true" "Everything is permitted"
tysonraylee said:
gesture typing is not working for me on aosp keyboard, currently on 15/12/2013 nightly with 14/12/2013 mini modular pa gapps. is it the same for others?? or is it a known bug?
thank you
Click to expand...
Click to collapse
+1 to that!.
mosheg91 said:
so.. been using that and didn't know that.. any other good kernel which is battery friendly and with good performance as well?
Click to expand...
Click to collapse
Omni kernel(with SD access) was only available after flashing ROM since 12th Dec nightly, so it depends what rom you're on right now. Or perhaps you flashed Raw Kernel over it?
I would advise you to do a clean install. There's no other kernel available right now for 4.4 But it should work.
madhugk said:
+1 to that!.
Click to expand...
Click to collapse
i solved it by flashing the Google keyboard from the pa gapps thread.
rebooting the device after clearing the aosp keyboard data didn't work.
the Google keyboard has no difference over the aosp one but has a working gesture typing.
you could do that too
-download Google keyboard zip
-reboot to recovery
-flash the zip
-clear cache and dalvik cache
-reboot
-select Google keyboard from settings->language and input
done
hope it helps
direct keyboard link from pa gapps thread www.androidfilehost.com/?fid=23252070760975522
"Nothing is true" "Everything is permitted"
Guys, a little confused here,
is openDelta already integrated into the 12/15 Nightly?
if so, then why is it trying to download the whole ROM?
I think the first time we use it, it Downloads the entire ROM and then the next time it checks hashes and then only downloads updated files...
please clarify, as I thought It only downlods changed files and checks hash for that.
thought downloading fails midway, tried almost 7-8 times now,
I already increased the screen time on to 30 minues, what else can I do to get it downloaded completely
Unhappy slow charging and poor battery life.. over heating while using mobile interne
First of all many thanks for developing such a good rom. everything is upto the mark the only critical issue i am facing is very very slow charging, and along with very poor battery life i am using build of 12-12-2013. i charge my phone to 100% (it takes almost 6hrs) and it drains within 1hr (normal usage). Also i tried with two other new batteries as well same issue.
And there is one more issue whenever we change the music (forward/play-pause) using headset screen automatically turns on. Screen also turns on automatically sometimes without going on anything.
Phone over heats while running multiple application or using internet
Screen brightness is way to high on automatic setting mode even though i adjusted it with the flux response settings, in the settings of phone.
Guys please help me out i don't know much abt anroid programming and bug fixing please.
gps fix
I had a problem when I wanted to use google map for navigation, I never managed to get a gps fix. (The real problem isn't the first fix but after, it never moove on map)
Does that work for you?
I'm on the nightlie of 15/12.
@techMagnificent
At first, OpenDelta will check if a Rom Zip is available on your device. If OpenDelta doesn't find it, it will download a Rom. (~170mb)
From then, it will only download the difference (delta) and patches the initial Rom zip within internal SD /OpenDelta.
Then, after the patch, the Rom zip will be around 280mb, as it is uncompressed.
For battery drain. Install better battery stats as system app (settings > advanced) which you can find on xda. Check which app and service is driving your phone nuts.
GALAXY NOTE N7000 // KITKAT 4.4.2 // OMNI
AA1973 said:
@techMagnificent
At first, OpenDelta will check if a Rom Zip is available on your device. If OpenDelta doesn't find it, it will download a Rom. (~170mb)
From then, it will only download the difference (delta) and patches the initial Rom zip within internal SD /OpenDelta.
Then, after the patch, the Rom zip will be around 280mb, as it is uncompressed.
For battery drain. Install better battery stats as system app (settings > advanced) which you can find on xda. Check which app and service is driving your phone nuts.
GALAXY NOTE N7000 // KITKAT 4.4.2 // OMNI
Click to expand...
Click to collapse
Added to FAQ in OP. Thanks
chacal1906 said:
I had a problem when I wanted to use google map for navigation, I never managed to get a gps fix. (The real problem isn't the first fix but after, it never moove on map)
Does that work for you?
I'm on the nightlie of 15/12.
Click to expand...
Click to collapse
I never use maps for navigation, but i just got to my destination using Sygic. No problems with gps lock or navigation.
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??
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.