Related
I went back to the stock rom to try and solve the issue I was having with my phone rebooting. Just got a popup with a huawei update.. Installing now, will report back with any new features and changes if any.
nanoloop said:
I went back to the stock rom to try and solve the issue I was having with my phone rebooting. Just got a popup with a huawei update.. Installing now, will report back with any new features and changes if any.
Click to expand...
Click to collapse
Please do..
nanoloop said:
I went back to the stock rom to try and solve the issue I was having with my phone rebooting. Just got a popup with a huawei update.. Installing now, will report back with any new features and changes if any.
Click to expand...
Click to collapse
I'm interested to see what differences it will have, fingers crossed for something special
all its seems to have added was the hotspot feature. nothing has changed otherwise.
nanoloop said:
all its seems to have added was the hotspot feature. nothing has changed otherwise.
Click to expand...
Click to collapse
kernel version?
NZ 2Degrees users are about to get their OTA update:
2DegreesCare
240 posts | 2 friends
Master Geek
Trusted
2degrees
Reply # 473907 posted on 24-May-2011 15:38
Software itself is tested and A-OK. Now finalising the upgrade process for all users and will contact them by end of May.
^POB
yup, I got the same OTA update yesterday here in kuwait. It added hotspot and seems to have some other minor updates. Not sure what they are, but the google calendar icon updated if that's worth anything.
In any case, kernel version for me is 2.6.32.9
seems they may have fixed the issue in regards to sound clarity. Every call i have made today has commented on how clear the line is, as to what it has normally been in the past..
What is the version number?
More info on this OTA please! Has anyone been able to isolate it?
Okay some info..
This will update to B136 (same as B160). They have made some kernel changes but have not published the changed source as far as I know, so you're either stuck with their kernel or a modified one with overclocking etc.
The only thing I know for sure that has been changed is the camera driver, which honestly isn't a significant improvement. It still benchmarks around 1500 in quadrant pro, and although not tested I would assume similar battery life etc.
I will be releasing a package soon to use this kernel on B160 should people wish to try it.
stockwell said:
Okay some info..
This will update to B136 (same as B160). They have made some kernel changes but have not published the changed source as far as I know, so you're either stuck with their kernel or a modified one with overclocking etc.
The only thing I know for sure that has been changed is the camera driver, which honestly isn't a significant improvement. It still benchmarks around 1500 in quadrant pro, and although not tested I would assume similar battery life etc.
I will be releasing a package soon to use this kernel on B160 should people wish to try it.
Click to expand...
Click to collapse
OP posted that people commenting on improved clarity when he call them. This is very interesting to me as people on the other end are forever asking me to repeat. So would this be in the kernel? Would this mean I would lose over-clock if I used this new kernel provided by you?
As I said above, you will lose overclocking and other tweaks (ie BFQ I/O Scheduler and Smartass CPU governor).
stockwell said:
As I said above, you will lose overclocking and other tweaks (ie BFQ I/O Scheduler and Smartass CPU governor).
Click to expand...
Click to collapse
Just to clarify, we lose root too?
OmegaModr said:
Just to clarify, we lose root too?
Click to expand...
Click to collapse
root is not related to kernel, just do z4root if the ROM is not rooted by default.
Root is not related to the kernel but it is related to boot image, so if you use the package in the B160 thread then you will still have root and won't need to use Z4.
Thanks, all I needed to know. I switched over form samsung where you do need a custom kernel for root. Starting to like this phone more and more
Just start the OTA update from 2degreesmobile NZ
WARNING: TRYING TO CUSTOMIZE YOUR VIEWSONIC MAY LEAVE THE DEVICE IN A BRICKED STATE. PLEASE MAKE SURE YOU FULLY UNDERSTAND HOW TO USE NVFLASH BEFORE TRYING THIS INCASE SOMETHING GOES WRONG AND YOU NEED OR WANT TO GO BACK TO THE VIEWSONIC STOCK TNT ROM.
What we offer here is a new way to keep you in full control of your tablet. Our 1.8 Honeycomb Kernel offers Speed, Reliability, and new added features. This kernel is a spin off of the Pershoot Honeycomb Kernel Source Code & want to thank Pershoot for all his work on the kernel already. You do not have to Flash your device or even update to a different ROM to feel the benefits of the Linux Box Solution Honeycomb Kernel...
Updating to the Linux Box Solution Honeycomb Kernel couldn't be easier. No wiping of User/Data is necessary. If you are already running a Honeycomb ROM then your good to go. This kernel was designed for Tegra 2, Harmony Board based devices. The LBS 1.8 Honeycomb Kernel has only been tested on a Viewsonic Gtablet. If any other developers with the Specified Tegra 2 & Harmony Board based devices wants to give this Overclocked Powerhouse a try please give me your feedback once you have tested it out.
Features as of Version 3.2:
Increased Kernel Cache Sizes from 256kb to 512kb
Improved Stability
Overclocking (Kernel is Overclockable to 1.4Ghz)
USB Mass Storage ( If your favorite Honeycomb ROM doesn't offer USB Mass Storage drop this Kernel in and Full Support is there)
Improved Video Play (480P Plays, Not sure about 720P but 1080P Does Not Work)
Git Hub Source Location: https://github.com/linuxboxsolution/LBSGtab
Linus Torvald Repo: http://android.git.kernel.org/platform/kernel/tegra.git
Pershoot Repo: https://github.com/pershoot/gtab-2632.git
For anyone in doubt or wondering. This Kernel has been fully updated with Pershoot's source code from his 7/2 update. Next changes to the source code are taken from Linus Torvalds Repo Source to help merge Pershoot's and Torvalds Source to make a more efficiently running Kernel.
Download Link:
LBS 3.2 Honeycomb Kernel: http://linuxboxsolution.com/linux-b...tions-Viewsonic-Gtablet-Honeycomb-Kernel-3.2/(increased kernel cache size for improved stability)
LBS 1.9.2 Honeycomb Kernel: http://linuxboxsolution.com/linux-b...ons-Viewsonic-Gtablet-Honeycomb-Kernel-1.9.2/(Wifi configuration changes to help people with wifi connectivity issues)
LBS 1.8 Honeycomb Kernel: http://linuxboxsolution.com/linux-b...tions-Viewsonic-Gtablet-Honeycomb-Kernel-1.8/ Initial Release
1. Download the zip file for the Kernel Version you want to the Root of your SDCARD Partition.
2. Rename file to update.zip
3. Reboot Tablet into Recovery Mode (When Tablets Off hold 'Power' Button and 'Volume +' Button at Same time till Recovery Mode is Shown On Screen)
4. Using Volume -/+ to navigate the Clockwork Mod Menu go to apply /sdcard/update.zip
5. Once Installation of New Kernel is done Reboot the Tablet & Enjoy your newly found Feature Set and Performance Improvements
aww what the hell i'll give it a go...currently running BoS 6.0 and it's smooth...I'll post back with Quadrent scores for those who care about them.
Updated: well it might be me but the lockscreen seems more responsive, Video plays about the same but im in Rockplayer, Quadrant was 2677 using Quadrant Advanced. Kepp up the work guys.
Update: Ok well been playing with it and just found out No WIFI here. it won't pick up any signel...this might be just me but so far Reboot + turning wifi off and back on did not fix it i'm going to wipe cache and see if it resoves it.
Update: as of right now the Update did not fix the problem nor did wiping cache/data...Going back to my nandriod and i'll watch for updates.
Also i'm using a static setup with WEP Security if that helps...it shows my old connections but won't connect or find new ones.
Awesome please do but if you haven't yet try the updated version.
I had an exchange with you on slatedriod about "your" new kernel. You admitted that it is based on per shoots old GB codebase with your new wiz bang improvements. Why don't you say that here and say that this kernel is an L BS modified version of his kernel. You must just be looking for donations for the work of others?
you're going to continue updating illuminate with this right?
how have you improved playback of video in this kernel? is the improvement rom agnostic?
WiFI Issues
Well I was having intermittent WiFi problems with Illuminate until I flashed this Kernel, now I am just getting an error when I try to connect to WIFI.
jbrianj said:
Well I was having intermittent WiFi problems with Illuminate until I flashed this Kernel, now I am just getting an error when I try to connect to WIFI.
Click to expand...
Click to collapse
Try the latest pershoot GB kernel. And/or try the Flashback of BoS roms
Hi Everybody,
I need some help. I installed this rom into my malata zpad. First opening, there was no problem but after restarting, touchscreen was not worked.
I reinstalled, but same problem was occurred. My touchscreen is not working, only back and home button, which are physical button, are working.
What can I do?
I noticed this behavieur with the latest Version before I hadn´t any problems
I read today that this is Pershoot's latest + cm7 modules. No changelogs, no submissions to github. I read in the rules here something about "don't do anything to get us in trouble". To me this kernel looks like something that might do just that.
I loaded this kernal on top of illuminate yesterday. Couldn't determine if this was already part of the rom or another update to the kernal. In any event it did add some pep to it. Haven't figured out all the improvements yet. It did however mesh nicely with illuminate.
For the record I think this kernel is only compatible with illuminate and bos. Flashing this or clemsyns ver11 onto Flashback breaks the wifi.
ramerco said:
This thread has turned into a joke with no information other than a re-compiled version of pershoot's kernel.
Can it be closed please.
Click to expand...
Click to collapse
No, it is working well. Thanks dev we appreciate all your work. Been driving this one around for a few days to see what was different -- speed. Still investigating but don't stop because you are the only HC dev that works on the kernal and the rom itself we definitely need more like you. Looking forward to your next works!
Kernel source needs provided as per GPL. All this looks like is a rebranding of someone else's kernel - to dispel that belief please provide source and changes or else this will be removed as it would be in violation of the rules.
edirector said:
No, it is working well. Thanks dev we appreciate all your work. Been driving this one around for a few days to see what was different -- speed. Still investigating but don't stop because you are the only HC dev that works on the kernal and the rom itself we definitely need more like you. Looking forward to your next works!
Click to expand...
Click to collapse
He would need a 'first' work to have any 'next' works. Someone who actually took the time to research a little web history might find that the guy is merely a thief of others' ideas and work. They might find that the guy also has multiple usernames and accounts on various threads, in different forums, and actually "talks to himselves" in those threads. They also might find that the guy is also pretty much clueless, and would have exactly a 0.0% chance of developing his own kernel.
I'm not saying they would, I'm just saying they might.
I'd run stock on my Gtab before I ever TOUCHED this.
Just sayin.
By the way, 'eDirector'...In no way was I implying that you could be just another one of linuxboxsolution's 'NPC's.
Of Course I wasn't.
REMOVED my post, as it's off-topic and no longer relevant.
roebeet said:
When I posted in the other thread, I did mention that I didn't know the history - I suppose this is the "other" thread that some had mentioned?
Again, I haven't delved into this kernels and mods, and I do agree mostly with what tlbardelljr had written - "stealing" is a very gray area here. Most of my own ROMs are just mash-ups of other people's work that I tried to make into something more usable for me, and possibly the community.
But, I usually try to give credit also. If I'm using pershoot's ROM, I document that. If I'm using gojimi's framework changes for Brilliant Corners, I give him a nod. If I'm using the Adam HC base for BoS, I give them a nod as well. It's not only good manners, but it's also part of the rules here. If you're going to take, you should give credit. It's not rocket science.
I am not saying that's what's going on here - I haven't looked into these allegations, myself. But jerdog had commented two days ago and I think his comment is not only valid but it's something that needs to be responded to by the OP. That would certainly answer the question and put this to rest.
Click to expand...
Click to collapse
Hello Roebeet,
This may help but I am not sure for I am not a developer...Git Hub Source Location: https://github.com/linuxboxsolution/LBSGtab. Boy I wish I was for I would be on my way to Silicon Valley with my latest brainstorm for the Android platform that's why I respect what you guys can do so much. I can package your coding, sweetly I might add, but I am not a coder.
REMOVED my post, as it's off-topic and no longer relevant.
Offended by what's going here!
Comments removed as promised.
REMOVED my post, as it's off-topic and no longer relevant.
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
There are a lot of zips floating around that fix the bluesleep issue on the Atrix, but I haven't seen any that implement an addon.d script. I made one and have been using it for awhile, and thought I would share.
What is addon.d?
On some ROMs, like Cyanogenmod, there are scripts in /system/addon.d that run during a ROM update or flash. They can backup and restore system apps (like Gapps), or perform many other functions. This mod includes an addon.d script, so the mod is not lost during a ROM update! If your ROM doesn't support addon.d, this mod should still flash properly, but you won't benefit from addon.d.
What is bluesleep?
Bluesleep is a wakelock. A wakelock prevents your phone from going into deep sleep. From my understanding, on the Atrix (and some other devices), when bluetooth is enabled, it will never deep sleep because it's bluetooth system is missing a few binaries. No deep sleep means horrible battery life. This mod changes permissions on 3 files, which fixes the issue.
Tested and Confirmed to work on:
CyanogenMod 10 epinter
It should work on any AOSP based Android 4+ ROM. Let us know if it works!
Install Instructions:
- Boot into recovery
- Flash Enable zip
- Reboot
Uninstall Instructions:
- Boot into recovery
- Flash Disable zip
- Reboot
Downloads:
Enable-BlueSleepFix-1.2.zip
Disable-BlueSleepFix-1.2.zip
Changelog:
Code:
1.2 - 11/30/12
- Minor compatibility fixes
1.1 - 11/29/12
- Initial public release
DISCLAIMER:
This mod involves editing system files. Use at your own risk! Also please don't forget, before you report ROM related bugs in the ROM developer thread, you should remove this mod to make sure the issue is not caused by this mod!
Nice! But I don't have a need for a bluesleep fix... not yet at least great to see more and more people stepping up for development for our Atrix!
I always wondered y this can't be part of an ROM,.... looks like it is now
tnx
Sent from my Transformer TF101 using Tapatalk HD
Great work
Nice. Installing it right away. My battery has been draining in the latest version of epinter's CM10 even with the existing bluesleep fix.
Hope this will resolve the issue. Great ROM and great work..:good:
rmkilc said:
There are a lot of zips floating around that fix the bluesleep issue on the Atrix, but I haven't seen any that implement addon.d. I made one and have been using it for awhile, and thought I would share. What is special about using addon.d? It is a folder with scripts in /system/addon.d that run during a ROM flash. In this case, I made it carry the bluesleep fix through when you flash a ROM update, as long as the ROM supports addon.d (Cyanogenmod does)! No more having to flash a bluesleep.zip after every ROM update.
When flashing a ROM update without addon.d:
- flash ROM
- flash Gapps
- flash bluesleep fix
When flashing a ROM update with addon.d:
- flash ROM
That's it! Works great for the OTA feature in epinter's CM10.
Install Instructions:
- Boot into recovery
- Flash Enable zip in recovery
- Reboot
Uninstall Instructions:
- Boot into recovery
- Flash Disable zip in recovery
- Reboot
Downloads:
Enable-BlueSleepFix-1.1.zip - 125.03 KB
Disable-BlueSleepFix-1.1.zip - 124.65 KB
Changelog:
Click to expand...
Click to collapse
excuse me,what is a "blue sleep" ?
mindstorms54 said:
excuse me,what is a "blue sleep" ?
Click to expand...
Click to collapse
Bluesleep is a wakelock. A wakelock prevents your phone from going into deep sleep. From my understanding, on the Atrix (and some other devices), when bluetooth is enabled, it will never deep sleep because it's bluetooth system is missing a few binaries. No deep sleep means horrible battery life. Bluesleep fix mods change permissions on 3 files, which fixes the issue.
i cant wait till this and battery fix are integrated on cm 7.2 rom!!
antmiu2 said:
i cant wait till this and battery fix are integrated on cm 7.2 rom!!
Click to expand...
Click to collapse
I don't think this will ever be integrated into CM. This issue is controversial to begin with about whether or not it's actually an issue. Your best bet: if your device (not just Atrix) doesn't deep sleep, flash this mod and see if it fixes it. If so, use it!
the hosinn
Is this CM10 specific or does it work for other roms?
Sarmo94 said:
Is this CM10 specific or does it work for other roms?
Click to expand...
Click to collapse
If the "other ROM" supports addon.d, then yes, this should work great. If it doesn't support addon.d, then there is no advantage of using it over any of the other bluesleep zips floating around.
Updated zips. It should work on ROMs that don't support addon.d now too. You just won't have the benefits of addon.d.
My download links will be broken for awhile. Goo.im is having issues, and they are working on it. More information can be found here: https://plus.google.com/103016236037938342074/posts/iWu73keEHtW
In the meantime, if you need a file ASAP, PM me.
Thank a lot for this. Really appreciate it.
Hi everyone ,
I got my Nexus 4 yesterday and I love it! Before I got the phone I did a bunch of research on loading custom ROM's and kernels, and even pre downloaded everything so when it arrived I could start tinkering right away. At the moment it seems Paranoid Android is an ideal ROM for me, as it strikes a nice balance between simplicity and customization. However, it seems that the Matr1x kernel doesn't run well on it due to the JSS/JWR incompatibility issue that came about with Android 4.3. I'd like to run the Matr1x kernel because it has a great balance between performance and battery life, and does some fancy GPU over clocking/CPU undervolting for you that I am too afraid to do on my own.
I found a zip file on the xda forums that remedies the incompatibility issue and allows Matr1x v11 and PA 3.99.1 to run together without issue. So my questions are these:
1. Is there any risk in using this JWR/JSS zip patch? Finding it was a pain in the butt and not many people have commented on its quality or where it comes from. Is it safe?
2. PA's gapps package has a bunch of G+ stuff included that I don't care about. Is there a way to remove it like in some of the slim gapps packages?
3. Has anyone else encountered a static hiss/ticking coming from their earpiece? It can only be heard faintly when the device is up to my ear but it's a little frustrating all the same. Is there a fix for this? Does the device's warranty cover it?
4. Finally, I have one thing I am confused about regarding rooting etc: I have CWMod installed on my phone and I have unlocked my bootloader. By unlocking my bootloader, have I also rooted my phone?
Thanks so much for your time!
Downloaded7 said:
Hi everyone ,
I got my Nexus 4 yesterday and I love it! Before I got the phone I did a bunch of research on loading custom ROM's and kernels, and even pre downloaded everything so when it arrived I could start tinkering right away. At the moment it seems Paranoid Android is an ideal ROM for me, as it strikes a nice balance between simplicity and customization. However, it seems that the Matr1x kernel doesn't run well on it due to the JSS/JWR incompatibility issue that came about with Android 4.3. I'd like to run the Matr1x kernel because it has a great balance between performance and battery life, and does some fancy GPU over clocking/CPU undervolting for you that I am too afraid to do on my own.
I found a zip file on the xda forums that remedies the incompatibility issue and allows Matr1x v11 and PA 3.99.1 to run together without issue. So my questions are these:
1. Is there any risk in using this JWR/JSS zip patch? Finding it was a pain in the butt and not many people have commented on its quality or where it comes from. Is it safe?
2. PA's gapps package has a bunch of G+ stuff included that I don't care about. Is there a way to remove it like in some of the slim gapps packages?
3. Has anyone else encountered a static hiss/ticking coming from their earpiece? It can only be heard faintly when the device is up to my ear but it's a little frustrating all the same. Is there a fix for this? Does the device's warranty cover it?
4. Finally, I have one thing I am confused about regarding rooting etc: I have CWMod installed on my phone and I have unlocked my bootloader. By unlocking my bootloader, have I also rooted my phone?
Thanks so much for your time!
Click to expand...
Click to collapse
1. Should be safe, as long as you have a nandroid backup in case something goes wrong.
2. You just delete the apks from the gapps zip. (system/app)
3. Haven't heard of it. Hope someone else has a solution.
4. Well, no. The term "Rooted" only applies to ROMs, when you have a superuser app and binary installed (Supersu, superuser etc.). But, you are just one step from rooting (Flashing the supersu zip).
All custom ROMs are already rooted, so you don't worry about that.
abaaaabbbb63 said:
1. Should be safe, as long as you have a nandroid backup in case something goes wrong.
2. You just delete the apks from the gapps zip. (system/app)
3. Haven't heard of it. Hope someone else has a solution.
4. Well, no. The term "Rooted" only applies to ROMs, when you have a superuser app and binary installed (Supersu, superuser etc.). But, you are just one step from rooting (Flashing the supersu zip).
All custom ROMs are already rooted, so you don't worry about that.
Click to expand...
Click to collapse
Gotcha, thanks very much for the help. So there's no threat of some 12 year old stealing my credit card if I use that JWR/JSS patch zip?
Downloaded7 said:
Gotcha, thanks very much for the help. So there's no threat of some 12 year old stealing my credit card if I use that JWR/JSS patch zip?
Click to expand...
Click to collapse
Most probably not. Certainly not a 12 year old
Give me a link to the zip. I want to check it out a bit.
abaaaabbbb63 said:
Most probably not. Certainly not a 12 year old
Give me a link to the zip. I want to check it out a bit.
Click to expand...
Click to collapse
This is the only thread I could find with a direct link to the .zip, which has me a bit skeptical since downloading it from a Google Drive account seems kind of sketchy.
http://forum.xda-developers.com/showthread.php?p=45690500
That said, it does work. It got PA and Matr1x running together very smoothly, but I reverted to my backup of stock PA before entering any private info because I wanted to see what others had to say about it first.
Thanks again!
Downloaded7 said:
This is the only thread I could find with a direct link to the .zip, which has me a bit skeptical since downloading it from a Google Drive account seems kind of sketchy.
http://forum.xda-developers.com/showthread.php?p=45690500
That said, it does work. It got PA and Matr1x running together very smoothly, but I reverted to my backup of stock PA before entering any private info because I wanted to see what others had to say about it first.
Thanks again!
Click to expand...
Click to collapse
I think it may not work. It has Adreno 200 and MSM8960 libs in it, a GPU and CPU that have nothing to do with the N4's APQ8064 and Adreno 320. You can still try, because they most certainly don't do any "stealing credit card" stuff.
abaaaabbbb63 said:
I think it may not work. It has Adreno 200 and MSM8960 libs in it, a GPU and CPU that have nothing to do with the N4's APQ8064 and Adreno 320. You can still try, because they most certainly don't do any "stealing credit card" stuff.
Click to expand...
Click to collapse
I did some more digging and found that the guy responsible for the patch has a profile on xda, found here: http://forum.xda-developers.com/member.php?u=3873953 and he seems pretty legit. The patch is also linked in the Purified Kernel thread page: http://forum.xda-developers.com/showthread.php?t=2368548 as a recommended work-around for the JSS/JWR graphical glitching. I installed v1.0 on my Nexus 4, which did nothing to help, then I installed v1.2 (linked in OP), and I now have Paranoid Android 3.99.1-RC running (so far) flawlessly on Matr1x v11. Pretty happy about that .
Downloaded7 said:
I did some more digging and found that the guy responsible for the patch has a profile on xda, found here: http://forum.xda-developers.com/member.php?u=3873953 and he seems pretty legit. The patch is also linked in the Purified Kernel thread page: http://forum.xda-developers.com/showthread.php?t=2368548 as a recommended work-around for the JSS/JWR graphical glitching. I installed v1.0 on my Nexus 4, which did nothing to help, then I installed v1.2 (linked in OP), and I now have Paranoid Android 3.99.1-RC running (so far) flawlessly on Matr1x v11. Pretty happy about that .
Click to expand...
Click to collapse
Nice! Good to know.