[Q] Video recording Samsung GT-I9001 - Galaxy Camera Q&A, Help & Troubleshooting

I am using the 'cyangenmod 10 alfa 6 version' with the Nexus kernel 3.062 version (Nexus Kernel V7.0_I9001_OC_UV_BIGMEM).
Video recording works with this configuration.
After the following procedure with TWRP: WIPE cache/Davikek cache/factory reset, flash 'Nexus Kernel V8.0_I9001_OC_exUV_BIGMEM'. fix permissions. reboot.
When I want to use video recording the screen keeps black, .tmp files are created in /DCIM/Camera and the application crashes.
Also tried it with 'Nexus Kernel V6.0_I9001_OC_exUV_HIGHbigMEM' same problem
What am I doing wrong?

JohnKersten said:
I am using the 'cyangenmod 10 alfa 6 version' with the Nexus kernel 3.062 version (Nexus Kernel V7.0_I9001_OC_UV_BIGMEM).
Video recording works with this configuration.
After the following procedure with TWRP: WIPE cache/Davikek cache/factory reset, flash 'Nexus Kernel V8.0_I9001_OC_exUV_BIGMEM'. fix permissions. reboot.
When I want to use video recording the screen keeps black, .tmp files are created in /DCIM/Camera and the application crashes.
Also tried it with 'Nexus Kernel V6.0_I9001_OC_exUV_HIGHbigMEM' same problem
What am I doing wrong?
Click to expand...
Click to collapse
BIGMEM with 720 dpi was the problem, changed resolution to 420 dpi. Problem solved.

you are posting on the wrong thread...this is for SAMSUNG GALAXY CAMERA EK-GC100...not a samsung "camera hardware" section..please read before you post

Related

[ROM][4 Dec][HC32] isi-galaxy 1.2.5v with pershoot's kernel

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

[ROM][ICS][IML74K] teamhacksung's CM9 ALPHA for Vibrant (BUILD 17)

