{
"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"
}
One of the best, hardly noticed things on non-stock roms is the extended power menu with options like reboot and recovery. Now we can use it on our stock Jellybean roms. The instructions are very simple for this -- make sure you're on a STOCK DEODEXED rom and flash the zip. I made sure that the zip wipes cache and dalvik to make things even easier.
To other rom cooks, devs, and tweakers -- the only changes I made in android.policy.jar is for the reboot menu. The only changes in framework-res.apk is the addetion of 2 pngs for reboot and recovery and their respective strings. I followed this guide here so you can see what changes I made if you'd like to use this in your roms.
To Install:
Download djmcnz for the wonderful tutorial about the Reboot Mod.
For Devs, Cooks, and Beginners
Since I've learned most everything Android from all the great tutorials here on XDA, I thought I should share the patch and the added smali's I'm using in the extended power menu that correlate to the tutorial I used to do it. I hope these help someone as much as the other similar patch zips have helped me in the past.
Great,bro.. Glad to see there's a modder still works for us. Thanks a lot. I'll definitely give it a go.
Btw,I saw you've ported Paranoid to Defy,Miley 2 and Bravo. Hopefully you'll port it to our AHD.
PA on the OMAP3 phones wasn't a port -- it was many hours of merging the PA code with Quarx's CM10 code, then many more hours compiling, fixing compiler errors, test builds, etc. I wouldn't want to port it for us either because, lets face it, most ports aren't as good as if someone spent the time to at least try to do it right from source.
Since PA is now based on AOSP, my idea is to get the Motorola sources on SourceForge to compile an AOSP rom. If we can manage to get a working rom from that then PA, theoretically anyways, shouldn't be too much harder to get working for us. The problem is that Moto's SF sources usually suck and don't contain the correct or fully patched source we need. I've synced with AOSP and merged in the Moto sources, but I've yet to set up a device repo and a proprietary repo (gonna mirror the RAZR HD's with our proprietary files to start). I planned on doing more, but then I read about Hashcode and kexec and that being the main reason we don't have fully working CM...then I read about the rumor of us getting a 4.2 update with an unlocked bootloader -- so I decided to wait a bit to see what happens and make a stock based custom rom in the meantime.
If a dev like Quarx or Hashcode reads this anytime soon. would the above paragraph or using a modified RAZR HD AOSP git repo be a better idea. PA isn't something I plan on doing until I get my stock based rom done -- 4 days to a week I'd imagine -- and event then I'd like to start with a fully working base -- guess I could start pushing random libs to the CM10 port and see what happens.
For a teaser, it'll be Xperia Z based/styled, fully working Playstation Market (haven't bought anything yet...broke and cheap ...but the freebies work), Bravia2 (works, though it could be placebo and a new phone with a better screen that what I'm used too), more Sony Apps, Awesome Beats (got permission yesterday; ABeats works perfectly for us), some performance enhancing tweaks (just like Pro Athletes), CM10 Messenger, CM10.1 apn list, Inverted Gapps, and as little bloat as possible*. I'm gonna include Walkman as well, though I gotta find one that's compatible with Awesome Beats -- it really is Awesome, you'll see -- that'll be later today once I figure out the Reboot\Rocker mods (or I get tired of smali editing, whichever comes first ). Well, that's what I want on the first release anyways.
*I've only had this phone for a little over a week now. If you guys could give me a list of stock apps we don't need I'd really appreciate it. Some are pretty obvious like AABSync (ATT Address Book) or QuickOffice, but, like, wtf is fota.apk? Basically, I'm just trying not to have to freeze app, reboot, lather, rinse, repeat for hours on end.
Re: [MODS][STOCK][DEODEX] Screen Off Vol Track Skip Mod; Extended Power Menu in progr
Yeah porting PA its not the way to go as it will just have more bug and i have tried porting it and was able to get it to boot up to the welcome screen but i get a ENCRYPTION UNSUCCESSFUL error which as far as i know this only happen in ICS builds. And I been seen in several google plus post that they might unlock the bootloader but who knows our best hopes right now are kexec.
Sent from my MB886 using xda premium
Re: [MODS][STOCK][DEODEX] Screen Off Vol Track Skip Mod; Extended Power Menu in progr
sickkside13 said:
Yeah porting PA its not the way to go as it will just have more bug and i have tried porting it and was able to get it to boot up to the welcome screen but i get a ENCRYPTION UNSUCCESSFUL error which as far as i know this only happen in ICS builds. And I been seen in several google plus post that they might unlock the bootloader but who knows our best hopes right now are kexec.
Sent from my MB886 using xda premium
Click to expand...
Click to collapse
If you got PA to boot, I can try and help with the encryption error
Sent from my MB886 using xda app-developers app
Re: [MODS][STOCK][DEODEX] Screen Off Vol Track Skip Mod; Extended Power Menu in progr
I have this feature in my touchwiz ROM it came with sonys framework which I added in with the walkman app.
Sent from my DROID Atrix HD MAXX using xda app-developers app
Re: [MODS][STOCK][DEODEX] Screen Off Vol Track Skip Mod; Extended Power Menu in progr
...
Maybachiswhereitsat said:
I have this feature in my touchwiz ROM it came with sonys framework which I added in with the walkman app.
Sent from my DROID Atrix HD MAXX using xda app-developers app
Click to expand...
Click to collapse
Which Walkman did you use? I'm using this one here and long pressing doesn't do anything, though all the Sound Enhancements do work. I'm wanting Long Press Tracks more for safety feature than anything -- when driving, it's much safer to long press volume versus even turning on the phone and using the lockscreen widget to change tracks.
While your way is a quick fix that I like, not everyone wants the Sony UI or Apps, so I'm still gonna try and make this work with our stock rom. Personally, I think our stock rom is pretty good and I'm very surprised the Moto didin't screw it up.
Logan and I managed to get it working after hours of work on a sleepless night.
We followed this guide.
Best of luck.
EcHoFiiVe said:
If you got PA to boot, I can try and help with the encryption error
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
We were getting that error on the Defy once we started using custom kernels. For us, it was because the init scripts were expecting ext4 when /data and /cache were formatted to ext3. Setting the fs to auto in the init scritps and fstab was the fix (or just making sure you're using the proper filesystem). I've seen many porting guides and most none of them mention fstab and such. If /etc was blindly dumped then improper mounts is a probable cause.
mattlgroff said:
Logan and I managed to get it working after hours of work on a sleepless night.
We followed this guide.
Best of luck.
Click to expand...
Click to collapse
Thanks, That's the same guide I have linked in the OP . I spent about 8-10 hours yesterday trying to get the volume skip working with no luck. I think I'm just gonna get the reboot working first and figure out the track skip later. With track skip, Moto's added some long press features and they just clash with the skip smali diffs around. For example, I had no idea we could take screen shots with Power+Volume Down...perhaps that's in the Owner's Manual I never bothered to read...
For the reboot mod, I'd like it to be
Shutdown--LP Reboot Safemode (already like this stock)
Reboot--LP Hot Reboot
Recovery--LP Bootloader
Ideally, I'd like to have Recovery launch Recovery Menu that has links to stock recovery, safe strap recovery, and bootloader. Rebooting into the custom recovery is one thing I really miss from the Defy...at least I don't have to time Volume Down with the LED blinks. The 10 sec wait with SSR is great in that regard.
Success :victory:
Reboot menu now working as expected -- Reboot actually reboots. It's shocking, I know .
Here's how it works: (LP = Long Press)
Shutdown --LP Reboot Safe Mode
Reboot -- LP Reboot
Recovery -- LP Bootloader
Airplane Mode
If anyone is curious, the fix was changing $500 to $200...
I'll add in Reboot -- LP Hot Reboot when I find a better method than just causing the system to crash and start over. I've looked at the W.Widow Razr HD Rom...its Hot Reboot is nothing more than my Reboot crash in the OP mod. If that method is safe, then I'll just change $200 back to $500...but I don't think it is. Zips made, I'm testing (again), and starting the upload. I'll update OP with a flashable zip & instructions when it's done.
Thanks!!!
Skeevy nice to see you in the Atrix Hd forums!! You made my Bravo great and this will be great for my AHD.
skeevy420 said:
We were getting that error on the Defy once we started using custom kernels. For us, it was because the init scripts were expecting ext4 when /data and /cache were formatted to ext3. Setting the fs to auto in the init scritps and fstab was the fix (or just making sure you're using the proper filesystem). I've seen many porting guides and most none of them mention fstab and such. If /etc was blindly dumped then improper mounts is a probable cause.[QUOTE/]
Exactly what I was gonna say, lol.
Sent from my MB886 using xda app-developers app
Click to expand...
Click to collapse
Are the working zips uploaded? I can't get either one to work. Even after manually wiping caches it still does nothing.
Markyzz said:
Are the working zips uploaded? I can't get either one to work. Even after manually wiping caches it still does nothing.
Click to expand...
Click to collapse
Yes, the exact same ones I'm using. What rom are you using? I'm using this deodexed stock rom from the Batakang ftp and this mod is based on the files from that rom. This mod does not support the stock /system (unless you deodex it). You gotta either deodex stock /system manually or use the above rom on a rom slot. The zip on Goo.im is the flashable, working zip. The attatched zip in the OP is the patch to the smali and the addded smali files -- they're just to help others do the mod manually and it isn't a flashable zip.
To anyone who knows:
I need a bit on enlightenment on Safe Strap. On the Defy our recovery was directly tied in to the rom that we flashed (it was installed on stock /system/bootmenu). Where exactly is SS installed to and is it safe to flash roms on the stock /system? I've seen /sdcard/safestrap and /ss/safestrap (assuming the latter). I need to know cause I don't have a Windows box and I can't get my Linux box to recognize the phone in fastboot. I even tried the special motorola fastboot on the Atrix forums, at least it said ??????????? with fastboot devices . What happened is I made a nandroid of my stock rooted, did some mods, factory reset, and lost that nandroid....I wish I'd have known a stock factory reset would wipe my stock nandroid .
I'm on the stock side, deodexed. I'll give it another shot.
---------- Post added at 10:29 AM ---------- Previous post was at 09:58 AM ----------
Got it working by pushing the files manually. Might be something wrong with the updater-script. Anyways thanks!
Here's the updater-script in its entirety. If anyone can find a fault with it let me know. I've only used it to flash on slot 1. I use a slightly different one for my long press testing -- permissions for /system/app/Settings.apk instead of framework-res.apk. Its worked for me every time.
Code:
show_progress(0.500000, 0);
ui_print("Wiping cache...");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/cache", "/cache");
delete_recursive("/cache");
ui_print("Wiping dalvik-cache...");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/userdata", "/data");
delete_recursive("/data/dalvik-cache");
ui_print("Mounting your system...");
mount("ext4", "EMMC", "/dev/block/platform/msm_sdcc.1/by-name/system", "/system");
ui_print("Starting Installation...");
package_extract_dir("system", "/system");
ui_print("Setting permissions...");
set_perm(0, 0, 0644, "/system/framework/android.policy.jar");
set_perm(0, 0, 0644, "/system/framework/framework-res.apk");
unmount("/cache");
unmount("/data");
unmount("/system");
/Glad you at least got it working.
I guess you beat me to the sony rom, I just thought about how amazing it would be to have ps games on my phone and just started porting, If you need any help inbox me. Good luck and looking forward to it!
Maybachiswhereitsat said:
I guess you beat me to the sony rom, I just thought about how amazing it would be to have ps games on my phone and just started porting, If you need any help inbox me. Good luck and looking forward to it!
Click to expand...
Click to collapse
Will do.
If you haven't gotten it working, PSM is pretty easy to port over. I did it by accident...it's that easy. Install the Bravia 2 and Xperia Z Walkman from Rizal Lovins -- between the two, all the necessary PSM permissions and framework jars are installed -- after that, just go the sony site, download the PSM apk, and adb install it (or extract libs, push libs to /system/lib & push app to /system/app, set the usual 644 permissions, and reboot).
Kitchen is currently deodexing the Xperia Z 4.1.2. At least all the apks I checked contain xhdpi resolutions. Hopefully it doesn't require too many smali edits. I'm sick of smali and really wish I had stock sources to play with. I was really hoping that Google would start putting Motorola sources in git repos like Sony does, unlock the bootloaders, and support the community.
Maybachiswhereitsat said:
I guess you beat me to the sony rom, I just thought about how amazing it would be to have ps games on my phone and just started porting, If you need any help inbox me. Good luck and looking forward to it!
Click to expand...
Click to collapse
I'm pretty sure you've got more than enough ROMs to maintain and fully fix
Sent from my MB886 using xda app-developers app
Related
Update 05/10/2011: So, at this point I've just fallen too far behind the curve, and it doesn't look like I will be updating GladiAtrix any further. I'll still support v4.2.3 for 1.57 (which is pretty stable, and almost all the issues I've seen users have up to this point are the installation). I may at some point throw something together for myself to use and release it (as I don't care for the themes/mods of GingerBlur/GreyBlur), but at this point I'm doing all the mods manually and have no current plans to make a flashable zip out of it.
GladiAtrix 2 for 1.5.7 v4.2.3 CWMNews and Important Info - READ FIRST
{
"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"
}
Looks horribly out of place I know
04/14/2011 @ 10:00am: Download links are fixed. Sorry all! As I stated in my last post, I will be unavailable for the next few hours. I DO see your questions and I WILL answer them. Please be patient, this isn't my full-time job and I have other things that need my attention today. Thanks!
04/13/2011 @ 11:17pm - NOTICE on theme: The THEMED version does not have reboot/recovery. I've been too busy working out the other kinks to add it in. The NOTHEME version is just like v3 and older, with the reboot/recovery options intact, as well as all the other changes up to this point. That is the only difference between the two.
All the bugs with the fingerprint scanner, wifi defaulting to on, custom keyboards not working, etc. etc. should all be resolved. Please PM me or reply to the thread if you have any issues.
Version 4.2.3 is going to be considered base from here on forward. It will create a backup of all the files it changes and copy them to the root of the internal SD card. PLEASE copy this backup to some place safe. Going forward, all updates will be released on top of 4.2.3, and will create sequential backups of any new files changed, if there's a need to back them up. It does not have any feature updates since 4.2.1, just many bug fixes.
04/13/2011 @ 11:00am(ish) - NOTICE on Reboot/Recovery power menu options: These are currently removed. I added a theme, and I haven't had time to add reboot/recovery options to it yet. If someone who knows what they're doing would like to add them and send me the updated files, it would certainly expidite the process as I'm not even sure how I got them working in the first place on v1-3. Screenshots will be in the second post as soon as I get a moment to upload some.History and SummaryCWM finally released! Sorry for taking so long with it, I'm very picky about my work and wanted to test EVERYTHING and make sure it was all working as it was supposed to. I hope the extra effort pays off and nobody has any issues with this
I've removed the script version as there's no need for it anymore. CWM is safer and does everything we need it to do with the latest version.
This is only for AT&T phones running firmware version 1.57. If you have 1.52 or 1.26 please go here first: [SCRIPT] GladRoot (Bell 0.37.4, AT&T 1.26/1.52/1.57 Supported) If you are a Bell user, DO NOT INSTALL.
If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
If you run into any issues, please PM me or post your /data/local/tmp/ga2.log here. This will help me diagnose what went wrong, in the very unlikely event something goes wrong.
Come chat with us!Features:
Deodexed
Creates a backup of your current /system/app and /system/framework directories (This does NOT delete anything outside specific AT&T bloatware files, however)
Custom boot logo (animated version coming soon!)
AppWidgetPicker (better widget management)
Enables sideloading
Ad blocking
Installs AT&T tethering APN
Enables desktop flash content, i.e. Hulu (You MUST install flashplayer 10.2 from market prior to installing the ROM. You must also use a browser that lets you set your user agent to Desktop, such as Dolphin Browser HD)
Clears Dalvik-cache (can cause some third party apps to behave strangely, just clear their data. Known to cause issues with Launcher Pro. Reset of LP data fixes)
Removes the AT&T bloat (see second post for list of what is removed.)
Enables HDMI mirroring
Disables background media scanning (speeds phone up a LOT)
Webtop without need for dock (through micro-hdmi cable)
Xperia Arc theme (ported to Atrix by olieebur)
Preferred install location
Various speed increase enhancements to settings
Replaces stock Gallery with Miui 3D Gallery
Full market access, no more restricted apps (Currently under testing, as it doesn't seem to be working properly)
Installation instructions:
Download and install Tenfar's latest CWM Recovery.
Download the GladiAtrix2 v4.2.3 THEME zip file here or GladiAtrix2 v4.2.3 NO THEME zip here
If you want the Hulu hack to work, install 10.2 from the market now, BEFORE installing GladiAtrix2 v4.
Put the GladiAtrix2v4.2.3 zip corresponding to the version you selected (normal or notheme) on either internal or external SD card.
Boot into recovery.
Select “Install zip from SDCARD” using the volume keys to navigate and power button to select.
Select "choose zip from sdcard" if you put it on your external SD card, or "choose zip from internal sdcard" if you put it in phone memory.
Browse to the location you put the zip.
Select GladiAtrix2v4.2.3 zip corresponding to the version you selected (normal or notheme).
Install it!
Read disclaimer below
DISCLAIMER
This script makes significant changes to the /system files on your phone.
By downloading the files you agree that you KNOW WHAT YOU ARE DOING and that you accept responsibility if something goes wrong.
This has been tested to the best of my ability.
We are NOT responsible if this bricks your phone. Thank you.
-ManagementDownload LinksDownload GladiAtrix2 v4.2.3 FULL here
Download GladiAtrix2 v4.2.3 FULL NOTHEME hereChangelog:* Version 4.2.3 - Released 04/13/2011
Split the theme and notheme into their own versions
Rolled all updates up to this point into a full install
New base install version is this version, all future updates will be incremental.
Cleaned up install methods to not mess with any user settings
* Version 4.2.2 - Released 04/13/2011
Permission fix update for settings.db causing a massive number of issues
* Version 4.2.1 - Released 04/13/2011
Fixed HDMI mirror errors
Changed fingerprint to allow unrestricted market access
Added Motoblur widgets/apps back in as people seem to use them (myself included). AT&T bloat still removed.
Replaced stock MediaGallery with Miui 3D Gallery
Added ability to use webtop without dock through micro-hdmi
Minor settings changes for increased battery life/performance
Fixed issues with flash hack (recompiled the lib as it was corrupt)
Added option for preferred installed locations to Settings -> Applications
Imported Xperia Arc theme (ported to Atrix by olieebur)
* Version 3 - Released 04/10/2011
Now removes some of the Motoblur/AT&T bloat
Added custom boot logo (Animated version coming soon!)
Added HDMI mirroring support (Credit to Weichel)
Turned off stagefright media scanning
Added local.prop tweaks for performance increase
Fixed issues with tethering on non-AT&T carriers
* Version 2 - Released 04/08/2011
Initial CWM release.
Added custom flash lib for desktop flash content (i.e. hulu)
Installation logged with errors to /data/local/tmp/ga2.log
* Version 1
Initial script release.
Notes/thanks:Special thanks to: kennethpenn for the base installation instructions, shawnbuck/dasmoover/cranch/thews/sogarth/brandon15811/(anyone else I missed, apologies if I did) for all their insight on the script, and Chainfire for the use of his .sh recovery output methods, olieebur for the great work on the theme, weichel for the HDMI mirroring trick, and everyone who helped test in IRC.If you see any spelling errors or have any other problems, feel free to PM me or post here.
If you have any feature requests, PM ME them. Please read post #2 for my current To Do list to make sure it's not already on there. If you know how to do anything on the to do list and would like to help out, send me a PM. I will ignore any "cn u add grhpix to the statuss bar?" in the thread.
To Do
bootanimation - Make static logo into animation
Fix reboot/recovery options - Anyone that wants to help with this is more than welcome to.
kill sound on sd mount - Possible?
Uninstall script - Coming soon!
List of Motorola/AT&T apps removed
com.telenav.app.android.cingular.apk
com.att.myWireless.apk
com.blockbuster.app.moto.apk
com.ea.nfsshift.apk
com.mobitv.client.tv.apk
com.mtag.att.codescanner.apk
com.wavemarket.waplauncher.apk
com.yellowpages.android.ypmobile.apk
com.qo.android.moto.apk
Screenshots (coming soon!)Will post screenshots of the major highlights here, but right now, I'm going to bed.
first !! thanks
Ririal, is it possible to add the option to set "Edge network only" as the stock Android would allow?
PM'd u
When I go to run this it asked too allow superuser, but superuser never asked to allow anything on the phone? Phone just sits there?
Running silky smooth. I'll report errors if they arise.
s0dhi said:
Running silky smooth. I'll report errors if they arise.
Click to expand...
Click to collapse
When you run the .bat file did you have too allow superuser on the phone?
JayRolla said:
When you run the .bat file did you have too allow superuser on the phone?
Click to expand...
Click to collapse
Yes. There are 3 (I think?) points at which you have to allow superuser.
The user interface for the install is really well done.
JayRolla said:
When you run the .bat file did you have too allow superuser on the phone?
Click to expand...
Click to collapse
Never mind had to reboot phone a few times and then it worked.
Ririal said:
To Do
bootanimation - Anyone up to making one is welcome, I'm bad with graphics :x
preferred install location - Need to figure out how to do this.
kill sound on sd mount - Possible?
Fix typo in splash screen - Sigh.
Click to expand...
Click to collapse
there are a handful of boot animations here if anyone is interested. if there's something in particular you want, i'd be happy to give it a go. i too suck at the whole graphics thing, so i wouldn't expect too much.
Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.
This is after you have done retain root and updated and the afterupdate retain root.
Sent from my MB860 using XDA Premium App
xyrovice said:
Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.
Click to expand...
Click to collapse
You need a 1.57 rooted to proceed with this as it says in the OP. if you are at 1.26 rooted then use the retainroot in xda to get rooted on 1.57 and then use this.
Will this work on the Atrix on Bell?
itsonlym3 said:
there are a handful of boot animations here if anyone is interested. if there's something in particular you want, i'd be happy to give it a go. i too suck at the whole graphics thing, so i wouldn't expect too much.
Click to expand...
Click to collapse
I was looking for a custom one. I have a friend who's going to be whipping up some images for me, but you're welcome to take a stab at it.
xyrovice said:
Please pardon my ignorance, but a few questions:
1) I'm basically on stock 1.26 right now (rooted). Would I have to first flash/ota update to 1.57 (while retaining root and whatnot) and only then be able to install this?
2) or is 1.57 packaged within this and I just have to flash a clean 1.26, retain root, etc. and then flash this, thus updating me to 1.57 via this ROM?
I know they're somewhat silly questions, it's just that a LOT of what I've been looking for in a ROM lately is (almost literally) a one click to 1.57+root.
Thanks for bearing with me...and any kind of ETA on an RC? I see you were up until 5 putting this together, so thanks for your hard work.
Click to expand...
Click to collapse
This rom does not update you to 1.57. You will need to be on 1.57 with root before this will work.
jayhammy said:
Will this work on the Atrix on Bell?
Click to expand...
Click to collapse
No, it will not.
I have a 1.57 w/ root (using before/after update script). Will Deodexing my Atrix make it faster/snappier?
kpfury said:
I have a 1.57 w/ root (using before/after update script). Will Deodexing my Atrix make it faster/snappier?
Click to expand...
Click to collapse
A bit, yes.
Ririal said:
To Do
kill sound on sd mount - Possible?
Click to expand...
Click to collapse
If you figure this out please share how you did it.
I don't think that sound can be killed. But then again I'm no expert. Also are there any known issues with GladiAtrix?
I have it installed but can't really tell for now. Great great work man!!
Any chance of some screen shots of this theme? If we had CWM I would just flash and check it out.Thanks.
Sent from my MB860 using XDA Premium App
[MOD] tabletUI on AOSP/CM10.1/CM10.2 - Auto-Patcher >>UPDATE: AOSP 4.3 supported!!<<
tabletUI for ANY DEVICE running AOSP, CM10.1, or CM10.2
{
"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"
}
Check out post 2 for way more screenshots!
All you need is to get the latest version of the Auto-Patcher.(or ApG)
Linux/Mac: Check out mateorod's thread for instructions on getting the auto-patcher set up and how to use it.
Windows: Check Kobik77's post on ApG and download the latest version of ApG, which puts everything you need to make these patches together for you automatically!
Once you have that all set up just run your favourite AOSP, CM or SlimBean rom through the auto-patcher, patching for tabletUI. Auto-patcher will automatically detect your rom type and use the appropriate patches. It really could not be any easier!
(In ApG if you must set the rom type then use AOSP for Slim)
Make A Backup Before Trying Any Of These Mods! I will not be responsible for your data loss.
The Auto-Patcher will produce an update.zip and a restore.zip. I recommend moving both to your device before flashing.
Flash the produced update.zip in recovery and reboot.
Enjoy the tabletUI goodness!
If you do experience any issues, or your device bootloops, or you just want to go back to the way things were before applying the tabletUI mod, boot into recovery and flash the restore.zip. This will replace ALL of the original rom files and you should be able to boot up normally.
Confirmed Devices (Roms):
Nexus 7 - 2013 (AOSP/CM)
Nexus 10 (AOSP/CM)
Nexus 7 (CM)
Galaxy Tab 2 (AOSP/CM/SLIM)
Asus Transformer TF101 (CM)
Nook Color (CM)
Motorola Xoom (CM) - Thanks LQQKS!
Acer Iconia A500 (CM) - Thanks rsriram22!
Galaxy Grand Duos GT-I9082 (CM) - Thanks @karipari95! (who says setting dpi to 160 perfects the tablet look!)
If you have just patched a new device, not on this list let me know so I can add it!Known Issues:
This mod is going away from what android has been moving toward for a few months so there are a few issues with some android features. I personally think that the gains outweigh the losses in this, but depending on your device usage YMMV.
Multi-User: If you use multiple users on your device then this mod is probably not going to work well for you. In tests it seems that any user will get the notifications for all users. They can't be clicked but they do come through and can be seen.
Encryption: I have had a report that enabling Security/Encrypt tablet in conjunction with tabletUI mod will lead to a boot loop.
Notifications: Most notifications will work fine, however certain ones will not be seen:
Storage related notifications may not be seen. For instance the popup to enable mass storage when you plug into your computer.
Persistent Alarm Notification will not be seen when you have the alarm set.
Preferences: Sometimes certain options in Settings (having to do with appearance) will either no longer be present, or will have no effect when changed.
Launcher/Apps: On devices with smaller screens and lower resolutions the default launcher may not look very good after applying tabletUI mods. I recommend using a custom launcher from the play store, like Nova/Holo, which let you customize appearances. Also some apps may appear a little odd, or be missing content. This only affects small, low-res screens and is minimal.(see Youtube: missing/squished "Like"/"Subscribe" buttons)
Bugs/Requests:
If you have to report a failed attempt at patching a rom please include as much detail as you can, including the log from auto-patcher (full log please, not copy/paste of terminal output) and the rom and device you are trying to patch for (link to thread/source appreciated)
Please do not report failures for roms other than those stated as working in this thread; currently AOSP, CM10.1, and SlimBean.
Please do not post requests for support for roms which are not currently supported.
Be aware that some roms which are called "AOSP/AOSP based" are actually heavily modified by their developer already and these patches may fail in that case.
If you need to report an issue with some function that worked on your device before flashing the tabletUI mod but isn't working after, a log of the failure can be very helpful in coming to a solution, and is appreciated. Please check the Known Issues above before reporting.
Thanks/Credits
mateorod & pastime1971 for the amazingly versatile Auto-Patcher!
kobik77 for ApG which really makes the Auto-Patcher accessible for everyone!
barrmulio for all his work on tabletUI!
All the happy, willing testers: brGabriel, 138, 19cam92, dlumberg, astro_75, rraaka, tuxafgmur, and anyone else I am forgetting! Without you...:crying:!
All the awesome, talented developers on XDA that bring us these great roms for our devices! Thanks to each and every one of you for helping make this community what it is!
All my fellow tabletUI fans out there, who don't want to accept an awkward user interface!
Anyone else who has slipped my mind at the moment, and anyone who has ever contributed anything to XDA you're great too!:highfive:
Screenshots:
Galaxy Tab 2 7.0: CM10.1 (for more see here)
Galaxy Tab 2 7.0: SlimBean
Galaxy Tab 2 10.1: CM10.1 (for more see here)
Nexus 10: CM10.1
Nexus 10: AOSP
Asus Transformer TF101: CM10.1
one more just in case
Thank you but still getting the same error with Team EOS4 rom (tf101)
http://codepad.org/S3qVlSss
i9apps said:
Thank you but still getting the same error with Team EOS4 rom (tf101)
http://codepad.org/S3qVlSss
Click to expand...
Click to collapse
That's because there aren't patches for Team EOS roms. Right now your choices are either AOSP, CM10.1, or Slim.
"Recent Apps" style?
Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".
SGH-i200 said:
Maybe I didn't get it right but after patching my CM 10.1 on my Nook Color the "Recent Apps" button still shows the phone style not the tablet one Recent Apps view!? Maybe this should be added to "Known Issues".
Click to expand...
Click to collapse
Thank you for the report. I guess to be honest I don't really think of this as an "issue" but I guess that you are right. At best it is still a shortcoming in acheiving what you would expect as tabletUI. I will have to see if I can get it to look like in Honeycomb, where it was a column view, pushed to the left of the screen. That is the way that you mean, right?
@SGH-i200
I think that I got it all sorted out the way you would like. I will try to include this fix in the auto-patcher the next time I update the tabletUI patches. It does look better this way, thanks for the push!
Awesome work Caldair!
Well done. Thanks for helping us Slimbeaners keep our phones secure.
Do you know what the GsmServiceStateTracker.smali does?
I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.
It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.
Oddly it wasn't there on build 2.5
Anyways, thanks again for all your help in making Slimbean a safe rom.
Didgesteve said:
Well done. Thanks for helping us Slimbeaners keep our phones secure.
Do you know what the GsmServiceStateTracker.smali does?
I see this error when I am compiling the latest Slim 4.2.2 build 4 patch.
It still completes the patch, and the patch works with no problems. Some people on the Slim thread have reported problems with Google maps, but as I have maps & network location disabled, I can't say.
Oddly it wasn't there on build 2.5
Anyways, thanks again for all your help in making Slimbean a safe rom.
Click to expand...
Click to collapse
Sorry, I don't know anything about that. I saw your post at the auto-patcher main thread as well and I think you have the wrong impression. This thread is meant to be for discussion of the tabletUI mod part of the auto-patcher. Your question would be better in the main thread, and trust me, those guys are way smarter than me anyway.
Updates were just pulled into auto-patcher. ApG users can try the newest patches right now, otherwise you could pull from Mateor/auto-patcher on github or wait for the next auto-patcher release.
Huge thanks to tuxafgmur for all the work he did on streamlining these patches!:good::good:
These changes help reduce the extra load that tabletUI seems to put on the gpu!
Also fixed the 'latest' symlink in the CM patch so you should be able to use multiple auto-patcher mods together with tabletUI (ie. pdroid)
And I changed the appearance of the recent apps panel so it is more similar to the old style tablet recent apps (similar to the pictures I posted a couple posts back), hope you like it!
hey mate,
i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.
i've already seen that someone did it successfully on the Xoom wingray.
but when i try : it fails to extract the build prop
hopefully the attached AP log will tell you something
this is on the most recent version of APG
LQQKS said:
hey mate,
i'm trying to patch this mod into my cm10.1 rom on Xoom MZ601 everest.
i've already seen that someone did it successfully on the Xoom wingray.
but when i try : it fails to extract the build prop
hopefully the attached AP log will tell you something
this is on the most recent version of APG
Click to expand...
Click to collapse
From the look of your log I think there is something wrong with your ApG installation.
I have never used ApG, as I don't use windows, so unfortunately I can't really be very helpful with this issue. But the patcher really should be working for that rom.
Maybe you could try completely removing ApG and starting fresh, that may help. I hope!
OK I will try that when I get home
and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently
Thanks for the help
Edit: working now \o/ I had a bad download of the rom, everything else was sweet feels like a complete n00b
You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/
Sent from my rooted Xoom MZ601
running Elemental CM10.1
using XDA Premium app \o/
LQQKS said:
OK I will try that when I get home
and I've found a patched version that I'm running but I'd like to do it myself as I update CM10.1 frequently
Thanks for the help
Edit: working now \o/ I had a bad download of the rom, everything else was sweet feels like a complete n00b
You can add Xoom MZ601 Everest to list of confirmed working devices (CM10.1) thanks heaps Caldair for the awesome mod \o/
Sent from my rooted Xoom MZ601
running Elemental CM10.1
using XDA Premium app \o/
Click to expand...
Click to collapse
Glad to hear it!
And don't worry we all fall victim to the simplest mistakes. They are never simple until you find the solution, and they are usually the most frustrating to solve!
Thanks for sharing your success:highfive: I will add the Xoom to confirmed devices!
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Edit: Well I got my feedback... and it was not good:crying: To make matters worse I have since read in one of the EOS threads that bigrushdog is working on bringing tabletUI back into these roms anyway, so I am just going to leave this for now. You EOS users should have your tabletUI back before you know it anyway!
ATTACHMENTS REMOVED.
Caldair said:
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Click to expand...
Click to collapse
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"
I click OK and it immediately pops up again.
Let me know if there's something specific you'd like me to try that will help you debug.
Caldair said:
@i9apps @rafal.k
For all you teamEOS users out there I have put together a test build of the Auto-Patcher that will patch your EOS roms for tabletUI!
I made test patches for Asus Transformer tf101. These zips are based on the build dated: 2013-05-05 from http://goo.im/devs/teameos/roms/eos4/nightlies/tf101 and must be used on that build and only on the tf101: The top 2 attachments are for the tf101.
I also made test patches for the Motorola Xoom Wingray model. These are based on the build dated 2013-05-04 from http://goo.im/devs/teameos/roms/eos4/nightlies/wingray and must be used on that build date and only on the Wingray: The bottom 2 attachments are for the wingray.
I don't have either of these devices to test and there is no EOS rom for the tablets that I do have so be warned:
These are completely UNTESTED! Be sure to download both the update and restore file and have them both on your device before flashing the update.zip in recovery. This way if you have issues like boot loops all you need to do is get back in recovery and flash the restore.zip to have all the original rom files back.
I hope to get some feedback on whether these patches work or not and then I can procede with getting EOS roms supported in the Auto-Patcher for TabletUI. Then EOS users with any device should be able to make these patches for any build!
I anxiously await your feedback:fingers-crossed:
Click to expand...
Click to collapse
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.
drewski_1 said:
I tried the Xoom version and as soon as it enters the OS I get a neverending "Unfortunately System UI has stopped"
I click OK and it immediately pops up again.
Let me know if there's something specific you'd like me to try that will help you debug.
Click to expand...
Click to collapse
Gatak said:
Tried with nightly 112 for TF101. Did not work. System UI kept crashing and I could not use the pad. Had to wipe system and reinstall without this.
Click to expand...
Click to collapse
Thanks to you both for testing this! I am sorry that it failed so miserably and you had to wipe and reinstall.
For now I will take a closer look at the patches themselves and the sources. There is definitely more going on in EOS roms than other AOSP/based roms, especially in SystemUI.apk.
Gatak, I would have said your issue could have been caused by the fact that you tried to flash the update over a newer build than the modded files came from, but since drewski_1 had the same exact issue I think the patches are probably not right.
Drewski_1, I am assuming that you did flash the update on a wingray model and that you were running the corresponding build of the rom, dated 2013-05-04. If that is not the case, and you are also using a newer (or older) build, please let me know.
These patches can really screw up when used on different nightly (or weekly or whatever the build frequency is for EOS) builds than they were based on. Devs can change a lot in a week, and these patches contain important core files.
Thanks again to you both, I really want to get EOS working. I see how many downloads there are of these roms from goo.im, just for these 2 devices, so I know a lot of people would benefit from this.
CyanogenMod 10.1 working on the Archos 80 Cobalt!
This is oma7144's ROM, I've been able to get it running under a bit of guidace from oma and I thought I'd share it here if anyone else is interested.
The original thread is here - but this ROM is designed for Odys Genio tablet, which has basically the same specs as the 80 Cobalt. (RockChip 3066 chip)
As always, only flash if you know what you are doing, I am not responsible for anything you do or break.
New Version 1.3.4
Thanks danielo83 for putting this zip together
Oma CM10.1 v1.3.4
Battery problem fixed and ROM is now ready for daily use
- CWM 6.0.1.5 recovery
- System ext4
- Internal Storage 2,5 GB
- PhabletUI & Multiuser
- Device spoofed as Nexus
- Ethernet Support
- Init.d support
- USB-Hub enabled
- Gameloft compatible
- Gamepad (PS2, XBox, ...)
- Kernel modules (cifs, tun, lan, serial)
- latest hosts, su, su-binary, busybox
- MX Video-Player, Apollo & FX Sound
- Reboot Menue, CPU Tweaker, Pimp my Rom
- Dateimanager HD (Root)
- Trebuchet & Nova Launcher
Instructions
Before you do anything, download the file below and extract everything to your desktop, find 'Oma RK30 CM10.1 Format NAND.zip' and copy to your externalSD card
then unmount and remove the externalSD, this is very important because if you try to boot after flashing the rom, you will not have access to the internal SD - which means you can't flash files from CWM or do anything basically
Boot to bootloader
Turn off the tablet
Unplug from charger and USB
Hold the 'volume down' button and then hold the 'power button' to turn the device on and boot into bootloader, keep holding both until you see the boot screen
Connect USB and you will get "Unknown Device" message in windows
Install device drivers included in the zip below under x64 or x86 depending on your system - see gavroche's root thread if you are having trouble
Open up RKandroidTool.exe as administrator (located in RKDevelopTool_v1.35 folder)
- if you have trouble try different USB ports on your computer
You should see at the bottom of the RKAndroidTool "Found RK Android Loader Rock USB"
Click 'erase IDB' button - this will only take a few seconds
Now click 'Run' button, this will take a few minutes to install the ROM
Insert your external SD card
The device will boot into CWM, now choose install zip from sdcard (not internal), install Oma RK30 CM10.1 Format NAND.zip that you copied to your external SD earlier
Reboot, and enjoy CM10.1
--------------------------------------------------------
Downloads
http://www.mediafire.com/download/15wh4o4xwhec11o/OMA_4.2.2_CM10.1_Rom.zip
--------------------------------------------------------
What is working
Wifi
Camera
Display
Touchscreen
Battery info showing
...everything apart from mentioned below
Known Problems -
Scren flicker when rotating screen,
When battery is low the tablet wont wake up from sleep and the power button will only reboot it instead of waking it up
- Thanks to danielolsman
- To "fix" this you could install "no sleep" from the play store.
--------------------------------------------------------
If anyone is interested in helping get rid of these three problems please don't be shy.
I'm not a dev and I'm looking at fixing the bugs but don't really know where to start...
Credits
oma7144, gavroche
kage00,
Thanks for your effort!!! You're breathing new life into our tablets. We (I am sure there's a very big community alongwith me) who have been waiting for this.
I don't have my cobalt with me right now but will try and install at some point and feedback how it goes.
Are you also willing to work actively on issues and improvements. I am happy to help wherever I can. Perhaps, others will join in as well.
Thanks
Looking at the forum feedback from HUKD, the rom is not far from being a stable rom for day to day use. I see following general issues raised with this rom so far
1. Waking up issues after deep sleep in case when the battery is low
2. Rotation issues
3. Default language
4. Nexus port and therefore certain apps incompatibility
As mentioned earlier, I am happy to help wherever I can.
Thanks
Hey nikunj87,
Thanks for your support! I would love to be able to work on the issues with this rom but to be honest, I'm not a dev, not even close, and I wouldn't even know where to begin to start fixing the problems.
For the moment I'm looking at putting together a kernel from Archos' source and adding overclocking, I've never built a kernel before so it's a learning curve... don't hold your breath, haha!
I just thought I'd post this rom here to see if we could get some interest in the project and maybe get a dev's (or two's) attention to take a look at the problems, but for the moment it's just you and me who are interested in this..
I think the best we can do is wait for an update to this rom from Oma (the original dev), as you mentioned all the problems with this rom on the cobalt are problems that exist with the same rom on other devices. So maybe with a new update it will work a bit better.
Unless if we can get someone else who knows what they are doing to take a look at it...
kage00 said:
Hey nikunj87,
Thanks for your support! I would love to be able to work on the issues with this rom but to be honest, I'm not a dev, not even close, and I wouldn't even know where to begin to start fixing the problems.
For the moment I'm looking at putting together a kernel from Archos' source and adding overclocking, I've never built a kernel before so it's a learning curve... don't hold your breath, haha!
I just thought I'd post this rom here to see if we could get some interest in the project and maybe get a dev's (or two's) attention to take a look at the problems, but for the moment it's just you and me who are interested in this..
I think the best we can do is wait for an update to this rom from Oma (the original dev), as you mentioned all the problems with this rom on the cobalt are problems that exist with the same rom on other devices. So maybe with a new update it will work a bit better.
Unless if we can get someone else who knows what they are doing to take a look at it...
Click to expand...
Click to collapse
willing to lend a hand tho I am only new to this stuff as well!
I tried this ROM, it seems that OMA posted an AKKU Fix here
I will trie it soon....
There are some problems with the camera; its inverted. The provides fix did not solve the problem, does someone know how to fix it ?
Akku fix does not work
Sent from my Nexus 4 using xda app-developers app
Cool! looks like we've got some attention from the devs!
So there is a new version of this ROM over at this thread
edit ----> please take note, if anyone tests this ROM you will need to keep the same kernel from the existing package in OP and use that to flash with new ROM, Otherwise you risk having a bricked device
Aparently the battery problem exists, but netlars has a possible fix on this thread if anyone can test it that would be great. My tablet is off getting fixed, I had some problems with the touchscreen.
Also Oma was asking if anyone could test this too
Are these paths there?
/sys/devices/platform/rk30-battery/startget
/sys/class/rk30_battery/rk30_battery_start_timer_work
Click to expand...
Click to collapse
If anyone can test and reply here please, then I can tell him on the other thread.
Thanks
Battery problem is solved (see original thread)
CM10.1 is now ready for daily use.
(@Kage00: maybe its possible for you to make a new zip package with the new boot image found here?)
EDIT:
made a zip package myself : CrewRKTablets_RK30_Cobalt 80 by Oma_CM10.1_v1.3.4.zip
Thanks danielo83,
Nice one, I'll update the OP,
I got news back from Archos repair about my tablet / touchscreen problem. They decided to replace the whole unit, so I'm going to sell the brand new one and get a Nexus 7, which means I won't be able to play around with this ROM anymore becuase I won't have the tablet. I'm happy to still keep the thread open and you guys can tell me if there's anything to update in the OP
Thanks
edit----------
In the new version do you still have the screen flicker artifacts on rotate?
danielo83 said:
Battery problem is solved (see original thread)
CM10.1 is now ready for daily use.
(@Kage00: maybe its possible for you to make a new zip package with the new boot image found here?)
EDIT:
made a zip package myself : CrewRKTablets_RK30_Cobalt 80 by Oma_CM10.1_v1.3.4.zip
Click to expand...
Click to collapse
Not sure if anyone will see this but I own an unrooted/untouched Archos 80 Cobalt which I haven't used for months. Decided to dig it out for my son to play with but I can hardly fit any apps on it so looking in to alternative roms.
Came across this rom which I want to flash but I'm unsure on how to start. Do I have to root and flash CWM on to the tablet before doing anything in this thread or are the instructions in this thread all that I need to do in order to flash this rom on to an unaltered tablet?
Yes you will need to be rooted first before using this ROM, please follow this thread to get root and CWM on your tablet then you can flash this ROM with the instructions in the OP
Yeah the storage space is limited for some stupid reason on the stock ROMs, that shouldn't be a problem on this ROM, also if you find you dont like this ROM there is also another custom ROM here based on stock 4.0.4 firmware with better app storage space
the new version still has the rotate "problem".
Sent from my Nexus 4 using xda app-developers app
I just wanted to say as well, that Archos have released kernel sources (downloadable from their website) that are from May or June 2013 from memory. The last stock ROM built for this device was released in February 2013. Which means if anyone wants to try their hand at compiling the kernel from Archos source, it would be a newer kernel than what you are using now and it could possibly fix any left over problems with this ROM. I don't have any spare time to do it anymore, but if anyone was interested I'm sure you could find a walkthrough on XDA to tell you how to do it easily enough.
The kernel for this ROM at the moment is still the stock kernel from the stock 4.0.4 ROM, which is working, but maybe if a newer kernel was made from the sources it may work a lot better
app space and vold.fstab
Does anyone know if this ROM exists with 6gb of app space? I currently have the supersport ROM with 6gb app space and edited the vold.fstab to swap the internal and external sd cards. I’d like to do the same with this JB ROM.
How difficult would it be to edit the ROM to change the app space?
Does this ROM use the vold.fstab to set where the internal and external sd cards are mounted? (I think this has been changed in JB 4.3 but I’m not sure about 4.2.2)
Cheers, T
To be honest I'm not sure if it is possible, but you could ask the devs who made the ROM they would probably be able to tell you if it was possible or not. Have a look over at http://www.arctablet.com
You'd need to ask oma7144 or netlars
You could try to post in this thread and see what they say
kage00 said:
Yes you will need to be rooted first before using this ROM, please follow this thread to get root and CWM on your tablet then you can flash this ROM with the instructions in the OP
Yeah the storage space is limited for some stupid reason on the stock ROMs, that shouldn't be a problem on this ROM, also if you find you dont like this ROM there is also another custom ROM here based on stock 4.0.4 firmware with better app storage space
Click to expand...
Click to collapse
Can you please tell me why I'm getting this error when trying to follow the root instructions from?
http://forum.xda-developers.com/showthread.php?t=2066972
{
"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"
}
I'm using Windows 8.1 64 bit
I'm doing this with USB debugging enabled and the device switched on as this is the only way I can get the 'ARCHOS' device to show in Device Manager under 'Other Devices.
If I put the tablet in to download mode (power + vol down) I get a dead Android symbol with red exclamation, is this normal? However when I insert USB cable in to the device at this point my computer doesn't bring up the 'ARCHOS' device in Device Manager...
All I get then is this:
I don't actually have this tablet anymore, but I remember mine being a bit strange when I first tried to root it too. It can be a bit temperamental... I remember reading someone saying somewhere about leaving the charger plugged in when trying to reboot into download or recovery mode, if that doesn't work try with the USB cable (or both) plugged in while you try.
I also remember with mine I had to direct windows to the specific driver folder extracted from the zip based on which drivers you need, eg, x86 or x64 etc.
You could also look at this thread http://www.freaktab.com/showthread.php?3244-Archos-80-Cobalt-900-supersport-rom where the might be more info on root.
I'm using windows 7 though, so I don't know exactly what differences there are with win 8.
If all else fails just keep searching and reading all/any forums you can find about rooting the thing, I'm sure you'll find that someone has had the same or similar problem
good luck
kage00 said:
I don't actually have this tablet anymore, but I remember mine being a bit strange when I first tried to root it too. It can be a bit temperamental... I remember reading someone saying somewhere about leaving the charger plugged in when trying to reboot into download or recovery mode, if that doesn't work try with the USB cable (or both) plugged in while you try.
I also remember with mine I had to direct windows to the specific driver folder extracted from the zip based on which drivers you need, eg, x86 or x64 etc.
You could also look at this thread http://www.freaktab.com/showthread.php?3244-Archos-80-Cobalt-900-supersport-rom where the might be more info on root.
I'm using windows 7 though, so I don't know exactly what differences there are with win 8.
If all else fails just keep searching and reading all/any forums you can find about rooting the thing, I'm sure you'll find that someone has had the same or similar problem
good luck
Click to expand...
Click to collapse
Hi do you have any idea how to get XBMC working with this rom? XBMC just goes back to home screen whenever i try launching it?
For xbmc you will need an older version of it. The one from August seemed to be the one to use for most people with the same issues on the HP slate 7 so am guessing it will sort your issue too. A quick search on Google should locate the archives for you
Sent from my ARCHOS 80G9 using Tapatalk
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
strazicic said:
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
Click to expand...
Click to collapse
No. Neither http://forum.xda-developers.com/member.php?u=3081699, nor http://forum.xda-developers.com/member.php?u=5019846 have this device. And there are no other developers with GT8.9.
DemonGloom said:
No. Neither http://forum.xda-developers.com/member.php?u=3081699, nor http://forum.xda-developers.com/member.php?u=5019846 have this device. And there are no other developers with GT8.9.
Click to expand...
Click to collapse
As you should remember, Arlic was the only dev of p7320 but unfortunately he disapeared suddenly...
Anyway, I am still satisfied on his rom:
http://forum.xda-developers.com/showthread.php?t=1923371
btw. there are some November's releases of stock roms at sammobile.
It is still 4.0.4 but I wonder if it comtain any improvements over previous builds?
Is your 7320 on Tegra or some diffrent SoC? I cant find reliable info...
pax0r said:
Is your 7320 on Tegra or some diffrent SoC? I cant find reliable info...
Click to expand...
Click to collapse
p7320 - SoC Qualcomm (2x1.5 Ghz, Adreno 220)
p7300/p7310 - Tegra 2
strazicic said:
hello there,
I know not many people own model 7320.
There is no updates or new ROMs at all for it
Was wondering if there is some developer that is willing to port some other ROM (4.3) to our (my) device
I am willing to start some support actions for that.
I love my tablet but software is too old...
Suggestions welcome
Click to expand...
Click to collapse
I have just made a new kernel, but it is based on ICS.
You can get it here:
Downloads:
https://sourceforge.net/projects/kernel-p7320t-ics/files/
Source:
https://github.com/CL0SeY/kernel_P7320T_ICS
The features so far are:
Interactive CPU governor available for selection (was left out of the stock kernel for some reason). If you want to enable this governer you will need to firstly get ROOT for the tablet, and then install some app to control it, e.g. Voltage Control. If you enable this, it should give you a more responsive tablet, compared to using the default ondemand governer.
Max CPU frequency "UNICPU" bumped to 1512MHz from 1242MHz. This is the maximum frequency that you will see the tablet sitting on at times. If you are concerned about battery usage you can tweak this the maximum frequency value down using using Voltage Control or other apps.
USB charging and notification, as per glitschi667 / pershoot's patch, which was previously in a honeycomb custom kernel: http://forum.xda-developers.com/showthread.php?t=1569122 . The tablet will show as charging when plugged into a PC with enough power, whereas previously you would see the red X over the battery icon.
Wow!
Do yoy think it will work with Arlic's ROM (I am still on)?
Does it actually change charging method or just change the visualisation of the status (i.e X replaced by powering)?
Many, many thanks !!!,
I hope it is just the beginning of your magic here...
janla said:
Wow!
Do yoy think it will work with Arlic's ROM (I am still on)?
Does it actually change charging method or just change the visualisation of the status (i.e X replaced by powering)?
Many, many thanks !!!,
I hope it is just the beginning of your magic here...
Click to expand...
Click to collapse
Not too sure if it will work with Arlic's ROM. You could give it a go at your own risk, if you were keen.
The USB charging is more than just a display thing, it should work the same as glitschi667 / pershoot's one. I didn't want to advertise the charging capabilities too much without trying it myself but I can report now that it seems to charge fine off my laptop.
I will probably try next flashing the AOKP test build from the i957 forum as people have reported that it works, to some extent. I shall report back.
CL0SeY said:
Not too sure if it will work with Arlic's ROM. You could give it a go at your own risk, if you were keen.
The USB charging is more than just a display thing, it should work the same as glitschi667 / pershoot's one. I didn't want to advertise the charging capabilities too much without trying it myself but I can report now that it seems to charge fine off my laptop.
I will probably try next flashing the AOKP test build from the i957 forum as people have reported that it works, to some extent. I shall report back.
Click to expand...
Click to collapse
I have a preliminary GT-P7320T AOKP 4.1.2 ROM working based off dan-htc-touch's http://forum.xda-developers.com/showthread.php?t=1899018
I had to change the mount point for /data inside the fstab.qcom file inside the boot.img. It has to be
/dev/block/mmcblk0p28
and NOT
/dev/block/mmcblk0p26
I will hopefully report back soon. If this turns out to be all the "migration" that we need to use ROMs from the SGH-i957, it's looking good. Beware though that while they have a few devs working on ROMs it isn't extremely active over there either (http://forum.xda-developers.com/galaxy-tab-8-9/i957-development)
CL0SeY said:
I have a preliminary GT-P7320T AOKP 4.1.2 ROM working based off dan-htc-touch's http://forum.xda-developers.com/showthread.php?t=1899018
I had to change the mount point for /data inside the fstab.qcom file inside the boot.img. It has to be
/dev/block/mmcblk0p28
and NOT
/dev/block/mmcblk0p26
I will hopefully report back soon. If this turns out to be all the "migration" that we need to use ROMs from the SGH-i957, it's looking good. Beware though that while they have a few devs working on ROMs it isn't extremely active over there either (http://forum.xda-developers.com/galaxy-tab-8-9/i957-development)
Click to expand...
Click to collapse
OK, so for the game people here that want to try this out... ensure you have a stock image from sammobile ready to plonk back on your device if you're unhappy with it...
Also once I get enough posts up I might be able to make a thread in the appropriate forum
ROM (flashable CM zip): aokp_p7320t_DannoRom_Nov-03-12.CL0SeY.20131124.zip (https://drive.google.com/file/d/0B48JIYNc4wvsT2txZS16WGV0MUE/edit?usp=sharing)
GAPPS required: http://goo.im/gapps/gapps-jb-20121011-signed.zip
Procedure:
(This has only been tested moving from a STOCK ICS ROM. Unsure if it will work for Arlic's ROM. If it all goes wrong try from a stock ICS ROM.)
Ensure you have a CWM recovery installed, see http://forum.xda-developers.com/showthread.php?t=1569122
* Copy the zips to your tablet
* Reboot into recovery
* WIPE data
* Install aokp_p7320t_DannoRom_Nov-03-12.CL0SeY.20131124.zip
* Install gapps-jb-20121011-signed.zip
* Reboot and enjoy!
Known working:
* Display
* 3G/4G/LTE
* Wifi
* Sound (headphones, speakers)
Known issues:
* Google play store seems to lose its network connection after a while. This seems to be a common problem amongst other ROMs.
* Plenty that we don't know about yet
{
"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"
}
CL0SeY said:
OK, so for the game people here that want to try this out... ensure you have a stock image from sammobile ready to plonk back on your device if you're unhappy with it...
Also once I get enough posts up I might be able to make a thread in the appropriate forum
ROM (flashable CM zip): aokp_p7520t_DannoRom_Nov-03-12.CL0SeY.20131124.zip
Click to expand...
Click to collapse
Great work!
I am going to give it a try next weekend or so.
Need to be sure no reverting problems will be while downgdading,
Definitely you should start new tread.
There is a typo in the filename of the rom?
should be p7320 instead p7520.
janla said:
Great work!
I am going to give it a try next weekend or so.
Need to be sure no reverting problems will be while downgdading,
Click to expand...
Click to collapse
Do you mean about going back to stock after trying it out? I have tried it myself going back to the sammobile OTA image fine.
janla said:
There is a typo in the filename of the rom?
should be p7320 instead p7520.
Click to expand...
Click to collapse
Yes! Thanks for picking that up... I was making the ZIP in a bit of a hurry It's definitely a typo.
---------- Post added at 05:26 PM ---------- Previous post was at 05:19 PM ----------
CL0SeY said:
Yes! Thanks for picking that up... I was making the ZIP in a bit of a hurry It's definitely a typo.
Click to expand...
Click to collapse
And the file is now named correctly
I have also succeeded in booting this ROM (CM10/JB 4.1) by using the same minor modification, but haven't uploaded my version for p7320 yet:
http://forum.xda-developers.com/showthread.php?t=1867579
It seems to be a smoother build than the AOKP one. If anyone wants me to upload it please let me know.
Also, if techy people are interested, I can make up a short guide for making a P7320 ROM out of a SGH-i957 ROM. This might be better for the "long term evolution" (pun intended ) of the tablet. But let me know if there is demand for it.
CL0SeY said:
I have also succeeded in booting this ROM (CM10/JB 4.1) by using the same minor modification, but haven't uploaded my version for p7320 yet:
http://forum.xda-developers.com/showthread.php?t=1867579
It seems to be a smoother build than the AOKP one. If anyone wants me to upload it please let me know.
Also, if techy people are interested, I can make up a short guide for making a P7320 ROM out of a SGH-i957 ROM. This might be better for the "long term evolution" (pun intended ) of the tablet. But let me know if there is demand for it.
Click to expand...
Click to collapse
OK guys, here's a nice little nugget for the weekend.
I've followed the instructions for making a CM10 ROM for the i957 above, and simply changed the mount point and have it working on the P7320.
The ROM (cm-10-20131130-UNOFFICIAL-p7320.zip) should appear in this folder as soon: https://drive.google.com/folderview?id=0B48JIYNc4wvscVpIZkRKZWd4RmM&usp=sharing
I've tested wifi, 4g, and that is about it. Once again flash at your own risk yada yada yada...
MASSIVE thanks to @nrvate for the guide! I would like to see if we can do something potentially with the upgrade scripts to make them generic. between the p7320 and i957. I suspect this ROM will work fine on the i957 with the reverse fix (ie. make it use mm block 26 instead of 28).
Also I will make a proper thread for this work soon enough...
thanks a lot for participating CL0SeY
It is great that we are moving somewhere ...
I have wish to start working on cooking but building house and 2 little children are taking all of my time (with full right
Where do people think the p7320 dev stuff should go? The I957 is sui similar, but I think people will find it easier in the other development section?
CL0SeY said:
Where do people think the p7320 dev stuff should go? The I957 is sui similar, but I think people will find it easier in the other development section?
Click to expand...
Click to collapse
I think that the "Galaxy Tab 8.9 Android Development" is the right place.
Oh, btw... I installed the CM10 to my P7320 and currently testing everything...
Issues :
Camera does not work. Camera app starts, but there's no image.
_kankea said:
I think that the "Galaxy Tab 8.9 Android Development" is the right place.
Oh, btw... I installed the CM10 to my P7320 and currently testing everything...
Issues :
Camera does not work. Camera app starts, but there's no image.
Click to expand...
Click to collapse
Same here, thanks for giving it a go and the feedback . Also, the auto brightness seems to be very unpredictable, I think it's something wrong with the values coming back from the sensor.
I've been bashing my head against a wall trying to get us up to at least cm10.1 without too much luck so far. Compiling is quite a slow process even on an SSD, so it can take a while between fixing build errors.
_kankea said:
Issues :
Camera does not work. Camera app starts, but there's no image.
Click to expand...
Click to collapse
There is a patch for the camera in the i957 thread: http://forum.xda-developers.com/showpost.php?p=31382526&postcount=47
I've downloaded it and applied it to my p7320 and it works fine.
I will incorporate it into my next update.
Other things I've noticed:
. The boot animation sometimes displays, sometimes doesn't
. Applications that want to write to USB storage seem to fail
CL0SeY said:
There is a patch for the camera in the i957 thread: http://forum.xda-developers.com/showpost.php?p=31382526&postcount=47
I've downloaded it and applied it to my p7320 and it works fine.
I will incorporate it into my next update.
Other things I've noticed:
. The boot animation sometimes displays, sometimes doesn't
. Applications that want to write to USB storage seem to fail
Click to expand...
Click to collapse
Yeah, camera works now \o/
I read from the i957-thread that the boot animation problem is a known issue...
The vibration seems to be a bit powerless...
But still, I have waited for ages that anything newer than ICS appears for this device. Great job, CL0SeY! :good:
EDIT:
Mobile hotspot function (tethering) does not seem to work...
So some kernel features through q&a
Does this kernel:
1. Play go fetch? No
2. Has this superduper ***No!
3. So this is like stock kernel but better? Yes, as is more up2date
4. Can it offer me better battery life? It might can yes
5. Can it offer me better performance too? Sure!
6. Can it play games that stock kernel cant? Performance wise they should run better
7. Can i quote this #1 post? No! you can't and you shouldn’t
8. Can i flash it on x,y,z rom? See next line:
For cm11 and compatibles
9.How i flash this? See next line:
As usual flash in recovery
Look at 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"
}
Source
Powered by loki flashing script.
Changelog for Rel4
Can you tell us what this Kernel does?
Gamma control?
Under volt?
....
Sent from my SM-N900W8 using Tapatalk
Its just a plain kernel simply updated, wip of course
Sent from my LG-P880 using Tapatalk
Didn't work for me on CM11 1/19, wiped cache and dalvik, flashed kernel then wiped dalvik and cache. Stuck on boot screen and cannot access recovery via power buttons.
Secure booting error
Cause: boot certification verify
You should be able to enter recovery as this only flashes the kernel.
Sent from my LG-P880 using Tapatalk
dont worry about the boot cert error, i already have loki-doki setup ( and a few useless kernel replacement tools) ported if need be/uploaded ( ill get it up after compiling pac), or @Demetris can lokify the boot.img if he wants
Demetris said:
Its just a plain kernel simply updated, wip of course
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Newb question. If the kernel had no added features what is different from stock kernel
Sent from my LG-V500 using Tapatalk
Canadoc said:
Newb question. If the kernel had no added features what is different from stock kernel
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
to test and eventually port the V510 (GPe Version of the LG G Pad, and probably the better kernel to base on going to kk and beyond) kernel to the v500 so that the Gpe Rom can work fully, Demetris from what i have been see might not have the tablet or the V500 version, so he needs testers to get back at him whether it works or not.
EDIT: @ikenvape if you want to give it another shot flash the zip below, it automatically lokifies and reflashes the boot.img so that you can get passed the error, ill think about setting up a thread on this much later...
Warning though, do not flash it on anything else, as there are no checks whether its a V500 or another device and can brick any other non lokifiable device
Demetris said:
You should be able to enter recovery as this only flashes the kernel.
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
Oh man what a ride. Yeah, couldnt get into recovery or reset, the boot error kept popping before i could hit the power button to start the operation. Used lg tools, procedure failed, then ran out of battery on the 2nd go. From there getting into download mode was touch and go. Finally got some juice for another run and was sucessfull according to the pc. The gpad was bootlooping the animation so then I retried manual reset but kept getting 'device needs to be charged more" by this time she was on charge for about an hour. Finally got manual reset to go through and voila. Lost root but not the pad.
Maybe it was a bad flash or d/l which i hope it was, but all in all, it was an entertaining night. Thanks for grabbing this and its definitely progress on the gpe road. :good:
---------- Post added at 03:00 AM ---------- Previous post was at 02:58 AM ----------
darkassain said:
to test and eventually port the V510 (GPe Version of the LG G Pad, and probably the better kernel to base on going to kk and beyond) kernel to the v500 so that the Gpe Rom can work fully, Demetris from what i have been see might not have the tablet or the V500 version, so he needs testers to get back at him whether it works or not.
EDIT: @ikenvape if you want to give it another shot flash the zip below, it automatically lokifies and reflashes the boot.img so that you can get passed the error, ill think about setting up a thread on this much later...
Warning though, do not flash it on anything else, as there are no checks whether its a V500 or another device and can brick any other non lokifiable device
Click to expand...
Click to collapse
Hey thanks man. Ill hold on to it for when i re-root in a bit.
no testers ?
I'am curious to know if it's working or not ( i can't test it for now since i have a week of exams... sure i will test at the end of the week)
Ok guys. i think you must be kidding me.
You scream and yell you want the Gpe Source code fully working on v500 and i see no reports here and only 3 downloads.
Didn’t i ask my self why bother but i do now.
This stays close to public until further notice.
I hope you are happy.
Edit Since the previous post am been getting a lot of pm's and interest on this seems healthy.
Downloads have increased and i know lokified script needs fixing as it doesn’t work now.
So ....
Lets continue the gpe kernel shall we?
Thread re-opened.
Thanks to all xda users for their reports and support on this, i hope for the best :fingers-crossed:
Demetris said:
Ok guys. i think you must be kidding me.
You scream and yell you want the Gpe Source code fully working on v500 and i see no reports here and only 3 downloads.
Didn’t i ask my self why bother but i do now.
This stays close to public until further notice.
I hope you are happy.
Edit Since the previous post am been getting a lot of pm's and interest on this seems healthy.
Downloads have increased and i know lokified script needs fixing as it doesn’t work now.
So ....
Lets continue the gpe kernel shall we?
Thread re-opened.
Thanks to all xda users for their reports and support on this, i hope for the best :fingers-crossed:
Click to expand...
Click to collapse
tried flashing the kernel in the first post with no luck, doesn't even flash so i can't even loki doki it
I'll fix it asap currently busy with slim
Sent from my LG-P880 using Tapatalk
Demetris said:
I'll fix it asap currently busy with slim
Sent from my LG-P880 using Tapatalk
Click to expand...
Click to collapse
no rush man just letting you know
Demetris said:
Ok guys. i think you must be kidding me.
You scream and yell you want the Gpe Source code fully working on v500 and i see no reports here and only 3 downloads.
Didn’t i ask my self why bother but i do now.
This stays close to public until further notice.
I hope you are happy.
Edit Since the previous post am been getting a lot of pm's and interest on this seems healthy.
Downloads have increased and i know lokified script needs fixing as it doesn’t work now.
So ....
Lets continue the gpe kernel shall we?
Thread re-opened.
Thanks to all xda users for their reports and support on this, i hope for the best :fingers-crossed:
Click to expand...
Click to collapse
since i you closed this thread without being able to voice my thoughts, i honestly believe that you pulled the plug a little too early, not only are we a small bunch of users compared to nexus and other tablet makers counterparts, but its it feels like there was no marketing at all, just word of mouth and a few publications pushing reviews (which i still dont understand how only one review noticed the few screen issues most have noticed),
sorry for OT, back on topic since i have the device ill take a look at your zip and see if ill be able to fix it...
EDIT: Took a quick look at the script and it seems the loki tools and script arent in the zip, simple fix which im uploading now
EDIT2: @thoughtlesskyle try it now...
darkassain said:
since i you closed this thread without being able to voice my thoughts, i honestly believe that you pulled the plug a little too early, not only are we a small bunch of users compared to nexus and other tablet makers counterparts, but its it feels like there was no marketing at all, just word of mouth and a few publications pushing reviews (which i still dont understand how only one review noticed the few screen issues most have noticed),
sorry for OT, back on topic since i have the device ill take a look at your zip and see if ill be able to fix it...
EDIT: Took a quick look at the script and it seems the loki tools and script arent in the zip, simple fix which im uploading now
EDIT2: @thoughtlesskyle try it now...
Click to expand...
Click to collapse
still getting a binary error
thoughtlesskyle said:
still getting a binary error
Click to expand...
Click to collapse
whoops didnt upload the right edited one...
one last try
darkassain said:
whoops didnt upload the right edited one...
one last try
Click to expand...
Click to collapse
Giving it a go now, trying the Gpe Rom hopefully this fixes it (I got a feeling there is little chance)
Sent from my HTCONE using Tapatalk
thoughtlesskyle said:
Giving it a go now, trying the Gpe Rom hopefully this fixes it (I got a feeling there is little chance)
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
i believe some of ricardos patches need to be reverted before that, this is mainly a base to build off for @Demetris