Database Info

[PC-UTIL] [Discontinued] [Source Opened] Android RTL Auto-Patcher + ProTools (v.1.5)

Discontinuation Notice + Source Opened!
This project is now discontinued, as I have moved on to Android 4.X (ICS) which has perfect built-in RTL support.
I will still provide basic support as much as I can, but if your device has it, I recommend you move on to ICS as well.
If you wish to continue working on this project and improving, you have my blessing (as long as you credit me, of course).
Source code is available here, but be-ware: it's an undocumented, unorganized mess.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Android RTL Auto-Patcher
Version 1.5
The Problem
It's a well known fact that while Android has Hebrew and Arabic fonts, it has a problem with Right-To-Left alignment. The problem: It doesn't exist.
Sure, MOST programs display text correctly, but mix text and numbers in the same line and you'll get reverse numbers (123 appears as 321), and in SOME Google apps (like Gmail and Maps) the words themselves are reverse (so 'apple' appears as 'elppa').
The Old Solution
There is a solution for this, however you have to create a separate patch for every build, because the patch changes files in the build's framework. It's a relatively easy process, but for people who change builds constantly, it can get tiresome.
This Program
This program detects if a build is compatible with the patch, and if so - creates it almost automatically and install it back to the phone. A process that took about 10 minutes to complete before and required some knowhow, now takes only seconds and requires almost no prior experience!
{
"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"
}
ProTools
The ProTools are a collection of tools that will allow you to patch ROMs manually either directly to ZIP files, to the phone, or to framework files. It will also allow you to push, pull, extract and manipulate files to and from ROMs of all kinds, with great flexibility and ease!
​​
Compatibility
This program is intended for use with custom DEODEXED roms of Android versions 2.1 and above. The program will inform you if your build is not deodexed.
The program will allow you to either push the fix directly to the device or flash via recovery.
WARNING: Some 'squashedFS' builds have been reported not to be compatible, and the program can not - at the moment - detect those!
Warnings
This program is in Beta stage!
Many features have not been thoroughly tested and error handling is far from perfect.
It may give some errors, crash or stall - at which point I ask that you please send me your log.txt (to find it, click 'About' and then 'Locate Log') or as an upload in this thread.
I do request - however - that you try to be as specific as possible regarding your build, your computer, and what caused the problem.
Also, if you include the log here, please enclose it in 'code' tags.
Requirements
You MUST have Microsoft .Net Framework 4 installed for this to work.
You will also need the latest Java Runtime Environment
You must also have the ADB drivers already installed:
In Windows Vista/7, just connect the phone and let Windows Update do it's thing.
In Windows XP, you need to manually install the drivers available here.
ADB itself comes with the program, so you don't need that.
How to use
If available, boot into recovery (recommended for non-rooted devices!)
Connect your phone to USB and make sure the computer recognizes it
Run the program, and select 'Test Connection'
After connection has been made, if the build is compatible - select the correct Sense version. The program WILL attempt to auto-detect, but it's not 100% reliable, so please confirm that the program detected correctly
Select distribution method:
Push to Device (Recommended) - does simply that, the program will attempt to automatically patch the phone for you.
Create ZIP - creates a ZIP file that's flashable through Recovery (Clockwork Recovery Mod). Will also offer you to save the ZIP on the SD card (doesn't even require mounting USB).
Show File - will just show you the patched 'framework.jar' so you can do whatever you want with it.
Select any additional options you might be interested in (Gingerbread keyboard, for example - is a fixed Gingerbread keyboard with fixed Hebrew RTL that is compatible with the patch the program installs. It should work on 2.2 devices as well, and replaces the stock Android keyboard).
GO GO GO!
Reporting bugs
Please be sure to provide the name and type of your build when giving feedback or reporting bugs. For better bug-squashing, please also provide your log.txt file, which you will find in the application's directory.
Also, even if you experienced no bugs, your logs will be appreciated.
Finally, if you put the the log content in your post, PLEASE encode it with 'code' tags.​
If you have any additional non-bug-related questions, feel free to ask them in this thread. I will do my best to improve this program as time goes by.
Thank you, and good luck!
Download
Always available here:

