HTC Explorer Pico Development

Awesmoe smartphone with Awesome specs in just 6k!

2014-09-03T15:55:00.001+05:30

Post by Mi India.
To Buy click on link given below....

Beanstalk [Multi Window] for HTC Explorer/pico

2014-03-14T14:17:00.003+05:30

[Rom][4-3-1][Beanstalk][Multi Window][11.12.2013]

Feature List.... Its a long one and growing every day!

CM based

Insane amount of edits/tweaks/fixes to make this build absolutely fly

Ultimate battery life through optimizations

HALO)))

Lockscreen background options (Color fill, Custom image, Transparent)

Customizable Lockscreen text color

Lockscreen rotation

Option to enable all widgets

Minimize lockscreen challange

Use widget carousel

Slider Shortcuts

Static Lockscreen shortcuts

Lockscreen button actions

LCD Density

Scroll elasticity options

Default App grip option

Custom Carrier label

Dual Pane options

Customizable boot animation (off, default, set your own bootanimation)

Custom original BeanStalk Wallpapers by skyliner33v

Custom BeanStalk bootanimation by skyliner33v

Status bar color and transparency

Clock and date options which includes color, location, style

Signal Styles which include color and text instead of icons, alternate GB signal layout, hide signal icons

Breathing SMS option

Battery styles - Includes specific colors and styles. Also includes battery bar

Do not disturb option

Show notification count

Pie controls (need to have lockscreen background set to something other then default to work correctly (dont ask why) )

Fully customizable navigation bar - Includes style, layout, color, nav rings, pretty much everything you can think of.

Quick settings color settings, tiles per row, Quick pulldown, text color

Notification shortcuts, behaviour, drawer style (customizable colors), toggle colors, longpress quicksettings icon to enable/disable toggles

Keyboard and input method options which include disable full screen keyboard and auto rotate

Kil app back button with customizable timeout values

High end graphic effects option

option to disable/enable vibrate on expand for notifications alerts

Low battery warning customizable options

Recents RAM bar fully customizable with color styles

Clock widget for LockClock including extra options to fully customize every feature of the lockclock

Build.prop MOD options to enable/disable tweaks as preferred

Less frequent Notification sounds options

CRT screen off/on options to specify how the animation shows

Enable/disable wake up on charge option

Superuser fully embedded into the build and accessed from settings menu

CM Performance options and features

About BeanStalk option with links to github source and facebook for beanstalk. Also links to my twitter and donate.

option to use a fully themable MMS packages. You can access from mms - settings - theme settings

Numerous other options hidding throughout the build

Instruction

Do a factory reset
Flash Rom & Gapps
Reboot
Done
-----------------------------------------------------------------------------------------------------------------------------

Beanstalk Boot animation

Screen Shots

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Download

ROM :- HERE
Gapps :- HERE

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Gallery fc's while opening camera.

Attached Thumbnails

P.A.C Man ROM For HTC Explorer/Pico

2014-03-14T14:10:00.002+05:30

[ROM][4-3-1][All MDPI] P.A.C Man ROM [ 11-12-13 ]

PAC-man ROM is a combination of the three Super ROMs Available
Paranoid Android + AOKP + Cyanogenmod = PAC-man

This ROM packs all the tweaks from the three super ROMs into one.
Why choose among ROMs, When you have All-in-One !!

Code:

* All in One Rom [PA, AOKP and CM]

* PhoneUI, TabletUI, PhabletUI

* Latest Version Nightly Builds

* All Feautures from PA

* Some Features from AOKP

* All Features from CM

* Parts from Slim Bean

* Parts from Rootbox

* Parts from Carbon

* Basically if there is a cool feature out there and its open source,
  then we will try to bring that feature into PAC-man
 (insert PAC-man eating a pellet sound here)

* Of course JellyBean 4.3

Code:

* CM's bugs

* Submit a bug

Code:

* Download the PAC-man ROM and GApps
 
* Reboot to Recovery

* Make Factory Reset

* Flash the ROM & GApps

* Reboot your phone

* And enjoy the latest version of PAC

----------------------------------------------------------------------------------------------------------------------------

Code:

ROM :- HERE

Gapps :- HERE

Attached Thumbnails

----------------------------------------------------------------------------------------------------------------------------

Buggs
No button works except home button
Camera app doesnt work
No input Method
Very slow

--------------------------------------------------------------------------------------------------------------

Have trouble in using this ROM ?
Yes, that is due to Gapps (the one posted by OP is not working properly and .... users are complaining for that !!!)

This Gapps will work coz it's working for me (download it..)
http://d-h.st/Df1
::Not my work::
-------------------------------------------------------------------------
About my experience on this PAC Man ROM
-------------------------------------------------------------------------
1. Battery is charging super fastly (and draining normally) (far better than the ROMs which takes 4hours for charging and discharging at the same rate)
2. Lots of customization available.
3. It's a good experience to have a ROM which can be crafted to any UI modes i.e. TABLET, PHABLET, PHONE
4. int2ext+ working
5. Super Slim.... 12MB still remaining in /system even after flashing the above prescribed Gapps and ODEXING the whole ROM (frameworks and apps).
6. Full of animations...(unbelievable) (good, but I would recommend using Seeder)

::BUGS (Blame Tyler for that)::
SYSTEM Settings > Storage (crashes)
Camera app (crashes) (3rd party camera apps works)
PAC-MAN Settings > Init.d (crashes)
(I would also recommend to use another launcher)

How about performance compared to cm10.2 w9? Is it better?

CyanogenMod 11 for HTC Explorer/Pico

2014-03-14T14:03:00.003+05:30

[DEV][ROM][4.4.2][KOT49H][ION] CyanogenMod 11 | BETA 5 | 05/03/2014

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KITKAT), which is designed to increase performance and reliability over stock Android for your device.

Code:

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

No Maps 7 glitches, Browser glitches, Gmail glitches, etc.
Uses ION memory allocator
Uses the newest Adreno (graphics) libraries and firmware available for our platform (these graphics libraries are newer than the graphics libraries in any other ROM; they were used in Android 4.2 for the Nexus 4)
Significantly smoother/faster graphics as a result of the new graphics libraries
Removed many hacks designed for old graphics
Adreno libraries version: AU_LINUX_ANDROID_JB_VANILLA_04.02.02.060.053

What's working:

GSM
Receiving and making calls
Display
Camera (photos, camcorder & panorama)
Audio playback
Audio recording
Video playback
Screenshot
Stock browser
WiFi
WiFi tethering
Bluetooth
Bluetooth tethering
SDcard
GPS

Not working:

You tell...

It's entirely possible that features not used by me are broken, but overall the device should be usable. You have been warned.

Before using ART, you have to enable expanding memory in Settings -> Extras!

Download:

BETA 5 : http://forum.xda-developers.com/show...postcount=1469

BETA 4 : http://forum.xda-developers.com/show...postcount=1074

BETA 3 : http://forum.xda-developers.com/show...&postcount=585

BETA 2 : http://forum.xda-developers.com/show...&postcount=457

BETA 1 : http://forum.xda-developers.com/show...&postcount=200

Gapps : http://goo.im/devs/BaNkS/GApps/4.4.2 (minimal gapps)

Install instructions:

Boot into Recovery
Wipe data and cache
Flash the CM11 zip
Reboot
Reboot into Recovery
Install gapps
Reboot

Upgrading from earlier version of CyanogenMod 11:

Boot into Recovery
Flash CM11 zip
Reboot

----------------------------------------------------------------------------------------------------------------------------

Changelog

BETA 5 05-03-2014

Fixed instagram
Fixed active touch in-call with S2W
Fixed MMS crash (upstream)
Fixed crash on theme changing (upstream)
Fixed invisible video controls (upstream)
Updated GPS HAL
Updated RIL libs
Updated drivers/staging/android
Enabled CMA
Final touch on sd-ext toggle
Increased in-call volume

BETA 4 04-02-2014

Fixed black screen issue in some games
Fixed in-call sound distortion (robotic voice)
Fixed Voice Search
Fixed Sound Recorder
Fixed random frezzes
Fixed PIN lockscreen layout
Fixed face detection FC
Fixed SDext mounting
Fixed USB tethering
Added memtrack module (fixes memtrack logcat spam)
Added S2W (with toggle)
Added charging animation (with toggle)
Added SDext memory increase toggle (int2ext)
Switched to ION audio subsystem

BETA 3 23-12-2013

ION
New Adreno blobs and firmware
Fixed graphical glitches
Fixed Emoji keyboard
Fixed auditd logcat spam
Fixed 0,00B RAM bug
Updated CM sources

BETA 2 14-12-2013

Fixed stock browser
Fixed SDcard mounting properly
Fixed lockscreen clock
Updated CM sources to Android 4.4.2

BETA 1 28-11-2013

Fixed Camera
Fixed Video Recording
Fixed Native screenshot
Fixed Recent Apps menu preview
Fixed battery icon alignment
Fixed genlock errors
Partially fixed stock browser [have glitches, but not full black like before]
Enabled low RAM optimizations introduced in 4.4

ALPHA 1 24-11-2013

Updated CM sources (KRT16S)
Fixed WiFi
Fixed SDcard
Fixed Video Decoding

PREVIEW BUILD 20-11-2013

Initial release

---------------------------------------------------------------------------------------------------------------------------

ScreenShot:

-----------------------------------------------------------------------------------------------------------------------------

Omni ROM[TeamCody] for HTC Explorer/Pico

2014-03-14T14:01:00.000+05:30

[KK4.4.2][KVT49L][ROM][ION][TeamCody]Omni ROM ▒ BUILD 6 ▒ 16 Feb 2014

OmniROM is a free, community built, aftermarket firmware distribution of Android 4.4 (KitKat), which is designed to increase performance, reliability and features over stock Android for your device.

Code:

#include <std_disclaimer.h>
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you. Hard. A lot.
 */

OmniROM is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts.

All the source code for OmniROM is available in the OmniROM Github repo.

NOTE: This is a developer discussion thread. All questions and answers can go here: http://forum.xda-developers.com/show....php?t=2597615

We'll not support users and answer questions from users who:

are running a custom kernel
have flashed mods
modified system files
are unfriendly

Even if you tell us that your problem is not related to your custom kernel /mod / magic => WE DON'T CARE!
Your mod => your problem!

Official OmniROM Wiki:
http://docs.omnirom.org

Notable features:

No Maps 7 glitches, Browser glitches, Gmail glitches, etc.
Uses ION memory allocator
Uses the newest Adreno (graphics) libraries and firmware available for our platform (these graphics libraries are newer than the graphics libraries in any other ROM; they were used in Android 4.2 for the Nexus 4)
Significantly smoother/faster graphics as a result of the new graphics libraries
Adreno libraries version: AU_LINUX_ANDROID_JB_VANILLA_04.02.02.060.053

What's working:

Display
Audio playback
Video playback
Camera/Video
RIL
Screenshot
Stock browser
WiFi
Bluetooth
SDCard

Untested:
These features are like cats on a wall. They can be either working/not working. Test and report, so I can put them in their place ;)

WiFi tethering
GPS
Bluetooth tethering

Issues:
Note: If you find any more issues, please report, so that I can add them here :)

Not that I found any, but you can try and report any bugs!

Quote:

It's entirely possible that features not used by me are broken, but overall the device should be usable. You have been warned.

Before using ART, you have to install some reverse-mount script like int2ext!

Downloads:

BUILD #6: http://forum.xda-developers.com/show...&postcount=103

BUILD #5: http://forum.xda-developers.com/show...0&postcount=97

Beta #4: http://forum.xda-developers.com/show...4&postcount=88

Beta #3: http://forum.xda-developers.com/show...9&postcount=59

Beta #2: http://forum.xda-
developers.com/showpost.php?p=48931766&postcount=24

Beta #1: http://forum.xda-developers.com/show...8&postcount=11

Alpha #1: http://www.mediafire.com/download/g3...-ALPHA%231.zip
Alpha #1 mirror: http://d-h.st/eQw

Gapps: http://www.androidfilehost.com/?fid=23269279319195954 (thanks to @abhijaincha and @Nihar.G for testing)

First time installing OmniROM to your HTC Pico, or coming from another ROM:

Read known issues and FAQs
Copy GApps and OmniROM ZIPs to your SDCard
Boot into Recovery
DO A DATA WIPE / FACTORY RESET (otherwise your device will be stuck at boot)
Flash OmniROM zip from SDCard
Flash GApps zip from SDCard
Reboot

Quote:

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

--------------------------------------------------------------------------------------------------------------

Changelog :)

Changelog:

Quote:

Build 6 Changelog : 16 FEB 2014:

