[SM-T520] CyanogenMod 11.0 UNOFFICIAL nightlies: Tab Pro 10.1 Wifi (picassowifi) - Galaxy Tab Pro 12.2, 10.1, 8.4 Original Android De

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.4 (Kitkat), 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 11.0 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
* See post #2
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
Links
CyanogenMod: (use latest build): http://download.crpalmer.org/nightlies/picassowifi/
* See the second post for most details about nightlies.
Google apps addon: (use latest kk gapps)
Download: http://goo.im/gapps
Mirror: http://download.crpalmer.org/downloads/gapps/
CWMR (Recovery): (use latest version)
Download: http://download.crpalmer.org/downloads/picassowifi/
* Unzip the .ZIP file and then flash the .tar.md5 that it contains using Odin
Source Repos::
* vendor
* kernel
* device
* And some other ones which I will post soon (hardware/samsung/...)
The CyanogenMod team would like to thank everyone involved in helping with testing, coding, debugging & documenting! Enjoy!
XDA:DevDB Information
Unofficial CyanogenMod 11.0 for Tab Pro 101 Wifi (picassowifi), ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
Version Information
Status: Beta
Created 2014-09-07
Last Updated 2014-09-17

Reserved
Working:
* adb [2014-09-14 and later]
* Audio: playback on both speakers
* Bluetooth
* Camera [2014-09-17 and later]
* Capacitive keys
* Capacitive lights
* Chromecast screen casting
* Display brightness (but not autobrightness)
* Display: Auto-brightness [2014-09-18 and later]
* DRM [2014-09-17 and later]
* Google Play Movies & TV (mostly) [2014-09-17 and later]
* GPS [2014-09-14 and later]
* Headphones
* IR blaster [2014-09-24 and later]
* Lid sensor [2014-09-19 and later]
* Microphone (voice recognition)
* Miracast displays [2014-09-17 and later]
* mtp [2014-09-14 and later]
* Netflix [2014-09-23 and later]
* SD Card
* Sensors
* Torch [2014-09-18 and later]
* USB OTG including USB storage
* Vibrator
* Wifi
* Youtube 1440p playback [2014-09-23 and later]
Not working:
* Google Play Movies: downloading a video and then playing the downloaded copy [still waiting on CyanogenMod review]
* Offmode charging

Reserved
Nightlies:
Download:
SM-T520 (picassowifi) nightlies folder
Known Issues:
* See post #2
Changelogs:
The changes are in there groups. There are upstream CM changes (independent of this device):
* Main CM changes (ignore everything in red): cmxlog for mondrianwifi
Device specific changes:
* Device changes
* Vendor blob changes
* Kernel changes
And then Exynos specific changes:
* I still have to get this setup
The changelog contains all changes made to that branch. Each nightly will be tagged and looks like:
7cd5c0b (HEAD, tag: nightly-20140808, m/cm-11.0, github/cm-11.0) picassowifi: init: Configure minimum GPU speed
The tag(s) that say "nightly-xxxxxxx" indicate that all changes from this commit down are in that nightly. Therefore, you can see what has changed since a specific version by looking for all entries between your current night's tag and the one that you are going to download and install.

I shall pay close attention to this one.

@crpalmer, let me be the first to congratulate you on this great effort. I may have a working port and all but mine is nothing compared to yours! It would probably take me a much longer time to fix all the bugs and glitches than it would take you.
I know I can speak for everyone when I say this that we will all love this and appreciate your efforts! Best of luck on developing this ROM and keep up the good work!
PS: When you say Google Play Movies & TV doesn't work you mean that it downloads and plays movies in very bad quality right?
EDIT:
Can confirm that headphones are working
Can confirm that ART is working
Can confirm that portrait orientation doesn't cause status bar to go crazy
Can confirm that recent app button works
Can confirm that Wi-Fi remembers password upon reboot
Can confirm that Google Play Music works properly
For others to confirm too:
Don't know if this happens to everyone but Play Store doesn't install apps till you quit out of it and restart it upon your FIRST time setup of tablet. Then it works!

Shaheer said:
@crpalmer, let me be the first to congratulate you on this great effort. I may have a working port and all but mine is nothing compared to yours! It would probably take me a much longer time to fix all the bugs and glitches than it would take you.
I know I can speak for everyone when I say this that we will all love this and appreciate your efforts! Best of luck on developing this ROM and keep up the good work!
PS: When you say Google Play Movies & TV doesn't work you mean that it downloads and plays movies in very bad quality right?
EDIT:
Can confirm that headphones are working
Can confirm that ART is working
Can confirm that portrait orientation doesn't cause status bar to go crazy
Can confirm that recent app button works
Can confirm that Wi-Fi remembers password upon reboot
For others to confirm too:
Don't know if this happens to everyone but Play Store doesn't install apps till you quit out of it and restart it upon your FIRST time setup of tablet. Then it works!
Click to expand...
Click to collapse
Exciting! Can't wait to flash.

Shaheer said:
@crpalmer, let me be the first to congratulate you on this great effort. I may have a working port and all but mine is nothing compared to yours! It would probably take me a much longer time to fix all the bugs and glitches than it would take you.
I know I can speak for everyone when I say this that we will all love this and appreciate your efforts! Best of luck on developing this ROM and keep up the good work!
PS: When you say Google Play Movies & TV doesn't work you mean that it downloads and plays movies in very bad quality right?
EDIT:
Can confirm that headphones are working
Can confirm that ART is working
Can confirm that portrait orientation doesn't cause status bar to go crazy
Can confirm that recent app button works
Can confirm that Wi-Fi remembers password upon reboot
For others to confirm too:
Don't know if this happens to everyone but Play Store doesn't install apps till you quit out of it and restart it upon your FIRST time setup of tablet. Then it works!
Click to expand...
Click to collapse
I didn't have any problems with the play store this morning. Did you wipe before installing? Which version of gapps did you use?
Google Movies doesn't work at all now. Either DRM or selinux related (probably).
Thanks for the extra testing!

crpalmer said:
I didn't have any problems with the play store this morning. Did you wipe before installing? Which version of gapps did you use?
Google Movies doesn't work at all now. Either DRM or selinux related (probably).
Thanks for the extra testing!
Click to expand...
Click to collapse
Nope looks like it was just me for the play store. :silly: I reinstalled and it worked fine afterwards.
I tested Google Play Movies and you're right it doesn't work. If you try downloading an HD movie it says its only like 356mb and it doesn't play I bet you'll get it working though! :good:

Thanks 4all crpalmer!!! Exciting rom!!! XD, will wait stable rom

Must say, that my battery life seems to have gone up just the slightest touch but i'm liking it!
Can't wait for next release! lol
---------- Post added at 08:52 PM ---------- Previous post was at 08:12 PM ----------
PS: Just a suggestion, enabling multiuser would be great! :angel:
EDIT: Can confirm that Google Play Music works properly

Awesome to see more CM for our device! Thanks you all guys, working hard to make it work :good:

This works great for me for daily driver. Thanks for your effort.

