Unofficial CyanogenMod 10.2 for the Kindle Fire HD 8.9 LTE
THIS THREAD IS SPECIFIC TO THE LTE VARIANT OF THE KINDLE FIRE HD 8.9". IF YOU HAVE A STANDARD 8.9" MODEL USE THIS THREAD:
http://forum.xda-developers.com/showthread.php?t=2388352
*** 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. ***
**** I DO NOT OWN THE LTE VARIANT OF THE KINDLE FIRE HD 8.9", SO THIS ROM WILL BE A WORK IN-PROGRESS. IF YOU'RE THE EASILY FRUSTRATED TYPE, YOU MAY WANT TO HOLD OFF. ****
BEFORE YOU BEGIN MAKE SURE YOU HAVE A 2ND-BOOTLOADER INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
LTE MODEL Download Information:
[LATEST][08/07 #3] BETA CM10.2 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jemlte/cm10.2/cm-10.2-20130807-UNOFFICIAL-jemlte.zip
md5sum: d499384a940dffb3ca7e6ac512fcf370
Older builds can be found in the same folder on goo.im:
http://goo.im/devs/Hashcode/jemlte/cm10.2/
Download Google Apps:
http://goo.im/devs/Hashcode/gapps
(For Android 4.3)
PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.
CHANGES:
[08/04] First CM10.2 build for Jem LTE
[07/31] Added RIL setup for LTE
[07/31] First CM10.2 build for Jem
FEATURES:
3.0.50 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 ]
SCREEN SHOTS:
FOR BUGS / TROUBLESHOOTING:
I need the output from:
adb logcat -b radio > logcat-radio.txt
SAME BUGS AS THE STANDARD VERSION OF KINDLE FIRE HD 8.9"
CURRENT KNOWN ISSUES:
Benchmarks are quite LOW at the moment due to lack of bionic optimizations for OMAP in 4.3. This will probably get worked out over time. DONT COMPLAIN ABOUT BENCHMARKS. YOU HAVE BEEN WARNED.
When long pressing icons in landscape mode to move them, etc the screen will flip upside down for a moment and right itself. This causes the action to be aborted.
Rotation selection in games is hit and miss. Some work perfectly and some like to flip the device upside down. Still debugging what is causing this.
AUDIO: Any decoder which uses Dolby surround current has a lower volume than the rest of the system (Netflix, Google Movies, etc). It's a WIP.
3D Performance: Is only OK. Needs some troubleshooting and perhaps kernel cleanup. Work-In-Progress.
Sensors: Testing various sensors, gyro seems 90 degrees off, etc.
I don't have an LTE version so this is not enabled in current builds.
Great news! Thank you very much.
logcat-radio as you request.
logcat-radio in attachment.
I get it on stock rom.
Thank you.
No LTE setting
Intalled.
But i can't find LTE setting.
GPS not work too.
Bluetooth can't turn on.
tethien said:
Intalled.
But i can't find LTE setting.
Click to expand...
Click to collapse
Same here. Don't have mobile data options under "setting-data usage".
But still many thanks to hashcode! ...and willing to continue testing.
logcat-radio get on this rom
in attachment
I found some issues with my first build and I'll be putting up #2 here in a bit once I iron out some other changes I currently have going.
Hashcode said:
I found some issues with my first build and I'll be putting up #2 here in a bit once I iron out some other changes I currently have going.
Click to expand...
Click to collapse
Sweet!
Updated OP w/ test #2:
LTE MODEL Download Information:
[LATEST][08/06] BETA CM10.2 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jemlte/cm10.2/cm-10.2-20130806-UNOFFICIAL-jemlte.zip
md5sum: d2d0be88c07ca9623d3b87e03797a33e
This ROM has a few notable changes:
- It's using the new sensor hardware layer (from source!) which is almost -- but not quite done. So for now, the ambient light sensor doesn't work. All other sensors work. Tho, the gyro still has mixed X and Y axis.
- I did some comparisons to the regular JEM build and noted that rild, the gsm permissions, MMS.apk and Phone.apk are in this build. Obviously, once things start working, I'll want to remove some of that as it doesn't apply but for now thats a good sign.
I need a new logcat -b radio of this build.
Tks god now I can post -_-
Thank you @Hashcode for trying to build rom for us
I follow topic every hour and I have some infomation for you:
-Your first LTE build has nothing about mobile network.
-Your second one has a setting named: emegency alert and setting about which situation and action.
-The Messenger app can't send a messenger to another number.
-No sign of mobile signal, nothing, no data roaming on off, no apn etc ...
-Call at lockscreen doesn't work.
I've tried many rom, but the rom that LTE network worked is stock 8.1.4 that has APN adding option (I'm living in Vietnam so I used local network operator here). The Stari-rom doesn't has APN option but still has network system and can recieve sms.
/// I've just tried to install your 8.4.3 stock rom zip, ithe 3G network worked
Thanks for the input. Did you by chance get the output from "adb logcat -b radio > logcat-radio.txt"?
Sent from my XT926 using Tapatalk 2
installed 0806 rom. still no mobile data options under "Settings - Data usage"
however, under "Settings - more...", there is line saying "cell Broadcasts".
i'm away from home on a business trip. will do the logcat once getting back to the bay area.
thanks a lot, hashcode!
Logcat radio from 0806 rom
As you request.
Thank.
Updated the OP with a new TEST build:
LTE MODEL Download Information:
[LATEST][08/07 #3] BETA CM10.2 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jemlte/cm10.2/cm-10.2-20130807-UNOFFICIAL-jemlte.zip
md5sum: d499384a940dffb3ca7e6ac512fcf370
CHANGES:
Fixed the overlay so that mobile data is supported by the OS
Using CM apns.conf file now (it includes the 2x ATT entries from the stock file)
Changed from a "phone" style build to a tablet + mobile data set of packages (No Dialer / MMS)
Need a new: adb logcat -b radio > logcat-radio.txt
Thanks!
The new rom has a Mobile networks settings, but no signal. Maybe this park is for the smartphone hardware and not for tablets. Cuz I see Network Operater doesn't show up at status bar, just a triangle with nothing. And when I was in the network operations setting, it scan for network, manage mobile plan doesn't recognize sim (the stock 8.4.3 does). Or maybe it just setup for AT&T network?
I don't know why I can't get the log file, my computer does recognize as ADB, but when I tried to log, it said waiting for device.
Your rom is improved every update ^^
thanks for your work, bro.
logcat radio from 0807 ROM
waiting your new rom!
gamer941 said:
The new rom has a Mobile networks settings, but no signal. Maybe this park is for the smartphone hardware and not for tablets. Cuz I see Network Operater doesn't show up at status bar, just a triangle with nothing. And when I was in the network operations setting, it scan for network, manage mobile plan doesn't recognize sim (the stock 8.4.3 does). Or maybe it just setup for AT&T network?
I don't know why I can't get the log file, my computer does recognize as ADB, but when I tried to log, it said waiting for device.
Your rom is improved every update ^^
thanks for your work, bro.
Click to expand...
Click to collapse
You must enable "USB debugging" under "Developer option" before run adb command.
Go to Setting/About tablet the press 7 time to "Build number" line. "Developer option" will appear on left menu.
tethien said:
You must enable "USB debugging" under "Developer option" before run adb command.
Go to Setting/About tablet the press 7 time to "Build number" line. "Developer option" will appear on left menu.
Click to expand...
Click to collapse
Oh that's it
I just a newbie started to use android :victory:
tethien said:
waiting your new rom!
Click to expand...
Click to collapse
I'm seeing lines like this in your radio logcat:
W/use-Rlog/RLOG-RIL_VDR( 134): ril_oem.c:194 Failed to set mtu::rc=1,0, cmd=[echo 1400 > /sys/class/net/rmnet0/mtu]
E/use-Rlog/RLOG-RIL_ODL( 134): pktio.c:271 cant open device: device=/dev/ttyUSB0, errno=13
Can you check the following in adb and post it for me?
ls -l /sys/class/net/
ls -l /dev/ttyUSB*
Thanks
Related
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
Unofficial CyanogenMod 10.1 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 INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
AUDIO: DO NOT ENABLE "LOCK SCREEN AUDIO" OR "TOUCH SOUNDS" IN SOUNDS MENU. THIS *CAN* BREAK AUDIO.
CyanogenMod Changelog (DO NOT DOWNLOAD ANY .ZIP FILES -- FOR OFFICIAL DEVICES ONLY)
http://changelog.bbqdroid.org/
Download Information:
[LATEST][08/12] BETA CM10.1 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130812-UNOFFICIAL-jem.zip
Mirror 2: d-h.st/xMG
md5sum: 6a717e9b085909e6407cab486f585b54
[07/26] BETA CM10.1 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130726-UNOFFICIAL-jem.zip
Mirror 2: d-h.st/4Uc
md5sum: 41d6331a9492ddc2dd576c6cad71c8f5
[07/17] ALPHA CM10.1 + 3.0.50+ KERNEL
Mirror 1: http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130717-UNOFFICIAL-jem.zip
Mirror 2: http://d-h.st/XxG
md5sum: 1a1204e8e74211213fd1414ebca80194
[07/13] ALPHA CM10.1 + 3.0.50+ KERNEL
http://goo.im/devs/Hashcode/jem/cm10.1/cm-10.1-20130713-UNOFFICIAL-jem.zip
md5sum: 5050e8c31851162a117d87d17a1b6806
Older builds can be found in the same folder on goo.im:
http://goo.im/devs/Hashcode/jem/cm10.1/
Download Google Apps:
Http://goo.im/gapps
(For Android 4.2.1/CM 10.1 use the top row gapps)
PLEASE BE SURE TO WIPE SYSTEM & DATA/CACHE (FACTORY RESET) WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "System" and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
Be aware that the "sdcard" space has changed slightly from ICS to JB4.2. You will find your stock amazon OS files in /data/media/ or "sdcard" on the Stock OS. But CM10.1 will create a sub directory "/data/media/0" and call that "sdcard". And in TWRP it will also use "data/media/0" as "sdcard". This has to do with multi-user settings. So when placing files on the "sdcard" be sure to check both locations before wondering why that file is missing.
CHANGES:
[08/12] Includes a Trebuchet patch to fix the screen flip-flop when trying to drag an icon in landscape (by XDA user Wickets^)
[08/12] Headphone volume raised (set to 114)
[07/26] Fixed occasional drawables issue with background / etc reverting to HDPI graphics
[07/26] More Dalvik VM changes
[07/17] Dolby: [WIP] Initial work for Dolby support in CM10.1 -- Still troubleshooting audio effect pre-gain handling
[07/17] Audio: Fixed MIC initialization -- works perfectly now, everytime.
[07/17] Camera: cleaned up DCC file handling for a bit more "Amazon"-like performance.
[07/13] USB Vendor ID / Product ID's have been reset to match the Amazon OS / TWRP values. Should help keep Windows drivers from going bonkers.
[07/13] Some Audio issues have been resolved. It shouldn't stop when swapping apps, etc. Still low volume currently where Dolby decoder is used.
[07/13] CM refreshed which includes several well-known security exploit patches
[07/13] PVR/SGX driver updated to 1.[email protected] fixing several games and Google Earth
[07/13] Enabled "dirty region" rendering which helps 2d rendering quite a bit.
[07/13] Fixed a Bluetooth issue: stuck in TRANSITION mode till it's enabled/disabled after a reboot. This was causing extra battery drain.
[07/13] Some tweaks to Android vm allocations. Still needs work, but less apps are being killed off on the boot.
[06/04] CM refresh for changes (no device updates)
[05/14] New android OS audio driver. MIC works but may need to be stopped / re-started once (WIP)
[05/11] Camera should be working again
[05/08] Fixed orientation for HDMI output (requires a /data wipe) -- sound is W.I.P.
[05/08] Fixed default landscape orientation (was backwards)
[05/08] Fixed power HAL to retain current max CPU freq (original code by twa_priv, patched by Hashcode)
[05/07] Raised headphone volume by 10%
[04/20] [Thanks to Javabugs] Bluetooth firmware is now renamed correctly so that it loads and should work
[04/05] Basic audio function is now working. This means volume adjustable speaker output and headset output. NO input works yet -- still WIP.
[04/01] Basic camera function now working, tho after video recording is stopped, camera will FC during thumbnail creation. Video is recorded successfully tho. Panorama crashed out entirely still WIP.
[02/25] Updates to CM10.1 (4.2.2_r1)
[02/01] First release
FEATURES:
3.0.50 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
Then you can setup the Kindle Fire Android projects by doing the following:
(This manifest allows for building Kindle Fire 1st and 2nd gen as well)
Code:
mkdir android
cd android
# Use main repo for CyanogenMod 10.1
repo init -u https://github.com/CyanogenMod/android -b cm-10.1
# Then add the local_manifest.xml for the Kindle Fire
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/KFire-Android/android_local_manifest/cm-10.1/local_manifest.xml
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch jem
CURRENT KNOWN ISSUES:
When long pressing icons in landscape mode to move them, etc the screen will flip upside down for a moment and right itself. This causes the action to be aborted.
Rotation selection in games is hit and miss. Some work perfectly and some like to flip the device upside down. Still debugging what is causing this.
AUDIO: Any decoder which uses Dolby surround current has a lower volume than the rest of the system (Netflix, Google Movies, etc). It's a WIP.
AUDIO: Headset volume still may be lowish. Testing better ways of increasing volume w/o distortion. It's a WIP.
3D Performance: Is only OK. Needs some troubleshooting and perhaps kernel cleanup. Work-In-Progress.
Sensors: Testing various sensors, gyro seems 90 degrees off, etc.
I don't have an LTE version so this is not enabled in current builds.
CURRENT KNOWN APP/GAME ISSUES:
Need For Speed Most Wanted: Crash
EZPDFReader: PDF close = Crash
Hey,
HashCode this is very great job!
Thx
Awesome work, Hash and Verygreen (and whomever else is involved). Much appreciated
slacka-vt said:
Awesome work, Hash and Verygreen (and whomever else is involved). Much appreciated
There's CM10 Development for the KFHD 7" here:
From past experiences, the Dev's do not like having requests for a different device in their threads (or any requests for that matter ). Just sayin' . . .
Click to expand...
Click to collapse
Yes i know, and i allready know that HashCode have not time to do something for the 7" and i have updated my post so you can also do it
Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
Hashcode said:
Unofficial CyanogenMod 10.1 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 INSTALLED CORRECTLY AND CAN SEE THE BLUE LOGO DURING BOOTUP:
http://forum.xda-developers.com/showthread.php?t=2128175
Download Information:
[02/01] ALPHA CM10.1 + 3.0.50+ KERNEL
Download the ROM
md5sum: 36a6ec8df79b6dedbe56692ee2f07391
Download Google Apps:
Http://goo.im/gapps
(For Android 4.2.1/CM 10.1 use the top row gapps)
Older builds are found here (under my "Jem" folder on goo.im):
http://goo.im/devs/Hashcode/jem/cm10.1/
PLEASE BE SURE TO WIPE DATA/CACHE WHEN COMING FROM AMAZON STOCK SOFTWARE.
(It's the "Wipe" button and then "Factory Reset" button in TWRP -- this does NOT clear your sdcard space)
CHANGES:
[02/01] First release
CURRENT KNOWN ISSUES:
AUDIO DOES NOT WORK. I'm still troubleshooting and working on a custom audio HAL (if needed)
I need to tweak the build.prop settings so that more apps are compatible.
Camera crashes at the moment
Bluetooth function turns on, but is largely untested.
Haven't touched HDMI yet
I don't have an LTE version so this is untested. Tho much of the RIL files are in place as well as APNs.
FEATURES:
[02/01] 3.0.50 kernel (up from a stock 3.0.21 kernel). This includes updates from Texas Instruments, Google and Kernel.org.
[02/01] PowerVR Graphics Drivers: DDK [email protected] for Android (Jellybean compatible)
[02/01] Updated bltsville libs to 2.2.2.0 (this is partial screen update code which enables smoother / faster screen draws)
[02/01] Wifi
[02/01] Bluetooth pairing (no audio)
[02/01] Sensors
[02/01] HWAcceleration
[02/01] HD Codecs for YouTubeHD and Netflix
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
Then you can setup the Kindle Fire Android projects by doing the following:
(This manifest allows for building Kindle Fire 1st and 2nd gen as well)
Code:
mkdir android
cd android
# Use main repo for CyanogenMod 10.1
repo init -u https://github.com/CyanogenMod/android -b cm-10.1
# Then add the local_manifest.xml for the Kindle Fire
curl -L -o .repo/local_manifest.xml -O -L https://raw.github.com/KFire-Android/android_local_manifest/cm-10.1/local_manifest.xml
repo sync
vendor/cm/get-prebuilts
. build/envsetup.sh && brunch jem
Click to expand...
Click to collapse
How we can port this rom to the kindle fire hd 7". I love your work, you are a great developer
Sent From My Super Modded KFHD
Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
Thanks for the hard work, downloading now!
Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
ChrisFa5 said:
Thanks for the hard work, downloading now!
Click to expand...
Click to collapse
Great, let me now how both the bootloader (from the other thread) and ROM installation goes.
Sent from my DROID RAZR HD using Tapatalk 2
Thank you!
Now to get a fastboot cable.
If anyone installed it please give us your impressions.
kls2k said:
Thank you!
Now to get a fastboot cable.
If anyone installed it please give us your impressions.
Click to expand...
Click to collapse
You can definitely do the install w/o a fastboot cable, but you do need to have a working fastboot driver on your machine. The KFHD's stock bootloader will check for fastboot commands for a short period of time during the boot.
There are other methods as well to get the partitions setup for this, however, in the case of disaster having a working fastboot setup will be required to restore.
Hashcode said:
You can definitely do the install w/o a fastboot cable, but you do need to have a working fastboot driver on your machine. The KFHD's stock bootloader will check for fastboot commands for a short period of time during the boot.
There are other methods as well to get the partitions setup for this, however, in the case of disaster having a working fastboot setup will be required to restore.
Click to expand...
Click to collapse
Hashcode,
Does a factory/fastboot cable work on the 8.9? Some say to buy it, and others say that it only works for the Kindle fire 2 and 7" and that there is no need for it. If it is needed, is there a specific cable that you recommend? Thanks
vaggolena said:
Hashcode,
Does a factory/fastboot cable work on the 8.9? Some say to buy it, and others say that it only works for the Kindle fire 2 and 7" and that there is no need for it. If it is needed, is there a specific cable that you recommend? Thanks
Click to expand...
Click to collapse
I do all my work without a fastboot cable but I have my fastboot driver configured correctly so that the KFHD8 is recognized as a fastboot device during the bootup.
So, while I have tested fastboot on almost every other device that I own, I've never needed to use it on the KFHD8.
EDIT: I just did a quick functional test and my Motorola OEM factory cable did *NOT* place me in fastboot mode. So I think getting a fastboot cable may be a waste of time for the HD 8.9. Rather that users download the Android SDK and make sure it's setup correctly for fastboot. Updating my OP's.
Hashcode said:
I do all my work without a fastboot cable but I have my fastboot driver configured correctly so that the KFHD8 is recognized as a fastboot device during the bootup.
So, while I have tested fastboot on almost every other device that I own, I've never needed to use it on the KFHD8.
EDIT: I just did a quick functional test and my Motorola OEM factory cable did *NOT* place me in fastboot mode. So I think getting a fastboot cable may be a waste of time for the HD 8.9. Rather that users download the Android SDK and make sure it's setup correctly for fastboot. Updating my OP's.
Click to expand...
Click to collapse
Thank you!!
Hashcode, I'm getting a black screen after installing the rom + gapps. Any help?
same here... wiped, factory reset, then installed cm10.1, then wiped and factory reset, then gapps. After blue Kindle screen just a black screen, nothing happens. installed again, cm10.1, then gapps, no wipe/reset. black screen. Got an Fire 8.9 32GB.
Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
are both of you using 32gb devices?
has anyone had a successfully installed this?
Sent from my DROID RAZR HD using Tapatalk 2
Just tried your build on my 16GB wifi model but got a black screen on boot (right after the blue KF logo). Happens no matter gapps installed and wiped or not.
I have a recently synced copy of your git repo and I could build myself and run the rom properly though.
Re: [ROM-AOSP] Unofficial CM10.1 (JB 4.2.1) [02/01 ALPHA]
siruba said:
Just tried your build on my 16GB wifi model but got a black screen on boot (right after the blue KF logo). Happens no matter gapps installed and wiped or not.
I have a recently synced copy of your git repo and I could build myself and run the rom properly though.
Click to expand...
Click to collapse
Can you get a copy of /proc/last_kmsg from the black screen boot and send it to my email? Dont pastebin as there is serial #, etc information that shouldnt be shared. hashcode0f at gmail.com
I will also wipe and flash this build again. could have been a bad build somehow.
Sent from my DROID RAZR HD using Tapatalk 2
I am afraid I couldn't. After the black screen I had to hold the power button to forcefully turn the tablet off and on again - it seemed that the kmsg didn't persist through that to recovery.
Hashcode
first of all, Thank you very much for developing this roms. I bought KD HD 8.9 16Gb when you were developing cm10.1 :laugh:
I read your post (bootloader and this rom) and follow steps. and succeed to enter twrp recovery. (+ blue amazon logo)
but after i installed this rom and gapps, logo appeared and black screen ...
I can enter twrp recover (by power + volume button) but i can't connect kindle 8.9 to pc (windows7 can't recognize KD driver )
so I can't move the file or enter the fastboot .. ( I ordered a factory cable.)
If you know to connect kindle to pc at black screen or at the twrp recovery mode ( I tried to mount use mode of twrp recovery but it was no useful)
tell me something please.
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...
LineageOS 13.0 (Marshmallow) {un,}official builds for the Droid 4
LineageOS is a free, community built, aftermarket firmware distribution of Android 6.0 (Marshmallow), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* We are not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at any of us for messing up your device, we will laugh at you.
* Collectively, and at the same time.
*/
LineageOS is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. LineageOS does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for LineageOS is available in the LineageOS Github repo. And if you would like to contribute to LineageOS, please visit our Gerrit Code Review.
Use these builds on your own risk!
Builds:
Current official builds:
https://download.lineageos.org/maserati (Droid 4)
(When migrating from CM (official and unofficial) or Lineage unofficial, flash this first (manually mount /data in TWRP before flashing and unmount it afterwards) and then directly flash the new image without rebooting)
Su addon for official builds: http://droid.cs.fau.de/lineage-13.0/addonsu/ (The official addon doesn't currently install on Omap4)
Current unofficial manual builds:
https://droid.cs.fau.de/lineage-13.0/
Old official CM nightly builds and snapshots:
https://droid.cs.fau.de/Official_CM_Builds/maserati/ (Droid 4)
Old manual builds:
https://droid.cs.fau.de/cm-13.0/test/
Changes (only device/family specific, CM base is always synced before build and contains more changes):
2017-03-25:
Sync with LineageOS (March security level)
2017-03-02:
Sync with LineageOS
2017-02-19:
Fix 10 kernel security bugs
Add SGX Omap4-changes
Sync with LineageOS
2017-02-10:
Sync with LineageOS (January security patchlevel)
2017-02-01:
Sync with LineageOS
2017-01-11:
Sync with LineageOS
Rebrand to lineage
2016-01-21:
Official CM13 nightlies: http://review.cyanogenmod.org/#/c/129192/
2016-01-16:
Added SELinux rules to allow fsck on stock-partitions and fixboot to unmount safestrap-partition
Graphics glitches fixed
zRAM uses 2 compression streams now
2016-01-14:
Implemented LiveDisplay/Color Calibration
2016-01-13:
More fixes for switching CDMA devices to GSM
T-Mobile CZ APN corrected
2016-01-11:
Preferred network type is now set earlier
Audio-routing through dock-audio (desk/car) added
Mouse-pointer (USB/Lapdock) fixed
2016-01-08:
Camera no longer crops pictures in portrait mode
USB storage integration added
Initial root-mode setting fixed
Migrated from busybox to toybox, busybox is gone
Fixed duration of boostpulse in power HAL
2016-01-06:
VZW data fixed
Reboot to recovery fixed
Wifi configuration updated
Widevine blobs updated (from sprout)
2016-01-04:
Adoptable storage fixed
Many kernel patches to filesystem-, block- and mmc-layers
2015-12-25:
Fixed internal storage for real. You need to manually remove /data/system/storage.xml and reboot when upgrading from previous builds. After that the internal storage will be the primary sd.
2015-12-24:
Fixed crashes of com.android.phone on GSM/UMTS (XT894/XT912)
Configure internal storage like expected in M (can't be adopted, would kill safestrap)
Fixed GPS initialization failing most of the time
Run wifi calibration at an earlier stage
Workaround for VZW data: toggle airplane mode after boot once
Something which needed ffmpeg and imagemagick
2015-12-18:
Switching of preferred network fixed
SELinux rules updated
SELinux is now enforcing
2015-12-14:
Audio-routing fixed
2015-12-11:
Capacitive buttons on {umts_,}spyder are no longer recognized as an external stylus, but as buttons
SELinux policies updated
Update widevine from mako
Added (very slow) emulation of idiv-operations not supported by Omap4 but required by newer blobs (gapps swype, widevine)
2015-12-07:
First build for most devices
What's working:
Phone (tested on Verizon and on GSM/UMTS in Europe)
Mobile data
WiFi
GPS
Camera
HDMI
Playback of DRM-protected content (using Widevine from sprout)
Reboot to recovery
What's not working:
Probably most everything else, including, but not limited to:
Data encryption (due to safestrap)
Gapps:
OpenGApps
If you install Gapps after the ROM has been booted for the first time you either need to wipe data or manually delete /data/system/users/0/runtime-permissions.xml and reboot. Without this Gapps will crash constantly. This is due to the new permissions-system in M.
Installation:
You need a recovery supporting SELinux
A version of Safestrap (3.75) which supports SELinux can be found here: https://github.com/stargo/android_packages_apps_Safestrap/releases/tag/v3.75
Please read the instructions on how to install this version and follow the order of the steps in it.
GSM users:
These versions (both unofficial and official) automatically switch to GSM/UMTS without installing additional patches.
Source / Repositories:
maserati device-support: https://github.com/LineageOS/android_device_motorola_maserati/tree/cm-13.0
omap4-common device-support: https://github.com/LineageOS/android_device_motorola_omap4-common/tree/cm-13.0
omap4-common kernel: https://github.com/LineageOS/android_kernel_motorola_omap4-common/tree/cm-13.0
local manifest to build cm-13 for the Motorola Omap4 devices: http://droid.cs.fau.de/lineage-13.0/local_manifest.xml
XDA:DevDB Information
LineageOS 13.0 on Motorola Droid4, ROM for the Motorola Droid 4
Contributors
stargo, Hashcode, Dhacker29
Source Code: https://github.com/LineageOS
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Nightly
Beta Release Date: 2017-03-25
Created 2015-12-14
Last Updated 2017-04-05
Good job
Thanks again!
Excited.
Installed 151214 this morning over the top of 151210.
The "low in call volume " issue appears to be fixed, as per the notes above; I've had a few phone calls this morning with only one issue:
I was in my car, listening to music from my phone via the 3.5mm socket, when I had a phone call come in. While the phone paused the song during the phone call, instead of hearing the call through my car's audio it was output via the phone's speaker. The music picked up from where it had left off, [edit: through the car audio system,] after the call ended. @stargo, is that related to the issue you've fixed? Or will that be something silly at my end?
hahahaha thanks stargooo one step more for our droid 4!
Hi,
Shobai said:
Installed 151214 this morning over the top of 151210.
I was in my car, listening to music from my phone via the 3.5mm socket, when I had a phone call come in. While the phone paused the song during the phone call, instead of hearing the call through my car's audio it was output via the phone's speaker. The music picked up from where it had left off, [edit: through the car audio system,] after the call ended. @stargo, is that related to the issue you've fixed? Or will that be something silly at my end?
Click to expand...
Click to collapse
All low-level audio-routing problems should be fixed, this sounds like a problem with the IncallUI (it probably did not specify that the audio should be routed over the headphone out). Haven't looked there yet...
Cheers,
Michael
Thanks Michael, much obliged!
Apologies for the double post! @stargo, I think this may have been mentioned in the CM12 thread - I've got "Playback control" turned on under Buttons, but a long press of the volume keys doesn't have any effect on playback. The volume keys work properly for volume, though.
Thanks again!
Tested 2015-12-11, looks awesome! However, I couldn't find a way to turn off vibration upon touching buttons (capacitative ones under screen), spent over 10 mins in settings, searched there for "vibr" and checked all results – nothing... Any clue?
LuH said:
Tested 2015-12-11, looks awesome! However, I couldn't find a way to turn off vibration upon touching buttons (capacitative ones under screen), spent over 10 mins in settings, searched there for "vibr" and checked all results – nothing... Any clue?
Click to expand...
Click to collapse
Flash the build from the 14th.
Whoa nice, you got it running. Not that there was ever really any doubt
I don't have time at the moment to flash it myself, but to those who've flashed it, I pose the questions that are always inevitably posed:
How's it running, about the same as Lollipop? Has the Doze mode done anything for battery life on our hardware?
Septfox said:
Whoa nice, you got it running. Not that there was ever really any doubt
I don't have time at the moment to flash it myself, but to those who've flashed it, I pose the questions that are always inevitably posed:
How's it running, about the same as Lollipop? Has the Doze mode done anything for battery life on our hardware?
Click to expand...
Click to collapse
Far better performance than LP. Also, with doze, my phone can last up to four and a half days in standby. I'm running the December 14th build on my RAZR as my DD. Performance is incredible!
So has the build from the 14th fixed the DATA issue?
By no LTE/CDMA support right now, does that mean I wouldn't be able to receive emails and online push notifications unless I am on WiFi or they are Text/SMS based?
hi, can i have noob question? is there some tutorial how to make own build (i have tried to google what to do in which order but i didnt have much luck - create folders, get local manifest, init repo but when and how get omap4 common files required for build...)?
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
Narevek said:
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
Click to expand...
Click to collapse
So by finding this out, it would seem that the Data connection for any provider is not functioning due to a permissions issue in which the OS cannot write the given APNs from the "search" function to the file which stores the data... is that correct?
Hi,
Narevek said:
Managed to get a working data connection with Verizon after tweaking the apns-conf file. Changed the Verizon apn lines to match what we had in Lollipop. Both 4g and 3g seems to be working, and I was able to successfully send and receive MMS messages.
Click to expand...
Click to collapse
Great
I've attached the edited file in case any other Verizon users want to test and confirm. Just extract and copy it to /system/etc using your favorite root explorer, then go into APN settings and reset to default (I don't remember if I had to restart or toggle airplane mode on/off before it connected the first time, but I don't think I did).
Click to expand...
Click to collapse
Does it work after a reboot, too?
Or do you then need to toggle airplane mode again? It might be that toggling airplane mode is what actually causes the connection to be established. Judging from the radio logs I have seen, the RIL responds with an error after bootup and toggling airplane mode might fix it.
Btw, for the people on UMTS: I'm testing a fix for the crash of com.android.phone after boot.
EDIT: Confirmed by @joojoobee666: toggling airplane is enough to get data working
Cheers,
Michael
Bobcus Leper said:
Flash the build from the 14th.
Click to expand...
Click to collapse
Yup, switching Vibrate on touch off in sounds settings helps from this build on. Thanks, I have decided to make this my primary system, so far great impression
Bobcus Leper said:
Far better performance than LP. Also, with doze, my phone can last up to four and a half days in standby. I'm running the December 14th build on my RAZR as my DD. Performance is incredible!
Click to expand...
Click to collapse
I second that; especially Trebuchet, Settings, dialer, contacts and messaging are way more responsive. I clean installed system (1218 build; wipe /system, install just this and Open GApps Pico) with keeping data from 12.1, it went pretty smooth.
Also it's been laying in standby for about 12 hours now, Wi-Fi on, and it's still charged ~96%. Either it's a battery level reading bug and will soon drop fast, or huge improvement over L - usually I'd lose 10% - 20% at least.
GREAT JOB I was looking forward to CM 13 since June. However, right after flashing GAPPS the processes crash and can't make any progreses. Doesn't matter if I use Slot 1 or 2, already tried mount no-mount /system and /data.
Hi all:
Here is a LineageOS 17.1 ROM for Z5 compact (suzuran).
Download 2022-09-11
This is a 7z archive with the zip'ed rom and the md5 file in it. Please unpack this archive, copy the included two files somewhere to your device, reboot into TWRP and flash this zip file. Enable md5sum checking. The zip file itself is not signed, so you have to disable zip verification.
Kernel sources
Tree sources
Features:
OS Version: 10.0 (Q)
Kernel: Linux 3.10
Kernel 3.10.108
New: Android security patch level: 5 September 2022
Using sony blob's from stock version 32.4.A.1.54
Memory issues finally fixed!
Battery consumption significantly reduced! For further reduction, please follow these instructions.
Google Pay does not give an error when starting the app. This does not mean, that payment is working. I can't test it, because I don't use this feature at all. Please report if it's working or not.
Updated aptX encoder blobs.
P2P-Crashes fixed.
Important informations:
You should be familiar with general installation of custom ROMs.
Required for installation: TWRP 3.2.1 (pick the version from 2018-02-23!!!) There is a version 3.2.3 out there, but with that version I had problems to restore my backups. 3.2.1 is just working perfect for me!
OR use my self built TWRP-version 3.6.2!
This ROM needs a clean install, old /data may cause problems!
This ROM is NOT pre-rooted.
It is highly recommended that your device is running (or HAS RUN in the past!) the latest stock ROM from Sony (32.4.A.1.54) before flashing this ROM.
Otherwise the baseband files may not match.
Working:
Bluetooth
Camera; both built-in camera (Snap) and 3-rd party camera apps.
Snap may be a little bit laggy, please use 3-rd party camera app instead; for example OpenCamera. If you're running into errors, please report.
Enforced SELinux support (see attached screenshot)
Fingerprint
FM-Radio
GApps (pick this version: ARM64, 10.0, pico [tested])
German app AusweisApp2 working (see this post)
GPS
Headset
LiveDisplay (see attached screenshots)
Location services
Notification LED
Offline charging
Phone calls (see attached screenshot)
SafetyNet test passed successfully
Signed build
SMS
Torch
WiFi
These things are NOT (or badly) working:
Camera focus at low distances.
Encryption
Payment
Streaming (mirroring)
VoLTE
Maybe some more things are not working.
If you have problems with GApps:
Sometimes the SetupWizard of GApps crashes on and on. Then you have to boot into TWRP, mount system, and go into terminal, where you have to delete SetupWizard (see screenshots):
Code:
cd /system/system/priv-app
rm -rf SetupWizard
Reboot.
Use this rom at your own risk! It comes without any warranty! I'm not responsible for any damage! If you don't agree with that, don't try to flash this rom in any way.
Benefits:
Added F-Droid and UnifiedNLP! If you don't want this, simply de-install it.
I've set maximum speaker volume to a higher value.
I've increased microphone gain.
I've changed the microfone gain to avoid echo in phone calls.
Changelog
Troubleshooting:
If you're running into an error, please search in this thread if this error is already posted, before you post it again!
If not, I need a LOG to see what went wrong. Without a LOG I can't help you!
A LOG can be fetched by connecting the device with an USB cable to your PC and then by typing these commands line by line:
Code:
adb root
adb shell logcat -b all -d > logcat
Send my this LOG file via PM.
If you think this could be a SELinux related issue, please try to set the device to permissive mode first.
If the issue is gone, I need the policy file too (plus LOG). Fetch it by typing this line in a terminal:
Code:
adb pull /sys/fs/selinux/policy
If you stuck in a bootloop you can fetch a LOG with this trick:
Press the power button and the volume up button together until the device shuts down.
HOLD the power button.
Release the volume up button and press the volume down button immediately after releasing the volmue up button.
The device should start into TWRP recovery.
Tap on "Advanced", then on "Terminal" and enter these commands line by line:
Code:
cd sys/fs/pstore
cp * /sdcard
Send me the copied file(s), if any, via PM.
Hi Bernie,
First things first : Thank you so much for your amazing work on this device.:highfive:
So hard to find a good, compact and up to date smartphone.
So i tried your Los17.1 and i just noticed another issue : ram usage.
Without nor the gapps neither other apps installed, the system is using 1.6go ram (even the keyboard can take time to appear once you launch an app)
On your Los14.1 (i tried with the last one you created, a few days ago) : it would be something like 0.8go ram (so everything run smoother) still without gapps and other apps / settings.
Maybe, now our days, 3go ram is mandatory for android + gapps + 3rd party ...
Ryu--X said:
So i tried your Los17.1 and i just noticed another issue : ram usage.
Without nor the gapps neither other apps installed, the system is using 1.6go ram (even the keyboard can take time to appear once you launch an app)
Click to expand...
Click to collapse
I know about that. I've tried with gapps and I can confirm that ram is running out of free space. Sometimes the system is not responding any more (screen is flickering and it seems that nothing happens) and I have to restart it (press power button quite a long time until power menu appears).
It is indeed far away from being a daily driver... :angel:
Another issue: It seems that location services (gps) are not working.
Does anybody confirm that?
Although Bernard warmed us that this ROM is not precisely ready yet, I tried to give it a go, Twice, already. At each time, some variations: with and without gapps (Pico and Nano), via the recommended TWRP and the 3.3.1 one. The result is always the same: after the language selection, my phone reboots on the 'Just a sec', endlessly. I have to restore a nandroid backup, on order to have a working phone again.
Sent from my Xperia Z5 Compact using XDA Labs
Berni-0815 said:
It is indeed far away from being a daily driver... :angel:
Another issue: It seems that location services (gps) are not working.
Does anybody confirm that?
Click to expand...
Click to collapse
I can confirm that unfortunately GPS isn't working.
By the way, i saw many other good roms on many devices ... that had an alpha rom far worse than this one
casouzaj said:
Although Bernard warmed us that this ROM is not precisely ready yet, I tried to give it a go, Twice, already. At each time, some variations: with and without gapps (Pico and Nano), via the recommended TWRP and the 3.3.1 one. The result is always the same: after the language selection, my phone reboots on the 'Just a sec', endlessly. I have to restore a nandroid backup, on order to have a working phone again.
Sent from my Xperia Z5 Compact using XDA Labs
Click to expand...
Click to collapse
i didn't have this behavior on my tests, but i usually let the system start and wait for few minutes before using it (especially on 1st boot).
Also, i always reboot once after the 1st boot.
Hope it will help
casouzaj said:
after the language selection, my phone reboots on the 'Just a sec', endlessly.
Click to expand...
Click to collapse
Clean install?
That should not happen...
Ryu--X said:
I can confirm that unfortunately GPS isn't working.
Click to expand...
Click to collapse
You have to enable google's location service in location settings. With that, maps is working with correct location; but I don't know if the location comes from gps, wlan or network. It's raining since many days and I don't want to stand outside in the rain and wait for gps connection... :angel:
I've tried to install f-droid and their location services; no better results...
By the way, i saw many other good roms on many devices ... that had an alpha rom far worse than this one
Click to expand...
Click to collapse
Yes, I know. The problems are always the closed-source binaries from qualcom and sony that are not properly working on LineageOS versions > 14.1
We're working on it but I'm not able to say if we can fix these issues.
BTW: Is anyone able to make an outgoing call successfully?
Berni-0815 said:
Clean install?
That should not happen...
Click to expand...
Click to collapse
Yup,, every single time!
Sent from my Xperia Z5 Compact using XDA Labs
As I said, that should not happen...
Berni-0815 said:
BTW: Is anyone able to make an outgoing call successfully?
Click to expand...
Click to collapse
i tried both calling and receiving a call without issue.
Just a pop up saying mobile network is unavailable ,at the end ,when i hang up (but it's wrong, network is still available)
Ryu--X said:
i tried both calling and receiving a call without issue.
Just a pop up saying mobile network is unavailable ,at the end ,when i hang up (but it's wrong, network is still available)
Click to expand...
Click to collapse
Weird! At my device this popup comes in the moment when trying to make an outgoing call. And this call is not started! The other end does not ring!
Could you please tell us, which preferred network type is set in *#*#info#*#* "Phone info" and in "Mobile network settings" (see screenshots)?
I'm not on any aspect a Dev but I give you all my energy on continuing the developpment of this ROM.
Any other support available ?
Berni-0815 said:
Weird! At my device this popup comes in the moment when trying to make an outgoing call. And this call is not started! The other end does not ring!
Could you please tell us, which preferred network type is set in *#*#info#*#* "Phone info" and in "Mobile network settings" (see screenshots)?
Click to expand...
Click to collapse
Here it is !
And you can make an outgoing call sucessfully? The other end rings and you can make a call?
Berni-0815 said:
And you can make an outgoing call sucessfully? The other end rings and you can make a call?
Click to expand...
Click to collapse
Yes exactly , both ways are ok (incoming and outgoing).
Ryu--X said:
Yes exactly , both ways are ok (incoming and outgoing).
Click to expand...
Click to collapse
Hmmm. Then is must be a problem with my german providers (with their apn I think); I've tested two: T-Mobile and O2. With both I can't make outgoing calls...
New version out; see 1st post
Berni-0815 said:
Hmmm. Then is must be a problem with my german providers (with their apn I think); I've tested two: T-Mobile and O2. With both I can't make outgoing calls...
Click to expand...
Click to collapse
Pretty strange, indeed.
The phone i tested with is on another provider than my z5c.
I got to say that i checked the apn before making my tests, and they were good.
I will retry with the new version tonight .
Thanks
The APN shouldn't matter for regular calls unless you're using Wifi calling or VoLTE, maybe disable both and see if it works.