Changelog, Known Issues and Planned Features
Changelog
1.5 - 14/08/2011
Advanced build numbers to 1.5 due to massive advances in the program.
Added global error handling - might not solve ALL problems, but will hopefully help avoid unlogged crashes.
When "Install Gingerbread Keyboard" and "Create Zip" are both selected, it will now also install the keyboard on the Zip.
The program will now also try to mount sd-ext in addition to system before patching (as will the flashable Zip).
When patching fails, the program will offer you to save the patched file to your computer for use with ProTools.
In the 'About' window, added the option to find the log file on your computer (for easier error reports).
Other minor undocumented improvements.
Completely overhauled the ProTools:
Offline Patching: Allows patching ROM Zips or 'framework.jar' files directly.
Manual Operations: Pretty much what ProTools was before, except with an easier straight-forward interface and with the option to operate on a ROM Zip file, from your phone, or directly from a 'framework.jar' file.
Added the option to manually push or pull anything to or from anywhere (with specific buttons for 'framework.jar', 'framework-res.apk' (for theming) and 'build.prop'.
Added the option to manually patch the Keyboard to the phone or the a ROM Zip.
1.1.2 - 20/07/2011 - minor update
Improved Sense 3.0 Detection
Updated build detection strings
1.1.0 - 14/06/2011
Fixed critical interface bug that caused the operation compelte / restart prompt not to appear if 'Push' was selected.
1.1.0 - 14/06/2011
Removed support for SD/SDRAM based builds
Instead, created three distribution methods: Push file, Create flashable zip or just Display file
Flashable zip will be flashable via recovery, and will attempt to push itself to the device's SD card.
Version 1.0.0 Beta
Build Detection:
Improved build properties detection
Vastly improved Sense detection mechanism
Sense versions now distinct by Sense version
Added Sense 2.1 (Gingerbread) support
'Pro Tools' (Beta) - Every single function of the patcher can now be called on seperately and manually.
Changed versioning scheme. Version 1.0.0 to be assigned.
Updated core framework files (fixed a lot of stability issues in Sense2.0 builds)
Planned Features
I plan to seriously improve the RTL fix itself in the near future, but since I lack the knowledge to do so myself, I'm waiting for some new methods currently under development by the excellent devs at iAndroid.co.il to be released.
I do plan to release to program's source code eventually, it's just such a mess at this point that I'm more ashamed of it than anything else.
I also plan to include a logcat monitor. Because the patch causes the phone to rebuild dalvik cache, first boot after patching often takes a VERY LONG time, and some users wrongfully assume their phone is frozen. I plan to include a logcat monitor that will hopefully know to differentiate between bootloops, errors, and dalvik rebuilding, so users can tell if their phone is actually frozen or just working. If this works, I might release this as an actual separate program.
Known Issues
Build 1.1.0 - If 'Push' is selected, when patching process finishes, no message is displayed and the program doesn't prompt to restart. - fixed in 1.1.1
There is hardly any error handling in the ProTools section. If they are called with no device available, it MAY freeze/crash the program. Will be fixed in upcoming release.
Fixes for Squashed filesystem roms do not work! Mostly.
Error handling is STILL utter ****e, may give unexpected errors (or not at all and just fail altogether).
If HTC Sync is installed and active, stuff may go nuts all around (as of 0.0.5 this is detected by the program and warns user).
Credits
Program and Graphics created by Elad Avron using Visual Studio 2010 Express.
ZIP Functions created by Elad Avron using free libraries from the IC#Code group, available at http://www.icsharpcode.net/opensource/sharpziplib/
Special thanks:
From HTCAddicts.com: Ronenpg, Ohect.
From XDA-Developers.com: TheAgent1982, silverbluem, mdeejay and the entire HD2 dev crew
From iAndroid.co.il: Classicaldude (Original fix, the hero of RTL!), Dudyk (Original fix), rasmux (Modified fix), Liavk1 (partial SenseHD fix), Avicohh (Gingerbread Keyboard), N1Man (RTL fix for Gingerbread Keyboard).
Keyboard fix by Avicohh and N1Man (from iAndoird.co.il)​

If it will work man i'll give you a real big THANKS!

Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..

Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App

congratulation
Congratz of your new Project!
I will give it a shot as soon as i can

my teset here ..
this is my test in the log file attached
thx

I appreciate your efforts
reverse numbers problem still exits
big thanks

Voffchik said:
Tested and it workes!
Got an error in middle of the prosses but in the end it did what it was supposed to do.
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Thanks
Can you send me your log.txt?
I'd like to see what the error was.

Sup3r said:
I appreciate your efforts
reverse numbers problem still exits
big thanks
Click to expand...
Click to collapse
Can I get build type and log file please?
Thank you
jaguaralani said:
Just tried it V 001 , successfully connected + fetched framework+modified then pushed classes back....
log attached
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Device restarted, passed the first splash (hTC) screen, took very long on the animation one, then started !
Changes :
1-No right side line alignement..
2-Numbers are still wrongly placed..
Click to expand...
Click to collapse
The log indicates that you did everything right and experienced no errors, so there are two things I'd like you to try:
In the 'Toolbox' dir in the app dir, the leftover files from the creation process are left. Try pushing framework.jar manually to the device.
If that doesn't work, try putting 'classes_new.dex' in 'framework.jar', renaming it to 'classes.dex' (thus replacing the old one), and repeat step 1.
If that doesn't work something went wrong in the patching process itself, i.e. my source files aren't good for your build (they should be), the compression failed, or any step in between. Let me know if the leftover framework.jar and classes_new.dex solve the problem, and we'll try to isolate the problem from there.
Thank you all for helping

Thank you
Thank you very much for your great work.

The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/

NSider said:
The alignment works great for Arabic, but the thing with Arabic is that letters need to be connected with each other when they are in one word. From what I gather, this means needing to change stuff in libskia.so and libwebcore.so (both in /system/lib/).
For more info, you can check out the efforts to add Arabic support for many Android devices at http://ardoid.com/
Click to expand...
Click to collapse
Yes, I understand it's a problem with a lot of software, not only Android.
I will try to implement patching of Arabic characters in the future, once the program has a more solid base.

this is my log
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0

Ambious said:
Thanks
Can you send me your log.txt?
I'd like to see what the error was.
Click to expand...
Click to collapse
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App

Voffchik said:
I sent it yesterday via PM
I sent the log file + screenshot
U said u'll look in to it
Sent from my HTC HD2 using XDA App
Click to expand...
Click to collapse
Right, sorry, my bad
I worked around your reported error in v.0.0.2, it was a little oversight I had in interface design.
Thank you for the report
Sent from my Android HTC HD2 using XDA App

Sup3r said:
my build is : MDJ's gingerbread CyanogenMod 7 v. 2.1 [A2SD+][GRH78][RMNET][Kernel: MDJ S10.2 OC
wating the Arabic characters fix
thanks :0
Click to expand...
Click to collapse
Thank you for the log.
From the log it seems like there were no errors and that everything went as planned. I'm using the same build as you, so I know it's compatible.
What I'd like you to try, if it's not too much hassle, is this:
In the 'toolbox' dir in the app dir, there are leftover files from the process. Push 'frameowkr.jar' to your device's "/system/framework/" using:
Code:
adb push framework.jar /system/framework/
and reboot.
If that solves it, the issue was with the push command (I currently have no method to actually detect if it was successful or not, I hope to fix that in future version).
If even that doesn't solve it, open 'framework.jar' using any zip/rar program, delete 'classes.dex' from it, insert 'classes_new.dex' (from the toolbox dir) into the 'framework.jar' file, and rename to 'classes.dex'. Push to the device, restart, and try again.
If you don't mind doing those things, it would help me greatly to detect where the patching process failed.
Thank you so much, and I promise to include Arabic fix as soon as the program structure is solid enough!

Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing

jaguaralani said:
Tried V 002
PC - Win7 + net 4
LeoAndroid - Desire Z ....
Log attached
changes
Nothing
Click to expand...
Click to collapse
Yeah, well, v002 changes nothing in the process, only the interface.
I'd like you to try, if not too much hassle - to push the framework file manually and reboot.
If that doesn't work, try to put 'classes_new.dex' into 'framework.jar' and rename it to 'classes.dex' and push framework.jar again.
If any of that works then I can narrow down the issue.
On another note, I got reports from other people using DesireZ that the process worked for them, so I know it's compatible, it's just a localized issue.

This doesn't specifically belong to NAND development.
Moved.
(Regardless of that, it's a wonderful project).

[Odin][Rom][6/20/11]AC's Altered Beast **Alpha 5**EE4 based

THREAD INDEX:
POST #1 = ROM info and download
POST #2 = How to extract a compressed file
POST #3 = Directions on flashing odin written and visual
POST #4 = TroubleShooting
POST #5 = Random post lol
POST #5 = Credits
Original content from AC:http://forum.androidcentral.com/cha...ed-beast-alpha-voodoo-clockwork-ed2-root.html
you will find me there most of the time.
Click to expand...
Click to collapse
XDA, jt1134, nor myself are responsible for modification done to your phone. This includes, bricking, exploding, spontaneous combustion, or it running away with your significant other!!!
Click to expand...
Click to collapse
EXTRA SPECIAL THANKS TO jt1134 FOR DEVELOPING THE FIRST VOODOO KERNEL. NOTE I WAS NOT INVOLVED WITH THE DEVELOPMENT OF THIS KERNEL.
Click to expand...
Click to collapse
PLEASE BE KIND THIS IS MY FIRST ROM
This Rom is SUPER ALPHA so do not tell me that you want this or that give me a chance to work on it please.[/quote]​[Note]
This ROM is fully Deodexed, but only Partially debloated as time goes on i will keep debloating deeper and deeper.
List of thing to do:
ED2 update
Full Deodex
Full Debloat
Black Status Bar
Dark themed Market
Dark google search
Change Colors on touchwiz theme (Work in progress but accomplished)
Remove touchwiz launcher
Replace Launcher (Launcher Pro for now)
Quickboot app (to boot into clockwork)
AOSP unlock screen (courtesy of nitsuj17)
Accurate battery mod (courtesy of nitsuj17)
Clockwork recovery (Modified by jt1134 )
Voodoo ext4 lagfix (courtesty of jt1134)
Themed Dialer
Themed Swype
Altered Beasts Themed Dock and Icons
Transparent notification pull down
Animated text notifications
Power button boot options[/note]
[INFO]THIS IS THE GOAL TO WHAT THIS ROM WILL LOOK LIKE, IT IS NOT THERE YET SO DONT ASK WHY IT DOESNT LOOK LIKE THIS PLEASE
{
"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"
}
[/INFO]
For those that ask if there is lag
This is still an ALPHA build so please do not be to critical, it needs alot of themeing to be done and there is more i need to put on but i think everyone will be happy with the direction this is going with. This is inludes everything Striked off the list of things to include above.
After flashing it will boot right into clockwork, press power to reboot. Clearing cache partition and Dalvik is not a bad idea but if you dont it wont hurt anything.
[tip]If you do not already have voodoo installed boot time should be 5-7 mins do not panic just be patient.[/tip]
DOWNLOAD Altered Beast voodoo+cwm here:
Code:
Altered Beast Alpha 5 (to be flashed in CWM) this does not contain a kernel but is a full system flash not a patch
Change log 6/20
Hulu (on boot, before you sign into google, go to settings privacy and make sure auto restore is not checked. Also make sure flash doesnt update)
voodoo control app
alot of themeing by gunner and myself
new tv shutdown animation that i modded up
charging fixed
aosp launcher themed up by me
Teamnew widget added
Androphile wallpapers added
icons added to /system/icons may need ES explorer or root explorer to get to them
For those of you who dont know how to use clockwork there is plenty of info on this site, otherwise wait till tonight or tomorrow and i will be opening a new altered beast thread as this one is cluttered[/code][/CODE]
Change log: 5/27
Clock fixed
Voice input fixed
Partially themed
Flying windows added
Change log:5/26
Calendar fixed
Visual voicemail fixed
Dark Angel USB mod made
Carbon fiber quickpanel added
Hulu Patch: (Flash with clockwork)
AlteredBeast_Hulu_patch.zip
apks :(move to /system/app folder then reboot your device)
Calendarprovider.apk
VVMservices.apk
DeskCradle.apk
GoogleCalendarsyncAdapter.apk To fix Calendar problems

Extracting a compressed file (ex. zip or rar)
1.) Download and install Winrar HERE
2.) Locate the compressed file you would like to extract
3.)Right mouse click on the file icon a drop down menu will appear , select Extract Here
4.) You will then see a progress pop up window that will appear then when completed will close itself
5.)This will leave an extracted file in the destination folder
Congrats you have successfully extracted the compressed file it is now ready for use

