To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Website:
http://androidarmv6.github.io/
Source code:
https://github.com/androidarmv6
You can watch development as it progresses, or you can sign in and participate here:
http://review.androidarmv6.org/#/q/status:merged
STATUS: NOT BOOTING
JENKINS SHUT DOWN
NO DOWNLOADS
sent from my towelrooted LG L34C using daishi4u bumped twrp 2.8.3.0 and bumped key-boot-recovery kernel
...as he looked back on the sleeping giants, exhausted from their long journey, the wizard Androidmeda new that he had taught them all that he could, and they had all that they needed. But he also knew that they would never be able to survive crossing the mountains into the new land. Only their child would be able...
Well I guess this is it my brothers. Seems that all has been tried, and CM-12 will not be released for armv6 devices. But many thanks to our devs for trying. It's been a long run. Amazing, just amazing.
ibub said:
To my brothers (you know who you are)
Long, long ago...
A small pet dinosaur was left, abandoned and alone. His keepers, it seemed, had more interest in newer, more capable pets. But he eventually met with other dinosaurs, also abandoned, and a man named hephappy...
The purpose of this thread is two-fold, I think. It is meant to be a venue for androidarmv6 (team) ,as most of their development is done off- site. It is also meant to be a place for hard core dinosaur lovers to test this work, and add to it as development proceeds. As androidarmv6 has brought us, the p500 community, through to working CM- 11, now we will start a new chapter, namely CM- 12. At the time of this posting, there have been several successful builds for the p500. But none are successfully booting, as yet.
I can't stress enough that most of this work is experimental, as the newer source code is being adapted to work on these devices. So unless you are okay with a possibly bricked (unusable) phone, don't flash any of these ROMs. Also, I do not have any responsibility or liability in the case that you should damage your phone by flashing any of this firmware. Also, your warranty will be voided. And I do not represent, and am not affiliated with androidarmv6. That said... YOU HAVE BEEN WARNED.
Source code:
https://github.com/androidarmv6
ROMs:
http://jenkins.androidarmv6.org
sent from my towelrooted LG L34C using tapatalk
Click to expand...
Click to collapse
Congrats! Nice preface wording, bro! :good:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Dovidhalevi said:
Great! and thanks.
I have not been using cm-11. Omni runs better and seems!! to have fewer bugs. Problem with cm is that when newer comes along, older bugs are left there. I guess we all prefer to play with the latest and greatest so not really complaining. My real problem with cm-11 is the special recoveries needed for it.
I would like to try cm-12 builds, but want to be able to get back to the omnirom. How do I get around the recovery changes (would be nice to have a cwm or twrp that asks on bootup: Want TSL? Switch system and data? But for now, I do not want to lose my alternatives or brick the phone.
How to proceed?
BTW: Link points to end-user builds (cm-11). We'll get there.
Click to expand...
Click to collapse
Thanks, link updated to View/All.
sent from my towelrooted LG L34C using tapatalk
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
D3oDex3D_AyusH said:
This is great @ibub !
Thanks for taking the initiative of building CM12 for this device, which never seems to grow old.....
The androidarmv6 team is just awesome! Keep up the gr8 work! It's always appreciated!
Waiting for it to boot for now...
Click to expand...
Click to collapse
Just to be clear, this is not my work. Androidarmv6 team (mainly androidmeda for p500) compiles these ROMs. Thanks belong to them (him).
sent from my towelrooted LG L34C using tapatalk
Wut? ART isn't compatible with ARMv6, AFAIK.
Casserole said:
Wut? ART isn't compatible with ARMv6, AFAIK.
Click to expand...
Click to collapse
We shall soon see.
sent from my towelrooted LG L34C using tapatalk
CyanogenMod announces official CM12 Nightlies!
http://phandroid.com/2015/01/05/cyanogenmod-cm12-nightlies/
Do not even expect P500 on the list!
EDIT:
CyanogenMod 12 nightlies now available for 31 devices, based on Android 5.0.1 Lollipop (LRX22C). LG Optimus One is out of the list to be sure
http://blog.gsmarena.com/cyanogenmo...able-31-devices-based-android-5-0-1-lollipop/
While in other hand, our devs are working to port experimentally newer version of CM12 (Android 5.0.2 LRX22G) on armv6 obsolete devices, though! :good:
You can look at development of android_art as it progresses here:
http://review.androidarmv6.org/#/q/status:merged
and here:
http://review.androidarmv6.org/#/c/7676/
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
xu3sno said:
Who dares (try this on p500) win!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1308/
http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150108-EXPERIMENTAL-p500.zip
Sent from my HM 1SW using XDA Free mobile app
Click to expand...
Click to collapse
Trimmed>>Flashed>>Stuck at CM bootlogo
CCXAlex said:
Trimmed>>Flashed>>Stuck at CM bootlogo
Click to expand...
Click to collapse
+1K
GERRIT_CHANGES: 7676 7748 7693 7651 7751 7792
Code:
7676: * runtime : make entrypoints ARM; if the target arch is lower than
armv7, set armv6.
* compiler: add a new define: ARM_MODE_WORKAROUND, enable it if
the target cpu is arm11. Use ARM assembler and replace
Thumb{1-2} opcodes with ARM ones. Update some code to
support new opcodes
NOTE: kArm is not implemented, probably it use to work only in
portable mode.
7748: Compatibility work around for bad graphics driver dependency
7693: legacy OMX: squashed commit for legacy OMX support for LP
7651: Revert "Revert "Turn on BLE, GATT, and SMP of Bluetooth stack""
7751: msm7x27-common: Initial cm-12 bringup
7792: jemalloc: Force gcc for atomic functions
GCC built-in functions provide advanced things like prefetch, expected, synchronization...
Bootloog attached.
It seems bootloop's culprit is regarding with dynamic shared libraries (lib*.so) which must be fixed first.
It does not work on any device arvm6.
Link
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Also, a reminder of some things you shouldn't do (now or ever): don't ask for ETAs, don't spam the dev thread, and don't PM me asking for information that isn't on a public post.
There are many things that need to be fixed for armv6 devices. I've sorted out the major issues specific to Broadcom hardware, but there are more important issues that need solving for ARMv6 devices in general that are being working on by several people (assembly errors, ART compatibility, build system integration, etc.). It's going to take time. Thanks for your understanding.
Click to expand...
Click to collapse
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
xu3sno said:
Build cm_p500-userdebug-cm-12.0 (Jan 11, 2015 9:45:30 PM)
Androidmeda built it for testing via Jenkins, if you dare to waste your time!
http://jenkins.androidarmv6.org/view/Developers/job/cm-experimental/1311/
ROM: http://jenkins.androidarmv6.org/vie.../archive/cm-12-20150111-EXPERIMENTAL-p500.zip
Click to expand...
Click to collapse
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Any PlayStore said:
If it works on s5360 it will also work on the P500. But this time it does not work perfectly on any device armv6. I will follow up if it worked on my s5360 will report over here.
Thanks for the update by @xu3sno
Click to expand...
Click to collapse
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Quote:
A reminder: unannounced experimental builds that you may see on Jenkins are made by and for developers alone, and are definitely not suitable to be flashed by users. The cm12 totoro build from today doesn't install or boot, and I expect many future builds will be the same, so don't waste your time with it.
Click to expand...
Click to collapse
Yes, yes, we know or should know. But, hey, who does not want to be the first to see this play? The only reason I am staying off is because of the CM tricks with switching system and data partitions meaning recoveries are not compatible.
Anyway, diehards within the CM universe, once in that bootloop if ART had indeed done its thing, check remaining system space and contents of those /system/app/... folders. My (un-) educated guess is that this may become the big problem.
xu3sno said:
@Any PlayStore
also @CCXAlex (may be you have luck to try it, but I doubt )
Even Any PlayStore has quoted previously, just to satisfy my curiosity, insisted to install cm12-20150111_EXPERIMENTAL-p500.
Trimmed > clean installed > rebooted > boot loop As previous attempt, it seems lib*.so need to be fixed (?)
Don't know it's wasting my time or not
Click to expand...
Click to collapse
I also attempted to install this. Initially my trimming method seems to have broken update binary, so flash failed. Next installed full ROM (/system =189MB) using @HardLight twrp 2.7.0.0 TLS (successfully flashed). Stuck at boot animation. No log (flashing while driving).
sent from my towelrooted LG L34C using tapatalk
Related
This thread is intended for developers and others who can contribute to the project
If you think you can contribute, please do so
Standard disclaimer:
I am not responsible if anything happens to your device
Status:
Device specific build of Ubuntu's minimal cm10.1 build ready
Ready for flashing
Working:
Touch screen
ADB
Browser (Although no net access yet)
You can browse and get a feel of the entire OS, including the homescreen (unity desktop), multitasking (the cool new way to switch between apps), etc.
Since it is a preview, many apps are dummy apps.
Screenshots:
Check them out here
Video:
Here is a video of the fresh new OS in action on the O2x made by JordanRulz
Download links:
Ubuntu touch preview (raring ringtail)
Current build of Ubuntu-CM10.1 (old bootloader)
New bootloader build by delaya73:
cm-10.1-20130604-UNOFFICIAL-p990.zip
Older Ubuntu phone quantal image
older build 2 of Ubuntu-CM10.1 by delaya73
older build 1 of Ubuntu-CM10.1 by delaya73 for the new bootloader
TWRP latest version is recommended (CWM 6.x may work too)
Note:
The raring/quantal image is large, but thankfully gets installed on the data partition, thus saving our small system partition the burden
Source:
Ubuntu-cm10 source
Building instructions:
Building instructions are similar to building CM10 (refer Raum's guide) till repo sync (instead of official cm10 repo, use above source during repo init)
Dont forget to add device props in "local_manifests" (local_manifest.xml is deprecated). Add the following in local_manifests:
Code:
(Taken from Raum's guide, thanks to him)
After syncing the repo,
1. cd device/lge/p990, connect your device running cm10.1 with usb debugging on, and then ./extract-files.sh
2. In device/lge/p990/fstab.p990, remove "nosuid" from data partition
3. In kernel/lge/star/arch/arm/configs, in cyanogenmod_p990_defconfig, add the following:
Code:
CONFIG_SYSVIPC=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_DEVTMPFS=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
CONFIG_FSNOTIFY=y
CONFIG_DNOTIFY=y
CONFIG_INOTIFY_USER=y
CONFIG_FANOTIFY=y
CONFIG_FANOTIFY_ACCESS_PERMISSIONS=y
CONFIG_FSNOTIFY=y
CONFIG_SWAP=y
# CONFIG_ANDROID_PARANOID_NETWORK is not set
4. Go to ubuntu folder inside your source folder and do
Code:
bzr branch lp:phablet-extras/libhybris hybris
bzr branch lp:platform-api platform-api
If you didnt have bzr, get it first using
Code:
sudo apt-get install bzr
Now you can build. This build would be for the old bootloader. For the new one, make these changes said by pengus77 here
Flashing instructions:
1. Make a full wipe (wipe data + format /system)
2. Flash the current build and raring/quantal image
Then flash this afterflash.zip
3. Reboot
Credits:
Ubuntu dev team (Canonical)
Ricardo and the rest of the CM team
delaya73 for the new bootloader build
pengus77 for bringing cm10 to the new bootloader
Adam77Root for helping find the missing components stopping it from booting
All other contributors
AW: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
You rock man!
Gesendet von meinem LGP990 mit CM10.
Good luck with your job, Buddy, and Congratulations for all your interest/performance for our machines!
Regards.:good:
Thnx, I downloading, after a try, I will post some feedback
R: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
Can i have some screenshot?
Sent from my LG-P990 using xda app-developers app
rugglez said:
"...If you think you can contribute, please do so ..."
Click to expand...
Click to collapse
I have not had time to install this ROM ... I have been testing other, but lack little longer to do so!
Once you have news post here the results.
Thank you all for the effort made
Thank you man you're doing a really good job
Very good job rugglez bro. cant wait for bootable version to test it on my self
Well, I tried to make some tests to see if he could complete the boot ... unfortunately without success after six or seven attempts.
Enough for today testing, hahahaha! ...
So finally your Repo synced! I've left Hope here! And yea, Rugglez Bhai, you are great! )
rugglez said:
This thread is intended for developers and others who can contribute to the project
If you think you can contribute, please do so
For now, this is only for the new bootloader. If the project is successful, it would be made available on the old one as well
Standard disclaimer:
I am not responsible if anything happens to your device
Status:
Device specific build of Ubuntu's minimal cm10.1 build ready
Ready for flashing
Does not complete the boot yet
Download links:
Current build of Ubuntu-CM10.1
Ubuntu kernel for O2x
Ubuntu phone quantal image
TWRP latest version is recommended (CWM 6.x may work too)
Instructions:
1. Make a full wipe (wipe data + format /system)
2. Flash the current build, Ubuntu_kernel and quantal image
3. Reboot
Note:
The quantal image is large, but thankfully gets installed on the data partition, thus saving our small system partition the burden
To do:
There is no "logcat" in Ubuntu (may be some other way to debug), so need another way to look at what is preventing the boot
Credits:
Ubuntu dev team (Canonical)
CM team
All other contributors
Click to expand...
Click to collapse
have u tried dmsg/kmsg?
how did u get a bootanimation on there ?, my nexus 7 with ubuntu phone os, dont have one, on the nexus 7 there is only a black screen for a seconds then it boots up
Re: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
Never got around to syncing myself, I'm a bit confused regarding the post, so is it usable?
Sent from my LG-P990 using xda app-developers app
JordanRulz said:
have u tried dmsg/kmsg?
Click to expand...
Click to collapse
Will try that today. Not sure if ill get time, but if you could also have a look, it would be great. Saw that you have some experience with this
FettleifIsMyUserName said:
how did u get a bootanimation on there ?, my nexus 7 with ubuntu phone os, dont have one, on the nexus 7 there is only a black screen for a seconds then it boots up
Click to expand...
Click to collapse
Boot animation comes from the Ubuntu-cm10.1 build and is the default cm10 boot animation. Since your tablet's Ubuntu image was released directly by canonical, they must have removed the cm10 boot animation before releasing it
Neefy said:
Never got around to syncing myself, I'm a bit confused regarding the post, so is it usable?
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
If you read the first post, it's written there that it does not complete the boot yet, still a WIP.
The reason I posted was that if more contributors join in, more expertise, more time, better debugging and much higher chance of project success
Jishnu Sur said:
So finally your Repo synced! I've left Hope here! And yea, Rugglez Bhai, you are great! )
Click to expand...
Click to collapse
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
After watching some vids about this OS, it trully have a great potential. gonna watch this thread closely for progress
Re: [DEV][WIP] Porting Ubuntu Phone for LG Optimus 2x
rugglez said:
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
Click to expand...
Click to collapse
Nice to know that the team is joining up and viewing to do great things
Great going guys
O2X with Magical ICS ROM and magnificent kernels from my buddies
rugglez said:
Will try that today. Not sure if ill get time, but if you could also have a look, it would be great. Saw that you have some experience with this
Boot animation comes from the Ubuntu-cm10.1 build and is the default cm10 boot animation. Since your tablet's Ubuntu image was released directly by canonical, they must have removed the cm10 boot animation before releasing it
If you read the first post, it's written there that it does not complete the boot yet, still a WIP.
The reason I posted was that if more contributors join in, more expertise, more time, better debugging and much higher chance of project success
Thanks
Come online later, I'll help you fix that issue. Install and keep team viewer ready
Click to expand...
Click to collapse
M always ready!!!!!!!!! =D
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
jasjeev4 said:
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
Click to expand...
Click to collapse
......and so on...!...
jasjeev4 said:
The Credits list looks too small.
Maybe you can add Ricardo Cerqueira (for ahem) and TonyP for porting TWRP.
Click to expand...
Click to collapse
Ricardo is always a name in every project of the O2x, and he is a part of the CM team, in case you didnt know
But thanks for the reminder, I explicitly specified his name too now, deserves so much credit for bringing CM10 to our device.
Tonyp is a great contributor and we are thankful for all his work. But this is a ROM, and TWRP is a recovery used to flash a ROM, they have non-overlapping work. What I mean is, this ROM doesnt use TWRP's work, rather it can be flashed in TWRP or CWM6.
By your logic, Koushik Datta (developer of CWM and one of the best android devs) should be included in every ROM's credits here. Also, creators of USB, personal computers, internet, world wide web, which are also tools used in the process of flashing it.
(No offense meant to any of the above, they are all revolutionary people whom I greatly respect)
My point is, if I am using someone's work in this project/ROM, thats the person whose name goes in credits, not the one who is creating the tools to install it.
It's better if the discussion doesnt go further about this off-topic thing, if you find that I have used anyone's work in this ROM and not given credits, please let me know, thanks
Let's try to make Ubuntu Phone OS boot on our phone. Thats the priority here. Didn't get much time today, got college this week too, will see if I get time to work on it soon
[SIZE=+1]CM11 for LG L90 LG-D415[/SIZE]
Ok guys and gals... I must first state that this is not my original work. The CM11 base I'm building off of is all due to the hard work and efforts of @Quarx. His ROM is located here for devices other than the LG-D415.
This thread was created to assist @Quarx by not littering his thread with posts for LG-D415 devices. He doesn't own a D415, but I do :silly:
With that said...
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.
*/
[SIZE=+1]To use this ROM you MUST have an unlocked bootloader[/SIZE]
All specs with this ROM are the same as the specs with @Quarx ROM minus the fact that this ROM is built specifically for D415 devices
What's working
Bluetooth
Calls
Front camera
GPS
Mobile Data
Rear Camera
Superb battery life
WIFI
Most everything else
What's NOT working or working correctly
CM Updater ( Until I figure out how to implement my own )
Video recording ( front/rear camera. Works for some, not for others )
Video playback ( Works for some, not for others )
IR
LG Knock Code ( Double tap to wake )
Credits located in post #2
Changelog located in post #3
Download links are located in post #4
Source links are located in post #5
Installation
Boot to recovery ( Custom recovery required )
Wipe cache ( only required on first installation )
Wipe Dalvik cache ( only required on first installation )
Format /system and optionally /data ( Only necessary if coming from stock or a different ROM )
Install ROM
Install GApps
XDA:DevDB Information
CyanogenMod 11 for LG Optimus L90 ( LG-D415 ), ROM for the LG Optimus L90
Contributors
shinobisoft
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Beta
Created 2014-10-15
Last Updated 2014-12-17
Credits and Thanks
Credits
@Quarx - For getting everything started for developing for the LG L90
@CyanogenMod - For CM11 obviously
@k2wl - For assisting with tips/hints/suggestions
@demonslayer12349 - For assisting with tips/hints/suggestions
@shoxxy - For Philz-Touch recovery for our devices. Also for helping "behind the scenes"
Very Special Thanks
@jran0880 - For his donation of $50.00
Changelogs
12/02/2014
No changes to note on my end. View CM's changelog for any changes/updates.
10/22/2014
Removed NFC again
Removed FM Radio again
There may be some OS changes thanks to the CM team. See their changelog for changes.
SELinux is still disabled in this build. Device doesn't seem to like it when it's enabled. LOL...
Something else to figure out
10/07/2014
Changed kernel configs and dtbs from W7_TMO_US to W7_OPEN_CIS. My first few builds were built using W7_OPEN_CIS. Seems to be fewer issues with those ROMs than my most recent.
Re-enabled NFC. I'm starting to think it does exist on the device.
Re-enabled FM. Strangley I can at least hear static now. So the hardware may actually be there.
Any other changes would be OS related and would be noted by CM in their changelog.
Enabled the "Quick Key", the button above volume keys, to wake the display.
10/04/2014
Removed most NFC related stuff. D415 doesn't have NFC
Removed FM Radio.apk. D415 doesn't have FM receiver
FIX - Correct camera drivers now load on device start up
FIX - Video playback drivers
Too many other changes over the last month to begin to try and remember. LOL
My last sync with CM may have had some fixes incorporated. About a week ago
09/10/2014 - There have been no real "changes" in any of my builds besides editing some config files and adding files to fully specify the device as a w7 device and not a w7ds device. The D415 is not a dual sim device which I believe was part of the conflict between @Quarx builds and the D415 devices. So with the 09/10 build as far as I have been able to determine, everything about the build now identifies the device as a w7 device.
Downloads
Newest build: 2014-12-02 Mirror: 2014-12-02
Previous builds:
2014-10-22 Mirror: 2014-10-22
2014-10-07 Mirror: 2014-10-07
2014-10-04
2014-09-10
2014-09-07
2014-09-04GApps: http://forum.xda-developers.com/showthread.php?t=2397942
Use the link above for PA-GApps for the moment. I will put together a GApps package eventually. LOL :silly:
Recoveries: ( flash with fastboot, an app like Flashify, or my LG L90 Utilities )
CWM 6.0.5.1 ( Swipe up/down to scroll. Swipe left to go back, Swipe right to select ) Factory Reset: DISABLED
Philz-Touch 6.57.5 ( Thanks to @shoxxy )
The TWRP 2.7.1.0 package attached to this post is flashable via recovery.
Sources
GitHub Sources
Device: https://github.com/shinobisoft/android_device_lge_w7
Kernel: https://github.com/shinobisoft/android_kernel_lge_msm8226
AV Frameworks: https://github.com/shinobisoft/android_frameworks_av
LG Proprietary blobs: https://github.com/shinobisoft/vendor_lge_proprietary
I must stress again that these works are based off of the works of @Quarx - [Rom][DEV][4.4.4] CyanogenMod 11 for LG L90
Awesome! Looking forward to continued development ...just curious anything fixed from the 9/4 build to the 9/7 build?
Sent from my LG-D415 using Tapatalk
slamdunksaliby said:
Awesome! Looking forward to continued development ...just curious anything fixed from the 9/4 build to the 9/7 build?
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
Probably not. I've only been building with my fixes on top of @Quarx sources on GitHub. I'm still trying to get everything of mine over to GitHub at the moment. I unfortunately have a full time job so I don't have a ton of free time. The weekends are usually the only free time I have. I overslept today and decided to play hookey for the rest of the day. LOL. Imma bad bad boy LMAO.
When I get settled in to GitHub and have a chance to really check out the source code, I'll then see what I can do.
shinobisoft said:
Probably not. I've only been building with my fixes on top of @Quarx sources on GitHub. I'm still trying to get everything of mine over to GitHub at the moment. I unfortunately have a full time job so I don't have a ton of free time. The weekends are usually the only free time I have. I overslept today and decided to play hookey for the rest of the day. LOL. Imma bad bad boy LMAO.
When I get settled in to GitHub and have a chance to really check out the source code, I'll then see what I can do.
Click to expand...
Click to collapse
Haha no worries thanks so much
Sent from my LG-D415 using Tapatalk
Nice thing to see coming here tonight!!!! You're the best![emoji2] [emoji4] [emoji2]
Sent from my LG-D415 using Tapatalk
shinobisoft said:
Probably not. I've only been building with my fixes on top of @Quarx sources on GitHub. I'm still trying to get everything of mine over to GitHub at the moment. I unfortunately have a full time job so I don't have a ton of free time. The weekends are usually the only free time I have. I overslept today and decided to play hookey for the rest of the day. LOL. Imma bad bad boy LMAO.
When I get settled in to GitHub and have a chance to really check out the source code, I'll then see what I can do.
Click to expand...
Click to collapse
Hey bro well i found your repo i was wondering are you going to set it up to where their will be your own device tree kernel etc? I also have d415 and would like to use this as a base and see what i can do to help get some things working/test and share.
I have built from the most recent source via Quarx repo however it still has all the issues with wifi, gps, and camera some of which you have gotten to work, may I ask what you altered to get those working?
toxinburn said:
Hey bro well i found your repo i was wondering are you going to set it up to where their will be your own device tree kernel etc? I also have d415 and would like to use this as a base and see what i can do to help get some things working/test and share.
Click to expand...
Click to collapse
Eventually. Don't fork anything yet. I've gotta change a few things at github.
Sent from my LG-D415 using Tapatalk
shinobisoft said:
Eventually. Don't fork anything yet. I've gotta change a few things at github.
Sent from my LG-D415 using Tapatalk
Click to expand...
Click to collapse
heheh of course i already did but no worries.
thanks! This is so much faster than stock ROM. Stock ROM used to redraw UI every time i stay in an app for a bit.
toxinburn said:
... may I ask what you altered to get those working?
Click to expand...
Click to collapse
Sure ,you can ask but I'll never tell. LOL. Just kidding.
It's actually kinda long winded tho and I'm not sure I can explain exactly what needs to be done. It will be easier for me to fix my GitHub and have you fork from it than to explain everything in enough detail to understand what needs to be done.
I'm just getting in from work. Hopefully I can have my GitHub repaired in the next couple hours
Just want to say thanks to you (for the D415 version) as well as Quarx for supporting this phone! I must say this L90, even with the stock ROM, was the best $50 I ever spent. I am still discovering features on this phone that I had no idea were even on here, such as NFC, infrared remote, and even the flashlight (yeah, I really thought this didn't have a camera flash until I launched the Torch app). But now to see this phone with CM11 just makes it that much better of a deal. Other than the front camera currently not working, which is fine for me since I never use it anyway, this ROM is absolutely fantastic and is twice as fast as the stock LG ROM.
Keep up the good development work! If you have any experimental ROMs, kernels, or any other mods, please let me know and I will be happy to test them. This is a great little phone for the price tag, and I'd love to see the development blossom for this thing.
Sent from my LG-D415 using XDA Free mobile app
1) Happy Birthday to me :silly:
2) I'm doing a test build now to see if I managed to fix what I broke last night. LOL
3) If #2 is successful, then I'll upload my kernel sources to GitHub for those who are interested. Then I'll also post a link in the OP to my GitHub for CM11.
Cross y'alls fingers and toes! No eyes please!!! LMAO...
shinobisoft said:
1) Happy Birthday to me :silly:
2) I'm doing a test build now to see if I managed to fix what I broke last night. LOL
3) If #2 is successful, then I'll upload my kernel sources to GitHub for those who are interested. Then I'll also post a link in the OP to my GitHub for CM11.
Cross y'alls fingers and toes! No eyes please!!! LMAO...
Click to expand...
Click to collapse
happy birthday !!!!have a great day!!!
shinobisoft said:
1) Happy Birthday to me :silly:
2) I'm doing a test build now to see if I managed to fix what I broke last night. LOL
3) If #2 is successful, then I'll upload my kernel sources to GitHub for those who are interested. Then I'll also post a link in the OP to my GitHub for CM11.
Cross y'alls fingers and toes! No eyes please!!! LMAO...
Click to expand...
Click to collapse
Sorry for OT
HAPPY B-DAY !!!! stay healthy
Ok. I got it to build. It flashes and boots just fine. But... I'm having one heck of a time pushing my kernel sources to GitHub.
The kernel sources are where most of the changes/additions I've made are. Without them the rest of the project is useless. LOL. I'm not sure if the issue is my wifi adapter or the wifi router I'm connected to but I keep getting kicked off during an upload. Sometimes I can get it to resume but never long enough got it to complete the upload. Grrrr...
All sources are now on GitHub. Source links are in post #3
EDIT::
New build up. See post #2
Hello there, it's time to get this rolling somewhere.
This is a Development-Thread. Please don't post if you aren't a developer.
What this IS
This is a Development thread, a platform for developers to discuss the development of CyanogenMod for the G925F. It's made so that we can get this working, fix up the problems - because there will be severe ones - and achieve a working official Rom at some point.
At the moment it's @OldDroid and me with help, but it would be awesome if interested devs would join in so that we can make this a team effort.
In short, it's a Dev-Thread in a dev section.
Right now it doesn't work and I'm not sure that it will work.
What this IS NOT
This is NOT a working Rom. Not even close. I can only link you to the kernel repo and soon to device and vendor, as they are almost completed for a first try.
And yes, there is no download link for the Rom. Because there isn't anything you could download yet.
This is also NOT intended as a Q&A thread. Please don't ask if your variant will be supported, I will respond by trolling. Firstand only priority is to get this running, then we'll talk about variants.
And ETA is an evil word with no meaning here. I work slowly, deal with it
Where are we currently?
Much further than a day ago
Thanks to @OldDroid, we've teamed up
All the links you want (minus the download link :angel
device: (soon, almost complete)
https://gitlab.com/mythos234/device_samsung_zeroltexx
vendor:
https://gitlab.com/mythos234/vendor_samsung_zerolte
kernel:
https://gitlab.com/mythos234/zerolte-kernel-CM
Once available, buggy alpha builds will be posted here
///
vendor and device will soon be pushed to my github
Reserved
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
vendor is setup
OldDroid said:
i'll join you ... also started working on cm12.1 for s6 edge 5 days ago (currently in england with my school class)
Click to expand...
Click to collapse
Welcome aboard then
vendor is finally setup and good to go!
https://github.com/mythos234/vendor_samsung_zerolte
It's apparently not without some minor casualties, but we got it. Huge thanks to @RaymanFX, he's helping me, since I'm not that much into CM building yet and I'm also basing this project on his CM for the N910C, which's 5433 is darn similar to our 7420, so we got a pretty good base to begin with.
add me as participant to the repos ^^
https://github.com/OldDroid
OldDroid said:
add me as participant to the repos ^^
https://github.com/OldDroid
Click to expand...
Click to collapse
Done for all the 3 of them
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
mythos234 said:
Looks like I killed Bluetooth for now (lol). Other than that it's slow but steady progress.
Click to expand...
Click to collapse
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
nasko_spasko said:
What do you mean "killed"? Killed the chip or wiped the MAC addr. or something?
Click to expand...
Click to collapse
I'm currently building the Rom with completely removed Bluetooth support
First Build is compiled and ready for a test.. But I can't install the zip. This would be hillarious if it wasn't so annoying
mythos234 said:
Besides I said it can't be installed Hard to test something you can't even install
Click to expand...
Click to collapse
I think that there was a mistake in the partition sizes.. /system was declared as 4.1GB, but it's only 3.6GB. Recompiling with a new value, should be able to flash it then
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Aircondition said:
Good luck develop without documentation for exynos chipset.
Click to expand...
Click to collapse
The lack of drivers makes this a fun exercise almost Where's be the challenge if everything was easy...?
Aircondition said:
Good luck develop without documentation for exynos chipset.
But can you tell us more in details how porting works and what are the challenges with it.
Is it hard to develop a rom without samsung binary files and drivers? I know they are proprietary and closed soruce.
If just Samsung could be more developer friendly like Sony.
We can request source for closed binaries here, http://opensource.samsung.com/reception/receptionSub.do?method=inquiryView, most likely they wont answer
Click to expand...
Click to collapse
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
mythos234 said:
I can't say what the challenges here will be, since I couldn't manage to even flash it yet - Second build is compiling since hours now. For now it's using all the proprietrary stuff we managed to grab and some additional stuff from the 5433 CM. But without booting it's hard to tell what won't work and might present a challenge ^^ From what I saw it'll be tough to just get the modem running. The hard part is to write the drivers yourself
Click to expand...
Click to collapse
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
lch920619x said:
It's interesting that you can use drivers from 5433, which is a 32bit platform. Most drivers are not compatible when you switch from 32bit to 64bit if I am right?
Sent from my SM-G920F using Tapatalk
Click to expand...
Click to collapse
As a base to know how to do it, obviously we can't just use drivers for a different chipset
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
mythos234 said:
Updated the /system size in the BoardConfig and at least it flashes. But it doesn't want to boot for some reason yet.
Click to expand...
Click to collapse
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
-Mr. X- said:
If you have the 5.1.1 boot loader and are using 5.0.2 as a base. Sboot will not boot it. As a fyi. It checks Linux versions.
Click to expand...
Click to collapse
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
mythos234 said:
Both is 5.1.1 and Sboot seems to clear the boot as well, everything seems to go fine, it just doesn't boot. :/ Trying with building the kernel during the build itself instead of using a prebuilt one and see how that goes
Click to expand...
Click to collapse
I would personally flash an Engineering boot loader while doing this, to ensure version checking is not the issue.
Hey guys
In memory of a very dear friend who passed away yesterday, I am starting this thread and a new era for our x3.
CM has pushed their CM13 branches yesterday, which means it's time for a new project. This time, though, I will be all by myself.
Please do not expect any miracles soon, as the M sources still need to settle a bit before we can even hope for a halfway working build.
Once again, you have several ways to get in touch with me/us:
You can use this thread (but keep it development related)
We have our own IRC channel on freenode, called #p880-dev
Use our github site
PM (even though the other ways are preferable)
We are of course still open source, and you can find the repos on our github:
Device tree
Kernel
Blobs
Any help is greatly appreciated, be it pre-alpha testing, or helping with actual development and fixing bugs. Feel free to make a pull request on github, which we will most likely merge happily. If you're not that experienced in git, feel free to contact me about it.
If you want to use this sources/ROM as your base, you sure are allowed to, but please let me/us know about it before you release it and give proper credits.
That's all we're asking for.
I know you want to know the actual Status, so I try to always keep it updated in this OP:
Not working:
Most likely everything
Working:
Most likely nothing
Now, the most important part:
If you like our work and all the time we spent in order to get it working, feel free to buy us a coke/beer/whatever by donating a litte bit
Special thanks go to: (names in no particular order)
@Daniel Kng
@fritzcola
@sunsettrack4
@thegrim11
@LGaljo
@alfsamsung
@Adam77Root
kingf1 from IRC
And last but not least, please keep this thread on topic! All OT posts will be deleted without further warnings!
XDA:DevDB Information
[DEV] [WIP] Unofficial CM13 for the p880, ROM for the LG Optimus 4X HD
Contributors
laufersteppenwolf
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.1.x
Based On: CyanogenMod
Version Information
Status: Testing
Created 2015-10-06
Last Updated 2015-10-06
Reserved
A quick update, CM's sources are still not compilable as they are still working on the initial bringup.
I will stay on it and see what I can do
I will pay you, just please make final ROM for 4X, with everything working as it shoud be! That would be awesome!
Wysłane z mojego LG-P880 przy użyciu Tapatalka
I will pay you too. I would like when I will be to have the final ROM fo 4x. Thanks
Make it working relibly and responsively, and I will pay you too. You deserve it!
I don't mind if it takes months to achieve it. Just make it at some point, and I'll be happy!
Can't wait !!!
ps. i'm sorry for your friend
laufersteppenwolf said:
A quick update, CM's sources are still not compilable as they are still working on the initial bringup.
I will stay on it and see what I can do
Click to expand...
Click to collapse
I'm also waiting for complete bringup tried for daily driver... failed. If you need help just send me message on hangouts/mail
@laufersteppenwolf, I was hoping you could give insight regarding this current dilemma seen with CM13. http://pastebin.com/vHMRMS0E
Feel free to PM me or reach out on here. Wanting to know if you were successful getting past the problem and if so what was your solution. Your time and consideration is appreciated.
SHM said:
@laufersteppenwolf, I was hoping you could give insight regarding this current dilemma seen with CM13. http://pastebin.com/vHMRMS0E
Feel free to PM me or reach out on here. Wanting to know if you were successful getting past the problem and if so what was your solution. Your time and consideration is appreciated.
Click to expand...
Click to collapse
that's a CM issue and needs their fixing. Hence I did not look into it, because if I go on do my "fix" it will most likely differ from CM's fix and may then cause some later issues.
So I'm currently waiting for CM to fix it
Some days ago is builded a cm13 ZIP, but it doesnt even pass bootloader.
Here are my commits for device tree. I disabled most likely everthong what causes building errors like Audio and CameraWrapper.
Here are my commits https://github.com/lenzwagner/android_device_lge_p880/commits/cm-13.0
@laufersteppenwolf will be on IRC the next evenings. Hope you'll be there too.
---------- Post added at 07:45 PM ---------- Previous post was at 07:40 PM ----------
laufersteppenwolf said:
that's a CM issue and needs their fixing. Hence I did not look into it, because if I go on do my "fix" it will most likely differ from CM's fix and may then cause some later issues.
So I'm currently waiting for CM to fix it
Click to expand...
Click to collapse
They fixed it some days ago.
Look here:
1. http://review.cyanogenmod.org/114239
2. http://review.cyanogenmod.org/114277
3. http://review.cyanogenmod.org/112338
I already fixed the device tree quite some time ago without disabling it, will have to look into it another time as I have to fix my mom's lappy first...
laufersteppenwolf said:
I already fixed the device tree quite some time ago without disabling it, will have to look into it another time as I have to fix my mom's lappy first...
Click to expand...
Click to collapse
If you find time, i'm on IRC atm
@fritzcola, just got home from work, gonna check out those commits now. Thanks for posting them. ffmpeg has been a pain for me this past week trying to compile CM13 :-/. Gotta love a fresh brunch out the kitchen lol.
edit: eh, those commits have already been merged so problem still persists.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
@fritzcola, just got home from work, gonna check out those commits now. Thanks for posting them. ffmpeg has been a pain for me this past week trying to compile CM13 :-/. Gotta love a fresh brunch out the kitchen lol.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Just run "make clean" and "repo sync". Commits are already merged in source apart from one.
@laufersteppenwolf Can you upload the fixes to a " cm-13.0" branch?
And do you already go further than BL?
fritzcola said:
Just run "make clean" and "repo sync". Commits are already merged in source apart from one.
@laufersteppenwolf Can you upload the fixes to a " cm-13.0" branch?
And do you already go further than BL?
Click to expand...
Click to collapse
Yea, just verified I already have them in the source. Stagefright still being an issue. Need to look at gerrit and see if there is a commit on standby that may resolve my problem. codecs_utils.cpp fails to compile over at external/stagefright-plugins/utils/.
SHM said:
Yea, just verified I already have them in the source. Stagefright still being an issue. Need to look at gerrit and see if there is a commit on standby that may resolve my problem. codecs_utils.cpp fails to compile over at external/stagefright-plugins/utils/.
Click to expand...
Click to collapse
Weird cause i just compiled a build with no errors.
fritzcola said:
Weird cause i just compiled a build with no errors.
Click to expand...
Click to collapse
I got passed it finally. Seemed it was just a fluke with no explanation. Got to deal with this problem now. Take note of line 232 specifically. Haven't had time to mess with it yet.
Sent from my Ascend Mate 2 using Tapatalk
SHM said:
I got passed it finally. Seemed it was just a fluke with no explanation. Got to deal with this problem now. Take note of line 232 specifically. Haven't had time to mess with it yet.
Sent from my Ascend Mate 2 using Tapatalk
Click to expand...
Click to collapse
Are you sure you're building for P880!? MSM8974 is Snapdragon stuff
fritzcola said:
Are you sure you're building for P880!? MSM8974 is Snapdragon stuff
Click to expand...
Click to collapse
No sir I am not. For another device, forgive me if that caused any confusion. My initial post on here was with regards to ffmpeg. A hunt for an unofficial build on xda brought up a few links and so wanted to make contact with the dev(s) to see if they had the same problem and/or fix so I may compare and possibly adapt if applicable my previous outcome. As for my current issue I do not expect any answer or results from here since its completely off topic from this device. I merely shared it in response with no intention or expectations for a solution. . I did take a look at your repo and saw ffmpeg is obsolete so I removed it from my tree as well since it was most definitely causing my builds to break.
The Unlegacy-Android ProjectIntroduction
Unlegacy-Android started out as the OMAP4-AOSP Project. It was created in late 2015 in order to maintain a clean and organized place for pure AOSP support for various OMAP4 devices, such as the Galaxy Nexus and the Samsung Galaxy Tab 2 series. Over time this evolved to support more than just these devices, but still maintains its roots of supporting "legacy" devices that no longer receive "official" updates: hence Unlegacy-Android was born.
Installation
It's important that /system needs to be unmounted before installing the ROM - some recoveries tend to leave it mounted after performing operations on it.
If you're planning to install GApps, be sure to read the second post!
Aside from these, installation and upgrading is no different than on other ROMs. As usual, 'espresso' goes for all non-3g versions, 'espresso3g' goes for all 3g versions.
Problems
- Occasional sound stuttering in some games
- No hwrotation (meaning the boot animation is landscape on p31xx). I don't consider this as a problem, as autorotation will take effect after bootup anyways... and most 7" tablets, like the Nexus 7 work this way as well.
- The 7.1 builds are experimental! Means: modem not working perfectly yet.
If you notice anything else, be sure to report it in this thread. While I'm kind of busy, I usually read the thread and acknowledge the bug reports, even if I don't reply directly to them.
Downloads
See: http://builds.unlegacy-android.org
Always use the latest TWRP, to flash Android 7.x, you must use TWRP 3.0.3-0 or newer.
Features?
There isn't much to say here - this is AOSP, if you install GApps, you pretty much get the same thing that's running on the Nexus devices. The aim of this project is to create a fast and stable ROM - although, one could use Xposed to add extra features.
As usual, feedback is appreciated
Want to support development? You can consider donating, I spent countless of hours with this
XDA:DevDB Information
Unlegacy Android Project, ROM for the Samsung Galaxy Tab 2
Contributors
Ziyan, Android-Andi
Source Code: https://github.com/Unlegacy-Android
ROM OS Version: 7.x Nougat
ROM Firmware Required: The latest bootloader for your device.
Version Information
Status: Beta
Current Stable Version: 4.4, 6.0
Created 2016-07-03
Last Updated 2017-10-22
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
siealex said:
One more note. DO NOT set up your Google account until you grant all permissions, otherwise you will be stuck on the initial setup.
Click to expand...
Click to collapse
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Ziyan said:
GApps
If you want to install GApps, we recommend Open GApps Nano or BaNkS GApps.
An important note: as this is a pure AOSP ROM, installing GApps tends to be problematic: in order to try to avoid installation issues, be sure to install GApps immediately after installing the ROM, before booting the system for the first time. After the initial bootup finished, be sure to go into Settings -> Apps, and grant every permission to every Google application - most importantly, Google Play services.
In the case of an upgrade, be sure to re-install the GApps package, as upgrading wipes /system. You shouldn't need to re-set the permissions afterwards.
Rooting
You can flash either the latest SuperSU or OpenSource SuperUser to get rooted.
Click to expand...
Click to collapse
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Bastiary said:
Wow, i saw this rom on galaxy nexus section. Does this rom included CMA?
Click to expand...
Click to collapse
No, at least not yet. I think that the big thing for this will be 3.4 in the near future - I made some very good progress with it, aside from camera not working yet, there are only minor problems remaining
Thank you for everything , dear friend ! And for the support of the old device , and what you are doing and Andi for us ordinary users .
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Az-09 said:
I understand correctly , that support will only 6.0.1 Android N and we do not see , because the device and its old base ?
Click to expand...
Click to collapse
Before every new Android release, we devs get all sorts of questions like this. I'd like to say it once and for all: there's no such thing as 'we do not see' the next versions and whatnot. People are being negative for some reason, but we always try and succeed in the end... I'm sure that if you start reading past posts, you'll find a lot of people saying that we1l never see Lollipop or Marshmallow due to the device being too old, lol.
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
radz_ said:
Download link?
It just says look at the top of the page? Is it soon?
Thanks for the new ROM....keep it up!
All the best...
Click to expand...
Click to collapse
check download tab section.
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
pickmod said:
Hello! The ROM with the codename "espresso" is for the version: Galaxy Tab 2 7.0 Wi-Fi P3110 / P3113 and Galaxy Tab 2 10.1 Wi-Fi P5110 / P5113. Namely we talk about all versions with codename "espressowifi"?!
Click to expand...
Click to collapse
Yes, that's correct.
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Screeshots
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
no need for this, it's aosp there isn't any custom features and everybody know how aosp looks
Astro Noid said:
Dear Mr. @Ziyan,
1stable congrat and thx Sir for being ROM Maker, we would love to see you update it regularly and add these:
*feature list
*changelog
*screenshot
~Omaple~
"...stay success and keep tab 2 alive at least till 2020"
Click to expand...
Click to collapse
Oh don't worry, I'm working extremely hard in the background almost since like a year... I know a lot about these devices (bought a P5100 specifically for testing 3G on the builds and kernels)
Feature list: well, this is AOSP, and I'd like to keep it this way. Imagine this like the stock ROM on the Nexus devices (with GApps flashed, of course).
Changelog: don't expect anything other than AOSP updates and hardware related fixes and updates - of course, I'm going to write a post each time I release an update, just like I do in the Galaxy Nexus thread however, it's unlikely that I'll add a changelog to the OP (I just don't see the usefulness in it).
Screenshots: will do, but then again, don't expect anything special. Stable and fast pure Android, that is AOSP. As a side note, it's Xposed compatible
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Thak you for your effort to keep tab 2 alive . Amazing work. Are RRO Layers compatible with this rom?
Ziyan said:
I hope everybody likes the new shiny unified forum section! There's still a bit of a work left to do, but I think it looks great and eases maintaining the threads; blame me if you think otherwise :silly:
Click to expand...
Click to collapse
Hi Ziyan,
I'm glad you mentioned this, as I thought that I was going insane this morning (or just slightly more insane than usual).
Just browsing the new "Unified" forum (to verify my subscriptions) and noticed that the "Dhollmen" threads could be clarified (just like the "Linaro" threads), for example ...
This thread: http://forum.xda-developers.com/showthread.php?t=2176563 could be titled: [KERNEL][P51xx][AOSP] Dhollmen Espresso
This thread: http://forum.xda-developers.com/showthread.php?t=2183830 could be titled: [KERNEL][P31xx][AOSP] Dhollmen Espresso
Just to avoid confusion (I freely admit that I am easily confused).
Thanks.
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Android-Andi said:
@mentat no need to have 2 threads, one is enough now in unified section
I also don't know what your question hast to do with this rom [emoji14]
~ All my work, news etc. on http://andi34.github.io ~
Click to expand...
Click to collapse
Hi Andi,
I only suggested renaming the existing "pair" of threads (they both exist in the Unified Forum) ... Just like the "pair" of Linaro threads (that also both exist in the Unified forum).
The download links in (all four) of the threads (mentioned above) link to unique builds on AFH (for both P31xx and P51xx devices) in this forum: http://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Sorry for all the edits (I put the blame on OCD).
Thanks.
mentat said:
@Ziyan, while we're on the subject, the CandySix for P51XX thread: http://forum.xda-developers.com/galaxy-tab-2/10-inch-development/rom-candysix-v1-1-t3331598 should also be moved to the new Unified forum as well (the CandySix for P31xx thread has already been moved).
Click to expand...
Click to collapse
Done; I guess this is it then. Like the XDA forum admin said, the best way to handle moving both threads is to move them both to this unified section, and close one of them (preferably the one with the less posts). While we could merge them into one thread, the posts would get all mixed through the other threads posts (because of the date order) and we would lose any sense of a flow in the conversation...
Minimum Custom Recovery version?
@Ziyan @Android-Andi Thanks for bringing new life to this old tabs
Is there any minimum requirement for recovery for flashing this ROM? I'm running pretty old CWM v.6.0.5.1. Is it sufficient?