Figured you TOPA folk needed your own thread... At least to track TOPA-specific issues!
FRX07.1 is here!!
This is a maintenance release - basically taking the newest components to make a completely up-to-date (as of Sept. 1).
Quite a lot has changed since FRX06 - the install process hasn't really, but be sure to read the changelog in the next post and the caveats in post #3!
<<<This is a link to the... FAQ Click it!!>>>
I have created a complete bundle of FroYo with a stable kernel from GIT (August 19 / 1348), and rootfs from GIT (Sept. 2).
Please, feel free to DONATE to the XDAndroid project!
Every little bit helps!
Directions:
1. Download the full bundle (zip). (Updated September 1 2011)
If instead you just want the system.ext2 (zip) (Updated July 15 2011) file by itself... Don't download this if you're not sure! Grab the full bundle!
2. Extract it. You’ll see a folder, FRX07.1, copy its contents to the root of your SD card. If you want to run Android from a folder instead of all the files on the root of the card, follow the steps below.
3. Go into the STARTUPS folder. Grab the appropriate startup.txt for your device (if you don't know what device you have, you should read the FAQ), and move it to the root of the card (or where you run haret.exe from. If you want to change the location of the build, put a rel_path= statement in the cmdline section of the startup.txt. Mine is located two folders deep on the SD, so my rel_path=Androids/TP2Ref)
4. Screen calibration - you have three choices:
Re-use an old ts-calibration file if you have it and you know it's good.
Download the ts-calibration.zip file and extract it to where you put the rest of the files (root of SD or in a folder - make sure it all stays together!)
Manually calibrate - boot with no ts-calibration file and watch the boot process - you'll be asked to hit 5 points to calibrate the screen. If you have issues calibrating, try an older kernel (1225 works well) Once you have the calibration file hold on to it (make 15 copies if it's a good one ), reboot & go back to the newest kernel!
6. Run haret.exe.. Profit!
Let it settle out on the first boot. Many have reported they had to reboot basically because it was so slow - if you let it sit for about 10 mins so the media scanner can go thru everything, etc. it will be much more pleasurable experience. If you want adb in and watch the processes via top, you'll see why the phone seems so slow - there's lots of background processes cranking because this is the first boot .
Troubleshooting:
Please read the... FAQ
If you have any issues with the kernel, feel free to change it:
There are some devices that are having issues with the newest kernels. Please see the kernel autobuild service to get archived kernels. Once you download a replacement kernel, go to where you run haret.exe from - remove your old zImage/modules-xxxxx.tar.gz. Take the new zImage/modules-xxxxx.tar.gz and replace the old ones, same folder - where you run haret.exe from. Make sure the ‘zImage’ is named just that. Do not rename the modules file, do not extract it - should be in .tar.gz format.
See Incremental Updates for more information on updating the kernel and other components.
Random issues can often be solved by forcing the system to create a new data.img. If you're worried about losing data (all user data is stored in the data.img!!), Titanium Backup works quite well. If you wish, you can rename the data.img to something else, and let the system create a new one - just to see if it resolves your problem.
Similarly, if you wish try formatting your SD card - I prefer to use the HP Tool - do a full format, FAT32.
Even though this build is considered fairly stable, you are more than likely going to run into issues. The next post will address issues particular to this build - PLEASE READ THESE before asking questions! Feel free to post questions in this thread, I will do my best to address them. Big thanks to stinebd for releasing the system image, and of course the other developers for their hard work on making these kernels available.
stinebd's Changelog:
stinebd said:
Here’s a new release for you, folks. This is a major release with a ton of changes, new features, and fixes. Our friend hyc/highlandsun did most of the heavy lifting for this release. Highlights include a rewritten RIL with support for world phones and greatly improved CDMA support; fixes for the media codecs; fixes for MMS on Sprint; increased security with the Superuser app.
A list of changes is included below. The FRX07 system image is available for download now, and will require the use of a new rootfs image, also available now. Additionally, we have a new bundle containing everything needed to enjoy a full FRX07 system.
Note: Due to the incredibly long list of changes, this is a somewhat condensed, terse changelog describing only the overall scope of the changes.
FRX07:
frameworks/base:
Major frameworks changes for CDMA/GSM dual-mode worldphone support. (hyc)
Fixes for data connection handling to improve startup time. (hyc)
Fixes for wifi handling to avoid issues on hanged drivers. (hyc)
Stagefreight (media codecs) fixes. (hyc/viruscrazy)
Fixes for Sprint’s wonky MMS markup structure. (hyc)
Fix MediaScanner not finding audio files (including ringtones) in system.ext2
hardware/libhardware_legacy:
Minor GPS driver fixes. (Alex[sp3dev])
Rename wifi interfaces to wlan0 on all devices (hyc)
hardware/xdandroid-ril: Major RIL refactoring for improved performance on all devices, and added CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Gallery3D: Switched back to Gallery3D as the gallery app (closes bug #111)
packages/apps/Mms: Fixes for Sprint’s wonky MMS markup structure. (hyc)
packages/apps/Phone: Fixes for CDMA/GSM dual-mode worldphone support. (hyc)
packages/apps/Superuser: Added the Superuser package for authorizing su privileges. This, along with our signed builds, provides greatly increased security for the end user (mostly against malicious apps from the Market).
system/extras/su: Added as a dependency for the Superuser package
vendor/qcom/android-open: Include missing stagefright codec symbols. (hyc/viruscrazy)
To coincide with the FRX07 system image, the following rootfs changes have been made:
init.froyo.rc modifications...
Adjust wpa_supplicant service for the new abstraction provided by libhardware_legacy, as well as interface rename
Abstract the hciattach service to provide bluetooth support on both chipsets
Rename wifi interface to wlan0 on all devices
apns-conf.xml updated
keymaps completely reorganized, and RHOD end-call key has been remapped to be the Home key in Android.
default.prop: set ro.secure=1 to lock down the adb shell - su can be used with the Superuser app to authorize root access in adb if needed.
Click to expand...
Click to collapse
Layman's Changelog
(As in, the changelog I wrote )
FRX07.1 Changelog:
RHOD - all buttons on the front no longer wake the device. Only the power button wakes the device now.
Updated to the newest RIL
hyc's modified libs for video now baked in - *most* HQ YouTube videos (and other HQ videos) should finally work!
RHOD & TOPA - Userland (Android) now controls the LED by default now. If you need to debug sleep, you will have to change the behavior manually. See Detule's post on this topic.
Facebook sync should now work, out-of-box.
FRX07 Changelog:
Updated RIL (thanks hyc!) - this covers many different bugs that were in the old RIL - I'm only going to cover the major ones...
CDMA now works correctly (for the most part). force_cdma (and north_am_dialing) is now deprecated (not needed/ignored!)
You can boot with a SIM in on a CDMA device and choose your GSM or CDMA on the fly under Settings.
Location based on towers now works on CDMA.
1xRTT now displays correctly, but I never seem to get EVDO Rev.a... I always get 0. This is represented by a 3g icon, as this is what the Android framework provides.
Full MMS support! Please see this page for configuration instructions. Will need help fleshing out the list of carriers folks!
Spotty service, switching towers, etc should no longer cause the dreaded SoD (Sleep of Death) condition!
(Basic audio) 3.5mm support for RHOD400/500
Droidwall works out of the box now
Keyboard backlight now fades in/out
Gallery3D back in! Picasa Web Sync comes with it
A couple new apps added to AndroidApps folder:
rpierce99's app GetLogs
Titanium Backup
Caveats:
BT - works! But audio doesn't route. See this thread if you're feeling adventurous and want to play with/don't mind using some unstable/incomplete code...
After booting, TOPA seems to have a crippling issue where if the first call is inbound, the phone reboots. So I guess after booting make an outbound call and everything is fine? Someone please confirm...
That audio routing thread is in the RHOD section, and I've only tested it on a RHOD - but AFAIK it should work on other devices. Let me know.
Whew, here you go TOPA folk!
I figured you guys needed a thread for this, if only to track issues that are TOPA-specific. Let me know what I need to add in the caveat section for TOPA! Also let me know if ts-calibration file is good or not .
Also, if you guys already have FRX07 running/working... there's nothing new here. Mainly using this thread as a place for newbie's to go and you experienced folk to help me track issues again for new users!
I have a small problem,when I run haret it comes to animated logo and then my phone go to rebote?
Every time when is starting FRX07 the mobile reboot and start's windows?. Where is the problem?...
kujrv1 said:
Every time when is starting FRX07 the mobile reboot and start's windows?. Where is the problem?...
Click to expand...
Click to collapse
Yes,that's right...
And solution...?
Use the latest kernel and rootfs, not the ones bundled with frx07.
kujrv1 said:
And solution...?
Click to expand...
Click to collapse
kujrv1 said:
Every time when is starting FRX07 the mobile reboot and start's windows?. Where is the problem?...
Click to expand...
Click to collapse
hb5 said:
I have a small problem,when I run haret it comes to animated logo and then my phone go to rebote?
Click to expand...
Click to collapse
Sorry guys grab the latest kernel. I just put that in the caveat list, thanks.
I put the last kernel and i have the same issue. Reboot on Animated logo
I too have the reboot issue on animated start screen. Latest kernel used.
Any suggestions??
last three kernels didn't work on my topa100
it runs haret and then reboot the device
Will you guy's please make an effort and read other posts on this topic instead of clogging up the forum.
Everything you need to know has been posted already, multiple times.
Zaknahhas said:
last three kernels didn't work on my topa100
it runs haret and then reboot the device
Click to expand...
Click to collapse
gtti148 said:
I too have the reboot issue on animated start screen. Latest kernel used.
Any suggestions??
Click to expand...
Click to collapse
kujrv1 said:
I put the last kernel and i have the same issue. Reboot on Animated logo
Click to expand...
Click to collapse
Wait...
zooster said:
Use the latest kernel and rootfs, not the ones bundled with frx07.
Click to expand...
Click to collapse
Seems to make me think it's working on the newest rootfs and kernel - is this not true?
arrrghhh said:
Seems to make me think it's working on the newest rootfs and kernel - is this not true?
Click to expand...
Click to collapse
I've been switching my TOPA to FRX07 + .27 + rootfs (all selfbuilt) yesterday, and it boots up fine since the latest kernel fix.
So anything reported not working with latest autobuild kernel implies user error for me if it resets during bootanimation.
arrrghhh, thanks for taking care of the topa threads! So I can concentrate on not getting anything done for .35
Michael
arrrghhh said:
Wait...
Seems to make me think it's working on the newest rootfs and kernel - is this not true?
Click to expand...
Click to collapse
Topaz can boot with last kernel, with htc-msm-linux @ 20110718_223029 it doesn't.
zooster said:
Topaz can boot with last kernel, with htc-msm-linux @ 20110718_223029 it doesn't.
Click to expand...
Click to collapse
20110718_223029 is the latest kernel tho... are you saying emwe is lying? .
emwe - perhaps you should be like us heathens and try to run the pre-compiled binaries? I know, blasphemy...
Hi to all, is 2 day frx7 work in my topaz all work bt, wifi, 3g, lokscreen, rotate screen (no good) photo, opera, sms, gps an battery when is 10% work 6 hour, is speed. i like use android. thanks
Related
This is based on P7500XWKK4_P7500NEEKK1_NEE Galaxy Tab 10.1 / HC 3.2 ROM but it is for the P7100 tablet.
Please read the whole thread before you flash. There are a couple of BUGS!
Flash on your own risk. I cannot be held responsible for any damage caused to your tab
This is not all my own work, I have worked with other members to get this ROM working.
DO NOT USE FACTORY REST IN ROM, EVER, USE WIPE SCRIPT TO RESET IF YOU NEED/WANT, IF YOU ARE GOING TO USE THE FACTORY RESET OPTION, YOU WILL BOOTLOOP!
kernel is provided by pershoot - compiled by myself - all kernel work is from pershoot here
first-time users you need to wipe! use supplied wipe script. Please read carefully, everything is here to get it flashed onto your TAB, if you do not understand what to do, ask, we will gladly try and assist.
Copy the downloaded files to sdcard (/sdcard/) and flash via ClockWorkMod
As always backup your data / apps before doing this! I use Titanium backup, search for it in the market.
Please read the thread before you report a bug. don't report already reported bugs. keep the thread clean. use xda's search feature
You need unlocked bootloader, click on link to see how to unlock.
You need root, click on link to see how to root.
Note: you MUST have Samsung Kies installed, or device drivers, for adb to work! It seems a lot of people do not have it installed, which causes a lot of confusion.
You need ClockworkMod Recovery (it is part of ROM Manager), download ROM Manager from market to install ClockWorkMod.
If you are a new to this please read this guide: http://forum.xda-developers.com/showthread.php?t=1232664, on how to unlock and root your TAB.
Please remember that this modified rom of P7500, Some features will not work 100%, most does but there are going to be a few bugs.
Features
Honeycomb 3.2 Based on P7500XWKK4_P7500NEEKK1_NEE ROM for the P7500, it will report as a P7500 but it is a P7100. Cannot change it to P7100 then some applications do not work.
Samsung TouchWiz UX UI
allows OC up to 1.4Ghz kernel, based on pershoot kernel compiled to include the following modules: ntfs.ko, tun.ko, cifs.ko
Kies via Wifi works on latest Kies in windows
Zipaligned
Deodexed - First boot will take a while, so be patient, if it did not boot after 30min then force a reboot!
Voodoo sound improvements (Download voodoo from Market)
NEVER USE FACTORY RESET IN INSIDE ROM SETTINGS OR DELETE DATA/CACHE IN CWM. YOU WILL BOOTLOOP!
See second post for other items
Bugs
3g: SIM PIN Lock must be removed for 3g to work after first boot. If you have SIM PIN please disabled it in Setting->Location and Security -> Set up SIM card lock
None of the security features work, Lock screen, PIN, Pattern, Password. If someone can let me know why and how to fix let me know!
Camera currently is only 3.2mp. May Crash sometimes - working on it.
Please report Bugs in thread
Thanks to:
pershoot, for getting the kernel working! He is the MAN! He worked nights to get the kernel working on the 10.1v, with not even having the device!
SEO, He has assisted me a lot over the last couple of months!, if it was not for him I could not have done this
To the community that got me into this without them I would not have been able to do this.
If I missed someone let me know it was not intended.
Changelog:
1.2.5.v: VoiceSearch.apk - deodexed
1.2.4.v: Camera fixed - touch autofocus - seo
1.2.4.v: Kernel modules cifs and ntfs added.
1.2.3v : Camera Fixes as per SEO
1.2.2v : Removed FactoryTest.apk and Factory.apk as per SEO suggestion.
1.2.1v : Public Release Build
1.2cv : third test build - limited testing
1.2bv : Second Build - internal
1.2av : Initial Build - internal
Download:
- 1.2.5v Full ROM
- please flash the "WIPE" zip, TB Galaxy WIPE script (SEO's), required for new users coming from stock. This will FACTORY RESET your tab but /data/media(sdcard) (your music, pictures & videos) will be left intact.
- this will NOT factory reset your tab if you're not on older version of this rom
More information available from. http://ismaakit.com/blog/
Kernel sources is compiled by me to make sure it is working 100%, but all credit goes to pershoot.
See this post: http://forum.xda-developers.com/showpost.php?p=20050409&postcount=128 for a different location. Thank you to algzed for providing this location.
Please do not link directly to the files, use this thread if you want to link.
[Q]
I updated and noticed cifs.ko is not included?
[A]
Here you go: Link This includes a compiled kernel without debug-info, it also include all the modules that is compiled for pershoots kernel. List of modules included:
asix.ko
aufs.ko
auth_rpcgss.ko
cifs.ko
dhd.ko
ff-memless.ko
hid-sony.ko
lockd.ko
nfs_acl.ko
nfs.ko
ntfs.ko
rpcsec_gss_krb5.ko
scsi_wait_scan.ko
sunrpc.ko
tun.ko
xpad.ko
[Q]
Where are the modules installed?
[A]
Have a look on the tablet via adb
Code:
adb shell
cd /lib/modules
ls
Latest Official buke2 Modem:
adb reboot bootloader
fastboot flash modem modem.bin
fastboot reboot
YOU DO THIS AT YOUR OWN RISK!
Modem.bin
-------------------------------------------------------------------------------------------------------------------
TIP: Enable USB Charging
Code:
adb shell
cd /sys/class/power_supply/battery/
echo 1 > force_usb_charging
To disable it:
Code:
adb shell
cd /sys/class/power_supply/battery/
echo 0 > force_usb_charging
b.t.w. a couple of users has asked why not default?
I DO NOT LIKE THE IDEA OF CHARGING THE BAT FROM USB, IF IT WAS SUPPOSE TO DO THAT, IT WOULD HAVE BEEN ENABLED, but that is me, you are welcome to do it if you wish.
This is active until you reboot. Then you will have to redo.
-------------------------------------------------------------------------------------------------------------------
TIP: IF YOU MAYBE LOOSE ROOT IF YOU RESTORE A ROM, TO GET ROOT BACK JUST DO THIS:
Code:
adb remount
adb shell chmod 6755 /system/bin/su
-------------------------------------------------------------------------------------------------------------------
You push me to flash my tab XD
Excellent job ! Thank you
I just got a tiny question, is it possible to made a touchwiz UX.zip apart ?
To keep the beauty of Honeycomb ?
Just asking
Downloading, will give this rom a try after download has finished
Thnx ISI (and offcourse seo and pershoot) to for all your work.
Downloading rom and will flash when, it's finished.
Richard
Send from my rooted 10.1v
Great Rom
Ok,
Fist of all thanks for having this new version of android on my tablet.
This is how i installed the ROM.
Coming from your HC3.1 1.03v:
booted in recovery via rom manager
install zip from sdcard isi-galaxy-1.2.1v.zip
wipe cache
wipe dalvik
reboot
I first thought my tablet was hanging, for several minutes it was stuck at the samsung logo during boot, so i hold the powerbutton and rebooted. After that it booted ok. Maybe i had to wait longer?
But everything seems to be ok. Appearantly it doesn't wipe
For me this rom is beter than the previous since I don't use camera and 3g.
The Calendar app is now amazing, it is fluent like it should have being.
I will report back if i encounted errors.
Fancois said:
You push me to flash my tab XD
Excellent job ! Thank you
I just got a tiny question, is it possible to made a touchwiz UX.zip apart ?
To keep the beauty of Honeycomb ?
Just asking
Click to expand...
Click to collapse
Nope, not at the moment. Maybe later. Let us get it stable first!
thzone said:
Ok,
Fist of all thanks for having this new version of android on my tablet.
I first thought my tablet was hanging, for several minutes it was stuck at the samsung logo during boot, so i hold the powerbutton and rebooted. After that it booted ok. Maybe i had to wait longer?
But everything seems to be ok. Appearantly it doesn't wipe
I will report back if i encounted errors.
Click to expand...
Click to collapse
Yeah you should have waited, first boot will take a while because the ROM is DEODEXED. After that is should fly.
ISI,
Do you know if the hooolmglow theme will work on this rom.?
Backing up my apps right now, then the flashing wil begin.
Thnx again
Send from my rooted 10.1v
isimobile said:
Yeah you should have waited, first boot will take a while because the ROM is DEODEXED. After that is should fly.
Click to expand...
Click to collapse
isi, some things I found so far while working on my own build:
- keeping stock p7500 gralloc.tegra.so / hwcomposer.tegra.so + stock 7500 kernel make video playback smoother. way smoother than *old* replaced hw libs + pershoot kernel. (of course camera does not work and orientation is always flipped but that's ok with stock kernel) we should wait for new official kernel source and keep p7500 libs in the future
- FactoryTest.apk BLOCKS setupwizard. removing FactoryTest.apk and Factory.apk should fix setup wizard and non-working lockscreen. pls test on your build.
I don't have much time ATM to fix camera / seccamera / secmediarecorder. will do it tomorrow and will post the apk here for you.
cheers
EDIT: btw I am not 100% sure that choppy video playback is caused by hw libs / kernel OR nvodm_* libs. no time to check atm.. will do later or tomorrow
You guys deserve a Christmas present. I know you don't take donations seo but what about a beer/coffee isimobile ?
seo said:
isi, some things I found so far while working on my own build:
- FactoryTest.apk BLOCKS setupwizard. removing FactoryTest.apk and Factory.apk should fix setup wizard and non-working lockscreen. pls test on your build.
I don't have much time ATM to fix camera / seccamera / secmediarecorder. will do it tomorrow and will post the apk here for you.
cheers
EDIT: btw I am not 100% sure that choppy video playback is caused by hw libs / kernel OR nvodm_* libs. no time to check atm.. will do later or tomorrow
Click to expand...
Click to collapse
Will test later today. thanks.
I got Camera at 8mp but Video Recoder crashed on me so I decided not yet to release and keep stock as to have a working camera set.
Thanks will wait for your patched files. I am no smali expert, would rather wait for you
[Edit] I can confirm if you delete those two files setup wizard works and lock screen as well! Great! Busy fixing....
Assistance needed: Someone with a fast internet connection. I only have a 512kb connection at home. It takes four hours to upload. So I did the change online. Hopefully it will work. It should!
Can you please test a fix for me. I did the fix online in the zip file not to upload everything from scratch.
Download this file. Do a full wipe and install. Post here if it works!
If no one tests it, I'll try that fix when I get home in a few hours...
isimobile said:
Assistance needed: Someone with a fast internet connection. I only have a 512kb connection at home. It takes four hours to upload. So I did the change online. Hopefully it will work. It should!
Can you please test a fix for me. I did the fix online in the zip file not to upload everything from scratch.
Download this file. Do a full wipe and install. Post here if it works!
Click to expand...
Click to collapse
Sorry isi im at work right now....
Will test tonight if still needed
So first flash wipe. Zip then flash rom....?
Send from my rooted 10.1v
Downloading...
Will flash and report..
-First Boot completed
-Setup - completed
-3G working
richard2311 said:
ISI,
Do you know if the hooolmglow theme will work on this rom.?
Backing up my apps right now, then the flashing wil begin.
Thnx again
Send from my rooted 10.1v
Click to expand...
Click to collapse
Not at the moment, will ask him later to get the theme.
Sent from my GT-P7500 using Tapatalk
isimobile said:
Assistance needed: Someone with a fast internet connection. I only have a 512kb connection at home. It takes four hours to upload. So I did the change online. Hopefully it will work. It should!
Can you please test a fix for me. I did the fix online in the zip file not to upload everything from scratch.
Download this file. Do a full wipe and install. Post here if it works!
Click to expand...
Click to collapse
Hi ISI
Just to confirm that it works
Just have to change than my signature
algzed said:
Hi ISI
Just to confirm that it works
Just have to change than my signature
Click to expand...
Click to collapse
Cool thanks.
Sent from my GT-P7500 using Tapatalk
I am not responsible for any possible bad effects which may result from using included software! You flash it on your own risk!!!
STOCK RELOADED v1 fix 1
Kernel base: stock XXUANC3 (kernel 3.4.0-1131235)
Kernel ramdisk: modded
Features: a few...
Security level: low!
Purpose: giving everyone who loves free exploring of Android secrets and who doesn't consider security as an absolute priority and who wants to put some life in this, indeed, awesome device, a possibility of playing with his device without disturbing restrictions, forced by Samsung, at least until fully-custom kernels, compiled from sources, appear (and that may take some time, as source code available atm seems to be broken, causing all the compiled kernels to stuck at boot screen).
Features working out-of-the-box:
- su binary from SuperSU by Chainfire @ /sbin/su (binary only for scripting purposes! Flash cf-root to use SuperSU app!)
- busybox 1.22.1 binary compiled by Stericson @ /sbin/busybox
- init.d support - just put your favorite scripts into /system/etc/init.d using any file manager and chmod 755 (not 777! it's NOT smart to permit write access for "world" to any system file), chown root:root, they will run on every boot. Well, to be honest, above permissions are given to all the scripts automatically during boot, but it has not yet been tested
- SELinux: Permissive - Samsung's most recent policy of forcing SELinux Enforcing mode by pre-compiling it into a kernel binary part, found in latest KitKat builds since at least a few months, HACKED FOR THE FIRST TIME EVER using innovative method of injecting an information directly into kernel memory space and forcing overwriting potentially-persistent kernel symbol value on-line during boot!)
- unsecure adb access (not tested yet)
- ext4 tweak: 20 sec (instead of stock 5 sec) write commit delay for /data partition (significantly increases IO performance!)
- some further, minor modifications
WARNING!!!
- flashing this WILL undoubtly trip KNOX, avoiding your warranty (which atm cannot be reverted! in any way)
- flashing this WILL cause a warning message of avoided warranty to be displayed on every boot (ofc it disappears right after reverting to stock boot.img)
- flashing this WILL disable some of the very important security features provided with stock firmware!!!! For advanced and experienced users only!!! Use at your own risk!
Known issues:
- AllCast Share mirroring not working (typical for all Samsung devices running not-exactly-stock kernels since S3). WORKING FIX AT POST #16!!!
http://forum.xda-developers.com/showpost.php?p=54516532&postcount=16
Please consider solution from post #3 as not-always-working and depreciated!
Installation:
- compatibile with XXUANC3 firmwares but probably also with other (past and hope future too...) KitKat 4.4.2 Samsung branded firmwares;
- rooting by Chainfire's CF-Root first recommended as it will install SuperSU app in Android (this kernel contains su binary only giving su access without any policy settings!);
- enter download mode and plug the tablet via USB...
- ...select provided file in PDA section (and NOT touch anything except that)...
- ...and flash with Odin in a same way as CF-Root or like anything else...
- enjoy.
DOWNLOAD HERE:
Current version - STOCK RELOADED v1 fix 1
http://www63.zippyshare.com/v/87557346/file.html
FIXED: file name changed so it can be flashed directly by Odin without renaming! Sorry for this silly mistake!
=======
Changelog:
v1 fix1:
- fixed permissive mode due to trivial error;
- delayed init.d execution to a moment AFTER init process set cfq scheduler so it is not overriding mmcblk0 tweaks (if put in init.d) anymore;
- minor code cleanups
v1:
- initial release
- init.d support
- SELinux permissive
- unsecure ADB
- ext4 delayed commit for /data
=======
Stock XXUANC3 kernel (to revert changes)
http://www65.zippyshare.com/v/32441894/file.html
Revert using Odin, in the same way you've installed a Reloaded Version....
Awww man,...I wish i could flash this, but I'm on the exynos =(
Sent from my SM-P900 using Tapatalk
rgolnazarian said:
Awww man,...I wish i could flash this, but I'm on the exynos =(
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Sorry pal, Qualcomm only, not even a chance to run this same way as the devices (and mostly important: provided software, ie. system structure) DIFFER A LOT between themselves.
Update 1: uploaded fix #1 which is resolving some trivial issues found in initial version; sorry for that, now we can say that every described feature has been included hope for some feedback... thank you...
Update 2: FIX FOR NOT WORKING SCREEN MIRRORING CAN BE DOWNLOADED HERE:
http://www67.zippyshare.com/v/25492738/file.html
I have personally modified a library that is being used by screen mirroring feature, which forces video encryption using keys from stock kernel, and which prevents to run mirroring at all . This is an issue of any modified kernel, on any Samsung device. Attached library fixes this, by disabling HDCP at all. It has been reported that the library resolves the issue for any Qualcomm based Samsung device running 4.4.2 KitKat and for any custom kernel. It will NOT work for Exynos devices...
Installation:
- download attached libwfdsm.so file
- overwrite genuine one in/system/vendor/lib (important! NOT /system/lib!!!!)
- chmod 644 libwfdsm.so ||| chown 0.0 libwfdsm.so ||| restorecon -R /system/vendor/lib
- mirroring will work again after reboot!!
YAY!
Beautiful, absolutely beautiful. You made ma a very happy man with this. I'll flash this as soon as I get home from work. Can't wait to try it out, the stock kernel is giving me SOD and frozen wifi issues sometimes.
esgie said:
Sorry pal, Qualcomm only, not even a chance to run this same way as the devices (and mostly important: provided software, ie. system structure) DIFFER A LOT between themselves.
Update 1: uploaded fix #1 which is resolving some trivial issues found in initial version; sorry for that, now we can say that every described feature has been included hope for some feedback... thank you...
Update 2: FIX FOR NOT WORKING SCREEN MIRRORING CAN BE DOWNLOADED HERE:
http://www67.zippyshare.com/v/25492738/file.html
I have personally modified a library that is being used by screen mirroring feature, which forces video encryption using keys from stock kernel, and which prevents to run mirroring at all . This is an issue of any modified kernel, on any Samsung device. Attached library fixes this, by disabling HDCP at all. It has been reported that the library resolves the issue for any Qualcomm based Samsung device running 4.4.2 KitKat and for any custom kernel. It will NOT work for Exynos devices...
Installation:
- download attached libwfdsm.so file
- overwrite genuine one in/system/vendor/lib (important! NOT /system/lib!!!!)
- chmod 644 libwfdsm.so ||| chown 0.0 libwfdsm.so ||| restorecon -R /system/vendor/lib
- mirroring will work again after reboot!!
Click to expand...
Click to collapse
I was literally just about to post in the old thread with bad news about the modified "libwfdsm.so" file & screen mirroring with a custom kernel...if u remember i confirmed that the file u altered would work with a custom recovery on the 8.4 lte & i just assumed that it would work with an altered boot.img as well but unfortunately thats not the case after testing the other night (unless something else is wrong with my setup). So...my question is have u changed something else since then to allow it to work again & have u personally tested this yourself?
sorry to hijack the thread...didnt know if i should pm or post in the older thread
THEDEVIOUS1 said:
I was literally just about to post in the old thread with bad news about the modified "libwfdsm.so" file & screen mirroring with a custom kernel...if u remember i confirmed that the file u altered would work with a custom recovery on the 8.4 lte & i just assumed that it would work with an altered boot.img as well but unfortunately thats not the case after testing the other night (unless something else is wrong with my setup). So...my question is have u changed something else since then to allow it to work again & have u personally tested this yourself?
sorry to hijack the thread...didnt know if i should pm or post in the older thread
Click to expand...
Click to collapse
No problem, anyway, thanks for pointing the issue out! This may be an important information for mirroring users!
Since then I didn't change anything, yet. Really, I am also not sure if I have tested it with modified kernel, as the one posted here is the first kernel for P905 at all, and it's not even "fully" customized, as the kernel binary base was left unchanged.
So, I'd like to be sure: you are saying that modded lib:
- fixed the problem for custom recovery, but...
- ...didn't fix it for custom kernel
right?
I was looking for a solution to persistent enforcing mode since some time, so I was flashing test boot.imgs from time to time, then reverting to stock again, meanwhile I created above lib, I can't really be sure about if it is working when both bootimg and kernel are customized (this would also be an opposite to previous Sammy's Android releases, where a single fix was solving all the issues related to customizations of both kernel and recovery!).
We also have to be aware that the issues may not be a result of flashing different kernel at all, but a result of the changes themselves, ie. disabled knox, disabled encryption of i-dont-really-know-what, etc, etc.
And the most important thing! Since I have heard of AllShareCast/Screen Mirroring for the first time (it probably appeared for the first time in S3/Note2/Note10.1), it always required resetting the flash counter - which could be viewed in download mode and which is NOT the same as Knox flag - to ZERO and that requirement AFAIR remained totally independent from the requirement of having stock boot/kernel (or lib patch). Have you checked the counter state? Did you reset it to zero again using Chainfire's Triangle Away after flashing non-stock kernel (which, obviously, TRIPPED the counter)? Can you check if it is working? Note that at least on my P905, Triangle Away still works flawlessly and resets the counter without any problems and even without a need of reboot!
Please check above info and try if the issue is fixed after running Triangle Away. I am leaving for a short business trip soon, so I'll perform my own tests with AllShare cast until next of the week, however, neither today nor tomorrow...
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
cavkic said:
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
Click to expand...
Click to collapse
Argh possibly too many dots in filename... will correct it tomorrow.
cavkic said:
I get an "md5 error! binary is invalid" when I choosse the file in Odin. I downloaded the file 6 times, and every time I get the md5 error.
What do I do?
EDIT: Renaming the file to "boot.tar.md5" seemed to solve the problem.
Click to expand...
Click to collapse
same here...
Hi,
I have a problem with screen mirroring.
Installed the patch and mirroring connects to the dongle, but the TV screen turns just black.
The dongle works perfect with HTC One M8, it must be a softwareproblem?
Thanks for help!!!
Will this work on the P905V (Verizon Variant)? I need to downgrade the permissions in my Security in order to use Towelroot, because they're set to Medium and I believe that prevents Towelroot to work properly. Most of the other Note 12.2 variants have been rooted....except the Verizon version.
Can anyone give me some advice please. When I enter the command in terminal emulator I get an error saying "Unable to open chown. No such file or directory". Am I missing something obvious lol.
Will this work on p907a AT&T version of note pro 12.2?
Sent from my SAMSUNG-SM-P907A using XDA Premium 4 mobile app
cnote74 said:
Will this work on p907a AT&T version of note pro 12.2?
Sent from my SAMSUNG-SM-P907A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On the topic name it says [P905 LTE ONLY], and your device is some different..
tdetroit said:
Will this work on the P905V (Verizon Variant)? I need to downgrade the permissions in my Security in order to use Towelroot, because they're set to Medium and I believe that prevents Towelroot to work properly. Most of the other Note 12.2 variants have been rooted....except the Verizon version.
Click to expand...
Click to collapse
I would like this answered as well. I also have the "v" variant. Maybe saying LTE includes many? See my link I attached, found while investigating this specific question.
http://www.usatoday.com/story/tech/2013/07/07/sprint-att-verizon-phones-network-carriers/2486813/
Ever since I rooted my tablet it goes on random reboot kicks. I want to start over. Also TWRP will not stick when I try to flash it.
I have many issues which I'm currently posing in their appropriate forums. It would be nice to wipe to a rooted stock.
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Thanks. The Galaxy is connecting to theTV, but the screen is only turning black - no Display...
Any idea?
Thank you.
esgie said:
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Click to expand...
Click to collapse
esgie said:
Guys!
I have probably found another solution for non-working Screen Mirroring / AllShare Cast when custom kernel is flashed (again, LTE devices only).
No need of modded lib
Seems that the only thing we need is to
1) run Terminal Emulator and type:
Code:
su -c setprop wlan.wfd.hdcp disable
(will work immediately; won't stick between reboots!), OR...
2) edit /system/build.prop file with any root file manager/text editor and add a line (no matter where):
Code:
wlan.wfd.hdcp=disable
(will work only after reboot; will stick between reboots).
Try this using kernel from op waiting for feedback!
Click to expand...
Click to collapse
I tried both methods and still get no devices found when I turn on screen mirroring.
ColBill said:
I tried both methods and still get no devices found when I turn on screen mirroring.
Click to expand...
Click to collapse
Hm.
This is weird, as the problems with allshare cast + custom kernels is not that "no devices are found" but that devices ARE found without any problem but the connection process fails after a few secs. This solution may help with the issue i described, but it will surely not solve the problem with no peers detected at all.
No peers detected = problems with wifi direct (are you able to send files between wifi direct between devices?)
Can you tell me what is your exact device config? And are you using allsharecast dongle or other third party hardware?
@fokus
Only one: also reset flash counter with Triangle Away and then try again. And make sure you spell the value in the command as "disable" not "disabled" - it's tricky and one can miss it...
Well, there are two additional things to add.
Guys, make sure you have updated Samsung's ScreenMirroring firmware update app to the latest version. And check out the samsung mirroring fix app in google play, which solves some issues for various devices (dunno which ones exactly as i have never been in need of using it).
The fix half worked for me lol. The tablet now connects fine to the Netgear PTV3000 but all I get is black screen. Step in the right direction though as at least it connects now. Just need to get a picture to show lol.
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
I DID NOT MAKE THIS ROM!!!!!! - A developer by the name of TheKit made this rom, so do not give me any credit for this rom, give it all to them.
I am simply linking it because I love this phone, I love Sailfish OS on it, and I think a lot of people would enjoy Sailfish OS on it as well and just don't know it is available.
Q: "What is Sailfish OS and why should I use it?"
A: Sailfish OS is a great OS for many reasons. Having used multiple android roms I can attest to the fact that:
1. It has MUCH better battery life (however it has a weird battery read bug, see issues below)
2. It is MUCH faster and generally more stable when it comes to the things that work (your calls won't drop, your system won't lock up due to lack of ram, etc.)
3. It has a great gesture driven UI that is a joy to use and very gorgeous to look at. No more of this all white bull**** Google has been forcing down our throats since 2014
Q: "How good is the battery life?
A: After a day of playing cave story at work and reading discord and listening to music, I am at about 30-40% end of day (I start at 8:30AM, stop at 4:00PM)
Okay now that the Q/A segment is over, lets get to the real meat
ISSUES
1. Battery Read is wonky, it only goes in 10% increments until it reaches 20%, then it starts going in 5% increments
2. If you use the 2.1.3.7 build keyboard backlight is broken, but it works fine on the 2.1.0.11 build
3. Bluetooth is wonky, I was able to play audio through speakers in the 2.1.3.7 build...
4. FM Radio is broken too
5. As the maemo-talk thread says, CDMA is untested, and like on Photon Q, most likely does not work. GSM works great though! :good:
6. The old 2.1.0.11 build has a slew of issues compared to the new 2.1.3.7 build. These include data not working out of box, wifi requiring a reboot to work, and auto rotation not working in a majority of apps by default. Consult this thread and the maemo talk thread for more help, and if you want rotation anywhere, install patchmanager 2.0 and auto rotate anywhere from warehouse for sailfish os.
Alien Dalvik install tutorial
I did not make this and do not know who did. the developer claims someone threw a brick at them with an sd card attached. The sdcard contained links to these files in the form of a text file names "monkeyAIDS.txt"
https://drive.google.com/file/d/1mS6di1jYfVeDoFBjcANS6SmfkhGyEKoa/view - AD Jolla C (different from the Turing phone rpm, this is built for 3.1.x kernels)
http://sfos.scanf.su/maserati/alien-patched.tar.gz
So extract both files to your ~/ (home) directory and type in the following:
devel-su
[insert root password you set in settings]
zypper in [alien dalvik rpm]
rsync -a /home/nemo/alien/ /opt/alien/
ln -s /vendor /opt/alien/system/vendor
reboot
OPTIONAL: fix for the default 320PPI value
devel-su
[insert root password]
vim /opt/alien/system/build.prop
change ro.sf.lcd.density to the value of your choosing (Droid 4 is 256)
Keyboard Backlight Fix, works on 2.1.0.11, don't know about 2.1.3.7 -- Thank you @moodroid for this legendary patch!
On <2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then do 'pkcon install mce' and 'systemctl restart mce'.
Download Links
Here is the thread with the Download Link to the 2.1.0.11 build
https://talk.maemo.org/showthread.php?t=99031&page=9
If you don't mind a lack of keyboard backlight and want a more up to date build, grab the new and fabulous leaked 2.1.3.7 Build:
https://drive.google.com/file/d/1k3MOCrMvbFb114Omf0MzSvnQ7wBkTiWH/view?usp=sharing
Basically if you are fed up with how ****ty the latest Lineage OS builds are and just want to try something new, give this a try. Why not? What have you got to lose. All in all great work by TheKit and I am very happy with the port as it is and I think you will be too.
Hi,
On <2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then doing 'pkcon install mce' and 'systemctl restart mce'.
Hope you get the OK to share your AD success!
Thanks
moodroid said:
Hi,
On 2.1.3.7, I got the keyboard backlight to work by creating an /etc/mce/20backlight.ini with:
[KeyPad]
BrightnessDirectory=/sys/class/leds/keyboard-backlight
Then doing 'pkcon install mce' and 'systemctl restart mce'.
Hope you get the OK to share your AD success!
Thanks
Click to expand...
Click to collapse
dude you are a legend!
I would add that to the OP but you are first comment so anyone viewing the op will see this. I will definitely tell TheKit about this (then again, he gave you the 2.1.3.7 build so you can just tell them yourself)
Greetings,
I've been playing around with SailfishOS on my Droid 4 in the past few days, and I have a few questions about the whole thing. TheKit publicly shared a 2.1.3.7 build for the Droid 4 on his thread at Maemo, is that the one you are talking about or is it a different build? As someone mentioned this specific build seems to have issues with wifi, and I have the same problem. I can't post links, but the download link to the build I mentioned is on page 12.
The 2.1.0.11 build seems to work fairly well, however I wasn't able to install Alien Dalvik. After the installation the "Android Support" button does show up in the settings app, however nothing happens when I click the start button. I also attempted installing an apk both via the GUI (by clicking on it in the downloads) and via the command line by using "apkd-install", but it doesn't seem to work. Full log of the installation process attached.
I talked with TheKit, and the 2.1.3.7 build I mentioned (the one at page 12) is indeed outdated. He just updated the OP at Maemo and added the latest 2.1.3.7 build, which I just flashed and it's working great. Also installed Alien Dalvik following the instructions in the OP and it seems to be working fine as well! However I wasn't successful with the backlight fix method yet.
For anyone wondering how I flashed the latest build I went CM11 --> SailfishOS 2.1.0.11 --> SailfishOS 2.1.3.7 (rel2).
NIKKOS said:
I talked with TheKit, and the 2.1.3.7 build I mentioned (the one at page 12) is indeed outdated. He just updated the OP at Maemo and added the latest 2.1.3.7 build, which I just flashed and it's working great. Also installed Alien Dalvik following the instructions in the OP and it seems to be working fine as well! However I wasn't successful with the backlight fix method yet.
For anyone wondering how I flashed the latest build I went CM11 --> SailfishOS 2.1.0.11 --> SailfishOS 2.1.3.7 (rel2).
Click to expand...
Click to collapse
Hi Nikkos,
Sorry - that was me that posted the backlight fix, and I agree that it doesn't work on 2.1.3.7-rel2. It'd worked on every other version I tried, and I've now edited my post above. Glad everything is working.
Sorry again
moodroid said:
Hi Nikkos,
Sorry - that was me that posted the backlight fix, and I agree that it doesn't work on 2.1.3.7-rel2. It'd worked on every other version I tried, and I've now edited my post above. Glad everything is working.
Sorry again
Click to expand...
Click to collapse
No worries.
If anyone is wondering how to change the SailfishOS UI scale (I find the default one to be way too big) here's how I did it via the terminal:
Code:
devel-su
rm /etc/dconf/db/vendor.d/locks/silica-configs.txt
dconf write /desktop/sailfish/silica/theme_pixel_ratio value
I believe the default value should be around 1.1; you can also reset the value to stock with:
Code:
dconf reset /desktop/sailfish/silica/theme_pixel_ratio
or read the value with:
Code:
dconf read /desktop/sailfish/silica/theme_pixel_ratio
Not exactly droid 4 related, but thought I'd share.
Okay, I got the backlight to turn on!
Type the following in the terminal:
Code:
devel-su
echo 255 >/sys/class/leds/keyboard-backlight/brightness
It seems to properly react to some triggers like standby after being turned on but not to others like sliding the keyboard in and out (which means it will always stay on if the screen is on, regardless if it's been slided in or out). My assumption is that the keyboard sliding trigger got broken in some way, as I believe that's the way the backlight is being turned on. The events which trigger the backlight seem to be stored in the file /sys/class/leds/keyboard-backlight/trigger, so I assume that would be a good starting point to attempt fixing this.
The keyboard backlight intensity can also be changed, just change the 255 to a different value (it goes from 0 to 255).
Note: this change is not permanent, it will need to be applied again at reboot. Writing a script which executes the above commands at boot should be trivial though, and I will include instructions when I get it done myself.
EDIT:
Here's how to make the change permanent. Following these instructions you will create a Systemd service which will turn the backlight on when active and off when inactive; it will automatically run at boot and it can also be controlled like any other Systemd service (i.e. using systemctl via the terminal)
Type the following commands through the terminal:
Code:
devel-su
cd /etc/systemd/system
touch keyboard-backlight.service
chmod 744 keyboard-backlight.service
You will now need to edit the keyboard-backlight.service file with a text editor (either vim or nano will do, vim comes preinstalled, nano does not). Depending on your preferred text editor, type the following:
Code:
vim keyboard-backlight.service
or
Code:
nano keyboard-backlight.service
Now write the following to the file and save it:
Code:
[Unit]
Description=XT894 keyboard backlight service
[Service]
Type=oneshot
ExecStart=/bin/sh -c "echo 255 >/sys/class/leds/keyboard-backlight/brightness"
ExecStop=/bin/sh -c "echo 0 >/sys/class/leds/keyboard-backlight/brightness"
RemainAfterExit=yes
[Install]
WantedBy=multi-user.target
Now type the following to enable the service:
Code:
systemctl enable keyboard-backlight.service
That's it. You can now control the service by using the following:
Code:
systemctl start keyboard-backlight //This will turn the backlight on
systemctl stop keyboard-backlight //This will turn the backlight off
systemctl status keyboard-backlight //This will display the service status
Can anyone share the google drive file from the first post? Is there an alternative link available? Or could you PM me a google drive link? Thanks!
Can anyone suggest the best/correct ROM-slot size for TWRP?
Is it still like for CM/LOS:
800MB for system
10MB for cache
and rest for data as one likes?