Shaheer said:
Must say, that my battery life seems to have gone up just the slightest touch but i'm liking it!
Can't wait for next release! lol
---------- Post added at 08:52 PM ---------- Previous post was at 08:12 PM ----------
PS: Just a suggestion, enabling multiuser would be great! :angel:
EDIT: Can confirm that Google Play Music works properly
Click to expand...
Click to collapse
Multi-user is an easy one, that will be in tomorrow's build.
Speaking of tomorrow's build, I was meaning to post a general note about this, which seems like a fine post to do so:
The reason the thread is labelled "nightlies" is that there won't be any "releases" that I announce. When there are important changes, I'll try to remember to post them but no matter way every night it will (try) to sync the latest code (mine and upstream CyanogenMod code) and build a release based on that code.

Thankyou so much crpalmer really appriciate it
One thing i miss a lot is fastcharching, it takes forever to charge. ...i know it's kernel related, but is there any chance you could get it implemented in roms stock kernel?
Again thanks a bunch for your great work, gonna flash soon :victory:
Edit: well i dirty flashed on top off r6 and did a clen install (full wipe) and just got a black screen both times! !

NIce ROm can't wait till Netflix get fixed!!

spoonymoon said:
Edit: well i dirty flashed on top off r6 and did a clen install (full wipe) and just got a black screen both times! !
Click to expand...
Click to collapse
Same here - 0907 ROM works fine, 0908 won't boot even after clean flash.
ETA : glad to see someone else having the same issue. At least I know now it wasn't a screw up on my end.
Later ETA: Sorry, just realized I should have gotten logs for the failed boot. I was more worried about getting it running again before I had to leave for work...

spoonymoon said:
Thankyou so much crpalmer really appriciate it
One thing i miss a lot is fastcharching, it takes forever to charge. ...i know it's kernel related, but is there any chance you could get it implemented in roms stock kernel?
Again thanks a bunch for your great work, gonna flash soon :victory:
Edit: well i dirty flashed on top off r6 and did a clen install (full wipe) and just got a black screen both times! !
Click to expand...
Click to collapse
Genesius01 said:
Same here - 0907 ROM works fine, 0908 won't boot even after clean flash.
ETA : glad to see someone else having the same issue. At least I know now it wasn't a screw up on my end.
Later ETA: Sorry, just realized I should have gotten logs for the failed boot. I was more worried about getting it running again before I had to leave for work...
Click to expand...
Click to collapse
Looks like my autobuild didn't pull in the vendor blobs correctly last night. That's most likely the problem you're seeing (it's about 10MB smaller than yesterday's build). I hopefully fixed that and kicked off another build. It's going to take about 1-2 hours for that to finish though.

crpalmer said:
Looks like my autobuild didn't pull in the vendor blobs correctly last night. That's most likely the problem you're seeing (it's about 10MB smaller than yesterday's build). I hopefully fixed that and kicked off another build. It's going to take about 1-2 hours for that to finish though.
Click to expand...
Click to collapse
@spoonymoon
 @Genesius01
There's a new build there now. The size looks better. Let me know if that one is built right or not...

That's a winner!
Sent from my SM-T520 using XDA Premium HD app

Yeah all great, flashed on top off r6, not a single hiccup
Really great with nightlys on this device. ..thanx a lot!
Ehrm, sorry for bringing this up again but is there any chance off supprt for fastcharge?

Related

CyanogenMod-6 for Aria: It's soo sexy - proof is in the kernel!

