Hello fellow old friends! I've brought something new and cool to this old forum(slow to keep up with the latest stuff).. And exremely cool for guys with non-working sd slots; You can now easily flash roms using "ADB Sideload" feature of TWRP.. bla bla...
UPDATE - 12MAR2013 - TWRP 2.4 Build taken down due to huge size which can't fit in our recovery partition.. Currently trying to slim it down..
Today, I felt like getting my ubuntu up and doing some fun stuff like old day. There! I decided to get another build of TWRP. I couldn't really test is as my bros phone is nowhere to be found . However, since I used the exact same source as the first build it should work just fine. Anyone willing to try their luck is welcome and appreciated..
{
"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"
}
Introduction:
Team Win Recovery Project 2.3, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and loading it with the standard recovery options, then added a lot of our own features. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Key Features:
Touchscreen driven with real buttons and drag-to-scroll
XML-based GUI that allows full customization of the layout – true theming!
Settings are saved to the sdcard and persist through reboots
Ability to choose which partitions to back up and which to restore
Ability to choose to compress backups – now with pigz (multi-core processor support for faster compression times)
Onscreen keyboard
Decryption of /data
Easy selection of internal/external storage
See changelog below for 2.3 features
What's new in 2.3:
-Rebased onto AOSP Jelly Bean source code
-Rewrote backup, restore, wipe, and mount code in C++ classes for easier maintenance going forward
NOTE: backups from prior versions of TWRP are still compatible with 2.3
-ADB sideload functionality from AOSP is included in 2.3, see this link for more info
-Re-wrote fix permissions entirely in C++ and runs in a few seconds instead of a few minutes (thanks to bigbiff)
-Improvements to zip finding in OpenRecoveryScript (should be a lot fewer GooManager automation issues)
-Faster boot times
-Added charging indicator while in recovery (only updates once every 60 seconds)
While this update may not bring a host of new must-have features, this update is a significant re-write of much of the core TWRP code. AOSP Jelly Bean recovery source moved to mostly C++ code and now all of the "TWRP" code is fully rewritten into C++ as well. Now that we've laid this groundwork, we're in a much better position to pull in future AOSP recovery updates as well as implementing more great new features.
Since TWRP 2.3 is based on AOSP jelly bean sources, TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder.
What's new in 2.2 & 2.1:
On-screen keyboard! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
Name new backups before creation and rename existing backups
Rename files and folders in the file manager
Pseudo-terminal emulator
Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
Simplified XML layout support between resolutions
Added dual storage selection radio buttons to zip install, backup, and restore pages
Improved zip install compatibility
Updated update-binary source code
Numerous small bug fixes and improvements
Zip queuing as seen in TWRP 1.1.x is back
Slider control (swipe to confirm most actions aka swipe to wipe)
Lockscreen (with slider to unlock)
Basic file manager (copy, move, delete, and chmod any file)
Added support for devices with /data/media (most Honeycomb tablets, new ICS devices like Galaxy Nexus)
Displays sizes of each partition in the backup menu
Added listbox GUI element (currently used for listing time zones)
Updated stock XML layouts to be more consistent and easier to port to different resolutions
XML layout files are significantly smaller
Partitions available backup are more accurate for some devices
Removed unneeded error messages (/misc errors, unable to stat sd-ext, etc.)
Fixed a bug with blkid detection code
Fixed bug where a blank line was inserted between every line of text during zip installs
Fixed a bug during zip installs where an invalid zip would cause TWRP to get stuck in the zip install
Added setting for themers to toggle simulation mode to make theming easier
New devices added - Galaxy Nexus GSM & CDMA (preview only, manual install), Acer Iconia Tab A500, HTC Vivid, Motorola Defy
Added support for .jpg images in the theme engine
Changed images for stock tablet theme - makes tablet builds about 500KB smaller
Removed unneeded non-GUI images from GUI - makes all builds about 100KB smaller
In addition to the above new features, TWRP 2.2 features a scripting engine that allows an app to send commands to the recovery for the recovery to perform during startup. We call this scripting engine OpenRecoveryScript. This engine will be put to use immediately in the GooManager app. GooManager will be able to install recoveries automatically for most supported devices. The app will also let you choose to install multiple zips from within Android, wipe cache & dalvik, and run a backup.
Theming:
Information on TWRP 2 Theming - http://teamw.in/project/twrp2themers
Known Issues: (General TWRP issues)
CWM backups are not compatible - please make a fresh backup in TWRP as soon as you have flashed it
Issues I found:
-UMS doesn't work
i installed but couldnt install any zip's or back ups looks really good tho...nice 2 see summit different :victory:
Congrats bro on your first source build!!! :thumbup:
shmokeyuk said:
i installed but couldnt install any zip's or back ups looks really good tho...nice 2 see summit different :victory:
Click to expand...
Click to collapse
Ill check install from zip. But backup was working good..
rishabh.raj37 said:
Congrats bro on your first source build!!! :thumbup:
Click to expand...
Click to collapse
actually not my first.. I'm building aosp for my nexus
Sent from my Galaxy Nexus using xda app-developers app
Haha grats i would count this as your first source build AOSP for maguro is officially supported and not much needs to build it just select the option
-Grift- said:
Haha grats i would count this as your first source build AOSP for maguro is officially supported and not much needs to build it just select the option
Click to expand...
Click to collapse
Well, yeah you have a point.
Sent from my Galaxy Nexus using xda app-developers app
Great, thank you! but where can I find "erase battery stats"? It's gone from the wipe menu!
Punkiderma said:
Great, thank you! but where can I find "erase battery stats"? It's gone from the wipe menu!
Click to expand...
Click to collapse
Ill see that when my bro comes back home...
XiproX said:
Ill see that when my bro comes back home...
Click to expand...
Click to collapse
Confirmed: can't install zips
Thanks anyway! I'll be waiting for further verions =D
Well thats weird I just checked now and it looked like it flashed AOSP 1.4 successfully.. Ill check again after a full wipe..
And yes battery stats button is gone. Have no idea why.. I had just disable sd_partitioning to lower recovery image size to fit our phone. I dont remember disabling anything else.. Why do you even need wiping battery stats?
did a full wipe including system and flashed:
1.AOSP GB 1.4 -- FLASHED
2.TX-MIUI-SDSL -- FLASHED
3.Grifts CM10 build -- Took longer than the previous 2 roms but FLASHED (I was even gonna make a battery pull cause I thought it was doing nothing, then just saw the final show_progress)
4.IceCreamSwift RC2 -- FLASHED
As you can easily see, it has no problem flashing android 2.3.7, 4.0.4, 4.1.2...
if you still cant flash, please try some other rom and report.. Thanks1
XiproX said:
did a full wipe including system and flashed AOSP 1.4 and successfully booted..
Ill be testing these roms and report..
1.AOSP GB 1.4 -- FLASHED
2.TX-MIUI-SDSL -- FLASHED
3.Grifts CM10 build -- Took longer than the previous 2 roms but FLASHED (I was even gonna make a battery pull cause I thought it was doing nothing, then just saw the final show_progress)
4.Miro's Oxygen
Click to expand...
Click to collapse
miro has oxygen ? you mean 4.0 that is based on ice cream swift ?
smileydr0id said:
miro has oxygen ? you mean 4.0 that is based on ice cream swift ?
Click to expand...
Click to collapse
yeah, but I think my bro deleted that rom from sd. so Im gonna try flashing IceCreamSwift RC2
btw, I think it was based on AOSP not CM
XiproX said:
yeah, but I think my bro deleted that rom from sd. so Im gonna try flashing IceCreamSwift RC2
btw, I think it was based on AOSP not CM
Click to expand...
Click to collapse
Can you explain me how did you ported it ? i wanna try to port it on my xperia U
smileydr0id said:
Can you explain me how did you ported it ? i wanna try to port it on my xperia U
Click to expand...
Click to collapse
if its TWPR you are asking, I had already got my build environment set up following this, then it was really easy to build TWRP;
you can simply follow those instructions there for ubuntu, udev rules, and other tools like java, then skip Gnex stuff, use the same process for getting repo commands and instead of initializing AOSP source initialize CM source(https://github.com/Cyanogenmod -----...). After getting the cm repo follow The official TWRP guide. NOTE: Youll need device files for your phone. I hope someone has an open-source project
Good Luck! feel free to pm if you need something. And in case of any problem with building twrp or other twr related make sure you check their freenode you'll get your answer faster than you would on the guide thread..
Again, if you still cant flash roms, please briefly explain what happens and provide a log (Advanced>Copy Log to SD) Thanks!
XiproX said:
Again, if you still cant flash roms, please briefly explain what happens and provide a log (Advanced>Copy Log to SD) Thanks!
Click to expand...
Click to collapse
My problem is not flashing roms (didn't tried either), is flashing mods (apks, fixes, and so on). With those installation fails always and with the previous version of TWRP they install correctly
coto39 said:
My problem is not flashing roms (didn't tried either), is flashing mods (apks, fixes, and so on). With those installation fails always and with the previous version of TWRP they install correctly
Click to expand...
Click to collapse
it could be because of TWRP 2.3 being based on AOSP jelly bean sources, "TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder."
if there was a particular reason then it would affect ROM flashing too. (I guess).. I think you should try to flash a not working patch with the above provided update-binary..
XiproX said:
it could be because of TWRP 2.3 being based on AOSP jelly bean sources, "TWRP now uses recovery API 3 instead of 2. Some zips may no longer work if the developer is using an out-of-date update-binary. This API change should not be a problem on newer devices, but older devices will probably encounter several zips that need to be updated. If needed, you can try using this update-binary that was compiled with current sources. It goes in your zip file in the META-INF/com/google/android folder."
if there was a particular reason then it would affect ROM flashing too. (I guess).. I think you should try to flash a not working patch with the above provided update-binary..
Click to expand...
Click to collapse
That's right I also had that issue but it was because of older binaries.
But I do have another issue, this version backs up my rom without problem but when it comes to restore, i just get bootloops. The thing is that apparently there are no errors restoring the backup. I have TWRP 2.1.4 and 2.3.1.1 flashable zips for when I need to restore
Are you aware of this XiproX?
Related
[RECOVERY] TWRP 2.2.0 with on-screen keyboard! [2012-07-12]
Team Win Recovery Project 2.2, or TWRP2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.0):
- On-screen keyboard in recovery! -- supports long press, backspace repeat, and swipe left deletes everything left of the cursor
- Name new backups and rename existing backups
- Rename files and folders in the file manager
- Pseudo-terminal emulator
- Support decrypting an encrypted data partition on Galaxy Nexus (enter password using keyboard)
- Backup archive splitting -- allows backup and restore of data partitions larger than 2GB
- Simplified XML layout support between resolutions
- Added dual storage selection radio buttons to zip install, backup, and restore pages
- Improved zip install compatibility
- Updated update-binary source code
- Numerous small bug fixes and improvements
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 30 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.
Changelog
Changelog:
2012-07-12 v2.2.0
See TeamWin's TWRP page for changelog.
2011-10-07 v1.1.1
See TeamWin's TWRP page for changelog.
2011-08-17 v1.0.3.1
Bug Fixes:
- Fixed issues with efs backup/restore - now fully tested
2011-08-05 v1.0.3
New Features:
- Added timezones that should cover everyone
- Added twrp spam feature (twrp settings)
- Added fix permissions (advanced menu)
- Added wipe cache and dalvik into Flash Zip menu
- Added copy recovery.log to /sdcard (advanced menu)
- Added output spam/no spam to restores
- Added mke2s prebuilt to /sbin
Bug Fixes:
- Fixed SD-EXT issues, (no partition SD-EXT features yet)
- Fixed EFS partition issues
- Changed the way we do backups on mtd devices, which should fix any boot partition issues
(we suggest making new backups if you have an mtd device, EVO4G,NS,NS4G)
2011-08-01 v1.0.2
Bug Fixes:
- Fixed SD-EXT issues
- Added Format SD-EXT into format menu
- Removed GAPPS support, CM7 automatically backsup and restores if you already have GAPPS installed. If you don't, just flash GAPPS zip
- Fixed issue where when flashing a rom, rebooting brings you back to recovery. Auto reboot after successful flash should work great now!
- Rearranged the format menu
2011-07-29 v1.0.1 - Initial release on Nexus S
FAQ:
How to install with Fastboot:
Download the fastboot binary for your computer and OS
Connect your phone and boot it into fastboot
Run fastboot with the command
Code:
fastboot flash recovery path/to/recovery-twrp-shooter-1.0.1.img
What's Fastboot?!
Check here for further information on fastboot and how to obtain it: http://forum.xda-developers.com/showthread.php?t=895545. Thanks to zephiK for directing me to it.
Moar winning...
Sweet. Trying on 4g now
snandlal said:
Sweet. Trying on 4g now
Click to expand...
Click to collapse
This is for the Nexus S, not the 4G. We are still working on making it compatible with the NS4G.
yes i know. Its in the nexus s section. Thanks for this. Seems to work great on 4g model. Can't wait for the full-blown 4g version. Great Job!
snandlal said:
yes i know. Its in the nexus s section. Thanks for this. Seems to work great on 4g model. Can't wait for the full-blown 4g version. Great Job!
Click to expand...
Click to collapse
sweet! thanks for the feedback!
screenshot please..
simms22 said:
screenshot please..
Click to expand...
Click to collapse
but of course! thanks to ffolkes for grabbing these:
{
"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"
}
shift_ said:
but of course! thanks to ffolkes for grabbing these:
Click to expand...
Click to collapse
thank you very much
Very nice to see this come out, looking forward to trying it out. Not to sound ungrateful but I have been hoping for a recovery that lets you name the backups rather than have them time stamped. Call me lazy but I flash back and forth between roms enough that keeping then straight just by the date and time is tough for an old fart like me...and yes I know rom manager can rename them for me but like I said I'm lazy...
Great work guys, thanx for your contributions to android life
Awesome guys, very smooth and much better looking than CWM recovery, a keeper indeed.
Edit: For those curious, it also works fine with the Reboot to Recovery feature build into many custom roms, such as CM7, Oxygen etc.
Thanks shift and teamwin, always good stuff.
Sent from my Nexus S 4G using XDA Premium App
Just tried it out and compared it to Clockwork Recovery. Seems a lot cleaner, definitely love how you can assign a folder for flashable .zips.
I think I'll keep this over my Clockwork Recovery 4.0.0.2 looking forward to future updates.
OK I took the plunge using the other teamwin contribution of the day(you guys rock!), the app for flashing img files like kernels and recoveries and it works fine so far on my ns4g. I especially like how I can mount usb in recovery and get at my files, never had any luck with any previous recoveries allowing it, even ones that had the option. Haven't tried all the options just yet but I am sure to find something to flash around here requiring a backup or two....let me dig around...
I too flashed it looks nice, love the options, thanks teamwin
Sent from my Nexus S 4G using XDA Premium App
raiderep said:
Very nice to see this come out, looking forward to trying it out. Not to sound ungrateful but I have been hoping for a recovery that lets you name the backups rather than have them time stamped. Call me lazy but I flash back and forth between roms enough that keeping then straight just by the date and time is tough for an old fart like me...and yes I know rom manager can rename them for me but like I said I'm lazy...
Great work guys, thanx for your contributions to android life
Click to expand...
Click to collapse
That would mean we'd have to create a software keyboard type interface which might bloat the recovery. As you said you could always use rom manager, or even mount the sdcard as a usb drive and change the folder name manually.
I knew for Shinzul my Ninzul was involved.
Uncle Jimmy says hello
AssassinsLament said:
That would mean we'd have to create a software keyboard type interface which might bloat the recovery. As you said you could always use rom manager, or even mount the sdcard as a usb drive and change the folder name manually.
Click to expand...
Click to collapse
Thats why I'm just a dreamer and not a doer lol...you guys know the limits and I guess I just don't see them...awesome work either way guys
One thing I could use some help with though, I tried to flash deck's latest and it gave me a status 7 error, just wondering if its because this isn't official for the ns4g or not...and I can report that it did a successful backup and restore for me
{
"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
I'm not responsible of your Incorrect flashing of a recovery that can brick your device! Do not install this recovery if you don't know what you are doing with your phone.
This is latest TWRP build for LG P500 which have full touch support.
Dees_Troy said:
Team Win Recovery Project 2.2, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG (for 2.2.2.0 compared to 2.2.0.0):
Mostly bugfixes:
Significantly improved sd-ext handling (ext partitions on sdcards)
Changes to kinetic scrolling in file selectors
Fixed a problem with using periods in backup names
Fixed problems in XML layouts with mounting system and USB storage
Fixed a problem with unmounting a partition before formatting during restore
Add Jelly Bean decrypt support
Updated 320x480 theme to match others (thanks to Llewelyn)
Improve "symlinking" of /data/media to either /sdcard or /emmc
Added sanitizing of device IDs for invalid characters (thanks to bigbiff)
Fixed free space calculation when switching backup devices on /data/media devices
Fixed a problem with using OpenRecoveryScript to create a backup without providing a backup name
Click to expand...
Click to collapse
This Recovery for :
Who tired of scrolling through huge lists of files in ClockworkMod with the volume rocke,
want a recovery with a graphical interface that can controlled using the touchscreen
ScreenShots:(from my P500)
FEATURES:
FULL TOUCH SCREEN SUPPORT
Graphical touchscreen interface with buttons and drag-to-scroll!
Ability to save custom recovery settings
New: Integrated Terminal Emulator
Easy one-button cache & dalvik cache clearing after an installation
Default partitions to back up
Default zip folder location
Default color theme
Default Time Zone
Zip Signature Verification
Zip md5 Verification
Compressed backups that can save you up to 50% disk space
New: Custom names for backups, rename and delete backups inside recovery
Ability to flash multiple zips in one go
Ability to select which individual partitions to backup, and restore.
Ability to choose compression or no compression backups.
Ability to auto restore GAPPS on zip flash
Ability to auto reboot after successful flashes
Battery Level and Timestamp
File Manager that allows you to move, copy, delete and rename files and change their permissions
Reboot into bootloader
ADB support
Detailed logfile
Themeable
Download links
2.2.2.1
1) download zip file and place on your root of sd card
2) reboot you phone into recovery mode and flash this zip file
3) enjoy twrp recovery
Common FAQ
Can I restore my CWM/Amon ra backups on TWRP?
No you can't. but other way is: flash CWM, restore a backup, flash TWRP, create new backup, repeat.
Click to expand...
Click to collapse
BUGS:
I have tested install,wipe and backup and it's working good, If you have found a bug post here but don't post common twrp bugs.
Credits:
- Dees_Troy and other all Twrp team - for making this recovery
- Cyanogenmod team - used cm7 device folder to compile this recovery
Just flashed it. Nice job!
No bugs so far, but don't take my word for it since I only played around with it for five minutes.
Noticed so far:
1. Very quick to exit recovery and reboot into the system (less than a second)
2. A lot of customizations and nice interface
I love it! Finally someone did.
The other day, I was thinking of compiling CWM 6 Touch from source but I guess I don't need it now
Real nice, just installed and take a fast look on it. Will test more later. Thanks:good:
been waiting for this. I had this on my a100 but i couldn't find it on my p500
finally this day has come
this should be in original development
hey it rebooted in the middle of a backup(that backup was like 200 mb). now it can't backup anymore. it can't create folder sdcard/ (text cuts off)
edit: reflashing recovery. rebacking up. seeing what happens
wierd... its says my sd-ext is 0 mb. i use link2sd and i definitly have stuff on my sd-ext
Edit: Now everything works. thanks...
It say's on recovery that it's 2.2.2.1.. And thank's a lot to this wonderful recovery..
Sent from my LG-P500 using Tapatalk 2
But how to wipe battery stats from recovery??
carrthee89 said:
But how to wipe battery stats from recovery??
Click to expand...
Click to collapse
it don't have that option
Thanks dude i am big fan of TWRP and only use twrp recovery.now time to update.
[Q] possible theme blue??? thanks by Notonlyeyes
Just a little bug here, there are some overlapping text specially when backing up..
Sent from my LG-P500 using Tapatalk 2
plzz....support multirom
thanks
dnle71 said:
Just a little bug here, there are some overlapping text specially when backing up..
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
This is due to our phone's screen size. I guess Ron can fix it while building, it needs some xml edits
Is it as stable as CWM 5.0.2.0? What are the added features? Need your suggestions as I never used any other recovery other than CWM.
Sent from my LG-P500
myawan said:
Is it as stable as CWM 5.0.2.0? What are the added features? Need your suggestions as I never used any other recovery other than CWM.
Sent from my LG-P500
Click to expand...
Click to collapse
The only added feature there is really a file manager everything else the same
Twip just has a really cool touch interface
Sent from the My Little Pony Official App
x-dira said:
plzz....support multirom
thanks
Click to expand...
Click to collapse
ask to Tasssadar for that
dnle71 said:
Just a little bug here, there are some overlapping text specially when backing up..
Sent from my LG-P500 using Tapatalk 2
Click to expand...
Click to collapse
i will try to fix on next version.
@Ron G: I posted about your work on DroidViews.com: Here
After long time twrp is back..just want to know is this fully suitable or compatible for ics or miuiv4 roms flashing like amonra???
Jaani said:
After long time twrp is back..just want to know is this fully suitable or compatible for ics or miuiv4 roms flashing like amonra???
Click to expand...
Click to collapse
Yes it is, successfully flashed AOKP, Oxygen, Hep's ics, CM7, MIUI GB/ICS
Sent from my LG-P500 using Tapatalk 2
At pershoots request, here is the official nightly discussion thread. I will be updating this with information that I find and users posts that are helpful. REMEMBER: THIS IS A WORK IN PROGRESS SO ALWAYS READ THE THREE POST FOR UPDATED INFORMATION
CyanogenMod 10.1 is a free, community built distribution of Android 4.2 (Jelly Bean) which greatly extends the capabilities of your tablet.
New CM Wiki page! http://wiki.cyanogenmod.org/index.php?title=Main_Page
New CM Documention! http://wiki.cyanogenmod.org/index.php?title=Documentation
{
"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"
}
Usual CM disclaimers:
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.
*/
Known Issues (copied from droidbasement):
-A random flicker (it’s faint and fast) can be observed occasionally/infrequently. If this becomes a nuisance to you, you can try to alleviate this by selecting ‘Disable HW overlays’ in Developer Settings. This does not survive a reboot (must be selected on every boot) and impacts swiping motion (it slows it down) in Trebuchet (the Launcher).
-P4*: A 720P recording, when played back, will have artifacts in the upper section of the image. Also when launching the recorded video for the first time, you will encounter a bit of a delay before it launches.
-P4*:If you use the standard GAPPS (from goo), the keyboard will close if typed on for 2 or 3 letters quickly in succession, if you use Google Search, Messaging and/or Gtalk (there could be more). This is a GAPPS library issue. Install a third party keyboard (Swiftkey 3 works ok) and switch to it. This does not affect Browser, System, etc (stock KB works fine there). The GAPPS from wingray don’t appear to exhibit this behavior from brief feedback (make sure your system is cleaned out using the latest recovery (format system), prior to installing the rom and gapps if you had the set from goo installed prior (it has also been reported that data needed to be wiped as well to rid of the residuals)): http://forum.xda-developers.com/showpost.php?p=35825009&postcount=3553
-Wallpaper will be down aligned on the lockscreen.
Things that need work from the community:
Samsung Keyboard Layout
Tell me more
CWM:
Make sure you have the latest (CWM 6.0.3.0)
Download from pershoot website, select your Tab version below:
P7510 (Wifi Only)
http://droidbasement.com/galaxy/roms/cm10.1/p4wifi/
P7500 (3G+Wifi)
http://droidbasement.com/galaxy/roms/cm10.1/p4/
SCH-I905 (Verizon)
http://droidbasement.com/galaxy/rom...//droidbasement.com/galaxy/roms/cm10.1/p4tmo/
Download recovery.tar.md5 and flash with ODIN or Mobile ODIN
Links for ODIN 1.85 : MediaFire
Links for Mobile ODIN by Chainfire Play Store and XDA
Bootloaders: Make sure you update your bootloaders to ICS. People who flashed an ICS custom ROM coming from HoneyComb (3.1) do not have the correct bootloaders.
Download Bootloaders from pershoot site: http://droidbasement.com/galaxy/roms/cm10.1/
Locate your variant and flash with ODIN. *NOTE: MOBILE ODIN DOES NOT FLASH BOOTLOADERS. ONLY ODIN WILL
Bootloader Flashing Instructions: (see image attached to post if unclear)
1) Open ODIN, all settings should be at default, if you change anything, hit reset or make it the same as image attached.
2) Select PDA slot and select the bootloader.tar file.
3) Flash
4) If unclear about the instructions, please ask!
Modems:
Download the recommended modem for your device at droidbasement:
http://droidbasement.com/galaxy/roms/cm10.1/
Install instructions are in post #3
P4 Variants Downloads: (Please see READ ME in post #2 to avoid and confusions or headaches)
P7510 (Wifi Only)
http://get.cm/?device=p4wifi&type=nightly
Changelog: http://mobile.10.1.cmxlog.com/?device=p4wifi
P7500 (3G+Wifi) (You must be on the ICS modem for best results.)
http://get.cm/?device=p4&type=nightly
Changelog:http://mobile.10.1.cmxlog.com/?device=p4
SCH-I905 (Verizon) (You must be on stock ICS (and it’s modem) before flashing to this build, for LTE functionality)
http://get.cm/?device=p4vzw&type=nightly
Changelog:http://mobile.10.1.cmxlog.com/?device=p4vzw
SGH-T859 (T-Mobile)
http://get.cm/?device=p4tmo&type=nightly
Changelog:http://mobile.10.1.cmxlog.com/?device=p4tmo
gapps: (update 01/29/2013)
P75xx gapps: gapps-jb-20130129-P75xx.zip http://www.mediafire.com/?44xhky6dyx4wlw2 Credit to dreamcwli from his thread on Xoom My Android ROM 4.2.1 for original package (Please thank him for the gapps)
Known Issues if using Goo Inside gapps or other gapp packages:
-Hot word detection for Google Now (caused the Google Now crash when starting)
-Gesture typing (causes random crashes when enabled)
-Photosphere (crashing when selecting camera or after aligning shot)
These features are removed in P75xx gapps.
Removed any Google Apps (e.g. Play Music, Sound Search, Calendar, Gmail) that can be downloaded in Play Store: https://play.google.com/store/search?q=Google+Inc.&c=apps
Credits:
pershoot for his hard work
Cyanogen for his amazing ROM
CyanogenMOD Team for their awesome work
Follow CyanogenMOD Team:
Google+
Twitter
PSA from CyanogenMOD about non-NEON future support: https://plus.google.com/u/0/117962666888533781522/posts/8wcuSVkr7zR
READ ME:
#If using 4.2.2 and want to roll back to 4.2.1 (last build is Feb 13th), you will need to do a full wipe to move backwards or you will bootloop. (update 02/19/13)
#PSA from CyanogenMod team: https://plus.google.com/+CyanogenMod/posts/M2pVM7Y6MTq (update 02/19/13)
ADB Whitelist
As of the Android 4.2.2 update, when you connect your phone to a computer, you are presented with your computer's RSA key fingerprint to open the adb connection. You also have the ability to permanently trust the computer, so you don't have to repeat this step upon every re-connect.
In order for this to work, you must be on the latest SDK which will grant you an updated 'adb' binary.
We will not be introducing any functionality to sidestep this default security, so if you don't update, you will lose the ability to access the device using adb.
# CM 10.1 is based on Android 4.2.1. Any and all proprietary applications that you have installed outside of CM should be updated to their 4.2.1 counterparts. Do not use the 4.1 versions of proprietary applications, else you will experience difficulties.
# Do not use the CyanogenMod Updater to go from 10.0 to 10.1. While you will have a functional rom, due to the 1st bullet point, you will be left without your proprietary applications and their data. We highly suggest performing the initial install manually via recovery (flashing CM and your addons). Once you are on 10.1, you can use the CM Updater as per normal.
# You do not need to wipe when updating to 10.1 if coming from an earlier CM version. However, as we mentioned in the weekend's PSA, users updating (instead of wiping) will experience a conflict in the application data for the Clock app. You are advised to clear this apps data on first boot of 10.1.
# Another item to note is that the support for the 10.0 feature that allowed for an expanded number of targets on the pattern lockscreen is not in 10.1. If you use this lockscreen, disable it before updating from 10.0.
# Finally, we always advise that you create a backup before any update. Do note, however, that due to Android 4.2 changes to support multi-user mode, your backups will automatically be transferred to /sdcard/0/[backup folder]. Remember this when attempting to restore 10.0. Credit to post from CyanogenMOD team (G+ https://plus.google.com/+CyanogenMod/posts/9X561GFMxL5)
Coming from Samsung ICS ROM (custom or not) requires a FULL WIPE (Wipe Data, Cache, and Dalvik Cache) If you do not WIPE you will get a bootloop.
From droidbasement:
GT-P7500 (p4), GT-P7510 (p4wifi), SCH-I905 (p4vzw) and SGH-T859 (p4tmo)
-For P4VZW: You must be on stock ICS (and it’s modem) before flashing to this build, for LTE functionality
-For P4WIFI UK: You must be on the US ICS bootloader (odin .tar.md5 inside the .zip in the folder), otherwise you may incur a rolling screen
-For P4: You must be on the UK ICS bootloader (odin .tar.md5 from AUS inside the folder), otherwise you may incur a rolling screen.
-For P4*: You must be on the ICS modem for best results.
BEFORE REPORTING ANY BUGS, PLEASE DO A FULL WIPE AND FLASH AGAIN TO VERIFY THE BUG! ALSO, NOTHING WILL GET FIXED WITHOUT A LOGCAT (we cannot debug xda posts, need a logcat)
Getting a logcat:
1) Make sure ADB is installed (http://developer.android.com/sdk/index.html)
2) Open Command Prompt
3) adb logcat -d > logcat.txt
4) Locate the logcat and upload to xda
Install Instructions: IMPORTANT TO SEE READ ME IN POST #2 It will save you a lot of headaches when upgrading or updating your Tablet.
1) Install the latest CWM (see 1st post for more info)
2) Install ICS bootloaders (1st post) *People who flashed an ICS custom ROM coming from HoneyComb (3.1) do not have the correct bootloaders.
3) Boot into CWM and flash CM10.1 (Please see READ ME in post #2 for more information)
4) Flash gapps-jb-20130120-P75xx.zip (see 1st post for download)
5) Reboot
pershoot has stated before: "best to wipe as some experience lag with multi user." and "if you get any latency/ bizarro behavior, wipe"
F.A.Q
Want Adobe Flash on your Jellybean Tab? (update 05/21/13) New version is (11.1.115.58)
Check out the latest download here: http://helpx.adobe.com/flash-player/kb/archived-flash-player-versions.html Scroll to Flash Player for Android 4.0 archives and download most current (11.1.115.58). *Note: Flash is not supported in Jelly Bean, no support given in this thread as well.
Need Developer options and Performance tabs?
Go to settings>About tablet and start tapping Build number until it says your a Dev.
I am getting sudden reboots or freezes?
Not all tablets are created equal, if you are experiencing sudden reboots after Overclocking, reset your options back to default.
I am still rebooting or freezing?
Do a full wipe and DO NOT install anything. If the tablet is not rebooting or freezing, install your apps one at a time to isolate the cause. If you are using Titanium Backup, DO NOT RESTORE DATA FOR SYSTEM APPS.
I get Force Closes (FC) when I launch ____ app?
Try clearing data for the application by going Settings>Apps and locate the app and select Clear Data.
How can I increase Launcher performance?
Enable wallpaper hack (Settings> Launcher>Homescreen) and select Wallpaper quick render to boost home UI response (when using a static wallpaper).
Once I am on CM10.1, do I need to continue getting my updates at get.cm?
No, you can update future nightly builds by going to Settings>About tablet>CyanogenMod updates. Once there, change Update types to "New Versions (incl. Nightlies)" *NOTE: Pay attention to the file name, you might occasionally see CM 9 or 10 in the list, DO NOT FLASH!
Can I enable Voice Calling on my tablet?
At this time, the framework has the hook enabled to allow for users to work on the feature. IT IS 100% UNSUPPORTED at this time because it requires you to flash modems which is a deviation from the recommended setup.
I flashed ___ from another___ thread, now ___ this stopped working?
Wipe data and flash CM 10.1 from get.cm, does this issue still happen? If so, post logcat... if not, seek support from the thread you flashed the file from.
I HATE the new layout with the navigation keys in the middle, can I move it?
At this time, the nav keys in the middle is the design. Who knows, CM Team might change this in future builds.
OH NO! Where did my previous CWM backup go?
4.2. changed the file structure on how internal storage is viewed. Data on the internal/fake sdcard will go to 0/ (i.e. /sdcard/0/; /data/media/0/) (both are the same thing).
Since the internal storage is emulated, it is setup now (using file explorer like ES) /mnt/shell/emulated then you will see /0/; /legacy/; /obb/; and /clockworkmod/. Copy clockwordmod folder to your PC and if you need to, flash back to old ROM with old CWM and then move the backup back to /sdcard and then restore.
Using the latest recovery, to find /sdcard while in recovery, you will need to adb to /data/media/. *Note: Make sure to have a copy on your PC, I ran out of space before restoring since it is all in the /data.
Hey! Did you see the easter eggs!!
So not only is there an easter egg when you press the Android version and long press on the jellybean, but if you hit CyanogenMod version, CM planted one too. But did you know that by doing the easter egg and long pressing on the jellybean, you unlock another one! Go to Daydreams under Display in settings and you will see BeanFlinger!
My sound is really low or really high when I am using headphones!
If you are having really low or high volumes while listening with headphones, I recommend Voodoo Sound from Supercurio in the Play Store (Link). This allows you to take control of your volume and change it to your preferences.
I see cm-10.1-xxxxxxxxx-UNOFFICIAL-p4xxxx.zip on Droidbasement, what's the difference between droidbasement builds and nightlies?
The UNOFFICIAL builds on droidbasement are experimental builds compiled by pershoot for testing. It is recommended to flash the nightly builds unless specifically asked to test an unofficial build.
Awesome man and thanks...
Sent from my GT-P7500 using Tapatalk 2
Crazy question, where is dev options located? can't seem to find it anywhere.
Thanks, and what about for Voice calling?
How much User acount can we create?
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi
kiladubz said:
Crazy question, where is dev options located? can't seem to find it anywhere.
Click to expand...
Click to collapse
Go to About in settings and hit the Build Number until it says your a Dev now
eddai said:
Thanks, and what about for Voice calling?
How much User acount can we create?
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
I am going to need more information about Voice calling since I have the Wifi only model. If someone else can chime in about multi user would be great, I haven't tested multi user yet.
nakedninja42 said:
Go to About in settings and hit the Build Number until it says your a Dev now
Click to expand...
Click to collapse
oh, rock on dude, thanks!
eddai said:
Thanks, and what about for Voice calling?
How much User acount can we create?
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi
Click to expand...
Click to collapse
Not sure about voice calling... but as far as user account limits, I don't believe there are any beyond the physical limitations of the internal storage.
Sent from my Nexus 10 using Tapatalk HD
kbluhm said:
as far as user account limits,
Click to expand...
Click to collapse
i've capped it at +3.
https://github.com/CyanogenMod/andr...mmit/b6458e0209ecee044dfb338f9dae98c29efdfcc6
How can I check which bootloader I am currently on?
Dreameagl said:
How can I check which bootloader I am currently on?
Click to expand...
Click to collapse
You can't if you are not sure, then you should flash the one on droidbasement (see OP).
pershoot said:
i've capped it at +3.
https://github.com/CyanogenMod/andr...mmit/b6458e0209ecee044dfb338f9dae98c29efdfcc6
Click to expand...
Click to collapse
Any Solution for creating more? ı need more than 5+. Dont ask why
ı am running unofficial Build of Cm 10.1 (D2dyno's build) and, outgoing voice calls working perfectly, but no incoming calls tablet doesnt rings.
Any idea for your work?
Thanks for Reply.
Nexus 7 cihazımdan Tapatalk 2 ile gönderildi
eddai said:
Any Solution for creating more? ı need more than 5+. Dont ask why
ı am running unofficial Build of Cm 10.1 (D2dyno's build) and, outgoing voice calls working perfectly, but no incoming calls tablet doesnt rings.
Any idea for your work?
Click to expand...
Click to collapse
sorry, i'm not increasing it more at this current time.
that unofficial rom is my device/vendor/kernel specific work + all of the cyanogenmod team's framework/system/build/misc work (from quick scan of the op's thread).
voice calls you are on your own with (the hook is enabled in the framework overlay so people can do what they will with it). you need to flash a separate modem for it. there's a thread around here where discussions were being held for it and people were attempting to fix some stuff regarding it.
Great thread. BTW I don't have KW issue on wingray's gaaps.
me_guitarist said:
Great thread. BTW I don't have KW issue on wingray's gaaps.
Click to expand...
Click to collapse
+1; everything is working great on P4vzw. Thanks to the OP for putting this thread together and to Pershoot for keeping the 10.1 alive and well.
Thanks ninja for creating this thread. The other one has grown too big. Cheers!
Sent from my GT-P7510 using xda app-developers app
Nice work
Wow. Great job Pershoot and team!
Running absolutely wonderful on the Google I/O P7510.
Been following your builds on droidbasement for the last 6 months. Glad to see it in the nightlies now.
Thanks for keeping this device alive.
Why is Google now often not working
Running the nightly with wingray gapps. It runs pretty good .
There were crashing issues with Google Now a while ago as well for CM10. What I'd so special about that app that it crashes way more easily than other apps?
This Rom is based on and derived from SLIMRoms compiled from scratch, looking for maximum performance.
My goal is not only to compile. Is to modify and optimize, adding value.
All sources: https://github.com/Dhollmen
Product Highlights:
Android 4.4.4
Compilation with 4.8 toolchain.
Apps and framework generated with Java-7
Integrated last Dhollmen Kernel.
Interface to overclock kernel options.
Management just like FAT32 NTFS without requiring either apps or additional widgets.
Management EXFAT exactly like FAT32 , without requiring either apps or additional widgets.
Management of F2Fs partitions.
IR support (p5113).
Viper4Android AudioFX Effects.
Multiwindow.
PIE controls.
Multiple keys programmable navigation bar.
More ...
This Rom includes Viper4Android AudioFX as equalizer and audio effects controller, credits to ViPER520 and zhuhang.
The Viper4 Add-On includes the IRS-Starter-Pack and very nice presets by BSDgeek_Jake.
Download & installation: Post #2
Some comments about: Post #3
Changelog:
20150618
New interface.
Many modifications in apps.
Some fixes.
Includes last kernel release.
Improvements in system base.
20150118
New compilation from scratch.
Includes new kernel release.
Restored 512 MHz Gpu frecuency.
Changes in some blobs.
20150103
New look in the browser, in line with other base apps (contacts, messages, email)
Removes unneded Hal power module.
Reducing camera resources.
Minimal improvements in system base.
Base inline 20150103 - 9
20141214
New system wallpapers
Improved translations
Modifications in some apps.
Improvements in system base.
Base inline 20141214 - 8.20
20141107
Rework SlimLauncher
Many modifications in apps.
More Improvements in system base.
Base inline 20141106 - 8.10
20141028
Includes new SlimLauncher modified by me.
Removes old Trebuchet Launcher.
Restore the ability to slide fingers in keyboard.
Many modifications in apps.
More Improvements in system base.
Base inline 20141027 - 8.8
20141018
Includes previous camera fix.
Solves encrypted /data issue.
Changes to status bar.
Reduced logs and dropboxes files.
More Improvements.
Base inline 20141017 - 8.6.1
20141013
Solved Blobs & camera issues.
Solved battery icon when tablet in shutdown loading state.
Added SDcard NTFS and F2FS support-
Added SDcard larger than 32 GB (i.e. 64GB) support.
Some more Improvements.
Base inline 20141012 - 8.4.
20141009
Pre-release (please, read this post)
..
NOTE: I not own a 7-inch model, so I can't try it personally..
..
XDA:DevDB Information
Dhollmen, ROM for the Samsung Galaxy Tab 2
Contributors
tuxafgmur
ROM OS Version: 4.4.x KitKat
Based On: Slim Roms
Version Information
Status: Stable
Created 2014-07-27
Last Updated 2015-06-29
.
Install:
Ensure you have installed a kit-kat recovery.
Download the zip file for your model.
Download the Google Apps.
Download the Viper4Android IRS file.
Reboot into recovery mode.
Imperative to do "wipe data/factory reset" (first time only)
Install the Rom zip file.
Install the Gapps zip file.
Install the Viper4Android IRS zip file.
Updates:
Download the last zip file available.
Reboot into recovery mode.
Install the zip file without doing wipes.
Download:
Rom for GT-P3100 device
Rom for GT-P3110/3113 device
Google Apps (Gapps)
Viper4 Convolver IRS
Recovery TWRP Dhollmen
Keyboard Xperia-TNG
Flash Player Kit-Kat
Dock module activation . . . . . . . (if you own such dock, only)
.
WARRANTY: You agree that this product is provided "as is" without any warranty, either expressed or implied, on its operation.
DISCLAIMER: Your assumes at your SOLE RESPONSIBILITY & RISK all results produced by the "software" and/or instructions in this thread.
.
> Rom's Notes.
Who installs this Rom, accept it "as is".
Contains just the apps and options installed.
What you want to add will have to be obtained from Google-Play or any other sources.
Please, don't report bugs if you are not using the installed Dhollmen Kernel.
In case of questions or comments, you must indicate additional apps, tweaks or installed "optimizations".
if you insert images, do it in a 'hide' tag. This hide your image until an user click to show it.
I assume you has installed a suitable Recovery and know how to perform the required steps.
Keep in mind that Antutu and others related apps give you very similar values, regardless of the Rom used.
In such apps, OC influence on speed, but its goal is to evaluate the hardware, not the Rom.
Don't use any kind of overclock before three consecutive stability test in Antutu.
> Rom take a long time to boot after installing.
It is quite normal if ART runtime is used as applications are self-compiled at first boot time, after installing a new Rom or changing to ART.
> Applications are slow to start after installing.
It is quite normal if ART is used because apps have self-compiled before first use.
Although it may seem at times, the Rom is not hung, just have to wait.
> Get Root access.
In Settings app, entering development option and select Root access.
If you don't see these items, we activate:
Touch repeatedly on About tablet > build number. From now on, initial setting screen show that option, plus Performance.
> Get Performance access.
If you don't see these items, we activate:
Touch repeatedly on About tablet > build number. From now on, initial setting screen show that option, plus Development option.
> Google Apps (Gapps).
All Gapps packages available are virtually identical.
Only differ, from each other, in the amount of installed applications.
Two different packages must be never installed as likely to cause Google applications FC.
The Dhollmen Gapps, being valid for any Rom, are specifically adapted for installation on it.
> Viper4 - Convolver - IRS.
This application controls the System Sound FX.
It also includes a number of advanced pre-equalizer settings (made by others) that are the IRS whose installation files requested.
Access to Convolver (manager of the IRS) is obtained by selecting the option Expert in Experience Settings.
Using another equalizer (provided by external applications) usually interfere with it.
You can only have one active equalizer in the system, but if you want to use another one, kindly Viper4 can be turned off.
> Restoring backups.
It is very common Titanium Backup (or similar) problems in Rom.
If backup /data partition are made and, after a change of Rom, restored, usually side effects will occur.
In this directory and subdirectories it contains, there are many configuration files and internal databases.
When it comes to a specific application should not be a problem as long as it is not part of the Rom.
When sub-directories containing settings are restored, the likelihood of problems increases exponentially.
For example, all Roms have a Settings application, but the content of his configurations differs between them and is not interchangeable.
Under no circumstances you should restore /system partition apps.
Rom Added to Index Thread
welcome aboard dude:good:
haven't heard from you for a while
edit:
Great n stable build, my quick test didn't find any issue, kudos :good: @tuxafgmur how did you make screenshot working, coz it didn't even work in AOKP rom by @Chirag_Galani?
I was able to test this great rom before you all
thanks @tuxafgmur for 20131215 Build and letting me test it
I really love it!
Great work! Keep it up! Nice to see that everybody now can use this Rom
Downloading 22th Rom now
What i forgot:
I really like the Sound and the MusicPlayer is great!
And it´s a much Stable Rom
Installed this last night - running nice and smooth. Thanks for a great release
PS - IR working well on P 3113
Regards,
sent from my GT-P3113 using Tapatalk HD
Hot Release <3
So far seems to be a Kickass Rom till used so far. :victory:
[Edit: I will report bugs if founds]
Thanks for this :laugh:
Thanks for rom!
NO OPTION in RECENTS RAM BAR
Other than that great rom
Hey @tuxafgmur,
How did you fix the screenshot bug and the small rotated recent apps??
I need those for my ROM.
Thanking you.
Regards,
Chirag.
Chirag_Galani said:
Hey @tuxafgmur,
How did you fix the screenshot bug and the small rotated recent apps??
I need those for my ROM.
Thanking you.
Regards,
Chirag.
Click to expand...
Click to collapse
I do not want to look like I refuse to answer it, but now I'm not focused on as I solved each of the bugs I found.
Note that I have made several thousand code modifications by adding, modifying or deleting lines.
I started my work on past July, then I abandoned her to get involved in Carbon and then restarted in past October.
When I got the initial repo version this included numerous previous changes.
If your bearings me a little about these problems, I can try to locate code sections related and, perhaps then, will serve you as an aid.
Regards.
tuxafgmur said:
I do not want to look like I refuse to answer it, but now I'm not focused on as I solved each of the bugs I found.
Note that I have made several thousand code modifications by adding, modifying or deleting lines.
I started my work on past July, then I abandoned her to get involved in Carbon and then restarted in past October.
When I got the initial repo version this included numerous previous changes.
If your bearings me a little about these problems, I can try to locate code sections related and, perhaps then, will serve you as an aid.
Regards.
Click to expand...
Click to collapse
Hey,
Ok so wanna continue in PM?? Or Google Hangouts???
As the bugs i face are very complex for me to debug having tried to debug since so many days....
Thanking you.
Regards,
Chirag
Sent from my GT-I9070 using Tapatalk
com.google.process.gapps
giving FC... tried everything
help required
Sent from my GT-P3100 using Tapatalk
Chirag_Galani said:
Hey,
Ok so wanna continue in PM?? Or Google Hangouts???
As the bugs i face are very complex for me to debug having tried to debug since so many days....
Thanking you.
Regards,
Chirag
Click to expand...
Click to collapse
Well. I'm wait your P.M.
tuxafgmur said:
Well. I'm wait your P.M.
Click to expand...
Click to collapse
Sent
Can someone else with a 3113 or 3110 running this ROM test their mic to see if its working properly?
I went to use Google now an noticed it could not hear me. Then went to sound recorder, same results. Just to be sure, I opened pitchlab, an app I use to tune my guitar and a few other instruments and still no response from mic. Didn't see it in "known bugs" in the thread so that's why I'm asking. I did compare the libs and modules for mic from a previous nandroid of aokp that i know the mic worked just to make sure it was all there. All is there, like it should be..
Ill pastebin a logcat if noone else reports this but I figured I'd ask first.
For reference I installed it clean like so:
Did a full format of
/system
/cache
/data
/sdcard
Then installed the latest ROM.zip and gapps from first post. Everything else in the ROM works beautifull. Fast and smooth. Using for about three days as a daily driver before I noticed the mic problem. Didn't experience any other bugs and I have been through every setting in customization available to get it setup how I like.
P.S. using built-in kernel. And no Xposed or modules
Edit: Fixed.. updated my recovery and re-flashed a clean flash. Rom works quite nice. Fast and smooth. Ill report bugs if I find any.
Stable , fast and good battery life. Tablet UI interface it's wonderful! I test mic later
{
"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"
}
sent from p3100
What is wrong with this ROM? Few times during the day a self restart. You can not watch the movies 720p.
{
"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"
}
OMNIROMUNOFFICIAL
He guys. I managed to find the time to port Omni to the z5c. Since it compiled, booted and works well (except camera) I thought I would upload to share. My goal being that we would have greater choices available adding to Stock, CM and AOSP roms. Note: This is not a developer thread. I'm just sharing this because it worked and others might be interested.
About Omni:
The goal of Omni is to experiment with Android development because we enjoy it. Omni isn’t better, just different. It’s another option for the billion Android users out there. Android (vs. iOS and every other mobile OS) has thrived on options as well as the gigantic, talented development community that has emerged to build those options. That’s the beauty of Android – that you can pick and choose from a smorgasbord of devices with varying features and functionality. https://omnirom.org/
BIG THANKS to...
@humberos - for creating the first omni device tree (that I know of) for the kitakami family. (my suzuran dev tree is largely his work)
@CTXz - for all the work he and the kitakamy dev team have done/will do for CM that will find its way in to the omni flavour of aosp.
@superR - I used his kitchen to make the zip file with sparse dat .img
The Sonyxperiadev team for releasing their sources to the public
The good..
Compiled with latest camera and vendor blobs provided by Sonyxperiadev.
Full working omni features
- Comes with latest TWRP packed in the kernel
- Advanced reboot menu - boot directly in to twrp or boot-loader, or reboot and hold up when led turns purple)
- Omni switch
-Advanced power menu (like kernel auditor)
The not so good..
Camera is slow.
- Colours are inverted on screen for main camera but pictures are fine in photo viewer.
- Colours are fine on screen for front camera but inverted heavy blue tinge in photo viewer.
Security in settings F/C (there is no trustzone for CM yet, when they reverse sonys binary and include it in their code I will kang it )
No fingerprint detection/ firmware (yet - this will be reversed from sony at some point as well.)
-Bluetooth reported to have the same limited functionality as AOSP.
-Root: The ramdisk.img patcher within systemless SU installer is detecting that Omniboot.img is already patched/rooted when its not, so aborts, thus at this stage we cant get full root. (Im working on this)
If anyone is interested in building Omnirom for the z5c let me know and Ill push my device tree and provide a link.
Here is the twrp installable zip for omni. Do NOT install this on another device other then the E5823
Do a factory reset/full wipe in twrp before you install. Make sure wou have GAPS and the latest SU zips ready to go as neither are included.
https://mega.nz/#!kkZRTb5Z!i96cGUNUztTAATQ8mkkv0ivcQI9aOqErZNjgVqNFoAE
Enjoy.
Kernel source is:
https://github.com/omnirom/android_kernel_sony_msm.git
Device tree/s :
https://github.com/joeisgood99/TWRP_device_sony_Omni-suzuran_MM.git
https://github.com/omnirom/
Reserved
wow finally,gonna transfer from cm to it
EDIT:no way to dirty flash from cm,android.phone will crash,will do clean flash.Camera seems better than cm one,keep going!
Really thank you! Will try soon!
Not sent by me!
Best of luck for your project and thank you!
Sent from my E5803 using XDA-Developers mobile app
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
mangusmeister said:
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
Click to expand...
Click to collapse
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
Click to expand...
Click to collapse
I tried the one from cm13 thread on these forums and the latest update from the site and same result with both.
Edit : deleted duplicate post.
mangusmeister said:
I tried the one from cm13 thread on these forums and the latest update from the site and same result with both.
Click to expand...
Click to collapse
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
What supersu version should be used ?
Good work btw.
Click to expand...
Click to collapse
mangusmeister said:
All functions seem to work fine though I couldn't get SuperSU working. Flashed the latest update but no dice. Just kept saying I had no root.
Also no icon appeared in the app drawer.
Click to expand...
Click to collapse
Excellent feedback guys.
I didn't test it with SU. I assumed it would need SU 2.7.1. Try installing it after the first or second full boot. Could someone test that for me?
In the mean time as it's systemless root, I'll look to see if it's trying to install in a folder within the kernel that doesn't exist in omni (not much to the ramdisk, just 4 binaries.)
Thanks!
Awesome work mate! Always good to have another ROM to choose from
Joeisgood99 said:
Excellent feedback guys.
I didn't test it with SU. I assumed it would need SU 2.7.1. Try installing it after the first or second full boot. Could someone test that for me?
In the mean time as it's systemless root, I'll look to see if it's trying to install in a folder within the kernel that doesn't exist in omni (not much to the ramdisk, just 4 binaries.)
Thanks!
Click to expand...
Click to collapse
Tried latest beta 2.74 via twrp.
Unable to find stock img
Unable to find ramdisc img
Installation failed.
Hope this helps.
This was after a clean install of just the rom and gapps and a couple of reboot cycles.
mangusmeister said:
Tried latest beta 2.74 via twrp.
Unable to find stock img
Unable to find ramdisc img
Installation failed.
Hope this helps.
This was after a clean install of just the rom and gapps and a couple of reboot cycles.
Click to expand...
Click to collapse
Double thanks.
I installed the su package and gapps with no errors in twrp. However there was no su apk in app drawer and gapps (smallest package) caused continues launcher f/c. I will have to see what a can do re adding apk to the installable zip...
Did you have trouble installing gapps?
Thanks again guys
Joeisgood99 said:
Double thanks.
I installed the su package and gapps with no errors in twrp. However there was no su apk in app drawer and gapps (smallest package) caused continues launcher f/c. I will have to see what a can do re adding apk to the installable zip...
Did you have trouble installing gapps?
Thanks again guys
Click to expand...
Click to collapse
I only had gapps issues if I did a reboot between the rom and gapps. Flashed together they were fine.
Concerning the SuperSU install in twrp, it appears at a glance to install ok but if you read what comes up in twrp(see my last post) it fails. Tried a few times and always the same result.
daanwassenaar said:
same here, flashed latest beta and installed apk through adb because security settings crash when you try to enable untrusted apks.
Click to expand...
Click to collapse
You can tweak with settings via adb shell, and the 'settings' command, ie: to allow untrusted apk installation :
settings put secure install_non_market_apps 1
Same problem with supersu. But otherwise, quite nice, and stable till now.
Does Bluetooth work?
civicsr2cool said:
Does Bluetooth work?
Click to expand...
Click to collapse
Same errors as in cm13.
mangusmeister said:
I only had gapps issues if I did a reboot between the rom and gapps. Flashed together they were fine.
Concerning the SuperSU install in twrp, it appears at a glance to install ok but if you read what comes up in twrp(see my last post) it fails. Tried a few times and always the same result.
Click to expand...
Click to collapse
LolaPalocz said:
You can tweak with settings via adb shell, and the 'settings' command, ie: to allow untrusted apk installation :
settings put secure install_non_market_apps 1
Same problem with supersu. But otherwise, quite nice, and stable till now.
Click to expand...
Click to collapse
Now I believe the issue is when the SU install script tries to split the kernel. the script is expecting to find /kernel & /ramdisk.cpio after splitting the boot.img. Omni boot.img has a slightly different ramdisk format. The file path to the ramdisk once split from kernel is /sbin/ramdisk.cpio (as ramdisk.cpio and ramdisk-recovery.cpio both occupy the sbin directory, which sits beside <init> which is just a simlynk to the real <init> inside /sbin/ramdisk.cpio/
I will look at either modifying the systemless su install binary which is a little difficult as Chainfire's script writing ability is a little more advanced then mine...:silly: OR modding the kernel to fit the script, root it then using the rooted ramdisk, re configure to original format, and re pack.... Ill keep you guys posted. Omni needs root.
Joeisgood99 said:
Now I believe the issue is when the SU install script tries to split the kernel. the script is expecting to find /kernel & /ramdisk.cpio after splitting the boot.img. Omni boot.img has a slightly different ramdisk format. The file path to the ramdisk once split from kernel is /sbin/ramdisk.cpio (as ramdisk.cpio and ramdisk-recovery.cpio both occupy the sbin directory, which sits beside <init> which is just a simlynk to the real <init> inside /sbin/ramdisk.cpio/
I will look at either modifying the systemless su install binary which is a little difficult as Chainfire's script writing ability is a little more advanced then mine...:silly: OR modding the kernel to fit the script, root it then using the rooted ramdisk, re configure to original format, and re pack.... Ill keep you guys posted. Omni needs root.
Click to expand...
Click to collapse
Good luck!!!
Got time to do my own testing with SU.2.7.1
The error Im getting is that su installer detects that the stock omni boot.img is already su patched....
Stay tuned.