Database Info

How to run the most stable rom avoid conflicts for newbies and skilled alike

The advice I provide is mainly for the stock 2.1 sense ui roms - 2.27.651.6 (+) but users will find the advice in here applies universally to several other rom builds, android versions, and problems many people will encounter as root - even if you follow dev directions for the rom...even if it is a final release...most of the info I posted is based off much testing, and, I have found the rom recommendations to be most stable for the recommended build 2.1 eclair build stock deoxed cdma sprint hero - again the advice, even apks I provide you may find useful for other roms you currently use). I cannot post large text due to spam regulations and since I am a new user so directions and info are attached in the word document. Trust me, this is a good read. I wish I had this advice when I first started modding my roms or even when I got good at it. Would have saved me days of time.
See attached ENJOY!
I attached one fix for the rom version as well as the circle battery mod which I think is awesome for ALL android phones. Kernals as well for the recommended 2.1 sense ui.
P.S.
Use the engineering boot flashable file at your own risk - it's optional - I happen to like it.
Also, if you brick your phone or you have problems with recovery - there is a way to fix this. Use the Unrevoked 3 for Windows on the hero (it is for the easy root) - this is not compatible yet - but go to load custom recovery and find your boot.img nandroid file which you may have trouble recovering from your current recovery or if you are having load up problems etc...this may get you temporarilly into the custom recovery for just enough time to use the proprietary recovery on the nand backup to recover your last most stable back up! This happens a lot to people who upgrade backup programs or alternate between them - read the document regarding recovery dos and don't. I also recommend reviewing some basic commands for adb shell and terminal programs.
Enjoy good luck. Comments or suggestions for improvements - re-wording is always appreciated - I'll see if I can modify as such and thank appropriate contributors. Oh and sorry for the typos
Cheers again,
Joe.

Hi,
Believe it or not, I read your whole Word doc. I am using ZenFX Lite ROM, which I like. I also tried the ZenROM.
Anyways, I'm run into the same problem. When I have JIT on, it always always locks and/or reboots when I use Google Navigation (turn by turn mode), or when I'm downloading about 3 or more apps at once from the Market. When JIT is off, I don't get reboots.
Can you confirm if you get this issue or not with JIT on with your solution?

[Q] Problem SDcard and Apps [XDAndroid FRX06]

Hello,
I have a HTC Touch Diamond 100 and I installed the "Froyo FRX06 XDandroid NEW system update" review in the post "[prj] [XDANDROID] [AOSP] [FroYo | GINGERBREAD] [31.03] System Update" and everything works fine except that it doesn't recognize SDcard applications.
There's no Error Message in the screen, is just that the system doesn't recognice anything in the SDcard. I put my apps in the folder: AndroidApps-> Other. I think it's not the common fault that I have read many people have "Waiting for SDCard error. For people who have problems with sdcard message, add this to your startupmsmsdcc_1bit msmsdcc_fmax=14000000 msmsdcc_nopwrsave" because for instance the phone let me save the pictures i've take with the camera phone or install and recognice any app from the market.
I 've Format the card with the HP tools after initial installation and then i had restore all the files in the internal storage.
P.S. Sorry for my possible spelling mistakes but English is not my native language

Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing

R^7Z said:
Keep in mind if you put the apk in anything other than the AndroidApps folder you will need to install them yourself. See THIS FAQ for further explanation. As far as the wating on sd card message you get when you are booting into Android, I get those all the time and have no problems with taking pictures. I would suggest that you use the full bundle from THIS post to ensure you have the latest. Unless you know what you are doing
Click to expand...
Click to collapse
Oh what A noob mistake xD I didn't know that apps in the "Other" folder doesn't follow the "typical rules" for instaling apps (i've come from previous releases of Android, Eclair specifically, and in that version it was only place in this folder to install apps).
I'm using froyo instead of gingerbread builts because HTC touch Diamond it's quite old and i don't know if the performance would be better or slower than froyo performace but if you recomend me to use that gingerbread bundle i would use it.
Thanks R^7Z.

Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...

R^7Z said:
Honestly, Gingerbread is "better" but it is alpha release at the moment. Yes, this means that there are quite a few more "improvements" to under-go! I only recommend it if you like the idea of Android. The latest releases for FroYo aren't bad but it seems there are a few hard instability hits it has taken since FRX03 (last time I really enjoyed running a FroYo build from the XDAndroid project). Since then, I've been playing around with a few things and builds to include but not limited to this new idea of CWM (clockwork mod/Gingercherry tutorial) which is posted in the neopeek forums. So, unless you've got an idea as to how neopeek variants work, it's suggested to stick with the XDAndroid builds...
Click to expand...
Click to collapse
I see what you say but honestly, right now, I'm looking for stability and performace, if you know that gingerbread build GBX0A have better performance (i supose that it's less stable because it's an alpha) than FRX06 i'll choose Ginger
Thanks again R^7Z.

[ROM] JXD S7100B ZCR v1_5 + setting [update 16 may]

this rom is only for S7100B
S7100B Zip's Custom Rom 1.5
the philosophy that underlies this first rom (do not expect miracles) is this:
If Android is not at 100% open, with the modifications of the house JXD, it is certainly less
for that cause this rom came WITHOUT any frills, so that the user choose what to have or not have on your console since the emu (not upgradeable) to app (not removable)
v1.5 changelog
-add theme faenza
-add advance task killer
-add my backup of vtl launcher settings
here is the v1.0 changes:
Based on the last official rom for JXD s7100b
- Removed ALL emulators series (since they could not raise it to update)
- Removed all serial applications to be added jxd (because there people who do not use FB Skype etc.)
- Removed serial launcher (really crappy)
-VTL.Launcher 1.6.5-added info link (ADW launcher launcher based on tablet-oriented
-FileManagerHD-added as a manager (much higher than 2 managers istallabili Series)
-Added superuser.apk
Changed clock font
changhed menu font
and that's it for now ..
The next thing I want to add (2.0) have a different boot animation, add a simple task killer, the theme for whiteware adw (if it works on VTL) default background, and another music video player
and then study how to make a backup of the settings of the launcher so who installs from scratch and restore my rom does not have to configure the home
A special thanks goes to SNESFAN and its forum: http://forum.openhandhelds.net/
Bitrider I create a custom rom for the first Android console,
to the reference point of android modding XDA
Android and the whole community
My community reference point for italian open source console users
www.OPENCONSOLE.it
BRIEF-Up Guide
1) get yourself a micro sd and put the files ZCR1.zip
2) make a backup of everything you need to save, (the new rom is really skinny)
3) Introduce the sd in the console
4) turn on the console by holding the keys POWER + MENU(the last button on the right of the 3 keys Android)
5) Wait and you will find in "bootloader)
6) Optional: make wipe of data/user
7) go to apply update from sd and start pressing the start / select
8) navigate and select ZCR1.zip and start the process
9) if all goes well should start installing the custom rom
10) when the process is finished you reboot system
you will come round to set up a launcher!
do not fear the next version will provide a backup of the settings in order to have everything already set
download: http://filesmelt.com/dl/ZCR1.zip
edit 16 may:
there is the 1.5 vers + my vtl launcher setting
download 1.5+ setting: http://www.openconsole.it/download/ZCR1_5s7100b.zip
extract on your sd card
follow the past guide
then go on vtl setting and restore setting

Thanks !
Hello,
First, thanks for your job !
i have linked your work on my french community openconsoles : http://caanoo.forumactif.org/t3185-rom-jxd-s7100b-zcr-v1#24052
Keep On the Good Work

Thanks a lot for this first ROM !
...microsd ordered, my s7100b will be flashed in few days ...

hello i know openconsoles france, and i know BAfelton
you tried out my rom?
i sold my s7100b, but before i made a last version of rom 1.5
-add advance task killer
-add theme faenza for adw (vtl is based on adw)
and i made a backup of my desktop configuration
ill post asap

00Zip00 said:
hello..
ill post asap
Click to expand...
Click to collapse
Thanks !
too bad you sold it, no more versions :/
I regret the lack of bluetooth ( no keyboard ..) but for the price ...