To install ODIN packages on your device
1.Download and install drivers on your computer HERE
2. Next you will need to download the Altered Beast zip file from post #1 which will be extracted and placed in the PDA section of ODIN:
3.) You will need to download the ODIN application tool found here ODIN or ODIN MIRROR
4) Extract the Altered Beast zip file to get the .tar.md5 file
5.) If your phone is plugged into your computer, unplug it now.
6.) If your phone is not powered down, power it down now.
7.) Remove battery from phone.
8.) Launch ODIN on PC.
9.) Plug USB cable into phone.
10.) Plug your Droid Charge into the PC via the USB cable that came with your phone.
11.) Press and hold the volume down key until (approx 3 secs) you see a gigantic yellow triangle on your phone, and your phone will be in download mode. The first thin rectangle in the upper left of the ODIN applicate should also turn yellow and identify a com port. You can now release the volume key.
12.) Click on the PDA button in ODIN
Triple check that you pushed the PDA button. Do NOT click the Phone button prior to continuing to step 13. If you choose Phone, you will have bought your Fascinate a one-way ticket to hell.
13.) Find and double click on the Altered Beast .tar.md5 file you downloaded & click the Start button. (This should take approx 3 to 6mins)
14.) Phone will power down when finished.
15.) Close ODIN, remove USB cable from phone, reinsert battery, power on phone and let ROM fully load.
[TIP]It may boot into stock recovery simply Press the home button to reboot
It is also advised to wipe cache partition while you are in recovery [/TIP]
******************************************************************************************************************************************
[INFO]Visual Instructions [/INFO]
First you must download
Odin v1.3
Once odin is downloaded open it, its an executable file so when you open it you will see the following :
Once this is up, do the following
-Remove the battery from your Device
-Plug in the USB cord
-Hold down the Volume Down button until you see a big bright triangle on your screen , underneath it will say Downloading and beneath that it will say Do not turn off target
At this point you will see one of the boxes in the corner turn yellow, letting you know there is a connection, it will look like this
after you are connected you want to hit the PDA button, NEVER PHONE, phone will erase your modem and you will have trouble connecting after that at all.
when you click the PDA button a pop up will appear and you will need to select the file you would like to flash and then click open
now you will see the file appear in the PDA window ,, with connection made and the file in the PDA window, you may now hit Start
Once you hit start this process Should take approx. 5 mins if you are returning to stock . shouldnt take any less time than that and not much more. So dont start freaking out at min 2...(wait till min 7) lol
If you are flashing a Clockworkmod file it should take approx 7seconds.
once it is completed you should see the following window:
Once you have reached this screen it is safe to unplug , put your battery in and boot up..

Trouble Shooting
Odin application displays one of the following in message box OR Odin is locking up in the middle of the process
<OSM> All threads completed. (succeed 0 / failed 0)
Click to expand...
Click to collapse
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Resolution
90% of problems associated with Odin are due to communication between phone and computer
Reboot your computer
Redownload the odin package
Use USB ports in the back of the computer, if you already are use a different port
Make sure you did not forget to remove battery from phone (Should be out the ENTIRE process)
make sure Odin is the only application running and Antivirus is DISABLED
If you are using a laptop make sure its plugged in also find the nearest desktop and try from there
****************************************************************************
After failed flash with odin upon power up the following is depicted on the screen
SOFT BRICK
Resolution
First off DO NOT PANIC. there is a simple solution, just remove the battery , plug the phone into the computer, press and hold volume down and it will enter download mode. Please review all the steps oulined in this thread and try and flash again

Credits
AC Member drewwalton19216801 for assistance deodexing
AC Adviser Paul627g giving instructions on themeing
AC Moderator Ragnarox for overall advise on Roms
AC Super Moderator gbhil for assistance on pushing deodexed folders to system without clockwork
XDA Developer jt1134 for developing the Voodoo Kernel
XDA Developer nitsuj17 for aosp lockscreen mod

So we can't install this through cwm right(if we already have it)?
Sent from my SCH-I510 using Tapatalk

Grillrd said:
So we can't install this through cwm right(if we already have it)?
Sent from my SCH-I510 using Tapatalk
Click to expand...
Click to collapse
no i honestly i am not sure how to make it in zip flashable form yet hopefully a developer will show mercy upon me lol and show me how its done

I'm game!
Downloading now.
Just wanted to give y'all a big "THANKS" for all you do!
This is the first time I've flashed a ROM in a long time. SO far, it's been fun - let's see what this one does!
EDIT #1
WooHoo!
After rebooting, it booted into recovery mode (Red Text), so I just rebooted, and it went to the "Red Eye", and about 2 minutes later, we're golden!
BTW, the boot animation is still 'glitchy'. Could this be from my original flashing of v4 Kernel?
EDIT #2
Looks like email is missing....no ability to add either POP email or Exchange email, unless I'm missing something.

Thank you for the ROM ...loaded up perfectly. Are you planning on keeping the background image for the notification pull down or going with a solid color/transparent?

Rom is amazing.

UPDATE: nevermind, found the solution in the thread on androidcentral.
Thanks!
Ok, the rom booted up great. But I'm having calendar problems. I downloaded both the .apks. The calendarsync installed fine, but my accounts say sync is experiencing problems and will be back shortly. So I tried to install the calendarprovider and it won't install.
Help??
Thanks!

teddykgb715 said:
UPDATE: nevermind, found the solution in the thread on androidcentral.
Thanks!
Ok, the rom booted up great. But I'm having calendar problems. I downloaded both the .apks. The calendarsync installed fine, but my accounts say sync is experiencing problems and will be back shortly. So I tried to install the calendarprovider and it won't install.
Help??
Thanks!
Click to expand...
Click to collapse
Appears to be working just fine for me. Did you move both apks to system/app and reboot?