Latest upstream changes (KVT49L)
A new bootanimation (lags, as ain't properly resized for our device... you can help me do so, by resizing it, from here: https://github.com/omnirom/android_v...tanimation.zip)
Note: The new bootanimation isn't included in this build because it gives some very nasty OOM errors, causing phone to not boot. So, reverted back to old bootanim. Will work fine on resizing.
One bug fix, (the controls not showing in video player (in h/w acceleration mode))
option to revert back to classic webview (though we still using chromium) (open up build.prop and change "persist.webview.provider" from "chromium" to "classic")

Quote:

Build 5 Changelog : 13 FEB 2014:

Fixed Camera (video recording's derped for now. metadata's disabled, but this time, its some kind of codec error, non support for legacy)
Upstream changes (notably the Omni Sound Packs, more info here: http://forum.xda-developers.com/show....php?t=2630011), and OFC, NTFS support!

Quote:

Beta #4 - 10-Feb-2014
frameworks/base:

Multi-Window Patchset 18 (as its stabler) (https://gerrit.omnirom.org/#/c/1510/)
omniarmv6 patches merged
htc headset handling fixed

system/core:

omniarmv6 patches merged

android/build:

omniarmv6 patches merged

vendor/omni:

omniarmv6 patches merged

frameworks/av:

omniarmv6 patches merged

frameworks/native:

omniarmv6 patches merged

hardware/ril:

patched up for support for legacy htc ril

device/htc/pico:

removed/updated overlay
reverted ums to 50 (speeds terrible with 20, but stable)
smaller languages list (removed am_ET ne_NP hi_IN pa_INpa_IN ml_IN si_LK th_TH lo_LA km_KH)
Fixed black screen issue in some games
Fixed in-call sound distortion (robotic voice) (fixed by stock libaudio)
Fixed Voice Search (fixed by stock libaudio) (someone check)
Fixed Sound Recorder (fixed by stock libaudio) (someone check)
Added memtrack module (fixes memtrack logcat spam) (thanks to lozohcum)
removed qcom_bsp support as we ain't using it!?

kernel/htc/pico:

Added S2W
use common cm kernel, with s2w, reverted back ion audio alloc (would be patched in next build)

Quote:

Beta #3 - 04-Jan-2014

Updated omni sources (till 4th Jan) (with various cherry-picks to get camera working, check these here: https://github.com/vineethraj49/andr...ts/android-4.4)
Updated libaudio (but headphones not fixed yet :\ )
Fixed FC in Settings>Notification Drawer>Contextual notification panel
Included latinIME, after removing all the dictionaries (don't change the language, and you're fine )
Yes, lockscreen clock's "broken"... But, enable immersive mode, it's worth it p.s. someone could help me patching that XML

Quote:

BETA #2 - 29-Dec-2013

Camera fixed!
RIL fixed!

Quote:

Beta #1 - 28-Dec-2013

ION
New Adreno blobs and firmware
Fixed graphical glitches
Updated Omni sources (KOT49H)

Quote:

Alpha #1:

Initial Release

Beanstalk ▒ BETA 2 [TeamCody] for HTC Explorer/Pico

2014-03-14T13:57:00.003+05:30

[KK4.4.2][ROM][TeamCody]Beanstalk ▒ BETA 2 ▒ 11 Feb 2014

Quote:

I am proud to present to you BeanStalk Builds put together by myself. This is a build composed off of the CM builds and i have added alot of features on top of it. So you get speed, stability, and ultra customization ability. Many of the additional code additions came from slim ROM and also Derteufels build and have been modified to work with my current setup. A huge thanks to Derteufel and the Slim ROM guys for their work and dedication. Also a big thanks to everyone involved with CM as that is the building stone in this project. Thanks to skyliner33v for the bootanimation and upcoming wallpapers!

I plan on updating this and adding features on a pretty regular basis, so if you happen to like this, keep checking back.

Like what you see? Click the thanks button or Donate to scott.hart.bti by clicking HERE

Interested in Porting/Building BeanStalk on another device? Check out Post #3!
If you have building/development concerns or issues, Please visit the BeanStalk Development Thread to avoid cluttering this thread.

CM based
Lockscreen background options (Color fill, Custom image, Transparent)
Customizable Lockscreen text color
Lockscreen rotation
Option to enable all widgets
Minimize lockscreen challange
Use widget carousel
Slider Shortcuts
Static Lockscreen shortcuts
Lockscreen button actions
LCD Density
Scroll elasticity options
Default App grip option
Custom Carrier label
Dual Pane options
Customizable boot animation (off, default, set your own bootanimation)
Custom original BeanStalk Wallpapers by skyliner33v
Custom BeanStalk bootanimation by skyliner33v
Status bar color and transparency
Clock and date options which includes color, location, style
Signal Styles which include color and text instead of icons, alternate GB signal layout, hide signal icons
Breathing SMS option
Battery styles - Includes specific colors and styles. Also includes battery bar
Do not disturb option
Show notification count
Pie controls (need to have lockscreen background set to something other then default to work correctly (dont ask why) )
Fully customizable navigation bar - Includes style, layout, color, nav rings, pretty much everything you can think of.
Quick settings color settings, tiles per row, Quick pulldown, text color
Notification shortcuts, behaviour, drawer style (customizable colors), toggle colors, longpress quicksettings icon to enable/disable toggles
Keyboard and input method options which include disable full screen keyboard and auto rotate
Kill app back button with customizable timeout values
High end graphic effects option
option to disable/enable vibrate on expand for notifications alerts
Low battery warning customizable options
Recents RAM bar fully customizable with color styles
Clock widget for LockClock including extra options to fully customize every feature of the lockclock
Build.prop MOD options to enable/disable tweaks as preferred
Less frequent Notification sounds options
CRT screen off/on options to specify how the animation shows
Enable/disable wake up on charge option
Superuser fully embedded into the build and accessed from settings menu
CM Performance options and features
About BeanStalk option with links to github source and facebook for beanstalk. Also links to my twitter and donate.
insane amount of edits/tweaks/fixes to make this build absolutely fly
option to use a fully themable MMS packages. You can access from mms - settings - theme settings
Numerous other options hidding throughout the build

FC's! Missing drawables might cause random FC's here and there. Please get me a logcat, or at least post the exact steps that'd reproduce the problem

Find one suitable, yourself; and post here if it works :p

***For a complete listing of all supported BeanStalk devices and downloads, please visit www.goo.im/devs/beanstalk***

***Our device isn't supported, so downloads are below***

BeanStalk Build 4.4.240 - 11/Feb/14: http://forum.xda-developers.com/show...6&postcount=16

BeanStalk Build 4.4.215 - 12/Jan/14: http://www.mediafire.com/download/28...40112-pico.zip

***Please keep in mind that this is the initial release and bugs are to be expected. Before reporting bugs, please make sure you verify everything on your end and make sure you do a full wipe and format first to make sure it is a legitimate issue. Im going to say this once and only once... I am doing this for fun. It is my CHOICE to share my work with everyone. If you decide that you do not like my work, good for you.. Move on and flash something else. I will not tolerate ungrateful people in my thread.***

Copy ROM,
Reboot into Recovery,
Factory Reset,
Flash ROM,
Reboot.

SlimROM source can be found HERE
DerTeufel's source can be found HERE
My source can be found HERE

--------------------------------------------------------------------------------------------------------------

Ok, let's quote scott.hart.bti here.

Quote:

I am doing this for fun. It is my CHOICE to share my work with everyone. If you decide that you do not like my work, good for you.. Move on and flash something else. I will not tolerate ungrateful people in my thread.

I remember my first work, around 7 months ago, which I released on XDA (before that I was just working on some random tools, scripts and stuff, making custom themed CM ROMs, naming them "Zeta ROM" etc), which was Cyanic Sense. Before that I had my first experience "making" a kernel. It took 40 minutes on my pre-pentium 4 processor. I remember Rishik999 who I worked with. I remember releasing a flashable zip for the Stock ROM v1.43.720.2 with the combined efforts of me, rishik and racerroney, with help from explorerman.

Back to cyanic sense, Though it was just theming, it was difficult, for I didn't know where to start. I quit that, because of two reasons.
1. stock, was buggy, and slow.
2. there wasn't any "real" developing that I was doing.
2.5. I had got a new computer, so, no longer did I have to wait for ~40 minutes to get a kernel compiled.

Now, looking back to about two months ago. The end of october. Cyanogenmod ICS was the first ROM that I compiled, just to test the specs of my pc, build times, etc. Still, I was making builds at the rate of a build per hour and half, or so. Looked at MiniCM, there was great potential in there, for it. I was starting to learn things.

MiniCM was THE greatest project (IMO, until now) ever that I worked on, that I can be proud of (till this day), just because I did it, and It was my first work. No matter, I decided to "stabilize" the ICS ROM with k3.0.101. I remember that day, when @rcane had released a flashable s2w zip update for it on the thread. I flashed it, didn't work. Decided to make it work, and voila! That was the first build, with very few changelog.
First, started out with cherry-picking, (too many of them), most useful ones had been abandoned by them cm-gerrit, just because ICS was outdated. decided to create repos, and implement some real useful features into ICS, making it "rock stable", and stuff as you'd say it. User suggestions started flowing in (those who did care for ICS). Had a hard time keeping up with all the features that the users requested (not many, as only a few used ICS). I wasn't able to fix up all their requests, but still... Anyways, I was still learning. Collaborated with Umair (omerjerk), and went on to add toggles and stuff... Finally, went on to create CodyROM, (with some more great collab, with Vaibhav (#Superuser), and Dhruman (dhrumangajjar)) just because of two things:
1. It was over with the MiniCM brand name, as it limited my functionality.
2. Users really didn't think any different of MiniCM, and i was just the guy, providing builds, and they neither do that now, either.

I also did a few builds of cm10, cm10.2, but never really released them. just because there wasn't anything that I added or so :\

Did anyone bother? Nope. Except the ones who used ICS? Nope. Did I bother? Nope. Because I knew I was outdated, and Kitkat had released too, so none really bothered. Did I care? No. Because I was learning. That project gave me both the headstart and confidence, experience and a little knowledge about the android build system.

Without it, I wouldn't be what I am today.

Finally, went from "I" to "we". Then, there was quite a some pressure from "people" regarding, "ICS is outdated", "move on", and so on...

So, decided to work on my first kitkat ROM, Omni. Thanks to the experience that I gained from MiniCM, and CodyROM, I was able to get it booted at first attempt (using the really outdated device tree at picokat) (the tree's still the same way).

Ok, so Kitkat booted. Problems: audio not routing. RIL didn't work. black screen in browser. dang outdated, because pico was using ION. and mainly: incompatibility of sources. AOSP doesn't simply make sources compatible. Even now, for CM, we use a hacked display-legacy, media-legacy, and frameworks/av. hoepfully, there were certain commits in the gerrit of omni, that helped me along the way. I'd like to thank sachin thomas for helping me get ION booted in pico, and cute_prince for enabling ION in the pico kernel. This fixed some of the issues. Also, few others like Nihar, and galaxyfreak helped, and RIL, camera working. That was Omni, for Pico. That was the ever first release of TeamCody, in kitkat.

At this point, i'd take a timeout to say how the ROMs itself are made:
First they add the features (keeping in mind to add compatibility later)
ROMs are compatible for nexus, voila! great! bravo!
And, at some point of time, it slips out of their mind that they have to add compatibility too.

One common example of it would be missing drawables. When adding new featues, mostly these are tested in XHDPI devices, like the Nexus? So, another problem faced: I really wouldn't know what's missing, until I boot the ROM, and get hell lot of FC's.

Meanwhile, ROMs were releasing in the Development section. Ported ROMs. I was never with the idea of ported ROMs, because I have a blind belief that ROMs built for the device would be stabler, and bugs can be more easily fixed that way. (not that I don't use ported ROMs. I do use them, in cases inevitable, or when I don't be able to build them from source)

So, decided to make them ROMs, so that I could fix bugs, along the way, thus helping the community back, and in the course, learning more. If you'd have seen, Carbon, AOSPA, Beanstalk, AOKP was already ported. I'd done only Evervolv, and Omni.

AOKP was a request by Amal, who said that he couldn't get AOKP booted with ION by porting... Evervolv, I did it for the legacy support (they're teh best at that). Beanstalk, I had a strong feeling to get this one done. because of the customizations available. Carbon, had to be done, because its another great ROM. Omni, was my wish to do.

Now, there's one thing that *most* of the custom ROMs lack today. Legacy support. I decided to use AOSPA-legacy repos, just because one can't build from the official AOSPA repos for older hardware. its built FOR nexus. Carbon, NVM, had a tough time cherry-picking commits. AOKP, was equally difficult. Omni, please. They said that legacy support would be their prime aim. now, all that vanished into thin air.

On the other hand, Cyanogenmod, says you. Great! Functionality at its best! Reason: solid legacy support! legacy support at its best. ALL phones are likely supported. You just need to hack device specific repos that are hardware oriented like media-legacy, display-legacy, and frameworks/av to get it working. Its easy to just sync the cm repos, and make fully booting, working ROMs, "without any bugs", as you say.

But, that's not the case with all other ROMs, both cm-derived and otherwise.

It takes time to find, merge support for legacy devices like ours.

It takes time to find missing drawables.

It takes time to hash out all changes that are "device specific" breaking builds, or so.

It takes time for me to build kitkat. 3 hours, for the first compile, with ccache, and a hour and half the next time. Not to mention, 3 hours, if the build doesn't break. and the build doesn't boot? then, derp around with frameworks, and hardware repos a bit more to find why it doesn't work, and how to get it working.

I don't have a build server that churns out builds every half an hour, so that I can test it, rebuild with fixes.

Beanstalk's frameworks/av was almost not synced with CM's for the past few days.

Also, Beanstalk had missing drawables, as said earlier, just like Carbon did. Sorry, if it seems like I'm repeating stuff.

And yes, users seem to be very very biased to names, ROms, and otherwise.

Cyanogenmod, yes. A build by a "recognized person", yes. I remember joilaroi, the person who was responsible to making a very stable cm-10.2, was first recieved with "doubt" when he said that he'd fixed them bugs.

Ok, this post's gone too far. Spoke too much.

I ain't saying that I am a great developer or anything. The real great people are the poeple who work on the ROMs, and its features. I am still learning stuff. just that it's taking too much of a toll on me, my health, and my academic life.

I've still got a lot to learn, and won't be *not* doing it, just because people say so.

Finally, I quote scott again.

Quote:

Don't like what I said? Go on, report this post. Report me. Just to let you know, that I don't give a damn.

ParanoidAndroid (AOSPA-legacy)[TeamCody] for HTC Explorer/Pico

2014-03-14T13:51:00.001+05:30

[KK4.4.2][KOT49H][ROM][ION][TeamCody]ParanoidAndroid (AOSPA-legacy) ▒ BETA 3 ▒ 08 Feb 2014

DISCLAIMER:
Your device, your responsibility. I am not liable for anything you flash, including this.
As a result you'll probably want to read the rest of the thread and at least be aware of what you're flashing.
You've been warned.

Android Open Source Paranoid Android
HTC Explorer (pico) using Official AOSPA-legacy repos
4.4 Base

Features:
AOSPA-legacy is the project headed by PA team member slick_rick to support other devices for PA beyond Nexus.
Only deviations are to allow it to build properly and are generally from CM repos.
Any modifications, enhancements, etc. will be brought in and supported through their Gerrit review process and/or Github pull requests into AOSPA-legacy repos.

Downloads:

Beta #3: http://forum.xda-developers.com/show...6&postcount=13

Beta #2: http://forum.xda-developers.com/show...4&postcount=10

Beta #1: https://www.mediafire.com/download/w...A-20140107.zip

GApps: Not tested. See if you find a suitable package.

Flash Instructions:
1) Back up your current system and all data if desired.
2) In your favorite custom recovery, wipe data, cache and dalvik.
If you want to flash the ZIP version you'll need to format system as well.
3) ROM - ZIP - Flash ZIP in recovery
4) Flash GApps

Summary Changelog (edited to remove device specific changes):

Quote:

AOSPA 4.0 Beta 4 <2014-01-27>

Restored two finger quick setting pull down
Immersive mode fixes (also, now a dual tile)
Network toggle tile is disabled if Google dialer is installed
Sleep tile long press opens power menu
Long press rssi (mobile network) tile takes you to data usage
Dimmed dual tile switch icon
Downloads notification now expandable (show download speed)
Add SuperSU to settings, hide app from launcher

Quote:

AOSPA 4.0 Beta 3 <2014-01-20>

Quick settings 3.0
Maximize lockscreen widgets
Fix bug with rotation lock tile
Update AOSP dialer icon to Google dialer icon
Separate device encryption password from lockscreen password
Contextual "on-the-spot" preference dialog (first implementation: Quick settings pull down)
AOSP dialer check (removes features that rely on AOSP dialer if Google dialer is installed)
Other AOSP bug fixes

Quote:

AOSPA 4.0 Beta 2 <2014-01-13>

Updated SuperSU
Increasing Ringtone
Additional Quick Setting Tiles
Quick Settings Pulldown (statusbar right side)
See Through Lockscreen (blur effect implemented) <Credits: David:D >

Bug Fixes:

Fix lockscreen blur rotation on tablets
Fix quick settings edit mode icon transparency
Fix possible force close when enabling see through lockscreen

Quote:

Initial Release - AOSPA 4.0 Beta <2013-12-24>

Built-in SuperSu
Advanced Power Menu
Enhanced Volume Buttons
Enhanced Volume Controls
Global Immersive Mode Toggle
Actionable Status Bar Date/Time
Keyguard Quick Unlock [standard]
Disable full screen keyboard [standard]
Basic file browser (Documents <from Omni>)
Exposed Google's Native App Privacy Controls
Recent/Clear All Button Combo (context aware)
Screenshot Delete Added to Screenshot Notification
Optional Lock Screen Transparency (blur effect WIP)
Optional Status Bar Battery Icons (mirrored in quick settings)
Quick Settings 2.0 (edit tiles from within the pull down panel)

___________________________________________________________________________________

~~Expect Beta 2 today.~~
Did I say something?

Changelog:

Code:

upstream changes
added halo
Fixed up two derped up lines in BoardConfig.mk (thanks to galaxyfreak)

OTOH, call audio bug hasn't been fixed, yet.

Download:

Beta #2: https://www.mediafire.com/download/n...h-20140112.zip

CyanogenMod 11 Weekly Builds [S2W][TeamCody] for HTC Explorer/Pico

2014-03-14T13:48:00.001+05:30

[ROM][4.4.2][S2W][TeamCody] CyanogenMod 11 Weekly Builds - 21/01/2014

As we got CM11.0 to beta-state fast, I decided to run weekly builds of it.

What are Weekly builds?
CM11.0 builds of the latest CyanogenMod sources from github, so you always have latest CM features and fixes.
New version will come out every week, most often during the weekends.

This is not a replacement for development thread. Post bugs there!

Quote:

Additional Features:
-Sweep2wake

---------------------------------------------------------------------------------------------------------------

Downloads

Quote:

It isn't really necessary that we do only one build per week

We *might* do more than one build, so, it'd be uploaded as weekly 1.1, 1.2 and so on.

Weekly 1: http://www.mediafire.com/download/bq...ICIAL-pico.zip

Weekly 2: http://forum.xda-developers.com/show...9&postcount=38

-------------------------------------------------------------------------------------------------------------------------

What's so special about this photo? The output of

Code:

cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies

Code:

122880 245760 320000 480000 600000 678000 722000 767000 800000 816000 828000 844000 878000

i.e. the overclocked frequencies show up only if two partitions exist. else, nope.

Attached Thumbnails

CarbonROM[TeamCody] for HTC Explorer/pico

2014-03-14T13:46:00.000+05:30

[KK4.4.2][KOT49H][ROM][ION][TeamCody]CarbonROM ▒ BETA 1 ▒ 11 Jan 2014

CarbonRom is an aftermarket firmware based on the Android Open Source Project.

We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.

Please feel free to look at, build, and use our code on CarbonDev GitHub.

We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.

Special thanks also go to Slim Rom for some of their features, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.

While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.

CarbonDEV Gerrit (but keep in mind the build date in the title)

Carbon Updates:

Join us on these Social Media Channels to keep yourself up-to-date on all the latest Carbon news, updates, contests/giveaways, and more! Join our completely open Google+ community for insider conversation with devs and other users! Join us and our fans in #teamcarbon on irc.freenode.net for chat.
---------------------------------------------------------------------------------------------------------------------------

Reserved

Downloads:

Beta #1: http://www.mediafire.com/download/4j...-2129-pico.zip

--------------------------------------------------------------------------------------------------------------------------

Working *hard* to get the bootanimation resized

nvm, got the bootanimation resized.

Here's how I did it:

For batch-resizing bootanimation (in linux):

resizing part:

Code:

for file in *.png; do convert $file -resize 320x320! $file; done

you'd know which part to edit

for zip'ing part:

Code:

zip -r -y -q -0 bootanimation.zip *

will edit this later

--------------------------------------------------------------------------------------------------------------------------

Patch For fixing Call audio!

-------------------------------------------------------------------------------------------------------------------------

Evervolv 4.0.0 for HTC Explorer/Pico

2014-03-14T13:39:00.000+05:30

[KK4.4.2][KOT49H][ROM][ION][TeamCody] Evervolv 4.0.0 ▒ Alpha 1 ▒ 30 Dec 2013

What is Android KitKat?
http://www.android.com/versions/kit-kat-4-4/

What is Evervolv?
Evervolv is an AOSP (Android Open Source Project) rom. They're fully open sourced and encourage it with no restrictions. The work put into this ROM is community driven and Evervolv Project is made up of numerous members and contributors.

Right now the current source they are working on is KitKat (Android 4.4.x).
Current Evervolv version: 4.0.0

Project Status: Nightlies.

Quote:

NOTE: HTC GINGERBREAD based roms - Android 2.3.x are the last ROMs that can be considered bug free. AOSP/CM for the Pico was never released by HTC. Development only exists in this community. There will be nuances and quirks that would not be there with OEM roms. Adjust your expectations accordingly.

Downloads:

Consider this an alpha. Lots still not ironed out, like camera working, but video recording *not*, but you can take it for a spin. Be sure to back up your current ROM first, so you can restore it...

Alpha #1: https://www.mediafire.com/download/r...0.0-ALPHA1.zip
--------------------------------------------------------------------------------------------------------------------------

Patch For fixing Call audio!

patch_callaudio: patch_callaudio.zip

This should fix the "user at other end not able to hear your voice properly" bug

If it doesn't work, reboot once?

p.s. This *should* be flashable on all of my kitkat ROMs, but I need testers for them all.

================================================== ==================================

patch_camera: patch_camerafix.zip

Reason for making camera fix separate: libaudio patch should be available for all kitkat ROMs

This should fix the "user at other end not able to hear your voice properly" bug

If it doesn't work, reboot once?

p.s. This *should* be flashable on all of my kitkat ROMs, but I need testers for them all.

---------------------------------------------------------------------------------------------------------------------------

KITKAT [ PARANOIDANDROID 4.0+] for HTC Explorer/pico

2014-03-14T13:33:00.003+05:30

[AOSPA 4.4.2 KOT49H] [ROM] [ION] [Beta] PARANOIDANDROID 4.0+ [29/12/2013]

AOSPA 4.0+ PARANOIDANDROID [beta]
Kitkat 4.4.2 KOT49H android-4.4.2_r1

Before proceeding make sure that
[*] you are on the latest TWRP
[*] 3 sd-ext partiitons

---> SD-SYSTEM ---> atleast 500 MB
---> SD-DATA --------> atleast 500 MB ( this will be your internal memory )
---> SD-CACHE -----> atleast 150 MB

1. DOWNLOAD YOUR ROM

ROM : HERE

2. DOWNLOAD GAPPS

GAPPS: HERE

3. Wipe 3 sd partitions

follow this : HERE

4. FLASH ROM & GAPPS

5. Reboot
----------------------------------------------------------------------------------------------------------------------------
RKING

Same as CM11 beta 3

Not working

USB mount : - use Multimount SD
Video Recorder .

-------------------------------------------------------------------------------------------------------------------------------

Unofficial Carbon builds for HTC Explorer/Pico

2014-03-14T13:30:00.003+05:30

[ION][ROM][KIT-KAT][4.4.2]Unofficial Carbon builds [ 29 - 12 - 13 ]

About Carbon

CarbonRom is an aftermarket firmware based on the Android Open Source Project. We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.

Please feel free to look at, build, and use our code on CarbonDev GitHub.

We would like to thank CyanogenMod for their device trees, framework/settings mods and their code that was incorporated into this project. We also extend our gratitude to the devs whose code that we have incorporated. Proper authorship has been maintained and can be viewed on our repository.

Special thanks also go to Slim Rom for some of their features, PA, AOKP, and anyone else we may have borrowed commits from that hasn't been mentioned here. If you feel you have been unfairly left out, please - let us know.

While we make every effort to test these builds as much as possible, we are not responsible for anything that may happen to your device, family, pets, or perception of reality. We ask that you do your part to know your device and know how to recover from problems before you flash! If you have questions, ask your fellow users or ask us in #teamcarbon on freenode IRC.

Features

Simply stated, we can't really list features here. There are too many and they change too frequently, and we now support a truly insane number of devices. Chances are, if you like a feature, we have it already. Seriously. But here is one for now:
Here are just a few of our features:

Not-Working :

> buggy stock browser
x-x-x-x-x-x-xx-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x-x

Quote:

I have included modified boot.img in the rom , so without 2 SD-EXT it wont boot .

Partition Order

SD-SYSTEM - -> SD-DATA

no need of memory increasing scripts :P

Instruction

Download the ROM & Gapps

Wipe 2 SD-Partitions using minitool partition wizard or disk utility

Reboot to Recovery

Do a factory reset

Flash the ROM & Gapps

Reboot

Screenshots

Download

ROM : Here

Gapps : Here

-----------------------------------------------------------------------------------------------------------------------------

KIT-KAT [PAC-Man ROM Version 4.4.2 Alpha 2] for HTC exlporer/pico

2014-03-14T13:26:00.000+05:30

[KIT-KAT][4.4.2] PAC-Man ROM Version 4.4.2 Alpha 2 [ 22-12-13 ]

PAC-man ROM is a combination of the three Super ROMs Available

Paranoid Android + AOKP + Cyanogenmod = PAC - man

This ROM packs all the tweaks from the three super ROMs into one.

Why choose among ROMs, When you have All-in-One !!

----------------------------------------------------------------------------------------------------------------------------

I have included modified boot.img in the rom , so without 2 SD-EXT it wont boot .

Partition Order

SD-SYSTEM - -> SD-DATA

no need of memory increasing scripts :P

Code:

Buggy stock browser --- > use 3rd party apps

Download the ROM & Gapps

Wipe 2 SD-Partitions using minitool partition wizard or disk utility

Reboot to Recovery

Do a factory reset

Flash the ROM & Gapps

Reboot

And enjoy the latest version of PAC

MOD EDIT: Link Removed

Gapps : Here

You have already single SD-Ext partition. How to make 2 SD-Ext Partition?You can't find the solution. you are having class 4 , 8GB SD Card.

refer this : http://forum.xda-developers.com/show...t=partitioning

KitKat [AORP - 4.4.20]

2014-03-14T13:15:00.000+05:30

[KitKat] [Rom] [BETA #1][AORP - 4.4.20] [22-12 -13]

AORP- Android Open Rebel Project is an aftermarket firmware based on the CyanogenMod with add functionalities . We are dedicated to fast, stable, and feature-filled roms, honesty and communication with our users, and openness with our code. We like frequent builds, with the very latest and greatest hardware support and fixes. We strive to not only provide you with the best rom we can build, but also to give back to the Android community and our fellow developers. For us, this is about creating something we can be proud of and hope you will enjoy.

Screenshot

---------------------------------------------------------------------------------------------------------------------------
Working

Same as cm11 beta 2

Buggs

Stock browser --> use 3rd party apps

To boot this rom you need 2 sd-ext partitions ( im lazy to setup memory scripts or apps )

the partition order should be

SD-SYSTEM ----> SD-Data

Instruction

Download the ROM & Gapps
Wipe 2 SD-Partitions using minitool partition wizard or disk utility
Reboot to Recovery
Do a factory reset
Flash the ROM & Gapps
Reboot

Rom : here

Gapps : Here----------------------------------------------------------------------------------------------------------------------------
totally u should have 3 partitions
1 ) normal
2 ) sd-system ---> ext4 ---> min 512 mb
3 ) sd-data ----> ext4 ---> 1 GB ( it will be your internal memory )