@ openconsoles france users
i read you made a screenshot of my rom
but i had problem to register account on that forum and i cant see it
could you post screenshot here?
Thanx

sorry i can't share them here...
"To prevent spam to the forums, ALL new users are not permitted to post outside links in their messages. After approximately eight posts
"
maybe this works for small link : goo.gl/2gzZV ?
...

ok thanx

updated my friends
post new screenshot if you can

link
filesmelt.com 7100b_ZCR_v1_5_+_setting.zip [/url]
link doent work anymore by chance is there something new out there for roms that i am missing?

Thank you and a question
First, I want to thank you for the ZCR 1.5 custom rom. It has really been great to have an alternate to the stock firmware. I've been trying to determine how to build my own custom rom for the JXD S7100B, but appear to be missing a step somewhere.
I've constructed a ROM and created the .zip image and then attempted to sign it with signapk.jar with the typical android testkeys. However, every time I attempt to update from sdcard zip file in the recovery menu, I'm greeted with an E:signature not verified error. I've tried to create my own certificates using OpenSSL and sign with those, I've compared the ZCR 1.5 custom rom to the latest firmware update from JXD, I've even tried to simply resign the ZCR1_5.zip image with the testkeys. All attempts have failed. I've scoured the internets for as much information as I can find and I can't see any difference between what I am doing and what I am reading. I've tried executing the signapk.jar under 32-bit XP and under 64-bit Windows 7 just on the off chance that there was a precision discrepancy between the two versions of java.
I'm at a loss and would like to know if you would consider outlining the process you use to sign the .zipped image? Do you use jarsign or signapk or some other tool? Are you signing with something other than the testkey certs?
Thanks,
jkgamer

http://www.multiupload.nl/IQP6BJUK15

jkgamer said:
...
I'm at a loss and would like to know if you would consider outlining the process you use to sign the .zipped image? Do you use jarsign or signapk or some other tool? Are you signing with something other than the testkey certs?
Thanks,
jkgamer
Click to expand...
Click to collapse
follow that guide
http://forum.openhandhelds.net/index.php/topic,47.msg118.html#new

Hey Zip,
no ICS update for S7100B coming from you?

i'v sold my s7100B but you can follow the custom rom scene in our site www.openconsole.it
and this is the topic whit all the custom rom for the console whit android:
http://www.openconsole.it/forum/viewtopic.php?f=25&t=869

how good does the JXD S7100B run n64 and psx games with this rom? im thinking about getting one.

not Perfect emulation, but most games run 80 % speed

hm, too bad. what about snes/gba ?

really well

I tried to upgrade on my s7100 and it gives me error
The error is as follows
E: error in /tmp/sideload/package.zip
Can someone help me ?

[APP] GooManager Beta official thread