ColSaulTigh said:
EDIT #2
Looks like email is missing....no ability to add either POP email or Exchange email, unless I'm missing something.
Click to expand...
Click to collapse
I think in the ROM imnuts created, he removed the stock samsung email app. Unless you're talking about something different entirely.

Wow, this ROM looks amazing! Seriously cannot wait to see how it progresses.

Keep up the great work! Followed your instructions and everything is going great. I'm about to download those apks and put them in the place to fix calendar.

anyone on that has the calendar problem?

Im using this rom and dont have the calender bug. Only.bug ive seen so far is when deleting a contact it erases it then force closes on me. But it still does its job so its all good
Sent from my SCH-I510 using XDA Premium App

Z51 said:
Im using this rom and dont have the calender bug. Only.bug ive seen so far is when deleting a contact it erases it then force closes on me. But it still does its job so its all good
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
can you give me the permissions for
calendarprovider.apk
googlecalendarsync.apk
and if you also have the VVM problem permissions for that aswell

Z51 said:
Im using this rom and dont have the calender bug. Only.bug ive seen so far is when deleting a contact it erases it then force closes on me. But it still does its job so its all good
Sent from my SCH-I510 using XDA Premium App
Click to expand...
Click to collapse
For some reason, I can't even access the Calendar on my phone. It's not even in the app launcher or anything like that. The widget still works, but even from the widget, I can't open the calendar. Any ideas?

nvikram said:
For some reason, I can't even access the Calendar on my phone. It's not even in the app launcher or anything like that. The widget still works, but even from the widget, I can't open the calendar. Any ideas?
Click to expand...
Click to collapse
go to the OP download the 2 calendar apk and then use root explorer or another manager to move it to /system/app, then reboot the phone let me know if it works

[TOOL][NABIXD] NabiRootXD Root, Gapps, Recovery

NabiRootXD v2​
{
"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"
}
This is a tool for rooting, installing Gapps(Play Store, etc), and adding custom TWRP recovery on Nabi XD. It's written as a windows command line batch file, and is based off NabiLab I made for Nabi2.
It was an adventure to say the least. I include some of the hurdles for those that want to duplicate the root process or just to place my thoughts "on paper" because of the 100's of posts I read from those that posted detailed information and allowed me to gain useful insight in how I could adapt things for the XD, and explain in one swoop to the many PM's I have received about "when will we see root on the XD" why it took so freaking long. Those that just want the program can continue to the Overview section.
What started as an interesting avenue was TWRP using the Nabi2 kernel was booting the NabiXD to TWRP without video. I thought it possible to dd the recovery, or boot kernel. Unfortunately it was unable to recognize internal storage as a block device and that ended that. Like a few devices on Android 4.1.1 and above the standard once click program using Bin4ry's ADB restore exploit doesn't work. It doesn't work for a couple of reasons, when restoring fakebackup.ab in locks up writing the first file, and even if it did work placing ro.kernel.qemu=1 in local.prop doesn't work because Jelly Bean doesn't parse any property files to set the ownership of adb daemon. Searching the file system I found su2 in the xbin directory. This was promising as it is the su program but renamed, also unfortunate was its permissions had no setuid bit set and while it was executable it would not change uid to 0. I then foolishly went down the path of nvflash(forced recovery). I attempted a few different avenues here to try and possibly get the SBK to unlock nvflash, that proved uneventful, especially without root access. I tried extracting what "could" be the key from the Nabi2 it hope it was reused. That lead no where, it would be awesome to have access to it for many other reasons but it turned out to be an exercise in learning but ultimately a waste of time. Then on to other Android exploits... Tried Samba, debugfs, and vfat exploit. All of those are either patched or I'm not skilled enough. I finally returned to looking at the ADB restore exploit.
The "tabletS" exploitation showed promise as it takes the avenue of installing /dev/sh vs ro.kernel. A side effect of the failed ADB restore bug was leaving a directory with full permissions. Bads3ctor had an interesting fakebackup.ab that was more reliable at making a directory or file that you simlinked have full permissions. Now you can step through the tabletS script more effectively where you couldn't before by manually setting permissions for files/directories you need by doing the restore for each file and directory you need. The script installs VPNfaker and backs up the /data/app directory, then creates a new app directory. This however will cause the NabiXD to rerun the initial kidsmode setup and breaks everything. You can dance around that by not rebooting, and VPN faker will still give you a Term app with system uid. From there you can't symlink the sysfs links properly to data/property but that can be worked around by moving and then removing files. Finally you can makedev /dev/sh and run su from /data/local/tmp. The end result is that the exploits and bugs found by others are adequate when strung together in the right order on the NabiXD just not the one click solutions provided on the forums, they needed some modifications and done by hand to figure out for the NabiXD
Here is a nice publication I found in my searches that is more layman terms for older root methods. http://www.sourceconference.com/publications/bos12pubs/android-modding-source.pdf
Overview
Video Overview of NabiRootXD - a video tutorial of the use of NabiRootXD.
-Root the Nabi XD
-Install Gapps(Play Store, etc)
-Make a stock backup of unrooted device
-Install stock, or TWRP recovery
-NabiLab patching system to install updates to this program
Version 2
-Fixed scripting error causing early exit
-Added 7z for patching system
Download
Read the installation section below to determine which version you want.
File names:
NabiRootXD.zip 96MB (Version 2)
Download
Download Mirror
Installation
NEW INSTALLS
1) Download NabiRootXD
NabiRootXD.zip 96MB
2) Extract the zip files to a location of your choosing. Run the NabiRootXD.bat file.
Prerequisites
1) Script is for Windows
2) ADB enabled in Android. Enter Mommy/Daddy mode. Open settings->developer options->put a check mark in USB debugging.
3) ADB and Fastboot driver. Most popular are the PDAnet drivers. You can get them here: PDAnet drivers
Usage
Obviously using this script on your NabiXD voids the warranty and I take no responsibility for the damage you cause.
MENU 1 - Root, Gapps, Recovery​
Menu Option 1 - Install Root, Recovery and Gapps
This option is best used if you have a brand new Nabi. At this point you should have met the prerequisites of enabling ADB in Android. Follow directions, most sticking points are pressing the volume + and then pressing the volume - button twice and making sure recovery kernel is the one highlighted. After its complete you should have a rooted Nabi, with Gapps and a backup of your unmodified Nabi in the folder TWRP/BACKUPS/YOURSERIAL/stockunrooted on your device. Not a bad idea to copy this off the Nabi to your computer if you need to free space or have it in a second location.
Menu Option 2 - Install Root and Recovery
Same as above but doesn't install Gapps. Some people have trouble with option 1 taking the Gapps install, I personally have never experienced it but the option is this one, or I guess if you are an elite hacker that just wants root.
Menu Option 3 - Install Gapps
Same Gapps installed in the Option 1. Useful for re-installing Gapps. This is Jelly Bean Gapps dated 10/11/2012 without Google Search. This makes NO backup of you Nabi. You will have to already have installed TWRP.
Menu Option 4 - Install Root
Installs root. Nothing fancy here, and likely unneeded but here for completeness if you find yourself in a strange situation. One that comes to mind is that you have a stock backup which you restored and don't want to do another backup so you would just run this and the gapps install. It makes NO backup. You will have to already have installed TWRP.
MENU 2 - Install Recoveries​
Menu Option 1 - Install TWRP 2.3.3.0 for Nabi Version 1.2.3
Installs TWRP 2.4.4.0. This is the latest at this time. It has a screen timeout, if the screen goes black touch the screen to wake the screen, it's not locked up.
Menu Option 2 - Install Stock Recovery
Installs stock recovery. This is useful for taking an OTA, or completely returning Nabi to stock.
Notes: TWRP installs are based off my work in this thread if you want to read more.
MENU 3 - Patch NabiLab​
Menu Option 1 - Install Patch
For any updates to NabiRootXD this is where you can automatically load them. Basically you will download NabiPatchXD.zip and place the entire zip in the patch folder. No unzipping just the single file. Then run this option.
Credits - If you see these guys buy them a beer.
jzmtaylor - Original Nabi2 script that this is based off of.
Bin4ry, Bads3ctor, HEXcube, drjbliss - all the bugs/exploits needed to accomplish root
Dees_Troy - TWRP build tutorial
Eric Karz - TWRP Theming and rooting assistance
TeamWin - They are the guys that make TWRP possible