just like this

2014-03-14T13:01:00.002+05:30

HTC Explorer



Manufacturer	HTC Corporation


Operating system	Android 2.3.5 (Gingerbread) with HTC Sense 3.5
CPU	Qualcomm MSM7225A Snapdragon 600 MHz processor Adreno 200 GPU
Memory	512 MB RAM (418 MB usable), 150 MB ROM (90 MB usable)
Removable storage	Supports up to 32 GB microSD
Battery	Li-Ion 1230 mAh
Data inputs	Multi-touch with HTC Sense interface
Display	3.2 in (8.1 cm) TFT LCD 320 × 480 capacitive touchscreen
Rear camera	3.15-Megapixel fixed-focus with geo-tagging and face detection
Connectivity	Bluetooth v3.0, microUSB v2.0

The HTC Explorer, code-named Pico, is a smartphone developed by the HTC Corporation announced in September 2011 and released a month later.Because of the low end processor, the HTC Watch movie rental service and the 3D scrolling effects on the homescreens are not available. The handset comes in four varieties of color options.^[2] Visually similar to the HTC Wildfire S, it comes with a 3.2-inch screen, a 600 MHz ARMv7 Qualcomm Snapdragon processor and runs Android version 2.3 (Gingerbread), bundled with the proprietary HTC Sense 3.5 user interface.

