Related
This is a thread for the discussion of the bluesleep fix / deep sleep issue specifically for the Motorola Atrix 4g
There is a known issue with some roms that prevents the device from entering the deep sleep cpu state, which is ultimately responsible for a significant reduction in battery life. This is believed to be caused by a glitch in the Bluetooth permission settings. A fix has been developed (known as the bluesleep fix) which is thought to correct the problem, and allow the device to enter deep sleep. It has been suggested that the bluesleep fix will also correct a glitch that prevents the wifi from sleeping. I have not experienced wifi sleep issues myself, so I can’t provide any first-hand knowledge.
Almost everyone who has experienced deep sleep issues and has used the bluesleep fix agrees that it works. I have corrected the problem on my device on CM7, CM9, and CM10 roms. The increase in battery life was dramatic.
However, the bluesleep fix is not without controversy. Many people, including at least one developer, believe the bluesleep fix works and recommends its use. Another developer submitted his version of a fix to CM. There are others, including one whose opinion I respect, that believe there is no reason the fix should work and don’t believe that it does. There have been many recent discussions on the topic on CM9 and CM10 threads that you can search for yourself.
If you have used the bluesleep fix to successfully correct deep sleep issues, or tried the fix and it didn’t work, or strongly believe one way or the other, please share your knowledge and experiences below for the benefit of the community!
[The bluesleep fix is attached (flash with CWM) along with before and after screenshots for a CM9 rom on my device.]
[FYI, I was involved in some of the linked discussions under my former user name (Atrix_FauxG). I thought I should mention this to avoid any confusion.]
[At the time I posted this thread I was unable to determine who created the bluesleep fix. If anyone knows, please inform me so I can give proper credit.]
______________________________________________
Edit:
1) I got confirmation from Th3bill that he wrote bluesleep_fix based on settings from olegfusion. Please take a moment to thank both of them (here and here). The bluesleep_fix file can also be found here (feel free to click on a few ads while you are there to further show your appreciation).
2) I neglected to mention that I observed the greatest increase in battery life on CM9 and CM10 roms.
Th3bill first brought it to our attention when building miui
Sent from my MB860 using xda premium
upndwn4par said:
[The bluesleep fix is attached (flash with CWM) along with before and after screenshots for a CM9 rom on my device.]
Click to expand...
Click to collapse
Or not?
As for me, my battery life was always very good on the Atrix. At some point I came across this bug and the fix for it and I applied it just to be safe. I know what the fix does (basically it setuids a few bluetooth-related utilities and fixes their ownership) and I guess I can kinda sorta see how it would be possible that that fixes the issue. However I can't say I noticed any big difference in my battery life after applying it.
For the record, I went from stock ROM to CM7-RC3, then to CM7-stable, and am now on ABC.
Not sure!
I posted this in another thread: http://forum.xda-developers.com/showpost.php?p=29854345&postcount=2154
After the full wipe and fresh install without the fix my Atrix is going into deep sleep fine.
I am using CM10 by epinter
Worked for me. I am using CM7 by the way. Before I implemented the fix, my phone never went into deep sleep. Now it does all the time.
Hmm,
Basically, mount /system rw, and chmod 04755 /system/xbin/hci*.
Not sure what the target rom is, but on my bell I don't have a hcidump. I have a dexdump though.
Cheers!
NFHimself said:
Hmm,
Basically, mount /system rw, and chmod 04755 /system/xbin/hci*.
Not sure what the target rom is, but on my bell I don't have a hcidump. I have a dexdump though.
Cheers!
Click to expand...
Click to collapse
Yeah, that's not the one.
I think the primary target would be CM7 and all ROMs based on it. I have a CM7 based ROM and I have all three hci* utilities.
And yeah, that's basically it, like I said in my previous post. It setuids all three and sets their ownership to root:shell (0:2000).
As stevendeb25 mentioned above, the primary target was MIUI (CM9).
ravilov said:
Yeah, that's not the one.
I think the primary target would be CM7 and all the ones based off it. I have a CM7 based ROM and I have all three hci* utilities.
And yeah, that's basically it, like I said in my previous post. It setuids all three and sets their ownership to root:shell (0:2000).
Click to expand...
Click to collapse
I got 17 hours deep sleep without the bluesleep fix file. I'm on Epinter's CM10.
Sent from my Nexus 7
upndwn4par said:
As stevendeb25 mentioned above, the primary target was MIUI (CM9).
Click to expand...
Click to collapse
Ah, I see. Yeah, CM7 (GB) has all the proper drivers to support the Atrix hardware fully, my guess is that that's the reason CM7-powered devices are able to enter deep sleep state regardless of permissions and ownership of the Bluetooth utils.
Here's a screenshot of my current state. This is after applying the patch though, so I don't know if it's relevant really, but here it is anyway.
I never checked while on CM7.0, but for me CM7.2 did not enter deep sleep until I applied the patch.
ravilov said:
Ah, I see. Yeah, CM7 (GB) has all the proper drivers to support the Atrix hardware fully, my guess is that that's the reason CM7-powered devices are able to enter deep sleep state regardless of permissions and ownership of the Bluetooth utils.
Here's a screenshot of my current state. This is after applying the patch though, so I don't know if it's relevant really, but here it is anyway.
Click to expand...
Click to collapse
Epinter's CM10 did not enter deep sleep for me. Though, the last update I applied was 20120729. Maybe he incorporated his own fix I mentioned in the OP in to his rom.
Soldier-2Point0 said:
I got 17 hours deep sleep without the bluesleep fix file. I'm on Epinter's CM10.
Sent from my Nexus 7
Click to expand...
Click to collapse
upndwn4par said:
Epinter's CM10 did not enter deep sleep for me. Though, the last update I applied was 20120729. Maybe he incorporated his own fix I mentioned in the OP in to his rom.
Click to expand...
Click to collapse
You should try 0803 build. No problems here. Epinter did not include any secret fixes to the rom because he did not mention it in the changelog. No sense in fixing something if you're never going to mention it. The blue sleep fix file is listed on his website, but not included on the rom.
This blue sleep fix file may have been useful on other roms, but is not needed on Epinter CM10.
Sent from my MB860 on CM10
I was on Epinter's 0803 build for a few days this week. No deep sleep without bluesleep fix.
Do you use bluetooth? If you don't leave your BT on then there are no deep sleep problems. I don't turn my BT off ever.
I have spent the last few days on Joker's CM10 and same thing - no deep sleep without fix.
Soldier-2Point0 said:
You should try 0803 build. No problems here. Epinter did not include any secret fixes to the rom because he did not mention it in the changelog. No sense in fixing something if you're never going to mention it. The blue sleep fix file is listed on his website, but not included on the rom.
This blue sleep fix file may have been useful on other roms, but is not needed on Epinter CM10.
Sent from my MB860 on CM10
Click to expand...
Click to collapse
My phone goes to deepp sleep without problem, cm7.2 latest nightly.
Sent from my MB860 using xda app-developers app
will this work for the new jelly bean nightly ( 815 ) ...? using darksides new cm10 a07.2
oh and my phone goes into the sleep of death where i can only pull the battery to fix it...will this work for that...?...thanks in advance...
This will fix the bluesleep problem on any CM7 device, but I don't think it will help your SOD problem and it could (in theory) make it worse. I have never experienced the SOD, but many users have said that increasing the minimum clock speed on your kernel to 456 MHz will help.
phordych05 said:
will this work for the new jelly bean nightly ( 815 ) ...? using darksides new cm10 a07.2
oh and my phone goes into the sleep of death where i can only pull the battery to fix it...will this work for that...?...thanks in advance...
Click to expand...
Click to collapse
How can I revert back after flashing the fix?
Restore the backup you should make before flashing anything.
TopDroid said:
How can I revert back after flashing the fix?
Click to expand...
Click to collapse
What I always do before flashing this kind of CWM zip is extract the flashable .zip, see what files it is going to replace or modify, backup my current version of them, replace the modified versions in the folder with my originals (renaming the originals to the modifieds' name, respectively, if necessary), zip it up, and there you have it! That Revert zip almost always works (never failed for me)!
Sent from my MB860 using Tapatalk 2
MONFRO AOSP
This is a pure AOSP rom: it has no extra features so it can be snappy and smooth at maximum level.
Indeed the goal of this rom is to be as fast as possible.
- CM10 partition layout (422mb for data)
- Devil Kernel 1.4.1 VC (new kernels with new CM vsync available as addon)
- Devil Kernel Config included (and a init.d script generated with this program, to have everything set up stable at the beginning. If you set bigmem, before reboot remember to set 480 in videocamera settings, otherwise camera app will crash with bigmem). I suggest to install also NSTools, to have more overclocking and BLN options.
- GAPPS (updated to latest) are included
- I SUGGEST A FULL WIPE BEFORE INSTALLING THIS ROM, because added features from CM10, Helly Bean, AOKP and other roms can conflict with pure AOSP settings and functions
DOWNLOAD MONFRO AOSP 23.09.2012 FROM HERE
MD5: 086981af9bd829a742d2d34dd3652b81
- BATTERY MODS
- Battery % Mod CM style
- Battery % Mod Perka Newborn
- Battery Mod restore original icon
- MODS
- Devil Kernel 1.5.2 + new CM vsync
- Semaphore Kernel 2.1.2 + new CM vsync
- MODEMS/RADIO
Here you can find a lot of compatible modems/radio
- THEMES
- MonfroWhite by sephhi
@ALL: feel free to post mods and themes. I will add them to the 1st post
Reserved.
It took me a lot to upload this rom.
It was ready and working perfectly on 21.09.2012...all today i was out and i could upload it only now.
Monfro said:
Reserved.
It took me a lot to upload this rom.
It was ready and working perfectly on 21.09.2012...all today i was out and i could upload it only now.
Click to expand...
Click to collapse
will give it a try.....thank you!
Great work! Appreciate the effort for another AOSP
Looks like I've got another ROM to try out... it will have to be tomorrow though...
Sent from my SGH-I897 using XDA
LOVE the toggle customization. Little laggy on first running overall but so far so good.
It's official, I'm in love! Soft keyboard type option in messages so I can "Enter for new line" and not have that dumbass key!!! THANK YOU
AceofSpades90 said:
Great work! Appreciate the effort for another AOSP
Click to expand...
Click to collapse
I have to say thank you, because your Lanight rom showed me how fast AOSP roms are, as you can see from my enthusiastic comment of 20.09.2012.
But on Lanight 4.0 there were some glitches, for this reason i decided to work on an AOSP rom. I see that you worked to fix Lanight while i was working here: if i would have seen your new rom build, probably i wouldn't have worked on my AOSP.
joe3681 said:
LOVE the toggle customization. Little laggy on first running overall but so far so good.
It's official, I'm in love! Soft keyboard type option in messages so I can "Enter for new line" and not have that dumbass key!!! THANK YOU
Click to expand...
Click to collapse
Message app is from CM: it works better than AOSP one.
AOSP message let you enter messages only of 160 letters, for this reason i decided to substitute it with CM one.
cant get radio working.....
Wifi and signal are not opening. Looked around but didnt see any other radios available? Am i looking in the wrong place? (in this forum) Other than that the rom looks great, but until I can get my wifi working i cant get a full picture of what this rom will be like... I am going to do some more reading. had this problem before, but flashed a radio and everything was good. Now I cant seem to find one. Call me an idiot if you will, just need some direction on where to go from here. The website i used last time has radios for ics but not JB.
Also shell was not given SU permissions. Bad flash maybe?
Thanks in advance....
Poke01 said:
Wifi and signal are not opening. Looked around but didnt see any other radios available? Am i looking in the wrong place? (in this forum) Other than that the rom looks great, but until I can get my wifi working i cant get a full picture of what this rom will be like... I am going to do some more reading. had this problem before, but flashed a radio and everything was good. Now I cant seem to find one. Call me an idiot if you will, just need some direction on where to go from here. The website i used last time has radios for ics but not JB.
Also shell was not given SU permissions. Bad flash maybe?
Thanks in advance....
Click to expand...
Click to collapse
Here you can find a lot of compatible modems/radio, find the one that works best in your area:
http://soggycashew.weebly.com/cm7miui--ics-modems.html
If you have problems with SuperUser, try SuperSU from Play Store.
Updated first post with modems/radio link and battery % mods.
@ALL: feel free to post mods and themes. I will add them to the 1st post
Added mods to flash latest Devil and Semaphore kernels + new CM vsync
Your cappy looks promising because you are a recognized Dev. seems your also using same partition layout as of hellybeans that why can't flash this cappy on my captivate as I'm using broken sd device.
Sent from my SGH-I897 using XDA
s0ul_ali said:
Your cappy looks promising because you are a recognized Dev. seems your also using same partition layout as of hellybeans that why can't flash this cappy on my captivate as I'm using broken sd device.
Sent from my SGH-I897 using XDA
Click to expand...
Click to collapse
This rom uses the same layout as CM10: 422mb on fastest nand for data and the rest (slow nand) for system.
I am sorry you can't try this rom. I have read here and there about people with broken internal SD but i didn't entered in details.
another AOSP rom to test...nice......will test it soon.....
Monfro said:
Here you can find a lot of compatible modems/radio, find the one that works best in your area:
http://soggycashew.weebly.com/cm7miui--ics-modems.html
If you have problems with SuperUser, try SuperSU from Play Store.
Updated first post with modems/radio link and battery % mods.
@ALL: feel free to post mods and themes. I will add them to the 1st post
Click to expand...
Click to collapse
I've been on xda long enough, but I'm drawing a blank at the moment. If my WiFi isn't turning on, would changing the modem affect that?
My Captivate has been relegated to my backup device, almost always used on WiFi.
From what I've played with on this rom, I like it a lot. Keep up the great work!
I have had similar issues with other JB AOSP roms with CM10 base. If I understand it correctly, it is due to the datadata partition that is included with this base (data partition table messes up the Kernel or something). To my knowledge there is no work around for this. Some of the AOSP roms here (LANIGHT for example) have a nodatadata version which solves the problem.
Hope this helps!
Poke01 said:
Wifi and signal are not opening. Looked around but didnt see any other radios available? Am i looking in the wrong place? (in this forum) Other than that the rom looks great, but until I can get my wifi working i cant get a full picture of what this rom will be like... I am going to do some more reading. had this problem before, but flashed a radio and everything was good. Now I cant seem to find one. Call me an idiot if you will, just need some direction on where to go from here. The website i used last time has radios for ics but not JB.
Also shell was not given SU permissions. Bad flash maybe?
Thanks in advance....
Click to expand...
Click to collapse
Sagui said:
I have had similar issues with other JB AOSP roms with CM10 base. If I understand it correctly, it is due to the datadata partition that is included with this base (data partition table messes up the Kernel or something). To my knowledge there is no work around for this. Some of the AOSP roms here (LANIGHT for example) have a nodatadata version which solves the problem.
Hope this helps!
Click to expand...
Click to collapse
To enable wifi try these 2 methods:
1. turn on Bluetooth, reboot, activate wifi and now it works.
2. activate wifi, turn on Bluetooth, reboot and now wifi works
Sent from my Captivate
Monfro said:
To enable wifi try these 2 methods:
1. turn on Bluetooth, reboot, activate wifi and now it works.
2. activate wifi, turn on Bluetooth, reboot and now wifi works
Sent from my Captivate
Click to expand...
Click to collapse
Method 1 worked for me....Awesome! Thanks!
tried downloading the file and my antivirus went crazy lol .....
Zero4 said:
Method 1 worked for me....Awesome! Thanks!
Click to expand...
Click to collapse
So the problem comes from the Bluetooth kill function in devil kernel, which kills also wifi.
I suggest to disable devil idle and deep idle and to leave "enable Bluetooth " in devil kernel config app.
MrSwiss876 said:
tried downloading the file and my antivirus went crazy lol .....
Click to expand...
Click to collapse
It is because of superuser, but there are no viruses inside the zip.
Sent from my Captivate
Flashing!! :fingers-crossed:
Hey Monfro, how is going the battery life so far ?
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.
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??