Weeee more Easter goodies haha.
thanks aicjofs

Sir can i use this tool for installing Gapps for unrooted Galaxy Tab 7.0+ (wifi)? bcoz i updated my tablet for Honeycomb to Ice creamsandwich (China Firmware), everything is fine except that i cant open google playstore...

first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results

srgsng25 said:
first of huge thank-you.. who do i send a bear donation to as a thank-you
there is a possible bug or its just me when pressing the menu button it will pull up a search, or say Google with a white back ground only way to get out isto press home if a menu appears then pressing back produces the same results
Click to expand...
Click to collapse
The gapps removes the problem in system/app/quicksearchbox.apk you can rename it toquicksearchbox.bak
only other way I can think of is some how playstore added it to data/app
rename com.google.android.googlequicksearchbox.apk to com.google.android.googlequicksearchbox.bak
hth
ps: thank the op he spent hours and hours to make this happen = sacrificed his free time

Thanks for the feedback.
Perhaps we should have used the 7/26/2012 gapps? http://goo.im/gapps/gapps-jb-20120726-signed.zip 10/11/2012 is suppose to be 4.1.1 backward compatible, but perhaps there are some bugs with it on XD. Flash over the top of the current one. It will leave behind /system/app/thinkfree.apk, /system/app/microbes.apk and /system/lib/libmicrobes_jni.so, which you could remove manually. Wipe caches.
How about GPS stuff? Is that working?

i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .

Eric Karz said:
i was looking at gapps-jb-20120810-JRO03C-Formula84-Custom
it has some things that sort of work like maps/local/ latitude /
I don't think gps is working
Even in the productions test it fails .
could it be a permissions problem ? I have not tried 20120726 .
Click to expand...
Click to collapse
Do we know that the GPS works at all?

aicjofs said:
Do we know that the GPS works at all?
Click to expand...
Click to collapse
with gapps installed it doesn't seem to work .
maybe we are going to need a edited gapps ?

I'm just going to remove Google Search for now. That is highly annoying, I was messing around with ways to fix it, and got it to open in apps when you press the settings button, I was previously only getting it when pressing back button.. I updated the downloads. Until we figure out the fix, it's just too troublesome.

cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious

srgsng25 said:
cool that did the trick renaming the file i do have a really stupid question is there a hiden proxy setting that makes the tablet able to bypass our DNS security filters with open dns just curious
Click to expand...
Click to collapse
I don't know if there is a hidden proxy. I'm not sure of your question. You could try going to settings-wifi. Long press the name of the network and a pop up will come up. Modify network, show advanced options. There is the proxy and DNS, for DNS you have to be static. I think there is 4.4.4.4 in there by default, plus what your router gives out.
If you are talking about something more underground I think you could use a getprop in adb shell or term.apk. I know I have seen stuff in there for DNS, something like dhcp.wlan0.dns there is stuff in there about "change" too. Should be able to set if you "su" and do a setprop. That would only be good until reboot, but could help you trouble shoot. I think it's set here /system/etc/dhcpcd/dhcpcd-hooks/20-dns.conf, maybe not in Jellybean. Anyway those are places to look if it's more then in settings that you are looking for.

ok it seems that this might be a work around to the quick search problem
edit the buildprop and change
ro.sf.lcd_density=160
to
ro.sf.lcd_density=145
I tried 149,150,59 and 120
120 does seem to fix it also but the screen makes every thing look smaller and some may not like that .(I do)
also I had to install BusyBox in order to get a few things to work including
build prop Editor by Nathan Campos (this tool seems to be a good test app to see if you have proper permissions)
note that the swipe screen will be a bit smaller under 160
maybe some one can use this info to edit quick search box we wouldn't have to change anything?

i am trying to get this tablet to use my network opendns settings and web filters

Can someone direct me to where I can get a Vista MTP driver for the Navi XD? I installed PdaNet as instructed but the tool wont connect, and I have a yellow exclamation mark by MTP Device. Can't seem to find anything else online.
EDIT: After rebooting a few times, then disabling my firewall, the tool connected. Thanks for the awesome tool.

Looks like an OTA was released for the Nabi XD today that bumbs the Nabi XD up to version 1.3.5. I tried doing the stock recovery option but the NabiRootXD app just closes out after selecting it. I looked into the NabiRootXD.bat file and I noticed on line 483 that it says to "GOTO Install_4" which doesn't seem to exist. I believe it should actually say "GOTO Install_2".
After making this change I was able to restore to the stock recovery to perform the OTA.
Now once I tried to install the OTA it appeared to atart the installs and then fails with the dead android symbol about a third of the way through. No idea what the problem is now so I'll just wait for others to try this and see what their results are.

yup getting the dead droid

Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.