Features

Software

An unlocked bootloader of HTC Explorer

HTC Explorer is considered a low-end smartphone, due to its comparatively low specifications. It offers Android 2.3 Gingerbread, with proprietary HTC Sense 3.5 custom graphical user interface by the manufacturer. The Explorer has an unlockable bootloader, allowing users from the outset to further develop the OS and "root" the device, or gain legitimate privileged control in Android's subsystem. Software-development community XDA-Developers was among the first to release a custom ROM and kernel for the phone, and since then the phone can unofficially be upgraded to newer versions of the Android OS family and other aftermarket versions.HTC Explorer being a Low-end phone has achieved Stable Build of CM10.2 a.k.a Android 4.3.x.Even it had a bootable build of FireFox OS.

Hardware

Back of the HTC Explorer

The Explorer has a plastic chassis that is 4.05 in (102.8 mm) long, 2.25 in (57.2 mm) wide, and 0.51 in (12.9 mm) thick, and weighs 3.81 (108 g). The screen is a 3.2-inch TFT capacitive touchscreen, supporting 256K colors and around 180 pixel-per-inch density. The device features a 600 MHz Cortex-A5 single-core central processing unit (CPU) and a single-core Adreno 200 graphics processing unit (GPU), in conjunction with an accelerometer and proximity sensor. Other features include a microphone, GPS, and 3.15-megapixel rear camera. The rear of the Explorer features a patterned plastic surface with a rubbery, leathery texture to help users to grip and hold the device, with an additional plate of brushed metal at the center of the rear cover.^[1]

Availability

This section needs additional citations for verification. Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (June 2013)

[GUIDE]Overclocking NAND Devices with PLL2

2014-03-14T13:01:00.001+05:30

[GUIDE]Overclocking NAND Devices with PLL2

/**** THIS GUIDE IS ONLY FOR ADVANCED USERS, WHO KNOW HOW TO COMPILE AND MAKE MODIFICATIONS TO KERNEL AND MODIFYING VARIOUS PARAMETERS IN RAMDISK ****/

Hello guys, here I am giving you a detailed tutorial for Overclocking devices that comes with NAND and having only PLL2 support.
Although this guide is written for HTC Explorer, the method can also be applied on similar devices.
So, before we begin you should understand the difference between OCing with PLL4 and OCing with PLL2.

XDA user @rootdefyxt320 has written an excellent post that tells the exact difference between PLL4 OC and PLL2 OC. I am quoting it:

Quote:

PLL2 overclock can be compared to FSB overclocking in computers i.e locked multiplier overclocking in the BIOS. FSB overclocking involves overclocking of the PC buses such as the Memory Bus, PCI/ PCI-Express bus and AGP buses (older computers) and the CPU. It works out by XXXXMHz multiplied by X multiplier and that will give the CPU speed. PLL2 overclock does the same thing because PLL2 controls the bus speeds (exists in the SOC). It overclocks the memory buses, SOC clock, internal storage (database IO) speed and of course the CPU. It works out by XX multiplied by 19/2 and that gives the CPU speed. That's why PLL2 on 800MHz is faster in performance than PLL4 on 800MHz . Therefore that's the reason why people complain of burnt NANDs on HTC Explorer and Motorola Defy Mini XT320/321.

PLL4 overclock can be compared to unlocked multiplier overclocking where you adjust the multiplier in the BIOS and it will automatically adjust the clock speed depending on the multiplier of the CPU. Therefore this only overclocks the CPU. PLL4 overclock only overclocks the CPU and NOT the buses so it can go at much higher frequencies than PLL2 overclock. PLL4 overclock does NOT adjust bus speeds so therefore it is much safer to overclock and it doesn't burn out your SOC.

In case of HTC Explorer, it uses Qualcomm MSM7225A chipset. This chipset does not have PLL4 support. So the only way to overclock is by OC'ing PLL2. But OC'ing PLL2 causes not only the CPU but also everything connected to the board to OC as well. This includes the External Bus Interface (EBI). Our NAND is connected to EBI and when OC happens the Write access through NAND becomes so high causing every block in those partitions which are mounted as RW to become Bad. This is what we call "NAND BURN".

The partitions in NAND that are affected by OC are /data and /cache. This is because only these two partitons are mounted with RW access. As I mentioned above the increased Write access during OC is what causing the blocks to corrupt. All other partitions including /misc, /devlog, /boot, /system and /recovery are mounted as Read-Only and therefore are not affected.

The Workaround for this dilemma is to disable both /data and /cache partitions ( By disable, I mean not even mounting them ) in NAND and use a portion of your SDcard to act as /data and /cache. This is what we are going to do.

/* FOLLOWING PROCEDURE IS FOR AOSP ROMS ONLY */

THE PROCEDURE
================

The procedure consists of four parts. They are listed below:

Preparing The SDcard
Kernel Level Changes
Setting Up RamDisk
Removing Memory Increasing Script

Detailed description of each part is given below:

PART 1 : Preparing The SDcard
==========================

********YOU MUST USE CLASS 10 OR ATLEAST CLASS 6 SDCARD WITH MINIMUM 8GB CAPACITY*******

CLASS 4 and CLASS 2 SDcards will definitely cause slow responsiveness because /data/data is on SDcard. Furthermore these SDcards can't handle OC at high frequencies and will die out quickly.

SO PROCEED ONLY IF YOU ARE HAVING CLASS 6 OR CLASS 10 SDCARD. YOU CAN TRY CLASS 4 SDCARD BUT YOU CAN'T OVERCLOCK ABOVE A CERTAIN LIMIT AND NO GUARANTEE ABOUT HOW LONG THE CARD WILL LAST.

We are going to create two EXT4 partitions ( First one for replacing /data and second one for replacing /cache in NAND ) on the SDcard, in addition to the normal FAT32 partition.

Using MiniTool Partition Wizard, create two EXT4 partitions as shown in following figure:

For SD-DATA, you can give whatever size you want. This where the user applications are installed.
For SD-CACHE, around 65MB is enough.

You should keep the order in which partitions are created. Partition Type for both SD-DATA and SD-CACHE should be Primary.

Assuming you have successfully prepared SDcard, lets go the second part:

PART 2 : Kernel Level Changes
==========================

First, you need to replace arch/arm/mach-msm/acpuclock-7201 with this one: https://dl.dropboxusercontent.com/u/...puclock-7201.c
This contains the overclocked frequencies and logic to dynamically calculate PLL2 values according to different frequencies.

When you look through the overclocked frequencies, you can see I have disabled 900MHz. This is because Class 4 SDcards can't handle data rate at this frequency. Those who have Class 10 SDcards can enable and try whether it is stable for them.

**** DO NOT OC GPU. ITS FAKE AND ACTUALLY DEGRADES PERFORMANCE. REVERT GPU OC IF YOU HAVE ENABLED IT ****

Next, you need to edit the configuration file ( pico_defconfig in my case ) and enable the following option. Its disabled by default so you have to enable it:

Code:

CONFIG_LBDAF=y

That's all. Now compile your kernel.

PART 3 : Setting Up RamDisk
========================

Since, we are not using /data and /cache in NAND anymore, the changes must be made in RamDisk.
All modifications are performed on init.rc file.

Open init.rc and perform the following modifications:

1. Find the following line:

Code:

mount yaffs2 mtd@userdata /data nosuid nodev

Replace the above line with following:

Code:

# Mount SD-DATA
    wait /dev/block/mmcblk0p2
    wait /dev/block/mmcblk0p2
    wait /dev/block/mmcblk0p2
    wait /dev/block/mmcblk0p2
    mount ext4 /dev/block/mmcblk0p2 /data nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue

2. Now find the following line:

Code:

mount yaffs2 mtd@cache /cache nosuid nodev

Replace the above line with following:

Code:

# Mount SD-CACHE
    wait /dev/block/mmcblk0p3
    wait /dev/block/mmcblk0p3
    wait /dev/block/mmcblk0p3
    wait /dev/block/mmcblk0p3
    mount ext4 /dev/block/mmcblk0p3 /cache nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue

