I am proud to present you with an UNOFFICIAL Evervolv powered by K3 for the HTC Desire.
I am grateful to Nikez for allowing me to publish this on xda.
WARNING:
THIS IS A REALLY REALLY PRE-ALPHA, STUFF ARE BOUND TO NOT WORK.
FOR ADVANCED USERS ONLY!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Disclaimer:
Please be aware this is an unofficial release compiled from the latest Evervolv codebase (2015-07-18).
If you rely on your device as it is your only phone you should thoroughly consider the risks involved when flashing a custom ROM (e.g. total loss of your data!).
If you decide for flashing this rom, then you do it at your own risk and I am not responsible for any resulting damages!
I don't claim responsibility for the code in this ROM, I have only built the ROM for this device.
My decent changes:
- Kernel 3.0.16 for Kitkat (based on qsd8k-3.0-wip by Nikez)
- Improved Torch (does not turn off when screen shuts down)
- Removed EVUpdater
- Added Jackpal's Terminal Emulator
- A few tweaks for faster scrolling, longer battery life and smoother overall performance
Not working:
- Same as in Evervolv Turba and any other of my KK roms; If you find new issues which are specific to this ROM/Kernel combination, please post your report in this thread together with a logcat
- Camera preview is sometimes distorted (but taking pictures works)
- WiFi tethering / Hotspot WPA/WPA2 not working
- At times, some SD cards cannot get properly mounted
Installation hints:
- Stock hboot or Alphajelly hboot
- SD-EXT partition (512MB or 1GB) required if you plan to use A2SD
- In order to reduce battery consumption switch CPU governor to smartass
Special credits go to:
- EVERVOLV, the original developer of this ROM, as well as htc vendor files and bravo device tree!
- @LaidbackNikez for being a force behind the development of kernel 3.0.16!
- @[email protected] for his awesome work in stabilizing the kernel!
- marc1706 for being a force behind the development of kernel 3.0.16!
- macs18max for providing great tips on kernel developments!
- noonamer for being a force behind the development of kernel 3.0.16!
- walter79 for providing great tips on kernel developments!
- franciscofranco for sharing his magic kernel tweaks!
- everyone else who was involved but does not appear in this list
Have a nice day!
Source:
https://github.com/Evervolv
https://github.com/spezi77/android_kernel_htc_qsd8k_3.0/tree/kitkat-ev
Changelogs
ev_bravo-UNOFFICIAL-4.0.0p2-turba-k3.0.16.
* Initial test release
ev_bravo-unofficial-4.0.0p3-turba
* Kernel Improvements
** added several ARM specific fixes
** used a newer toolchain version (GCC 4.8) for compilation
** added boost pulses for SmartassV2 / introduced SmartassH3 CPU governor (credits H3ROS, M66B and NobodyAtAll)
* GPU: added newer Adreno libs from AU_LINUX_ANDROID_JB_VANILLA_04.02.02.60.051 Build Date: 04/11/13 Thu
* Fixed a problem with SD card mounting at boot
* Added a patch to prevent wakelocks caused by Google Play Services 7.x SystemUpdateService (credits CM)
* Added several tweaks to improve the overall performance of the ROM
* Improved incoming call response time (if screen is turned off the call appears now after ~3 seconds) (credits pixelfreak and walter79)
ev_bravo-unofficial-4.0.0p3-turba-built-for-performance
* Kernel Improvements
** Use per default SMARTASSH3 (allows a better speed/battery-saving ratio)
** Boost enabled per default in smartass governors
** Added conservative governor
** Freed some more ram
** Added a few security fixes from mainline Linux kernel
** Guarded code against potentials deadlocks (ashmem)
** Added improvements taken from Franco's kernel magic
*** I/O boosted - I/O dirty writeback system backported from 3.2
*** Deadline I/O scheduler by default
*** CRC32 library that is used by a lot of internal kernel mechanics completely patched up to the latest version (credits Ezekeel)
*** Merged two stability hotplug patches from mainline Linux kernel
*** Add dynamic writeback feature from 3.1
*** Introduced fsync_control for better performance and i/o throughput (credits cuteprince)
Downloads
ev_bravo-UNOFFICIAL-4.0.0p2-turba-k3.0.16.zip
md5 - df040e5204e7678d132e49de0ef2e318
ev_bravo-unofficial-4.0.0p3-turba.zip
md5 - 5d960975b14ebd4775cf9ef0e34c8fba
ev_bravo-unofficial-4.0.0p3-turba-built-for-performance.zip
md5 - 599d68732a59b8314e18fc754b6984b7
Great cocktail:
kernel 3 + stock hboot + kk turba
ze7zez said:
Great cocktail:
kernel 3 + stock hboot + kk turba
Click to expand...
Click to collapse
I knew that you would like it.
1st of all - let me say thanks. a BIG thank you !
without dev like your self the desire is just another paper brick.
Can you please run a benchmark to give us a hint of the overall responsiveness with K3 Vs K2 ?
I know the K3 is a major upgrade in term of a linux user/dev - but after all the good work that Evervolv et-al put into it - how much the upgrade, qualitatively speaking, worth ?
tested
SD Card doesn't mount (i don't know why?)
some times it fails to boot and i had to eject the battery then try it
thanks for your work!
Rminsh said:
tested
SD Card doesn't mount (i don't know why?)
some times it fails to boot and i had to eject the battery then try it
thanks for your work!
Click to expand...
Click to collapse
Thanks for your reply. I didn't have one of the problems you reported.
Could you share more details about your phone.
- hboot
- sd-ext partition
- recovery
Maybe could you also share a logcat when the phone failed to boot?
Cheers!
P.S.: after leaving my Desire on standby through one night (CPU gov: SmartassV2; 3G on; Wifi off), batt still had 28%.
P.P.S.: I have right now installed slim-gapps from Dec 2014: Slim Gapps 2014-12-02 - md5 26306ee3fb6b57a88c05286a1fef4ff9
P.P.P.S.: I have set zRAM to 30%; reduced animation/transition scales to 0.5%. Everything works really smooth in this rom.
gps3dx said:
Can you please run a benchmark to give us a hint of the overall responsiveness with K3 Vs K2 ?
Click to expand...
Click to collapse
What is the tool that you would recommend for doing a benchmark?
Wow, i'll try as soon as posible! Thanks! :good:
Just a question, why "4.0.0p2-turba" and not lastest nightly? "4.0.0p2-turba" is a very very old build, no?
zinconnu said:
Wow, i'll try as soon as posible! Thanks! :good:
Just a question, why "4.0.0p2-turba" and not lastest nightly? "4.0.0p2-turba" is a very very old build, no?
Click to expand...
Click to collapse
No, no, my stuff is not old. This rom has been compiled from the latest codebase. However there were only little developments in AOSP and/or EVERVOLV's kitkat branch since more than one year. Devs have hopped off kitkat and grabbed for lollipop.
Since there is no official development for this rom, we can say that it is now sort of "abandoned". As I am not a part of Evervolv team, my hands are tied and I decided simply to stick to the "old" codename for the HTC Desire.
In short, you could say that this is a brand-new build which is based on latest nightly from 2015-07-18.
spezi77 said:
Thanks for your reply. I didn't have one of the problems you reported.
Could you share more details about your phone.
- hboot
- sd-ext partition
- recovery
Maybe could you also share a logcat when the phone failed to boot?
Cheers!
P.S.: after leaving my Desire on standby through one night (CPU gov: SmartassV2; 3G on; Wifi off), batt still had 28%.
P.P.S.: I have right now installed slim-gapps from Dec 2014: Slim Gapps 2014-12-02 - md5 26306ee3fb6b57a88c05286a1fef4ff9
P.P.P.S.: I have set zRAM to 30%; reduced animation/transition scales to 0.5%. Everything works really smooth in this rom.
Click to expand...
Click to collapse
Hey
Stock hboot
2GB ext partition (class 10)
Cwm4 recovery (still i didnt change the recovery ) )
I will take a logcat as soon as i can
Sd card doesn't mount and on the status bar shows sd card is damaged or insert one!
Sent from my HTC Desire using Tapatalk with KitKang
spezi77 said:
In short, you could say that this is a brand-new build which is based on latest nightly from 2015-07-18.
Click to expand...
Click to collapse
OK, i understand now, thanks for your answer. I'll try to keep this ROM an entire week to see how it reacts compared to the "old-kernel" version.
zinconnu said:
I'll try to keep this ROM an entire week to see how it reacts compared to the "old-kernel" version.
Click to expand...
Click to collapse
There is nothing better than using a rom for one week, in order to do benchmarking. :thumbup:
Sent from my nexus™4 ?
spezi77 said:
There is nothing better than using a rom for one week, in order to do benchmarking. :thumbup:
Sent from my nexus™4 ?
Click to expand...
Click to collapse
Ok here is my logcat and i find out that the USB tethering is not working!
i think the logcat is not complete and the device sometimes goes offline on adb!
if it's not enough then tell me to repeat it!
Thanks!:good:
Rminsh said:
Ok here is my logcat and i find out that the USB tethering is not working!
i think the logcat is not complete and the device sometimes goes offline on adb!
if it's not enough then tell me to repeat it!
Thanks!:good:
Click to expand...
Click to collapse
That logcat is sufficient. You were telling the truth. There is indeed an issue with your sd card (see error below).
It is tricky to do a remote diagnosis, but the simplest trick could be to format your sd card and again create a sd-ext partition. 1GB is really sufficient.
Or maybe do you have a 2nd sd card, just to ensure that the root cause isn't your sd card?
Code:
I/fsck_msdos( 114): ** /dev/block/vold/179:0 I/fsck_msdos( 114): Invalid signature in boot block: 0000 I/fsck_msdos( 114): fsck_msdos terminated by exit(2) E/Vold ( 114): Filesystem check failed (not a FAT filesystem) W/Vold ( 114): /dev/block/vold/179:0 does not contain a FAT filesystem E/Vold ( 114): /dev/block/vold/179:0 failed to mount via NTFS (No such device) E/Vold ( 114): Volume sdcard0 found no suitable devices for mounting :(
Sent from my nexus™4 ?
spezi77 said:
That logcat is sufficient. You were telling the truth. There is indeed an issue with your sd card (see error below).
It is tricky to do a remote diagnosis, but the simplest trick could be to format your sd card and again create a sd-ext partition. 1GB is really sufficient.
Or maybe do you have a 2nd sd card, just to ensure that the root cause isn't your sd card?
Code:
I/fsck_msdos( 114): ** /dev/block/vold/179:0 I/fsck_msdos( 114): Invalid signature in boot block: 0000 I/fsck_msdos( 114): fsck_msdos terminated by exit(2) E/Vold ( 114): Filesystem check failed (not a FAT filesystem) W/Vold ( 114): /dev/block/vold/179:0 does not contain a FAT filesystem E/Vold ( 114): /dev/block/vold/179:0 failed to mount via NTFS (No such device) E/Vold ( 114): Volume sdcard0 found no suitable devices for mounting :(
Sent from my nexus™4
Click to expand...
Click to collapse
oh sorry! it's 1GB ext4 partition (not 2GB!)
im really confused! isn't it the swap partition that recognize for second partition?or /data ?
honestly it doesn't have problems with kitkang (kernel 2) or other roms!
Rminsh said:
oh sorry! it's 1GB ext4 partition (not 2GB!)
im really confused! isn't it the swap partition that recognize for second partition?or /data ?
honestly it doesn't have problems with kitkang (kernel 2) or other roms!
Click to expand...
Click to collapse
Alright. I thought that there is something wrong with your sd card partitions. Maybe it is worth to consider reformatting it? Have you used this guide? http://forum.xda-developers.com/showthread.php?t=2125513
Sent from my nexus™4 ?
spezi77 said:
Alright. I thought that there is something wrong with your sd card partitions. Maybe it is worth to consider reformatting it? Have you used this guide? http://forum.xda-developers.com/showthread.php?t=2125513
Sent from my nexus™4
Click to expand...
Click to collapse
ok , you were right
i changed my sd card with 8GB class 4 with 750mb ext4 and it works perfect!
still i have boot problems! after the htc logo the screen get dark and reboot to the htc screen again!
here is my logcat
Rminsh said:
Stock hboot
2GB ext partition (class 10)
Cwm4 recovery (still i didnt change the recovery ) )
[...]
Sd card doesn't mount and on the status bar shows sd card is damaged or insert one!
Click to expand...
Click to collapse
For me it is the same.
TWRP or 4EXT - does not matter.
SD Class 10 16GB (FAT32 + 1GB ext4 by gparted)
A moment ago I did logcat on the same hardware just after a clean install.
In the original turba mount the SD operate normally.
K3 is more sensitive.
Related
_~~~ Avaritia HD ~~~__
...when a DESIRE grows inordinately strong it becomes AVARICE ...
I tested almost all Desire HD ROMs with data2sd (!).... and i didn't like any of those. The reason is that the data2sd solution is done in a bad "patchwork" way. The reason is this: A Desire HD rom needs about 350mb for the system partition (nand). But the Desire has only 250mb for system available. To make HD Rom work all the devs move system stuff to the SD. This is needed if you provide an app2sd ROM because app2sd still needs some space of the internal data partition. But this is different on a data2sd ROM. In that case you only need 1mb of the internal nand. All other ROMs STILL move system stuff to the sd for their data2sd version although there is much free space on the internal now. Thats why i decided to make my own ROM .... optimized for data2sd only. This way all the 350mb of system is installed to the nand. This way i make good use of all the free memory that you get on data2sd and thats why i wont provide an app2sd version of this ROM. Instead of making data2sd for a ROM i made a ROM for data2sd.
Apart from that i tried to improve data2sd in general and the included script has advantages you don't get on other Desire HD roms. Other HD Roms use a "loop" device for data2sd. I find that a bit risky and thats why i didnt make that default but provide this as an OPTIONAL addon. The life-of-the-edge mod is not more risky than other data2sd Roms .... the difference is that I tell you about the risk and give you to choice if you want to use it....
This ROM is still work in progress and i still won't provide a full feature list (but i think you won't miss a thing because all "usual" features are included). Instead i give you a feature list of features that won't find in any other data2sd HD-ROM.
Features: (that make this ROM unique - at least for some time )
- partition alignment with zips.
- optimized layout for data2sd (system apps on NAND)
- ReiserFS, btrfs, JFS support + recovery
- "deadline" scheduler instead of cfq/bfq which is better for a microSD
I'll add some explanations for the features in future.
Requirements:
-A second Partition in Ext2/3/4 format (same as for app2sd - min 512 but 1024 mb highly recommended max is 2048 mb)
-FULL WIPE (if you come from any other rom or a version before 0.6)
-Default nand partition layout (if you dont know what this means dont care about it .... youll have it then )
Apart from the ext2/3/4 partition this ROM also supports other filesystems (btrfs, Reiserfs, jfs). See 2nd post for "mods" to align, format you partion in the desired filesystem. And for recovery.
Download
Avaritia HD v0.7 alpha (ftp - thanks c0urier)
Avaritia HD v0.6 alpha (ftp - thanks c0urier)
Avaritia HD v0.5 alpha (ftp - thanks c0urier)
WARNING: btrfs is still experimental, jfs is made for IBM servers with battery backed hdds, and the developer of reiserfs killed his wife ... so be careful with those.
Additional info: EXT3 is recommended. Akso see /sdcard/Avaritia/ for the config file.
Pictures
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Changelog (newest)
v0.7
- reverted rebase - Base is now RUU_Ace_HTC_WWE_1.32.405.6
- Cgroup errors on bfs fixed (through rebase)
Note: HTC using cgroup to speed up interactivity on CFS is not the way forward when
a sheduler MADE for interactivity (BFS) - CFS + cgroups is intended for large servers
and not for a phone.
- Dpad to wake / volume keys works now and included (see mods to "unflash")
- Power Notification widget included as default (see mods to unflash)
- Add custom Wallpaper to the default skin
- Fixed bootanimation (2 frames were too bright + made it a bit slower)
- Bluelight "fun" on boot
- Updated apks
- Some tweaks (mostly adopted from ownhere - thx ownhere)
- Some fixes.
For a complete changelog see the attached full-changelog.txt file
Known Issues and Recommendations
-As for all data to sd solution you may have slowdowns in some situations like market downloads if you have a slow microSD. Any data2sd solution is about space in the first place. But compared to other data2sd ROMs this ROM is faster.
-If you use any other filesystem you need the custom recover from 2nd post.
-FAKE quadrant scores if you use "life-on-the-edge". This does not show the real performance. This skips data base synchronization. It improves the performance (but not as much as bench suggests) at the risk of data safety.
- 720p not working. (see here)
Further Plans
Many....
Thanks
- Coutts99 for the Kernel
- ownhere for tools an help
- Sibere for data2sd/ext
- snq- : vdd, powermenu, camera etc
- woti23 for his unrestless benching
- supercurio and Unhelpful from #project-voodoo
- IEF from #alpharev
- c0urier for hosting
- all devs @ xda
GPL: kernel is an exact git-clone from coutts99 kernel till commit http://git.couttstech.com/?p=coutts...it;h=73857c9910ea276eca798f6cc6a10f424a5eace9 ... no changes to source only different .config .
Also make sure you check coutts thread:http://forum.xda-developers.com/showthread.php?t=849002
All credit for the Kernel to him
[ROM] Avaritia HD v0.1 alpha [ data2ext4 | data2btrfs]
Additional stuff:
Recovery
Clockwork 2.5.0.7 and 2.5.1.8 with support for wipe, install, Nandroid backup and restore for reiserfs, jfs, btrfs ... and ext2,3,4 of course
Custom recoveries
Alignment zip
This will format (WIPE !!!) you sd-ext in the desired format. In addition it will align the sd-ext partition to the "erase block size" of your sd-card ( 1 MiB alignment like gparted - Infos here. Zips do that for you ... ).
ALL alignment zips
Kernel
BFS kernel is here (default)
CFS Kernel is here
Mods:
- dpad to unlock (in ROM as default) + uninstall
- Power notification widget (in ROM as default) + uninstall
- The modified skin (in ROM as default) + original
- a custom splash1.img (see picture)
ALL mods
Splash1:
Looks great, will test it
----- place ------
EDIT: LOL. I was to slow for a placeholder. NVM i dont think i need it anyway... it's not a tutorial or something .....
melethron said:
----- place ------
EDIT: LOL. I was to slow for a placeholder. NVM i dont think i need it anyway... it's not a tutorial or something .....
Click to expand...
Click to collapse
hehe, sorry
what is the benefits of data2btrfs?
b3ndik said:
hehe, sorry
what is the benefits of data2btrfs?
Click to expand...
Click to collapse
Check the thread. In short btrfs is a copy on write filesystem. And overwriting is the slowest operation for a microSD. Btrfs has some options to optimize the ssd devices. Especially slow cards profit from it (for good cards it may be worse). Apart from that it doesn't need journaling to be safe because of COW. This decreases the overhead on writes.
Overall data2sd feels smoother on btrfs than on ext4 (at least for a class 2 microSD). Check the thread for more info and note that BTRFS is a BETA FILESYSTEM.
I just gave you another post directly below your original one All you have to do is edit it and use it.
Nice to see you choose the right ROM
I'm following your progress of your btrfs work a time now, and played around with it, too. I flash it to my device, lets see how it is
Please make the same with the desireZ rom
PaY87 said:
Nice to see you choose the right ROM
I'm following your progress of your btrfs work a time now, and played around with it, too. I flash it to my device, lets see how it is
Click to expand...
Click to collapse
Coutts99 recommended it and after i looked at it found it rather easy to check the structure. Not much symlinks etc. Very clean and AFAIK the ROM that is closest to stock. Still needed to adjust many things (zipalign etc).
rolfd said:
I just gave you another post directly below your original one All you have to do is edit it and use it.
Click to expand...
Click to collapse
Thx for that
animehq said:
Please make the same with the desireZ rom
Click to expand...
Click to collapse
Atm i first focus on btrfs and this rom. I also need to get familiar with cooking first. Maybe in the future, but don't wait for it. Sorry
We will wait for pays next release.
With btrfs
but good work by melethron.
PaY87 said:
Nice to see you choose the right ROM
I'm following your progress of your btrfs work a time now, and played around with it, too. I flash it to my device, lets see how it is
Click to expand...
Click to collapse
Sent from my HTC Desire using XDA App
animehq said:
Please make the same with the desireZ rom
Click to expand...
Click to collapse
If this btrfs works good, then of course i will release such version dont worry hehe
@melethron
Congrats on the rom btw
WHAT software can i make a data2btrfs in my sd card???
gn123099 said:
WHAT software can i make a data2btrfs in my sd card???
Click to expand...
Click to collapse
The best way if you are not already on a linux based system, is to grab a livecd and use gparted. Normally I would recommend Ubuntu, but Ubuntu 10.10 LiveCD got problems with btrfs + gparted. So you could try fedora or opensuse e.g.
Of course you can also use the gparted live cd or usb version.
I never tried them, but should be the same:
http://gparted.sourceforge.net/livecd.php
With gparted format your sd card to FAT32 (first partion) and then 1024MB to btrfs (second partition).
Copy the ROM to your FAT32 partition and flash it through the recovery. I recommend AmonRAs latest recovery!
Don't forget to wipe before you flash! Don't worry if you get error messages when trying wiping the sd-ext, just ignore that.
Regards
I flashed the rom in btrfs mode. Installation without problems.
Its nice to see so much space on the phone.
The only thing is that the device really seems slower now.
Of course this is not your fault, you give us a great solution for more storage, but you can feel the difference.
I will let the phone do some caching and will use it a hole day tomorrow. (Navigation included). Lets see maybe things will settle down a little.
Maybe it could be improved with a optimized kernel.
I got a class 6 sd card by the way.
PaY87 said:
The best way if you are not already on a linux based system, is to grab a livecd and use gparted. Normally I would recommend Ubuntu, but Ubuntu 10.10 LiveCD got problems with btrfs + gparted. So you could try fedora or opensuse e.g.
Click to expand...
Click to collapse
Pays, i normally use either UltimateLinux build for the meerkat or plain lynx. Are any of these distros have issue with btrfs too ?
Thanks
BL
I'll be testing this as soon as I can as I'm skeptical of Btrfs. Only way to check and test the actual Btrfs usability and performance with our device and ROMs is to use it with one. I'll try it with a class 2 SD first, then class 4 and 6 that I own. Thanks.
EDIT: Yeah, your "my data2btrfs" link talks about "advantages" where no. 1/2/4 are all speculation yet. There's no studies or widespread reliable, repeatable, and conclusive testing showing either. Basically, this is experimental.
EDIT2: Sorry can't help further. I bricked my device. Carry on.
------------------------------
- Sent via HTC Desire -
I'm giving this ROM a shot, currently downloading and partitioning it. You used coutt's btrfs_test kernel right?
Dragooon123 said:
I'm giving this ROM a shot, currently downloading and partitioning it. You used coutt's btrfs_test kernel right?
Click to expand...
Click to collapse
Read first post again...
Lol, missed it. Sorry .
FolioMod TG 1.0
BY TOPOGIGI
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEATURES:
- Based on Toshiba 5.0.131 Final Release (Froyo 2.2) with some spices from Dexter's FolioMod
- TG (me!) OC kernel rel. 2.6.32.9 with CIFS, UTF-8, 1.4 Ghz OC, UV capabilities, CPU Spy support, TUN/TAP support (kernel is compiled with an optimized Linaro Toolchain)
- EXT4 filesystem for /system, /data and /cache partitions
- /system/etc/init.d support
- Deadline scheduler tweaked for better performance is the default scheduler
- Optimized OOM and minfrees in init.rc
- Optimized ipv4 buffers in init.rc
- HoloLauncher and Stock Toshiba Launcher are available
- Optimized mount points for maximum performance
- Updated Gapps with network localization support (new Google Play Apps including Store, Maps, Street, Gmail, YouTube)
- Built-in Google Play Music
- Built-in updated Flash Player
- Built-in Backported ICS keyboard
- Built-in Button Savior (On Screen Buttons)
- Built-in J4velin Notification Toggle
- Built-in Opera Browser and useful apps
- ICS-ish Theme
- Build.prop tweaks to pretend to be a Motorola Atrix for market apps compatibility
- 1% Battery Mod
- Busybox 1.19.3 installed in /system/xbin
- SuperSU is included
- Folio Buttons is included (you can have the HW buttons lit during night operations)
- Extended Poweroff menu with reboot option
Click to expand...
Click to collapse
Long story short, this is a Stock Toshiba ROM rom with a ton of tweaks applied. Yes I know, it's Froyo, but this rom is a good performer, can do almost everything and has the following plus points:
- All is in working condition, including SCO over bluetooth, IR Remote, Hardware Keys and so on
- Almost no SOD. I struggled a lot to achieve this result, but now I can say that this rom is behaving like any other Tegra tablet on the market. SODs are very rare here and the device sleeps like a child.... (As a side effect, you have to push the power button two or three times to make the device wake up)
- Easter Egg: Selecting Backup from the Privacy menu in Settings, the rom will reboot to recovery....
Feedbacks are welcome.
DISCLAIMER: This ROM comes with NO warranty. If you brick your device, don't blame me, I'm only experimenting with my phone and sharing the results with you, mates!
The widgets in the screenshots are SiMi Clock (clock & weather) and Android Pro Widgets (with modern ICS theme). They are NOT included in this ROM but they are available through the Google Play Store
INSTALLATION INSTRUCTIONS:
- BACKUP BACKUP BACKUP your actual rom and your data before installing anything!!!!!!
- I assume you have CWM recovery installed on your tablet. If not, flash the CWM 3.0.28 recovery before installing this rom and format all the partitions if you are coming from CM10/JB roms
- Copy the file you have downloaded "as is" (don't try to extract the files contained in the .zip archive!) in the root directory of your SD Card.
- Boot in CWM, select "Install zip from SD Card", then choose the .zip archive you have previously copied and wait until the process ends.
- Reboot your device and enjoy your new rom.
- This rom installs CWM 3.0.28
Click to expand...
Click to collapse
P.S. This rom WIPES your SYSTEM, DATA and CACHE PARTITIONS!!!
KNOWN ISSUES:
-None so far. Sometimes some SD card make the system hang on boot, so remember to extract your SD card on reboot! (you can put it back in when the boot is finished...)
Click to expand...
Click to collapse
Good luck!
DOWNLOAD:
1.0 - Full ROM with TG's kernel (1.4 Ghz) with EXT4 partitions http://dl.dropbox.com/u/74640239/TG_FolioMod_10.zip
1.1 - Full ROM with TG's kernel (1.4 Ghz) with EXT4 partitions http://dl.dropbox.com/u/74640239/TG_FolioMod_11.zip
Click to expand...
Click to collapse
__________________
CHANGELOG:
1.0 Initial Release [OBSOLETE]
1.1 NTFS, 3G [ACTUAL]
- Cleaned up all the unuseful stuff (gps permissions, gps.conf, unuseful build.prop entries, Huawei ril, etc.)
- Added ntfs r/w support via USB OTG Helper (see below notes for how to)
- Added preliminary 3G dongles support via PPP Wizard
- Added delayed execution for mount tweaks to avoid filesystem corruption if a SD card is left in the slot on reboot (you have now 60 secs of time to safely reboot if system hangs due to the forgotten SD card in the slot)
Click to expand...
Click to collapse
CREDITS:
- The entire Folio 100 XDA community
- Zeppelinrox for V6SuperCharger
- Dexter for his hard work on FolioMod
....and many others that helped sharing their ideas and work for free.
Click to expand...
Click to collapse
Woah ! This is what i was looking for ! Downloading ...
Sent from my Galaxy Nexus using xda app-developers app
What a nice surprise!!!! Thank you, I try.
Wow....something new but old!!!
I mea...maybe with a dual boot with CM10 and this release.....but CM10 is better, faster and newer!!
Thank you for sharing your work, congratulations for the high optimization you achieved.
raptor92 said:
Wow....something new but old!!!
I mea...maybe with a dual boot with CM10 and this release.....but CM10 is better, faster and newer!!
Click to expand...
Click to collapse
CM10 is not directly comparable: some people need a fully working rom (IR remote, SCO audio over bluetooth, etc.)
So, this rom is aimed to solve some problem for some kind of people.
On the "faster" point: are you sure?
You are comparing a 1.4 Ghz kernel with a stock 1.0 Ghz one, it's unfair.
This rom wins hands down in all speed tests only due to the OC kernel....but it is faster!
TG Foliomod 1,0 - frodo
Topogigi said:
CM10 is not directly comparable: some people need a fully working rom (IR remote, SCO audio over bluetooth, etc.)
So, this rom is aimed to solve some problem for some kind of people.
On the "faster" point: are you sure?
You are comparing a 1.4 Ghz kernel with a stock 1.0 Ghz one, it's unfair.
This rom wins hands down in all speed tests only due to the OC kernel....but it is faster!
Click to expand...
Click to collapse
do not listen to people's comments. I particularly think it's a great rom and very fast. thank you very much:
This is what I'm looking for since december 2010..... a great great great thank you from Imola.
Install Guide CM10 A4/JB
Hello,
Install Guide for CM10 A4/JB.
1. Format everything.
2. Erase recovery.
3. Flash needed recovery.
4. Install update-cm-7.2.0-RC0-Folio100-KANG-signed.
5. Go to "Settings">"Storage"> "Erase SD card"(It should be 1GB of size)
6. Then your Internal SD card size should be 12,53GB.
7. Enter recovery and install ROM.
8. Your Internal and External SD should work.
Aheros said:
Hello,
I didn't tested ths ROM, but here is couple of things:
Click to expand...
Click to collapse
Here comes something I don't understand: if you did not test it, how can you write a review on it?
Positive:
1. Good performance
2. Battery life.
3. Flash player.
4. Added some useful functions.
Click to expand...
Click to collapse
All true, indeed, but nothing more besides what you can argue by reading the OP, huh?
Negative:
1. Android 2.2.
2. YouTube app is hard to use.
3. Text selection, copy&paste.
4. Status bar low functionality.
5. HD videos?(Don't remember)
6. SD card SOD.
Click to expand...
Click to collapse
1. Yeah, that's declared in the OP
2. YouTube has now the same inteface among Android releases....Try the included app!
3. A simple keyboard with cursor keys helps a lot here. I personally use Smart Keyboard Pro, but there is a wide choice on the Store
4. Elaborate, please....With j4velin Notification Toggle and Button Savior you have the same functionality of an ICS/JB/CM9/CM10 status bar....Try it, you'll be amazed!
5. HD Videos are working flawlessly (with the tegra 2 platform limitations, i.e. 1920x1080 only main [email protected] level HW decoding)
6. SOD what?
You could help improving CM10 on Folio 100, like adding new stuff and fixing minnor issues.:good:
Still, good work!
Click to expand...
Click to collapse
All the roms I have built here on XDA are based on stock stable releases (or rock solid CM final releases) to grant users the maximum available compatibility and ease of use without bugs. This is not a rom for pioneers, it's a rom for people needing a solid performer. CM10 is now in experimental alpha stage (although I'd define it an advanced beta stage thanks to the great developers that are involved into the Folio100 CM10 project) but this is another story...
Bye
Aheros said:
Hello,
I didn't tested ths ROM, but here is couple of things:
Positive:
1. Good performance
2. Battery life.
3. Flash player.
4. Added some useful functions.
Negative:
1. Android 2.2.
2. Hard to use some apps.(YouTube,Gmail etc.)
3. Text selection, copy&paste.
4. Status bar low functionality.
5. HD videos?(Don't remember)
6. SD card SOD.
You could help improving CM10 on Folio 100, like adding new stuff and fixing minnor issues.:good:
Still, good work!
Click to expand...
Click to collapse
Yes, Topogigi can you not help DerArtem with the CM10 rom? Maybee you can add cornerstone on your rom and on the CM10 rom. This is a thing that a lot of peoples will see on our folio.
I agree, but all this useful info should be included in OP because:
1. Its based on FolioMod and you must write what new is incuded and fixed after that many years.
2. Android 2.2 is already fast on its own, increasing speed and adding tweaks is minnor.
3. Added apps didn't amazed me.
4. I'll test it for sure.
5. Include something "new" to your ROM, because it same FolioMod 1.4 just added nice effects.
I will post full feedback & continue your ROM.
Aheros said:
I agree, but all this useful info should be included in OP because:
1. Its based on FolioMod and you must write what new is incuded and fixed after that many years.
2. Android 2.2 is already fast on its own, increasing speed and adding tweaks is minnor.
3. Added apps didn't amazed me.
4. I'll test it for sure.
5. Include something "new" to your ROM, because it same FolioMod 1.4 just added nice effects.
I will post full feedback & continue your ROM.
Click to expand...
Click to collapse
1) This rom id not based on Foliomod, it's based on last Toshiba official release. Foliomod 1.4 has only the libraries from it.
2) Network Location does not work on FolioMod 1.4 (guess what? here it works....)
3) Initial Setup Wizard hangs on Foliomod 1.4, and it asks you to slide a keyboard out (our device has no physical keyboard) and here it works flawlessly
4) Google Play Services do not install on Foliomod 1.4 (mismatched signature of googleservicesframework.apk) and here it installs properly
5) You can't reboot to recovery in Foliomod 1.4 and here you can
6) No loop mount points here, while foliomod mounts the databases on a loop mount point for faster db access... but, guess what? In this rom you get the same database access speed without the risk of getting data losses if the device hangs unexpectedly
7) No CPU Spy support on Foliomod 1.4. This is the first Folio rom with CPU Spy support
8) No CIFS Support on Foliomod 1.4 while here you get CIFS and UTF-8 support
9) No TUN/TAP..............etc. etc.
10) No OC/UV...............etc. etc.
11) No enhanced deadline scheduler.................................etc. etc.
12) On Foliomod you have frequent unwanted screen wakeups while on this rom..............etc. etc.
13) On Foliomod you experiment network issues after wakeup while on this rom......etc. etc.
14) On Foliomod you experiment frequent SODs while....................etc. etc.
I can continue for a while on but frankly I am bored because ALL these infos are on the OP if someone takes care of reading it completely.
I called this rom Foliomod because I do respect all the efforts Dexter made for making this device a functional device. This does not mean I copied his rom only making it more attractive. You got the point now?
Regarding speed, I do not want to resemble Monsieue De La Palisse stating that a 1.4 Ghz Froyo rom is 1.4 times faster than a 1.0 Ghz Froyo rom, but you forced me to put that in evidence.
All added apps are in /data. If you don't like them, you can uninstall them with a few touches.
That's all, I'll answer other question if you will be so kind to test the rom for real. I put in it some weeks of hard work to reverse engineere, debug, code, patch and so on: testing it will cost you less than 1/2 hour, so.....
swimmer 4 said:
Yes, Topogigi can you not help DerArtem with the CM10 rom? Maybee you can add cornerstone on your rom and on the CM10 rom. This is a thing that a lot of peoples will see on our folio.
Click to expand...
Click to collapse
DerArtem and Nopy are very skilled developers, trust me. If they eventually will need help on a specific issue/bug/problem, I'll cooperate for sure. But I'm developing roms for 4 different devices ATM, and I have little if not less spare time to dedicate to another project. I'll actively support this rom for sure and I'll take care of feedbacks and suggestions. But this will cost me time and time is the real richness nowadays....
This is an excellent work Topogigi. Thank you for the time you spent there.:good:
I was convinced we could improve the stock rom but could not myself, especially lack of time and knowledge. I am glad that you have done.
(I speak here : http://forum.xda-developers.com/showthread.php?t=1655050&page=2)
I installed your rom from the alpha 4 CM10 with CWM 3.0.2.8, formatting partitions and flash file formatsd of DerArtem, but it did not work and I had no access to the SD card internally. I also lost access to recovery, I flashed using fastboot.
So I installed CM7 to unlock the internal sd (erase sd card in settings) and reinstalled TG FolioMod.
(To unlock the internal sd is here: http://forum.xda-developers.com/showthread.php?t=1639690)
Improvements are superb with lots of good ideas. For the moment, I have not encountered any problems and the rom is very smooth, continuous testing and I installed some games well greedy and I joined your rom to work on our little Foliowiki.
Congratulations and sorry for my English.
Thank you for all the information and explanations. Will keep this ROM in mind.
Hi,
my ext sd card is not working
there are known problems?
how I could get them back to work?
gironimo said:
Hi,
my ext sd card is not working
there are known problems?
how I could get them back to work?
Click to expand...
Click to collapse
No known issue about external SD, besides the caveat contained in the OP
Try this way:
1) copy all the contents of the SD card on a PC
2) format it with FAT option
3) Put the SD card back into the Folio and check if it's correctly recognized
4a) If the SD card is recognized, restore all the content from the PC
4b) If the SD card is not recognized, please try with another: if the new one is not recognized you have a faulty SD card slot on your Folio.
Please report if the above solution solves your problem.
daveheart14 said:
This is an excellent work Topogigi. Thank you for the time you spent there.:good:
I was convinced we could improve the stock rom but could not myself, especially lack of time and knowledge. I am glad that you have done.
(I speak here : http://forum.xda-developers.com/showthread.php?t=1655050&page=2)
I installed your rom from the alpha 4 CM10 with CWM 3.0.2.8, formatting partitions and flash file formatsd of DerArtem, but it did not work and I had no access to the SD card internally. I also lost access to recovery, I flashed using fastboot.
So I installed CM7 to unlock the internal sd (erase sd card in settings) and reinstalled TG FolioMod.
(To unlock the internal sd is here: http://forum.xda-developers.com/showthread.php?t=1639690)
Improvements are superb with lots of good ideas. For the moment, I have not encountered any problems and the rom is very smooth, continuous testing and I installed some games well greedy and I joined your rom to work on our little Foliowiki.
Congratulations and sorry for my English.
Click to expand...
Click to collapse
Thank you very much for your positive feedback and your detailed instructions. I will try to make Huawei dongles work in my next release, alongside with NTFS r/w capabilities....
Thanks a lot for your rom, i will try it.
This started out as a little side project on the OmniROM threads, and it's about time some things are clarified, and what exactly done, is explained.
Currently, only a modified version of TWRP 2.7 recovery is available, and we *might* support other recoveries soon
We have moved ahead of the TWRP 2.7.0.0 originally available in orig-development, to 2.7.1.0, and eventually to 2.8.0.0 too. Enjoy!
What is aw3som3?
Developers have long tried to sqeeze in ROMs into legacy devices with low internal memory, and one of the ways to do this was by using custom tailored mtd_parts, which gave the kernel a partition table to use, with resized partitions. This was widely used on many devices like the HTC G1, MT3G, Hero, Evo4G, Desire, etc.
While that was a viable option for the HTC Pico, a small "problem" that popped up was that different phones have different NAND Devices, with different partition tables and pagesizes. Incase the modified custom mtd_parts even accidentally touched the boot partition, or has been offset'ed out of the available space, a partition would be lost.
As a solution, dynamically obtain 32 mB from userdata partition, and 48 mB from the cache partition, and hax the partition table as soon as the information is got from ATAG. This should make this method work on *almost* all Pico's out there, which have partition layouts as misc:recovery:boot:system:cache:userdata:devlog and partitions in the order misc:rec..cache:devlog:userdata.
Click to expand...
Click to collapse
I've changed the partition table layout, without modifying the actual mtdblock<n>, thus no further fstab/ramdisk editing is required.
table: 0->misc::1->recovery::2->boot::3->system::4->cache::5->userdata::6->devlog
original layout : recovery:boot:system:cache:devlog:userdata:misc
new layout : recovery:boot:misc:devlog:userdata:cache:system
To developers:
In case you want to modify any of the partition size defines, there are three defines, CACHE_SIZE_LEAVE, USERDATA_SIZE_LEAVE, and DEVLOG_SIZE_LEAVE. This, will leave that much mB as defined, and take the rest, put it in system partition. The default defines are: 8, 4 and 1 respectively.
You may clone this repo, and follow the following steps:
download and compile kernel from android-4.4-recovery branch from https://github.com/thewisenerd/android_kernel_htc_pico
put compiled zImage (arch/arm/boot/zImage) in root directory (i.e. cloned directory)
run the following command to repack recovery ./repack.sh
output recovery would be in output/recovery.img
Downloads:
TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=56168368&postcount=125
[*] TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55685051&postcount=108(26 sep 2014)
[*] Modified TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55430289&postcount=106(14 sep 2014)
[*] Modified TWRP 2.8.0.0: http://forum.xda-developers.com/showpost.php?p=55375649&postcount=104(11 sep 2014)
[*] Modified TWRP 2.7.1.0: http://forum.xda-developers.com/showpost.php?p=55246774&postcount=97 (05 sep 2014)
[*] Modified TWRP 2.7.0.0: http://forum.xda-developers.com/showpost.php?p=54709263&postcount=69 (09 Aug 2014)
[*] Modified TWRP 2.7.0.0: http://forum.xda-developers.com/showpost.php?p=54688800&postcount=65 (08 Aug 2014)
[*] Modified TWRP 2.7.0.0: http://forum.xda-developers.com/showpost.php?p=54484381&postcount=58 (30 Jul 2014)
[*] Modified TWRP 2.7.0.0 (resized): http://forum.xda-developers.com/showpost.php?p=53704940&postcount=6
[*] Modified TWRP 2.7.0.0: http://d-h.st/I4L
Kernel: You may use CodyKernel or the kernel provided by your ROM's developer that supports aw3som3.
Q: How to use?
A:
Wipe the system, data and cache partition.
fastboot flash the given recovery.img.
wipe the system, data and cache partitions, again. preferably use flash_erase on the partitions.
flash your preferred ROM
flash the given kernel, *with* aw3som3
you're good to go!
Sources
you can get the patches here:
PS#1: 0001-aw3som3-hax-the-partition-table.patch
PS#2: 0002-aw3som3-set-msm_nand_data.parts-later.patch
PS#3: 0003-aw3som3-rearrange-and-relay-the-partition-table.patch
thewisenerd said:
I've moved all the partition re-laying, resizing, etc, to a separate file, in drivers/misc, which should help keep clean the nand_partitions.c file, and we would have to worry only about one file, and related code. It also means that awesom3 is reduced to one patch
Click to expand...
Click to collapse
PS#1 (26Sep'14):
0001-awesom3-hax-the-partition-table.patch
0002-awesom3-allow-a-128-mB-userdata.patch
XDA:DevDB Information
awesom3, Tool/Utility for the HTC Pico (Explorer)
Contributors
thewisenerd
Version Information
Status: Stable
Created 2014-10-21
Last Updated 2014-10-21
Reserved
Questions&Answers
Q: Does this work?
A: Yes, it does
Q: Will it work on my phone?
A: no. it will blast into pieces. jk.
Yes, it should. The main reason that partitions are dynamically resized, is to avoid having to create tailor-made hex values for every type of NAND device that different picos have.
Q: why the name awesom3?
A: A couple of reasons, actually. I was using the awesome D.E. in my distro a few days before I wrote this patch. I liked that UI, mainly because it was cluster-free, and the maximum available space was always used.
Another, was a couple of twn_oc_helper scripts which I had written before this. I had decided to get rid of the scripts, once and for all, due to various reasons (you can read them here), and the working dir for those scripts was named awesom3. The name just stuck by, and voila!
misc
- setting timezone
1. settings-> Time Zone -> set timezone (closest) and offset.
Reserved
changelog
21Oct2014
- 128 mB userdata partition
- Fix wiping crash when block device is not present (credits to Ethan Yonker)
- mtp: fix log spam: findNode not finding a node is not an error (credits to that)
- Update reference to 24-hour clock (credits to Captain Throwback)
- display cpu temperature in twrp use TW_NO_CPU_TEMP := true to disable display use TW_CPU_CUSTOM_PATH := path to set custom path (credits to Jenkins)
- Add support for TrueType fonts (credits to Vojtech Bocek)
- Fix exfat-fuse handling (credits to Dees Troy)
- performance profile support (credits to Tom Hite)
- mtp: cleanup, fixes and performance improvements (credits to that)
- Update RECOVERY_VARIANT blocking to use project-path-for (credits to Matt Mower)
- Attempt to fix md5 issue with backups (credits to Captain Throwback)
- applypatch: add support for BML partitions (credits to Conn O'Griofa)
- atime is access time, let's just use mtime (credits to Jenkins)
- Remove extra slashes from zip path in openrecovery (credits to Matt Mower)
- Fixes for exfat-fuse (credits to Captain Throwback)
- recovery: Fix adb with linux 3.10 (credits to Benoit Goby)
- ADB sideload command not work (credits to Da Zhou)
- Check sehandle before fixing permissions (credits to Dees Troy)
- Attempt to automatically identify data/media devices (credits to Ethan Yonker)
older logs:
26sep'14
Fix handling of MTP fork/child process (upstream)
Include no strict aliasing for MTP (upstream)
Additional checks to prevent partitioning internal storage (upstream)
pico: use twrp.fstab (help unify recovery compilation with device tree)
removed UMS
updated MTP configs (Sachin Thomas)
aw3som3 -> awesom3
Click to expand...
Click to collapse
14sep'14
add mtp config
Click to expand...
Click to collapse
11sep'14
Add MTP support to recovery thanks mostly to bigbiff with a little help from Dees_Troy
Add command line capabilities - you can now execute various TWRP features via adb instead of the touchscreen
Add support for color in the console and give error, warning, and highlight lines different colors
Track backup and restore progress based on file sizes to provide a much more accurate indication of progress
Improve handling of /misc thanks to mdmower
Improve setting of time on Qualcomm devices thanks to [NUT]
Allow using images on slidervalue GUI objects thanks to Tassadar
Allow using variables and addition and subtraction in variables for easier theming
Add support for 1440x2560, 280x280, and 320x320 resolutions and update 240x240
Allow ui.xml file to include additional xml files to help break up the theme and make TWRP easier to maintain
Other minor fixes and improvements
Click to expand...
Click to collapse
05sep'14
updated sources to TWRP 2.7.1.0 (till 01 sep 2014)
removed TW_EXCLUDE_SUPERSU := true
removed TW_NO_EXFAT := true
Click to expand...
Click to collapse
09aug'14
use inverted logo
Click to expand...
Click to collapse
08aug'14
relay partition table
add graphic logo && text to differentiate between normal and awesom3 recovery
Click to expand...
Click to collapse
30jul'14
uses the normal pico_defconfig: !not! slimmered (this fixes *some* of the random reboots caused in recovery)
aw3som3: set msm_nand_data.parts later (0002-aw3som3-set-msm_nand_data.parts-later.patch)
Click to expand...
Click to collapse
27jun'14
resize the recovery
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
here's mine.
it's working.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
great work for this one @thewisenerd. :good:
i'm really excited for this aw3som3.
btw. what if we completely get the whole mtdblock5? we'll get a great space for /system.
it's time to use sd-ext completely.
Agaphetos said:
btw. what if we completely get the whole mtdblock5? we'll get a great space for /system.
it's time to use sd-ext completely.
Click to expand...
Click to collapse
That's a question to the users.
p.s. added that to OP
thewisenerd said:
That's a question to the users.
p.s. added that to OP
Click to expand...
Click to collapse
make a POLL for it. :good:
will you please tell me step by step procedure i am noob and don't know how to do all this stuff
I am currently using CM11 weekly 4 TWRP 2.7 recovery
the recovery has been resized, hopefully. get another beta here: http://www.solidfiles.com/d/e6d39a02c4/recovery.img
hopefully, we're just a few commits away from a complete partition table rewrite... I've decided to move devlog to the beginning, then, a 4 mB cache (you shouldn't need more), and the rest for the /system partition. What about /data? sd-ext becomes /data partition by default. I posted a poll on the FB group and most of the people are clearly fed up with internal memory being very low hence, already using sd-ext by default, why "waste" the data partition?
This would stay in beta till some more time.
a new build of twrp should be out any time soon... the kernel, slimmered down to 1.8 mB without affecting actual functionality, *and* adding back support for ext2/3 and exfat and ntfs.
the recovery's size has been slimmered too, by modifying its ramdisk compression. you might not be much interested in all that, but you should see the change in recovery size from this build itself.
and finally, here's the boot.img: http://d-h.st/5jK
proof that it works (otherwise which no one's going to download anyways):
as we are going to use complete /data partition + some moar of cache partition, 112 +
just pushed sources to git some time ago...
you can get the patches here: https://github.com/thewisenerd/android_kernel_htc_pico/commit/eaa7cd3d0d25b44ecbe026ea03dce796868adb35
slimmered recovery defconfig: https://github.com/thewisenerd/android_kernel_htc_pico/commit/1fbb5f37851d6ff4a1d40d91e71d39ac107cd8c4
Tried it on cm 11 works great thanks for the recovery and boot.img
noob question
pico hackr said:
Tried it on cm 11 works great thanks for the recovery and boot.img
Sent from my XT1033 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
how do I made this work bro?
I mean how many partitions should I have particularly their each sizes too
thanks in advance
Agaphetos said:
here's mine.
it's working.
Click to expand...
Click to collapse
instead of
Code:
http://dl-1.va.us.xda-developers.com/2/8/1/6/0/8/7/Screenshot_from_2014-06-24_202911.png?key=Kg2Fp7s86-Ky-H0UFugPJQ&ts=1403661729
use
Code:
http://forum.xda-developers.com/attachment.php?attachmentid=2816087
as your image link... that should fix image not showing.
memontalha said:
will you please tell me step by step procedure i am noob and don't know how to do all this stuff
I am currently using CM11 weekly 4 TWRP 2.7 recovery
Click to expand...
Click to collapse
theBstep said:
how do I made this work bro?
I mean how many partitions should I have particularly their each sizes too
thanks in advance
Click to expand...
Click to collapse
Its for this very reason that I wrote this patch. Users don't have to do anything, except what's written in OP.
This is out of beta now, (read: stable), and can be used.
For others: I'll be shifting to a "no userdata", "4 mB cache", and all for "system" policy soon. Hopefully, you can revert back those commits if you don't need. As a user, 150 mB has never been adequate since I had used 40int2ext, and so, I'll be making sd-ext for /data as default.
This would also involve refactoring the entire table, I've decided to move devlog a few places ahead and order it as boot:devlog:cache:system, which should, technically, make stuff easier (for me) if done in the kernel side.
Don't want that? Revert back those commits, simple as that.
p.s. after thinking about this for sometime, this would also involve editing fstabs, recoveries, etc, etc, so, we'll rather stick to the current partitioning, i.e. mtdblock3/4/5, and keep it as 1 mB userdata, rather than no userdata, so that all the mess of having to edit other stuff would be minimised.
welcome working pa's micro modular gapps (soon), which takes up about 135 mB of /system partition, which should fit, after we bring in some more space from userdata partition.
Perfect Setup Bro
Well it will be good if we use sd-ext as data default
Much System Space :laugh:
Regards : Bilal
Sent from my One M8 using XDA-FORUM, powered by appyet.com
well it's a nice work,but also make a guide on how to revert back to original partition table.
Jituv1996 said:
well it's a nice work,but also make a guide on how to revert back to original partition table.
Click to expand...
Click to collapse
Just flash a recovery and kernel that's not modded?
can i try using this recovery and boot.img with in2ext+??
will it work without any problem?
i dont wanna lose my partition
Hpsgill said:
can i try using this recovery and boot.img with in2ext+??
will it work without any problem?
i dont wanna lose my partition
Click to expand...
Click to collapse
it didnt worked for me I have to install fresh rom for using this mod .
btw thanks @thewisenerd for this aw3som3 mod ill be using it for weeklies
noobified
I tried and so far so good with cm weekly 5 :laugh: I flashed latest cody kernel by the way
the thing is how can I increase internal memory cus only system increased? do I need to add a partition again so that makes 4: fat32, sd-data, sd-cache and sd-ext
theBstep said:
I tried and so far so good with cm weekly 5 :laugh: I flashed latest cody kernel by the way
the thing is how can I increase internal memory cus only system increased? do I need to add a partition again so that makes 4: fat32, sd-data, sd-cache and sd-ext
Click to expand...
Click to collapse
nah, fat32, and sd-data would do
Its really messed up (all the "extra" partitions), considering we don't need to worry about the /cache partition.
The only partitions you need are a fat32 partition, and *one* ext2/3 partitions. Any more partitions, your headaches.
Also, I would suggest that mmcblk0p2 is directly mounted as /data, instead of using any scripts :angel:
hahaha okay as a matter of fact I followed your instructions to partition without card reader http://forum.xda-developers.com/showthread.php?t=2532212 which is really helpful
mmcblk0p2 mean I can modify it for increasing internal?
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.
*
* DO NOT LEECH MY DOWNLOADS, PLEASE RE-DIRECT YOUR FORUM /PAGE
* TO THIS THREAD, IF YOU LIKE MY WORK, YOU CAN SAY THANKS,
* AND MAYBE BUY ME SOME BEERS
*/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Open Sourcing Mediatek - Wiko DarkMoon ; SoC MT6582
Being owner of an Mediatek device, means (most of the times) not having the sourcecode published by the Official vendor.
Wiko only published an faulty source (incompleted, and unbuildable sources).
Furthermore the source is not for our device (its incompleted and belongs to another phone ...)
Well this is xda after all, meaning we can accomplish pretty much everything
This is an fully Custom Kernel Source.
Hello Guys !
In this thread you will find my custom Kernel for the Wiko DarkMoon (and Clones)
Please be sure to read (and re-read) to avoid unnecessary questions.
Changelogs
Changelog v1.2 (February 15 2015)
Toolchain: Now compiled with the Latest Linaro-Cross 4.9.1
Source fixs in order to compile with Linaro's 4.7>+
New compilation build flags (enabled neon/ ffast-math, etc)
Disabled Mediatek debugger daemon aee
Kernel compression LZMA > XZ
Reduce vfs cache pressure to 20
Random: Entropy tweeks
TCP: initial TCP window size lock to 64K
Dynamic Management of dirty page writebacks (Fully controled on Performance Control app / other kernel management apps)
Increase Swappiness 60>70 (Better UI)
vm MAX readahead increase 512>1024
mm: vm MIN readahead increase 16>32
Several MTK Platform Fixs; Bad symbols fixs
Add IO Schedulers:
Sio
row
vr
zen
Add CPU Governors (enabled):
Ondemand
Hybrid
Conservative
Interactive
Changelog v1.1 (10 August 2014)
ToolChain: Mooved to Linaro Toolchain 4.6.4 Cortex Optimized
CPU Governor: Added SmartAss v2
MTK vermagic hack …
VM_MAX_Readahead 128 --> to 512 Kb
Tweak vm dirty ratios
Compile vfp with neon
NOATIME and NODIRATIME by default
Disabled GFS and enabled ARCH_POWER
Optimized SLUB
Asynchronous I/O latency to a solid-state disk greatly increased
Changelog v1.0 (August 06 2014)
Insecured
Persistent ADB
Compiled using GCC 4.6 ToolChain
zImage Compression changed from GZIP to LZMA
VM MAX READAHEAD changed from 128 to 512 Kb
Removed debug Sh##
Merge Userdata Partition + Internal SDCard
GPL Compliance:
Kernel 3.4.5
GitHub Repo
I do respect the GPL, but using someone else's work without proper credits is just LACK OF RESPECT.
The inclusion of this kernel in your ROMS is NOT allowed.
Instead add a link to my kernel thread as a recommendation on your thread.
I Don't support KANGS!
So please Show some respect, when using my commits, as well as the commits i added from other Dev's (with proper credits/ git authorization)
Fail to comply and i will drop this project
Credits:
superdragonpt
Christopher83 For his awesome ToolChains / Dirty Pages writebacks
varun.chitre15 For several MTK commits (git Authoriz)
faux123 For some merged commits
All (common) kernel contributors | www.kernel.org for keeping Linux / Android alive
I would also like to thank:
bgcngm, for the MTK unpack / repack kernel scripts
XDA:DevDB Information
[KERNEL][3.4.5] Wiko DarkMoon (MT6582) | Performance |, Kernel for the Android General
Contributors
superdragonpt
Source Code: https://github.com/dragonpt/Kernel_Wiko_DarkMoon_Custom
Kernel Special Features:
Version Information
Status: Stable
Current Stable Version: 1.2
Stable Release Date: 2014-08-06
Created 2014-08-06
Last Updated 2015-02-16
How to Flash You'll need an Custom Recovery:
You can find the latest Carliv Touch Recovery (CWM Based) here
On recovery:
No need to wipe anything
Just Flash the kernel.zip
It wont afect the rom, or your userdata
But Just in case, make an full backup before flash
Download
Kernel Download is available in the XDA: DEVDB
Or
On my dev-Host
KERNEL_Wiko_DarkMoon_v1.2.zip - 4.05 MB
KERNEL_Wiko_DarkMoon_v1.1.zip - 4.21 MB
Notes
When giving feedback, please refer what's the kernel version / Rom your using
YOUR FEEDBACK IS IMPORTANT
F.A.Q
F.A.Q
What's this new Partition Layout thing ?
--> In Order to fix the Bad stock device Layout (having so less space for installing apps), since Wiko choose to have the emmc nand divided into an Internal SD + Userdata.
I Modified the Kernel partition layout, so that both are merged together (and this is the right way)
So.. What do i need to do?
---> If your using the Stock partition Layout, i have included an modified fstab on the rom.zip so that your device dont fall into bootloop ... however only one of the internal partitions will be available
---> I stongly advise that you modified your Device Layout with the internal userdata mod v2 (2.5GB)
--> IF you still find some issues mounting the SD Card (External), there's an alternative patch that you can download and flash on Recovery (EDIT: Merged on Kernel v1.1)
After flashing the internal userdata mod v2, i have "Phone Storage is damage", what Can i do ?
--> You need to reboot into recovery and wipe /data , later you can restore your data in the advanced Restore Option.
How can I change IO Schedulers and Governors ?
--> You can use the Performance Control app to change CPU Governors / IO Schedulers and many other Kernel features.
What's the Best Governor / IO Scheduler?
--> Depends on your needs (Performance; Powersaving; etc)
An good resource, check this This Thread OR Just Google it ...
Great congratulations!
One question: with the partition mod, there's only sdcard storage available?
Gesendet von meinem T0LTE mit Tapatalk 2
After install sdcard with 0mb free. And sdcard1 with external SD. Cannot install nothing.
Have I done something wrong. On 2.5gb mod.
Regards
Obrigado
Sent from my DARKMOON using Tapatalk
DerTeufel1980 said:
Great congratulations!
One question: with the partition mod, there's only sdcard storage available?
Click to expand...
Click to collapse
Hi, yes (check pics)
I could made the External SD Card show as "SD Card" but apps still think that was an Internal SD card..
So i modified the fstab this way, and everything works (keep in mind that for this to work i had to modified the partition.define on kernel source code)
Regards
jcvr said:
After install sdcard with 0mb free. And sdcard1 with external SD. Cannot install nothing.
Have I done something wrong. On 2.5gb mod.
Regards
Obrigado
Sent from my DARKMOON using Tapatalk
Click to expand...
Click to collapse
Hi
There's an new alternative fstab file, that you can download, simply flash on recovery (no wipes required)
Update INFO about this issue.
Thanks for the feedback
Regards
OK. With alternative fstab all work fine.
Thanks.
Regards.
Sent from my DARKMOON using Tapatalk
superdragonpt said:
Hi, yes (check pics)
I could made the External SD Card show as "SD Card" but apps still think that was an Internal SD card..
So i modified the fstab this way, and everything works (keep in mind that for this to work i had to modified the partition.define on kernel source code)
Regards
Hi
There's an new alternative fstab file, that you can download, simply flash on recovery (no wipes required)
Update INFO about this issue.
Thanks for the feedback
Regards
Click to expand...
Click to collapse
Ah, got it. At first I thought you merged [email protected] (I think it is dev/block/mmcblk0p5) with mmcblk0p8 (which is sdcard) to create only one big /data partition. In your rom you then could use sdcard binary (system/bin/sdcard) to map a virtual sdcard from data/media to storage/sdcard0. But that's only theory and I didn't try this.
Btw:
Do you also have a commit history for older changes?
Gesendet von meinem T0LTE mit Tapatalk 2
Good to see kernel development for mt6582! :thumbup:
Can't just imagine that it took 5 mnths compile it! Well to be really honest i think you would have got better feedback if you realeased it for canvas 2 colours and its clones like myphone agua rio, explay fresh, wiko rainbow, qmobile noir i9 etc because it have the most Android development mostly custom roms and users when we talk about mt6582 generally! ( its my opinion )
Dnt know wether we have the sources for our device or not but is there a way that we the users of similar device but much larger screen i.e 5" can take advantage of this kernel sources and its github repo???
I am new to kernel development so plz never mind this comment of mine you are already doing a great job out there once again keep up the good work! :thumbup:
Sent from my Micromax A120 using XDA Free mobile app
DerTeufel1980 said:
Ah, got it. At first I thought you merged [email protected] (I think it is dev/block/mmcblk0p5) with mmcblk0p8 (which is sdcard) to create only one big /data partition. In your rom you then could use sdcard binary (system/bin/sdcard) to map a virtual sdcard from data/media to storage/sdcard0. But that's only theory and I didn't try this.
Btw:
Do you also have a commit history for older changes?
Click to expand...
Click to collapse
Hi
With this modified layout, ebr2 wonr be used (so indeed i merged emmc+mmcblkxx internal SD into one single partition)
I wont be use an virtual SD Card (data/media) that really messes things really bad ...
ON all my source projects i always have an full commit history, but since this was an on going development for many months, it would be virtually impossible to make an full commit history.
Even worse, it would be useless, since you can't make an "diff" with an "original/stock" source, since there's none.
Most of the changes are under mediatek/platform drivers and mediatek/common and device configs.
And thers files are not on my repo, since they are copyrighted (as we all know) and i really dont need (another) DMCA takedown in one of my git repos.
--> In terms of changes in this new MTK platform MT6582/92, you can check both the Makefile, and build script under /kernel they've got several changes/ commits on them to get this source to compile.
I've done the best i could on # comment my changes on the files. (So you'll see a lot of #CM #WIKO DarkMoon .... etc)
Regards
malick186 said:
Good to see kernel development for mt6582! :thumbup:
Can't just imagine that it took 5 mnths compile it! Well to be really honest i think you would have got better feedback if you realeased it for canvas 2 colours and its clones like myphone agua rio, explay fresh, wiko rainbow, qmobile noir i9 etc because it have the most Android development mostly custom roms and users when we talk about mt6582 generally! ( its my opinion )
Dnt know wether we have the sources for our device or not but is there a way that we the users of similar device but much larger screen i.e 5" can take advantage of this kernel sources and its github repo???
I am new to kernel development so plz never mind this comment of mine you are already doing a great job out there once again keep up the good work! :thumbup:
Sent from my Micromax A120 using XDA Free mobile app
Click to expand...
Click to collapse
I usually only release source built works for devices that i own, it would be impossible to work on an device that i do not own...
About "porting":
Keep in mind, that the only common thing is the SoC (MT6582) everything else is different (device sensors/ custom configs and even custom drivers)
But yes, for an developer that knows what his doing, this aditional source, should be usefull
Regards
Camera
Hi guys
I got feedback from some users that some of you can only use the front camera, and you can't see the rear camera.
Let me just tell you, that this is not kernel related, but this depends on the Wiko rom version your using, i also tested and my own custom rom also suffers this minor issue.
Reason why, is that the initial wiko JB 4.2.2 Roms (from Build 8 /9/10/11/12/13) have different camera .blobs that are not compatible with this kernel (and thats why you see an different kernel build on different wiko rom builds), my rom is based on wiko build 8 btw ...
Tomorow i will release an patch (that will be pre-included in future kernel builds) that fixs this issue for all of you.
Regards
Thanks for the feedback
Kernel v1.1
Kernel Build : v1.1
Changelog v1.1 (August 10 2014)
ToolChain: Upgraded to Linaro-Cross Toolchain 4.6.4 Cortex Optimized
CPU Governor: Added SmartAss v2 (Check F.A.Q)
VM_MAX_Readahead: set to 512 Kb (was 128Kb on Stock)
Tweak vm dirty ratios
VFP: Compile with neon now
NOATIME and NODIRATIME by default
Disabled GFS and enabled ARCH_POWER
Optimized SLUB
Asynchronous I/O latency to a solid-state disk greatly increased
Camera (Rear) fix, for older WIKO Rom builds (including my own modded rom) (.blob)
Merged corrected partition table (older alternative fstab.zip)
Regards
Nice work. I've flashed your kernel 1.1 and after that I can't access my sd card. The apps on sd won't run. Can't take screenshots because it's says that don't have a sd card. I'm on latest official rom with your extended data mod with 2gb partition. Can you help me please. Thanks.
edit:
even after a factory reset i'm stuck in bootloop.
I'm using the official wiko tool to flash the original rom and i'll star all over again
any tips to make this work?
edit 2:
after flashing official rom, root, install custom recovery, extended data MOD 2.5gb (previous has 2gb), flashing kernel 1.1... now everything looks fine.
Sent from my Nokia 3310 using my fingers
outcubus said:
Nice work. I've flashed your kernel 1.1 and after that I can't access my sd card. The apps on sd won't run. Can't take screenshots because it's says that don't have a sd card. I'm on latest official rom with your extended data mod with 2gb partition. Can you help me please. Thanks.
edit:
even after a factory reset i'm stuck in bootloop.
I'm using the official wiko tool to flash the original rom and i'll star all over again
any tips to make this work?
edit 2:
after flashing official rom, root, install custom recovery, extended data MOD 2.5gb (previous has 2gb), flashing kernel 1.1... now everything looks fine.
Sent from my Nokia 3310 using my fingers
Click to expand...
Click to collapse
Hi
Thanks for the feedback.
So your saying that:
A) with the Extended userdata Mod v1 (2GB) ---> No SD Card
B) with the Extended userdata Mod v2 (2.5 GB) -- > OK
Myself im using v2, and everything is ok also
this is the best option, since you'll get the full internal memory for apps.
There's a lot of things im working on at the same time for the wiko ... but working with MTK stuff makes it a lot more harder ...
Regards ... and have funn
superdragonpt said:
Hi
Thanks for the feedback.
So your saying that:
A) with the Extended userdata Mod v1 (2GB) ---> No SD Card
B) with the Extended userdata Mod v2 (2.5 GB) -- > OK
Myself im using v2, and everything is ok also
this is the best option, since you'll get the full internal memory for apps.
There's a lot of things im working on at the same time for the wiko ... but working with MTK stuff makes it a lot more harder ...
Regards ... and have funn
Click to expand...
Click to collapse
Pretty much that. It didn't work for me with the 2GB mod, but so far so good with the 2.5gb. Seems to me that I got better ram management with your kernel nice work. If you need testers tell me.
Sent from my Nokia 3310 using my fingers
outcubus said:
Nice work. I've flashed your kernel 1.1 and after that I can't access my sd card. The apps on sd won't run. Can't take screenshots because it's says that don't have a sd card. I'm on latest official rom with your extended data mod with 2gb partition. Can you help me please. Thanks.
edit:
even after a factory reset i'm stuck in bootloop.
I'm using the official wiko tool to flash the original rom and i'll star all over again
any tips to make this work?
edit 2:
after flashing official rom, root, install custom recovery, extended data MOD 2.5gb (previous has 2gb), flashing kernel 1.1... now everything looks fine.
Sent from my Nokia 3310 using my fingers
Click to expand...
Click to collapse
Did you then restore data or you installed apps again
I'm getting Phone storage is damaged,when i flash v2.5GB,and when i flash custom kernel i can't install apps,i used the alternative script and tried restore data but it didn't restore anything...
pren22 said:
Did you then restore data or you installed apps again
I'm getting Phone storage is damaged,when i flash v2.5GB,and when i flash custom kernel i can't install apps,i used the alternative script and tried restore data but it didn't restore anything...
---------- Post added at 08:31 PM ---------- Previous post was at 08:18 PM ----------
Did you then restore data or you installed apps again
I'm getting SD Card is damaged,when i flash v2.5GB,and when i flash custom kernel i can't install apps,i used the alternative script and tried restore data but it didn't restore anything...
Click to expand...
Click to collapse
Hi. Here's what I've done:
- I flashed original rom with wiko tool.
- install the 2 updates OTA from wiko - root the phone
- install custom recovery
- flash the 2.5gb data mod.
- flash kernel 1.1
- finally restore all apps with titanium backup.
I hope it helps.
Sent from my Nokia 3310 using my fingers
hi,
i have the same problem!
i have instaled the v1.1 kernel and puffff... no SD card anymore!!!
Hi
Like said:
Flash the 2.5Gb userdata mod via SPFlashtool.
Reboot to recovery and wipe data ( make an backup of your internal SD)
Flash the kernel.
If by any chance it says "sd card damaged" this is normal becouse we had disabled the internal sdcard partition...
You can then follow up that message and format the internal userdata ( now extended)
Reboot
Regards
pren22 said:
Did you then restore data or you installed apps again
I'm getting Phone storage is damaged,when i flash v2.5GB,and when i flash custom kernel i can't install apps,i used the alternative script and tried restore data but it didn't restore anything...
Click to expand...
Click to collapse
After flashing the internal userdata mod, thats normal.
You need to reboot to recovery and wipe /data since the partition was now modified.
Later you can restore your old /data in carliv recovery on advanced restore.
FAQ Was updated with more Info
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.1.1 (LOLLIPOP), 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.
*/
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.
Unofficial build of CyanogenMod 12.1(Android 5.1.1) for the HTC Explorer (Pico)
Notable features:
No Maps 7 glitches, Browser glitches, Gmail glitches, etc.
Uses ION memory allocator
Native Sd-Card -- Using sd-ext partition for system and data
F2FS Support In kernel and Device tree
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)
Significantly smoother/faster graphics as a result of the new graphics libraries
Removed many hacks designed for old graphics
CAF KitKat 2.7 branch Adreno blobs
What's working:
RIL
Data Connection
Display
Stock browser
Camera
WiFi
GPS
WiFi tethering
Bluetooth
Bluetooth tethering
SDcard
Video playback
Audio playback
Headset
Audio Recording
Sensors of All type
Not working:
OMX ( hardware decoding/encoding )
Camcorder
Download:
BETA#1 : http://forum.xda-developers.com/showpost.php?p=61134823&postcount=316
CyanogenMod 12.0 Builds
Gapps :- https://www.androidfilehost.com/?fid=95897840722646482
Install instructions:
Use Class 6 or Class 10 sd-card for best performance
Make 2 ext4 sd-ext partitions like this
1st partition :- sd-data --->> 1GB minimum
2nd partition :- sd-system --->> 1.2 GB
Flash the updated [03/02/2015] TWRP 2.8.5.0 Recovery
Convert your /data and /system partition to f2fs you can find it in wipe option
Wipe all partitions
Flash the cm-12.1-*-UNOFFICIAL-pico.zip
Reboot
If you Stuck at HTC Splash Screen go into bootloader mode, take out boot.img from rom zip and flash it
Reboot
Done!
After first boot reboot back to recovery
Flash Gapps
Source:
https://github.com/CyanogenMod
Thanks to:
All Pico developers before me
PecanCM (TeamHackLG)
LegacyXperia
Use BUG Tracker in Thread to report your Bug
If you want to help fixing those bugs, please report the bugs in the bug tracker and provide me logcat or i cant help you. Thanks!
Logs are needed (logcat/dmesg/last_kmsg), not just "got FC" or "+1" useless replies.
You can get more info here on how to take log HERE
Donations :-
Buy Me A cup of Bear click on donate to ME button
XDA:DevDB Information
Android 5.0 lollipop ( CM-12.1 ) For HTC Explorer, ROM for the HTC Pico (Explorer)
Contributors
kirmaniarslan, Sachin Thomas
Source Code: https://github.com/HtcLegacy
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
ROM Firmware Required: Rooted
Based On: CyanogenMod
Version Information
Status: Beta
Current Beta Version: 1
Beta Release Date: 2015-03-03
Created 2014-11-19
Last Updated 2015-06-11
Changelog :-
CyanogenMod 12.1
Beta#1 03/06/2015 :
- Lollipop 5.1.1
- CM-12.1 Upstream
- Fixed Deepsleep issue
- Disable dialer lookup by default
- Switched to QCOM power HAL
- Added LZ4 Compress/decompress support
- Update zram and zsmalloc up-to 3.17 kernel changes
- inherit media_codecs_google_video_le.xml better for low end devices
- update ril.h for 5.1
- Disable dex2oat watchdog
- Don't disable jit cache
- Set dalvik.vm.dex2oat-filter=balanced
- Disabled LTE as our device doesnot support it
- Update Audio policy for 5.1
- Call broken and Wifi Calling fixed
- Increase ZRAM swap size to 192MB
- fixed heatset and Data connection problem on kernel level ( no patches needed )
CyanogenMod 12.0
Beta#3 02/03/2015 :
- CM Upstream
- Fixed Data Connection
- Fixed Headset thanks @thewisenerd for fix
- Fixed MTP connection with PC
- Enabled WITH_ART_SMALL_MODE you can read it more here : http://source.android.com/devices/tech/dalvik/configure.html#with_art_small_mode
- Symlink dalvik-cache to nand for performance and also decreases the battery usage ( u can see it as sd-ext in recovery for cleaning it )
- Disabled data encryption
- Updated audio_policy.conf from HTC one M7
- Set sd cache to 1MB
- Enable LOGD
- Using NuPlayer instead of Awesome player
- Based on Aw3some mod thanks @thewisenerd
- Gapps Lags Fixed
- Headset profile update from DX kernel 3.4
More Kernel Changelog
Beta#2 29/01/2015 :
- Cm Upstream
- Fixed GPS
- F2FS support in kernel and device tree added for /system and /data partition
- Fixed Sound Recorder
- Enable cortex a9 optimization
- Update HtcMsm7x27aRIL class
- Disabled alpha trasformation in animations
- Added New CPU GOV Intelliactive and set it to default governer
More Kernel Changelog You can Check from HERE
Beta#1 20/01/2015 :
- CM Upstream
- Fixed Camera (Still camcorder is broken )
- Setup for chromecast support.
- Lowmemory killer tweaks to fix oom issues
- Sepolicy inherit from common qcom sepolicy
- Force camera API to version 1
- Updated partition layout
- Set background process to 4
- Inherit dalvik-heap props with 512mb ram (This fixes browser Image Cache problem)
- Enable SystemUI flags to optimize performance
- Builtin bcmdhd module in kernel to fix loading and unloading issues
- Add custom HtcMsm7x27aRIL to fix SignalStrength on gsm
- Disable TARGET_CPU_SMP
- Disable Atlas service
- Cleaned up system.prop
- Disable JIT
- Configure ksm with low ram
- Allow legacy allocations from MM heap
Alpha#2 - 28/11/2014 :
- CM Upstream
- Enable dex-preoptimization to speed up first boot sequence
- Patches for performance Much stable and faster now
- SELinux Support : Set to Permissive mode
- Temp fixed soft reboots
- Forced high-end graphics for transparent lockscreen and statusbar
- Ril fixed GSM working but data connection is not fixed
- Added FFMPEG codec configuration
- Added SELinux support in kernel
- Disabled kernel features
- Added Multi User support upto 4 users allowed can be enabled with ( ro.config.low_ram=false in build.prop )
- Using Awsome Latest layout
Alpha#1 - Nov 19, 2014 :
- Initial upload
- Updated Libaudio
- Disable LOGD
- Enabled Minikin fonts
- Display and Media hals based on msm8960 with some hacks for msm7x27a
- Used dlmalloc instead of jemalloc
FAQ :-
Q: Why SD-ext and what is Partition layout ?
Ans:There is not much space in system partition even with awsome partition layout and secondaly here is the partition layout
/dev/block/mmcblk0p3 mounted as /system i used this partition so that you dont have to create partition again and again
/dev/block/mmcblk0p2 mounted as /data
Q; How Can I clean my sd-ext partitons ?
Ans : you can flash this before flashing rom http://forum.xda-developers.com/showthread.php?t=2392001
Q: I am stuck at HTC splash screen what to do ?
Ans:Simply Take out boot.img from Rom zip and flash it in fastboot mod
Code:
Fastboot flash boot boot.img
Q: I can't find developer options and performance settings, why?
A: Settings -> About phone -> Click 'Build number' several times
Q. No ROOT access WTF ?
Ans : Enable it from Developer option
CyanogenMod 12.0
CyanogenMod 12.0 Builds :-
BETA-3:http://forum.xda-developers.com/showpost.php?p=59174157&postcount=244
BETA-2: http://forum.xda-developers.com/showpost.php?p=58525401&postcount=177
BETA-1 : http://forum.xda-developers.com/showpost.php?p=58297444&postcount=142
Alpha-2 : http://forum.xda-developers.com/showpost.php?p=57106417&postcount=76
Alpha-1 : https://www.androidfilehost.com/?fid=95784891001612903
BasketBuild Mirror
Pico still alive, thank you kirmani for the sweet lollipop Hope it gets stable soon.
@kirmaniarslan You really Rock bro.. Didnt even think of getting a lollipop on our device. Salute you bro Really a grand salute.. You are keeping our device alive and running up.
wow amazing plzz build cm12 for redmi 1s a.k.a armani
Awesome work !!!! hope
Great Stuff Here i See (Y) Good Luck... if people have some issues they can P.M me i have some minor fixtures which can be done in Lollipop... as for now Lollipop is in alpha stages and is a real pain in the arse...
I'll be reporting issues myself when i see other than the given one's in the OP
Thanks man....awesome work
wow the feels!
bro kirmani is really hyping us up!
great work man!
I'll stay tune for this
Booted Successfully
It takes about 10-12 minutes to boot on Class 10 SD-Card
Wow good going pico rocks
Awesome!
BTW, guys is there any way to flash this recovery with any app in pico? (No PC atm)
Error
I'm getting a (bad) error. Any one else getting the same? I'm on CWM 5.0 and on Thinking Bridge rom.
kratikedat said:
I'm getting a (bad) error. Any one else getting the same? I'm on CWM 5.0 and on Thinking Bridge rom.
Click to expand...
Click to collapse
Use the given recovery
I installed from a 4GB mem card
It took 30mins or more to boot... but after booting too, it bootlooped! Same happening again and again!
Need to make any partitions?
TheStrix said:
I installed from a 4GB mem card
It took 30mins or more to boot... but after booting too, it bootlooped! Same happening again and again!
Need to make any partitions?
Click to expand...
Click to collapse
Havent u made sd-ext if yes then flash the rom again after wiping
kirmaniarslan said:
Use the given recovery
Click to expand...
Click to collapse
My bad, didn't read theiinstructions thoroughly enough. Another noob question if you dont mind, how do I flash a recovery over my existing recovery? Does the pico being s-on have an issue with it? Sorry again for the noob question!
Aswin08 said:
Awesome!
BTW, guys is there any way to flash this recovery with any app in pico? (No PC atm)
Click to expand...
Click to collapse
Use terminal emulator
keep the recovery3.img in the root of sdcard
su
cd sdcard
flash_image recovery recovery3.img
Aswin08 said:
Awesome!
BTW, guys is there any way to flash this recovery with any app in pico? (No PC atm)
Click to expand...
Click to collapse
@Ashwin08 this may help for you http://forum.xda-developers.com/htc-explorer/general/how-to-flash-recovery-phone-t2831744