OTA procedure
srgsng25 said:
yup getting the dead droid [
BOOT into TWRP and perform and system restore to pre-root image
reboot
download and install the OTA
reapply root and gapps
Click to expand...
Click to collapse

aicjofs said:
Reinstall TWRP and "Install" this to update. Have a backup. Should work if you have made no system modifications, except what NabiRootXD did.
Download
TWRP may or may not ask you to reinstall superuser.
Also working on a patch to fix the exiting error in script.
EDIT: New links for a version 2. Fixed scripting error and patch system error. Easier to just download the whole program again then for me to explain fixing the patching system manually.
Click to expand...
Click to collapse
Thanks for the update aicjofs! I'll test this out shortly and let you know how everything goes.

[ROM][6.0.1][CM13][UNOFFICIAL] Cyanogenmod 13 for Lenovo A760

DISCLAIMER: I do not own/build this ROM, This is not my work. I am posting this thread to help other Lenovo A760 users.
How to Install CM13 (Cyanogenmod 13) UNOFFICIAL 6.0.1 Marshmallow on Lenovo A760​
***** Android Rooting/Modifying Disclaimer *****
You are making these modifications to your device. I am not responsible for whatever happens to your phone, shall this process fail. You understand that I cannot be held responsible if you do not follow directions and brick your device. You are the only person responsible if you brick your device, as you are the one choosing to modify your device. You are voiding your warranty by rooting, making modifications, and install custom roms. I encourage you to READ CAREFULLY before following along and continuing to void your warranty. A fair knowledge of ADB and ROM flashing might be needed . You have been warned! Not following directions CAN result in a soft or hard brick. Thank you for if you read all of this!
Screenshots:​
{
"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"
}
Known Bugs:​
- No FM Radio
- Screen Recorder app causing phone to reboot (please do not use the app)
(All the links for download will be available at the end of these steps)
Step 1
Download cm-13.0-20160502-UNOFFICIAL-audi.zip and A-GAPPS 6.0.1.zip and save it under root directory in your phone's SD Card.
WARNING!! Step 4 to Step 9 will erase your Internal Storage. PLEASE BACKUP of all your files in Internal Storage (NOT SD Card) before proceed further!!
Step 2
Download the Qualcomm QPST zip, and install it on your Computer. (You may restart the computer after finished installation to make sure the driver is in effect)
Step 3
Power off your phone, take the battery out. Connect it with USB cable to the computer.
Step 4
Press & Hold (Vol +), (Vol -) & (Power Button) while its connected to your computer until you feel its vibrate 2x times. (check at the computer taskbar and see if device called Qualcomm CDMA Technologies MSM connected) DO NOT press FORMAT/ERASE drive if your computer prompt it. Just click cancel if the message appear.
Step 5
Download the HDD Raw Copy Tool and double click it to execute the application. You can now see 'Qualcomm MMC Storage' shown in the software.
Step 6
Download Lenovo_A760.imgc. Under the 'Qualcomm MMC Storage' line, there is another 'FILE' line, double click the line and select your downloaded Lenovo_A760.imgc
Step 7
Once your Lenovo_A760.imgc selected, it will display 'Please select TARGET' message. Click the 'Qualcomm MMC Storage' line and click the Continue>> button
Step 8
Click START and confirm to continue the process. This will take up to 20minutes.
Step 9
Once it shows 100% complete, you may remove the phone from USB cable, and insert back the battery. DO NOT power it on yet.
Step 10
Press & Hold (Vol +), (Vol -) & (Power Button) to go to Recovery Mode. Once you are in TWRP recovery, press ‘Wipe’, and swipe to proceed wipe/factory reset.
Step 11
Press 'Install' and select your cm-13.0-20160502-UNOFFICIAL-audi.zip.
Swipe to Install your zip. Press ‘Reboot system’ at the bottom.
Voila! you will be greeted with Cyanogenmod Boot Animation. Please proceed with the necessary steps to setup your phone for first time.
Step 13
Once booted up, go to Settings, scroll down until ‘About phone’. Tap on ‘Build Number’ for few times until a message appear: ‘You have enabled development settings!’.
Step 14
Go back once, and tap on ‘Developer options’. Turn on ‘Advanced reboot’ in Developer options, and scroll down a bit to set ‘Root access’ to ‘Apps and ADB’.
The following steps are only for those of you who want to install Google Apps:
Step 15
Press & Hold the Power button, select Reboot, and then select ‘Recovery’
Step 16
In the Recovery, press 'Install' and select your A-GAPPS 6.0.1.zip. Swipe to Install your zip. Once finished, just Press the ‘Wipe dalvik/cache’ button at bottom. After that, press ‘Reboot system’ again.
If your google Contacts does not sync, download the 'Google Contact Sync 6.0.1' apk and install & replace the current version in your phone.
Click to expand...
Click to collapse
If you are facing the ‘Unfortunately Setup Wizard Has Stopped’ or ‘Unfortunately Google Play Services Has Stopped’ errors, you may follow this steps:
For Setup Wizard, go settings, scroll down to ‘Memory’ > ‘Memory used by apps’ > ‘Setup Wizard’ > (Press i in the circle) > ‘Permissions’ > Turn on the options for ‘Contacts’ & “Phone’
For Google Play services, go settings, scroll down to ‘Memory’ > ‘Memory used by apps’ > ‘Google Play services’ > (Press i in the circle) > ‘Permissions’ > Turn on all the options
Download links
Qualcomm QPST: http://www.x-drivers.com/catalog/flash/mobile_phones/companies/qualcomm/models/qpst/12051
HDD Raw Copy Tool: http://viid.me/q0YITi
Lenovo_A760.imgc: http://viid.me/q0YH1w
Download CM13 Unofficial: http://viid.me/q0I8UI
Google Apps for Android 6.0: http://viid.me/q0I6nC
Google Contact Sync 6.0.1: http://viid.me/q0HCDh
--------- PLEASE SUBSCRIBE TO MY YOUTUBE ---------
Please Subscribe: https://goo.gl/Mr3YMF
Visit my website: http://tekmastah.blogspot.com
Credits
• Vlad Den from Youtube for HDD RAW Copy flash guide: https://goo.gl/i6bK9k
• Weritos from 4pda.ru forum for Cyanogenmod 13 UNOFFICIAL Rom: https://goo.gl/NdYfuS
• A-TEAM from XDA developers forum for Gapps: https://goo.gl/7A6kyX
• ZENELKA MILKO from Lenovo A706 Indonesia FB Group: https://goo.gl/wFKOsZ
• APKMirror for Google Contact Sync: https://goo.gl/mRJH8y

Hi mellomade,
Thanks for this ... I'm using another phone now running Lollipop, but still have the A760 running unofficial CM11.0. as a backup, I've downloaded all files, and will give it a go at a later date ... I'm between cataracts eye operations right one fixed, left should be done soon, I can't get new reading glasses until then, so I'm struggling with anything close-up right now. ...Jack

jachol said:
Hi mellomade,
Thanks for this ... I'm using another phone now running Lollipop, but still have the A760 running unofficial CM11.0. as a backup, I've downloaded all files, and will give it a go at a later date ... I'm between cataracts eye operations right one fixed, left should be done soon, I can't get new reading glasses until then, so I'm struggling with anything close-up right now. ...Jack
Click to expand...
Click to collapse
Hi Jachol. Good to hear some of us are still hang on to A760. No worries, do post here if you have any questions about the installation process. Get well soon!

mellomade said:
Hi Jachol. Good to hear some of us are still hang on to A760. No worries, do post here if you have any questions about the installation process. Get well soon!
Click to expand...
Click to collapse
mellomade ... The A760 has always worked well for me, I wouldn't scrap it, I only have the newer one because it came as a present ( so far it's been equally as good).
I've been studying the instructions, and guess steps 1-9 install the new TWRP recovery, the new ROM installation is then normal TWRP procedure.
I do have TWRP recovery v.2.6.3.0 already installed, but I'm sure it isn't compatible with latest android versions, so no chance of an install via that
It will be interesting to see if others from the old thread pick up your link.Thanks again. .. Jack

jachol said:
mellomade ... The A760 has always worked well for me, I wouldn't scrap it, I only have the newer one because it came as a present ( so far it's been equally as good).
I've been studying the instructions, and guess steps 1-9 install the new TWRP recovery, the new ROM installation is then normal TWRP procedure.
I do have TWRP recovery v.2.6.3.0 already installed, but I'm sure it isn't compatible with latest android versions, so no chance of an install via that
It will be interesting to see if others from the old thread pick up your link.Thanks again. .. Jack
Click to expand...
Click to collapse
Great! Actually, Starting from lollipop, rom installs require larger internal space. Since we barely have sufficient space for system on our A760, the internal storage needs to be repartition (done by HDD Raw copy tool). Luckily the provided image 'Lenovo_A760.imgc' will automatically install the updated recovery TWRP 2.8.7 (compatible for the rom install) so we dont have to.
I do think others from the old thread already shifted to other phones

The QPST link given is no more. Any chance you have another download link? Preferably one without malware, as there seems to be some of them floating around.
Thanks