3. Since we are extensively using SDcard, we should adjust the read_ahead_kb parameter for maximum performance:
Add the following lines after the line: mount ext4 /dev/block/mmcblk0p3 /cache nosuid nodev noatime nodiratime barrier=0 data=ordered commit=15 noauto_da_alloc nouser_xattr errors=continue

Code:

# SDcard read speed boost
    write /sys/block/mmcblk0/bdi/read_ahead_kb 2048

PART 4 : Removing Memory Increasing Script
=====================================

*** This is very important. You should remove any memory increasing script that you were using. Because /data partition is now on SDcard, using memory increasing script will cause conflict and makes ROM unbootable. ***

That's all, now you can flash your favourite ROM with the new OCed boot image and enjoy overclocking.

NOTE: A new Recovery must be made to support the new /SD-CACHE partition.

SCR Screen Recorder Pro root v0.11.2-beta Apk

2014-03-14T13:01:00.000+05:30

SCR Screen Recorder Pro ★ root

Description

** Root only **
Record great quality screencasts directly from your phone or tablet!
SCR Screen Recorder uses hardware accelerated video encoding to achieve best quality screen recording on any device. It’s the only video recorder on the market supporting Tegra device including Nexus 7.
If you got stuck with touch indicators (white circles) use “Show Touch Indicators” app to turn it off.
This is an early BETA preview version so it may not work on all devices and ROMs.

What's New

If previous version of SCR didn’t work for you give it another try!
Simply go to SCR settings and select “Software MPEG-4″ video encoder. The new software encoder, although a bit slower then hardware one, is totally independent of device drivers and should work on virtually all ICS+ devices. If your recording isn’t smooth try reducing resolution and video bitrate or mute audio.
Version 0.11.2-beta
- Initial KitKat support. Expect more performance and stability improvements in next updates.

Screenshots

Download Apk from

Server1

Server2

CyanogenMod 11 Kitkat 4.4 for HTC Explorer/pico

2013-12-08T19:47:00.003+05:30

[DEV][ROM][4.4][KRT16S] CyanogenMod 11 | BETA 1 | 28/11/2013

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4 (KITKAT), which is designed to increase performance and reliability over stock Android for your device.

Code:

#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/

Unofficial build of CyanogenMod 11 (Android 4.4) for the HTC Explorer (Pico)

What's working:

GSM
Receiving and making calls
Display
Camera (photos, camcorder & panorama)
Audio playback
Audio recording
Video playback
Screenshot
WiFi
WiFi tethering
Bluetooth
Bluetooth tethering
SDcard
GPS

Not working:

Glitches in stock browser
USB tethering

It's entirely possible that features not used by me are broken, but overall the device should be usable. You have been warned.

Before using ART, you have to install some reverse-mount script like INT2EXT!

Download:

BETA 1!

BETA 1

- Fixed Camera
- Fixed Video Recording
- Fixed Native screenshot [untested, no screenshot option in CM yet]
- Fixed Recent Apps menu preview
- Fixed battery icon alignment
- Fixed genlock errors
- Partially fixed stock browser [have glitches, but not full black like before]
- Enabled low RAM optimizations introduced in 4.4 (will not turn your phone into a space shuttle, read more here)

Download

Gapps : http://www.androidfilehost.com/?fid=23252070760973598

Install instructions:

Wipe data and cache
Flash the CM11 zip
Reboot
boot into recovery mode
Install gapps
Reboot

Upgrading from earlier version of CyanogenMod 11:

Boot into Recovery
Flash CM11 zip
Reboot

Source:
https://github.com/PicoKat
https://github.com/CyanogenMod

Thanks to:

PecanCM/TeamHackLG
LegaCyMod

XDA:DevDB Information
CyanogenMod 11, a ROM for the HTC Pico (Explorer)

Contributors
galaxyfreak
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod

Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2013-12-28

Created 2013-11-20
Last Updated 2013-12-07

Changelog

BETA 1 28-11-2013

Fixed Camera
Fixed Video Recording
Fixed Native screenshot
Fixed Recent Apps menu preview
Fixed battery icon alignment
Fixed genlock errors
Partially fixed stock browser [have glitches, but not full black like before]
Enabled low RAM optimizations introduced in 4.4

ALPHA 1 24-11-2013

Updated CM sources (KRT16S)
Fixed WiFi
Fixed SDcard
Fixed Video Decoding

PREVIEW BUILD 20-11-2013

Initial release

-----------------------------------------------------------------

Android KitKat

Key Developer Features

Welcome to Android 4.4 KitKat!
Android KitKat brings all of Android's most innovative, most beautiful, and most useful features to more devices everywhere.
This document provides a glimpse of what's new for developers.
Find out more about KitKat for consumers at www.android.com.

Making Android for everyone

Android 4.4 is designed to run fast, smooth, and responsively on a much broader range of devices than ever before — including on millions of entry-level devices around the world that have as little as 512MB RAM.
KitKat streamlines every major component to reduce memory use and introduces new APIs and tools to help you create innovative, responsive, memory-efficient applications.
OEMs building the next generation of Android devices can take advantage of targeted recommendations and options to run Android 4.4 efficiently, even on low-memory devices. Dalvik JIT code cache tuning, kernel samepage merging (KSM), swap to zRAM, and other optimizations help manage memory. New configuration options let OEMs tune out-of-memory levels for processes, set graphics cache sizes, control memory reclaim, and more.
In Android itself, changes across the system improve memory management and reduce memory footprint. Core system processes are trimmed to use less heap, and they now more aggressively protect system memory from apps consuming large amounts of RAM. When multiple services start at once — such as when network connectivity changes — Android now launches the services serially, in small groups, to avoid peak memory demands.
For developers, Android 4.4 helps you deliver apps that are efficient and responsive on all devices. A new API, ActivityManager.isLowRamDevice(), lets you tune your app's behavior to match the device's memory configuration. You can modify or disable large-memory features as needed, depending on the use-cases you want to support on entry-level devices. Learn more about optimizing your apps for low-memory devices here.
New tools give also give you powerful insight into your app's memory use. The procstats tool details memory use over time, with run times and memory footprint for foreground apps and background services. An on-device view is also available as a new developer option. The meminfo tool is enhanced to make it easier to spot memory trends and issues, and it reveals additional memory overhead that hasn't previously been visible.

New NFC capabilities through Host Card Emulation

Android 4.4 introduces new platform support for secure NFC-based transactions through Host Card Emulation (HCE), for payments, loyalty programs, card access, transit passes, and other custom services. With HCE, any app on an Android device can emulate an NFC smart card, letting users tap to initiate transactions with an app of their choice — no provisioned secure element (SE) in the device is needed. Apps can also use a new Reader Mode to act as readers for HCE cards and other NFC-based transactions.

Android HCE emulates ISO/IEC 7816 based smart cards that use the contactless ISO/IEC 14443-4 (ISO-DEP) protocol for transmission. These cards are used by many systems today, including the existing EMVCO NFC payment infrastructure. Android uses Application Identifiers (AIDs) as defined in ISO/IEC 7816-4 as the basis for routing transactions to the correct Android applications.
Apps declare the AIDs they support in their manifest files, along with a category identifier that indicates the type of support available (for example, "payments"). In cases where multiple apps support the same AID in the same category, Android displays a dialog that lets the user choose which app to use.
When the user taps to pay at a point-of-sale terminal, the system extracts the preferred AID and routes the transaction to the correct application. The app reads the transaction data and can use any local or network-based services to verify and then complete the transaction.
Android HCE requires an NFC controller to be present in the device. Support for HCE is already widely available on most NFC controllers, which offer dynamic support for both HCE and SE transactions. Android 4.4 devices that support NFC will include Tap & Pay for easy payments using HCE.

Printing framework

Android apps can now print any type of content over Wi-Fi or cloud-hosted services such as Google Cloud Print. In print-enabled apps, users can discover available printers, change paper sizes, choose specific pages to print, and print almost any kind of document, image, or file.
Android 4.4 introduces native platform support for printing, along with APIs for managing printing and adding new types of printer support. The platform provides a print manager that mediates between apps requesting printing and installed print services that handle print requests. The print manager provides shared services and a system UI for printing, giving users consistent control over printing from any app. The print manager also ensures the security of content as it's passed across processes, from an app to a print service.

You can add printing support to your apps or develop print services to support specific types of printers.

Printer manufacturers can use new APIs to develop their own print services — pluggable components that add vendor-specific logic and services for communicating with specific types of printers. They can build print services and distribute them through Google Play, making it easy for users to find and install them on their devices. Just as with other apps, you can update print services over-the-air at any time.
Client apps can use new APIs to add printing capabilities to their apps with minimal code changes. In most cases, you would add a print action to your Action Bar and a UI for choosing items to print. You would also implement APIs to create print jobs, query the print manager for status, and cancel jobs. This lets you print nearly any type of content, from local images and documents to network data or a view rendered to a canvas.
For broadest compatibility, Android uses PDF as its primary file format for printing. Before printing, your app needs to generate a properly paginated PDF version of your content. For convenience, the printing API provides native and WebView helper classes to let you create PDFs using standard Android drawing APIs. If your app knows how to draw the content, it can quickly create a PDF for printing.
Most devices running Android 4.4 will include Google Cloud Print pre-installed as a print service, as well as several Google apps that support printing, including Chrome, Drive, Gallery, and QuickOffice.

Storage access framework

A new storage access framework makes it simple for users to browse and open documents, images, and other files across all of their their preferred document storage providers. A standard, easy-to-use UI lets users browse files and access recents in a consistent way across apps and providers.

Box and others have integrated their services into the storage access framework, giving users easy access to their documents from apps across the system.

Cloud or local storage services can participate in this ecosystem by implementing a new document provider class that encapsulates their services. The provider class includes all of the APIs needed to register the provider with the system and manage browsing, reading, and writing documents in the provider. The document provider can give users access to any remote or local data that can be represented as files — from text, photos, and wallpapers to video, audio, and more.
If you build a document provider for a cloud or local service, you can deliver it to users as part of your existing Android app. After downloading and installing the app, users will have instant access to your service from any app that participates in the framework. This can help you gain exposure and user engagement, since users will find your services more easily.
If you develop a client app that manages files or documents, you can integrate with the storage access framework just by using new CREATE_DOCUMENT or OPEN_DOCUMENT intents to open or create files — the system automatically displays the standard UI for browsing documents, including all available document providers.
You can integrate your client app one time, for all providers, without any vendor-specific code. As users add or remove providers, they’ll continue to have access to their preferred services from your app, without changes or updates needed in your code.
The storage access framework is integrated with the existing GET_CONTENT intent, so users also have access to all of their previous content and data sources from the new system UI for browsing. Apps can continue using GET_CONTENT as a way to let users import data. The storage access framework and system UI for browsing make it easier for users to find and import their data from a wider range of sources.
Most devices running Android 4.4 will include Google Drive and local storage pre-integrated as document providers, and Google apps that work with files also use the new framework.

Low-power sensors

Sensor batching

Android 4.4 introduces platform support for hardware sensor batching, a new optimization that can dramatically reduce power consumed by ongoing sensor activities.
With sensor batching, Android works with the device hardware to collect and deliver sensor events efficiently in batches, rather than individually as they are detected. This lets the device's application processor remain in a low-power idle state until batches are delivered. You can request batched events from any sensor using a standard event listener, and you can control the interval at which you receive batches. You can also request immediate delivery of events between batch cycles.
Sensor batching is ideal for low-power, long-running use-cases such as fitness, location tracking, monitoring, and more. It can makes your app more efficient and it lets you track sensor events continuously — even while the screen is off and the system is asleep.
Sensor batching is currently available on Nexus 5, and we're working with our chipset partners to bring it to more devices as soon as possible.

Moves and Runtastic Pedometer are using the hardware step-detector to offer long-running, low-power services.

Step Detector and Step Counter

Android 4.4 also adds platform support for two new composite sensors — step detector and step counter — that let your app track steps when the user is walking, running, or climbing stairs. These new sensors are implemented in hardware for low power consumption.
The step detector analyzes accelerometer input to recognize when the user has taken a step, then triggers an event with each step. The step counter tracks the total number of steps since the last device reboot and triggers an event with each change in the step count. Because the logic and sensor management is built into the platform and underlying hardware, you don't need to maintain your own detection algorithms in your app.
Step detector and counter sensors are available on Nexus 5, and we're working with our chipset partners to bring them to new devices as soon as possible.

SMS provider