The official app of Goo.im
We have spent a lot of time getting the server side changes in place to automatically parse our developer's rom files to grab data to make a functional OTA update system without the need for editing manifest files, or other tedious tasks. This is our attempt at creating a way for Android developers to simply publish material, and distribute it to the masses without any hassle.
This app is and will always be FREE!
General Features:
Ability to browse and search all of the files we have on our site, and download directly to your mobile device.
Receive OTA style updates from your favorite rom developers that we have hosted here.
CyanogenMod nightly build update support
Incremental (differential) rom updates for sequential builds
Flashing roms & installing recoveries
Update gApps packages
If you would like to sideload the app on your phone and avoid the market, we distribute the APK by itself, and also as a prebuilt repo maintained by solarnz(github.com/solarnz)
Are you a rom developer wanting to publish your work with our updating system?
To get your rom compatible with our updating system, you should make the appropriate changes to your build.props. For more information on this system, see the link below (sorry it's not clickable but i need 8 posts!)
goo.im/howto-rom-updating-via-our-app (For developers who are curious about how to modify their build prop file for compatibility with GooManager)
GooManager download page (To download the actual app)
KNOWN ISSUES:
DownloadManager API is buggy on Gingerbread
Installing OpenRecoveryScript on devices that do not support flash_image and do not have a /cache/recovery/command supported recovery will fail
FEATURE REQUESTS
Feel free to post them in this thread, but as my time is limited and Goo.im/GooManager's code is just something I do in my free time, there are simply not enough hours in the day to address them all
SHOUT OUTS
Chris Solarnz (For his java advice and contributions)
Mike Wielgosz (For contributing to the rom reordering and listing code)
Dees_Troy for all of his amazing work on OpenRecoveryScript and TWRP
eyeballer (For countless nights of helping test stuff, and awesome suggestions)
Shift (For the market icon)
Drmacinyasha (For all the testing / anal retentive bug reporting)
toastcfh (For helping bounce lots of ideas around)
EVERYONE ELSE I PROBABLY LEFT OUT!
FREQUENTLY ASKED QUESTIONS:
Why is _________ phone/tablet not supported?
In order to offer us flexibility without compromising other software such as rom manager premium, etc we did not want to rely on /cache/recovery/extendedcommands. At the time of developing the flash automation features, extended commands were licensed to RM only and it would have been illegal to use them. Since then, the license has changed, but we still feel it is the best direction to have our own since we can change it to fit our needs.
Why does this not work with my recovery i downloaded from Rom Manager?
CWM and CWM touch builds distributed by rom manager ONLY WORK WITH ROM MANAGER SO STOP ASKING!!!! #@$#@$#
Why are incremental updates only available for some roms?
Incremental updates are enabled on a per rom-device basis. Not all builds are even capable of this, since wipe can be required. It is at the discretion of the developer to toggle this as needed.
If you are a developer and would like to sign up: goo.im/signup
If you are a recognized developer, chances are you will get approved. (Note not all buildbox applicants are approved, and you may get only hosting)

Awesome. Used it to put TWRP2.1.2 easily on my ATT Galaxy Note.

It's Goo time! Been using this to distribute my unofficial cm9 nightlies for the touchpad and nook color for a while now and we've had nothing but positive feedback from users. Encourage your favorite rom developers to sign up

Not only is GooManager a great app, the whole ecosystem is, I believe, second to none.
A fantastic, simple system for developers to upload their ROMs and specify what device that ROM is for.
Easy for device users to find the ROMs that work with their devices.
Notifications of ROM updates for the ROM that you're using.
Easy download and installation of ROMs for devices with a supported recovery.
Differential updates - only flashes the files that have changed from one version to the next - smaller download, less wear and tear on your device, and quicker updates.

Thanks for this free app!
People don't have to donate to automatically check if there is an update to a CM nightly now.

for those of us who are not update-happy (although it is addicting) is there anyway to know from either this app or from Goo notifications in general whether an update requires a full wipe and then the requisite re-setting up of one's device?
I get a notification everyday for the new Gapps and for an update of my ROM (AOKP milestone 5 for Kindle Fire). I've ignored them because I'm just too lazy to spend an hour or two getting everything back up and running.

I've tried repeatedly to download CM9 nightlies and gapps via the latest market version of the app (2.06 I believe) and I always get a "download failed" message no matter if I'm on wifi or 3g. I've tried uninstalling and reinstalling, clearing cache, and clearing app data, and nothing seems to work. Is the download manager problem referenced in the OP a problem with ICS as well as GB? I have a Galaxy Nexus (toro) using BAMF Paradigm 1.25 in case that info makes a difference.
Sent from my Galaxy Nexus using Tapatalk 2

lanceman5000 said:
I've tried repeatedly to download CM9 nightlies and gapps via the latest market version of the app (2.06 I believe) and I always get a "download failed" message no matter if I'm on wifi or 3g. I've tried uninstalling and reinstalling, clearing cache, and clearing app data, and nothing seems to work. Is the download manager problem referenced in the OP a problem with ICS as well as GB? I have a Galaxy Nexus (toro) using BAMF Paradigm 1.25 in case that info makes a difference.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Please get a logcat. It will give you a reason why the download failed. If you are on linux, adb logcat | grep GOO
There seems to be issues with some people or devices that I have yet to narrow down. If you can replicate this bug consistently please contact me on freenode IRC in the #goo-inside.me channel and i'll try to look into it. My time is limited these days hunting a bug i can't reproduce so despite the needs of the community -- work and life comes first!

peters4n6 said:
for those of us who are not update-happy (although it is addicting) is there anyway to know from either this app or from Goo notifications in general whether an update requires a full wipe and then the requisite re-setting up of one's device?
I get a notification everyday for the new Gapps and for an update of my ROM (AOKP milestone 5 for Kindle Fire). I've ignored them because I'm just too lazy to spend an hour or two getting everything back up and running.
Click to expand...
Click to collapse
It is up to the developer to state whether it requires a wipe in their changelog. Generally nightly builds will not require a full wipe though

thereals0up said:
Please get a logcat. It will give you a reason why the download failed. If you are on linux, adb logcat | grep GOO
There seems to be issues with some people or devices that I have yet to narrow down. If you can replicate this bug consistently please contact me on freenode IRC in the #goo-inside.me channel and i'll try to look into it. My time is limited these days hunting a bug i can't reproduce so despite the needs of the community -- work and life comes first!
Click to expand...
Click to collapse
I have no clue what I'm looking at, but here is the logcat of a download attempt. At least I hope this is what you meant.
http://db.tt/bpWD2LWo
Sent from my Galaxy Nexus using Tapatalk 2

Anybody can explain how to use with Galaxy note CM9?
I'd li ke to flash nightly in diff mode. First of all do I need to unistall cwm and install the open recovery?
Somebody has already tried?
Inviato dal mio GT-N7000 con Tapatalk 2

I like this app man, Good work...

Great job, it's nice to see such a useful app for no cost.

Raistlin82 said:
Anybody can explain how to use with Galaxy note CM9?
I'd li ke to flash nightly in diff mode. First of all do I need to unistall cwm and install the open recovery?
Somebody has already tried?
Inviato dal mio GT-N7000 con Tapatalk 2
Click to expand...
Click to collapse
You simply install goomanager, hit menu -> install openrecoveryscript which will DD over the image to your recovery partition for twrp 2.0.
As far as differential patches go, the feature is still being enabled on a per-rom basis while I make sure there are no bugs CM nightlies in general do not have it enabled yet but some devs do.. the list will improve but i don't want to make any big changes until I am 100% positive the incremental system is perfect

I'm having quite a few failed downloads recently via goomanager, anybody else?
Not sure if this is device related issue or they app/appserver etc.
Using GTAB P1000 btw.

This thing is a piece of crap if you are trying to download on 3g.

superstargoddess said:
This thing is a piece of crap if you are trying to download on 3g.
Click to expand...
Click to collapse
Please keep this conversation constructive. If you have anything relevant to resolving the issue go ahead and post it but complaints are not helpful. If you have a failed download, paste a logcat or simply the line which gives a numerical code for why the download failed. The tag will be "GOO"
We are aware of downloading issues but since this is just a project we do strictly on free time for no profit, we can only get what we can afford which is why we are on all used hardware and frequently have hiccups with our distribution boxes. We're looking into getting more in the rotation to lower the load on the servers but there are not enough hours in the day or dollars in the bank account to handle it right away. We're looking into financing some sexy new servers from dell if we can get approved

thereals0up said:
You simply install goomanager, hit menu -> install openrecoveryscript which will DD over the image to your recovery partition for twrp 2.0.
As far as differential patches go, the feature is still being enabled on a per-rom basis while I make sure there are no bugs CM nightlies in general do not have it enabled yet but some devs do.. the list will improve but i don't want to make any big changes until I am 100% positive the incremental system is perfect
Click to expand...
Click to collapse
Ok so I prefer to wait...I have no rush.
But it is safe to install the openrecovery? I mean 0% of brick over n7000 running CM9
Inviato dal mio GT-N7000 con Tapatalk 2

thereals0up said:
Please keep this conversation constructive. If you have anything relevant to resolving the issue go ahead and post it but complaints are not helpful. If you have a failed download, paste a logcat or simply the line which gives a numerical code for why the download failed. The tag will be "GOO"
We are aware of downloading issues but since this is just a project we do strictly on free time for no profit, we can only get what we can afford which is why we are on all used hardware and frequently have hiccups with our distribution boxes. We're looking into getting more in the rotation to lower the load on the servers but there are not enough hours in the day or dollars in the bank account to handle it right away. We're looking into financing some sexy new servers from dell if we can get approved
Click to expand...
Click to collapse
Sorry, was just being honest! ^^
Edit: I'd totally donate if it were reliable on 3g!

superstargoddess said:
This thing is a piece of crap if you are trying to download on 3g.
Click to expand...
Click to collapse
Then complain to your 3G provider dumbass.

[ROM] iPioneer Slim 10c v0.1 for LGV521 - Rooted, busybox, init.d, debloated, etc...

ROM Ipioneer Slim 10c v0.1
A light, clean & faster rom!!!
Disclaimer:
/***
* Your warranty is now void (and I'm sure it was void before this process).
* I am not responsible for hard or soft bricked devices, boot loops, dead or corrupt sd cards, strange behavior or you getting a heart attack 'cuz your youtube app is not working properly.
* YOU and only YOU are choosing to make these modifications, do not blame on me.... I will just ignore you.
***/
iPioneer Slim 10c v0.1 is a light, clean and fast custom rom designed for the Lg G Pad X 8.0 (T-Mobile variant only) and it's aim is to become a replacement for the default system of this device.
iPioneer Slim 10c v0.1 it is light because it only takes 519.8Mb of disk space which is a big difference when you compare the 1.2Gb of a stock rom, it is clean because it only contains the essential apps to make it work properly and it is faster because the whole system have been 100% optimized.
iPioneer it have been designed with the User Freedom in mind, it only provides you with the basic OS so you can do what you need to do on top of that.
Features:
Based on stock (10c)
Rooted
Busyboxed
Init.d Support
Extremely debloated (very serious)
Deodexed
Zipaligned
Nova as default launcher
Installation instructions:
Download the rom to your desire location (link to download to the end of this post).
Boot into Twrp recovery and do a standard wipe (factory reset).
Install the downloaded rom .zip.
Reboot the device.
Be patient, is going to take more time than a regular stock rom to boot into the system, at first is going to be stuck at T-Mobile logo but after few seconds is going to enter into App Optimization mode and after that you will be able to setup your system.
Enjoy it.
First things to do after you install this rom:
Add your google account (if you didn't complete that step at the first setup).
Download your favorite app manager (Rom Toolbox, Titanium, etc.).
Freeze the application called App Updates in order to stop the system update beacon for OTA. I removed 3 core apps in order to stop OTAs but it seems to be very integrated with the system, there is no way I can remove it from the rom without breaking the system. This is the most practical way to my knowledge right now.
Optionals things to do after you install this rom:
You can uninstall Nova Launcher if you want as is not part of the system apps, but before you need to install your favorite launcher. If you don't install another launcher and remove Nova you will have a broken system and most likely you'll have to re-flash the rom.
On purpose bugs and missing options:
On purpose bugs are bugs that comes when you remove a functionality from the system but it can not be removed from a third party component, example: LG VPN app it has been removed but the options remains in the Settings of the device and when you tap that option you will provoke a crash event, the way to resolve this is to decode the third party component (very difficult) or reinstall the missing part (in this case the LG VPN app).
iPioneer Slim 0.1 it comes without some apps that can not be removed from the system setting options, this is like that because I believe that these apps are not necessary for all people, if someone need them they can be downloaded/replaced from the Play Store or I will provide a flashable file with these apps so you can install them.
On Purpose bugs (located at settings):
From the Share & Connect menu:
File Sharing that contains BLE and Android Beam doesn't work, package SmartShare it has been removed.
Media Server (DLNA) doesn't work, package SmartShare that also contains SmartShare.MediaServer it has been removed.
Lg Airdrive doesn't work, package LGAirDrive & LGAirDriveSettings were removed.
From More>VPN menu:
LG VPN doesn't work, package VpnClient_LG it has been removed. Basic VPN it works.
From Display menu:
Home screen doesn't work, packages LGHome, HomeSelector, LGHome_Theme_Optimus, com.lge.launcher3, com.lge.launcher2.theme.optimus were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.​
Missing options (located at settings):
Smart Cleaning not present, package LGSpringCleaning it has been removed.
Cloud (cloud integration in settings) not present, package CloudHub (maybe dependant on SmartShare package) it has been removed, please also note that this cloud integration it was integrated on the stock File Manager, so... if you want a full integration of the Cloud service on settings maybe you will have to install the stock File Manager provided by LGFileManager package.
From Backup & reset menu:
LG Backup is not present, packages LGBackupLauncher and LGBackup were removed.
From About tablet menu:
Update Center and its content (App updates & System updates) is not present, packages com.lge.appbox.client (app updates), com.lge.updatecenter & LGUpdateCenter (main menu for updates) were removed.
If you need these options to be available on your system just download these app on Play Store if they are available or just wait until I have ready the System Apps flashable zips.​Flashable zip with system apps:
Coming soon when I have a free time.
What to do if you get the OTA notification:
Freeze the app called App Updates with your favorite app manager.
With your favorite file manager go to /cache and delete the update.zip (the downloaded ota).
Tap on Restart & Install button on OTA pop-up, the pop-up it will start counting to 0 in order to restart but your device won't restart because there are 3 core apps removed from this rom plus 1 app that you just disabled (all these 4 app controls the OTA), the notification is just gonna disappear, push recent button and clear the ota pop-up window.
Bugs Report:
If you find a bug in this rom just notify me about that in this thread, please, just use the title as "Bug Report" so I can pay close attention to that, my time is very limited. Thank you.
Feature Request:
If you want a feature to be added into future revisions of this rom just notify me about that in this thread, please, just use the title as "Feature Request" so I can pay close attention to that, my time is very limited. Thank you.
More info:
-------------------------------------
Device: Lg G Pad X 8.0
Model: LGV521
Code Name: b3
Carrier: T-Mobile
Android version: 6.0.1
Security patch level: 2016-07-01
Software version: V52110c
Link: https://www.androidfilehost.com/?fid=385035244224403624

Screenshots:
Default View: (sorry guys, I was not able fix Nova in order to show an organized and clean layout by default).
Default App Drawer: remember this is an extremely debloated rom, only the most basic core apps remains.
Settings view, yes some options are not present, read above about this.
Software info.

Reserved 2...

For some reason this post doesn't show up on ET page: lg-g-padx
Too bad, a lot of people won't be able to see this rom, but I can do nothing.
If someone knows an admin who can fix this issue please make mention of this post to him. I would do it but I don't have the time to.
Thank you.

Some screenshots added on post #2...

How fast does it run compared to the stock rom?

Munns86 said:
How fast does it run compared to the stock rom?
Click to expand...
Click to collapse
How fast it can go is a subjective matter:
It will depend on hardware lifetime span (how you use it and how other people use this tablet).
It will depend how much apps and content you put in it (the more things you download the more slow android is gonna be, this is kind a Swap area).
I did not do a benchmark, when I declared that is faster than a stock rom is because that speed response enhacement it comes based on the Deodex and Zipalign process. It can be or maybe not noticeable to your eyes but based on deodex and zipalign process is for sure that is faster than an odex and not-zipaligned rom.
The best answer is that you need to try it on your own and see the difference.
Sent from my LG-H918 using Tapatalk

Poll added at the beginning (not visible in tapatalk or xda app).
Please only select the apps that you really need or you really think that should comes with the next revision of iPioneer Slim rom.
This will help me to build a better version with features that users needs.

C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!

xtremelora said:
C'mon guys... only 3 users have use the poll...
I need more data background in order to release a new version of the Slim line version (may be the last one).
All V521 users please contribute with this.
Right now I'm testing a new build that it seems to have success stoping ota download and notification & I have removed even more bloat background packages.
As of today I start the syncing process of CyanogenMod for our device, so all I ask is that V521 users vote in the poll so I can build and release what I think it would be the last Slim version (iPioneer Slim 0.2) based on users needs.
Once I start the developtment with CM I will not pay attentions to the Stock & Slim version until I finish with what is gonna become iPioneer CM 13.
Thank you for your attention guys.
BTW: sorry for my english, I try so hard to write all this in a good way. Arriba Mexico Papa!!!
Click to expand...
Click to collapse
The reason is that the xda app can't see the vote going on.
Personally, I will be excited to see a cm/aosp custom build, which will sure draw much more attention.

googlephone said:
The reason is that the xda app can't see the vote going on.
Click to expand...
Click to collapse
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...

xtremelora said:
But it is visible and operable through a normal web browser in android: http://forum.xda-developers.com/lg-...ioneer-slim-0-1-lg-g-pad-x-8-0-t3513030/page1
Or the option LOAD IN BROWSER in xda app and WEB VIEW in tapatalk...
Click to expand...
Click to collapse
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.

googlephone said:
Another reason is not many users are interested enough in a slimmed stock rom. The benefits of a slimmed stock rom may include less system storage usage. But the free uped system storage is not accessible for users to use as data storage anyway. Speedwise, I wouldn't expect noticeable improvement from a slimmed stock rom. As a result, the benefits of a slimmed stock rom is not enough to draw users' attention or interest.
I am a flashholic but I actually not interested in slimmed stock at all because I already have root.
I personally advise you to not spend too much time on modified stock rom.
I appreciate your work and look forward to your future possible cm rom, which I will definitely try it out and will draw many g pad x users here. And don't forget there is a bounty for custom roms like cm.
Click to expand...
Click to collapse
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.

xtremelora said:
You are right about working in a stock version. The reason why I'm doing this is because we all know that CM most of the time has bugs, bluetooh problems, camera issues, data conectivity troubles, etc...
Sooooo, if the version of CM I'm going to compile it results with many bugs there is gonna be the option to go back to stock slimed or stock bloated.
I can build a CM verion but Im not the kind of guy who inverts his time in CODE MODIFICATION, so hopefully the build it comes with no bugs at all or at least no major bugs.
The other alternative is that I can sync, compile and build and one more guys can do the bug fixes.
Click to expand...
Click to collapse
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.

Munns86 said:
That would be great! I think if you took a poll most people would prefer a CM build to a slimmed down stock build.
Click to expand...
Click to collapse
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.

xtremelora said:
Yeah, I know that. Wish me luck.
Right now I'm stuck trying to get the Blobs for this device and compiling the kernel so I can build the CM recovery, once I have the recovery done I can start compiling CM and start testing.
I'm trying to by pass the kernel (as is not need it right now to build the recovery) but for some reason the system is demanding an standard and working kernel... weird...
But honestly speaking is gonna take lot of time. So be patient guys.
Click to expand...
Click to collapse
There is already a TWRP recovery for v521. Why you need to compile cm recovery?

googlephone said:
There is already a TWRP recovery for v521. Why you need to compile cm recovery?
Click to expand...
Click to collapse
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk

xtremelora said:
Ik, is just a prebuilt because our device doesnt have a device tree or structure already, so making this at first is gonna help me to buil the cm zip.
Is not need it if a device tree already exist but not in this case, just see it like a pretesting of code for this device.
When I try to compile this recovery things are gonna break so you get info of what is missing, what you need, log, etc... So you fix everything you can in this step and then you build the cm.zip in a better way (less issues).
Sent from my LG-H918 using Tapatalk
Click to expand...
Click to collapse
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.

shabbypenguin said:
https://github.com/Shabbypenguin/android_device_lge_b3
device tree has been around for a while, it obviously will need some renaming to work for cm source but its a good foundation to start with.
Click to expand...
Click to collapse
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.

xtremelora said:
These are your device tree for twrp 4 b3 right?
Let me see if I can work with that, I was almost done building the cm.recovery and fixing some boot.img issues but if I can take your files that would save time.
Did you forked that device tree or u just build it from scratch?
If you forked them, from what device?
I was thinking on pulling the v500 just to figure out some sort of missing info I havent been able to catch from ramdisk.
Click to expand...
Click to collapse
i built it from scratch, id be careful looking too much at the v500, it's a snapdragon 600 SOC which is very old and is a quad core. the 615 in the g pad x is octacore and much newer. even the ramdisk is going to have big differences in how its handled.