CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0.x (Lollipop), 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 us for messing up your device, we will laugh at you.
*
*/
CyanogenMod 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. You will need to provide your own Google Applications package (gapps). CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit our Gerrit Code Review. Your changelog is whatever was merged into gerrit.
Instructions
First time flashing CyanogenMod 12.0 on your device, or coming from another ROM?
Download the zip(s).
Install a compatible Recovery
Perform a NANDroid backup of your current ROM (Optional)
Wipe data & cache partitions of your device (required when coming from stock!).
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Known Issues
* None
Other Issues?
Before posting on this thread, make sure of a few things:
You've utilized the search function of the forums. Nothing irritates me more than lazy people who do not search for an answer before asking.
If you are the only one having a problem. Boot into recovery, wipe data/factory reset, reflash the rom/gapps and nothing else. Boot up and see if the problem persists.
Make sure your post is relevant to this thread. "I'm having problems rooting/unlocking" is NOT relevant here.
LOGS LOGS LOGS!!!! Use this: SysLog by Tortel
Experience issues?
* Nightlies: bug reports are not accepted. You are relying on yourself and your peers in this thread for support!
* M-series: file a bug in Jira.
Download Links
Mod edit:
Download links removed for lack of GPL compliance.
Useful Links
Unofficial changelog
klimtwifi wiki
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
In particular I would like to thank:
@crpalmer for his work porting cm12 to the picassowifi. It was of great help getting cm12 on the sm t700
@nvertigo67 && @UpInTheAir for their kernel magic and misc fixes
XDA:DevDB Information
CyanogenMod 12.0 for klimtwifi (Tab S 8.4)
Contributors
@eousphoros
ROM OS Version: 5.0.x Lollipop
Version Information
Status: Testing
Created 2015-03-13
Last Updated 2015-03-13
Awesome stuff! Excited to give it a try.
Edit: Super smooth and very pleasant to use. Thank you!
After all this time...
Been away for a while. Heard about the news and thought I'd stop by to congratulate you for the official release. I've been reviewing the threads and am frankly stunned at your attitude and work ethic. Thank you very much and I'll be sure to post if anything isn't up to snuff.
I am so glad to see this. Another great device saved from the buggy laggy touchwiz. Have been using the bliss cm12 with mine. I will flash this asap
Congrats on the official release! Is there anything we need to flash in order to get vibration for the capacitive keys working?
You just made my day. Rooted, flashed and looks great!
(finally no more touch wizz)
Congrats on your official release. I've been using CM12 unofficial since the first day I bought the Tab S. Runs buttery smooth ever since (it's been about a month or two). Still runs silky smooth, no lag and even better no touchwizz Just did a clean install to the new update.
Two thumbs up!
Same here, I think my tablet spent 30 minutes on stock before running your CM12. The official is even smoother, so really thanks a lot
My tablet gets stupidly slow and choppy randomly on this official release
Sent from my SM-T700 using XDA Free mobile app
---------- Post added at 03:52 AM ---------- Previous post was at 02:55 AM ----------
Nvm figured it out. It was the auto display where it changes your screen temperature at night. It made my tablet laggy for some reason
Sent from my SM-T700 using XDA Free mobile app
Is anyone having trouble getting their tablet to go jump deep sleep mode?
I only have faux clock, bbs, es file Explorer, sleep timer and mx player installed. Exact same setup as the unofficial build a few weeks back
Clean install of the first official nightly. Faux clock underclocking to 900mhz and only having 2 cores running
Bbs tells me that it won't go into deep sleep mode with the screen off. It's sitting at the 250mhz frequency the whole time
Looking into kernel wake locks and I see its the PowerManagerService.Wakelocks that is keeping it up
Like I said, it's the same setup as last time. Tomorrow I'll test and see if faux clock is what is keeping it up but I can't see why it would
If there's certain logs that you would like me to collect during certain times. Please let me know
Enddo said:
Is anyone having trouble getting their tablet to go jump deep sleep mode?
I only have faux clock, bbs, es file Explorer, sleep timer and mx player installed. Exact same setup as the unofficial build a few weeks back
Clean install of the first official nightly. Faux clock underclocking to 900mhz and only having 2 cores running
Bbs tells me that it won't go into deep sleep mode with the screen off. It's sitting at the 250mhz frequency the whole time
Looking into kernel wake locks and I see its the PowerManagerService.Wakelocks that is keeping it up
Like I said, it's the same setup as last time. Tomorrow I'll test and see if faux clock is what is keeping it up but I can't see why it would
If there's certain logs that you would like me to collect during certain times. Please let me know
Click to expand...
Click to collapse
If partial wakelocks shows play.services it might be this.
BTW: why do you use faux clock? What advantages does this app has over Settings->Performance for underclocking?
nvertigo67 said:
If partial wakelocks shows play.services it might be this.
BTW: why do you use faux clock? What advantages does this app has over Settings->Performance for underclocking?
Click to expand...
Click to collapse
Partial Wakelocks shows "SystemUpdateService" keeping my device awake for 9 of the 11 hours yesterday/last night. With some text under it that says "Google Services". Does this tell us what it is? All of my apps are updated. The Gapps package I'm using is called "gapps-lp-20141109-signed.zip". I don't remember exactly where I got it(maybe linked from the CM website back in November). It's the Gapps package I've always used.
I have tried a regular reboot. I could try a factory reset if you think that would do the trick, or do you think doing a clean wipe(again) with a new/different Gapps package is best? I'm about to investigate this SystemUpdateService thing and see if I can pull something up from Google searches
Edit - Oh, and I just use Faux Clock since it's what I've been using for a while now. On devices with a custom kernel it gives me a lot more options to tweak the kernel/performance and since CM12 hasn't always had a working Performance section(after you enable Developer Options), I've just continued using it on the tablet.
So far I have found this - http://forum.cyanogenmod.org/topic/...ce-wakelock-on-cm11-m7-massive-battery-drain/
Enddo said:
Partial Wakelocks shows "SystemUpdateService" keeping my device awake for 9 of the 11 hours yesterday/last night. With some text under it that says "Google Services". Does this tell us what it is? All of my apps are updated. The Gapps package I'm using is called "gapps-lp-20141109-signed.zip". I don't remember exactly where I got it(maybe linked from the CM website back in November). It's the Gapps package I've always used.
I have tried a regular reboot. I could try a factory reset if you think that would do the trick, or do you think doing a clean wipe(again) with a new/different Gapps package is best? I'm about to investigate this SystemUpdateService thing and see if I can pull something up from Google searches
Edit - Oh, and I just use Faux Clock since it's what I've been using for a while now. On devices with a custom kernel it gives me a lot more options to tweak the kernel/performance and since CM12 hasn't always had a working Performance section(after you enable Developer Options), I've just continued using it on the tablet.
So far I have found this - http://forum.cyanogenmod.org/topic/...ce-wakelock-on-cm11-m7-massive-battery-drain/
Click to expand...
Click to collapse
Sorry, run out of Thanx...
What you found is a bit older and 'bout cm11. This is something new or a regression to the old problem. I hoped to solve this by downgrading to an older bersion of gapps...
Would you please go to Settings->Apps->All->google play services and check what version it is? Thanx in advance.
What about hardware support? FP Sensor, Cam, Hdr, etc.? Is everything there?
nvertigo67 said:
Sorry, run out of Thanx...
What you found is a bit older and 'bout cm11. This is something new or a regression to the old problem. I hoped to solve this by downgrading to an older bersion of gapps...
Would you please go to Settings->Apps->All->google play services and check what version it is? Thanx in advance.
Click to expand...
Click to collapse
My current version of Google Play Services is at 7.0.96
And right, that is an older issue, but there were some tips about using a Disable Service app to enable something that CM was disabling. I haven't had a chance to try it yet, but I'm hoping it will help out when I get a chance later today
Connected to bluetooth successfully but the sound very choppy. Is this a common problem?
Otherwise wery stable ROM.
Sent from my SM-T700 using XDA Free mobile app
Enddo said:
My current version of Google Play Services is at 7.0.96
And right, that is an older issue, but there were some tips about using a Disable Service app to enable something that CM was disabling. I haven't had a chance to try it yet, but I'm hoping it will help out when I get a chance later today
Click to expand...
Click to collapse
AFter researching and testing I posted this.
Enddo said:
My current version of Google Play Services is at 7.0.96
And right, that is an older issue, but there were some tips about using a Disable Service app to enable something that CM was disabling. I haven't had a chance to try it yet, but I'm hoping it will help out when I get a chance later today
Click to expand...
Click to collapse
I tried and it does work. Look for all update services in disable service and check them off. Sleeping well now.
twped said:
Connected to bluetooth successfully but the sound very choppy. Is this a common problem?
Otherwise wery stable ROM.
Sent from my SM-T700 using XDA Free mobile app
Click to expand...
Click to collapse
Screen off was fine for me but as soon as its on the music was choppy. Tried different governors to no effect.
Anyone else having issues auto updating the nightlies?
When it boots me into recovery, it fails to install the downloaded update and I have to then go back into recovery and install in manually.
interfreak said:
Anyone else having issues auto updating the nightlies?
When it boots me into recovery, it fails to install the downloaded update and I have to then go back into recovery and install in manually.
Click to expand...
Click to collapse
Do you have the TWRP recovery installed?
The auto updating feature just creates a script that is loaded in TWRP and then tries to boot up into TWRP to run the script(aka dirty flash the nightly it just downloaded).
If you have CWM(like we've been using since before the official nightlies) as the recovery, then you can't auto update
Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 2.3 (Gingerbread), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 7 to the HTC Incredible S, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 7?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
Official post
CyanogenMod:
Latest version: update-cm-7.1.0-IncS
Download: link
Mirror: link
MD5sum: 517788657622e8a77abb8cc893365261
Google Apps addon:
Version: gapps-gb-20110828
Mirror: link
Mirror: link
Version: Google Talk with video addon
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Hmmm curious.. Nightly 108 with tiamat has been perfect for me though I wish I knew what changed from that.
I've already tried it, so far so good. I forgot how fast it is to have a AOSP rom!
scoobysnacks said:
Hmmm curious.. Nightly 108 with tiamat has been perfect for me though I wish I knew what changed from that.
Click to expand...
Click to collapse
Feel the same way, not sure if I want to flash or not.
How about battery life?
Sent from my HTC Incredible S using xda premium
baste07 said:
How about battery life?
Sent from my HTC Incredible S using xda premium
Click to expand...
Click to collapse
Cm7 is much better than any sense roms for battery life
Also i have arhd rom, can i just update recovery via rom manager? And download &install this?
How about the 4ext format, anything i should do first?
Sent from my HTC Incredible S using xda premium
---------- Post added at 09:16 AM ---------- Previous post was at 09:01 AM ----------
scoobysnacks said:
Cm7 is much better than any sense roms for battery life
Click to expand...
Click to collapse
how long does it go for on a normal usage
4ext is preserved, make sure you wipe everything if your coming form a sense rom. I don't think I need to say it, but make sure you make a backup just in case.
baste07 said:
how long does it go for on a normal usage
Click to expand...
Click to collapse
Well its really depends on what you running at behind on your phone.
If your phone is running many keep-online apps, like turning on g-maps latitude, gtalk, skype, facebook, twitter, whats app, talkbox, viber, G+, news updater etc. I say, 8 hours.
Plus if your phone have a single "buggy" app, something like older version of skype that will keep your phone CPU "Awake" all the time, I say, battery could last only 4-5 hours.
If you dont have any of those or you only use quality apps, plus 5 calls 10 text and 10mins brownsing per day, the power could last about 2 days and 1 night.
thanks! so i should be good by just updating revoery from ROM Manager and downloading the stable release (of course wipe and backup i'll do)
Yes, that is pretty much it.
i'm having problems with google market.. it's force closing.
baste07 said:
i'm having problems with google market.. it's force closing.
Click to expand...
Click to collapse
that's a simple fix go to language settings and select english again it fixes that
Is the connection issues ironed out? Had problems with the nightly 80s, dunno if the 90s had problem, don't think I tried any of them. I'm on like 78 now, and as tempting as this is to upgrade, I want to make sure I can actually make and receive calls and texts.
That sucked when I found out it wasn't working, really bad actually.
Works ok, just need to test the headphones mic with this new ROM.
Sent from my Incredible S using XDA App
how about the data and wifi connections? stable and all good?
backlights don't switch in landscape mode.
quoler said:
backlights don't switch in landscape mode.
Click to expand...
Click to collapse
that is a sense-rom-only feature, from what i've read.
anyone try out #110?
Getting a FC issue in settings>sound, to change default ringtone. Anyone else facing similar issues in settings? Also any replies as to whether stock kernel is better or need to switch to tiamant? I'm using tiamant latest BTW.
Sent from my HTC Incredible S using XDA App
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.0 (Ice Cream Sandwich), 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 me for messing up your device, I will laugh at you.
*/
CyanogenMod 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. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Instructions:
First time flashing CyanogenMod 9.0 your device, or coming from another ROM?
Root the device and install ClockworkMod Recovery. Instructions are available here.
Perform a NANDroid backup of your current ROM.
Format the system, data & cache partitions of your device.
Perform a factory reset.
Flash CyanogenMod.
Optional: Install the Google Apps addon package.
Upgrading from earlier version of CyanogenMod 9?
Perform a NANDroid backup of your current ROM.
Flash CyanogenMod (your Google Apps will be backed up & restored automatically).
Issues?
Experience issues? Please provide the following info to our bug tracker:
If the device was hard reboot, please provide the file "/proc/last_kmsg".
If the device was soft reboot or is "bootlooping", please run a logcat and provide the full output.
Please use Pastebin when possible.
Download Links:
CyanogenMod:
Latest version: cm-9.0.0-RC1
Download: link
Mirror: link
MD5sum: 289c93e70b500e05abe56b9d7e19606dGoogle Apps addon:
Version: gapps-ics-20120317
Mirror: link
Mirror: link
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
Thanks a lot from Italy!
Thank's, changelog please
Огромни благодарности from Bulgaria as well =) Flashing RC1 at the moment.
although we have known CM9 long enough , but still would like to see some feature explanation
Changelog can bem checked here: https://github.com/CyanogenMod/android_vendor_cm/blob/ics/CHANGELOG.mkdn
KalimochoAz said:
Changelog can bem checked here: https://github.com/CyanogenMod/android_vendor_cm/blob/ics/CHANGELOG.mkdn
Click to expand...
Click to collapse
YOU'RE ALIVE. Lol, we miss you. And thanks for the great builds, CyanogenMod and Kali....
Been using CM9 RC1 for a couple hours now and everything is running pretty good.
The only thing i'm noticing is lag and screen tearing on stock launcher, and that's with or without forcing gpu rendering or surface dithering.
Other then that, everything seems stable enough for a daily driver.
Thank You CM Team!
EDIT: Seems to be happening with other launchers and with window and transition animations...
mellocello83 said:
..screen tearing on stock launcher..
Click to expand...
Click to collapse
Yeah, its the only thing i dont like about CM9, i got it also in apps with white background.
But i love the RC1. Thanks for the hard work CM-Team!
Scofield. said:
Yeah, its the only thing i dont like about CM9, i got it also in apps with white background.
But i love the RC1. Thanks for the hard work CM-Team!
Click to expand...
Click to collapse
Try another kernel (matr1x, _thalamus). It should go away.
karx23 said:
Try another kernel (matr1x, _thalamus). It should go away.
Click to expand...
Click to collapse
Thanks, but im not a fan of 3rd party kernels, hope CM-Team can fix it soon.
Btw, why does the CM team link to the 0317 Gapps, and not the latest - 0429?
elnahir said:
Btw, why does the CM team link to the 0317 Gapps, and not the latest - 0429?
Click to expand...
Click to collapse
Was curious about this as well. Just a goof?
3/17 is the one we test against and has confirmed good signatures for all components.
Sent from my Galaxy Nexus using xda app-developers app
ciwrl said:
3/17 is the one we test against and has confirmed good signatures for all components.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
So I use the4 latest and no problems here but is there anything you can elaborate on that might have caused conflicts?
I've always wondered why I have a greenish look on CM9.
changing kernels solves the problem. Looks like color hue is off.
Any ideas ? why is this kernel related ?
would anyone care to share any major differences between AOKP and CM9? Would flash myself but don't have the time at the moment
Screen tearing on white background is the reason I stop flashing CM9 two month ago... I guess it was never fixed...
rasengan82 said:
Screen tearing on white background is the reason I stop flashing CM9 two month ago... I guess it was never fixed...
Click to expand...
Click to collapse
What do you mean by "Screen tearing"
wrick01 said:
I've always wondered why I have a greenish look on CM9.
changing kernels solves the problem. Looks like color hue is off.
Any ideas ? why is this kernel related ?
Click to expand...
Click to collapse
I've been on AOKP for awhile and never had the issue. I just flashed the RC1 this morning with 04292012 gapps and the matr1x kernel (v22) and mine is not greenish. (Sorry I didn't even boot before flashing kernel).
I've only been running it today with this setup and it is really fast and snappy.
ejatds said:
would anyone care to share any major differences between AOKP and CM9? Would flash myself but don't have the time at the moment
Click to expand...
Click to collapse
I just switched from AOKP today and the main difference is bootanimation, launcher and AOKP has a little more customization options. :silly:
Honestly though, this build is running really nice and fast and I sure missed CM's "go to sleep" button in the notification pull down. So who knows what I'll do...
DO NOT post in this thread until you have read the first three posts and last two pages of this thread in their entirety!
"Me Too" posts for known issues with no useful debugging information WILL BE REPORTED.
What is Omni?
Omni Gerrit Review
OmniLog - changelog
Disclaimer
Code:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you. Hard. A lot.
*/
ROM:
Omni for Samsung Galaxy S 4
Gapps:
http://forum.xda-developers.com/showthread.php?t=2397942
(recommend the MODULAR FULL package, however, keep in mind that the STOCK package is intended for Nexus devices)
UPDATE FROM VARIANT OMNI BUILD TO UNIFIED BUILD
Backup your apps and other pertinent data and DO A FULL WIPE.
Don't complain about it. Just do it. If you try to post bug reports or complaints and you have not conducted a wipe of:
/system
/data
/cache
/dalvik
I will completely and utterly ignore you, as well as report your post for not reading the clearly posted rules at the top of this post.
UPDATE FROM OMNI VIA OPEN DELTA UPDATER
Settings -> System Updates -> Check for update
You will NOT need to wipe anything with the delta updates unless it is explicitly stated or you start having strange issues.
Omni only supports TWRP recovery, use any alternate recovery at your own risk.
Kernel Source: https://github.com/omnirom/android_kernel_samsung_jf
XDA:DevDB Information
Omni for Galaxy S4, ROM for the Samsung Galaxy S 4
Contributors
jakew02, xplodwild
Source Code: http://www.github.com/omnirom/
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Version Information
Status: Nightly
Created 2014-05-28
Last Updated 2015-04-20
Important Information
This is NOT the place to ask questions like:
When will <feature> be included?
Is <feature> included yet?
Can you bring <feature> to Omni?
ETAs of any nature
Follow the rules. This is a new thread and it WILL remain clean and ON TOPIC. I will immediately report any off-topic posts, trolling, flaming, etc. of any sort. This is a DEVELOPMENT thread, and as such, has been posted in the DEVELOPMENT section.
INCLUDE LOGS when reported a bug. Even if you think that you might be the only one with the bug, POST LOGS, that will help narrow down the issue about 100 million times!
Explore the ROM a bit before posting here things like " WHERE IS <feature> CAN YOU ADD FEATURE etc. etc.
You have to understand, that gets extremely annoying after 50 posts like that. Most features can be seen on the blog or in the MERGED section of gerrit.
Root IS NOT included with Omni by default, so you will need to flash SuperSU in recovery SuperSU
How to build Omni from sources:
OmniROM - Setting Up A Compile Environment
Bug Reports and Feature Requests
jira.omnirom.org
Important Information Part 2
Omni XDA Discussion ( NOT DEVICE RELATED DISCUSSION ONLY)
http://forum.xda-developers.com/omni
IRC
Web Client
irc.freenode.net
#omni
First
Using 052814 unified build with 052414 full modular gapps...ROM boots but gets stuck at the "setup wizard". After you select your language and press the white triangle it reads " Welcome...please wait a few minutes" for a minute or so...the the screen goes black except for the status bar and the backlights on the hardware keys stay on.
I clean flashed twice then downloaded the ROM and gapps for a 2nd time then clean flashed those twice...all with the same results as described above.
Hope this helps.
Sent from my SPH-L720 using Tapatalk
Hello,
I know one can flash the 9505 rom on the i337m becuse the bootloader is not locked, but what about the AT&T version (i337), can i flash this (jflte) version on my i337 ?
rabiny said:
Hello,
I know one can flash the 9505 rom on the i337m becuse the bootloader is not locked, but what about the AT&T version (i337), can i flash this (jflte) version on my i337 ?
Click to expand...
Click to collapse
Yes. If you notice, I closed the individual variant threads and put a direct link to this thread. Basically, you can see a list of supported variants by checking this:
https://github.com/omnirom/android_device_samsung_jflte/blob/android-4.4/BoardConfig.mk#L129
That is the list of device asserts that the updater-script will accept.
buzzwyzr said:
Using 052814 unified build with 052414 full modular gapps...ROM boots but gets stuck at the "setup wizard". After you select your language and press the white triangle it reads " Welcome...please wait a few minutes" for a minute or so...the the screen goes black except for the status bar and the backlights on the hardware keys stay on.
I clean flashed twice then downloaded the ROM and gapps for a 2nd time then clean flashed those twice...all with the same results as described above.
Hope this helps.
Sent from my SPH-L720 using Tapatalk
Click to expand...
Click to collapse
I just flashed the 05/28 nightly (on my jfltespr) with the 4-16 Minimal PA Gapps with absolutely no errors. This most definitely sounds like a Gapps problem to me, since the SetupWizard is not packaged or built with the ROM, but instead flashed with Gapps. This is why if you were to NOT flash a Gapps package, you don't have to run through it.
jakew02 said:
Yes. If you notice, I closed the individual variant threads and put a direct link to this thread. Basically, you can see a list of supported variants by checking this:
https://github.com/omnirom/android_device_samsung_jflte/blob/android-4.4/BoardConfig.mk#L129
That is the list of device asserts that the updater-script will accept.
Click to expand...
Click to collapse
Thank you for the quick reply,
What about the locked bootloader, Are there any points I should pay attention to ?
Or i can just download the recent file (from http://dl.omnirom.org/jflte/) and flash it over my current version (jflteatt)
rabiny said:
Thank you for the quick reply,
What about the locked bootloader, Are there any points I should pay attention to ?
Or i can just download the recent file (from http://dl.omnirom.org/jflte/) and flash it over my current version (jflteatt)
Click to expand...
Click to collapse
If you are already running Omni then you're fine. Just follow the instructions from the OP.
These instructions are written under the assumption that you know how to root and install a custom recovery.
Sent from my X9006 using Tapatalk
Is custom hot word launcher built in yet?
ahoslc said:
Is custom hot word launcher built in yet?
Click to expand...
Click to collapse
Yes. I've been using it and it works perfectly fine.
You can see that from gerrit as well as the XDA News Portal...
I'm squashing questions like this now. Please re-read Post 2 as I have updated it.
flashed the 30th nightly, thought of asking about two things,
1. why does the initial setup page needs a working data connection?
2. i lost root after a clean install, am i missing something?
bala_gamer said:
flashed the 30th nightly, thought of asking about two things,
1. why does the initial setup page needs a working data connection?
2. i lost root after a clean install, am i missing something?
Click to expand...
Click to collapse
the root apk has to be flashed via recovery as stated on the first page post.
---------- Post added at 08:40 PM ---------- Previous post was at 08:27 PM ----------
Hello Jakew02
I moved over to your latest rom yesterday the 5/29 nightly and i came across a couple issues.
i have been using cm mod since the days of android cupcake and decided to try this out.
1st issue is when im trying to lower the phone ringer volume, it always goes to lower the sounds/music volume. it is pretty annoying because i have to make all the sliders come out and manually slide the phone ringer volume. even after switching between apps and what not it insists on lowering the music volume.
2nd issue is i cannot get the multi window to work or how to enable it. i have downloaded and installed these apps :halo)),multiwindowsidebar, toggle multiwindow, xhalo floating, xmultiwindow, and xposed installer. also the fixvisibilityofmultiplenonulls. Any help on getting it to work will be appreciated. i am very new to this feature since ive never had it in CM since i thought u couldnt get it, only on Stock Samsung roms.
lastly, is there any way to add shortcuts to the unlock slider like in cm?
thanks
djbootleg said:
the root apk has to be flashed via recovery as stated on the first page post.
---------- Post added at 08:40 PM ---------- Previous post was at 08:27 PM ----------
Hello Jakew02
I moved over to your latest rom yesterday the 5/29 nightly and i came across a couple issues.
i have been using cm mod since the days of android cupcake and decided to try this out.
1st issue is when im trying to lower the phone ringer volume, it always goes to lower the sounds/music volume. it is pretty annoying because i have to make all the sliders come out and manually slide the phone ringer volume. even after switching between apps and what not it insists on lowering the music volume.
2nd issue is i cannot get the multi window to work or how to enable it. i have downloaded and installed these apps :halo)),multiwindowsidebar, toggle multiwindow, xhalo floating, xmultiwindow, and xposed installer. also the fixvisibilityofmultiplenonulls. Any help on getting it to work will be appreciated. i am very new to this feature since ive never had it in CM since i thought u couldnt get it, only on Stock Samsung roms.
lastly, is there any way to add shortcuts to the unlock slider like in cm?
thanks
Click to expand...
Click to collapse
These aren't issues or bugs at all; you just haven't looked around the settings.
all of your questions can be answered by just looking through the settings.
OP updated, please re-read it.
Download page says 193 Mb, the download is 183 mb. I downloaded twice, both 183. Anyone else? The newest nightly.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Shaftamle said:
Download page says 193 Mb, the download is 183 mb. I downloaded twice, both 183. Anyone else? The newest nightly.
Sent from a Shaftamle Galaxy S4
"Thanks Button" is always appreciated!
http://mycolorscreen.com/Shaftamle/
Click to expand...
Click to collapse
It's 183mb, I've just flashed. Working fine.
ZordanKV said:
It's 183mb, I've just flashed. Working fine.
Click to expand...
Click to collapse
Have you tried flashing a custom kernel with the latest nightlys?
bobbarker2 said:
Have you tried flashing a custom kernel with the latest nightlys?
Click to expand...
Click to collapse
Nope, already switched to the other ROM. Omni is good, but doesn't suit my needs
bobbarker2 said:
Have you tried flashing a custom kernel with the latest nightlys?
Click to expand...
Click to collapse
gpu drivers fixed
jakew02 said:
i have stated multiple times that kernel developers will need to begin released "omni-based" kernels.
I WILL NOT alter this ROM to accommodate custom kernels. the kernels need to change to be compatible with the ROM.
Custom kernels will not just magically start working. Kernel developers need to remove the flo adreno drivers and related commits from their kernels. If they don't know which commits those are, they can simply cherry-pick this commit: https://github.com/omnirom/android_kernel_samsung_jf/commit/068449af3996f1072c80dcc4a09a88af43abd7f7
contained in that commit is all of the reverts needed to make a cyanogenmod-based kernel work with Omni.
I have spoken with @Entropy512 about this a few times and we both agreed that we will NOT be altering the ROM in order to this one device to be able to use flo adreno stuff. That's just stupid and causes more work and problems for everyone else.
So the bottom line on this is, if you want a custom kernel, ask your kernel devs to cherry-pick the above commit and release Omni kernels separately from CM-based one.
If anyone has a problem with this, well, gerrit is free to use and open to all.
As before I will use this comparison to better justify my decision:
You wouldn't buy a Playstation controller(an accessory) to use with your Xbox(a primary), once you get home and realize it doesn't work because it's designed for something other than what you have, you call Microsoft and demand that they make the Xbox(primary) work with Playstation controllers(accessory)?
Absolutely Not. If ANYTHING, you would call Sony and demand that they make their controllers(accessory) work with the xbox system.
Hope this clarifies that issue a little better for everyone.
Also on another note:
I have narrowed down the camera preview freeze down to one repository
Click to expand...
Click to collapse
Jake the only reason I asked was because I did a bit of testing for you where the testbuild had support for custom kernels and you said that it should be fixed and you would push the change when you could. I even followed up with you at a later time and you said you hadn't had time/inclination to do it yet. I'm not demanding anything of you and I didn't want to bug you with the issue so I asked someone else who was in similar territory. Had I known about your changed stance on the issue, I wouldn't have brought it up.
CyanogenMod is a free, community built, aftermarket firmware distribution of Android 5.0 (Lollipop), which is designed to increase performance and reliability over stock Android for your device.
Code:
#include
/*
* Your warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
Downloads:
CM server
Installation:
Unlock the bootloader
Flash a recovery
Reboot into recovery
Flash rom.
Reporting bugs:
You are allowed to report bugs only in this thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
Report bugs on Jira at jira.cyanogenmod.org
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
If the problem disappears after running "setenforce 0" from a root shell, grab /data/misc/audit/audit.log
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow. Note: If you can provide the latest night/build that the bug didn't exist, it would greatly help in tracking down what caused it.
Code:
What is your:
Phone model:
CM Download url:
Gapps version:
Radio (baseband):
CM version:
Did you:
Install xposed framework?
Restore apps in titanium backup?
Flash another kernel?
Are you using a supported recovery?
start Art Runtime?
search the thread for similar issues before posting?
I don't reply to tech support by pm or emails/hangouts messages.
If you have xposed installed, please bother to post.
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
Offiical cm for peregrine, ROM for the Moto G
Contributors
Somcom3X, @BlueFlame4
Source Code: http://www.github.com/CyanogenMod
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
ROM Firmware Required: Unlocked Bootloader with recovery
Version Information
Status: Beta
Created 2014-11-24
Last Updated 2015-04-20
Reserved
I present to you CyanogenMod 12 for the peregrine. After delaying my initial release to an almost fully working state, it is here now.
Video review:
Big thanks to @Cm9aphla
Bugs:
Wifi tether (Experimenting)
Bluetooth stack issues with multitasking. Somewhat buggy
GPS issues as well.
Reserved
Big thank you to all of the donators:
Please confirm your username by posting the remainder of the transaction ID. To donate, please send to [email protected] via paypal
Donators
Code:
S. Fabbro 4HR94540AN4xxxxxx
D. Noonburg 604068013C4xxxxxx
G. Girotto 9SH91349CF4xxxxxx
Gracias!
New recovery is in the works, stay tuned.
If anyone needs some assistance, join #cyanogenmod or #carbonrom on irc.
I'll be in #carbonrom-dev most of the time.
If no one responds instantly, simply wait. Don't be this guy (You know who you are):
Code:
[22:57:18] --> carbon_guest ([email protected]/web/freenode/ip.97.xx.3.xx) has joined #teamcarbon
[22:58:19] <carbon_guest> I'm having an issue, this is my first time trying the carbon ROM the installation
was succesful but every time i try to install the GAPPS it gives me an error and says (Satus 6), any aid please?
[23:01:02] <carbon_guest> anybody here?
[23:10:06] <carbon_guest> hellooooooooooooooooooooooooooooooooooooooooo
[23:26:12] <-- carbon_guest ([email protected]/web/freenode/ip.97.xx.3.xx) has quit (Quit: Page closed)
Great work! I'll stay here until official 5.0 ota arrives. [emoji16]
Which superuser flashable zip should I use? The ones I used in KK don't work.
---------- Post added at 10:33 PM ---------- Previous post was at 10:33 PM ----------
And the ROM is rock solid, congrats!
Awesomeness, grabbing it now and will run it through the paces.
@Somcom3X
great work man =D
Bugs that I saw:
Wifi Tether (mentioned on op)
CPU Clock on 1190 almost all the time when the screen is on
@Somcom3X Excellent release! Though I've encountered a few issues apart from the mentioned ones.
AOSP keyboard gesture swiping does not work
Power Off does not work
Notification sound does not work. Tried changing it a few times but none of which works. It vibrates though.
Notification LED doesn't work? I don't think it's working or how it's intended to work in 5.0 Lollipop, but Pulse Notification light is turned on (This seems to work for alarms though)
Random Settings force closes
Maps is not working -- I know it's totally unrelated but it could be GPS related as it just kept showing "Waiting for location..."
Some apps are left even after clearing all apps. ie: SuperSU requests, Contacts, app installs.
Volume rocker for Media Volume gets stuck at a certain point, though it's only a visual bug.
Crossed out stuff just suddenly worked. lol
Is it possible to get Busybox working on CM12 too? Can't find one that would install.
Using this as a daily driver until I find something that wouldn't let me.
zackwire said:
Which superuser flashable zip should I use? The ones I used in KK don't work.
---------- Post added at 10:33 PM ---------- Previous post was at 10:33 PM ----------
And the ROM is rock solid, congrats!
Click to expand...
Click to collapse
I used this and it seems to be working fine. http://download.chainfire.eu/589/SuperSU/
I'm testing since you release the zip in the other thread (I was even about to suggest a new thread ).
I did a dirty flash from cm11, so, maybe some of my reports here are specific about doing dirty flash (just in case, remember to redo your lockscreen security, because the dirty flash made your lockscreen accept anything as password. Remaking the lockscreen security fix it).
* Stock camera doesn't work (shows image, but doesn't take photos, even after cleanup the application). Downloading the google camera or whatever other camera works (and it seems the camera bug from cm11 is gone).
* f2fs doesn't work, ext4 works but useless (you can't do anything, but the cm12 reads that there's a partition and with size, etc), exfat doesn't work either. The worse is: using any of the filesystems I said made you unable to even reformat de sdcard. Only fat works for me. Btw, I'm unable to copy from pc to sdcard.
Thanks
Downloading now. Thanks for posting, been waiting for a lollipop rom.
Edit:
Gps is working fine for me, camera works when it wants to, replaced the stock camera with a port from the apps section of this forum.. Google camera seems a bit more stable. Installed no frills cpu control and disabled safety valve and other apps being able to set frequency and I noticed while it still says min is 1.1 if you look at stats it will go to 300 like normal.
Guest Mode is enabled ?
settings crash sometimes, but it's working well
thanks for your great work
Hi. I'm so excited to install this, but I want to know if I'll be able to go back to KK if there is any problem
Thanks for all your hard work!
Great work man
Just out of curiosity, the thread name is "[ROM] unOfficial Cyanogenmod 12 4.4.4 for the Moto G 4G (Peregrine)".
CM12 is made after 5.0, not 4.4.4 - right?
Or am I misunderstanding what the 4.4.4 means?
Thanks!
athlantar said:
Just out of curiosity, the thread name is "[ROM] unOfficial Cyanogenmod 12 4.4.4 for the Moto G 4G (Peregrine)".
CM12 is made after 5.0, not 4.4.4 - right?
Or am I misunderstanding what the 4.4.4 means?
Thanks!
Click to expand...
Click to collapse
This is CM12 5.0
Probably just a typo by SomCom3X.
Can confirm lack of GPS signal lock. Could be the same bug with CM11.2 where you need to get it just right with a previous signal lock on stock and then flash. Otherwise, running extremely smoothly. Latest SuperSU Beta 2.27 gives root without any big problems, restoring TiBu as we speak. Also can confirm lack of swipe in stock keyboard. SD Card access is working. Great work!
Getting a GPS lock before you flash cm12 worked for me. That should be step one from now on before flashing any ROM. Just in case ya know. So far everything's running great.
Level99 said:
Can confirm lack of GPS signal lock. Could be the same bug with CM11.2 where you need to get it just right with a previous signal lock on stock and then flash. Otherwise, running extremely smoothly. Latest SuperSU Beta 2.27 gives root without any big problems, restoring TiBu as we speak. Also can confirm lack of swipe in stock keyboard. SD Card access is working. Great work!
Click to expand...
Click to collapse
I've read it's an issue with quite a bit of Motorola devices. The stock GPS trick is the best thing possible to do at the moment.
zackwire said:
Which superuser flashable zip should I use? The ones I used in KK don't work.
Click to expand...
Click to collapse
here you go mate
edit:
whoops someone posted it already ^^
mhh, better more links than no links
gr3ud said:
here you go mate
edit:
whoops someone posted it already ^^
mhh, better more links than no links
Click to expand...
Click to collapse
Okay, when already posting links, there is latest beta v 2.27
THERE WILL BE NO MORE UPDATES HERE!
This thread hasn't been updated in a while as I'm working on mainline support and a kernel 5.10 release for the Note 10.1. There are excellent releases of Android 9+ from @html6405 now and I don't intend on updating this thread. I'll leave everything as is, but don't expect me to view this thread on a regular basis. Most questions are already answered, use the search.
For the new mainline kernel version, please don't ask for any ETAs, there's still some things to be fixed before there will be an official release and I have a normal life to take care off.
If you have experience with kernel / ROM development and want to help me out? Leave me a message, I'd appreciate any helping hand no matter how much you can contribute, every little bit helps. Even looking at the device tree and giving me hints would be great as I would still consider myself being intermediate at best at putting everything together, it's just a lot to dig into with the little time I have.
=====================
Code:
/*
* Your (expired) warranty is now void.
*
* I am 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 me for messing up your device, I will laugh at you.
*/
Hi, I'm currently trying to get this device officially supported again as I really love it and it never let me down in the last 5 or so years. It still works amazingly fast and I have no need to replace it with anything else.
As I'm a Java engineer for my day job there is a lot of new stuff here, I had some contact with C/C++ when I studied CS a couple of years ago but never actually wrote anything bigger than two or three files in these languages. This is quite an adventure and I learned a lot already but I'm open for any help you can offer. After all, I'm doing this for fun and getting better at whatever hits me in the face while doing it.
Current Status
Frozen - No further development!
Working
Audio
Video
Bluetooth
GPS
Hardware Acceleration
SELinux
Sensors
IR
RIL (N8000)
Wifi (98% of the time?)
Partly working
Camera (use OpenCamera, zoom and focus not working currently)
Setup Wizard: Voice Match installation screen has wrong rotation
MTP (occasionally crashing)
Not working at all
RIL (N8020)
Reporting Bugs
Please provide logcat, dmesg, kmsg, steps to reproduce or whatever is appropriate to help me understand the issue.
Here is a link to help you help me: How To Logcat
Source Code
Device #1: n8000
Device #2: n8013
Device #2: n8020
Common: n80xx-common
Common: p4notelte-common
SoC: smdk4412-common
SoC QC: smdk4412-qcom-common
Kernel: smdk4412
Hardware: samsung
FAQ
Q: Why another thread?!?
A: The ROM provided by @lirokoa is great but it is based on sources that deviated quite a lot from the official LOS repo, I try to close this gap and get the ROM aligned to the remaining devices based on the SMDK4412 core so that everbody profits from the development going on there. This ultimately means that we can get a 8.x alpha version "soon" after fixing the remaining issues.
Q: How can I help to improve the ROM?
A: If you are a developer, I'd be happy to discuss the remaining issues with you and how to approach/solve them. I'm open for pull requests on Github. If you are testing the ROM and can provide log files for issues this is also a great thing, even more so if it is one of the devices I do not own.
Q: What's up with the performance?
A: Disable Live Display, it's actually not supported by the GPU (or at least by the current driver)
Q: The camera is crashing!
A: Use Open Camera
Q: Wifi attempts to connect but never succeeds!
A: Try reflashing again, including wiping. This usually fixes it.
Credits and Thanks
all the people that worked/are still working on the smdk4412 device and kernel source code, this wouldn't be possible without their hard work!
the guys from #lineageos-dev channel for helping me out with my questions
all the people posting helpful guides in various sections all over the forums
@lirokoa for the updates and support that helped this device to live on until today
XDA:DevDB Information
LineageOS 14.1 N8000/N801X/N8020, ROM for the Samsung Galaxy Note 10.1
Contributors
Don Carnage
Source Code: https://github.com/Viciouss?tab=repositories&q=android
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.0.x
Based On: LineageOS
Version Information
Status: Beta
Created 2018-12-28
Last Updated 2019-11-28
Updates
Build N6 (12.03.2019)
Bluetooth for the N8020
Reactivated pegasusq boost
Set maximum volume from 5 to 7
Platform Security Updates (03/19)
Build N5 (15.02.2019)
Enabled IR sender
SELinux rule cleanup
Added N8020 support!
Build N4 (21.01.2019)
Fixed Power HAL permission issues
Eliminated some warnings from logcat (camera and boost related)
Camera shouldn't crash anymore
Build N3 (07.01.2019)
Fixed the video playing issues
Build N2 (31.12.2018)
N801x now available!
Basic camera support, some problems with video
Activated CPU Power Management
Streamlined some kernel parameters with other configs for the same board
Build N1 (29.12.2018)
Make the Note 10.1 great again!
Lots of device file adjustments
Fixed keyboard not showing up initially
Fixed Settings app crash
Installation
use TWRP files from the link below!
coming from stock: flash TWRP TAR.MD5 file via Odin (I used 3.12 for this) or Heimdall (latest)
TWRP already installed: flash TWRP IMG file via TWRP
boot into recovery
wipe cache + dalvik/art
coming from stock/another rom: wipe system + data
flash ROM first, then GApps without rebooting the device
wipe the cache again just for fun
Need Root for Apps?
go to https://download.lineageos.org/extras
download the addonsu-14.1-arm-signed.zip package
open TWRP and flash it via the Install button
TWRP
TWRP got it's own thread, click this link to get there.
ROMs
ROM N8000 - Build N6
ROM N801x - Build N6
ROM N8020 - Build N6
Open GApps
Click me (ARM - 7.1 - don't use FULL as there is not enough space to install it - try micro or lower instead)
Archived Downloads
ROM N8000 - Build N5
ROM N801x - Build N5
ROM N8020 - Build N5
-
ROM N8000 - Build N4
ROM N801x - Build N4
-
ROM N8000 - Build N3
ROM N801x - Build N3
-
ROM N8000 - Build N2
ROM N801x - Build N2
-
ROM N8000 - Build N1
Wow!
thank your development for this old Pad.
will try it in a free time.
: )
Downloading. Will post some feedbacks later. Thanks for continuing the development on this old brick. ?
i couldn't get secretwolf98 version to install on my n8013 so i am keen to see if this one will install for me when the n801x version is ready
There is a new build with basic camera support, the back camera has some issues with recording videos which will crash your camera app. I noticed that activating the torch while having the camera app open in the background/foreground will also crash the camera app, so still some issues there.
The work on the camera will go on after the big party, I wish everyone a good start into 2019
I still use 2 of these and thank you for getting back into it. Using lineage 14.1 now. Will keep watching.
Great. I've just incidentally gone back to this forum after a long time to check if there's any newer ROM than lirokoa's for my N8000
I'll check it out. Thanks a lot
Got it all installed - but can't get over an error code 190 ("can't download app")when trying to install chrome. Unsure if this is rom related or gapps related.
Also flashed the 14.1 su package - works well with the rom as expected. Youtube from the play store does not work - plays audio but no video. Other than that as I play with this I'll see if I can find any other bugs. Really appreciative of you picking this up!
Thank you very much for continuing the development of this tablet!
My N8000 is presently running on lirakoa's latest build lineage-14.1-20170810-UNOFFICIAL-n8000 with open gapps micro and as root solution Magisk 18.0.
Recovery is TWRP 3.02.
Everything is working fine except the well known bugs, and it seems that most of these have been fixed in your latest build.
I've never tried video recording with this tablet but had some camera crashes recently when using the ClearScanner app, in fact it's not usable with this app.
Otherwise I think it's usable as daily driver, and it was.
My daughter used it for university until recently.
So, as far as I understand, your build should be on the same level and I'm gonna try it very soon.
Do you think a dirty flash could work?
thepolish said:
Got it all installed - but can't get over an error code 190 ("can't download app")when trying to install chrome. Unsure if this is rom related or gapps related.
Also flashed the 14.1 su package - works well with the rom as expected. Youtube from the play store does not work - plays audio but no video. Other than that as I play with this I'll see if I can find any other bugs. Really appreciative of you picking this up!
Click to expand...
Click to collapse
Thanks for pointing those out, I'll have a look at it later today.
curiousde2002 said:
So, as far as I understand, your build should be on the same level and I'm gonna try it very soon.
Click to expand...
Click to collapse
Not quite yet, lirokoa put some effort in the ROM and there are probably things that I don't know about yet which are broken. See my last quote above for example. I'm still learning the inner working of the linux kernel and Android which is quite a huge task.
curiousde2002 said:
Do you think a dirty flash could work?
Click to expand...
Click to collapse
It could work but there is no guarantee as always. There are some changes here and there which can potentially break it.
Don Carnage said:
Thanks for pointing those out, I'll have a look at it later today.
Click to expand...
Click to collapse
The 190 issue was fixed with a reflash and and formatting my system. Took 3 times - not sure but I think it was on my end. The youtube however is still at issue. I was able to view in browser w/o issue though. It is just the app. Side loaded a bunch of older APKs of youtube with same result.
thepolish said:
The 190 issue was fixed with a reflash and and formatting my system. Took 3 times - not sure but I think it was on my end. The youtube however is still at issue. I was able to view in browser w/o issue though. It is just the app. Side loaded a bunch of older APKs of youtube with same result.
Click to expand...
Click to collapse
I can confirm your observations. Chrome is running smooth but the youtube app is only giving me audio with a black video stream.
Don Carnage said:
I can confirm your observations. Chrome is running smooth but the youtube app is only giving me audio with a black video stream.
Click to expand...
Click to collapse
It is really good ROM for N8000! But it seems not all video codecs are switched on in assembly. Except YouTube any IPTV application does not work, there is no video in Instagram (the still image of the first frame only) and in browsers many videos cannot be reproduced too.
Samsung SmartThins and Samsung Galaxy Apps application and is not started too. Sadly, as I remember, only from Galaxy Apps can be install the S-Pen application. By the way, somebody knows where to take .apk for Samsung Galaxy Apps? And how to work with the stylus?
Thank you very much for this ROM I'm new here on XDA, however I have recently flash this ROM to my n8013 it's running pretty good, but I have 2 issues so far.
First, I'm having some troubles accessing to my wifi network, I have a Spectrum router which have 2g and 5g but it keep saying that the password may be incorrect, I have try many apps so far changing settings on my router but no success; but when I go with my phone on Hotspot I can get access and establish connection.
I'm also trying to get root access, I already flash the path for LineageOS 14.1 but when I go to developers I can't get access to the manage option. And when I run the root checker app I shows that I don't have root access.
Thanks,
meca42 said:
I'm also trying to get root access, I already flash the path for LineageOS 14.1 but when I go to developers I can't get access to the manage option. And when I run the root checker app I shows that I don't have root access.
Thanks,
Click to expand...
Click to collapse
Have you tried Magisk for root already?
NikoNik7 said:
It is really good ROM for N8000! But it seems not all video codecs are switched on in assembly. Except YouTube any IPTV application does not work, there is no video in Instagram (the still image of the first frame only) and in browsers many videos cannot be reproduced too.
Samsung SmartThins and Samsung Galaxy Apps application and is not started too. Sadly, as I remember, only from Galaxy Apps can be install the S-Pen application. By the way, somebody knows where to take .apk for Samsung Galaxy Apps? And how to work with the stylus?
Click to expand...
Click to collapse
UPD.
Found Samsung Galaxy Apps. It's no S-Pen application too. There is a Google hand-written input. It is possible to cost them also and not to found S-Pen any more.
So, will be great if there is a video's full support and will earn Samsung SmartThins and if earns the IR-port for control of household appliances (now does not work on N8000). After everything it will be a masterpiece!
many thanks for the new build :good:
curiousde2002 said:
Do you think a dirty flash could work?
Click to expand...
Click to collapse
for me it worked
There is an issue with decoding the video stream but I'm not quite sure what's the root cause yet. Still investigating.