Introduction
Teamhacksung (the rest of them really!) has been porting ICS (to be CM9) for the Galaxy S and they feel that it has reached a state where it would benefit from public testing. However this is still a very early versions and there will be bugs. Bug reports are allowed in this thread only. Please check the known issues section before reporting a bug. The most minor bugs are welcomed (we'd love to know them, but we may not fix them instantly).
Download
ROM: BUILD 17: androtransfer.com / Mediafire
Google Apps: Download from ROM Manager. (Or http://goo-inside.me/gapps/gapps-ics...213-signed.zip)
Google Apps Fixer: MultiUpload / tux-head.net / faramir.eriador.org (md5: af8bcaf5f8158e8e1be7097fc86b6b28)
Google Apps Fixer will fix your problem with not being able to add Google Account or Calendar Sync, but will also reset your Google Apps data. Only flash if you're having problems. If Google Apps Fixer does not work for you, do a factory reset from CWM (or Android Settings) and do not restore system data via TitaniumBackup.
Older Downloads
ROM
Build 16B: Mediafire
Google Apps
v7.1: MultiUpload / tux-head.net / faramir.eriador.org (md5: 8bf66137f18de45657f29c129a8f4d52)
v7: MultiUpload / tux-head.net / faramir.eriador.org (md5: 1888fbb15f36a076cb3908acaf1bd15a)
v6: MultiUpload / tux-head.net / faramir.eriador.org (md5: 6f51ded731d173c31b8c47395ca580b7)
v5.3: MultiUpload / tux-head.net / faramir.eriador.org (md5: e7d69d98a633b646e4f14e6a43208e66)
v5.1: MultiUpload / tux-head.net (thanks! Kaik541) (md5: 87415730a1db2e90d3588bc895f239e5)
v5: MultiUpload (thanks! Kaik541) (md5: 8667c9ddca581a98867fc02db29a2326)
v4: MultiUpload (thanks! Kaik541) (No longer include apps downloadable from Market.) (md5: 8b2dad009bc2f8724d27f78bca162495)
v3: internal
v2: MultiUpload (thanks! koush)
v1: MultiUpload (thanks! koush)
Installation
- First time flashing ICS to your Vibrant (or coming from another ROM)?
Root your device and install ClockworkMod Recovery.
Reboot into Recovery using 3-button-combo
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
WIPE again or Calendar Sync will not work.
- Upgrading from CM7?
Do a Nandroid Backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
- Coming from onecosmic's ICS build?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
Reboot into recovery and WIPE (wipe data/factory reset + wipe cache partition)
If radio doesn't work, go back to Samsung ROM and flash from there.
- Upgrading from another build of ICS by teamhacksung?
Do a Nandroid Backup!
Install the ROM from internal sdcard using ClockworkMod Recovery
Optionally install the Google Addon
Note: The upgrade process from CM7 to ICS is automatic, but downgrading from ICS to CM7 (or restoring Nandroid) requires flashing twice. Once from ICS and again from CM7's recovery.
Source
Kernel Source: https://github.com/teamhacksung/samsung-kernel-aries
Userspace Source: Patches are being integrated into CM's mainline tree. Device tree is available on teamhacksung's GitHub, but may not be buildable. No support for the source code, do not post that you are not able to build it.
Known Issues
Camera does not support scene modes
Phone unnecessarily gets data connection on device encryption password enter screen.
Cannot format external SD *
Android OS battery usage display higher than normal.
Sometime wrong SMS selected for forwarding
Format internal instead of external SD when requested to format ext. SD
Transfer speed slows down when screen off
Screenshot shutter sound
TV Out using HW-decoding (probably won't be fixed)
Sim Toolkit (probably won't be fixed)
No camera focus mode setting
Compass doesn't work in Google Maps v6
Unable to dial "0001" in some regions
Slow USB transfer speed for some people
Camera still photos problem after recording video
Top of widget selection selector says "Select screen lock"
Note: there are a lot of new options in Settings, but many of them are not implemented yet. DO NOT REPORT THEM AS BUGS. Additionally, some users has reported boot failure after disabling boot animation.
Empty wifi icon when using juice defender / sometimes on boot
Unused bottom bar in landscape dialer
Send contact to voicemail doesn't work
911/E911 is unknown, one report of weirdness
Fixed Issues
BUILD 17
Top of widget selection selector says "Select screen lock" (Upstream fix)
Chrome not working
Various other upstream fixes
BUILD 16
Regression in BUILD 15: Superuser application crashes
Regression in BUILD 15: Data Roaming enabled by default
Back camera does not record geotagging
Camera crashes when changing resolution
New: WM8994 Extensions (aka "Voodoo Sound") is now configurable from DSP Manager
BUILD 15
Duplicate entries in MediaScanner (will only prevent new duplicates, need to clear data to get rid of old duplicates)
Regression in BUILD 14: Screen flicker while turning off
Regression in BUILD 14: adb turns off every reboot
Mute-unmute needed on some calls (hopefully)
Notification power widget uncustomizable (now integrated into Settings)
Reboot into recovery on crash (it will still reboot, just not into recovery)
Unreliable Wi-Fi on screen off (hopefully)
Gallery face glow FCs
BUILD 14
Laggy video recording in low light
"sin" does not work in calculator in Spanish
Laggy playback of some video in .mkv container (same video works in the .mp4 container) (Recommendation: Dice Player from market. Does its own mkv extraction and has hw decoding support)
New Feature: Gamma tuning (equivalent to Voodoo Color's "v1 gamma hack")
BUILD 13
720p Video Recording laggy
No camera zoom
Timelapse video recording crashes
TV Out broken on sleep
TV Out black video
Broken encryption (regression in BUILD 11) (WARNING: users with already encrypted phone will have their data cleared (for real this time))
BUILD 12
Compass, accelerometer broken in certain apps
Random force closes (hopefully)
Missing camera touch to focus (thanks to havlenapetr)
GPS does not work (regression in BUILD 11)
Off-charging does not show progress
/datadata cache not cleared when space is low
Slow mass storage transfer speed
Automatic brightness not working
GApps v7.1
Network location broken
GApps v7
Market purchase broken
BUILD 11
Encryption not working without a data wipe (WARNING: users with already encrypted phone will have their data cleared)
Cannot authenticate new apps for root
Data sometimes get disabled on boot
GApps v6 / Face Unlock v6
Updated: based on IML74K
Face Unlock not working on BUILD 10+
BUILD 10
No hardware composition (but hardware acceleration works)
Video recording does not work.
Video playback is not hardware-accelerated.
The front camera produces distorted preview.
Photo taking does not work with the front camera.
Some camera options FC. (The camera is a temporary hack, when the Nexus S ICS source is released, there will be a proper fix.)
Movie Studio does not work.
WiFi automatically turns on after quitting airplane mode if WiFi was used during airplane mode.
Data Roaming is enabled by default
Can select widget on launcher without being on the widget screen *
GApps v5.3
Updated: Market apk
Removed: unneeded GoogleLatinIME
BUILD 9
WPA Wifi Tethering broken (regression in BUILD 8)
Audio recording by android app crashes (phone calls still work) (regression in BUILD 8)
Phone crashes in landscape with T9 enabled
Reboot to recovery by default even though recovery not selected.
Slow T9 speed
CPU rarely scaling up to 1000 MHz
GMail sometimes fills up /datadata with attachments
BUILD 8
USB Tethering on Windows requires the user go to to driver update and manually select the RNDIS driver.
Sketchy wifi tether (breaks if data connection comes up while tether is active) (it will still error, but you can now re-enable it)
Mounting external SD via USB broke in BUILD 7
Cannot accept many file types via bluetooth
Data activity icon sometimes gets stuck even data is off.
New feature: T9 Dialing by devatwork (Enable in Dialer Setting)
BUILD 7
Cannot encrypt phone after restoring data.
Wi-Fi problems for Iran users
Market download temporarily goes to /datadata
Support for TV Out (in Galaxy S Setting application)
Screen appearing for a split second after screen off animation
BUILD 6
Persistent "Removed SD card" message on external sd card removal.
Missing library for Android Open Accessory
Support for USB Mass Storage (see FAQ)
BUILD 5
VPN does not work
Regression in device encryption
BUILD 4
Large photos cannot be edited.
Missing Live Wallpapers
Bluetooth Reverse Tether does not work
Wi-Fi Direct not supported (it's supported in settings now, but apps are needed to use it as ICS does not come with any use-case for Wi-Fi direct)
Sometimes wifi strength won't show after boot if wifi is enabled. Toggle once to fix. (fixed, hopefully)
GApps v5.1
GApps: Missing TTS libs
GApps v5
GApps: Missing Picasa Sync
GApps: Unable to purchase apps
Build 3
Device encryption does not work. (Note: temporarily broken again in BUILD 4, works on BUILD 5)
User does not have write permission for external sd
A2DP bluetooth headsets do not work.
GApps v4
GApps: More missing libs for GoogleTTS
Build 2
Superuser.apk does not open.
Installer does not work on Samsung ROMs.
Factory reset (from settings menu) does not clear /datadata.
GApps v2
GApps: Missing voice chat, maps, text-to-speech libraries
GApps: Android Keyboard appears twice in Settings.
Frequently Asked Questions
My calendar sync isn't working!
Install the latest build and gapps and gapps fixer. If it still doesn't work, wipe your data.
App X isn't working!
Check the list at http://forum.xda-developers.com/show....php?t=1402210 (unaffiliated with teamhacksung) first and check if it works on other ICS phones. Most likely, it's the application's problem, not ours.
Can I mount the phone as mass storage via USB?
Starting from BUILD12, mass storage is the default configuration (might not apply to existing installations). The below command can be used to change into USB Mass Storage mode. USB Mass Storage mode is always used in recovery.
Code:
setprop persist.sys.usb.config mass_storage,adb
If you want to switch to MTP mode use
Code:
setprop persist.sys.usb.config mtp,adb
Please reboot after executing the command.
I can't adb into the phone!
Please install Nexus S drivers from Google. (Or Galaxy Nexus's driver in MTP mode)
Can I flash other modems?
You may flash modem packages designed for CM7.
How do I take a screenshot?
The screenshot taking function is built into ICS. Hold volume down + power.
Can I use CM7 kernels?
No, the kernel has modifications to make graphics, camera, data counter and data limit work.
Can I disable LED Notification?
Yes. Untick Settings -> Display -> Pulse notification light.
Maps keeps asking me to sign in even though I'm signed in!
Ignore the sign in dialog and pull down the notification menu. Answer the request for permission. Do this a few times and Maps will work.
How do I enter Galaxy S Settings (Device Settings)?
Type "am start com.cyanogenmod.AriesParts/.AriesParts" from adb. Or starting from BUILD 7, it is available as an icon in your launcher.
Is there a Captivate version?
A captivate build from the same source (but with captivate config) is available here.
What's working? Why is there only a list of issues?
Everything else not listed are supposed to be working (aside from the usual CM7 bugs). If they're not listed, please post so that they can be added to the list of issues. A list of issues is far more useful from a development standpoint.
Why am I getting notified that my data partition is getting full when I have 1+ GB free?
Your /datadata partition, a smaller partition, is getting full.
I want to install gazillion apps on my phone and /datadata is too small
Run the following and datadata will no longer be used on next reboot. Your phone might become slower though.
Code:
touch /datadata/.nodatadata
IRC?
#cmsgs on freenode
My adb shell isn't root!
Run "adb root" to restart adb in root mode.
Why is "Android OS" battery usage so high?
It's just a reporting change in ICS. Android OS now includes battery usage from more components than in Gingerbread, the actual battery drain is the same.
What is "Random Offset" during installation?
It's just a harmless message given as a verbose logging due to the new ASLR security feature in ICS. It is not an error.
How do I get the latest version of Rom Manager without market?
If the bundled version doesn't work, update from http://download.clockworkmod.com/rec...RomManager.apk.
I would like feature X
This thread is not the place for it. Submit it to the CM bug tracker once an official RC is released.
Thanks
syndtr: Updated touch and graphics driver
onecosmic: Being the first to successfully build the AOSP tree
Kaik541: GApps from v3 onward
ancdix: For hosting on tux-head.net
nikademus (_renaud_): For hosting on faramir.eriador.org
SysTem-X: For hosting on ics.haxer.org
sixstringsg: For hosting on androtransfer.com
CyanogenMod team: Setting up the infrastructure and being a great help in the porting process.
sixstringsg, TkGlitch, and Skitz: Helping me get GPS going on ICS.
Team ICS Passion: This build uses a gpsd blob they found for their ROM from older versions of CM7.
and everyone else involved in this port or CM7 for SGS.
Reserved. *10 char*
thanks FaultException. was waiting on six to bring us Build 16, going to give it a try later when i get home, thank for this and the good work you are doing on cm7.
thanks will try tomorrow
Thank
Thanks FE and wish you all best.
Thanx man...will flash this.
What is the stock kernel the rom comes with???
krackerjac said:
What is the stock kernel the rom comes with???
Click to expand...
Click to collapse
It's the standard Aries CM kernel.
Thanks again FaultException for your time and effort which I know the Vib community here appreciates it 800% !
Fault Exception is there any way you could committ the yagf2 GPS fix in to this rom. It makes a huge difference in GPS lock speed over stock.
hurtz777 said:
Fault Exception is there any way you could committ the yagf2 GPS fix in to this from. It makes a huge difference in GPS lock speed over stock.
Click to expand...
Click to collapse
The what? You'll have to give me a link.
FaultException said:
The what? You'll have to give me a link.
Click to expand...
Click to collapse
I think this http://forum.xda-developers.com/showpost.php?p=19869399&postcount=1
Yeah that is the link to it. It makes a world of difference on GPS locks and accuracy.
the usual gps problem....
it works good first time...then no more and doesnot go in ds too...
damn vibrant first stock!
daffyno said:
the usual gps problem....
it works good first time...then no more and doesnot go in ds too...
damn vibrant first stock!
Click to expand...
Click to collapse
From what rom you came from.i came from cm7 and ended up in a bootloop..wander what im doing wrong.
Edit* if you end up in a bootloop all you have to do is pullthe battery.enter the clockworkmode useng three button combo.reinstall.done.
Sent from my SGH-T959 using XDA App
daffyno said:
the usual gps problem....
it works good first time...then no more and doesnot go in ds too...
damn vibrant first stock!
Click to expand...
Click to collapse
Can you try using yagf2 + http://forum.xda-developers.com/showpost.php?p=22119563&postcount=80 ?
nuwanmw1988 said:
From what rom you came from.i came from cm7 and ended up in a bootloop..wander what im doing wrong.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
another ics rom
chui101 said:
Can you try using yagf2 + http://forum.xda-developers.com/showpost.php?p=22119563&postcount=80 ?
Click to expand...
Click to collapse
the same...
hurtz777 said:
Yeah that is the link to it. It makes a world of difference on GPS locks and accuracy.
Click to expand...
Click to collapse
I'll look into it. If it does make that much of a difference, and I have permission from the authors, I'll throw it in CM9 and 7.
Dougfresh said:
Thanks again FaultException for your time and effort which I know the Vib community here appreciates it 800% !
Click to expand...
Click to collapse
+1 that's right
Sent from my SGH-T959 using xda premium
chui101 said:
Can you try using yagf2 + http://forum.xda-developers.com/showpost.php?p=22119563&postcount=80 ?
Click to expand...
Click to collapse
If u flash that file it works on this rom. I am using this rom and I flashed the GPS fix and I get a GPS lock.
Sent from my SGH-T959 using XDA App

[ROM-AOSP] OFFICIAL CM11.0 KFire HD 8.9 (KK 4.4.2) [05/20 AUDIO/CAMERA FIXES]

OFFICIAL CyanogenMod 11.0 for the Kindle Fire HD 8.9
*** USE AT YOUR OWN RISK! WHILE I TRY MY BEST TO PROVIDE WORKING KERNELS/ROMS, I AM NOT RESPONSIBLE IF THIS SOFTWARE OR ANYTHING I'VE WORKED ON SUDDENLY FRIES YOUR DEVICE. ***
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER AND TWRP 2.7.0.0 INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
NIGHTLY BUILDS SHOULD BEGIN IN THE NEXT FEW DAYS:
Official CM Downloads:
http://download.cyanogenmod.org/?device=jem
Download Google Apps for CM11:
[UPDATED: 01/05] http://wiki.cyanogenmod.org/w/Gapps
Unofficial builds can be found in the mirrors below (cm11 folder for those builds):
Mirror 1: Download (Goo.im)
Mirror 2: Download (Crackflasher)
PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) BEFORE UPGRADING TO ANDROID 4.4.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
CHANGES:
[04/14] Kernel cleanup including bugfix for app-asec related APP crashes
[04/14] Partition mount flag cleanup
[03/25] Bugfix for streaming video where stream dies every 4-5mins (specifically Google Play Movies)
[03/15] Testing 128mb of ZRAM use
[03/15] Added KSM and ZRAM to kernel
[03/15] MMC discard / trim fix
[01/17] Kernel updated to google/common 3.0.72
[01/17] "Manufacturer" and "Brand" props changed to: Android / Google for app compatibility
[11/25] First CM11.0 build
[11/15] SElinux now included in the kernel and set to permissive. I don't recommend turning it to enforcing as I'm still debugging the "deny" messages.
[08/12] All new "from source" sensor driver
[08/12] Temp. disable light sensor (due to recode of sensor driver)
[07/31] First CM10.2 build
FEATURES:
3.0.72 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
PowerVR Graphics Drivers: DDK [email protected] for Android (Jellybean compatible)
Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
Audio
Camera
Wifi
Bluetooth
Sensors
HWAcceleration
HD Codecs for YouTubeHD and Netflix
HDMI video out is now correct and work across several resolutions. YMMV
DEVS
BUILDING THIS ROM:
First, read through Google's Android website about "how to setup a build environment":
http://source.android.com/source/initializing.html
[ COMING SOON ]
IGNORE THE LINE BELOW THIS SAYING THIS ROM IS FOR THE KINDLE FIRE HD 7". IT'S NOT. IT'S FOR THE KINDLE FIRE HD 8.9".:
XDA:DevDB Information
OFFICIAL CM11.0 KFire HD 8.9 (KK 4.4.2), ROM for the Amazon 7" Kindle Fire HD
Contributors
Hashcode
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Stable
Stable Release Date: 2014-05-20
Created 2013-11-26
Last Updated 2014-05-27
Reserved
KNOWN ISSUES:
Bluetooth tether (to say a phone for internet) doesn't seem to be working correctly
Accelerometer can stop working occasionally. Needs debugging.
Ambient light sensor needs to be re-coded as an IIO driver
Headphones / BT audio route testing (plugging / unplugging can cause stuck audio)
Fix USB OTG support in the kernel
Better HDMI support for more resolutions
No Amazon Prime Video support
No Dolby audio support
"Cast Screen" does not function correctly under Settings -> Display
[FIXED-2014-05-20] Audio HAL cleanup and use system/media audio-route sources
[FIXED-2014-05-20] More camera tweaks
[FIXED-2014-05-13] Hardware Decoder/Encoder support update to KK-based sources
[FIXED-2014-05-13] Camera could use a small update for better handling
[FIXED-2014-05-02] Audio low latency issues when cover is closed or 2 apps play audio at once (stuttering)
[FIXED-2014-04-18] VPN has issues, needs debugging
[FIXED-2014-04-18] Some games like Plants Vs. Zombies 2 don't work right, researching
[FIXED-2014-04-15] Possible other game issues, but I need more examples of games that don't run
so are you gonna abandon the cm10.2 development?
i was trying to flash it a few days ago, but it didn't work...now of course this one would be nice, but it's still in an erly development i suppose^^
---------- Post added at 09:57 AM ---------- Previous post was at 09:57 AM ----------
so are you gonna abandon the cm10.2 development?
i was trying to flash it a few days ago, but it didn't work...now of course this one would be nice, but it's still in an erly development i suppose^^
Thank you !!!!!!!!!!
Thanks a lot...
No problems during installation.
Until now it works like a charm...
dirthy flash from cm10.2 without problems
cache+dalvik wiped...
Installed on my Jem LTE.
-install completed with no problems.
-Run very smooth.
-Icon drag bug come back
Thank Hashcode.
Waiting for Jem LTE version.
I don't know how you do it man, but you've always got something new and awesome every single day for me, whether it's my KFHD or my S4, so thanks for being awesome!
Downloading now.
Cannot get this to install. It just gets stuck at the blue kindle fire logo. ANY ROM I flash ends up this way.
Sent from my SCH-R530M using Tapatalk
legmando33 said:
Cannot get this to install. It just gets stuck at the blue kindle fire logo. ANY ROM I flash ends up this way.
Sent from my SCH-R530M using Tapatalk
Click to expand...
Click to collapse
Please make sure you're flashing this with the latest TWRP 2.6.3.1 and that you've done the required wipe + advanced -> format system.
Hashcode said:
Please make sure you're flashing this with the latest TWRP 2.6.3.1 and that you've done the required wipe + advanced -> format system.
Click to expand...
Click to collapse
Okay I'll try that. Thanks Hashcode.
Sent from my SCH-R530M using Tapatalk
I am unable to get the new Amazon AppStore to run on this rom. Immediately force-closes. The same problem happened when updated the Amazon appstore on the 11-15 CM10.2 build. There is a similar comment on that thread by another user but without reply.
I tried re-installing, clearing data, and even a full wipe and clean install but to no avail.
Any suggestions?
P.S. No post in this forum should go without thanking Hashcode for his time and efforts. Without him, this tablet isn't good for anyone between 5-60 years old.
mssaleh said:
I am unable to get the new Amazon AppStore to run on this rom. Immediately force-closes.
Click to expand...
Click to collapse
Juppp... same here installed the old Version of the store, everything is OK.
Wow thank you so much! I wish there was some way I could help but I only know the basics on programming but I am more than willing to help in any way. I really hope this improves the device with kitkats memory management
Having lots of problems
First I did a backup (TWRP 2.6.0.1 or something dont remember exactly but older version)
Then I updated TWRP to the newest one
After that I restarted recovery it seams to work fine (other then USB mount which would be very very much appricated if it worked) I wiped System and Seamed to Working like it should
Then I did factory reset and then advanced wipe System
after that I installed the 2 files for CM11 and Gapps
CM11 will look like its starting then go really fast and say success but really do pretty much nothing
the GAPPs will just fail
Now I cant restore the file from the older TWRP since its in a different folder and it fails when i use the file managment to move it to the correct folder..
I cant ADB push a rom file to try an older version of CM ADB sideload also fails Smaller files Like TWRP work but not Roms and this is plenty of open space that is not a problem
Right now I cant install anything but TWRP
Is anyone else having problems?
Thanks!
Just wanted to say Thanks Hashcode, really pleased and surprised to get KitKat for my Kindle, especially so early.
I did a clean install (wipe system, data and cache) with the newest TWRP and then enabled Art as the runtime environment and so far everything seems to be working ok. Installed rotate app to take care of the rotation bug and so far not found any other problems.
Thanks again
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
narse said:
Installed rotate app to take care of the rotation bug and so far not found any other problems.
Click to expand...
Click to collapse
Which one do you have installed? There are so many diiferent apps on playstore
Bastlwastl2010 said:
Which one do you have installed? There are so many diiferent apps on playstore
Click to expand...
Click to collapse
I use https://play.google.com/store/apps/details?id=nl.fameit.rotate. There is a 7 dart trial, but I use the paid for version. It has always worked well for me.
Sent from my Amazon Kindle Fire HD using XDA Premium 4 mobile app
Here's a test CM11 build which seems to fix the rotation/orientation issues - at least for me far as I can tell.
http://d-h.st/users/loosethisskin/?fld_id=28911#files or http://goo.im/devs/loosethisskin/jem/cm-11.0
@Hashcode ... the relevant commit is here: https://github.com/loosethisskin/an...mmit/f5c558fa4acee3b793be6e1de9949e9624014c55
It's a first version and will need to be modified if it's worth pursuing (e.g. make it property driven). The change should have a result similar what apps like Rotation Control do. I am forcing sensor (landscape) orienation for every landscape or reverse landscape request.
Let me know...
lizzord30 said:
Having lots of problems
First I did a backup (TWRP 2.6.0.1 or something dont remember exactly but older version)
Then I updated TWRP to the newest one
After that I restarted recovery it seams to work fine (other then USB mount which would be very very much appricated if it worked) I wiped System and Seamed to Working like it should
Then I did factory reset and then advanced wipe System
after that I installed the 2 files for CM11 and Gapps
CM11 will look like its starting then go really fast and say success but really do pretty much nothing
the GAPPs will just fail
Now I cant restore the file from the older TWRP since its in a different folder and it fails when i use the file managment to move it to the correct folder..
I cant ADB push a rom file to try an older version of CM ADB sideload also fails Smaller files Like TWRP work but not Roms and this is plenty of open space that is not a problem
Right now I cant install anything but TWRP
Is anyone else having problems?
Thanks!
Click to expand...
Click to collapse
I'm getting the same thing. Also did the same with updating recovery. Had 2.6.0.0 before updating. Now even with the recommended wipes it won't boot, just stuck on blue kindle fire logo. =(
Sent from my SCH-R530M using Tapatalk

[P905 LTE ONLY!][KERNEL][ODIN] STOCK RELOADED | su | busybox | init.d | permissive !

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.

[Q&A] [ROM][SlimKat][4.4.4] [unofficial]

Q&A for [ROM][SlimKat][4.4.4] [unofficial]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Anghirrim said:
Finally tried the cast fixed version and still have boot loop. So back to version 8.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I have the same problem with 8.4. With 8. everything works fine
IparryU said:
Cast version works perfectly fine.
Any chance you could include OmniSwitch in the next build @infrag? And possibally an option to use that as default recents? If not, no problemo!
Click to expand...
Click to collapse
Reposting here.
Proximity
Anyone else having problems with their proximity sensor?
updated modern, still getting invalid mmi
I was getting loads of chinese text through with the ussd/mmi system like trubul here, infact I made a thread about it. And also the loss of ussd code functionality with "invalid mmi code" error that he described.
Azlanhu says:
"had the same problem. Apparently, u need to flash the new modem/baseband I9305XXUFNI3 . "
Trubul seems satisfied with the solution, however when I flash the modem linked, whilst it sorts out the Chinese text, I still get invalid mmi codes all the time.
Am I missing something? Is a baseband something separate I need to flash, and if so where can I find it. Or something else?
Cheers.
I9305 (d2lte) SlimKat
I would like to know is it possible to install in Germany the SlimKat D2LTE version, or it may thereby lead to problems?
SlimKat vs SlimSaber
I know that Slim Saber Saber with the mod has been created, but I do not see quite the difference, so I would like to know your opinion of what you think are friendly for BATTERY?
Google Play No connection issue
My i9300 is stuck in a no connection issue in all the gapps, tried everything, clearing cache, data and even hard resetting
I have a rooted Slimkat 4.4.4 build8.0, stock Slimkat's kernel
Sorry for my bad english
SlimKat 4.4.4 8.6 Camera issue
Really nice rom - well done! The only issue I found so far on i9305 is that the camera does not work - it crashes when trying to access it. Even installed Camera MX but that freezes the phone completely on a black screen and a restart is required. I've noticed others were having the same issue. Are there any fixes for this?
Anghirrim said:
Hi, camera used to be fixed by just going back into CWM and wipping cache + dalvik cache. It used to work for me.
For the DPI, did you activate the root in the security option. I think you need it.
Sent from my GT-I9305 using XDA Free mobile app
Click to expand...
Click to collapse
I have the exact same issue with my camera. It was working before V8.6 but now I can't seem to fix it anymore.
No wiping of cache, even clean install (with format of /system) didn't do any good.
I also tried to extract various camera2.apk packages from older versions but I always run into the same problem
when starting up the stock camera app (other camera apps result in a freeze of the entire phone).
Unfortunately this time this does not solve my camera issue, and I assume it's the same for the others here. I even tried to replace the camera2.apk with various apks from older releases but it didn't help either. And if I try different camera software (apps) the systems just freezes completely. Any ideas?
TheDesperadoz said:
Unfortunately this time this does not solve my camera issue, and I assume it's the same for the others here. I even tried to replace the camera2.apk with various apks from older releases but it didn't help either. And if I try different camera software (apps) the systems just freezes completely. Any ideas?
Click to expand...
Click to collapse
Install CMFix from the Play Store, read the Important Instructions on the app's Play Store page & click the link to download Temasek's Restart Camera app. Do not open CMFix - first install Temasek's app & grant it SuperSU root permission. Then place a shortcut to Camera CMFix on your home screen instead of the link to the 'normal' camera. It's worked for me on all SlimKat & SlimSaber versions & with CM11.
woww thanks you
Is there a way to return to the AOSP recent apps window? The only thing I don't like on this rom is the recent apps window and how it looks and also the fact that there's a gesture instead of a clear recent apps button
Sent from my GT-I9305 using Tapatalk
nielowen said:
Install CMFix from the Play Store, read the Important Instructions on the app's Play Store page & click the link to download Temasek's Restart Camera app. Do not open CMFix - first install Temasek's app & grant it SuperSU root permission. Then place a shortcut to Camera CMFix on your home screen instead of the link to the 'normal' camera. It's worked for me on all SlimKat & SlimSaber versions & with CM11.
Click to expand...
Click to collapse
Thanks for the support. I already tried this twice though (and yes I followed the instructions to the letter) but I get the same annoying "unfortunately camera has stopped"
popping up when I then start the CMfix app.
I'm just not sure if this is a ROM issue or if this might be due to a conflict between my apps. Maybe I will try a clean wipe, of cache and system, then reboot into ROM
and see if the camera will work or not. This should tell me if it's ROM related or not.
I hate to restore everything afterwards though and to return to the issue for further investigation
I'd be glad to hear if someone else found an alternative solution!
Have you enabled root access? I would re-install the ROM having formatted system & cache & wiped dalvik and only then tried a complete wipe if that didn't work.
Finally got the camera working again
nielowen said:
Have you enabled root access? I would re-install the ROM having formatted system & cache & wiped dalvik and only then tried a complete wipe if that didn't work.
Click to expand...
Click to collapse
Yes I have, that was not the problem though I finally got it to work again, here's what I did (in case anyone runs into the same issue):
1.) Install CMFix from the Play Store + download & install Temasek Restart Camera (with root permission)
2.) Run camera CMFix --> still got the "can't connect to camera" error message
3.) Reboot to recovery, wiped dalvik, wipe cache partition & wipe data/factory reset
4.) Restored apps & system data via Titanium
5.) Run "Restart Camera" and CMFix again --> This time the camera did work again :good:
6.) Tried other camera apps --> camera is working just fine now --> uninstall Restart Camera & CmFix --> camera is still working
Also one could try installing a different GAPPS build - there is a stable one from mid September and various betas up to a day ago,
maybe that might be another cure (or cause) to fix the camera bug.
Slim install failed
hi people who can not install Slim, brings in TWRP 2.7 Failed with what have for a recovery flashed her. sorry for my english
https://drive.google.com/file/d/0B4k...ew?usp=sharing
TheDesperadoz said:
Yes I have, that was not the problem though I finally got it to work again, here's what I did (in case anyone runs into the same issue):
1.) Install CMFix from the Play Store + download & install Temasek Restart Camera (with root permission)
2.) Run camera CMFix --> still got the "can't connect to camera" error message
3.) Reboot to recovery, wiped dalvik, wipe cache partition & wipe data/factory reset
4.) Restored apps & system data via Titanium
5.) Run "Restart Camera" and CMFix again --> This time the camera did work again :good:
6.) Tried other camera apps --> camera is working just fine now --> uninstall Restart Camera & CmFix --> camera is still working
Click to expand...
Click to collapse
Hey! Tried this and the other mentioned stuff several times but still no success... has anyone heard from other ways to get the cam to work? or maybe an alteration of the quoted post?

Categories

Resources