[KERNEL][Stock 4.4] 22-12-2013 Enhanced Kernel (All models) - sweep2sleep/fast charge - Moto X Original Android Development

Based on 13.11.3Q2.X-69-3-2 source
Compatible with all unlocked GSM/Verizon models on stock Android 4.4 (uses existing ramdisk)
Features:
- Built with Linaro toolchain
- Init.d support
- Stock undervolted
- Fast charge
- Voltage Control
- Custom sweep2sleep (swipe from right-to-left at the bottom of the screen)
- Max screen off frequency (default 706mhz)
Download 0.3: http://d-h.st/Xxq
* Tested with TWRP/CWM. The installer will create a backup of your boot image before starting.
* Settings are compatible with Trickster Mod
Source: https://github.com/rob43/motox_kernel
0.3 Changes:
- Lowered stock undervolt amount for stability
- Harder to activate sweep2sleep

...

I'm going to install this. At the risk of sounding like I'm new here, if this borks my phone, I can just fastboot the stock boot image, yes?
Sent from my XT1056 using Tapatalk

Bradart said:
I'm going to install this. At the risk of sounding like I'm new here, if this borks my phone, I can just fastboot the stock boot image, yes?
Sent from my XT1056 using Tapatalk
Click to expand...
Click to collapse
Yep. It will also back up the original image to the sdcard if you don't have it.

Never mind. I apparently just learned to read!
Sent from my XT1058 using XDA Premi

Its good to see someone built a kernel for this device. I was starting to lose hope..lol
@matt99017d Use twrp to flash
Sent from my XT1060 using Tapatalk

Yea, @jwthompson just re-read it and realized it was for unlocked devices.....boo.
I got all excited when I saw "stock"
I was hoping I could extract it and fastboot it.
Sent from my XT1058 using XDA Premium 4 mobile app

Please update if you downloaded v1, wifi had issues with the first release.

Finally a custom kernel. Thx
Enviado desde mi XT1053 mediante Tapatalk

Good job buddy, flashing now.

Does not work for me: bootloop with bootlogo and blank screen. XT1058 Latam with unlocked bootloader with T-Mobile 4.4 stock ROM. Open Recovery as custom recovery.
After restoring original boot.img from backup (made in Open Recovery) I am not able to find boot_backup.img. Looks like it is not created at all.

Installed no prob on vzw Dev. Back up is made to the root of sdcard

Installed via dhacker29's CWM6.0.4.5 recovery and the kernel works.

Kernel works good on xt1060...however....could sweep to sleep be moved to the top? I keep accidentally putting it to sleep when typing.

timpohladthomas said:
Kernel works good on xt1060...however....could sweep to sleep be moved to the top? I keep accidentally putting it to sleep when typing.
Click to expand...
Click to collapse
Try the new version, it should be harder to activate

Would love to have fast charge on a locked moto x :/
Sent from my Nexus 7 using Tapatalk

Works great on Droid MAXX DE. Thanks!

Anyway you could make a version for 13.11.3Q2.X-69-3-8?
It is for the XT1058 model.

Thanks OP! I can't believe it's taken this long to develop a kernel ; thanks for your efforts! What are your plans for the kernel? Cheers! :beer:

Anyone else having issues accessing the wifi settings menu? Not quite sure why the kernel would affect this, unless it cant load wifi connections, but it freezes upon entry.

Related

[ROM]May 13| Speed Rom|Fast|Smooth|Great Battery

Speed Rom with two things always important
Speed And Battery Life
Includes:
Based on RUU 1.78.401.2
Deodexed
Zipaligned
Rooted
Unsecured boot.img
RAM optimizations
Added busybox
Tweaked for best performance
Fast and Smooth UI
Deleted bloatware
Deleted freedback apps
Ability to choose any language you want
General clean up
Added ES File Explorer
A lot of other changes
550Mb of free Ram
This is a Senseless Rom with apex launcher
To Install
Flash a custom recovery
Flash the Rom
Reboot
I AM NOT RESPONSIBLE FOR WHAT YOU DO TO YOUR PHONE
Flash Android Fastboot Kit V1.0 before flashing device. It contains new kernel needed for proper work.
Flash Android Fastboot kit
*Note there might be bugs
Alpha
Download Here!
Nice I hope to try ALL of these ROMs in a few months! Love to see development go on here. Nice work EclipzeRemix
Downloading now, will let you know how it goes, thanks op
I tried installing but got an infinite bootloop of death... Had to restore. I'll try again tomorrow.
Sent from my HTC One S using Tapatalk 2
General problem with 1.78 base.
HTC with tapatalk
invasion2 you actually got this phone.
downloading!!!!
I too am getting the boot loop, so I can't even get it to boot to the homescreen.
Going to try and fix it soon
Sent from my HTC_Amaze_4G using Tapatalk 2
Why post work in the Dev section that is completely broken and a waste of user's time? Mods please close thread?
Sent from my HTC One S
Opentang said:
Why post work in the Dev section that is completely broken and a waste of user's time? Mods please close thread?
Sent from my HTC One S
Click to expand...
Click to collapse
Excuse me, as far as I know, eclipse does not own this device, so he he is probably doing this blindly, he is also developing for another device so if he cant fix this Rom, than now you know, just a heads up
Sent from my HTC_Amaze_4G using Xparent Green Tapatalk 2
I want to be able to use this Rom 550 mb of free ram is great!
Sent from my HTC VLE_U using XDA
I would fix this and make a great rom but I need testers
Sent from my HTC_Amaze_4G using Tapatalk 2