CyanogenMod is a free, community built distribution of Android 2.2 (Froyo) which greatly extends the capabilities of your phone.
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.
*/
This is an AOSP-based build with extra contributions from many people which you can use without any type of Google applications. I found a link from some other project that can be used to restore the Google parts, which can be found below or elsewhere in the thread. I've still included the various hardware-specific code, which seems to be slowly being open-sourced anyway.
Visit the CHANGELOG for a full list of changes and features!
All source code is available at the CyanogenMod Github!
If you'd like to to contribute to CyanogenMod, checkout our Gerrit instance.
INSTRUCTIONS:
- First time flashing CM 6 to your Aria(or coming from another ROM)?
1. Unlock/root your device and install Clockwork Recovery via ROM Manager
2. Do a Nandroid backup!
3. WIPE/Factory Reset
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM6?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
HOW TO REPORT BUGS OR PROBLEMS?
- Was it a hard reboot? Get me the file "/proc/last_kmsg".
- Was it a soft reboot or a "boot loop"? Run "adb logcat" and get me the full output.
- Pastebin links preferred
- Please use the issue tracker whenever possible!
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
http://mirror.kanged.net/gapps/
Latest version: 6.0.2.1-Aria - 09/12/2010
Download: update-cm-6.0.2.1-Liberty-signed.zip
Mirror: update-cm-6.0.2.1-Liberty-signed.zip
MD5Sum: 0b93e84a33a5f98d7e8f4162f5b2a5a4
Release Candidate: (MANY Updates/bugfixes) Includes new kernel with many perfomance enhancements, including overclock (when used with setcpu)
Download: update-cm-6.1.0-RC0-Liberty-signed.zip
MD5Sum: 20af9ea0218cd7097ec5d843b1b0b414
Google Addon: MDPI-20101020
Mirror: http://www.tap3w0rm.com/hosted/android/gapps/gapps-mdpi-20101020-signed.zip
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
Linux GPL information:
Kernel modified by cyanogen, based on source provided for the HTC Liberty (Aria) and HTC Legend by HTC
Current kernel source and config are located at http://github.com/attn1/htc-kernel-liberty
ReadMe Here: http://github.com/attn1/htc-kernel-liberty/blob/master/README
Kernel credits are posted in the readme and github repository changelogs, with additions and configuration by cyanogen.
Credits:
This bulk of this PROJECT is still largely (overwhelmingly) the result of the efforts of cyanogen and team cyanogenMod.
I need to be crystal clear that I didn't do this by myself in a vacuum. This was a team effort. I'd like to thank cyanogen, who pointed me in the right direction when I had a false start and has now integrated this device project into cyanogenmod..
I'd like to thank Eugene, who got me started.
I'd like to thank the entire crew at irc channel #liberatedAria for helping so many noobs get started so I could do other stuff, but especially endeng, for building the first dev environment to follow and verify my process to keep my builds honest, and for helping jznomoney also build a dev environment and continue work while I was sidetracked. jznomoney did a ton of grunt work and some good guesswork to finish up and get a largely working ROM. Atlas gave me a clue after I needed one after not sleeping for a few days.
Large and in charge and consistently contributing big time in the IRC channel are:
shad0wf0x
yoshiofthewire
redapex
jasonyump
NeoLobster
Please read the FAQ before/while downloading. Failure to do so will result in bad voodoo.
Nightly:
It's a beautiful thing: nightly builds from the cyanogenMod buildbot - these are builds against the latest cm code repository, are experimental and may not work. But it you want to look at the very latest, this is where you'll find it:
http://mirror.kanged.net/cm/nightly/liberty/
Non-standard disclaimer:
In order to use this ROM, you must have already installed clockwork recovery. If you manage to brick your phone with this ROM from there, you are a dumb ass of unimaginable proportions, and I absolve myself of any responsibility whatsoever. Further, any damage done to your phone with this experimental software is your fault and no one else's.
FAQ
Q. I bricked my phone/my signal sucks/my cat exploded since installing this ROM.
A. See the Non-standard disclaimer above.
Q. I can't seem to flash the rom successfully, and my Nandroid backups don't restore.
A. Do NOT start Clockwork recovery by powering down the phone with the USB port plugged in. Clockwork WILL NOT operate reliably that way. Power down the phone with the USB cord disconnected so that the phone powers off properly. Then start the phone by pressing and holding the vol-down button while pressing the power button to start. After diagnostics complete, you can enter Clockwork the proper way.
Q. I lost my 3g connection after I flashed cm6, now the icon just says "H".
A. You didn't lose 3g - the H is for HSDPA, which is enhanced 3g, sometimes referred to as 3.5g. It's a good thing, if you see an "H" where the "G" used to display - don't worry about it. Print this out for next time you head to the can: http://en.wikipedia.org/wiki/High-Speed_Downlink_Packet_Access
Q. How do I keep my wifi from going to sleep every time the screen shuts off?
A. There is a hidden feature that disables wifi sleep.
menu > Settings > Wireless & networks > wifi settings > menu (again) > advanced > Wi-Fi Sleep policy > Never > menu > Save
However: although you can keep the wifi service from sleeping, the wifi driver will still sleep on it's own after detecting no bus activity for a period of time.
Q. Will this ROM support over or under clocking with Set CPU?
A. The kernel has been updated to support overclocking with SetCpu
Q. I can't get flash to work. What's going on?
A. Flash 10 is not supported by this CPU and AOSP Android does not support flash lite. Even if a hack allows installation of Flash 10, it's doubtful it will run very well.
Q. Where's the FroYo wireless hotspot?
A. It's in there!
menu > Wireless & networks > tethering and portable hotspot
Q. What's wrong with bluetooth? It doesn't work with my floozengadget.
A. Nothing. All bluetooth functions have been confirmed *WORKING* with compatible devices.
Q. But my floozengadget device is bluetooth compatible. What's wrong with bluetooth?
A. Nothing. Android AOSP bluetooth on the broadcom chipset is not compatible with every bluetooth device. Consistent compatibility issues have been noted with devices using certain parrott chipsets, certain automobiles with factory bluetooth including most Nissans, Volkswagons and an assortment of other devices and autos.
Q. Can you fix bluetooth so it will work with my floozengadget device?
A. No.
Q. Does the FM Radio work?
A. No, and there are no plans for FM radio support at this time.
Q. I miss HTC Sense. Can it be added to CM6?
A. No. HTC Sense is proprietary. Further, it is more than just a launcher and add on programs.
Q. But I really really really miss Sense. Can it be added to CM6?
A. No. And still - no. Yet - no.
Q. What's an ETA for the fixes and when will the ROM be finished?
A. No one gets a dime for this port, and no one works on it full time. It's a work in progress and as we make any significant breakthroughs, we'll update the ROM and post it. Sometimes I take time off from the project just to be a wise ass and beat on jznomoney. I don't know how any of this answers the question, but if it conveys an urgency to meet a schedule, then I recommend reading the answer over and over again until it doesn't.
Q. My widgets don't load or I am missing icons on the desktop or in folders.
A. The sdcard mounts late in the startup process - later than when desktop icons and widgets are loaded. This is a problem inherent in Android 2.2 and manifests itself when an application/widget is moved to the sdcard that has a presence on the Desktop. This is not a bug in this ROM, it's apps2sd in FroYo.
Q. If this is cyanogenmod, then how come it doesn't work exactly like it does on xyzphone?
A. Good question. I guess mostly because it's not an xyzphone.
Q. May I use your work and customize it and republish it?
A. My work is a small portion of this project. Ask cyanogen specifically about what you want to do and if he's okay with it, who am I to argue? Do not ever claim the work you are using as your own or fail to give cyanogen or his team credit for the project and my group credit for the device port or you will be on a lot of s-lists faster than you can hit your spacebar. I don't think cyanogenmod should be skinned up for redistribution.
Q. May I republish this ROM, giving proper credit?
A. Get permission first.
Q. Will you put out customized/skinned versions of this ROM?
A. No. This is meant to be a clean port of cyanogenmod for the HTC Aria, and nothing more. cyanogenmod is an awesome project, and I don't plan to detract from what it is in any way shape or form by customization. Once you install it, you are free to do whatever you like with it. You are of course also free to build flash-able skins and whatever mods you'd like to share.
Color me excited!
Can't Wait!... just kiddin... but not really.
Oooo exciting!!!
Cant wait to try this out!
Sent from my HTC Liberty using XDA App
Is this Froyo?
Attn1, is my f'in hero!
Omg... its here!
Sent from my HTC Liberty using XDA App
Almost broke my phone in excitement
Sent from my HTC Liberty using XDA App
am I dreaming?
nice ........ waiting waiting waiting and waiting .....
drjim said:
Is this Froyo?
Click to expand...
Click to collapse
Yes cyanogenmod 6 is based off the froyo source.
Congrats attn1!
Sent from my SAMSUNG-SGH-I897 using XDA App
Can't wait for this! Here comes my new everyday ROM.
Thanks so much attn1!!!
Sent from my HTC Liberty using XDA App
attn1 said:
wife/factory reset - YES - it's required
Click to expand...
Click to collapse
might wanna fix that
Thanks for a great effort, can't wait to try! Just curious, why is it that all non-stock ROMs that have been released so far do not have a functional camera? Is it particularly difficult to get working?
fantastic. flashing as we speak.
hi2u2 said:
might wanna fix that
Thanks for a great effort, can't wait to try! Just curious, why is it that all non-stock ROMs that have been released so far do not have a functional camera? Is it particularly difficult to get working?
Click to expand...
Click to collapse
I will like to know that also... the camera is always that thing that does not work...
hi2u2 said:
might wanna fix that
Thanks for a great effort, can't wait to try! Just curious, why is it that all non-stock ROMs that have been released so far do not have a functional camera? Is it particularly difficult to get working?
Click to expand...
Click to collapse
figures my first new bug report would be a spelling correction in my post.
This is fantastic I'm flashing right now. To those asking about the camera, I can't really answer your question, but I can input this little tidbit; On the Clean Eclair ROM, the camera was functioning, but didn't handle colors properly, everything had a blue tint to it that led to the inversing of a number of colors (mostly blues with reds and vice versa), which led to some quite interesting photographs although that's not necessarily everyones cup of tea
Also take note, not all the colors you see there are a direct result of the camera, I use CameraFX for all those shots altering the color IT applied to the picture as well, although there were things I had no control over, i.e. the lighter pictured is red with a blue button, the actual lighter is red with a blue button.
attn1 said:
figures my first new bug report would be a spelling correction in my post.
Click to expand...
Click to collapse
The "wife" thing or the camera thing? Does the camera work? Stupid question..I guess everyhting is working, right?