astudent said:
The QPST link given is no more. Any chance you have another download link? Preferably one without malware, as there seems to be some of them floating around.
Thanks
Click to expand...
Click to collapse
I have updated with new download link (now its working). Sorry for the ads. You can click the 'Skip the ad' button after waiting for 5 seconds, or you can Google Qualcomm QPST if you prefer not to click it.

GM mellomade,
I have CM13 flashed OK now + the updated recovery, I'm finding heavy it on battery consumption,
mine loses 25% overnight with no additional apps installed as yet.
This is much higher than the unofficial CM11 Rom I have been using,
I've restricted some of google services in Privacy guard, this has helped a little
but I see no other way of reducing battery drain.
How do you find yours ?, and any suggestions please ?. ... J.

jachol said:
GM mellomade,
I have CM13 flashed OK now + the updated recovery, I'm finding heavy it on battery consumption,
mine loses 25% overnight with no additional apps installed as yet.
This is much higher than the unofficial CM11 Rom I have been using,
I've restricted some of google services in Privacy guard, this has helped a little
but I see no other way of reducing battery drain.
How do you find yours ?, and any suggestions please ?. ... J.
Click to expand...
Click to collapse
I was having the same experience too. I use Greenify App from play store, and put ALL apps into hibernation, except the one I required their notification to be alive (e.g; WhatsApp). That helps too. I guess that is one of disadvantages having an unofficial build, because it is not natively supported for our phone. Hence the high battery drain issue. On the bright side, we get to experience the latest (even though not updated) ROM :victory:

mellomade said:
I was having the same experience too. I use Greenify App from play store, and put ALL apps into hibernation, except the one I required their notification to be alive (e.g; WhatsApp). That helps too. I guess that is one of disadvantages having an unofficial build, because it is not natively supported for our phone. Hence the high battery drain issue. On the bright side, we get to experience the latest (even though not updated) ROM :victory:
Click to expand...
Click to collapse
OK, Thought I may have a problem with ROM download, I did try a reflash which didn't help any. I'll try Greenify later, one thing I like about this ROM is the minimal system apps used (no bloatware).
My present phone (X-BO 06) running Lollipop, has a setting which allows the phone to switch off/on automatically overnight which is great for battery saving, I must see if i can find an app that does the same. Thanks again for the info. ... J. :highfive:

jachol said:
OK, Thought I may have a problem with ROM download, I did try a reflash which didn't help any. I'll try Greenify later, one thing I like about this ROM is the minimal system apps used (no bloatware).
My present phone (X-BO 06) running Lollipop, has a setting which allows the phone to switch off/on automatically overnight which is great for battery saving, I must see if i can find an app that does the same. Thanks again for the info. ... J. :highfive:
Click to expand...
Click to collapse
aah.. we do have that auto start & shutdown setting on our official rom (4.1.2). Im guessing you want that functionality without installing any new apps right? If not, you may look into Phone Schedule from play store. It support android 6.0. No prob

mellomade said:
aah.. we do have that auto start & shutdown setting on our official rom (4.1.2). Im guessing you want that functionality without installing any new apps right? If not, you may look into Phone Schedule from play store. It support android 6.0. No prob
Click to expand...
Click to collapse
mellomade,
Are you saying that we do have the Off/On option with this lollipop ROM ?, if so I haven't found that it in settings, I will take another look, it does make a big difference to battery saving. ... J.

jachol said:
mellomade,
Are you saying that we do have the Off/On option with this lollipop ROM ?, if so I haven't found that it in settings, I will take another look, it does make a big difference to battery saving. ... J.
Click to expand...
Click to collapse
No no no. I think you may have misinterpreted my message there. I did mention, on our official rom, which is 4.1.2, the A760_1_A_2_0057_130828 updates from Lenovo. Sadly not on this unofficial cm build. However you can check out greenify, it does makes a lot difference if you hibernate unused apps. Hence, if this is your secondary phone, you may even hibernate all apps (which can significantly reduce battery consumption) without have to worry about any incoming notifications, am I right.

mellomade said:
No no no. I think you may have misinterpreted my message there. I did mention, on our official rom, which is 4.1.2, the A760_1_A_2_0057_130828 updates from Lenovo. Sadly not on this unofficial cm build. However you can check out greenify, it does makes a lot difference if you hibernate unused apps. Hence, if this is your secondary phone, you may even hibernate all apps (which can significantly reduce battery consumption) without have to worry about any incoming notifications, am I right.
Click to expand...
Click to collapse
Ah yes !, gotcha now ... total misunderstanding this end, and yes I've installed greenify, it helps a lot. Thanks again. ... J.

Can you please give a device tree of this rom.I really need it.

LineagOS - Jingpad