[KERNEL] [JB 4.2/4.2.1] Stock kernel - CWM flashable

Hello all,
I made this over at the GNex forums for a stock GNex 4.2/4.2.1 kernel... here it is for the Nexus 7 for those that accidentally flashed a 4.1.2 kernel or just want to get back to stock.
Flash at your own risk, should work just fine though!
UPDATED: Kernel should work now! Sorry about the bad zip before!
Will it work on 4.1.2? I have AOKP on my device, would like to flash this, just need to check if it's safe...
Cheers
Sent from my Nexus 7 using xda app-developers app
where were you couple of days ago when I was dealing with the issue - trying to flash stock kernel.....wish you posted this before.
I will save this just in case :silly:
thanks!!!
I flashed LeanKernel and then wanted to go back to stock kernel before flashing latest Faux Kernel.
So I have just flashed your kernel but "about tablet" is telling me I still have LeanKernel installed?
If you can overclock then you're still on lean kernel. Either way, I'd suggest a reflash.
Sent from my Nexus 7 using xda premium
Caliyork said:
If you can overclock then you're still on lean kernel. Either way, I'd suggest a reflash.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
It was definetely still on LeanKernel, I tried it twice.
Only issue could be that I was using an older version of TWRP that wasn't updated for 4.2, but it seemed to flash ok.
edit
Ok, tried it again now I have the updated TWRP and the same thing happens...i.e. nothing, it flashes in the normal way but changes nothing.
This is all wrong. The boot.img inside does not match the one from the N7 nakasi factory image and the updater-script is written for the Galaxy Nexus.
Code:
"of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");
N7 certainly doesn't run OMAP. Flash at your own risk, indeed.
I urge you to take this down and make sure you know you've got it right before you put it up again. Only saving grace here is you were using the platform by-name method (which just plain won't work on the N7) instead of the actual mmc block names or you could have really messed up some peoples' devices.
osm0sis said:
This is all wrong. The boot.img inside does not match the one from the N7 nakasi factory image and the updater-script is written for the Galaxy Nexus.
Code:
"of=/dev/block/platform/omap/omap_hsmmc.0/by-name/boot");
N7 certainly doesn't run OMAP. Flash at your own risk, indeed.
Click to expand...
Click to collapse
My mistake. I thought it would just transfer over. I will fix the link... Didn't realize when I tested it I already had the stock kernel on there. Gimme a minute to fix it!
OK should be fixed and good to go! Again, my apologies!
Sent from my Galaxy Nexus using Tapatalk 2
stonebear said:
It was definetely still on LeanKernel, I tried it twice.
Only issue could be that I was using an older version of TWRP that wasn't updated for 4.2, but it seemed to flash ok.
edit
Ok, tried it again now I have the updated TWRP and the same thing happens...i.e. nothing, it flashes in the normal way but changes nothing.
Click to expand...
Click to collapse
Please try again... I have updated my zip and tested it by flashing a 4.1.2 kernel, having the device sit at the X for a few minutes without doing anything (to test a non-working kernel) then flashing my zip, and my N7 is back up and running again.
I am still learning about kernel stuff... sorry about any confusion!
SkaldfraNorden said:
Will it work on 4.1.2? I have AOKP on my device, would like to flash this, just need to check if it's safe...
Cheers
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Negative. This is the stock 4.2 kernel... I found the stock 4.1.2 kernel on XDA... Should be easy to find!
Sent from my Galaxy Nexus using Tapatalk 2
Where can I find the stock kernel for the Galaxy Nexus running on 4.2? If you can redirect me to the link, I'll greatly appreciate it. Thanks in advance.
evaradar said:
Where can I find the stock kernel for the Galaxy Nexus running on 4.2? If you can redirect me to the link, I'll greatly appreciate it. Thanks in advance.
Click to expand...
Click to collapse
wasn't that hard to find out, but here you go: stock kernel
This is JOP40C kernel for 4.2 but will it work on JOP40D 4.2.1 stock ROM please ?
I've added this kernel to the Nexus 7 Complete Index
Sent from my Nexus 7 using xda premium
..
BTW..Excellent system stability with this kernel and rasbeanjelly ROM. Tested on my daughter.
cydef said:
This is JOP40C kernel for 4.2 but will it work on JOP40D 4.2.1 stock ROM please ?
Click to expand...
Click to collapse
+1
Sent from my Nexus 7 using xda app-developers app
Can anyone confirm if the kernel listed (jop40c) is the actual kernel used in the stock 4.2.1 system? The build is jop40d, and the question seams to be getting overlooked. I cannot find the stock jop40d 4.2.1 kernel anywhere, and just do not have any interest at this time in flashing the factory image/re-rooting etc. Any help would be appreciated.
annoyingduck said:
Can anyone confirm if the kernel listed (jop40c) is the actual kernel used in the stock 4.2.1 system? The build is jop40d, and the question seams to be getting overlooked. I cannot find the stock jop40d 4.2.1 kernel anywhere, and just do not have any interest at this time in flashing the factory image/re-rooting etc. Any help would be appreciated.
Click to expand...
Click to collapse
This.. I was about to post, my N7 (16g, wifi) is JOP40D as well, not 40C.
Thinking about trying out a custom kernel, but want the stock to fall back on, as it's super stable.
khaytsus said:
This.. I was about to post, my N7 (16g, wifi) is JOP40D as well, not 40C.
Thinking about trying out a custom kernel, but want the stock to fall back on, as it's super stable.
Click to expand...
Click to collapse
As it turns out, I built a "slightly rooted" JOP40D stock flash kit yesterday (mods to build.prop in boot.img, and su/SuperSU in system.img). I'm posting this reply from that.
I started with the Google JOP40D (grouper) distro to do that. I thought I was going to need to unpack the boot.img from the OP's .zip to do comparisons of the kernels (to answer your question) ... but it turns out that his boot.img has the same MD5 sig as the boot.img from Google's JOP40D... and the OP's updater-script merely flashes boot.img to the /boot partition.
That means one of two things: either the two successive Google releases (for grouper) had identical boot images (which implies identical kernels), or there is some mistake by the OP. (I don't have the 40C distro to check ... only picked up my N7 a few days ago.)
It should work in your specific case though, as you are on JOP40D.
In any event, flashing boot.img is way way more than just a kernel replacement. I haven't looked at it for a while, but I would suppose that Koush's kernel flasher is a much more appropriate technique for switching ONLY the kernel out from underneath an arbitrary ROM.
cheers
That's great info there. I'm searching for the simplicity of just flashing a kernel instead of pushing the entire boot image. Thanks for a step in clarifying this question
Sent from my Nexus 7 using xda premium

[ROM][Sept 12th 2013] GE 4.3 JWR66Y.H1 BlackJelly 1.2 Deodexed/Odexed

Nothing flashy, just straight to the point:
4.3 Google Edition Rom JWR66Y.H1
Features:
Rooted
Busybox
Deodexed
Init.d support
Unsecure boot.img
AOSP Browser (credits @blackhand1001)
Nova Launcher Added
MMS with Emoji and Quick Reply (credits @jase33)
Holo Backgrounds replaced with Black
Smaller overall system font (don't like it? too bad, change it in settings or flash another font)
Xposed FW installer
Gravity Box Xposed Mod
Adobe Flash
To do:
Add Battery %
Some more themeing
Instructions:
Flash in recovery, if coming from a sense rom a full wipe is required. If coming from another GE rom you should be fine. If you are coming from CM/AOKP you might be ok with a dirty flash, if not then full wipe.
No requests! I make this rom to MY liking and just decide to share it with everyone. If there is a feature I would use, then I would add it but if it's something I wouldn't use then I will not add it to the ROM.
Download Link version 1.2 Deodexed: http://forum.xda-developers.com/devdb/project/dl/?id=411&task=get
Mirror: http://d-h.st/OEE
Download Link version 1.2 Odexed: http://forum.xda-developers.com/devdb/project/dl/?id=413&task=get
Mirror:http://d-h.st/lbR
I will work on this op later when I get back from school.
Disclaimer: I am not responsible if you flash this and it bricks your device, makes it blow up or impload, Fire starts shooting from it or if it kills your neighbor's dog. FLASH AT OWN RISK.. Again, I am NOT responsible if you screw up your device
XDA:DevDB Information
[ROM][Sept 12th 2013] GE 4.3 JWR66Y.H1 BlackJelly 1.2 Deodexed/Odexed, a ROM for the HTC One
Contributors
graffixnyc
ROM OS Version: 4.3.x Jellybean
Version Information
Status: Stable
Created 2013-09-07
Last Updated 2013-09-14
Change Log:
9/12/2013- Updated base to JWR66Y.H1. Didn't put the APM in but included xposed installer and gravity box which can do that and then some
8/8/2013- Added APM Menu, Restore stock Host file, Added Adaway App
8/7/2013- Initial release

			
				
One of the faster GE Roms so far.. Love love love inverted stuff. Nice work man. Running flawless so far
Sent from my HTC One using Tapatalk 2
Nice another GE to test
Cool, thanks mate, let's test it... I'm curious... Keep it up!
Sent by the one and only
InflatedTitan said:
One of the faster GE Roms so far.. Love love love inverted stuff. Nice work man. Running flawless so far
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
Wait who's this? Get back too the onexl forums :sly: :thumbup:
Sent from my METAL PHONE not some plastic phone bloated phone
Nice work sir. The rom is very zippy.
I'll report my battery consumption findings after a full charge and a day off charger.
My eyes hate the smaller fonts, but they look very sharp.
I think I'm going to give this a whirl tomorrow morning....
Sent from my HTC One using Tapatalk 2
Cant wait to try this out! thanks!
graffixnyc said:
Nothing flashy, just straight to the point:
4.3 Google Edition Rom JWR66V
Features:
Rooted
Busybox
Deodexed
Init.d support
Unsecure boot.img
AOSP Browser (credits blackhand1001)
Nova Launcher Added
MMS with Emoji and Quick Reply (credits jase33)
Holo Backgrounds replaced with Black
Smaller overall system font (don't like it? too bad, change it in settings or flash another font)
To do:
Add APM
Add Battery %
Some more themeing
Instructions:
Flash in recovery, if coming from a sense rom a full wipe is required. If coming from another GE rom you should be fine. If you are coming from CM/AOKP you might be ok with a dirty flash, if not then full wipe.
No requests! I make this rom to MY liking and just decide to share it with everyone. If there is a feature I would use, then I would add it but if it's something I wouldn't use then I will not add it to the ROM.
Download Link: http://d-h.st/0z8
I will work on this op later when I get back from school.
Disclaimer: I am not responsible if you flash this and it bricks your device, makes it blow up or impload, Fire starts shooting from it or if it kills your neighbor's dog. FLASH AT OWN RISK.. Again, I am NOT responsible if you screw up your device
Click to expand...
Click to collapse
what recovery do you use sir
Jerzdre said:
what recovery do you use sir
Click to expand...
Click to collapse
I use twrp but it should be fine with cwm
Sent from my HTC One using Tapatalk 4
graffixnyc said:
Nothing flashy, just straight to the point:
4.3 Google Edition Rom JWR66V
Features:
Rooted
Busybox
Deodexed
Init.d support
Unsecure boot.img
AOSP Browser (credits blackhand1001)
Nova Launcher Added
MMS with Emoji and Quick Reply (credits jase33)
Holo Backgrounds replaced with Black
Smaller overall system font (don't like it? too bad, change it in settings or flash another font)
To do:
Add APM
Add Battery %
Some more themeing
Instructions:
Flash in recovery, if coming from a sense rom a full wipe is required. If coming from another GE rom you should be fine. If you are coming from CM/AOKP you might be ok with a dirty flash, if not then full wipe.
No requests! I make this rom to MY liking and just decide to share it with everyone. If there is a feature I would use, then I would add it but if it's something I wouldn't use then I will not add it to the ROM.
Download Link: http://d-h.st/0z8
I will work on this op later when I get back from school.
Disclaimer: I am not responsible if you flash this and it bricks your device, makes it blow up or impload, Fire starts shooting from it or if it kills your neighbor's dog. FLASH AT OWN RISK.. Again, I am NOT responsible if you screw up your device
Click to expand...
Click to collapse
graffixnyc said:
I use twrp but it should be fine with cwm
Sent from my HTC One using Tapatalk 4
Click to expand...
Click to collapse
oh ok, cuz i was a bit confused to which recovery worked with the google edition running 4.3
man you're awesome at this s***, keep it up
I'll never understand why people insist on quoting full op's.
Thanks graffixnyc for sharing your rom. Hopefully I have time to try it before work tonight.
Sent from my HTC One using Tapatalk 4
CheesyNutz said:
Wait who's this? Get back too the onexl forums :sly: :thumbup:
Sent from my METAL PHONE not some plastic phone bloated phone
Click to expand...
Click to collapse
Been lurking cheezeballs, been having a one for a bit now. Still stalk the OneX threads lol
Sent from my HTC One using Tapatalk 2
How can I change the DPI to larger font.. Maybe through terminal emulator?
big nu said:
How can I change the DPI to larger font.. Maybe through terminal emulator?
Click to expand...
Click to collapse
http://bit.ly/17yA52W
big nu said:
How can I change the DPI to larger font.. Maybe through terminal emulator?
Click to expand...
Click to collapse
you can just change it is settings -> display. Make it large or huge if you want. The small default is the "normal" size. Or you can just flash a different font
Been running this since yesterday when you posted it in the other thread. Dirty flashed over GPe 4.3, I've been off the charger for more than 14 hours and still have 65% battery left. This might be the best battery life I've seen on my one, and I normally allow a few days for the ROM to settle in before I comment on the battery.
Kudos man. We appreciate all your hard work. :beer:
AT&T HTC One
GPe 4.3
graffixnyc said:
you can just change it is settings -> display. Make it large or huge if you want. The small default is the "normal" size. Or you can just flash a different font
Click to expand...
Click to collapse
Changing the font only helps with some things. There are still some words that remain small.
Sent from my HTC One using Tapatalk 4

MOTO G, custom ROM = Yes or No?

I have been using Custom Rom's for a while. But this is usually to bring a phone up to the latest possible Android version well after the manufacturer has stopped updating a device . I have been using Nexus devices so typically this is 18 months after a model is first introduced. Bit of a sore point with me coming from iPhones which get supported for much longer period. but I digress.
In the case of the Moto G. I question whether it is beneficial ATM to install a custom ROM? I have tried a couple, but have been quite disappointed up till now with reliability and performance.
So for now I have stayed with the standard Moto G Rom. Then tweaked it a little by doing the following.
1. Unlocked the phone
2. Rooted using TWRP (couldn't get CWM to work right)
3. Eliminated the Unlocked warning screen at start up :- http://forum.xda-developers.com/showthread.php?t=2548530
4. Changed the 3G data to H, H+ format :- http://forum.xda-developers.com/showthread.php?t=2600654
5. Installed Qualcomm-optimized bionic and dalvic from here :- http://forum.xda-developers.com/nexus-4/general/4-4-4-4-x-qualcomm-optimized-dalvik-t2546120 (thanks @drfr )
6. Installed a new Faux123 Kernel, flcon_umts-faux123-kk-005u-signed.zip from here :- http://faux.romhost.me/falcon_umts/kk44/
7. From Play store installed the xposed installer
8. From Play Store added module Gravity box (KK)
9. From Play Store added module Ringer & Notification Volume
10. Installed the Apex launcher
11. From Play Store purchased Faux123 Kernel Enhancement Pro (couldn't find a free tool that worked!)
Result is a very stable ROM together with most of the little tweaks that I like to get from a Custom ROM. Plus everything works great. The current Antutu result is 19860.
So my general question, what is the advantage of using a Custom Rom, when for at the moment at least, the manufacturers ROM is fully up to date and with a few simple tweaks provides Custom Rom like appearance, together with great stability and performance?
As far as I know, the stock rom has a lot of optimizations for the Moto G hardware. For instance, its based on F2FS which is something the GPE Moto G does not have going for it.
Sent from my XT1034 using Tapatalk
grahamgo said:
...
Click to expand...
Click to collapse
That´s exactly the way I see things too. Played around with custom ROMs for a while and then came back to stock + all the enhancements you mentioned. Just a note to the point 5 of your list. Optimized dalvik and bionic are already included in stock ROMs.
I have this way of thinking too. So just going through the steps 1, 2, 3, 7, 8 and 10. My phone is excellent.
drfr said:
That´s exactly the way I see things too. Played around with custom ROMs for a while and then came back to stock + all the enhancements you mentioned. Just a note to the point 5 of your list. Optimized dalvik and bionic are already included in stock ROMs.
Click to expand...
Click to collapse
Thank you, I didn't know that, funny but I could swear that Antutu improved! I am still trying to decide if Point 6. Faux123 is really worth it. The 1.6gh/z over clocking is working and I am still getting two days of average use per charge. Can't decide either way really......
Same here, at this point, custom roms (non stock based) are non sense, since the stock is almost Aosp and updated as hell. Xposed is all you need.
Sent from my XT1032 using XDA Premium 4 mobile app
All you need is Xposed, Faux kernel and the optimized Dalvik :S
Enviado desde mi iPod touch con Tapatalk
Correct me if I am wrong but the stock roms from moto are equipped with the Qualcomm-optimized bionic and dalvik patches, aren't they?
If not where can I find this patches?
Soerdroid said:
Correct me if I am wrong but the stock roms from moto are equipped with the Qualcomm-optimized bionic and dalvik patches, aren't they?
If not where can I find this patches?
Click to expand...
Click to collapse
1. http://forum.xda-developers.com/showpost.php?p=48932223&postcount=430
2. http://forum.xda-developers.com/nexus-4/general/4-4-4-4-x-qualcomm-optimized-dalvik-t2546120
Great antutu result. Mostly due to the overclock. CM based roms doesnt have working overclock yet.
Im far away from that 19860 antutu score, any tips? I installed faux kernel and optimizers from qualcomm and cant get even close to 18000.
Enviado desde mi XT1032 mediante Tapatalk
grahamgo said:
I have been using Custom Rom's for a while. But this is usually to bring a phone up to the latest possible Android version well after the manufacturer has stopped updating a device . I have been using Nexus devices so typically this is 18 months after a model is first introduced. Bit of a sore point with me coming from iPhones which get supported for much longer period. but I digress.
In the case of the Moto G. I question whether it is beneficial ATM to install a custom ROM? I have tried a couple, but have been quite disappointed up till now with reliability and performance.
So my general question, what is the advantage of using a Custom Rom, when for at the moment at least, the manufacturers ROM is fully up to date and with a few simple tweaks provides Custom Rom like appearance, together with great stability and performance?
Click to expand...
Click to collapse
True. But its for now and that is because this is a brand new phone also with multiple variants like 1031/2/3
Hence creating a kind of obstruction for a successful ROM dev
Furthermore you don't just dev a ROM to get an Android update.
Its for the different features that people are looking for.
You might wanna try xposed modules.
Hell l0tta options there. Not for now but then for future.
Also then small little tweaks from other phones can be ported to this one.
There are just countless things that you can customize once you are rooted.
I had a Galaxy Ace duos CDMA which had no custom ROM.
But once I got it rooted my phone was so much better.
I had an extended internal memory with my SD card.
The bloatware that covered the small little internal memory was completely removed.
And it was so much faster and Functional with those rooted apps.
If that small little phone could do some magic with rooting.
Then this is a beast.
Half the new functionality that we get on the updates are actually the features of apps that work on rooted phones.
Wifi hotspot for an instance.
Agreed that in the current scenario its really not so useful but rooting your phone is a gift to yourself
Sent from my XT1033 using xda app-developers app
How you guys were able to use Faux with Dalvik? Faux only works on my phone with ART. If i try Dalvik, com.android.phone force closes all the time. I also have tried the new dalvik, no luck either.
And that prevents me to use XPosed, cause it doesn't have an ART version. And i really miss GravityBox...
Can someone explain me how to do it?
Moto G Dual Sim (XT1033) with KitKat 4.4.2
checked the system/lib in my motog stock(nongpe) and doesnt have all the files from the Qualcomm-optimized Dalvik & Bionic libraries so can I have the latest version links to flash?Thanks
tsimitsangaz said:
checked the system/lib in my motog stock(nongpe) and doesnt have all the files from the Qualcomm-optimized Dalvik & Bionic libraries so can I have the latest version links to flash?Thanks
Click to expand...
Click to collapse
Look into system/vendor/lib
Sent. Really?
yes checked.. I need to have ( libc.so, libm.so, libcutils.so, libdvm.so, libqc-opt.so, libcutils.so) and I have only libqc-opt.so from these files.
tsimitsangaz said:
yes checked.. I need to have ( libc.so, libm.so, libcutils.so, libdvm.so, libqc-opt.so, libcutils.so) and I have only libqc-opt.so from these files.
Click to expand...
Click to collapse
You do have all those files, they are not in the same folder. Just search harder.
intellq said:
How you guys were able to use Faux with Dalvik? Faux only works on my phone with ART. If i try Dalvik, com.android.phone force closes all the time. I also have tried the new dalvik, no luck either.
And that prevents me to use XPosed, cause it doesn't have an ART version. And i really miss GravityBox...
Can someone explain me how to do it?
Moto G Dual Sim (XT1033) with KitKat 4.4.2
Click to expand...
Click to collapse
No one?
intellq said:
No one?
Click to expand...
Click to collapse
Use this rom, stock, debloated, faux kernel and xposed. Clean and fast.
http://forum.xda-developers.com/showthread.php?t=2606943
[ROM]Nexus G+ Build 007[4.4.2]
Sent from my XT1032 using XDA Premium 4 mobile app
Alejandrissimo said:
Use this rom, stock, debloated, faux kernel and xposed. Clean and fast.
http://forum.xda-developers.com/showthread.php?t=2606943
Click to expand...
Click to collapse
That rom probably won't work in my phone. I'm on an XT1033 (dual sim)
Someone with stock was able to make faux + dalvik work?

[ROM][NOOK HD+] Unofficial CM10.2.1 Stable w/ TabletUI + ArchiDroid Optimizations

CM10.2.1 Stable* for Nook HD+ (Ovation)
Credit to
-Verygreen and CM team for Ovation's CM10.2
-JustArchi for build optimizations
-Caldair for TabletUI patch
In this edition:
--- TabletUI capable. Caldair's patch stopped working after nightly Dec 5, 2013. I reverted minor commits to mainly translations and circle battery to allow the patch to succeed:
--- ArchiDroid Optimizations using GCC 4.7
http://forum.xda-developers.com/showthread.php?t=2754997
The build using GCC 4.8 toolchain would not boot, but all other optimizations remain.
--- 30 media volume steps
--- 0.25x animation speed options under developer settings
--- Tiny reduction to cm10.2 speaker gain to reduce distortion at highest volumes.
--- STABILITY. Not my doing. In my experience, cm10.2 rarely reboots or crashes.
--- Flash videos works well enough
*Technically a June 14 nightly post-stable. However, there have been very few commits since the 10.2.1 stable was released months before.
**Touch fuzz 3x5 and Trim support are already integrated into the CM10.2 kernel. No need to flash an old separate kernel.
__________________________________________________________________________________________________________​Installation notes:
-Compatible with New and old CWM recovery (no need to downgrade)
1)Format /system AND factory reset (data, cache), then flash ROM zip
2)Flash GAPPs for android 4.3. These work: http://forum.xda-developers.com/showthread.php?t=2240652 (Use 4.3)
-DO NOT restore system data from CM11
3)First complete a full boot and setup of the rom before installing tabletUI patch
Download ROM: http://d-h.st/jpd
Download TabletUI Patch: http://d-h.st/5Ar
*DO NOT install the tabletUI patch without first completing a full boot and setup of the rom.*
__________________________________________________________________________________________________________​TIPS
For a permanent menu button, I like to set my nook hardware key to open/close menu.
Xposed modules can do this or you can edit the gpio user key file very easily.
Go to the folder user - > key layouts - > gpio-keys.kl
Edit the file with system rw.
Change the word "HOME" to "MENU". Reboot.
Default trebuchet launcher slow? Try Nova or Apex from store. They work a lot better in my experience.
__________________________________________________________________________________________________________​UPDATE 6/21:
Fixed ExFat support.
Added ROW I/O, Intelliactive CPU governor.
Get flash player below!
Enjoy!
__________________________________________________________________________________________________________​Chrome Pop-up blocker perfect for visiting Dev-Host
Looks good I will try it out later this morning and let you know how it goes.
jamus28 said:
Installation notes:
"Assert" line has been removed from the updater script to allow compatibility with the kitkat recoveries.
Click to expand...
Click to collapse
You are going to be sorry you did that if someone with an HD gets a hold of this and tries to flash it. It will brick his device.
A better solution is to use the update-binary from a kitkat zip and the assert works.
Sent from my BN NookHD+ using XDA Premium HD app
Overall pretty good so far. Very smooth. Still testing.
Sent from my BN NookHD+ using XDA Free mobile app
---------- Post added at 11:29 AM ---------- Previous post was at 11:00 AM ----------
Screen can be a bit twitchy, anyone know if there is a fuzz kernel for 10.2?
Sent from my BN NookHD+ using XDA Free mobile app
Was trying an app called map book and it reboots my tablet. Never used it before so it could be an app issue and not a Rom problem but figured I would mention it if someone else wanted to try it.
Sent from my SPH-L900 using XDA Free mobile app
leapinlar said:
You are going to be sorry you did that if someone with an HD gets a hold of this and tries to flash it. It will brick his device.
A better solution is to use the update-binary from a kitkat zip and the assert works.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I see what you're saying, but it's a bit of an exaggeration to say someone will brick. They'll need to boot into recovery and flash a new Rom.
I deleted the line because not everyone has the new kk recovery, and I want it to be compatible with both.
jpisini said:
Overall pretty good so far. Very smooth. Still testing.
Sent from my BN NookHD+ using XDA Free mobile app
Screen can be a bit twitchy, anyone know if there is a fuzz kernel for 10.2?
Sent from my BN NookHD+ using XDA Free mobile app
Click to expand...
Click to collapse
Dr. Marbles touch (3x5 I remember?) fuzz commit is already integrated. If it's laggy for you, maybe try to run a manual trim with lagfix and reboot. Also, the stock launcher is a bit slow, I'd get Nova or similar.
jamus28 said:
I deleted the line because not everyone has the new kk recovery, and I want it to be compatible with both.
Click to expand...
Click to collapse
If you did what I said it will be compatible with both new and old recoveries. That way you will not be responsible for causing grief for noob HD users.
The issue is not that the assert line exists, it is because the KK recovery using the older update-binary interpreter from older zips causes the assert statement to fail. If you put a new update-binary from a kk ROM in your ROM then the kk recovery will interpret the assert command correctly and it passes. The beauty is that older recoveries also interpret the assert command correctly using the new kk update-binary.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
If you did what I said it will be compatible with both new and old recoveries. That way you will not be responsible for causing grief for noob HD users.
The issue is not that the assert line exists, it is because the KK recovery using the older update-binary interpreter from older zips causes the assert statement to fail. If you put a new update-binary from a kk ROM in your ROM then the kk recovery will interpret the assert command correctly and it passes. The beauty is that older recoveries also interpret the assert command correctly using the new kk update-binary.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I didn't know the new assert line was backwards compatible. I'll upload a new one. Would using the newer update-binary be enough or do I need to alter the update-script as well?
jamus28 said:
I didn't know the new assert line was backwards compatible. I'll upload a new one. Would using the newer update-binary be enough or do I need to alter the update-script as well?
Click to expand...
Click to collapse
Just put the original assert line back and put the kk update-binary file in your ROM zip replacing the one that is built with the CM10.2.1.
Sent from my BN NookHD+ using XDA Premium HD app
Ok done. Thanks for clearing that up.
For those who didn't understand what leapinlar was talking about, don't worry. The ROM is exactly the same. No need to reflash.
Also, since there's some confusion around, I should mention that 3x5 touchfuzz and trim support have been in all cm10.2 nightlies/stables since november 23 and jan 8, respectfully. There's no need to download an old separate kernel from the one of the threads.
https://github.com/CyanogenMod/android_kernel_bn_omap/commits/cm-10.2
Took a break from cm11 due to the aggressive memory management affecting multitasking, and installed this. Pretty solid, smooth and speedy. Great work!
Just found out that my 32gb Samsung MicroSD card formatted with exfat file system doesn't seem to be mounting. It shows up fine in TWRP though.
Edit: Fixed below
jamus28 said:
Yes I had trouble with exfat and cm10.2 as well. Its not unique to our device either. I would use ntfs or ext4/3.
Click to expand...
Click to collapse
It works fine on official 10.2 Nightlies and the stable 10.2.1. Just a heads up.
This is the exact rom I have been looking for: a solid, smooth, stable rom with optimization.
Even though I jumped boat to 4.4 for one night, but 10.2.1 is my all time favorite! Now with this rom I don't think I would even need to use recovery in the future!
Thank you so much for the work, @jamus28
andr0idfreak said:
It works fine on official 10.2 Nightlies and the stable 10.2.1. Just a heads up.
Click to expand...
Click to collapse
You know what, you're right. It's the kernel optimizations. I see a commit patch for it too. When I get the chance I'll recompile those files.
jamus28 said:
You know what, you're right. It's the kernel optimizations. I see a commit patch for it too. When I get the chance I'll recompile those files.
Click to expand...
Click to collapse
Could you also test setting the fuzz to 8x8?
Just as a test build, maybe separate?
andr0idfreak said:
Took a break from cm11 due to the aggressive memory management affecting multitasking, and installed this. Pretty solid, smooth and speedy. Great work!
Just found out that my 32gb Samsung MicroSD card formatted with exfat file system doesn't seem to be mounting. It shows up fine in TWRP though.
Click to expand...
Click to collapse
Try this
http://d-h.st/jpd
Haven't had chance to test.
Also added Row I/O scheduler and intelliactive governor options
jamus28 said:
Try this
http://d-h.st/jpd
Haven't had chance to test.
Also added Row I/O scheduler and intelliactive governor options
Click to expand...
Click to collapse
Thanks for the quick update and this fixed the mounting issues of sdcards formatted with exfat. Thanks a ton!
jamus28 said:
Try this
http://d-h.st/jpd
Haven't had chance to test.
Also added Row I/O scheduler and intelliactive governor options
Click to expand...
Click to collapse
Been running this since yesterday morning looking very good fast and stable. Thanks for all your work.
Loving this. One glitch I noticed was with the xposed framework per app settings made my status bar disappear. Odd and probably the fault of the app. But still loving this ROM. Thanks a million! My only request is a menu button in the status bar.
Sent from my BN NookHD+ using XDA Free mobile app

Categories

Resources