If you develop a messaging app that uses SMS or MMS, you can now use a shared SMS provider and new APIs to manage your app's message storage and retrieval. The new SMS provider and APIs define a standardized interaction model for all apps that handle SMS or MMS messages.
Along with the new provider and APIs, Android 4.4 introduces new semantics for receiving messages and writing to the provider. When a message is received, the system routes it directly to the user's default messaging app using the new SMS_DELIVER intent. Other apps can still listen for incoming messages using the SMS_RECEIVED intent. Also, the system now allows only the default app to write message data to the provider, although other apps can read at any time. Apps that are not the user's default can still send messages — the system handles writing those messages to the provider on behalf of the app, so that users can see them in the default app.
The new provider and semantics help to improve the user's experience when multiple messaging apps are installed, and they help you to build new messaging features with fully-supported, forward-compatible APIs.

New ways to build beautiful apps

A new immersive mode lets apps use every pixel on the screen to show content and capture touch events.

Full-screen Immersive mode

Now your apps can use every pixel on the device screen to showcase your content and capture touch events. Android 4.4 adds a new full-screen immersive mode that lets you create full-bleed UIs reaching from edge to edge on phones and tablets, hiding all system UI such as the status bar and navigation bar. It's ideal for rich visual content such as photos, videos, maps, books, and games.
In the new mode, the system UI stays hidden, even while users are interacting with your app or game — you can capture touch events from anywhere across the screen, even areas that would otherwise be occupied by the system bars. This gives you a great way to create a larger, richer, more immersive UI in your app or game and also reduce visual distraction.
To make sure that users always have easy, consistent access to system UI from full-screen immersive mode, Android 4.4 supports a new gesture — in immersive mode, an edge swipe from the top or bottom of the screen now reveals the system UI.
To return to immersive mode, users can touch the screen outside of the bar bounds or wait for a short period for the bars to auto-hide. For a consistent user experience, the new gesture also works with previous methods of hiding the status bar.

Transitions framework for animating scenes

Most apps structure their flows around several key UI states that expose different actions. Many apps also use animation to help users understand their progress through those states and the actions available in each. To make it easier to create high-quality animations in your app, Android 4.4 introduces a new transitions framework.
The transitions framework lets you define scenes, typically view hierarchies, and transitions, which describe how to animate or transform the scenes when the user enters or exits them. You can use several predefined transition types to animate your scenes based on specific properties, such as layout bounds, or visibility. There's also an auto-transition type that automatically fades, moves, and resizes views during a scene change. In addition, you can define custom transitions that animate the properties that matter most to your app, and you can plug in your own animation styles if needed.
With the transitions framework you can also animate changes to your UI on the fly, without needing to define scenes. For example, you can make a series of changes to a view hierarchy and then have the TransitionManager automatically run a delayed transition on those changes.
Once you've set up transitions, it's straightforward to invoke them from your app. For example, you can call a single method to begin a transition, make various changes in your view hierarchy, and on the next frame animations will automatically begin that animate the changes you specified.

Apps can use new window styles to request translucent system bars.

For custom control over the transitions that run between specific scenes in your application flow, you can use the TransitionManager. The TransitionManager lets you define the relationship between scenes and the transitions that run for specific scene changes.

Translucent system UI styling

To get the most impact out of your content, you can now use new window styles and themes to request translucent system UI, including both the status bar and navigation bar. To ensure the legibility of navigation bar buttons or status bar information, subtle gradients is shown behind the system bars. A typical use-case would be an app that needs to show through to a wallpaper.

Enhanced notification access

Notification listener services can now see more information about incoming notifications that were constructed using the notification builder APIs. Listener services can access a notification's actions as well as new extras fields — text, icon, picture, progress, chronometer, and many others — to extract cleaner information about the notification and present the information in a different way.

Chromium WebView

Android 4.4 includes a completely new implementation of WebView that's based on Chromium. The new Chromium WebView gives you the latest in standards support, performance, and compatibility to build and display your web-based content.
Chromium WebView provides broad support for HTML5, CSS3, and JavaScript. It supports most of the HTML5 features available in Chrome for Android 30. It also brings an updated version of the JavaScript Engine (V8) that delivers dramatically improved JavaScript performance.
In addition, the new Chromium WebView supports remote debugging using Chrome DevTools. For example, you can use Chrome DevTools on your development machine to inspect, debug, and analyze your WebView content live on a mobile device.
The new Chromium WebView is included on all compatible devices running Android 4.4 and higher. You can take advantage of the new WebView right away, and with minimum modifications to existing apps and content. In most cases, your content will migrate to the new implementation seamlessly.

New media capabilities

Screen recording

Now it's easy to create high-quality video of your app, directly from your Android device. Android 4.4 adds support for screen recording and provides a screen recording utility that lets you start and stop recording on a device that's connected to your Android SDK environment over USB. It's a great new way to create walkthroughs and tutorials for your app, testing materials, marketing videos, and more.
With the screen recording utility, you can capture video of your device screen contents and store the video as an MP4 file on the device. You can record at any device-supported resolution and bitrate you want, and the output retains the aspect ratio of the display. By default, the utility selects a resolution equal or close to the device's display resolution in the current orientation. When you are done recording, you can share the video directly from your device or pull the MP4 file to your host computer for post-production.
If your app plays video or other protected content that you don’t want to be captured by the screen recorder, you can use SurfaceView.setSecure() to mark the content as secure.
You can access screen recording through the adb tool included in the Android SDK, using the command adb shell screenrecord. You can also launch it through the DDMS panel in Android Studio.

Resolution switching through adaptive playback

Android 4.4 brings formal support for adaptive playback into the Android media framework. Adaptive playback is an optional feature of video decoders for MPEG-DASH and other formats that enables seamless change in resolution during playback. The client can start to feed the decoder input video frames of a new resolution and the resolution of the output buffers change automatically, and without a significant gap.
Resolution switching in Android 4.4 lets media apps offer a significantly better streaming video experience. Apps can check for adaptive playback support at runtime using existing APIs and implement resolution-switching using new APIs introduced in Android 4.4.

Common Encryption for DASH

Android now supports the Common Encryption (CENC) for MPEG-DASH, providing a standard, multiplatform DRM scheme for managing protecting content. Apps can take advantage of CENC through Android's modular DRM framework and platform APIs for supporting DASH.

HTTP Live Streaming

Android 4.4 updates the platform's HTTP Live Streaming (HLS) support to a superset of version 7 of the HLS specification (version 4 of the protocol). See the IETF draft for details.

Audio Tunneling to DSP

For high-performance, lower-power audio playback, Android 4.4 adds platform support for audio tunneling to a digital signal processor (DSP) in the device chipset. With tunneling, audio decoding and output effects are off-loaded to the DSP, waking the application processor less often and using less battery.
Audio tunneling can dramatically improve battery life for use-cases such as listening to music over a headset with the screen off. For example, with audio tunneling, Nexus 5 offers a total off-network audio playback time of up to 60 hours, an increase of over 50% over non-tunneled audio.
Media applications can take advantage of audio tunneling on supported devices without needing to modify code. The system applies tunneling to optimize audio playback whenever it's available on the device.

Visualization of how the LoudnessEnhancer effect can make speech content more audible.

Audio tunneling requires support in the device hardware. Currently audio tunneling is available on Nexus 5 and we're working with our chipset partners to make it available on more devices as soon as possible.

Audio monitoring

Apps can use new monitoring tools in the Visualizer effect to get updates on the peak and RMS levels of any currently playing audio on the device. For example, you could use this creatively in music visualizers or to implement playback metering in a media player.

Loudness enhancer

Media playback applications can increase the loudness of spoken content by using the new LoudnessEnhancer effect, which acts as compressor with time constants that are specifically tuned for speech.

Audio timestamps for improved AV sync

The audio framework can now report presentation timestamps from the audio output HAL to applications, for better audio-video synchronization. Audio timestamps let your app determine when a specific audio frame will be (or was) presented off-device to the user; you can use the timestamp information to more accurately synchronize audio with video frames.

Wi-Fi CERTIFIED Miracast™

Android 4.4 devices can now be certified to the Wi-Fi Alliance Wi-Fi Display Specification as Miracast compatible. To help with testing, a new Wireless Display developer option exposes advanced configuration controls and settings for Wireless Display certification. You can access the option at Settings > Developer options > Wireless display certification. Nexus 5 is a Miracast certified wireless display device.

RenderScript Compute

Performance benchmarks for Android 4.4 relative to Android 4.3, run on the same devices (Nexus 7, Nexus 10).

Ongoing performance improvements

When your apps use RenderScript, they'll benefit from ongoing performance tuning in the RenderScript runtime itself, without the need for recompilation. The chart at right shows performance gains in Android 4.4 on two popular chipsets.

GPU acceleration

Any app using RenderScript on a supported device benefits from GPU acceleration, without code changes or recompiling. Since the Nexus 10 first debuted RenderScript GPU acceleration, various other hardware partners have added support.
Now with Android 4.4, GPU acceleration is available on the Nexus 5, as well as the Nexus 4, Nexus 7 (2013), and Nexus 10, and we're working with our partners to bring it to more devices as soon as possible.

RenderScript in the Android NDK

Now you can take advantage of RenderScript directly from your native code. A new C++ API in the Android Native Development Kit (NDK) lets you access the same RenderScript functionality available through the framework APIs, including script intrinsics, custom kernels, and more.
If you have large, performance-intensive tasks to handle in native code, you can perform those tasks using RenderScript and integrate them with your native code. RenderScript offers great performance across a wide range of devices, with automatic support for multi-core CPUs, GPUs, and other processors.
When you build an app that uses the RenderScript through the NDK, you can distribute it to any device running Android 2.2 or or higher, just like with the RenderScript support library available for framework APIs.

Graphics

GLES2.0 SurfaceFlinger

Android 4.4 upgrades its SurfaceFlinger from OpenGL ES 1.0 to OpenGL ES 2.0.

New Hardware Composer support for virtual displays

The latest version of Android Hardware Composer, HWComposer 1.3, supports hardware composition of one virtual display in addition to the primary, external (e.g. HDMI) display, and has improved OpenGL ES interoperability.

New Types of Connectivity

New Bluetooth profiles

Android 4.4 support for two new Bluetooth profiles to let apps support a broader range of low-power and media interactions. Bluetooth HID over GATT (HOGP) gives apps a low-latency link with low-power peripheral devices such as mice, joysticks, and keyboards. Bluetooth MAP lets your apps exchange messages with a nearby device, for example an automotive terminal for handsfree use or another mobile device. As an extension to Bluetooth AVRCP 1.3, users can now set absolute volume on the system from their Bluetooth devices.
Platform support for HOGP, MAP, and AVRCP is built on the Bluedroid Bluetooth stack introduced by Google and Broadcom in Android 4.2. Support is available right away on Nexus devices and other Android-compatible devices that offer compatible Bluetooth capabilities.

IR Blasters

Android 4.4 introduces platform support for built-in IR blasters, along with a new API and system service that let you create apps to take advantage them.
Using the new API, you can build apps that let users remotely control nearby TVs, tuners, switches, and other electronic devices. The API lets your app check whether the phone or tablet has an infrared emitter, query it's carrier frequencies, and then send infrared signals.
Because the API is standard across Android devices running Android 4.4 or higher, your app can support the broadest possible range of vendors without writing custom integration code.

Wi-Fi TDLS support

Android 4.4 introduces a seamless way to stream media and other data faster between devices already on the same Wi-Fi network by supporting Wi-Fi Tunneled Direct Link Setup (TDLS).

Accessibility

System-wide settings for closed captioning

Android 4.4 now supports a better accessibility experience across apps by adding system-wide preferences for Closed Captioning. Users can go to Settings > Accessibility > Captions to set global captioning preferences, such as whether to show captions and what language, text size, and text style to use.
Apps that use video can now access the user's captioning settings and adjust presentation to meet the user's preferences. A new captioning manager API lets you check and monitor the user's captioning preferences. The captioning manager provides you with the user's preferred captioning state as well as preferred locale, scaling factor, and text style. The text style includes foreground and background colors, edge properties, and typeface.

Apps can now refer to the user's system-wide captions preferences. An example of the expected display style is shown right in the settings.

In addition, apps that use VideoView can use a new API to pass a captioning stream along with a video stream for rendering. The system automatically handles the display of the captions on video frames according to the user's systemwide settings. Currently, VideoView supports auto-display of captions in WebVTT format only.
All apps that show captions should make sure to check the user's systemwide captioning preferences and render captions as closely as possible to those preferences. For more insight into how specific combinations of settings should look, you can look at a preview of captions in different languages, sizes, and styles right in the Settings app.

Enhanced Accessibility APIs

Android 4.4 extends the accessibility APIs to support more precise structural and semantic description and observation of onscreen elements. With the new APIs, developers can improve the quality of accessible feedback by providing accessibility services with more information about on-screen elements.
In accessibility nodes, developers can now determine whether a node is a popup, get its input type, and more. You can also use new APIs to work with nodes that contain grid-like information, such as lists and tables. For example, you can now specify new supported actions, collection information, live region modes, and more.
New accessibility events let developers more closely follow the changes that are taking place in window content, and they can now listen for changes in the touch exploration mode on the device.