[ROM] CyanogenMod 7 for the Motorola Droid :: V7.1.0 (9 Oct 2011)

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 Motorola Droid, 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-Droid
Download: link
Mirror: link
MD5sum: eb53ac6d591dc7ceb8cc43f4e8dffbb0​
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!
Woot! Woot!
CM7.1 plays very nice with the aging D1.
Long time fan. Droid nightlies, and Eris unofficials before that.
Wouldn't consider a new device till at least a CM port is available.
BTW, CM7.1 also goes great with Kentucky Straight Bourbon ;-p
Sent from my Droid using xda premium
Great Work Man!
Actually just flashed this last night as soon as it came out for the OG Droid. I got my Droid 2 days ago,fixed the screen problem,rooted it with SOC,did factory data reset and flashed the CM. It is very stable and I love it! Now I'm just trying to figure out how to change the PRL,Radio,and S-off for the phone. Anyways...keep up the great work man,I support what you do fully and thanks for the great ROM's!
For the life of me, I can't get apps2ext to work (you know, where you have a second partition on your SD card and when you install apps, the files go there). It keeps telling me the SD card is blank or damaged or whatever and I can't mount it. I was told CyanogenMod had this feature built-in. Am I just completely retarded?
Sent from my un-throttled, 1.1ghz OC'd, fully flashed cricKet Moto Droid running CM7.1 using XDA Premium App
pomeroythomas said:
For the life of me, I can't get apps2ext to work (you know, where you have a second partition on your SD card and when you install apps, the files go there). It keeps telling me the SD card is blank or damaged or whatever and I can't mount it. I was told CyanogenMod had this feature built-in. Am I just completely retarded?
Sent from my un-throttled, 1.1ghz OC'd, fully flashed cricKet Moto Droid running CM7.1 using XDA Premium App
Click to expand...
Click to collapse
You are not retarded man,the Apps2SD is included in the CyanogenMod,not sure about Apps2Ext but it should work. Once you click the settings button a window should show up that has different options for Add,Edit,Manage Apps,Settings,Search,or More.Or you may click on Settings button and go to: >Settings>Applications>Manage Applications. From there you should be able to manage your apps or download the Apps2SD and manually do it. I can upload the file for you if you'd like it.Let me know bro!
So. The CM 7.1 camera app has problems closing if you use auto flash. The workaround is to use manual flash (on or off). Strange...
Sent from my Droid using XDA App
I have been running this version for the past couple of days. It has not crashed once and even maps keeps its s*it when you search for something... I am very impressed.
Love it. Made this phone come alive as did my old Eris!!! Thank you.
Zlatty said:
I have been running this version for the past couple of days. It has not crashed once and even maps keeps its s*it when you search for something... I am very impressed.
Click to expand...
Click to collapse
So, here is a random issue I have. I've paired my Droid with my head-unit. Now every time I turn on my car and activate Bluetooth, audio galaxy starts up and google music opens and starts playing. However, I just want to use Spotify. How do I disable auto music player?
Tried MIUI, unstable.
This one is much more stable, but Google maps crash randomly (without FC, it just quits and goes back to main screen).
Feel a bit sluggish compared with MIUI though. (MIUI's main launcher screen is silky smooth - even to the point of comparable to iPhone's interface), this one has slight jerkiness.
That said, so far everything else appear to be working fine.
I put ChevyNo1 kernel (LV 1100 in interactive mode). Still have issues with Google maps crashing randomly though. (I usually have cellular data turned off, so that may be the issue? I don't know).
I use CM7 on my Nook Color so the interface is more familiar to me than others.
EDIT: At this point, I am unable to use my camera. Don't know why, it was working before using this rom and this kernel. All of sudden, I am unable to use camera, camera app is force closing. I think I will try other roms and see.
Nevermind I figured it out...
maps
hpark21 said:
Tried MIUI, unstable.
This one is much more stable, but Google maps crash randomly (without FC, it just quits and goes back to main screen).
Feel a bit sluggish compared with MIUI though. (MIUI's main launcher screen is silky smooth - even to the point of comparable to iPhone's interface), this one has slight jerkiness.
That said, so far everything else appear to be working fine.
I put ChevyNo1 kernel (LV 1100 in interactive mode). Still have issues with Google maps crashing randomly though. (I usually have cellular data turned off, so that may be the issue? I don't know).
I use CM7 on my Nook Color so the interface is more familiar to me than others.
EDIT: At this point, I am unable to use my camera. Don't know why, it was working before using this rom and this kernel. All of sudden, I am unable to use camera, camera app is force closing. I think I will try other roms and see.
Click to expand...
Click to collapse
I've had the map close issue for ages now ... ever since the first v7 nightlys.
For me it happens when I try to search. Its quite annoying.
Zlatty said:
I've had the map close issue for ages now ... ever since the first v7 nightlys.
For me it happens when I try to search. Its quite annoying.
Click to expand...
Click to collapse
I am currently using latest version of Bugless Beast and it certainly is bugless beast!!
Customization is rather limited, but I would rather have a solid working phone which has less customization (I am using GO launcher anyways) than very customizable but flaky rom.
I wonder if cyanogen will update this phone to android 4.0
Hello guys!
Tell me please - are there any working kernels for OG Droid with CM7.1 to overclock CPU?
I've installed Chevys (maybe a little mistake), but after I turn off phone - it drops down CPU speed to 600mhz(

[ROM][SM-T320][CM-11.0][Unofficial] CyanogenMod 11.0 for Tab Pro 8.4 WiFi

CyanogenMod is a free, community built, aftermarket firmware distribution of Android 4.4.2 (Kitkat), 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.
Links
* Current Build: 2014-05-04
* GAPPs: gapps-2014-01-05
Source Code
* CyanogenMod: github.com/CyanogenMod
* Device specific repos in my dev thread.
XDA:DevDB Information
CyanogenMod 11.0 for MondrianWiFi (T320) [Unofficial], ROM for the Samsung Galaxy Tab Pro 12.2, 10.1, 8.4
Contributors
crpalmer
Version Information
Status: No Longer Updated
Created 2014-03-01
Last Updated 2014-05-08
Reserved
Working:
* App switch capacitive key
* Audio (speaker, headphones, VOIP)
* Auto-brightness of the display
* Bluetooth
* Camera (include camcorder and video chat)
* Display
* GPS
* IR blaster
* Lid sensor
* Removable SD card
* Rotator
* Sensors
* USB-OTG including usbdisk
* Vibrator
* Voice recognition
* WiFi
Not Working:
* Nothing!
Other:
* MX Player with H/W decoder stutters but using H/W+ decoder seems to work fine
* Has phone capabilities (which I may or may not fix depending on whether or not I try to add support for the EUR LTE edition).
Reserved
New build: 2014-03-02
High level changelog:
* Fix basic audio use cases (speaker, headset, VOIP)
Detailed changes:
Device:
852efab mondrianwifi: Add qcmediaplayer to the build
31bde97 mondrianwifi: Add custom audio_effects.conf
75678fb mondrianwifi: Improve boot speed
db0a2d5 mondrianwifi: audio: Fix basic audio use cases
55e9d3c mondrianwifi: audio: Add in our mixer_paths.xml from stock
9bab7be mondrianwifi: overlay: We don't have a menu button
Kernel:
be522ab msm: pm: bug in pc debug counters logic
97e0d73 msm: pm: print active clocks before entering into pc
ba550f8 PM / devfreq: Fix out of bounds access of transition table array
5f7c58c msm: mdss: implement overlay prepare ioctl
744352d msm: lpm_levels: return new idle level to cpuidle framework
db1e573 msm: mdss: optimize MDP pipes cleanup
cbfcc12 mondrianwifi: Fix windows newlines
d18d08f ion: system_heap: only use low gfp flags for order-0 pages
781e9dc ARM: dts: msm: lower LDO 11 minimum voltage constraint for msm8974
Great start.
Nice to see CM11 working even with it present fault mainly bluetooth & camera.
I will play around a bit longer then try a restore of my backup from CWM.
Nice not having a lot of the Samsung crapware.
Setting up cm11 now.
Any theory on why /system and /cache take so much longer to format than /data?
Please let us know what kinds of feedback / logging you'd like to get.
Ah, here's one unsolicited one: you might want to set lcd density to 320 in the build.prop - the display is a little low res in the build as first installed. I do use app settings in xposed to dial back resolution on text heavy items, but like lots of things on the homescreen
Ah, one other sensor not working - the device supports wake with a magnet, and that's not available right now. Or I don't know where to find it in CM?
roustabout said:
Setting up cm11 now.
Any theory on why /system and /cache take so much longer to format than /data?
Click to expand...
Click to collapse
I hadn't noticed, so no theory...
Please let us know what kinds of feedback / logging you'd like to get.
Click to expand...
Click to collapse
The usual. If something that is not listed under "Not Working" doesn't work let me know. If it crashes, let me know.
Provide logs and detailed instructions to reproduce any problems that you do have so that I can try to reproduce them and thereby fix them.
If something that is neither listed in the "Working" or "Not Working" category then let me know whether or not it works!
Ah, here's one unsolicited one: you might want to set lcd density to 320 in the build.prop - the display is a little low res in the build as first installed. I do use app settings in xposed to dial back resolution on text heavy items, but like lots of things on the homescreen
Click to expand...
Click to collapse
Yeah, the resolution bugs me too but I will probably not change it in the build as that forces it on everyone. It's easy enough to change yourself.
Ah, one other sensor not working - the device supports wake with a magnet, and that's not available right now. Or I don't know where to find it in CM?
Click to expand...
Click to collapse
Do you know where the magnet is for that sensor? I don't have a case that does this so I don't know how to test whether or not it's working (the rest of the sensors are working on my unreleased build but I doubt that one is).
Yes, the sensor is at about eight o'clock, about an inch from the left edge of the screen.
I saw but didn't pay attention to an error in the backup referencing .android_secure. I think I should have, as my nandroid failed to be bootable - play store and clock both crash and it looks as if the system wants to run the one time setup but can't.
I'm trying a second restore now but expect I'll need to reimage.
Something in format /system is odd. The log finishes with can't partition non mmcblock device, although it also references having created a filesystem...
New build: 2014-03-03
* Fix sensors (include autobrightness)
* Fix external sdcard
* Fix USB-OTG including usbdisk
* Fix APP_SWITCH capacitive key (which you can remap to menu in Setting >> Buttons)
crpalmer said:
New build: 2014-03-03
* Fix sensors (include autobrightness)
* Fix external sdcard
* Fix USB-OTG including usbdisk
* Fix APP_SWITCH capacitive key (which you can remap to menu in Setting >> Buttons)
Click to expand...
Click to collapse
You sir are the man.
Sent from my SM-N900T using XDA Premium 4 mobile app
I successfully got the CWM build loaded on the phone and it worked fine, then I rebooted into CWM and tried to flash this version of CM11 and I'm stuck in a boot loop that goes into Odin and says Could not do normal Boot. Any ideas?
boosting1bar said:
I successfully got the CWM build loaded on the phone and it worked fine, then I rebooted into CWM and tried to flash this version of CM11 and I'm stuck in a boot loop that goes into Odin and says Could not do normal Boot. Any ideas?
Click to expand...
Click to collapse
Did you check the md5 on the download? It's very unlikely that a download is corrupt and still flashes but it's good to double check it anyway...
Next I would try flashing it again and see if something funny happened during the flash.
If not, I guess the most expedient would be to flash the previous build.
crpalmer said:
Did you check the md5 on the download? It's very unlikely that a download is corrupt and still flashes but it's good to double check it anyway...
Next I would try flashing it again and see if something funny happened during the flash.
If not, I guess the most expedient would be to flash the previous build.
Click to expand...
Click to collapse
Yep the md5 was good. I'll pull the 03/02 build and see if that one will boot.
---------- Post added at 08:22 PM ---------- Previous post was at 08:14 PM ----------
crpalmer said:
Did you check the md5 on the download? It's very unlikely that a download is corrupt and still flashes but it's good to double check it anyway...
Next I would try flashing it again and see if something funny happened during the flash.
If not, I guess the most expedient would be to flash the previous build.
Click to expand...
Click to collapse
Interesting, the 4th try of the current build flashed and booted like nothing happened. Hot damn does this hardware fly on CM! Thanks a lot for the work you've done so far!!
boosting1bar said:
Yep the md5 was good. I'll pull the 03/02 build and see if that one will boot.
---------- Post added at 08:22 PM ---------- Previous post was at 08:14 PM ----------
Interesting, the 4th try of the current build flashed and booted like nothing happened. Hot damn does this hardware fly on CM! Thanks a lot for the work you've done so far!!
Click to expand...
Click to collapse
Glad to hear it worked. Weird that it was flaky.
And, yeah, this hardware is really great. I'm still not sure how Samsung managed to make it feel so slow and sluggish...
This rom will be darn near perfect when the rotation is fixed. Thanks for all of the hard work. Greatly appreciated.
Sent from my SM-T320 using XDA Premium 4 mobile app
Yeah, I'm excited for this, but I'm waiting on that rotation. My wife would be less than pleased with me if I put a ROM that didn't "work" on our brand new tablet.
From my Pro Tab 8.4
I changed the DPI to 400 and rotation seems to work just fine.
Sent from my SM-T320 using xda app-developers app
JaylanPHNX said:
Yeah, I'm excited for this, but I'm waiting on that rotation. My wife would be less than pleased with me if I put a ROM that didn't "work" on our brand new tablet.
From my Pro Tab 8.4
Click to expand...
Click to collapse
I know it's not mentioned in the post, but using the most recent build auto-rotate works perfect for me.
ART Runtime
Can someone please report whether the ART runtime is included in this ROM? (ART can be selected in Settings>Developer Options>Select Runtime)
bsutton said:
I know it's not mentioned in the post, but using the most recent build auto-rotate works perfect for me.
Click to expand...
Click to collapse
Weird.. I don't think it did for me, but maybe I forgot exactly when I had built it. The next build definitely should for everyone.

[ROM][UNOFFICIAL][13][N7100][Samsung Galaxy Note 2][LineageOS 20.0][ALPHA]

Code:
/*
* 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.
*
*/
Hi,
here you can find my version of LineageOS 20.0 for our Samsung Galaxy Note 2 (3G).
At first I want to thank @rINanDO, @ChronoMonochrome for all your work on these devices!
This is an alpha version, it's not finished from the LineageOS side and also not from mine.
Most of the LineageOS specific features are missing or not working yet,
please do not report bugs.
Attention:
As it looks like does the device stuck at the "Samsung Note II" screen when you boot out of TWRP,
simply touch the screen with your fingers and it will move on...
I try to find out whats going on there
If you wan't to enable the back gesture for gesture navigation, do the following:
adb shell
setprop toggle_navbar true
You can do the same to disable it.
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
Tethering via WIFI and Bluetooth
much more...
Spoiler: Whats not working
NFC
Encryption
BT audio in a phone call
Network monitoring because of missing eBPF
Maybe random reboots
Spoiler: Links
TWRP
ROM direct link
ROM Android-Filehost
ROM Mega
Spoiler: Changelog
29.09.2022
17.10.2022
26.01.2023
10.03.2023
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /system/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][13.x][N7100][ALPHA] LineageOS 20.0, ROM for the Samsung Galaxy Note 2
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 13.x T
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive
Version Information
Status: Alpha
Created 2022-09-23
Last Updated 2023-03-10
*reserved
Thank you 6405.
Please keep up the good work.
Let me try it out will come up with reviews
Just downloaded the ROM.
The new themed icons seems to work for some apps.
The battery icon on the notification bar seems broken. You can't change the style or percentage.
Languages per app screen shows no apps.
I will share my real experience after testing some more.
It seems like you forgot to upload this ROM on Adroid-Filehost.
<accidentally double post removed>
Great job. Thanks for implementation. But I can't find the device/kernel/vendor sources in you github repros. Only device for LOS18.1
Update 29.09.2022:
Fixed GPS
Tried to fix surfaceflinger crash, let's test if it worked
It's Good
Unfortunately it isn't very good at all!
Not suitable as a daily driver yet!
Even the experimental LineageOS 19.1 GO builds here much more stable.
After some weeks of trying this ROM, I like to share my experience.
I started from a clean install / clean flash.
As usual, I really appreciate that you enhance the privacy and security with your degoogled Roms.
I know this is a based on a beta release of LineageOS and this ROM is in alpha release, but I like to help you improving this ROM.
Here is a list of things that are not working or are not working as intended:
Spoiler
- A lot of random reboots. Worst part, after the reboot ,WIFI won't work. You need to reboot the device manually again in order to fix this which is a huge waste of time.
The reboots mostly happens while browsing with the Brave browser or while typing long messages. I use OpenBoard as keyboard.
- A lot of (FC) force closes while opening some apps.
I can even barely use F-droid! Session and is even as good as unusable on this ROM!
Some apps like NewPipe are usable for a while, but suddenly closes for no particular reason.
Started from a clean slate, so all apps were clean installed as well.
- Very long startup times (Samsung Galaxy Note logo, not the LineageOs splashscreen)
- One day, I could no longer use my device.
When the device was booted, a message was displayed about factory reset and it will reboot automatically. After rebooting, the same message was shown again. The only option was to format the device using TWPR an flash everything over.
Fortunately, this happened only once, but that's a big problem that shouldn't happen again!
- After previous problem I decided to give encryption a try sine I got nothing to loose after all. Encryption still doesn't work!
- 5Ghz WIFI networks don't work. It's not a router problem because I can connect other devices just fine.
Problems occurs on our corporate network and my home network as well.
- Sometimes, the screen starts flickering black on pages with some more graphical intensive tasks, such as websites with embedded video's on it. I only could trigger this in the Brave browser and Firefox Focus.
- Colour correction mode won't work and isn't even available in settings. This prevent the blue light filter from working when it's late or dark. (orange tint).
- The battery icon is broken. You can't see the battery percentage.
Even if you enable circular and percentage in icon, the battery icon won't change.
- Display settings are not saved after a reboot. (example, go to settings>display and change the icon shape to squirqle and choose a custom font. After a reboot, the icon shapes will be circles again and custom font is default font.
Besides all the negative stuff, I also have some positive feedback as well.
I was really surprised (in a positive way) to see the Aurora Store was preinstalled.
This saves me some time downloading/installing it after a clean slate.
Receiving Android 13 on this device before same brand new Galaxy A devices was already a big surprise on its own.
Some nice to gets to make the ROM even more better:
Spoiler
- Make encryption work
- Completely degoogle LineageOS to protect our privacy even more. This will saves me some time after eery update of your ROM.
I referring to removing/replacing Google's DNS (default DNS is 8.8.8.8), Removing or replacing Google's SUPL (A-GPS).
Preferable better privacy respecting DNS:
Quad9: 9.9.9.9 149.112.112.112
Cloudflare: 1.1.1.1 1.0.0.1
Adguard DNS: 94.140.14.14 94.140.15.15
Here is a blog that can help you to understand the privacy problems and how to solve them:
https://www.reddit.com/r/degoogle/comments/cldohl
My goal is not to "tweak" or making any "cool mods " to your ROM.
My goal is to make it more privacy friendly by default for people who doesn't choose to flash MicroG or GAPPS.
- Remove the VIA browser or replace it with something more privacy respecting.
After a clean install, deleting it with ADB is often one of my first steps.
Bromite, Fennec or even Brave are some better alternatives.
- Optionally, you can replace the default AOSP system webviewer with Bromite as well.
- Optionally, a preinstalled F-Droid would be nice as well.
My apologies for the overload of information.
As usual, I like to help making this ROM as good as your previous ROMs or even better!
I hope my feedback is could be useful.
wiijordends said:
Unfortunately it isn't very good at all!
Not suitable as a daily driver yet!
Even the experimental LineageOS 19.1 GO builds here much more stable.
After some weeks of trying this ROM, I like to share my experience.
I started from a clean install / clean flash.
As usual, I really appreciate that you enhance the privacy and security with your degoogled Roms.
I know this is a based on a beta release of LineageOS and this ROM is in alpha release, but I like to help you improving this ROM.
Here is a list of things that are not working or are not working as intended:
Spoiler
- A lot of random reboots. Worst part, after the reboot ,WIFI won't work. You need to reboot the device manually again in order to fix this which is a huge waste of time.
The reboots mostly happens while browsing with the Brave browser or while typing long messages. I use OpenBoard as keyboard.
- A lot of (FC) force closes while opening some apps.
I can even barely use F-droid! Session and is even as good as unusable on this ROM!
Some apps like NewPipe are usable for a while, but suddenly closes for no particular reason.
Started from a clean slate, so all apps were clean installed as well.
- Very long startup times (Samsung Galaxy Note logo, not the LineageOs splashscreen)
- One day, I could no longer use my device.
When the device was booted, a message was displayed about factory reset and it will reboot automatically. After rebooting, the same message was shown again. The only option was to format the device using TWPR an flash everything over.
Fortunately, this happened only once, but that's a big problem that shouldn't happen again!
- After previous problem I decided to give encryption a try sine I got nothing to loose after all. Encryption still doesn't work!
- 5Ghz WIFI networks don't work. It's not a router problem because I can connect other devices just fine.
Problems occurs on our corporate network and my home network as well.
- Sometimes, the screen starts flickering black on pages with some more graphical intensive tasks, such as websites with embedded video's on it. I only could trigger this in the Brave browser and Firefox Focus.
- Colour correction mode won't work and isn't even available in settings. This prevent the blue light filter from working when it's late or dark. (orange tint).
- The battery icon is broken. You can't see the battery percentage.
Even if you enable circular and percentage in icon, the battery icon won't change.
- Display settings are not saved after a reboot. (example, go to settings>display and change the icon shape to squirqle and choose a custom font. After a reboot, the icon shapes will be circles again and custom font is default font.
Besides all the negative stuff, I also have some positive feedback as well.
I was really surprised (in a positive way) to see the Aurora Store was preinstalled.
This saves me some time downloading/installing it after a clean slate.
Receiving Android 13 on this device before same brand new Galaxy A devices was already a big surprise on its own.
Some nice to gets to make the ROM even more better:
Spoiler
- Make encryption work
- Completely degoogle LineageOS to protect our privacy even more. This will saves me some time after eery update of your ROM.
I referring to removing/replacing Google's DNS (default DNS is 8.8.8.8), Removing or replacing Google's SUPL (A-GPS).
Preferable better privacy respecting DNS:
Quad9: 9.9.9.9 149.112.112.112
Cloudflare: 1.1.1.1 1.0.0.1
Adguard DNS: 94.140.14.14 94.140.15.15
Here is a blog that can help you to understand the privacy problems and how to solve them:
https://www.reddit.com/r/degoogle/comments/cldohl
My goal is not to "tweak" or making any "cool mods " to your ROM.
My goal is to make it more privacy friendly by default for people who doesn't choose to flash MicroG or GAPPS.
- Remove the VIA browser or replace it with something more privacy respecting.
After a clean install, deleting it with ADB is often one of my first steps.
Bromite, Fennec or even Brave are some better alternatives.
- Optionally, you can replace the default AOSP system webviewer with Bromite as well.
- Optionally, a preinstalled F-Droid would be nice as well.
My apologies for the overload of information.
As usual, I like to help making this ROM as good as your previous ROMs or even better!
I hope my feedback is could be useful.
Click to expand...
Click to collapse
yes you're right. But fren: Android 13 on an ancient device (more than 10 years old). And at the end: it works!
Of course not very stable, maybe as you said android 12 (ever made by html64) is better, but also android 9 by comicox works fine.
In my case: i really can't use n2 as a primary or secondary smartphone. N7100 hasn't 4g, in my country is not more usable outside your home. So i want to se what is his limit. Even if there more crash and restart. no problem for me
There is a problem with the alarm clock. After opening the clock and then alarms that have been set in the clock app I only see a grey area for a set alarm. It is just a grey box without any text. Only after I click on the entry I see the details of the alarm.
PS: Any chance you could indicate in the file names what version(alpha, beta, final) it is from your point of view? May be an _alpha, _beta_, _final at the end of the archive file? Thx again for all the hard work!
Update 17.10.2022:
Fixed tethering
Synced with LineageOS sources
Fixed most missing / broken features
Fixed hang on boot screen
Updated gps.conf for A13
Update 18.10.2022:
Fixed crash when uninstalling any app
Hello my friend,
It looks like you've been working hard, I'm glad to hear you've made progress on Lineage20's development. I hope you can solve all the bugs so that we have a very stable version to use in our daily lives.
I'm looking forward to the release for the Note 10.1 tablets.
But I understand that there is still a lot of work ahead.
But here's my respect for your work.
lineageos 20 on my device crashes when i unplug the charger it turns off when i plug it back in it comes back on
Tranvy2022 said:
lineageos 20 on my device crashes when i unplug the charger it turns off when i plug it back in it comes back on
Click to expand...
Click to collapse
Hmm strange, just tried it again on my device, it behaves correct, stops charging and wakes up, are you using a n7100 or a different model number?
I really don't see any problem here.
Hi
I try to pit a custom rom tó my gt n7100 16 gb.
The rom is ok, its work fine, bút i cant install google apps őackage, always runt to error 70 in trwp, not enough disk space. The phone has got 8-10 gb free space . What is the problem?
html6405 said:
Code:
/*
* 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.
*
*/
Hi,
here you can find my version of LineageOS 20.0 for our Samsung Galaxy Note 2 (3G).
At first I want to thank @rINanDO, @ChronoMonochrome for all your work on these devices!
This is an alpha version, it's not finished from the LineageOS side and also not from mine.
Most of the LineageOS specific features are missing or not working yet,
please do not report bugs.
Attention:
As it looks like does the device stuck at the "Samsung Note II" screen when you boot out of TWRP,
simply touch the screen with your fingers and it will move on...
I try to find out whats going on there
If you wan't to enable the back gesture for gesture navigation, do the following:
adb shell
setprop toggle_navbar true
You can do the same to disable it.
Here you can see how far everything is working for now.
Spoiler: Whats working
Boot
Audio
Bluetooth
Graphics
Cameras
Sensors
Wifi
GPS
USB
Video playback (HW/SW)
Tethering via USB
RIL
OTA-Updates
Tethering via WIFI and Bluetooth
much more...
Spoiler: Whats not working
NFC
Encryption
BT audio in a phone call
Network monitoring because of missing eBPF
Maybe random reboots
Spoiler: Links
TWRP
ROM Android-Filehost
ROM Mega
Spoiler: Changelog
29.09.2022
17.10.2022
Spoiler: How to improve GPS
You could use a gps.conf from https://app.box.com/s/w57s1v1n3hie7l5lk28i for your location and replace /vendor/etc/gps.conf.
Or you try GPS Server Optimizer app for a faster 3D fix.
For both methods you need root rights.
I would recommend to use microG instead of BitGapps,
here you can find the installation instructions:
Spoiler: microG instructions
Download Magisk 24.1 and flash it via TWRP (yes, flash the APK file), reboot
Open Magisk and update the App (and do a reboot if it's asking)
Enable Zygisk in Magisk
Download and install microG installer in the Magisk manager, reboot
Download and install safetynet-fix in the Magisk manager, reboot
Check with a safetynet checker app and you should pass
Do you like my work?
Than you can simply hit the thanks button and consider to spend me a coffee or a beer,
I'm doing this in my free time and it also costs a lot of money to buy hardware.
donate
Wanna improve your sound configs, control your charging current and more?
Now you can use my app to access all boeffla configurations, there will follow more functions.
Exynos4 Kernel Manager - Apps on Google Play
This app provides Boeffla sound control and other kernel + charging tweaks
play.google.com
Spoiler: How to install it?
Instructions
XDA:DevDB Information
[ROM][13.x][N7100][ALPHA] LineageOS 20.0, ROM for the Samsung Galaxy Note 2
Contributors
html6405
Source Code: https://github.com/html6405
ROM OS Version: 13.x T
ROM Kernel: Linux 3.4.x
ROM Firmware Required: TWRP 3.5.2
Based On: LineageOS
Selinux: permissive
Version Information
Status: Alpha
Created 2022-09-23
Last Updated 2022-10-17
Click to expand...
Click to collapse
Say what ? Did I miss this ? Big Up HTML !!!!!
stefannn said:
What is the problem?
Click to expand...
Click to collapse
The problem ist the free space of the system partition,
I've never tested gapps on this ROM and will not recommend them.
But if you wan't to install them you maybe have to expand the system partition before (with parted).
Or try to find a smaller package.

Development [ROM][Official][Weekly] LineageOS 20 for Edge S / Moto G100

LineageOS is a free, community-built, aftermarket firmware distribution of Android 13, 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.
*
*/
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. You will need to provide your own Google Applications package (gapps). 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. Your changelog is whatever was merged into gerrit.
Important information:
This thread is for LineageOS 20 builds for Edge S / Moto G100. The following will not be supported here:
Custom kernels
Mods
Xposed
We don't support Xposed and any logcat which includes an Xposed module will be ignored. You're kindly invited to not report bugs if you:
Flashed a custom kernel
Installed or did mods from untrusted sources
Modified system files
Installation:
https://wiki.lineageos.org/devices/nio/install
Notice on SafetyNet:
As announced in the charter, LineageOS does not ship any hacks to help you bypass SafetyNet. The Universal SafetyNet Fix (USNF) Magisk module is a popular 3rd-party choice to workaround SafetyNet on custom ROMs. However, USNF is not sufficient to bypass SafetyNet on LineageOS, because we track the latest Android security patches while SafetyNet fails if the underlying security patch level (SPL) doesn't match stock.
To workaround this issue, I created a simple Magisk module to spoof SPL, which can be downloaded at https://github.com/MoetaYuko/spoof-spl/releases. Activating both USNF and spoof-spl should enable you to bypass SafetyNet checks. Noting that this is provided for convenience and NOT an official LineageOS solution.
Source code:
https://github.com/lineageos
Credits:
LineageOS Team & Contributors
Code Aurora Forum
Special thanks to Electimon, this work is heavily based on his prior ones.
......
Changelog & Download:
2022/10/7 initial release:​https://drive.yuko.moe/d/E5/Android/nio/lineage-20/lineage-20.0-20221006-UNOFFICIAL-nio.zip​2022/11/4:​https://drive.yuko.moe/d/E5/Android/nio/lineage-20/lineage-20.0-20221104-UNOFFICIAL-nio.zip​
Sync latest source
Fix wifi display
Reduce auto brightness latency
Other minor fixes
This is supposed to be the last custom build before official release
2023/1/2 and later:​https://download.lineageos.org/nio​
Ok. I upgrade from 19.1 to 20.0 and everything work exelent on this moment.
sp6ina said:
Ok. I upgrade from 19.1 to 20.0 and everything work exelent on this moment.
Click to expand...
Click to collapse
Dirty flash?!?!
@dianlujitao , did you use test keys or can I upgrade after a clean install of your build to official 20.0 when it is coming out? Probably I will just do a clean install then, but good to know
Yes. Dirty flash.
Moto-J said:
@dianlujitao , did you use test keys or can I upgrade after a clean install of your build to official 20.0 when it is coming out? Probably I will just do a clean install then, but good to know
Click to expand...
Click to collapse
Okay, installed 20.0 myself for test and indeed other build signature.
Great build, everything seems to work, no issues so far.
Dirty flash probably will work as @sp6ina mentioned, though I would recommend a clean flash always when you update to a mayor new version.
Moto-J said:
Dirty flash?!?!
@dianlujitao , did you use test keys or can I upgrade after a clean install of your build to official 20.0 when it is coming out? Probably I will just do a clean install then, but good to know
Click to expand...
Click to collapse
I personally don't use officially signed builds so can't tell.
Really excited for this, thanks @dianlujitao !
I do hope the echo/noise cancellation bug with speakerphone is fixed with the upcoming official release, as I'm still stuck on stock because of it being broken in 19.1...
Some small issues here, further very stable build:
1. USB file transfer seems not to work, though PTP is (phone not showing up in explorer);
Edit: solved this by installing "Mobile universal MTP USB device" driver and now XT2125-4 is recognised ;-)
No idea now if the reason was the LOS20 install, though when it happenes, you know what to do.
So: Portable Devices - Default MTP Device - MTP USB Device solved it.
2. Some app settings seems to reset after reboot like battery setting restricted
That's it for the moment, looking forward for the next build! ;-)
I modified my phone to 16gb of RAM, but the system can't fully utilize the memory. Even though continuous use can use up to 80 percent of the memory, there are still a lot of applications that get killed in the background after a while.
The number of apps running in the background is not as good as the 12gb pixel.
Is there any possiblity to improve it?
@dianlujitao
Do you plan new release of LineagoOS 20 ?
I know, newer ask about release time but... you know
noahhhh said:
I modified my phone to 16gb of RAM, but the system can't fully utilize the memory. Even though continuous use can use up to 80 percent of the memory, there are still a lot of applications that get killed in the background after a while.
The number of apps running in the background is not as good as the 12gb pixel.
Is there any possiblity to improve it?
Click to expand...
Click to collapse
GitHub - kerneltoast/simple_lmk: A simple low memory killer kernel driver for Android devices. Pick from the branch that corresponds to your kernel version.
A simple low memory killer kernel driver for Android devices. Pick from the branch that corresponds to your kernel version. - GitHub - kerneltoast/simple_lmk: A simple low memory killer kernel driv...
github.com
NFC, gpay?
I love lineageos, but I really need my camera. You essentially discard your 64MP camera when you flash a custom ROM. Is there any app that has the option to use your ULTRARES cam? Open camera and all the others go up to 16MP. Has lineage found a way to make use of all the cams / options? Also, has an option to remap the bixby button been included?
I noticed same volume issues like on version 19.1.
e.g. can't control volume when on speaker, can't change volume when using headset (wired) in signal, wire....,adds stronger echo for the other side
Can anyone confirm?
Latest is working great here; no issues found till now. Ready for official I think
Great work @dianlujitao !
nahoda said:
I noticed same volume issues like on version 19.1.
e.g. can't control volume when on speaker, can't change volume when using headset (wired) in signal, wire....,adds stronger echo for the other side
Can anyone confirm?
Click to expand...
Click to collapse
I confirm, same issues of 19.1. Echo on the other side is a real pain
Strange thing happened .. i was able to control volume during last wire call I made (both when on speaker and with headset). I changed nothing except installed magisk. But that shouldn't matter. I'm confused.
nahoda said:
Strange thing happened .. i was able to control volume during last wire call I made (both when on speaker and with headset). I changed nothing except installed magisk. But that shouldn't matter. I'm confused.
Click to expand...
Click to collapse
Happens to me too.
This is what I experienced:
- Call volume cannot really be changed from the settings app (you can slide it, but nothing will change)
- Most times you cannot control call volume during a call. Sometimes, you can, but it's rare.
However, even if I slide the call volume to the minimum (if I can do it, which is rare) my caller still hears echo. The only workaround is using a pair of headphones (or stock rom). It's really sad that all custom roms have this problem and nobody seems to be able to figure out how to fix it. I tried to contact a few developers of custom ROMs to see how I can help but so far I got 0 answers...
Demax55 said:
However, even if I slide the call volume to the minimum (if I can do it, which is rare) my caller still hears echo. The only workaround is using a pair of headphones (or stock rom). It's really sad that all custom roms have this problem and nobody seems to be able to figure out how to fix it. I tried to contact a few developers of custom ROMs to see how I can help but so far I got 0 answers...
Click to expand...
Click to collapse
Thanks for your involvement. It's unfortunate that noone can track the cause down.
I also noticed the echo is not present with headphones, tho if it's headset with mic it has echo.
I tried to experiment when i was still on 19.1 to replace sound related xml files with files from stock rom (i think from vendor fs), it did't help much, but headset behaved as headphones without mic, just using phone mic and echo wasn't present in such case.
This morning I was looking at the build server sites etc... to find some info about the status of LOS20. Is there a place where we can find info about the progress (not the changelog) and planning of it?
Just wondering ;-)

Categories

Resources