Has anyone looked into compiling / porting LineagOS for the Jingpad A1? They released the source code. Why use LineagOS and not their released because theirs is in Chinese and it's lacking features available in LineagOS. I understand that the company has stopped developing their default OS and everyone with them now kind of has a dead product. I someone ported UBports to it, but Ubports lacks somethings that LineagOS / Android brings to the usefulness for a tablet. I know they had android app support that you could install on their default OS, but it has bugs and some apps were slow or errored out upon launch.
jingpad-bsp
jingpad-bsp has 421 repositories available. Follow their code on GitHub.
github.com
Android ROM source code for JingPad A1
The source code has been zipped into the 8 packages below, you have to download them all before you compile. How to compile Full compilation (take the userdebug version as an example, if you are editing the user version, just change the ud710_3h10_native-userdebug-native in the instruction to...
forum.jingos.com

[Guide] Install Gapps on JingPad (Android ROM)
Here are some extra changes I made in my pac file: Changed internal software version to 1.0.002.014 (Previously 1.0.002.013) Just to distinguish my build from the official pac file Changed OS name to “Android 10” (Previously “JingOS 1.0”) Because it is Android 10 Changed...
forum.jingos.com
Follow the instructions to the letter and you will have gapps and all languages... Be careful when rebooting after installing the ROM to change from Chinese to English...
Let me explain: after installing the ROM you restart; change the language from Chinese to English (for the moment you will not see other languages); set developer mode; restart in recovery and go ahead following the guide.
That's already something waiting for lineage OS

Excellent thank you for this. I am trying to flash my system with the image in the post. The process worked, thank you for showing me the post.
How to change to english
edit the following file in the source code
/source/device/sprd/roc1/ud710_2h10u/jingos/device.mk
edit the following lines.
persist.sys.language=en
persist.sys.country=US
persist.sys.timezone=America/New_York
persist.sys.locale=en-US
ro.product.locale.language=en
ro.product.locale.region=US
and compile
cd /source/vendor/sprd/release/IDH/Script
./build_pac.sh -a ud710_3h10u_native-user-native -b all 2>&1 | tee build.log
​

Have there been any new developments for the JingPad? I have one and I would consider putting Lineage OS on it. However, I'm not competent enough to build it from scratch. Is anyone developing AOSP for this tablet?
I am presently running UBPorts (Ubuntu Touch) and it is certainly less than stellar. I can't get WayDroid to run. Things might change when UT upgrades from 16.04 to 20.04 in the near future. But for now, I am checking everything before I stick it in the closet.

Hmm, I guess no one has mirrored the instructions?
Because all jingos.com links are now dead.
Maybe someone who has copied the instructions or the original author could add them to this thread?

I have a lot of the files for this tablet including the flashing application Research Download, the .pac file from January 2022, and USB drivers for Windows. I have the .docx file with the Research Download instructions.
I am leary to reinstall the JingOS without clear instructions on how to do it since I now have UBPorts installed.

LoTo62 said:
[Guide] Install Gapps on JingPad (Android ROM)
Here are some extra changes I made in my pac file: Changed internal software version to 1.0.002.014 (Previously 1.0.002.013) Just to distinguish my build from the official pac file Changed OS name to “Android 10” (Previously “JingOS 1.0”) Because it is Android 10 Changed...
forum.jingos.com
Follow the instructions to the letter and you will have gapps and all languages... Be careful when rebooting after installing the ROM to change from Chinese to English...
Let me explain: after installing the ROM you restart; change the language from Chinese to English (for the moment you will not see other languages); set developer mode; restart in recovery and go ahead following the guide.
That's already something waiting for lineage OS
Click to expand...
Click to collapse
Is there any chance you keep the guide or somehow remember how to do it? The link is dead already. I got developer mode ready.

r3d10tu5 said:
Is there any chance you keep the guide or somehow remember how to do it? The link is dead already. I got developer mode ready.
Click to expand...
Click to collapse
No. Sorry. The only files I have are the original files distributed with the JingPad.

I found those links, and hope they can help those who come across this topic. I can share the original files either.
-
- http://web.archive.org/web/20220823...ow-to-flash-android-rom-on-jingpad-a1-c1/2716
- https://web.archive.org/web/2022052...ide-install-gapps-on-jingpad-android-rom/3007

r3d10tu5 said:
I found those links, and hope they can help those who come across this topic. I can share the original files either.
-
- http://web.archive.org/web/20220823...ow-to-flash-android-rom-on-jingpad-a1-c1/2716
- https://web.archive.org/web/2022052...ide-install-gapps-on-jingpad-android-rom/3007
Click to expand...
Click to collapse
Great work. Thanks.
Edit: I downloaded the gapps file and I have all the rest I need. Now I need to look into if this will flash OK after installing UBPorts.

jmd8800 said:
Great work. Thanks.
Edit: I downloaded the gapps file and I have all the rest I need. Now I need to look into if this will flash OK after installing UBPorts.
Click to expand...
Click to collapse
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to add that you properly should clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
How did you install the gapps?
I tried again today, and finally found how I was able to use gapps before.
You should have booted to the system once, before you boot to recovery and flash gapps.
“open_gapps-arm64-10.0-pico-20220215.zip” and “open_gapps-arm64-10.0-nano-20220215.zip” are probably the only two available version that work.
After reboot, you should get an error like “This device isn’t Play Protect certified” which keeps popping up, not “There is a problem contacting with google server”.
Steps:
Go to play store, click sign in;
It said “This device isn’t Play Protect certified”, click that green link “g.co/AndroidCertifiedDevice”;
Follow Google’s instructions to register your device;
Go to Settings, try your best to force stop gms & play store and clean their data;
(But do NOT clean gsf’s data! Clean cache is enough)
Go to play store and sign in before gms know it.
Click to expand...
Click to collapse

r3d10tu5 said:
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to ask that you properly clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
Click to expand...
Click to collapse
Looks like I have some work cut out for me. If I can get this to work and cover my needs I'll be happy. If not .... back in the closet it goes and I will buy an Apple or Samsung next week as I need something for travel.
Thanks

r3d10tu5 said:
I can confirm it would be no problem since I got utouch on my device before I reloaded it with android as an experiment; you can see. It would be a piece of cake.
ANW, in case you and everyone miss this part by caten (the one who makes the above video). I did follow him/her and success to get a working gapps. I want to add that you properly should clear the storage of the google play store and google play services, also CACHE (not storage) of google services frameworks in one go before trying to stop those services and try to sign in again.
GL.
Click to expand...
Click to collapse
This afternoon I set up a Windows computer and I have the pac file loaded into the Research Download program but it will not flash. I am wondering if I am missing something.
When I boot the JingPad to recovery (UB Ports orange) and look in the command line adb see the Jing Pad. (Windows actually mounts the device if I am fully booted to UTouch.) It will not flash the pac file to the JingPad. I waited 5 or 10 minutes and tried 2 or 3 times. USB drivers are working although I did get an error that the USB drivers are out of date.
I have developer mode ON in UTouch.
Once I get to recovery are there options I need to select?
For some reason, I cannot reboot to bootloader if that matters.
What am I missing?

jmd8800 said:
This afternoon I set up a Windows computer and I have the pac file loaded into the Research Download program but it will not flash. I am wondering if I am missing something.
When I boot the JingPad to recovery (UB Ports orange) and look in the command line adb see the Jing Pad. (Windows actually mounts the device if I am fully booted to UTouch.) It will not flash the pac file to the JingPad. I waited 5 or 10 minutes and tried 2 or 3 times. USB drivers are working although I did get an error that the USB drivers are out of date.
I have developer mode ON in UTouch.
Once I get to recovery are there options I need to select?
For some reason, I cannot reboot to bootloader if that matters.
What am I missing?
Click to expand...
Click to collapse
Did you follow the below step til the progress showing on the ResearchDownload (be sure to press start button on the ResearchDownload)? I have had to wait a bit and it was a success without any issues. I actually did flashing the device three times. In my case, there was no logo, just a progress bar on the ResearchDownload.
- Click the “Power” button then the “Volume Down” button. Do not release the buttons until the JingPad logo appears

r3d10tu5 said:
Did you follow the below step til the progress showing on the ResearchDownload (be sure to press start button on the ResearchDownload)? I have had to wait a bit and it was a success without any issues. I actually did flashing the device three times. In my case, there was no logo, just a progress bar on the ResearchDownload.
- Click the “Power” button then the “Volume Down” button. Do not release the buttons until the JingPad logo appears
Click to expand...
Click to collapse
I have 2 questions:
1) How long do I need to wait to see the progress bar for the flashing part? (I see the progress bar loading the pac file)
2) When I press ' power' and then 'volume down' the tablet boots to UB Ports recovery screen. Is this what is supposed to happen?
Thanks again

jmd8800 said:
I have 2 questions:
1) How long do I need to wait to see the progress bar for the flashing part? (I see the progress bar loading the pac file)
2) When I press ' power' and then 'volume down' the tablet boots to UB Ports recovery screen. Is this what is supposed to happen?
Thanks again
Click to expand...
Click to collapse
In my case, I start the process on the ResearchDownload, then hold the combo keys power + volume down. Next, release combo keys when I see the progress bar start loading and wait until the Status becomes Finish, and the Progress is Passed. Afterward, I just unplugged my tablet and restarted it.
Something's like this.
{
"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"
}

r3d10tu5 said:
In my case, I start the process on the ResearchDownload, then hold the combo keys power + volume down. Next, release combo keys when I see the progress bar start loading and wait until the Status becomes Finish, and the Progress is Passed. Afterward, I just unplugged my tablet and restarted it.
Something's like this.
Click to expand...
Click to collapse
Thanks. I was just about to try again when I saw your post. Using this method I got better results but I cannot install because 'my driver version is too low'. I'll have to dig into this. But it appears to contact the JingPad and even errored out in the status bar. Progress!
I don't use Windows so I don't have a legitimate Windows OS working. It says it is test mode as I've not registered it. I can source the BIOS to find the key and hopefully that will let me get to a point where I can update the driver required to connect the PC and the JingPad.
Thanks again

Success! Thanks for all of your help @r3d10tu5
Well.... Success installing the pac file. I'm still working on the gapps. the adb command said it was a successful instal but Google software is not on the screens.

Just a thought as I was playing with this. Has anyone tried to use microG instead of going through all the hoops to get Google services running?