Support for international Users

Drawable mirroring for RTL locales

If your app is targeting users who use RTL scripts, you can use a new API to declare that a drawable should be auto-mirrored when the user's locale setting includes an RTL language.
Declaring a drawable as auto-mirrored helps you prevent duplication of assets in your app and reduces the the size of your APK. When you have drawables that are the reusable for both LTR and RTL presentations, you can declare the default versions as auto-mirrored and then omit those Drawables from your RTL resources.

The Force RTL layout option makes it easier to test your app's localization.

You can declare various types of drawables as auto-mirrored in your application code, such as bitmap, nine-patch, layer, state list, and other drawables. You can also declare a drawable as auto-mirrored in your resource files by using a new attribute.

Force RTL Layout

To make it easier to test and debug layout mirroring issues without switching to an RTL language, Android includes a new developer option to force RTL layout direction in all apps.
The Force RTL layout option switches the device to RTL layout for all locales and displays text in your current language. This can help you find layout issues across your app, without having to display the app in an RTL language. You can access the option in Settings > Developer options > Force RTL layout direction.

Security enhancements

SELinux (enforcing mode)

Android 4.4 updates its SELinux configuration from "permissive" to "enforcing." This means potential policy violations within a SELinux domain that has an enforcing policy will be blocked.

Improved cryptographic algorithms

Android has improved its security further by adding support for two more cryptographic algorithms. Elliptic Curve Digital Signature Algorithm (ECDSA) support has been added to the keystore provider improving security of digital signing, applicable to scenarios such as signing of an application or a data connection. The Scrypt key derivation function is implemented to protect the cryptographic keys used for full-disk encryption.

Other enhancements

On multiuser devices, VPNs are now applied per user. This can allow a user to route all network traffic through a VPN without affecting other users on the device. Also, Android now supports FORTIFY_SOURCE level 2, and all code is compiled with those protections. FORTIFY_SOURCE has been enhanced to work with clang.

Tools for analyzing memory use

Procstats

A new tool called procstats helps you analyze the memory resources your app uses, as well as the resources used by other apps and services running on the system.
Procstats keeps track of how apps are running over time, providing data about their execution durations and memory use to help determine how efficiently they are performing. This is most important for apps that start services that run in the background, since it lets you monitor how long they are running and how much RAM they are using while doing so. Procstats will also collect data for foreground applications about memory use over time to determine the overall memory profile of the app.
Procstats can help you identify background services started by your app. You can keep track of how long those services continue running and how much RAM they use while doing so. Procstats also lets you profile your app while it's in the foreground, using its memory use over time to determine its overall memory profile.

The new procstats tool lets you check the memory use of apps and services over time.

The enhanced meminfo tool lets you see details of memory use for an app.

You can access procstats from the adb tool included in the Android SDK, adb shell dumpsys procstats. Also, for on-device profiling, see the Process Stats developer option, below.

On-device memory status and profiling

Android 4.4 includes a new developer option to make it easier to analyze your app's memory profile while it's running on any device or emulator. It's especially useful to get a view of how your app uses memory and performs on devices with low RAM. You can access the option at Settings > Developer options > Process stats

Process stats is a convenient way to check your app's memory use. You can see how your app compares to other apps and zoom in on specific data about your app or it's background services.

The Process Stats option shows you a variety of high-level metrics on your app's memory use, based on data collected using the new procstats service. On the main screen you can see a summary of system memory status. Green indicates relative amount of time spent with low RAM usage, yellow indicates moderate RAM usage, and red indicates high (critical) RAM usage
Below the summary is a list summarizing each app's memory load on the system. For each app, a blue bar indicates the relative computed memory load (runtime x avg_pss) of its process, and a percentage number indicates the relative amount of time spent in the background. You can filter the list to show only foreground, background, or cached processes, and you can include or exclude system processes. You can also change the duration of the data collected to 3, 6, 12, or 24 hours, and you can include or exclude uss memory.
To take a closer look at a specific app's memory usage in isolation, tap the app. For each app, you can now see a summary of the memory consumed and the percentage of the collection interval that the app has been running. You can also see the average and maximum usage over the collection period, and below the app's services and the percentage of time they've been running.
Analyzing your app using the data in Process Stats can reveal issues and suggest possible optimizations for your app. For example, if your app is running longer than it should or using too much memory over a period of time, there could be bugs in your code that you can resolve to improve your app's performance, especially when running on a device with low RAM.

CyanogenMod 10.2 Weekly + HALO2 Build 9 for htc explorer/pico

2013-12-08T19:42:00.002+05:30

As we got CM10.2 to beta-state fast, I decided to run weekly builds of it.

What are Weekly builds?
CM10.2 builds of the latest androidarmv6* source from github, so you always have latest CM features and fixes.
New version will come out every week, most often during the weekends.

This is not a replacement for development thread. Post bugs there!

Quote:

Additional features:
- Sweep2wake
- HALO 2.0
- Gesture unlock
- Off-charging animation
- and of course, performance.

Weekly 9: 12-11-2013

Weekly 8: 29-10-2013
Weekly 7: 19-10-2013
Weekly 6: 06-10-2013
Weekly 5: 28-09-2013
Weekly 4.1: 17-09-2013
Weekly 4: 15-09-2013
Weekly 3: 08-09-2013
Weekly 2: 31-08-2013
Weekly 1: 27-08-2013

GAPPS LINK

Can I use OC?
This gapps are not working for me!
I'm getting Status 7 error!

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Quote:

Originally Posted by galaxyfreak

As we got CM10.2 to beta-state fast, I decided to run weekly builds of it.

What are Weekly builds?
CM10.2 builds of the latest androidarmv6 source from github. New version will come out every week, most often during the weekends, but i will do 1st one today

Weekly 1: 27-08-2013 (includes fixed WiFi tether)

keep up good work ...!!

Android 4.3's Best Features

The latest version of Android may be an incremental update, but it brings some much-needed improvements to Google's mobile platform.

9 Android Apps To Improve Security, Privacy

(click image for larger view)

Google introduced Android 4.3 Jelly Bean this week, a minor update to its smartphone and tablet operating system. Android 4.3 does not present a significant visual overhaul of the OS. Instead, it adds a handful of features that make the whole platform a bit more fully rounded. As usual, Google's Nexus-branded devices will be among the first to receive the new platform software. The Nexus 4 and Galaxy Nexus smartphones, and the Nexus 7 and Nexus 10 tablets are on deck to get the update shortly. At the same time, Google has already made the new operating system available to developers, who can get to work adjusting their apps and content for the improved operating system.
Here are some of the best features of the new platform:
First, Android 4.3 is the fastest version of Android yet. The new system software makes advancements on the Project Butter tools already present in Jelly Bean, such as vsync timing, triple buffering, reduced touch latency, and hardware-accelerated 2D rendering, to make gains in overall performance. The new system software also improves rendering for shapes and text, which are higher quality and accomplished more efficiently within the software. It is also better at threading tasks across multi-core systems for balancing power and processing needs.
[ Chromecast brings multiple screens together. Read more at Google Takes On Apple With Chromecast, Android 4.3. ]
Second, Android 4.3 adds support for Bluetooth Smart, also called Bluetooth 4.0 Low Energy. This is the Bluetooth spec we've all been waiting for. Until now, Bluetooth wasn't part of the core Android stack and it was up to individual device makers to implement it in their own way. This caused problems for application developers. With Bluetooth 4.0 baked into the core of the platform, app developers should see many of their headaches go away. The payoff is that it will be easier to create apps that can talk to low-power sensors that track fitness, medical, proximity, location and other data.
Game developers should be pleased that Android 4.3 adds support for OpenGL ES 3.0. By stuffing these extensions into Android, gamers can create even more realistic and immersive 3D graphics. OpenGL ES 3.0 provides acceleration of advanced visual effects, better compression, advanced texture rendering and more. The most beneficial aspect of OpenGL ES 3.0 support is that developers will be able to create a single texture-compression format that will run across a number of devices.
One of the more interesting features in Android 4.3 is support for restricted profiles. Android 4.2 added support for multiple user profiles on the same device, which lets parents create a profile for themselves and others for their children. Each profile can set its own home screen, favorite apps and so on. Restricted profiles in Android 4.3 takes the idea a step further by giving parents more granular control over what apps and services other profiles can access and use. For example, Google Play Store purchases can be nixed, as can in-app updates. One drawback, however, is that it requires app developers to opt in.
Android 4.3 brings with it new digital rights management tools that will eventually lead to a better selection of content for Android devices. For example, third-party content companies, such as Netflix, won't offer some HD content due to the restrictions of DRM tools within Android 4.2. In Android 4.3, Google has improved the modular DRM framework so that developers can stick DRM into their content more easily. In the long run, it should improve the video and audio content that's available to Android devices.
Finally, Android 4.3 gives developers greater control over notifications. With the tools in 4.3, developers can let their apps access and interact with status bar notifications in any way that they want. According to Google, notifications can be set to skip the notification bar entirely and routed to Bluetooth devices.
While it's true that the bulk of these new features focus more on developers than consumers, both groups will benefit greatly from the added toolset in Android 4.3 Jelly Bean.

Revolution KitKat for htc explorer/pico

2013-12-08T19:40:00.000+05:30

[ROM] | [4.3] | Revolution KitKat [BETA] | [3-11-2013] | [Build-2]

REVOLUTION KITKAT - "Something different"

Hey Folks !
Here I am presenting you, something that many of you might actually didn't thought of.
This is a ROM based on the leaks of the upcoming Android version, KITKAT.

Quote:

NOTE:
1. Please take a note that this is NOT KitKat, it's JB 4.3 and is modded to match the kitKat leaks.
2. Work on this ROM is still in progress.
3. I need contributions of themers or modders so that this ROM grow faster.

What's changed(Till now ):

Status Bar
Dialer
Wallpaper
Play Store
Status Bar[Transparency]
Status Bar icons
Icons ...MANY MORE
Others yet to come ! Stay tuned ![/LIST]

Quote:

What's Working:
EVERYTHING

Quote:

Bugs/Issues :

For few people, 'com.android.phone' stops ! [WorkAround]

Quote:

Features

Sweep2Wake

HALO

All memory script works :cheers:

SCREENSHOTS in Post 2
DOWNLOADS in Post 3

Quote:

For OC Kernel, refer this

Quote:

Video Review

Quote:

CREDITS

@Red Devil
@7alvi
@ALESSIO94x [His thread here]
@galaxyfreak
@sakshamx
@Ashutos1997
@amit.lohar
@legendlee
@joehanh88
PM me if I forgot anyone.

PS - I don't want anyone to say that these are just leaks or you have taken leaks seriously and all that crap stuff. Use the ROM, enjoy, review and rate. I am working hard on the ROM and would be pleased if you hit the 'THANKS' button.

XDA:DevDB Information
Revolution KitKat ROM, a ROM for the HTC Pico (Explorer)

Contributors
#Superuser
ROM OS Version: 4.3.x Jellybean
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Rooted Pico
Based On: CyanogenMod 10.2

Version Information
Status: Beta
Current Beta Version: 2
--------------------------------------------------------------------------------------------------------------

Screenshots

SCREENSHOTS

------------------------------------------------------------------

Downloads

Quote:

DOWNLOADS

Quote:

BUILD2 - http://forum.xda-developers.com/show...0&postcount=70

Quote:

GAPPS [Use only these] - http://d-h.st/d4s

Previous Builds:

Have a great time !

Android 4.3's Best Features

The latest version of Android may be an incremental update, but it brings some much-needed improvements to Google's mobile platform.

9 Android Apps To Improve Security, Privacy

(click image for larger view)

Unofficial_Carbon for htc explorer/pico

2013-12-08T19:34:00.000+05:30

[Unofficial_Carbon] | [4.2.2] | [4.3] | [24/10] | [HALO 2] | [-O3] | UPDATE!

What is Carbon, you ask?

Quote:

JELLY BEAN 4.2.2

What's working:
Everything which isn't in 'Not Working' section

What's not working:

-No Carbon specific bugs anymore
---4.2.2 bugs---
-WiFi hotspot and WiFi direct
-Bluetooth is buggy (force stop bluetooth services in app settings when toggle is stuck)

SCREENSHOTS

JELLY BEAN 4.3

What's working:
Everything which isn't in 'Not Working' section

What's not working:
-No Carbon specific bugs
---4.3 bugs---
-WiFi hotspot and WiFi direct

Screenshots

================================================== ================================================== =================================
================================================== ================================================== =================================

Quote:

