This a a CM9 Port for the Thinkpad Tablet made by Jon2555 and me. Its still under development, so you might run into bugs.
You are flashing this ROM on your own risk. It could eat your kittens, steal your breakfast or brick your device!
{
"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"
}
(Higher Resolution)
Requirements:
- A US, UK or WE device (Might also work on others)
- root (obviously)
- CWM
Installation:
- Download xxx.zip and put it on a sd-card
- Boot into CWM (Reboot and press Vol+)
- Make a nandroid backup in CWM!
- Make sure the backup worked!
- Full Wipe (May not be needed if you come from an earlier CM9 version)
- Flash zip in CWM
Restore HC:
- Boot into CWM (Reboot and press Vol+)
- Restore old nandroid backup
Working:
- Wifi
- Touchscreen + Stylus
- Bluetooth
- HW Acceleration
- Sound
- External Mouse
- Folio (mostly)
- VPN
- Hardware Button
Not Working
- Camera
- 3G
- HW Video Decoding (i.e. for Youtube HQ)
- No mount as USB/MTP
Known Bugs
- Wifi doesn't always reconnect to networks
- Trebuchet has wrong size and misses a few pixels
- Sometimes apps on the market are incompatible (see Play Store/Market)
- Sound doesn't mute when headphones are plugged in
Play Store/Market
Sometimes the market marks apps as incompatible. This happens randomly. If it happens to you try one (or more) of the following:
http://forum.pocketables.net/showthread.php?p=80033
http://forum.xda-developers.com/showpost.php?p=23753023&postcount=5
Search here in xda for a hacked market and install it
Reflash the whole ROM
Folio
The Folio works but some of the special keys don't. One problem with the Folio is, that there are different Keylayouts (i.e. UK, US) but without a different device ID. In the standard setup this ROM uses the UK layout, if you want to use a US layout, you have to delete a file:
Code:
su
mount -o rw,remount /system
rm /system/usr/keychars/Vendor_1241_Product_0003_Version_0110.kcm
Thanks:
- The Cyanogenmod team
- digetx for the Green Flash fix
- Everyone releasing their source codes for other builds
- Everyone trying to find and report bugs
If you like our work press the thank button or buy us some lego.
Download
http://everyrandom.com/files/download.php?file=185alpha00731.zip
Sourcecodes
https://github.com/Koshu
Changelog:
Code:
[B]Version 0.0.7.3.1[/B]
- Fixed Pen driver to solve reboot problem
[B]Version 0.0.7.3[/B]
- Added new experimental play store hack v2
[B]Version 0.0.7.2[/B]
- Added new experimental play store hack
[B]Version 0.0.7.1[/B]
- removed assert check again
[B]Version 0.0.7[/B]
- fixed touchscreen scrolling issue
[B]Version 0.0.6.3.1[/B]
- added missing generic.kl again
[B]Version 0.0.6.3[/B]
- Added xt_qtaguid to kernel to solve reboot bug
- Changed some configs to fix minor bugs
[B]Version 0.0.6.1[/B]
- Fixed wrong Generic.kl for folio
[B]Version 0.0.6[/B]
- Fixed Hardware Button Rotate Key
- Fixed Hardware Button Home Key
- Added disable Touchscreen through pressing the Browser Button
- Fixed VPN (Needs testing)
- Fixed Folio (Expect some keys not available in normal CM9)
[B]Version 0.0.5[/B]
- Changed to newest CM9 Sourcecode
- Fixed naming in storage listing
- Quill recognizes pen as pen
- Gtalk works with new CM9 and new Gapps
[B]Version 0.0.4.2[/B]
- Sound works (no Headphones, but maybe we will get there today) Update: Headphones work
[B]Version 0.0.4.1[/B]
- Sound works in ALSA and partially in Android (Click sounds work, youtube and Music doesn't)
[B]Version 0.0.4[/B]
- Fixed Green overlay issue (thanks digetx for the hint)
- Fixed Problem with surface Buffer (No force close of GUI anymore)
[B]Version 0.0.3.2[/B]
- Modified N-Trig drivers directly in Kernel (Touch Wrapper isn't needed anymore)
- Still trying to figure out how to fix the green overlay issue
[B]Version 0.0.3.1[/B]
- Fixed GPS (?)
- Fixed internal media storage
[B]Version 0.0.3[/B]
- Wrapper for new ICS-Touchscreen API -> Touchscreen works
[B]Version 0.0.2[/B]
- Wifi works (But not Signal Strengh in UI)
- Reboot Problems hopefully fixed (needs further testing)
[B]Version 0.0.1 (First Try)[/B]
Working:
- successfully booted
- stylus
- bluetooth (loaded fine but not tested transfering)
Bugs/Not working:
- Reboot Problems (like in CWM)
- No touchscreen (only Stylus)
- No wifi
- No camera
- a bunch of other things
First!!!!.
On a more serious note, nice to see a more organised OP for the rom. I hope we can make more progress with the development.
I can confirm this version does fix any freezing that was happening due to the pen button bug. This version is also silky smooth thanks to Koshu's and Jon's hard work.
Also, a fix for trebuchet not displaying correctly is to use Apex Launcher highly recommend. It has additional features as well that in my opinion make it a better experience.
Yup, that problem was happening every 5-10 minutes, and just worked for two hours without any problem with .00731. Also, just on another note, there's that ever occurring problem of loss of pen strokes after like 5-10 minutes after which I have to replace the battery or lock/unlock the tablet before it continues to work. Is this now a hardware problem as I've had it since day 1, through all the updates and also this ROM now.
@yahoowizard
I had that issue since day once as well, and it happened just yesterday when I restored an early build (I think it was 005x but not sure). But I feel like since 006x I haven't had that issue.
I've used build 00731 (full wipe) with Quill and Lecture Notes for several hours today without that occurring. So yeah I'm not sure what causes that bug, but like I said above, I feel like it was fixed a few builds past.
Put this on last night. Not having any market issues (any problem apps you want me to check?)
Only problem I have now is Chrome Beta still crashes after a few seconds use?
Thanks for all the hard work!
soveryevil said:
Put this on last night. Not having any market issues (any problem apps you want me to check?)
Only problem I have now is Chrome Beta still crashes after a few seconds use?
Thanks for all the hard work!
Click to expand...
Click to collapse
Yeah it does... and it does this on my other devices, too. Its still a beta so lets fix things with chrome when its stable or when there is nothing else to do.
with full wipe the installation takes about 15 seconds, says its complete (really skeptical here). on boot, it shows the lenovo logo but wont boot up, tried for about 20 minutes now..
//got bootloop now. so i guess i cant really say how it works for me
pau-pau123 said:
with full wipe the installation takes about 15 seconds, says its complete (really skeptical here). on boot, it shows the lenovo logo but wont boot up, tried for about 20 minutes now..
//got bootloop now. so i guess i cant really say how it works for me
Click to expand...
Click to collapse
A lenovo boot logo? Then something went totally wrong. I replaced the boot animation, means that there are still parts of stock HC on your tpt. You might want to recheck if the zip is downloaded and moved to your sdcard without errors and try again.
well, the very inital font saying 'lenovo', right after the vibration.
downloaded once more, which eventually led to the bootloop (156mb).. installed on top of the no bloat ota2.5, installed full wipe, installed just witch dalvic and chace wipe. no clue what went wrong really
pau-pau123 said:
well, the very inital font saying 'lenovo', right after the vibration.
downloaded once more, which eventually led to the bootloop (156mb).. installed on top of the no bloat ota2.5, installed full wipe, installed just witch dalvic and chace wipe. no clue what went wrong really
Click to expand...
Click to collapse
Ah ok that logo^^, that's normal, sorry thought you were talking about the bootanimation. Do you have an US device?
Koshu said:
Ah ok that logo^^, that's normal, sorry thought you were talking about the bootanimation. Do you have an US device?
Click to expand...
Click to collapse
haha ye, should have put it a little clearer.
ye, US, 32GB
pau-pau123 said:
haha ye, should have put it a little clearer.
ye, US, 32GB
Click to expand...
Click to collapse
Just to make sure, did someone else try to install ICS on a tpt with OTA2.5?
Koshu said:
Just to make sure, did someone else try to install ICS on a tpt with OTA2.5?
Click to expand...
Click to collapse
I did. I got stuck on the boot animation as well, but a full wipe of things followed by a reinstall of this ROM fixed it.
Koshu,
Thanks for the excellent ROM -- after a few hurdles that were all my fault, I managed to get it up and running.
First, I'd like to say: if anyone is unable to get this running because ClockworkMod Recovery reboots itself after 30 seconds (even if you're doing nothing, e.g. sitting at the main CWM menu), chances are you installed the "ROW" (Rest of World) CWM on a non-ROW tablet. This was the case for me. HOWEVER, don't fret if you already wiped out your system -- there's a workaround.
Plug a USB device with logic (e.g. not a "dumb" battery; something like a phone or flash drive) into the full-size USB "Host" port on your thinkpad. This, magically, will prevent CWM from rebooting after 30 seconds, allowing you to properly use it for backup/restore and for flashing CM9.
In fact, this is the only difference I could find between the ROW CWM that I accidentally flashed, and the US one. So if you always will have a USB device handy of some type, you can continue to use the ROW CWM and don't have to mess with it. Plug 'er in and it magically works!
However, I am having a problem. My attachable USB folio keyboard doesn't work at all. No keyboard, no mouse, no errors. Your OP has it down as "mostly", so does that mean it only works if you do some hack, or is it just my specific model not working? I'd expect that something like a USB keyboard would be handled by upstream Linux kernel USB device drivers... no?
For posterity's sake: my TPT is the 64GB variety, with no 3G/WAN, US Version, and I installed ICS after wiping data and Dalvik, on a system that had NEVER had an OTA applied to it -- straight stock from the factory, running a ROM ending in "_0065". I was running CWM version 5.5.0.4 and tested CM9 version 0.0.7.3.1.
yahoowizard said:
Yup, that problem was happening every 5-10 minutes, and just worked for two hours without any problem with .00731. Also, just on another note, there's that ever occurring problem of loss of pen strokes after like 5-10 minutes after which I have to replace the battery or lock/unlock the tablet before it continues to work. Is this now a hardware problem as I've had it since day 1, through all the updates and also this ROM now.
Click to expand...
Click to collapse
pen wonk - pen is periodically not recognized by the system
Unfortunately, I experienced the pen wonk periodically in class today. I wonder if it's a hardware issue too or an Android issue, because I have also experienced it on every ROM including stock. I'll try to get a logcat while note taking tomorrow to see if we can get any information about the 'pen wonk' issue.
allquixotic said:
Koshu,
However, I am having a problem. My attachable USB folio keyboard doesn't work at all. No keyboard, no mouse, no errors. Your OP has it down as "mostly", so does that mean it only works if you do some hack, or is it just my specific model not working? I'd expect that something like a USB keyboard would be handled by upstream Linux kernel USB device drivers... no?
For posterity's sake: my TPT is the 64GB variety, with no 3G/WAN, US Version, and I installed ICS after wiping data and Dalvik, on a system that had NEVER had an OTA applied to it -- straight stock from the factory, running a ROM ending in "_0065". I was running CWM version 5.5.0.4 and tested CM9 version 0.0.7.3.1.
Click to expand...
Click to collapse
First of all, congrats on getting up and running and figuring out that CWR workaround. I also have US, Wi-Fi only US TPT. I can successfully connect my bluetooth keyboard and even enable it as a input device within the bluetooth settings. But the keyboard isn't listed anywhere in the Language & Input settings menu. I believe it should have a new subsection name Physical Keyboard Is the keyboard folio listed?
@Koshu
I was wondering if there was a way to disable the 3G/WAN in ICS if no such connection is possible? I have a Wi-Fi only model but still have empty cell bars in my status bar. Just curious
pau-pau123 said:
well, the very inital font saying 'lenovo', right after the vibration.
downloaded once more, which eventually led to the bootloop (156mb).. installed on top of the no bloat ota2.5, installed full wipe, installed just witch dalvic and chace wipe. no clue what went wrong really
Click to expand...
Click to collapse
Ok, so it already worked on similar devices. Did the installation Finish? Like allquixotic stated there reboot problems in cwm. It shouldn't reboot on it's own in the installation process.
allquixotic said:
Koshu,
Thanks for the excellent ROM -- after a few hurdles that were all my fault, I managed to get it up and running.
First, I'd like to say: if anyone is unable to get this running because ClockworkMod Recovery reboots itself after 30 seconds (even if you're doing nothing, e.g. sitting at the main CWM menu), chances are you installed the "ROW" (Rest of World) CWM on a non-ROW tablet. This was the case for me. HOWEVER, don't fret if you already wiped out your system -- there's a workaround.
Plug a USB device with logic (e.g. not a "dumb" battery; something like a phone or flash drive) into the full-size USB "Host" port on your thinkpad. This, magically, will prevent CWM from rebooting after 30 seconds, allowing you to properly use it for backup/restore and for flashing CM9.
In fact, this is the only difference I could find between the ROW CWM that I accidentally flashed, and the US one. So if you always will have a USB device handy of some type, you can continue to use the ROW CWM and don't have to mess with it. Plug 'er in and it magically works!
However, I am having a problem. My attachable USB folio keyboard doesn't work at all. No keyboard, no mouse, no errors. Your OP has it down as "mostly", so does that mean it only works if you do some hack, or is it just my specific model not working? I'd expect that something like a USB keyboard would be handled by upstream Linux kernel USB device drivers... no?
For posterity's sake: my TPT is the 64GB variety, with no 3G/WAN, US Version, and I installed ICS after wiping data and Dalvik, on a system that had NEVER had an OTA applied to it -- straight stock from the factory, running a ROM ending in "_0065". I was running CWM version 5.5.0.4 and tested CM9 version 0.0.7.3.1.
Click to expand...
Click to collapse
"Mostly" Means that the Folio is working except some special keys, because there is no function to map them to in ASOP/CM9. These still need to be implemented. The rest should work out of the box. The driver folio is in the kernel, thats correct, but android still needs some mapping files to get a keyboard working. This is not the case for the mouse, which always worked if i remember correctly. Could you post a dumpsys with connected Folio?
obscure.detour said:
pen wonk - pen is periodically not recognized by the system
Unfortunately, I experienced the pen wonk periodically in class today. I wonder if it's a hardware issue too or an Android issue, because I have also experienced it on every ROM including stock. I'll try to get a logcat while note taking tomorrow to see if we can get any information about the 'pen wonk' issue.
Click to expand...
Click to collapse
Hm, never happened to me and I took a lot of notes with the tpt, too. Please also try to get a dmesg, because if this is happening on all roms, it could also be a problem of the kernel driver.
First of all, congrats on getting up and running and figuring out that CWR workaround. I also have US, Wi-Fi only US TPT. I can successfully connect my bluetooth keyboard and even enable it as a input device within the bluetooth settings. But the keyboard isn't listed anywhere in the Language & Input settings menu. I believe it should have a new subsection name Physical Keyboard Is the keyboard folio listed?
@Koshu
I was wondering if there was a way to disable the 3G/WAN in ICS if no such connection is possible? I have a Wi-Fi only model but still have empty cell bars in my status bar. Just curious
Click to expand...
Click to collapse
Jepp there is a way. It's not really disabling the 3G, more like removing the icon. But let me check if there is a way to auto detect this, because i try to avoid multiple ROM versions and I'm still planing to get 3G working.
How do I get a logcat or a dmesg? While using some developer setting in Writepad Stylus (I think?) I noticed that the screen doesn't recognize the stylus at all at some points. It wasn't that the lines weren't registering, it was just that it was almost as though the pen was dead. But yeah, replacing battery or lock/unlocking tablet fixes it so >.> no idea what's going on there. If you fix that problem, I will love you forever, hahahaha
Related
Okay everybody, I want to start a WIP on this as it seems that we can get somewhere. The last dev seems to have dropped the project so I picked it up. :good:
***NOTE*** This is meant for development/testing purposes ONLY. It is in NO WAY for the faint of heart and you must follow ALL instructions or it will not boot! You have been warned!
As of 5/7/2013, the following things are working:
Camera (flash works, it takes pictures)
Sound (the only reason I know this works is because the shutter noise goes off in the camera app, there is no other way to test this right now)
The test apps (browser, notepad, gallery, camera, browser, phone, calculator, calendar, clock)
Power button (phone goes to sleep and wakes, hold the power button down to shut off the phone - the shutdown takes a second because it shuts down just like a linux kernel would - plug it in the charger to test this, it will vibrate once it is off)
Not working - just about everything else. Most items are still placeholders and there is a stability issue where the apps all close themselves after a few seconds which I am trying to figure out. There is no data or cellular connectivity of any kind. This may be fixable, however, since I was able to get the camera working by pulling the prebuilts from a different CM version. I'll keep experimenting with this. If you put the device to sleep, it does not wake up to the same brightness (it is dimmed) and you can not adjust the brightness right now (working on this as well, its a permissions issue in the kernel source but I haven't been able to narrow it down yet).
It is VERY finicky about how it is installed. I won't give any support for anything but TWRP 2.5.0.0
To install:
-Download the kernel zip and the latest daily from Ubuntu (I will post links later)
-Backup your current ROM in its entirety using TWRP - check every item on the list or you may have to go to a fresh install of your version you were running previously.
-In TWRP (once again, make sure its 2.5.0.0 because these are 2.5.0.0 specific instructions), factory reset but do an advanced reset, check dalvik, data, system, and cache. ***MAKE SURE THAT YOU DON'T FORMAT YOUR MICROSD***
-Install the kernel zip and do not wipe cache or dalvik
-Install the Ubuntu preinstalled image, once again make sure you do not wipe the cache or the dalvik.
-Do not do anything else, no fixing permissions or anything, just reboot
-Wait about 2 minutes for the lock screen to come up and then you can use it
I will keep working on the kernel - the other functions will not work until Ubuntu implements them.
This is my first time working with actual development - if anyone wants to give me a tutorial to get my project up on GitHub so everyone can work on it, I would be more than happy to do so.
Here are the links:
Kernel built 5/7/2013: http://d-h.st/185
Latest Ubuntu Touch base: http://cdimage.ubuntu.com/ubuntu-to...current/raring-preinstalled-phablet-armhf.zip
Since the source has been moved to Raring Ringtail, there should not be a need to update that link. Please note that the 5/7/2013 build is the one that I tested and be sure to let me know if it gets broken in the future.
Enjoy everyone and once again, if you want to contribute, I'm more than happy to set up a GitHub, I just need some basic help getting it started.
How about now since they are realeasing daily builds
Sent from my SGH-T999 using Tapatalk 2
Sweet!
if you need testers or people to try it out let me know
Summarized Standard Disclaimer: use at your own risk. I use it at mine.
*Full wipe recommended if coming from another kitkat rom*
MAKE SURE TO HAVE A BROWSER APK. THERE IS NO MORE STOCK BROWSER. For firefox see below.
My personal build "Diamond Rom 4.4" is based on omnirom with the following additions:
CM Calculator (the newly redone one they're proud of)
CM File Manager
CM Wallpapers
Bash shell
Nano text editor
Powertop
Koush's full featured open source superuser (and it's INTEGRATED into settings :cyclops: )
Carbon rom blue balls wallpaper
Cyanogenmod port of 2 column settings adapted to Omni rom.
Omni floating window
I've added a few of my personal touches which include
Batter circle color changing: green 100%-51% yellow 50%-16% red 15%-0% This was my favorite I9000M framework-res mod that I've missed since switching to CM7.2 way back.
Killed lock screen music full screen (personal privacy thing when riding public transportation)
Disable android external storage management: messes with ext4 formatted hard drives or multi partitioned hard drives. Use the unix style mount command
Disable hardware keyboard on boot: disabled but not removed. You'll have to manually turn it on
Removed camera sounds
Disable SELinux at the kernel level. It's even disabled on my laptop/desktop at the kernel because it seems like it's more trouble than it's worth.
Put the dalvik cache in the cache partition. Don't waste the data partition for it. :cyclops:
And of course, comes bundled with my A1 kernel :cyclops:
Every thing I've tested: camera, youtube hd, sound, gps, usb otg(use manual mount command) etc work.
*Instructions*
First time flashing omni:
-Read second post FAQ and other important information.
-Flash TWRP (you can flash twrp over cwm from cwm if you're in that situation)
-Reboot into new recovery
-Make recovery backup (optional)
-Run Titanium Backup (highly recommended)
-Full wipe
-Format system partition
-Install ROM
-Install gapps
-Reboot :cyclops:
Subsequent flashes:
-Install ROM
Downloads
Mediafire Wifi download folder with md5sum file
Mediafire 3G download folder with md5sum file
Mediafire TMobile download folder with md5sum file
*Authorization to download is just a captcha. Simply enter the text in the picture or name the item being advertised in the picture.* Mediafire sure beats sh***y sites like uploaded.net or rapidgator
A1 Kernel (as its own download)
V1.9.2: Security fix made aware by cyanogenmod, specifically this. The commit message on my github has a copy and paste mistake. It should list both of those security flaws as patched instead of the same one twice. Oops :cyclops: Security fix comes with ALL roms June 28 and onwards.
3G/Wifi 6ff199d6c9037d222a70ec0c561c8028
TMobile a675fd353ad3ad7dbf8e6bf2109fa360
TWRP Recovery
2.7.1.0 Wifi 6c995325e749e7561893e398847b09a0
2.7.1.0 3G 8fa04be69d0faf3d9a134e829ddff680
2.7.1.0 Wifi July 8 a8d12c13aac7430a319369069d814e72
2.7.1.0 3G July 8 dc1c50622c29c621f29b95f4c53734ea
2.7.1.0 Wifi August 11 b2c21e8fd58dc38a9c8b7669031b84b1
2.7.1.0 3G August 11 9f48defe78391e63a9053cbd281f738f
2.7.1.0 TMobile August 11 87fb29c803a2e3a56d98a1475c5fce8f
2.8.0.0 Wifi cfdac70d0ccac34cf220887eab72f8b0
2.8.0.0 3G d7918eb397f54c484e04a6d5cb07945c
2.8.0.0 TMobile aaf7c6d2455ca32178ec846f5186c774
Newer versions of firefox explicitly disable flash on tegra2. Use my firefox mod which is just normal firefox with a hacked tegra2 blacklisting mechanism. Don't use the old firefox apk. It has unpatched security holes.
Changelog: omnirom gerrit
Sources: https://github.com/AAccount?tab=repositories Has my device trees as well as all the omni repos I forked with my additions.
Credits:
Kasper_h: helping to make 4.4 possible
pershoot: original device tree from CM10.1
Omni team: providing great starter rom and keeping it TF101 compatible
fred6681: original gapps package. I just removed the 4.4.2 check
Cyanogenmod team: rom extras like calculator, superuser, to fill in Omni's missing holes and 2 panel settings template.
XDA:DevDB Information
Omnirom+ 4.4 for Galaxy Tab 10.1, ROM for the Samsung Galaxy Tab 10.1
Contributors
AAccount
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.1.x
Based On: Omni
Version Information
Status: Stable
Created 2014-10-12
Last Updated 2014-10-11
Known Issues:
Wifi signal indicator and speed indicator don't show up
No list of 3G APN. Write down your settings first
Bluetooth audio issues
Recovery adb doesn't start automatically. In recovery, go to Advanced --> ADB Sideload and start it. You can then cancel it if you don't want to use that. It just starts the recovery adb and will continue to run until you reboot. fixed thanks to twa_priv
Use another recovery for TMobile. Apparently the twrps I make can't boot on TMobile hardware even though it boots on my Wifi only.
FAQ
How do I get multi window: Settings-->(second) More --> App circle bar (check box) && --> Included apps (choose what you want available in multi window)
Yes you can flash TWRP over CWM
Random flickering: Try Settings-->Developer options -->Disable HW Overlays.
Can't install a very large quantity of apps: fix
Can't mount ext4 media: kill the e2fsck process assuming you safely removed the media before sticking into the tablet.
(Below this is optional)
(Android device manager does have legitimate uses. However, please read and consider the following paranoid but realistic fantasy:)
Completely disable android device manager: By only going to Settings->Security->Device administrators and un checking "Android Device Manager" this doesn't completely remove the ability for google to send in commands to your device. Go to the google play store through a web browser, choose android device manager, and try "ringing" your device. To my horror, my tablet started to ring as if it got a phone call. I don't find it acceptable that gapps gives google a way to setup a remote command and control operation. In any other operating system this is considered a back door or virus.
To close this back door install Xprivacy. Enable system apps to be modified. Look for the entry (should be highlghted in red to indicate a system app) "Google Account Manager, Google Backup Transport... (lots of items here) ...Google Services Framework". Check mark Notifications and open its menu. Check mark the items in red. These are cloud to device (c2d) permissions which do exactly what you think. While not necessary, disable identification too for good measure. This disabled the ring feature on my tablet which means android device manager should no longer be able to send in commands. I don't have the guts to try the device wipe feature but it should work too. Do not disable location otherwise google maps won't be able to find you which means no gps car navigation.
See this post about building from source. I use a different, simpler trick for prebuilt chromium binaries. Fear not, they are source built but only when there are real source changes. They're just recycled in between to save 90mins/build of time.
Downloading now!! Thanks for your work!!
Enviado desde mi GT-I9195 mediante Tapatalk
Another 4.4.3 for the tab?
Thank you very much!
Hi AAccount,
thanks for your 4.4.3 ROM, sounds promising ... however, what about the graphical glitches on that vesion? I always went back to ROM version CM10.2/SGT7 as this seems to be the latest one without those glitches (last version I tried was Nameless ROM version 4.4.2 where they were still visible ... and annoying).
Thanks in advance,
mistersixt.
Great job!! Runs fast without bugs and glitches, only youtube HD...
The best kitkat rom!! Thanks !
Enviado desde mi GT-P7510 mediante Tapatalk
Best kitkat rom. I have some glitches. It is not as smooth as cm10.2 so i am going back to cm10.2.
What graphical glitches do you mean? I think ever since omni fixed the screenshot way back most graphical bugs have been ironed out. By youtube hd do you mean it doesn't play or can be laggy? If you mean laggy I read on wikipedia the GPU video decoding on the tegra2 sucks. That's a hardware problem.
3G build and new recovery coming later today. I cheated the chrome renderer build process by copying all the freshly done ones from the wifi only output folder.
My github is now fully up to date with all the appropriate omni repos forked with my personal touches whether it be the audio blob fixes or little things I like.
Sent from my GT-P7510
What are the flashing instructions? Is there a preferred gapps package?
Sent from my GT-P7510 using Tapatalk
AAccount said:
What graphical glitches do you mean?
Click to expand...
Click to collapse
With all ROMs starting with 4.3 it looks like if a flash of lightning goes from one corner to the other (my wife is saying it looks more like a scratch) for maybe 100 ms, this happens quite constantly though, every minute or something. Also, in some games like flappy bird the application gets stuck for maybe 100 to 200 ms completely (every 5 to 10 seconds maybe) before it continues, this makes playing games unpossible (temple run is another good example).
With 10.2/SGT7 this does not happen ... for whatever reason.
Regards, mistersixt.
lancem71 said:
What are the flashing instructions? Is there a preferred gapps package?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
I added instructions. There's no really preferred gapps package. I just like that one because it's the smallest one that gets the job done. There are some gapps packages that are bigger than the rom which I consider bloated.
mistersixt said:
With all ROMs starting with 4.3 it looks like if a flash of lightning goes from one corner to the other (my wife is saying it looks more like a scratch) for maybe 100 ms, this happens quite constantly though, every minute or something. Also, in some games like flappy bird the application gets stuck for maybe 100 to 200 ms completely (every 5 to 10 seconds maybe) before it continues, this makes playing games unpossible (temple run is another good example).
With 10.2/SGT7 this does not happen ... for whatever reason.
Regards, mistersixt.
Click to expand...
Click to collapse
I get these randomly sometimes but not often enough that I would consider it an issue. In angry birds it's an issue but if you go to Settings-->Developer Options check mark "Force GPU rendering" and "Disable HW overlays". Then you can play angry birds at least without the lightning.
And now for an important question
I have a script that puts /data/dalvik-cache on /cache/dalvik-cache as it was way back in android 2.2 froyo. Even though our tablet shipped with android 3.0 and my I9300 S3 shipped with android 4.0, Samsung seems to have been very sloppy and left the /cache partition huge to accomodate the froyo standard. This is a waste of space that will never be used. The cache paritition is 0.5GB. Is it OK if I include this script as a boot script? Is 0.5GB/500MB enough for most peoples' dalvik-cache? This will free up that space and add it to the internal sd card.
Great room, thanks! Everything working OK during the first hour of use
Sent from my GT-P7500 using XDA Free mobile app
Thanks for posting this! Great ROM. Only problem I'm having is the APN settings are blank for my 3G tablet (P7500). I input them manually and everything works, but normally they are preset.
AAccount said:
I get these randomly sometimes but not often enough that I would consider it an issue. In angry birds it's an issue but if you go to Settings-->Developer Options check mark "Force GPU rendering" and "Disable HW overlays". Then you can play angry birds at least without the lightning.
And now for an important question
I have a script that puts /data/dalvik-cache on /cache/dalvik-cache as it was way back in android 2.2 froyo. Even though our tablet shipped with android 3.0 and my I9300 S3 shipped with android 4.0, Samsung seems to have been very sloppy and left the /cache partition huge to accomodate the froyo standard. This is a waste of space that will never be used. The cache paritition is 0.5GB. Is it OK if I include this script as a boot script? Is 0.5GB/500MB enough for most peoples' dalvik-cache? This will free up that space and add it to the internal sd card.
Click to expand...
Click to collapse
Many thanks for this!
"Disable HW overlays"- for some reason this setting does not stick between reboots (not your ROM problem- it happens in all devices that I've ever seen). Is there a way to apply it automatically during or after boot? Such as in a script, or init settings etc?
Regarding the Dalvik cache, is there a way to know how much space all my installed apps + system are currently using?
jaibar said:
Regarding the Dalvik cache, is there a way to know how much space all my installed apps + system are currently using?
Click to expand...
Click to collapse
Go to the CM File Manager --> Settings --> General Settings -> Compute folder statistics and check mark that box. Also in the same area be sure to set access mode to prompt user mode or root access mode. Then, go to /data and hold dalvik-cache folder until get a menu and choose properties. The size will show up under "Size: ". Mine is 208mb.
AAccount said:
Go to the CM File Manager --> Settings --> General Settings -> Compute folder statistics and check mark that box. Also in the same area be sure to set access mode to prompt user mode or root access mode. Then, go to /data and hold dalvik-cache folder until get a menu and choose properties. The size will show up under "Size: ". Mine is 208mb.
Click to expand...
Click to collapse
238MB here. Maybe a quick poll can help gather info on how much allocation must users are using?
Sent from my GT-P7510 using Tapatalk
jaibar said:
238MB here. Maybe a quick poll can help gather info on how much allocation must users are using?
Sent from my GT-P7510 using Tapatalk
Click to expand...
Click to collapse
Same around 2xx mb. I'm fine with it, since the 400mb in /cache is wasted anyway.
Sent from my GT-P7500 using Tapatalk
223MB here
Is Netflix working on this ROM. Asking because there is problems on the Nameless ROM.
Sendt fra min GT-I9305 med Tapatalk
thra1982 said:
Is Netflix working on this ROM. Asking because there is problems on the Nameless ROM.
Click to expand...
Click to collapse
Every time somebody asks about Netflix... I fell I'm missing something big...
Thread created by hbenz2008 but now maintained by me CWGSM3VO:
Requirements:
- Unlocked JBBL/KKBL bootloader. Builds are bootloader specific.
- Updated KKBL recovery, can find one here: https://twitter.com/dhacker29/status/583847256589213696
- Updated JBBL recovery, can find one here: http://downloads.blissroms.com/Recovery/Recovery/moto_msm8960_jbbl/
Builds can be downloaded from:
- CMxlog: http://www.cmxlog.com/12.1 and choose your device.
- CyanogenMod: http://download.cyanogenmod.org/ and choose your device.
GApps:
- DHacker gapps:
4-25-2015: https://www.androidfilehost.com/?fid=96042739161893996
6-07-2015: https://www.androidfilehost.com/?fid=24052804347756927
- Delta gapps: http://forum.xda-developers.com/android/software/app-minimal-gapps-gapps-lp-20150107-1-t2997368
What works:
- Phone
- WiFi
- GPS
- SMS/MMS
- Mobile Data
- Camera/Camcorder
- HDMI
- Bluetooth
- Call Recording
- Tethering (WiFi: Yes / USB: Yes / BT: Yes)
- USB storage
- F2FS for /data, /data/media and /cache (recovery/kernel dependant)
Known issues:
- The "calc bug". This affects some users. This is due to the GPU crashing. A fix may be hard to nail down. Workaround is to disable H/W layers + force GPU rendering via devopts.
- HDMI. Depends on TV. Works 100% on some, not others (in my testing) -- statusbar/navbar is visible and small scaling issue (statusbar cut off somewhat). Reported not working on AHD.
- Bluetooth; some reported issues with different car makes/models. For me personally, it's worked with a variety of headsets and devices (decks, etc). Tethering appears to work for me, some reports of issues. Issues reported with wearables being paired and WiFi not working or requiring BT to be activated after WiFi connected.
- MMS; most issues can be tracked to incorrect APN settings, please verify with your provider (or try searching this or CM11 threads)
- WiFi; some users have reported issues connecting to certain brands of APs and/or band-mode; most reports isolated to security protocol being used (WPA vs WPA2)
- Clock resets to 1970. Thanks to @MaicolS for using this solution successfully: http://forums.androidcentral.com/an...-update-can-t-connect-google.html#post4323256
- Snapchat crashes sending video. @VlitalityX found this solution: Developer Options->Drawing->Turn on "Force RTL layout direction" then turn it off.
- Alarms not firing or repeating. Disable Automatic Network Date & Time in Settings->Date & Time. Appears to be an issue with RTC writes and/or QCom time_daemon.
- Some reports of GPS not working, try this fix: http://forum.xda-developers.com/showpost.php?p=56659808&postcount=5264
Reporting issues:
- Please ensure your signature includes device, rom, etc to help if posting in the thread.
- Provide a logcat capture if possible, otherwise enable aplogd.
- Enable aplogd, see here: http://forum.xda-developers.com/showpost.php?p=59620294&postcount=2327 and provide logs. You can safely leave this enabled.
- Open a JIRA bug report, see here: https://jira.cyanogenmod.org and provide logs.
Notes:
- There are unofficial builds provided in this thread and should not be used when filing reports with JIRA.
- When coming from another ROM (non-CM) a clean-wipe is recommended (backup your data + internal sdcard data)
- Some users have had issues clean installing CM12.1 - one workaround known is to install CM11 first then upgrade to CM12.1
- The Xposed framework is not supported. Please uninstall/remove it and any modules before reporting issues.
Tips:
- I use TWRP
- I use DHacker's GApps package and let Google via my account update everything as need be.
- For me, a "clean wipe" is formatting the following: /system, /cache, /data and /data/media. Backup anything of value from /data and /data/media before doing this. Flash ROM, flash GApps, reboot. Authorize your PC USB connection on the phone after enabling Developer Options and test adb from the Android SDK.
- When performing a "dirty flash" (upgrade) I manually wipe /cache and dalvik-cache before rebooting to UI.
- For KKBL to JBBL issues with downgrading, see this: http://forum.xda-developers.com/showpost.php?p=63091712&postcount=4465 and this: http://forum.xda-developers.com/showpost.php?p=56963255&postcount=702
- Drained to 1% battery and boot-looping? Try this: http://forum.xda-developers.com/showpost.php?p=61728073&postcount=3754
- If your CM build is 1+ month older than what you plan to flash/upgrade, it is recommended you do a clean flash.
So far, I had some issues with network, apparently it's losing WiFi connection randomly . The Play Store takes a long time to download or update apps or get "Retry" messages.
None of those issues here,however i had some unfortunately dialer stopped,it corrected itself after couple reboots.
Downloaded es file explorer as fx explorer couldn't get into System files.
GPS still hosed in my case
I forgot to mention: during the flashing, a mount error appear, but the ROM booted, normally. Happened to you to?
No but flashing was really quick I was surprised.under a min maybe then it took bout 5 min to reboot.but no errors
Hummmm, strange... What recovery are you using? I flashed dHacker's one, before flashing the ROM.
And something happened just now: I rebooted the phone and the DPI as changed! All the things are smaller now. Weird...
Most likely need to reflash.using twrp 7.1 and flashed dhacker gapps.
note: cant write to System file yet
I know this is for KKBL, but can this be built for JBBL? How is the overall feel of the build anyways?
Sent from my ATRIX HD using XDA Free mobile app
douglasvbarone said:
I forgot to mention: during the flashing, a mount error appear, but the ROM booted, normally. Happened to you to?
Click to expand...
Click to collapse
FYI he said SD card doesnt work yet
doesnt work in what capacity?
lngwca said:
FYI he said SD card doesnt work yet
Click to expand...
Click to collapse
Well, that kills it for me then. Will have to wait. I have all my music and photos on my SD card.
doing a nandroid backup now, but photos in SD can be seen .Once done, i will test music...
Anyone can post a gps.conf from a working gps whether it be jelly bean or kitkat.
... will be appreciated. Under System/etc
very smal file 2kb or so
both music and photos in SD can be manipulated just fine
iBolski said:
Well, that kills it for me then. Will have to wait. I have all my music and photos on my SD card.
Click to expand...
Click to collapse
major beef i have is editing system file. Device is rooted, titanium has access, file explorer have access and sees system file but cant edit.
hbenz2008 said:
both music and photos in SD can be manipulated just fine
major beef i have is editing system file. Device is rooted, titanium has access, file explorer have access and sees system file but cant edit.
Click to expand...
Click to collapse
Ahh, gotcha. I thought there was NO access to the SD card. So, it's just write access. I know under Lollipop, they were supposed to make it work better than they did under KK. Supposedly, it's a setting where you can say give it all access or only to it's own directories. Supposedly though, many apps might have to be rewritten to get this, so if the app hasn't been updated to ask for the new permission, then it won't work.
lngwca said:
FYI he said SD card doesnt work yet
Click to expand...
Click to collapse
The tweet:
Everything except SD YouTube video seems to work on RAZR HD
Click to expand...
Click to collapse
Has nothing to do with SD card, it means SD YouTube videos (SD - Standard Definition, as opposed to HD - High Definition).
his tweet said "Everything except SD YouTube video seems to work on RAZR HD "
so sd as in resolution. i asked him if he could try viralpopup or tubemate. might try this on the weekend to see how this feels.
oh and can someone upload a mirror pls? page won't load 2 download.
ps it's a cm12 port not AOSP too from his threads on twitter
absolutely true, the challenge for now is to gain access to editing system file.
kabaldan said:
The tweet:
Has nothing to do with SD card, it means SD YouTube videos (SD - Standard Definition, as opposed to HD - High Definition).
Click to expand...
Click to collapse
hbenz2008 said:
both music and photos in SD can be manipulated just fine
major beef i have is editing system file. Device is rooted, titanium has access, file explorer have access and sees system file but cant edit.
Click to expand...
Click to collapse
try root explorer to edit system files
http://www.reddit.com/r/Android/comments/2m7fqo/i_wanted_to_keep_a_chart_going_of_apps_we_know/
check play store if you bought/have titanium backup
they pushed an update for support. now if only they updated their UI....
confirmed, works-root explorer-
my bad... just thought that he missed a comma. lol also every ones sd wasnt mounting
While waiting for Euphoria marshmallow I did a test build for CM-13, so here it is.
If anyone want to take over this, I can help setting everything up.
Installation instructions:
Installing CM 13 for the first time, or coming from another ROM:
- Make sure you're running a proper working ClockworkMod-Recovery/Team Win Recovery Project for ext4 and with selinux support.
- Copy GApps and ROM ZIP to your SDCard
- Boot into Recovery
- Make a backup of your current rom just in case
- Wipe system, data, cache and dalvik-cache
- Flash CM zip from SDCard
- Flash GApps zip from SDCard (Don't reboot before installing this if you plan to use GApps)
- Reboot
- Don't restore system data using Titanium Backup!
- I don't recommend changing kernel.
Upgrading from an earlier version:
- Copy the ROM ZIP to your SDCard
- Boot into Recovery
- Wipe cache and dalvik-cache
- Flash the ROM zip from SDCard
- Reboot
Download:
ROM HERE
Recommended GAPPs HERE Don't use google stock package
Source:
Cyanogenmod: here
device_lge_p880: here
kernel: here
repo patches: here
Notes:
-Selinux is in permissive mode for now.You can change it to enforce by typing setenforce 1 in terminal.
-Wifi display(Screen cast) is disabled and it will not work with the old blobs that we have.
-I'm not trying to take ower for laufersteppenwolf. I use stock blobs and I'm just trying to help.
-I created this because someone shared the build in the Euphoria thread.
bugs:
-reboot to recovery
-after reboot "System process not responding" is displayed
-error "invalid number" after remote call disconnect
- Keyboard bug with open_GApps: After install of GApps, install attached cm-13.0-UNOFFICIAL-OpenGapps-keyboard_hotfix_5-16.zip to fix the FC of AOSP keyboard.
- video problems in default browser. Try a differnt browser.
- video preview in gallery have a green overlay, video playback is ok.
- some minor bugs in setting->performance
- (Perfomance is not great on this old phone)
-??
Please add signature faking patch!
Sometimes when I press the power button it opens up the camera app. Other than that it is stable and much faster than the stock ROM.
Great job. Keep it up!
--EDIT--
Also when the phone is charging the touch buttons are lighting up.
is it worth updating from euphoria? what changes
Thanks for creating a new thread :good:
ItsClobberinTime said:
Sometimes when I press the power button it opens up the camera app. Other than that it is stable and much faster than the stock ROM.
Great job. Keep it up!
--EDIT--
Also when the phone is charging the touch buttons are lighting up.
Click to expand...
Click to collapse
"Sometimes when I press the power button it opens up the camera app." It is feature on android 6.0, press power button twice and camera app open directly.
Overall this ROM is excellent.
Thanks for your support Alfa samsung.
Do you have a changelog for the new version @alfsamsung ?
What a great surprise. Again thanks for your dedication in developing this device.
I intsalled yesterday, installed with google keyboard via recovery, sometimes laggy but almost ready for daily driver. And I can say that M is better than L.
Thanks so much!!! Its nice to see there is still hope for my old and trusty phone
Works fine. Just a few reboots in 10 hours. Still can't get 100% deep sleep. Stopped a few services and it system update. Sleeps only 80%. Because of Android system .
any change log for cm-13.0-20160219-UNOFFICIAL-p880-beta.zip
Salman Al-Badgail said:
any change log for cm-13.0-20160219-UNOFFICIAL-p880-beta.zip
Click to expand...
Click to collapse
2 commits on github:
libsymbols: Shim load ril and camera libs. Remove libboringssl-compat
power: Add powerHAL (Based on asus flo powerHAL.)
maybe we get better changelog later
Why I can't see drivers when I connect the phone to pc ?
Edit :
I found the way,
developer options > Usb Config. > choose MIDI and ready to go
asgz said:
Why I can't see drivers when I connect the phone to pc ?
Edit :
I found the way,
developer options > Usb Config. > choose MIDI and ready to go
Click to expand...
Click to collapse
Did you find any bugs??
Very good for early build! Keep it up. I didn't test it enough. I can only say app launch speed is good but there is so much fps drop in apps.
Salman Al-Badgail said:
Did you find any bugs??
Click to expand...
Click to collapse
As usual working very smooth, all apps working fine.
Sometimes restart itself,
Wake up screen with sound button is working,
Gps is working,
sometimes beginning of call other person can't hear me, I can hear very clear.
after finishing call msg appear and says invalid number.
And for now I will not return to 5.1.1. After a few new vers. I believe that M will work better than other android vers. on our P880.
@alfsamsung, our last developer, I hope you will continiue developing.
Greetings
asgz said:
As usual working very smooth, all apps working fine.
Sometimes restart itself,
Wake up screen with sound button is working,
Gps is working,
sometimes beginning of call other person can't hear me, I can hear very clear.
after finishing call msg appear and says invalid number.
And for now I will not return to 5.1.1. After a few new vers. I believe that M will work better than other android vers. on our P880.
@alfsamsung, our last developer, I hope you will continiue developing.
Greetings
Click to expand...
Click to collapse
Thanks for replying, Did anyone had same bugs or extras???
Thanks for all @alfsamsung,you are a great guy and helpfull developper ,now ı'm trying cm 13
On my phone after switching on GPS power button stop working.
One restart for 2 days all the rest works very well.
After a few tests, I know that this is not problem with GPS, only applications which leave screen turned on.
Updated version of this ROM: [ROM][TMOBILE][S7_SM-G930T][Oreo 8.0 Rooted][WifiCalling]G930TUVU4CRI2
ROM last updated: 10/30/2018
Introduction:
HUGE thanks to the guys that got this going like root & figuring out hybrid stocks! This ROM is a complete rewrite of my ROM [ROM][TMOBILE][S7_SM-G930T][Oreo Rooted] That ROM doesnt have WifiCalling & I couldn't get it to work for the life of me, so I rewrote it. I started with stock, and slowly stepped back making changes, reinstalling each time, confirming it still worked. About 200 installs later & 1000s of changes, this is the result. Yes, it took a LONG time. Hope you enjoy it! Don't forget to say Thanks so I know it is actually helpful to others, and continue doing this!
Description:
Stock Tmobile Oreo 8.0 modified (G930TUVU4CRF1)
EXTREMELY debloated! Nearly bare minimum, while still retaining hardware functionality. Eg, Samsung Gallery & Camera exist so we get 4k recording, and there aren't errors when we pull up the Gallery to edit, etc. Yes, this means NO Samsung or Android Pay. There could be more apps to debloat but Im out of time for now! (Please provide suggestions if interested)
Everything possible I replace Samsung with Google
Solid ROM. It was actually kind of slow for me, but I'm curious how this works for others.
Xposed is part of the guide, which will give you infinite customization & tweak-ability
If you hate Samsung SW and just want a solid working ROM with very few install options to get you up and running this is for you.
This will delete all of your data on the phone! (Not external SD card) This is the only way so don't ask. Backup your data!
Features:
Tmobile Wifi Calling works, along with Visual Voicemail & Mobile Hotspot
Many Aroma Installer app options
(Optional) KevinsFavorites option in Aroma. I'm not sure I'd recommend it due to my tastes. If you're looking for some good common apps tho, it includes: Amazon, AmazonMusic, AquaMail, Gmail, GoogleDrive, GoogleKeep, GooglePhoto, Hangouts, IFTTT, Pandora, RootBrowserClassic, TitaniumBackup, Uber, & Wink (If you install these and want to remove them later, use TitaniumBackup (or similiar) to uninstall
Root Features: See Downloads->Recommended Root Zip & say Thanks!
Debloated
De-Knoxed
Decrypted /data/ partition
OTAs disabled
Speed & Build Prop Tweaks
Dual speaker
Ruthless Launcher
Apps
AdAway
AOD Clock Face Themes
CPUSpy
DisableService
Kernel Adiutor
Samsung Video Editor and Trimmer
Xposed
Many more...
Download Links:
Base.7z & Oreo_Kevin71246Modded_v3.#.#.zip
Installation:
This will delete all of your data! If you continue, you acknowledge that the Author is NOT responsible for anything that happens to your phone!
Summary (for Pros)
Flash Oreo stock
Root
Flashfire
Oreo_Kevin71246Modded_v3.1.##, Auto-mount, Mount /system read/write Option
Go through Aroma setup. When finished, it should boot to Recovery (if not do this). Do a "Wipe data/factory reset"->Reboot
Detailed Steps
Install Stock Oreo:
Download mode & Setup
Make sure you have latest device drivers setup on your PC
Enable USB Debugging on phone in Developer Settings
Boot phone into Download Mode:
Turn off your device
Press and hold Volume Down + Home + Power button
When you see the warning screen, release buttons & press Vol UP. Phone should say "Downloading..."
Download and unzip Base.7z to PC (This contains stock Oreo, ODIN, & root)
ODIN
Open ODIN on PC (\Base\Odin_313.exe)
Connect USB from PC to phone. ID:COM in Odin should turn Blue with a COM port
Select AP, BL, CP and CSC files from the \Oreo_Stock\Base\ folder for corresponding files
Select HERO2QLTE_USA_VZW.pit
Select Start
Finished: Phone will reboot & show Carrier screen for 3-5mins. Wait until Setup screen & go through quickly (bare minimum) since you'll wipe it again. Once in Android, go to Settings->Display->Screen resolution->WQHD->Apply
Root Instructions: (+Flashfire, SuperSU)
Reboot phone into Download mode
Odin
AP: Select \Base\Root\AP_SM_G930_OREO_ENG_BOOT.tar
Start-> Wait for phone to boot to Android OS
Root
Double-click \Base\Root\cmd-here.exe & Type: root.bat [enter]
Option: 1 (Install Root No tweaks) (Or pick whatever you want)
*Note: With this system root, do not update su binary. Disable notifications for SuperSU app. Don't flash any superuser zips in recovery that are not made by jrkruse
Install Custom Hybrid ROM & Xposed
Download & copy Oreo_Kevin71246Modded_v##.zip to phone
Flashfire
Open Flashfire on phone
Red + symbol->Flash Zip or OTA->Oreo_Kevin71246Modded_v#, Auto-mount, Mount /system read/write Option->Check mark
Click Lighting bolt at bottom-> OK
Phone will reboot to Aroma. Go through setup. (See above for what's in KevinsFavorites)
When finished, allow Aroma to exit.
It should reboot into Recovery (If not, do this: immediately hold Vol-Up btn+Home btn until you see recovery on screen. If you missed it, try again: hold Vol-Down+Pwr btn ~10sec until phone restarts & immediately hold Vol-Up btn+Home btn until you see recovery on screen.)
In recovery: Factory Reset->Yes->Restart phone
*Wait 5-10min on loading screens
Go thru Android setup. Ignore "Xposed Installer has stopped" error
Followup-Steps:
Set Dialer: Phone Settings->Apps->Menu->Default Apps->Calling App->Select Phone
Recommendations:
Xposed
Setup Xposed: Xposed Installer app:Install framework option & restart phone
Xposed Installer app: Settings button (3 lines)->Download->Search "GravityBox [O]"->Click it->Versions tab->Download->Install->Back arrow (upper left)->Settings->Modules->Check box next to GravityBox [O]->Restart phone
GravityBox [O] Tweaks: (Open GravityBox app)
Battery indicator: Statusbar tweaks->Battery settings->Turn on Master switch->Battery indicatory style: None->Battery percent text...->Back
Clock: Statusbar tweaks->Clock settings->Turn on Master switch->Center clock...
Firefds Kit [O] Tweaks: (Install same way as Gravity box)
This is a supplement to Gravitybox. Things of note: Advanced power menu, call recording, & disable bluetooth toggle popup, etc
Known Issues:
Visual Voicemail may fail to register, but restart phone and give it a few hours. It works eventually.
RCS (Rich Communication Services/AdvancedMessages/Chat) texts don't show up in Android Messages & Textra, etc apps (This is an issue on stock as well!!)
Fix: (Use Samsung Messages)
How to Install Samsung Messages via ADB (Easiest way though is just reinstall!):
Download Messaging_SEP81.zip, unzip, & manually copy apk to phone via usb/Windows My Computer
adb shell (Get into shell to run beow commands)
su (Run as root)
mount -o rw,remount /system (Mount system read/write since default it read-only)
chmod 755 /system/priv-app/Messaging_SEP81 (Set permissions on folder)
chmod -R 644 /system/priv-app/Messaging_SEP81 (Set permissions on apk file)
ls -l /system/priv-app/Messaging_SEP81 (Check permissions - Should be: -rw-r--r-- 1 root root - not sure what 1 & 2 is)
ls -l /system/priv-app | grep "Messaging" (Check permissions - Should be: drwxr-xr-x 2 root root)
reboot (Reboot device)
Changelog:
Version 3.1.32: First stable build
Ver 3.1.36:
-Disabled encryption on /data/ partition to resolve "Bluetooth paired devices deleted after reboot" issue & so mods play nicer with ROM
-Fixed "Device not supported" error on Google Phone app
Ver 3.1.37:
-Added most of the apps I replaced or added as options in Aroma Installer now
Credits:
- @jrkruse & @klabit87 for Root
- @partcyborg for helping jrkruse
- @jrkruse for his similar ROMs as guides & help
- @Lanc-City for assistance in ROM modding
- @gustco for eng boot.img
- @Raymonf for modified odin
- @amarullz for Aroma Installer
- @Chainfire for FlashFire & SuperSU
- @rovo89 for Xposed
- @JaeKar99 for the cool & colorful boot animation
- @mrRobinson for AdAway ADAway.org
- Brandon Valosek for CPUSpy
- WangQi for DisableService
- Willi Ye for Kernel Adiutor
- @shubby for Ruthless Launcher
- @Craz Basics for Dual Speaker Mod
...
- Please PM me if you were forgotten!
Some screenies:
Saved2
Saved3
Well nice job!
jrkruse said:
Well nice job!
Click to expand...
Click to collapse
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
kevin71246 said:
...but your'e the best! (You & I both know I couldnt have done it without all your other work!)
Once I FINALLY got WifiCalling to work, I thought... Imagine ALL the S7 XDA members out there with crappy Tmobile signal across Rural America that could TOTALLY use Wifi Calling!!! Haha, but seriously!! & that thought was the birth of this thread
Click to expand...
Click to collapse
Is this Ufirm firmware?
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
I have so many FW packages on my PC at this point, from so many places that I used while trying to get this to work, but I think it might be a package from one of your threads(?) Since I'm not exactly sure what you're asking regarding "Ufirm FW", I'll elaborate hoping that answers your question. (Tho I'm thinking you mean the U variation/unlocked. So based on these stock files below I guess the answer is no.) If you're question is really, "is it possible to get tmobile wifi calling to work on a U model #", then I'd have to really think about that. But at this point I don't have an answer. I can tell you a million dependencies about it tho! (I seriously have hundreds of revisions I made while testing, & notes. The symbolic & meta links in Aroma initially broke it, as I found out after a week or so of testing - wish I knew a bit more about them, and why they're all there, then I'd know what was wrong about them...)
High-level process:
1)Flash Base/Stock/Oreo Rom:
- AP_G930TUVU4CRF1.tar
- BL_G930TUVU4CRF1.tar
- CP_G930TUVU4CRF1.tar
- CSC_TMB_G930TTMB4CRF1.tar
- HEROQLTE_USA_VZW.pit
2)Root with your method
3)Flash Xposed framework & my ROM (it's a "start with stock then remove what we don't want" type of Aroma/Edify script)
jrkruse said:
Is this Ufirm firmware?
Click to expand...
Click to collapse
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
kevin71246 said:
BTW, any idea how to prevent the "verification failed" error I mention in the OP steps, after flashing Xposed framework? I tried flashing dm-noverity but no luck. At least my guide covers it at this point tho... Thanks again
Click to expand...
Click to collapse
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
It works perfectly!!
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
---------- Post added at 10:17 PM ---------- Previous post was at 10:15 PM ----------
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
charredchar said:
First, I want to thank you so much kevin71246. I tried your previous version as I was sick and tired of how sluggish my phone felt after the last two T-Mobile OTA updates. So far the experience on the phone has been great but I wanted to post about an issue I had with that version to see if anyone else has come across it or can figure out what is going on. The reason I am making this a reply in this thread instead of your other is because I will be flashing this update shortly but I want to get the ball rolling on the issue first.
I went through the whole process, installing the minimum with Google Apps, though I did restore everything previously installed once I log in with my Goggle Account. I am unsure if this contributed to the problem but I will not be restoring apps on the next try. It seems no matter what process I attempt to connect my Ticwatch E to my S7 the Wear OS app will not recognize it which causes the watch to get stuck in the setup phase, making it useless. This was after multiple and different connection attempts, resets, reboots and factory (watch only) restores. The watch will show up under bluetooth and create the initial connection but it will not stay connected. Anyone have any idea? Is this ROM missing something?
Edit: Mid way through the install, I wanted to note that I checked for the issue after doing the "Install Stock Oreo" but before Root and everything worked as it should. Wear OS sees the watch instantly and Bluetooth connects fine.
Edit: So I am a day into using the ROM and I am still having issues. While it will connect and work perfectly fine now, when ever I do a reboot of the phone the watch no longer connects. I will just get constant Bluetooth Connection Requests, every single time the watch tries to get data, and it never actually connects. To fix this I need to do a complete reset of the watch and do the whole setup process again. As you can imagine this is no good, expecting to wipe my watch every time my phone reboots makes it still almost useless.
Click to expand...
Click to collapse
I believe I know what the issue is, I'm testing a fix (for THIS ROM) as we speak. Stay tuned. Maybe tomorrow if I have time and it works I'll update the OP. BTW, this ROM and my other ROM are TOTALLY different. Thanks for the feedback!
FranMLG said:
I have not had any problems so far, here I leave you for the link to download and try those who are interested in VIPER4ANDROID: https://drive.google.com/file/d/1572ORe6TOrsRBuxWWBChH-WMnxkvcUjH/view?usp=drivesdk
You just have to flash it with Flashfire, but if you do not pull them, let me know Thank you very much !!! Kevin for the effort!
Click to expand...
Click to collapse
What do you mean by this? "but if you do not pull them, let me know"
And tell me more about Viper4Android, and if it works solid for you on this ROM...then I'll consider adding it. Thanks!
New version, see change log in OP for details.
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
jrkruse said:
If you choose the keep safestrap option during root the it will flash the system/vendor/etc/ fstab.qcom that totally removes data encryption but when that fstab.qcom is flashed it also requires a data wipe for phone to boot then when you install xposed you won’t see that error but either way you end up wiping data so your choice
Sent using some kind of device I modified
Click to expand...
Click to collapse
Hi, why you have to flash this - HEROQLTE_USA_VZW.pit on 930t, is it ROM specified? if I do and don't then what are pro and cons?
---------- Post added at 01:36 PM ---------- Previous post was at 01:26 PM ----------
josh2020glacier said:
Yeah i.a give this a shot in a little. Do I need to root phone or can I just flash through Odin. Sorry not used to this locked bootloader crap..... s8crj1 are the last 6 digits of the software I'm on. I did receive the latest update will this effect me installing this. Sorry as I said not used to this locked bootloader crap.
Click to expand...
Click to collapse
since bootloader is locked you can't use TWRP so you have to use Flashfire to install this ROM, as you know flashfire required root so you have to setup the base per OP and then root the base then install the ROM and then root it again, read the first page I don't think you will get a instructions more detailed then his
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Alkan3 said:
Okay so I just realised I was posting comments on the old thread, my bad. Coming back to the question, can the boot animation be changed? I've messed with the qmg files in an attempt to replace the weird, nauseating rainbow animation but even after overwriting the latter, it persists. Looking forward to a reply kek
Click to expand...
Click to collapse
Nauseating rainbow? LOL. Sorry. This is much more of a general question though, that wouldn't exactly pertain to this ROM specifically. And given I don't have an answer, I'd try searching BootAnimation How-Tos to get this customized. The ONLY thing I did regarding this was replaced the existing files with the rainbow ones. That's it. Apologies in advance.
Just discovered an issue: RCS (Rich Communication Services / Chat) texts don't show up in Android Messages app. See "Known Issues" in OP for a solution. BTW I posted a new ROM version a few days back that allows many choices in Aroma Installer. Make sure to pick Samsung Messages (instead of Google), so you get RCS chat text messages!