NOTES:
-->Many features might not work if you dont flash gapps. For e.g. quick settings, etc
-->For memory scripts, for me int2ext+ works..s2e will work..mounts2sd app will work WITHOUT REVERSE MOUNT. So I want minimum discussion about memory scripts.

CREDITS

Quote:

INT2EXT+
Since many people have been asking how to increase internal memory/how to get int2ext+ working and I'm tired of answering everyone individually, here is a How-to. Just follow it exactly and it will work as it has for me and many other peeps
--download this file
--copy it in your sd-card
--flash the ROM
--install a file manager or use cm file manager with root access
--copy the file you downloaded to system/etc/init.d
--tick all boxes in permissions
--reboot

--------------------------------------------------------------------------------------------------------------
Sources:
]ROM Source: https://github.com/CarbonDev
Vendor tree: https://github.com/7alvi/vendor-htc-pico
Device tree: https://github.com/7alvi/carbon-devi...evice/htc/pico

DOWNLOADS

4.2.2
BUILD #1
BUILD #2
BUILD #3
BUILD #3.1

4.3
Build 1: http://forum.xda-developers.com/show...&postcount=168
Build 2: http://forum.xda-developers.com/show...&postcount=192
Build 3: http://forum.xda-developers.com/show...&postcount=250
Build 4: http://forum.xda-developers.com/show...&postcount=302

Gapps:
New Gapps (keyboard gesture FC fixed)

Check this page for extras (DSP 2.0, modded Play Store, etc) and Carbon wallpapers
-----------------------------------------

Android 4.3's Best Features

The latest version of Android may be an incremental update, but it brings some much-needed improvements to Google's mobile platform.

9 Android Apps To Improve Security, Privacy

(click image for larger view)

CyanogenMod 10.2 | BETA#2 | LEAN MEAN PASTRY MACHINE FOR HTC EXPLORER

2013-12-08T19:31:00.002+05:30

[DEV][ROM][4.3.1]CyanogenMod 10.2 | BETA#2 | LEAN MEAN PASTRY MACHINE | 18/10/13

CyanogenMod 10.2 is a free, community built, aftermarket firmware distribution of Android 4.3.1 (Jellybean), which is designed to increase performance and reliability over stock Android for your device.

Code:

#include 
/*
 * Your warranty is now void.
 *
 * I am not responsible for bricked devices, dead SD cards,
 * thermonuclear war, or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at me for messing up your device, I will laugh at you.
 *
 * Submitting bug reports on nightly builds is the leading 
 * cause of male impotence.
*/

CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.

All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.

Generic source code- http://github.com/cyanogenmod
Device Config- https://github.com/sakindia123/cm10.2_htc_pico
Features- http://www.cyanogenmod.com/about/features

BETA#2: http://forum.xda-developers.com/show...&postcount=297

BETA#1: http://forum.xda-developers.com/show...7&postcount=91

ALPHA#2: http://forum.xda-developers.com/show...1&postcount=76
---------------------------------------------------------------------------------------------------------------

- Working:

WiFi
Display
SDcard
Rotation
RIL
USB mass storage
Audio
Screenshot
Camera
Video Decoding
Video Recording

Not Working

?

GAPPS: http://www.mediafire.com/download/v5...M10.2+PICO.zip

Attached Thumbnails

------------------------------------------------------------------------------------------------------------------------------------

Quote:

Originally Posted by sakindia123

yeah right.I'm not joking.Android 4.3 CM10.2 for our beloved pico.

http://www.mediafire.com/download/wl...ICIAL-pico.zip

Note: SUPER ALPHA.

Super alpha...
Downloading right away.... Thanks dude.. Thanks a lot...

Edit the post with all the bugs and all..
Thanks again bro..

-----------------------------------------------------------------------------------------------------------

Android 4.3's Best Features

The latest version of Android may be an incremental update, but it brings some much-needed improvements to Google's mobile platform.

9 Android Apps To Improve Security, Privacy

(click image for larger view)

MokeeOS for htc explorer

2013-12-08T19:26:00.001+05:30

[MokeeOS] | [JB 4.3.1] | [JLS36I] | [16/10] | [Halo 2] | [S2W] | [Vsync] | [GCC 4.8]

About:
MoKee OpenSource is based on the Google AOSP and CyanogeMod project. We update our source code frequently to keep up with the latest development, and not forgetting to merge in special features of our own at the same time.

The Mfunz Forums launched this project on the 12th of December 2012, and is committed to make this ROM better and better.

Since this project is open source, anyone interested can participate in the development. Newcomers are always welcomed!
Forum: http://bbs.mfunz.com
Guide: http://bbs.mfunz.com/thread-754544-1-1.html
Statistics: http://stats.mfunz.com
Review: http://review.mfunz.com
Github: https://github.com/MoKee
Bug Tracker: http://issues.mfunz.com/

What's working:
Everything which isn't in 'Not Working' section

What's not working:
I found no bug. Everything from WiFi hotspot to settings of Mokee itself are working just fine. But if you find any bug then reports are welcome.

Screenshots:

NOTES:
-->Many features might not work if you dont flash gapps. For e.g. quick settings, etc
-->For memory scripts, mounts2sd app works WITHOUT REVERSE MOUNT just fine. So I want minimum discussion about memory scripts.
--> If you enable pie, status bar will disappear meaning it will go in expanded desktop mode. It's not a bug. It's how it works in Mokee

--------------------------------------------------------------------------------------------------------------

Quote:

Credits:
Nihar.G
Red Devil

---------------------------------------------------------------------------------------------------------------

Sources & Downloads

Sources:
Find my device configs here https://github.com/7alvi
Rom sources: https://github.com/mokee

Downloads:
Build #1: http://www.mediafire.com/download/q4...UNOFFICIAL.zip
Build #2: http://forum.xda-developers.com/show...6&postcount=79

Gapps - USE ONLY THESE ONES:
http://www.mediafire.com/download/a5...s-pico-4.3.zip

------------------------------------------------------------------------------------------------------------

Android 4.3's Best Features

The latest version of Android may be an incremental update, but it brings some much-needed improvements to Google's mobile platform.

9 Android Apps To Improve Security, Privacy

(click image for larger view)

Unofficial_VanirAosp for htc explorer

2013-12-08T19:21:00.001+05:30

[Unofficial_VanirAosp] | [JN 4.3.1] | [JLS361] | [Vsync] | [S2W] | [14/10]

About
Ok guys, So actually there are is no official "Introduction" given anywhere which I would copy and paste like I always do but as the tradition goes, the thread must have an about. So, this ROM is no non-sense after party firmware. It is, what people call "Lean Mean Pastry Machine". Based off AOSP, Vanir is aimed at providing you with the fluid and top-notch performance without compromising on Customization sector. It has all cherries like Pie, HALO, Active Display, Appbar and much more. So, Flash it. and get a taste the Viking Experience.

What's working:
Everything which isn't in "Not working Section" -- Phew!

What's not working:
Didn't find any bugs yet. Bug reports are more than welcome.

Screenshots:

NOTES: No, Seriously, read it:
-->Many features might not work if you dont flash gapps. For e.g. quick settings, etc
-->For increasing internal memory, I've given a kernel (NON-OC) which mounts your other partition (must be in ext2, ext3 or ext4) as /data. So, you just have to replace the boot.img in rom zip and flash the rom. You DO-NOT need three partitions as you needed for oc-kernel. You just need two partitions like you always do if you use a memory increasing script.
Thanx @ShadowTR9 for this trick. It's awesome, simple and I'm using it!

--------------------------------------------------------------------------------------------------------------
Sources:
my device configs: https://github.com/7alvi
Vanir sources: https://github.com/VanirAOSP

Downloads:
Build #1: http://www.androidfilehost.com/?fid=23159073880936294

Gapps:
http://www.mediafire.com/download/a5...s-pico-4.3.zip

Kernel which I mentioned in Notes:
http://www.androidfilehost.com/?fid=23159073880936276

Instructions for kernel:
--Make sure you have two partitions in such order
FAT32 -- Ext(2/3/4) (size of your choice)
--Rename the downloaded databoot.img to boot.img
--Replace the boot.img with the newly renamed boot.img
--Watchu waiting for. Flash the rom! -.-
---------------------------------------------------------------------------------------------------------------

Android 4.3's Best Features

The latest version of Android may be an incremental update, but it brings some much-needed improvements to Google's mobile platform.

9 Android Apps To Improve Security, Privacy

(click image for larger view)

SlimBean for htc explorer

2013-12-08T19:19:00.000+05:30

[SlimBean] | [Unofficial] | [4.1.2] | [4.2 ] | [4.3] | [18/9] | Update!

4.1.2

What's Working:
Everything which isn't in 'Not Working' Section.

What's Not Working:
Navbar settings
4.1.2 bugs

4.2.2

What's Working:
Everything which isn't in 'Not Working' Section.

What's Not Working:
Only 4.2.2 bugs

Screenshots::

4.3
What's Working:
Everything which isn't in 'Not Working' Section.

What's Not Working:
Some people get robotic call issue but most people don't

--------------------------------------------------------------------------------------------------------------

Downlaods:

4.3 Builds:
Beta #4: http://www.androidfilehost.com/?fid=23060877490005014
Stable Build #1: http://forum.xda-developers.com/show...&postcount=159
Gapps: http://www.androidfilehost.com/?fid=23060877489997929

4.2 Builds:

Build 1 (v6)-By ngoralph: http://www.mediafire.com/download/1j...30603-1729.zip

Build 2 (v8.1) :http://www.androidfilehost.com/?fid=23060877490004287

4.1.2 Builds:
Build 1 (v3.1): Slim bean 4.1.2

-------------------------------------------------------------------------------------------------------------

Android 4.3's Best Features

The latest version of Android may be an incremental update, but it brings some much-needed improvements to Google's mobile platform.

9 Android Apps To Improve Security, Privacy

(click image for larger view)

HTC Explorer Pico Development

Awesmoe smartphone with Awesome specs in just 6k!

Beanstalk [Multi Window] for HTC Explorer/pico

P.A.C Man ROM For HTC Explorer/Pico

CyanogenMod 11 for HTC Explorer/Pico

Omni ROM[TeamCody] for HTC Explorer/Pico

Beanstalk ▒ BETA 2 [TeamCody] for HTC Explorer/Pico

ParanoidAndroid (AOSPA-legacy)[TeamCody] for HTC Explorer/Pico

CyanogenMod 11 Weekly Builds [S2W][TeamCody] for HTC Explorer/Pico

CarbonROM[TeamCody] for HTC Explorer/pico

Evervolv 4.0.0 for HTC Explorer/Pico

KITKAT [ PARANOIDANDROID 4.0+] for HTC Explorer/pico

Unofficial Carbon builds for HTC Explorer/Pico

KIT-KAT [PAC-Man ROM Version 4.4.2 Alpha 2] for HTC exlporer/pico

KitKat [AORP - 4.4.20]

HTC Explorer

Contents

Features

Software

Hardware

Availability

[GUIDE]Overclocking NAND Devices with PLL2

SCR Screen Recorder Pro root v0.11.2-beta Apk

CyanogenMod 11 Kitkat 4.4 for HTC Explorer/pico

Android KitKat

Key Developer Features

Making Android for everyone

New NFC capabilities through Host Card Emulation

Printing framework

Storage access framework

Low-power sensors

Sensor batching

Step Detector and Step Counter

SMS provider

New ways to build beautiful apps

Full-screen Immersive mode

Transitions framework for animating scenes

Translucent system UI styling

Enhanced notification access

Chromium WebView

New media capabilities

Screen recording

Resolution switching through adaptive playback

Common Encryption for DASH

HTTP Live Streaming

Audio Tunneling to DSP

Audio monitoring

Loudness enhancer

Audio timestamps for improved AV sync

Wi-Fi CERTIFIED Miracast™

RenderScript Compute

Ongoing performance improvements

GPU acceleration

RenderScript in the Android NDK

Graphics

GLES2.0 SurfaceFlinger

New Hardware Composer support for virtual displays

New Types of Connectivity

New Bluetooth profiles

IR Blasters

Wi-Fi TDLS support

Accessibility

System-wide settings for closed captioning

Enhanced Accessibility APIs

Support for international Users

Drawable mirroring for RTL locales

Force RTL Layout

Security enhancements

SELinux (enforcing mode)

Improved cryptographic algorithms

Other enhancements

Tools for analyzing memory use

Procstats

On-device memory status and profiling

CyanogenMod 10.2 Weekly + HALO2 Build 9 for htc explorer/pico

Revolution KitKat for htc explorer/pico

Unofficial_Carbon for htc explorer/pico

CyanogenMod 10.2 | BETA#2 | LEAN MEAN PASTRY MACHINE FOR HTC EXPLORER

MokeeOS for htc explorer

Unofficial_VanirAosp for htc explorer