Develop Bugs

I9505 Common (CM10.1)

Post Updated from Original
Cyanogen has posted a i9505 common device tree.
It is based on his working configurations for US T-mobile.
There are two ways to get this:
1) Clone these repos:
https://github.com/CyanogenMod/android_device_samsung_jf-common
https://github.com/CyanogenMod/android_kernel_samsung_jf
https://github.com/CyanogenMod/android_device_samsung_jfltetmo
2) Set up your CM environment and "breakfast jfltetmo" to pull the 3 repos above.
The first 2 are the common device and kernel. The third can be used as a base for your device.
(So fork it to your own repo and start making changes)
Hope this gets other variants up quickly! Thanks again to Cyanogen for the work to get it this far so quickly!

garwynn said:
Well, while waiting for the SPH-L720 (Sprint GS4) to come out this weekend I'm trying to do what prep work I can. I'm checking both here and #cyanogenmod-dev to see if anyone else has started this, but just in case I created jflte-common repos to start allowing collaborative efforts for GS4 work to get CM going ASAP. I'll be using these to get the jfltespr (SPH-L720) trees up and running.
Now fair warning, I'm doing this as my first port attempt but have several kernels and a few recoveries that I've done already. So please bear with the learning curve...
I9505 Common Repos:
https://github.com/garwynn/i9505_rec_ramdisk (Thanks to ewmno for posting the i9505 recovery.img!)
https://github.com/garwynn/device_samsung_jflte-common
https://github.com/garwynn/vendor_samsung_jflte-common
https://github.com/garwynn/kernel_samsung_jflte
I'm downloading the only i9505 source I saw so I can find out what linux build version they're using as a base. Figured that's a good starting point to figure out where we start for kernel dev.
Anyone interested in helping - would be most appreciated! I'll start working on the tree repos this morning (US CDT)
Click to expand...
Click to collapse
Since it's Qualcomm based - First thing you should do is fork https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=summary
Then go to Qualcomm's CAF release list at https://www.codeaurora.org/xwiki/bin/QAEP/release and go through the tags for your SoC and Android version. Check each out one by one. I'm fairly certain you are APQ8064T. Whcih is odd, there are no tags for the T variant...
Code:
git checkout <TAG>
Drop the Samsung tarball on top of the checked out tree, and diff it.
Code:
git diff > ../<TAG>.patch
Keep going until you find the patch that is the smallest. This is likely the CAF base that Samsung started from.
Two other things:
Be warned, Samsung hacks the **** out of their bases
Also, try to coordinate with cyanogen himself, I believe he'll be working on either the AT&T or T-Mobile variants.

Entropy512 said:
Since it's Qualcomm based ................................Blah Blah
Click to expand...
Click to collapse
What if i need to make 1 for I9500

Entropy512 said:
Since it's Qualcomm based - First thing you should do is fork https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=summary
Then go to Qualcomm's CAF release list at https://www.codeaurora.org/xwiki/bin/QAEP/release and go through the tags for your SoC and Android version. Check each out one by one. I'm fairly certain you are APQ8064T. Whcih is odd, there are no tags for the T variant...
Code:
git checkout <TAG>
Drop the Samsung tarball on top of the checked out tree, and diff it.
Code:
git diff > ../<TAG>.patch
Keep going until you find the patch that is the smallest. This is likely the CAF base that Samsung started from.
Two other things:
Be warned, Samsung hacks the **** out of their bases
Also, try to coordinate with cyanogen himself, I believe he'll be working on either the AT&T or T-Mobile variants.
Click to expand...
Click to collapse
Thanks for the starting point, Entropy! I'll start on that during my lunch break.
I'm keeping up IRC on the build box but just sent an alt contact in case anyone else you know is interested in collaborating.
I'm guessing that they're not differentiating (yet) between the APQ8064 variants.
So I'll start pulling standard APQ8064 and hopefully get lucky.

might want to look at cpu_is_apq8064ab related stuff in the jb_2.5 branch to get an idea of where stuff is - The APQ8064T may be referenced as APQ8064AB in kernel sources. Not sure.
Still doesn't answer which tag to follow.

We are lucky to have such a driven Dev. Thank you gawynn, for all you have done, and all that you will do.
Kudos from the E4GT community.

Entropy512 said:
might want to look at cpu_is_apq8064ab related stuff in the jb_2.5 branch to get an idea of where stuff is - The APQ8064T may be referenced as APQ8064AB in kernel sources. Not sure.
Still doesn't answer which tag to follow.
Click to expand...
Click to collapse
No but it does allow me to thin out the list.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Every build that I have seen so far is March so we should be able to rule out any April builds.
So once I get access to my build box again (TV died yet again...) I'll start at the bottom and work my way up.
(Edited post) So far the above (AFAIK) addresses kernels. Still haven't addressed device.
Thinking we can still use this for graphics base:
https://github.com/CyanogenMod/android_device_samsung_msm8960-common
I almost want to fork d2-common for the jflte common device and start replacing S3 with S4 details.
I have that 9505 system dump on my build box so I can start extracting stuff from there.
More as I keep reading and digging.

Looking forward to development for S4 , planning on getting it as soon as my renewal will allow .
Sent from my SPH-D710 using xda premium

Cyanogen found kernel already, head is jb_2.5, didn't get the branch point but says he knows what it is.
In the meantime I went ahead and stripped d2-common and used that as a shell for jflte-common device.
Future status updates on this will be placed here at Cyanogen's request:
https://jira.cyanogenmod.org/browse/QSDB-25
Feel free to take a look there for progress reports.
Will be requesting thread lock for now.

As far as graphics base you'll almost surely have the same flags as any other caf-display device.
Sound can get a bit more funky... I'd look at mako, Sonys, and Oppo Find5 for inspiration there as those are the current non-T APQ8064s.

Entropy512 said:
As far as graphics base you'll almost surely have the same flags as any other caf-display device.
Sound can get a bit more funky... I'd look at mako, Sonys, and Oppo Find5 for inspiration there as those are the current non-T APQ8064s.
Click to expand...
Click to collapse
i9505 Latin JB source has Alsa audio folder in the platform side - wouldn't be able to use that?
You know what? Seeing as OSRC pulled it (for now) I'll make a repo for both the kernel and platform side and add the links here in a sec.
Edited:
https://github.com/garwynn/i9505_latin_jb_platform
https://github.com/garwynn/i9505_latin_jb_kernel
Hopefully we get the L720 stuff here soon so I can compare ROMs and kernels against the ones I have already.
Should give a good idea as to what can be common vs. proprietary.

Had to change my search for the kernel based on a misunderstanding of where to start.
So I started with the jb2.5 head and pulled this list from it.
As you can see I've been trying a "divide and conquer" method to figure out where the branch point is.
Tried checkout method after cloning the repo but can't seem to get it to pull the branch source.
So for now I'm resorting to a rather tedious process of clone branch, diff, delete, repeat.
Also doesn't help that I lost the build box for a day but hopefully will be fixed by 7 pm.
So while I wait for the build box to come back I'm going to see if that AT&T dump is different from the i9505 one I have.
If so should shed some light on what in the ROM will be common and what won't be.

garwynn said:
No but it does allow me to thin out the list.
Every build that I have seen so far is March so we should be able to rule out any April builds.
So once I get access to my build box again (TV died yet again...) I'll start at the bottom and work my way up.
(Edited post) So far the above (AFAIK) addresses kernels. Still haven't addressed device.
Thinking we can still use this for graphics base:
https://github.com/CyanogenMod/android_device_samsung_msm8960-common
I almost want to fork d2-common for the jflte common device and start replacing S3 with S4 details.
I have that 9505 system dump on my build box so I can start extracting stuff from there.
More as I keep reading and digging.
Click to expand...
Click to collapse
I don't know much about porting and building CM but I noticed there was some confusion about the chipset model. I'm wondering if this might help you in any way:
http://www.anandtech.com/show/6914/samsung-galaxy-s-4-review/3

ilabs said:
I don't know much about porting and building CM but I noticed there was some confusion about the chipset model. I'm wondering if this might help you in any way:
http://www.anandtech.com/show/6914/samsung-galaxy-s-4-review/3
Click to expand...
Click to collapse
That isn't useful. We are fully aware of which chipset is in this device. What we're not entirely sure of is which release tags/branch in CAF it corresponds to (unlike most other qcom processors, there is not a direct match between the chip's identifier and any CAF tags. That said, it is starting to seem like CAF is using the apq8064 releases for both apq8064 and apq8064t)

As embarrassing as this may be for me, let my facepalm teach others...
Read advice from mentors well.
And if not sure, read it again. And if still not sure, read it again.
Bold and italics below are my emphasis.
Entropy512 said:
Since it's Qualcomm based - First thing you should do is fork https://www.codeaurora.org/gitweb/quic/la/?p=kernel/msm.git;a=summary
Code:
git checkout <TAG> [I][B](Notice no -b here like I was doing and thus causing my headaches)[/B][/I]
Drop the Samsung tarball on top of the checked out tree, and diff it. (Don't go erasing what's already there like I do with other projects.)
Code:
git diff > ../<TAG>.patch
Keep going until you find the patch that is the smallest. This is likely the CAF base that Samsung started from.
Click to expand...
Click to collapse
Why does this matter? My diffs went from 24MB to 4MB and is a lot easier to see what may be going on.
When we do get to find the branch point it will make a huge difference when I pull a more recent version and then want to apply that patch to the newer version.
Entropy, had another question... In stock kernels I would normally patch Linux before doing anything else.
I'm assuming I'll want to grab the latest jb_2.5, patch Samsung's mods in first and wait until we get stable before patching Linux versions?
Just because we add Samsung's mods in doesn't mean everything will work perfectly as-is... and that logically would need addressed before anything else.
And still waiting for my build box to come up - the host is having their ISP issues addressed. Thankfully the home dual boot works great for simple things like these kernel diffs.

garwynn said:
As embarrassing as this may be for me, let my facepalm teach others...
Read advice from mentors well.
And if not sure, read it again. And if still not sure, read it again.
Bold and italics below are my emphasis.
Why does this matter? My diffs went from 24MB to 4MB and is a lot easier to see what may be going on.
When we do get to find the branch point it will make a huge difference when I pull a more recent version and then want to apply that patch to the newer version.
Entropy, had another question... In stock kernels I would normally patch Linux before doing anything else.
I'm assuming I'll want to grab the latest jb_2.5, patch Samsung's mods in first and wait until we get stable before patching Linux versions?
Just because we add Samsung's mods in doesn't mean everything will work perfectly as-is... and that logically would need addressed before anything else.
And still waiting for my build box to come up - the host is having their ISP issues addressed. Thankfully the home dual boot works great for simple things like these kernel diffs.
Click to expand...
Click to collapse
You mean pull in patches from kernel.org? I personally don't do that any more - it usually causes more problems than it is worth. The only time I've done that was a situation when I had to match d2's wifi backport on 4412 devices.
So far, devices in CM are a mix of two approaches:
1) The old (and usually quick) approach of taking the manufacturer tarball and dropping a bulk update from mako onto it. Since this is a MUCH newer CAF base and is 4.2.2 - this may not be necessary. You may just be able to get the kernel running CM10.1 with not much modification.
2) Chunk up the manufacturer's diffs and rebase them onto the latest jb_2.5 - d2 has done this, HTCs are in the process of doing so, and Sonys are probably going to do so in the next month or two. Same for Oppo Find5 - we used approach 1 initially, but are switching to 2.
For your sanity, you probably want to chunk up the manufacturer's diffs into smaller parts if you can. The workflow I used was:
Check out the closest CAF tag once you determine it.
Check out a new branch at this point using
Code:
git checkout -b <branchname>
In my case, I named the branch for find5 find5_CAFTAGHERE so I would always remember the tag.
Drop the kernel tarball on top of the CAF tag
Commit the whole big mess
Now, here's the fun part:
Unstage some files out of the commit. For example, if you want to unstage drivers/media/video out, do:
Code:
git reset HEAD^ drivers/media/video
Then
Code:
git commit --amend
This will remove the changes from drivers/media/video from the megacommit
Then
Code:
git add drivers/media/video
git commit
Commit just those changes. Try to find associated headers if you can from include/
Now, if you just split out one commit:
Code:
git rebase -i HEAD~2
to switch the order so the megacommit is the last commit for further chunking.
It's time consuming but makes the chunks much easier to analyze.
When I get home, I'll post my bash alias 'gitshowfiles' which shows a list of all files changed by the last commit. It's hightly useful.
When you're done, you'll have a nice reference like:
https://github.com/Entropy512/kernel_find5_reference/commits/find5_A8064AAAAANLYA101034

With the build box back in business I finally got to the point Entropy was talking about.
For reference here is the commit:
https://www.codeaurora.org/gitweb/q...it;h=b5075e02c2ff1d959c589552c62329c4797b0535
And I've attached the diff file so those following along can keep doing so.
(I've posted the same stuff on CM's Jira as well)
So I'll start 2 repos next.
1) Fork current CAF jb_2.5 to a new repo.
https://github.com/garwynn/kernel_samsung_jflte
2) Fork above version to this repo:
https://github.com/garwynn/i9505_CAFDiff
...where I'll start the process of splitting the big diff into smaller ones, just in case they are needed.
Now it's possible that Sprint's kernel could have branched off differently but there's an easy way I can think of to check that. Take the i9505 kernel source I have now, drop Sprint's on top and run a diff to see how different they really are.

And just an update. Sprint's GS4 is making its way to folks today. One person already has and I'm trying to get what I need to really get going.
Update 1: Odin mode shows "Write Protect Enabled" - wondering if this means bootloader is locked.

Few updates while I get things moving.
A second look at that LA kernel had what seems to be everyone's defconfig. Added and pushed to common kernel.
You'll probably need to combine your specific additions still to jf_defconfig to get a full one.
At least the Sprint one identifies an Audience audio chip and binary that should be there.
Did an initial push of common device folder after confirming Sprint's fstab matches common i9505.... so I'm guessing they're all the same. It's very rough so wouldn't try using it yet... just want access to it in case I pull to my home box. Now working to get a device specific one up enough to try a CWM build. Going to have to hold testing anyhow until we get a full restore and figure out about that write protect.

OK, for those not following the SPH-L720 thread, I'm doing test builds of CM/CWM at the moment to see what I can get working before I move over to the kernel.
I tried including msm8960-common and it failed on kernel issues. Think I'm going to leave it out for now and try just getting the CAF jb_2.5 to build successfully first. I can leave in qcom-common and that seems to at least play nice.
CWM working for SPH-L720 but users reporting that moving up/down requires 2 key presses to get it to move. Alpha 5 was reported as losing External SD card functionality - not sure why as I didn't change the fstab. i9505 users reporting that it didn't work, suggesting there may be a difference. We better nail that down and if need to move something from common to variant, do so before others start building off of it.
I'm starting to read the Find 5 configs as it seems one of the only ones with the Adreno 320 config. But again, I've got to get the kernel to build before I start really getting into this stuff.
I'll push updates to repos tonight after I get another successful build.

K860/i CM10.1 - Linaro - beta 1 -updated 19.10.'13

Versioning explained:
>>>>>>>>>|0.92*|>>>> alpha>>>>>>beta>>>>RC>>>>1.0>>>>>
*0.92 will be removed as an option once RC comes out
This ROM is a spin-off from Mr. Linscue's and CyanogenMod sources.
What makes it different is that it is built with Linaro toolchain, current 4.7., instead of Google supplied one.
It's a product of my curiosity, Mr. Linkscue's extensive patience with helping me to understand the whole picture and his work so far on our devices. This wouldn't be possible without him.
To be able to build with Linaro toolchain there is a lot of CM source editing and git cherry-picking to make code fit for Linaro's GCC so the final ROM can actually be compiled. Thanks to Open Source, Android, internet and XDA-devs, I have been able to make it real by collecting the info and conveying it to this ROM.
I have to remind you, this is my personal build, it was never intended to be released to the wide public, I'm not a programmer/coder and there is no warranty.
Few notes:
1
The build: This is a first functional build through Linaro for this phone. It's compiled with -O3 flag, so /system (ROM) side is 90% optimized. I' m continuing to find proper code snippets that will further improve the build.​
2
Battery life. Kernel used is prebuilt Lenovo, therefore battery life should be similar to official ROM, bar the specific LenovoPower settings, however if you are installing CM you are expected to know how to manage your phone. Without Lenovo's updated kernel sources, further optimizations are not possible, either for performance or extending battery life. If you are experiencing poor battery life, there are two things, 1. You have just I nstalled the ROM, give it a few days for system to settle in. There are few things going on during first day or two that might deteriorate your battery life 2. You have an app installed that is keeping your phone awake, preventing it to go to deep sleep. You can install BetterBatteryStats from here: http://forum.xda-developers.com/showthread.php?t=1179809 and find the offending app.​
3
If you like it, use it. We are fixing general bugs as we go, and we know what those are. You may report them here but don't expect them to be fixed. Any app addition request or AOKP/MIUI/whatever port will not be entertained. As I said in the beginning, this is my personal build and I'm just sharing it with you.​
4
Why name it SENNA: Ayrton Senna: “And so you touch this limit, something happens and you suddenly can go a little bit further. With your mind power, your determination, your instinct, and the experience as well, you can fly very high.​This rom was made possible thanks to:
1.
linkscue​
2.
zuncun​
3.
xda-dev usersDJLamontagneIII, @Dri94​
4.
OpenSource​
5.
Linaro​
Sharing is caring, so if you want to repost this ROM to other places, I don't care but I do ask you kindly to refer to http://bbs.lephone.cc/k860/t570716/
Since 99% of the work is by Mr. Linkscue,take your time and drop by his thread: http://bbs.lephone.cc/k860/t553805/1/ and give him some kudos.
That's all.
Two releases:
SENNA 0.92
Latest CM source
Reverted the codecs to official, now video is ok
Updated busybox binary
Special thanks to linkscue on his continued support
SENNA beta 1
Kernel is built from Lenovo old source and adapted for JB
Both kernel and ROM are built with Linaro at O3 optimization level
Samsung's gralloc, hwconverter, fimg and kernel mali drivers, readjusted memory use, replaced ion libs.
Bloetooth works.
Disable HW overlays to have video working in landscape mode
(Current result on Antutu is 21605) (I have to note here that I have noticed performance deterioration, the number you get varies and drops on subsequent tests)
SENNA beta 1
[bugfix] *Wireless hotspot - so far ONLY open network is supported
*replaced Bluedroid stack with Bluez - core to UI - BT works now,
****please report special use cases if there are bugs.****
[enh.] *Screen off animation
alpha6 / kernel 3.0.40
* corrected schedulers in cgroups (oops)
* Latest lowmemorykiller
* lowmemorykiller autodetect oom_adj values
* added CPU topology patch
* added compaction and migration
* CPU unaligned access path
* Patched CRC32
* Replaced TreeRCU > jRCU (Read/Copy/Update)
* Replaced SLUB > SLQB memory allocator
* WasActive page flag
* Makefile optimizations
* disable preemption in machine_shutdown
* synchronize_rcu_expedited instead of synchronize_rcu
* patched fimg
* completely updated kernel internals
* completely updated net and fs layer
* completely updated memory management
* [bugfix] long press on touchscreen during charging has been fixed
alpha5 / kernel 3.0.15
* Added SIO IO Scheduler
* Added BFQ IO Scheduler
* zram enabled (one zram device in use)
* KSM enabled in kernel, use menu to on/off its use
Beta 1: http://pan.baidu.com/s/1892bL
md5: af12fd4fc63542858cba978a8b7f6f51
0.92: http://pan.baidu.com/share/link?shareid=1733734082&uk=2184427820
md5: 25dffc77e3e269656497fa382a3897ba
Google stuff:
If you visit Mr. Linkscue's thread here http://bbs.lephone.cc/k860/t553805/ there is a link to Gapps preload partition.
http://dl.vmall.com/c0zc102rqh
Flash it as you would do with the ROM and then go to Settings/Advanced/K860(i) Install gms. Reboot. All should be there. In the same menu you are also able to lock the MAC address so it doesn't change on reboot.
Github is here:
https://github.com/jason013?tab=repositories

Good job. Running on my k860 with no issues. I hope you try to keep updating this ROM.
I will update you with issues I face.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Stuttgart using Tapatalk 2

finch.****break said:
Good job. Running on my k860 with no issues. I hope you try to keep updating this ROM.
I will update you with issues I face.
Sent from my Stuttgart using Tapatalk 2
Click to expand...
Click to collapse
Thanks for liking it. I will keep it updated as much as possible. There are few bugs remaining on the platform and we are working on fixing them.
Definitely let me know if you have any problems with the ROM.

Good Job
This rom so good ! Waiting next update !

great room :victory:
waiting next update

finch.****break said:
Good job. Running on my k860 with no issues. I hope you try to keep updating this ROM.
I will update you with issues I face.
Sent from my Stuttgart using Tapatalk 2
Click to expand...
Click to collapse
btw how about gmaps? its work? coz i try to cm 10.1 phone reboot after i open gmaps,
Thanks before :good:

Harmalah said:
btw how about gmaps? its work? coz i try to cm 10.1 phone reboot after i open gmaps,
Thanks before :good:
Click to expand...
Click to collapse
Maps work for some time now.

first to vote for 5 star YAY
easily a 5 star for me since i dont know any programming/coding and im too lazy to do so...almost no support on lenovo ROM side so this addition is very much welcome...please keep it updated and kudos/respect to you my sir :good::good:
my only request would be a transparent and small on screen button for more screen orientation (see attached of my current screen)
you can get the systemUI here http://bbs.lephone.cc/thread-556541-1-1.html thanks thanks

Wow cool...will try ASAP
Sent from my Lenovo K860 using xda premium

innocence07 said:
easily a 5 star for me since i dont know any programming/coding and im too lazy to do so...almost no support on lenovo ROM side so this addition is very much welcome...please keep it updated and kudos/respect to you my sir :good::good:
my only request would be a transparent and small on screen button for more screen orientation (see attached of my current screen)
you can get the systemUI here http://bbs.lephone.cc/thread-556541-1-1.html thanks thanks
Click to expand...
Click to collapse
I'm sorry, you are talking about transparent taskbar? That iis as much as I could understand from the pics you posted.
To put it bluntly, what is going on now is trying to build kernel from source to match 4.2.2 and then cleaning up of proprietary files. Any UI polishing/additions I might consider at later date. So far, it seems to be a very far date But hey, it is functioning so far and sorry, but no..

relevant_placeholder said:
I'm sorry, you are talking about transparent taskbar? That iis as much as I could understand from the pics you posted.
To put it bluntly, what is going on now is trying to build kernel from source to match 4.2.2 and then cleaning up of proprietary files. Any UI polishing/additions I might consider at later date. So far, it seems to be a very far date But hey, it is functioning so far and sorry, but no..
Click to expand...
Click to collapse
yes both the onscreen button and the taskbar...its ok your the boss here anyways...and again thank you for sharing
i have another question uhm can i use this gapps http://wiki.cyanogenmod.org/w/Gapps since your rom is missing google play and other such gapps TIA

innocence07 said:
yes both the onscreen button and the taskbar...its ok your the boss here anyways...and again thank you for sharing
i have another question uhm can i use this gapps http://wiki.cyanogenmod.org/w/Gapps since your rom is missing google play and other such gapps TIA
Click to expand...
Click to collapse
Ok, I had skipped few tips here. If you visit Mr. Linkscue's thread here http://bbs.lephone.cc/k860/t553805/ there is a link to Gapps preload partition.
http://dl.vmall.com/c0zc102rqh
Flash it as you would do with the ROM and then go to Settings/Advanced/K860(i) Install gms. Reboot. All should be there. In the same menu you are also able to lock the MAC address so it doesn't change on reboot.

relevant_placeholder said:
Maps work for some time now.
Click to expand...
Click to collapse
btw how to fix USSD and change animated while charging ?
1. i try ussd not working and i used rillibrary.rar to fix ussd its working but signal bar not fully detect (how to fix)
2. and i could not charge if handphone is trunoff (how to fix)
thanks berfore

Harmalah said:
btw how to fix USSD and change animated while charging ?
1. i try ussd not working and i used rillibrary.rar to fix ussd its working but signal bar not fully detect (how to fix)
2. and i could not charge if handphone is trunoff (how to fix)
thanks berfore
Click to expand...
Click to collapse
Phone board/bootloader recognizes several operating modes like off charge, on, off, test etc. Mr. Scue identified them and it is working, however there is a problem that when you boot the phone after charging it in off mode, screen will turn white around the edges sometimes. For safety of your devices this part of functionality is not included yet.
I'm not familiar with the USSD problem yet. Will have a look into it, but if it wasn't working in official release, it could take time to make it working here.

relevant_placeholder said:
Phone board/bootloader recognizes several operating modes like off charge, on, off, test etc. Mr. Scue identified them and it is working, however there is a problem that when you boot the phone after charging it in off mode, screen will turn white around the edges sometimes. For safety of your devices this part of functionality is not included yet.
I'm not familiar with the USSD problem yet. Will have a look into it, but if it wasn't working in official release, it could take time to make it working here.
Click to expand...
Click to collapse
:good: thanks for explain

relevant_placeholder said:
Ok, I had skipped few tips here. If you visit Mr. Linkscue's thread here http://bbs.lephone.cc/k860/t553805/ there is a link to Gapps preload partition.
http://dl.vmall.com/c0zc102rqh
Flash it as you would do with the ROM and then go to Settings/Advanced/K860(i) Install gms. Reboot. All should be there. In the same menu you are also able to lock the MAC address so it doesn't change on reboot.
Click to expand...
Click to collapse
ive done all there is to do but still youtube dont work...em i missing something or youtube doesn't really work ???

innocence07 said:
ive done all there is to do but still youtube dont work...em i missing something or youtube doesn't really work ???
Click to expand...
Click to collapse
Ok, this questions now are going out of topic but let's chase this rabbit down the hole.
I am not familiar with the workings of youtube app (I assume you have successfully installed Play store and had it installed from there) so I am not sure what video/audio codecs it uses.
I can tell you right now one thing, related to video playback and Samsung's OMX codecs (the ****ty opensource ones) hw accel. video on this ROM is currently broken. I will soon reissue the ROM with files from official ROM to have that part working again, until I sort out what gets broken on OSS ones.
Currently I'm hands deep in kernel, I managed to transplant updated mali drivers into the old source to make it run on 4.2.2 and did some ugly hack job on HAL layer to have CM working, I have it at system stable level now. I'm tired and sorry for not being of much help, please google yourself and see what exactly are youtube app dependencies to make the videos run. If it uses on board hw codecs, I already told you what is the problem.
EDIT: try to disable GPU rendering for a test, in Developer options. just to see.

I flash several times this rom and always the same 2 problems ! Wifi doesnt work ! Stays there it said "turning wifi on..." and the 2nd camera program ( i dont remember the name ) always force close !!! Thanks
Sent from my K860 using xda app-developers app

what a great rom !! i hope you can fix the youtube problem and others minor problem soon!! :good:

Yup tried with GPU rendering disabled, HW accel enabled disabled.. Not just with youtube, videos don't work on many video content apps like imdb etc..
---------- Post added at 01:15 PM ---------- Previous post was at 01:15 PM ----------
However, wifi and focal seems to be fine

[ROM][03-12-13] Andromadus - CM10.2 & CM11.0 - Vision

I guess you've been waiting for this for quite a long time.
So I felt I should upload at least something and stop keeping these builds secret.
Before we start...
This is unstable. VERY unstable, compared to my latest CM10.1 build.
By the way, I had to remove CM10.1 build environment because I have no space left on SSD. No more CM10.1 builds from me, sorry
On a positive note, this build has (compared to CM10.1):
Camera button options (wake/unlock/peek/playback control) — I put this feature upstream. Try it, it's cool
Flash sync is fine
KSM works again (it just magically fixed itself)
DSPManager doesn't suddenly get unloaded from memory and break your listening experience
Persian language for hardware keyboard. The whole hardware keyboard support has been reworked.
Newer Trebuchet, with live folders, icon pack support and other stuff
RAM is about 150 MBytes free with Theme Chooser enabled
Thanks to: (in no particular order)
Flinny
Flemmard
guest1
mosi110
kylon
szezso
nadlabak
Sources:
Local manifests: https://github.com/NeverGone-RU/Andromadus
Device tree: https://github.com/Andromadus/android_device_htc_vision
MSM7x30 common: https://github.com/Andromadus/android_device_htc_msm7x30-common
Kernel: https://github.com/Andromadus/htc7x30-3.0/tree/andromadus_4.3

How to install?
The usual process, nothing different here.
1: backup
2: wipe
3: install the ROM
4: install Google Apps. I prefer PA GApps "Mini Modular Packages".
How do I report bugs?
Now that's important.
I've set up an issue tracker to prevent cluttering this thread.
Keep in mind that a bug report without a logcat/dmesg or at least a precise description of a bug wouldn't help anyone.
If you stumble upon anything strange — try to reproduce it (and save a logcat, just in case).
Pro-tip: use "adb logcat -C" to colorize the output and make it easier to read! (not sure if this works on Windows, though)
Unfortunately, there are bugs that are caused by CM devs or Google (GApps are buggy, too). I'll close these bug reports, because I just can't fix that. I'm not a magician
Issues we already aware of:
EGL: flashy CRT animation (disable it) and buggy hwcomposer (icons/widgets suddenly blacked out is also caused by it). This was the major show-stopper.
Switching SELinux to Enforcing mode will instantly make the phone freeze. Don't do this!
Trackpad wake/unlock doesn't work, and there's no way to enable it. I use "pure" CM frameworks_base that doesn't have these features baked in.
Camcorder FCs when you try to un-pause video recording.
[Fixed] AOSP Keyboard FCs if you don't install GApps — install them
[Fixed] Mobile data is unstable — edit build.prop to fix the issue.
Issue you should be aware of: (non ROM-related)
Don't buy Samsung laptops, they have display hinges made of a sh*tty plastic.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Give me the download, already!
Google Drive link for 4.3.1: https://drive.google.com/file/d/0B5ahny5WGurFWDhhRnRWUDRMdUE/edit?usp=sharing
MD5 checksum: 657c81b1f46fd2987a175fa5ad66547d
Please don't make additional mirrors. Instead, ask me to mirror the file myself.
Why? I need to keep control of builds, and remove/replace them if something goes really wrong.

Kitkat?
While I still prepare my build environment for Kitkat and applying some patches to make it compile, you can have a build provided by guest1.
Initially, it was built purely for ringtone bug testing (factoid: every other htc msm7x30 device has ringtone shutting off randomly. I don't know why), but I think that'll do it for giving you an overview of what does CM11 look like at the moment.
This is even more unstable!
4.4 is also slower for some reason (probably because of different qcom_display repo used for it).
I did almost no tests with it, so there's probably a lot more to fix.
Google Drive link for 4.4: https://drive.google.com/file/d/0B5ahny5WGurFS1Z3N3N6V0xsSVk/edit?usp=sharing
MD5 checksum: 4ba38cc9fe4879687d0a279d0fbc0ced

Once this gets a tad more stable I am going to for sure try this out. I just flashed a fresh rom today and I'm trying to limit the fact I flash a rom at least 7-15 times a week (it's addicting, what can I say).

Re:[ROM] [14-11-13] Andromadus - CM10.2 - Vision
@NeverGone\RU you are a beast. Of course also thanks to @Flinny and the whole andromadus team. Does this use the same htc7x30 andromadus 3.x kernel as the previous builds?
Downloading now Btw hopefully I can get some logcats

HTCDreamOn said:
Does this use the same htc7x30 andromadus 3.x kernel as the previous builds?
Click to expand...
Click to collapse
Yeah, just a different branch (with SELinux enabled).

OMG!
OMG , I never expected KK for our device, btw i was too waited for this without any expectation
Once again thanking the guys who working on our devices :laugh::good:

great work Nevergone, thanks. I hope in some day we get Kitkat. I'm test it at this weekends.

great to see this, have downloaded and will give it a shot shortly. Have you, NeverGone, or have others, got an MD5 we could check against...I'm happy to post mine as a starting point:
657c81b1f46fd2987a175fa5ad66547d
---------- Post added at 07:54 PM ---------- Previous post was at 07:54 PM ----------
great to see this, have downloaded and will give it a shot shortly. Have you, NeverGone, or have others, got an MD5 we could check against...I'm happy to post mine as a starting point:
657c81b1f46fd2987a175fa5ad66547d

NeverGone\RU said:
Kitkat?
Wait for it.
Actually, this post is reserved for KK builds.
Click to expand...
Click to collapse
Cool!
I'll wait for KK if I can...

I think, that we'll wait for kitkat for a long time yet... desire z isn't as famous as earlier, community is less and phones with HW qwerty as well.
BUT I'm a still faithful user and BIG THANKS for this great piece of rom and great work from devs! Thank you!

great news!!!! thanks hitted

Let's not clamor for Kitkat yet. The Galaxy S4 got a stable-ish build of Kitkat just a few days ago, and it'll take a while for unstable builds to come out from the official CM tree. When that happens, development will trickle down here.
I mean, I would like to maintain my always-faithful-if-slow backup phone. It's gotten me through some times when my other primary phones went dead on me.

I get server connection errors in the Google Play store with this ROM and the linked GApps. Is anyone else having this problem?
I can actually connect to the store fine, it's the downloading or updating of apps that it errors out on.

Fafhrd42 said:
I get server connection errors in the Google Play store with this ROM and the linked GApps. Is anyone else having this problem?
I can actually connect to the store fine, it's the downloading or updating of apps that it errors out on.
Click to expand...
Click to collapse
Go to settings --> Storage --> And I think there should be a cache storage size for the sd card+internal rom, clear those, sign out of your google account then sign back in! At least I think those are the steps, I can't fully recall

That did it! Thanks! In all the years I've had an android phone I've never had to do that after flashing a rom.

Fafhrd42 said:
That did it! Thanks! In all the years I've had an android phone I've never had to do that after flashing a rom.
Click to expand...
Click to collapse
Yeah, from my research a few days ago on that problem it seems to be common in 4.3 roms for some unknown reason. I'm glad I could help!

I made an issue tracker.
That'd be easier to track bugs and get feedback without constantly quoting each other on forum pages. (because forums are linear)
I also decided to try to adapt some Sony/Samsung MSM7x30 changes. Maybe they've been more successful than we were?

If I were you, I would give up developing Android 4.3 and focus on preparing 4.4. But I am not a developer and I possibly don't know something so...
Anyway, thanks for making Android 4.3 happen on our Desire Z and good luck!
I will wait for 4.4 though.

TheReduxPL said:
If I were you, I would give up developing Android 4.3 and focus on preparing 4.4. But I am not a developer and I possibly don't know something so...
Anyway, thanks for making Android 4.3 happen on our Desire Z and good luck!
I will wait for 4.4 though.
Click to expand...
Click to collapse
Valid point.
The thing is, 4.4/CM11 is in early stage yet, and it will still need the same work I'm doing for 4.3 (plus, camera is broken on other MSM7x30 devices).
4.3 is at least able to boot

[Alpha][20141228] CM12 for the Xperia Z3

CyanogenMod 12 for the Xperia Z3
[STATUS]
Some vital functionality is still missing, mobile data being one of them and the camera being another. This build is therefore primarily targeted at developers and experimenting users.
NOTE: After booting up, try toggling wifi to avoid sleep issues.
[Working]
Touch Screen
Cellular radio
Bluetooth
Wifi
NFC (Temporarily broken)
Speaker audio
Adaptive Brightness
Gyroscope (Auto rotation)
Charging
Screen sleep (In lack of better term)
++++
[Not Working]
Mobile Data
Camera
Probably a lot of bugs and annoyances
++++
[Changelog]
>20141228
-- Updated CM12 sources with the new telephony stuff
>20141226 v2
-- Now using open source libril
>20141226
-- Android 5.0.2
-- 23.0.1.A.5.77 vendor libs update
-- New Audio HAL
-- Bluetooth improvements
-- Added missing proprietary service (modem related)
-- Thermanager updates (Results in very dim recovery though, sorry about that. Will fix asap)
-- NFC broken (Will get that up again, just didnt make it a priority for this build)
-- gsiff daemon still crashing. Remove it to improve battery life significantly.
>20141217
-- Added NCI HAL Module (credits: chirayudesai). NFC now works! (yay!)
>20141211
-- Kernel updates. Added several new modules.
> 20141210
-- Fixed the keymaster issues. systemui no longer crashes and security settings are now available. Bluetooth improvements.
> 20141209
-- Updated device config, kernel and CM12 sources (check Github for details)
> 20141201
-- Initial Release
[Installation Instructions]
Note: Do not flash unless you know what you're doing.
STEP 1 - Push the .zip file to your /sdcard partition. Boot into recovery and flash it. Make sure to do a full backup first. If you want to go back to a non CM12 ROM please flash a CWM recovery featured boot.img as the CM12 recovery is not exactly functional.
STEP 2 (Optional) - Flash Google Apps (Download Link)
[DOWNLOADS]
cm-1220141228-UNOFFICIAL-leo.zip
cm-1220141226-UNOFFICIAL-leo-v2.zip
cm-12-20141226-UNOFFICIAL-leo.zip
cm-12-20141217-UNOFFICIAL-leo.zip
cm-12-20141211-UNOFFICIAL-leo.zip
cm-12-20141210-UNOFFICIAL-leo.zip
cm-12-20141209-UNOFFICIAL-leo.zip
cm-12-20141201-UNOFFICIAL-leo.zip
NOTE: Be sure to wipe data if you're coming from a non-CM12 ROM.
[SCREENSHOTS]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[THANKS]
A big thanks to nycbjr for sparring with me and to everyone here who's spending their time testing, giving feedback and shoehorning in fixes and hacks.
XDA:DevDB Information
CyanogenMod 12 for the Xperia Z3, ROM for the Sony Xperia Z3
Contributors
Untouchab1e
Source Code: https://github.com/Zyg0te/android_device_sony_leo
ROM OS Version: 5.0.x Lollipop
ROM Kernel: Linux 3.4.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-12-01
Last Updated 2014-12-28

Just a suggestion, maybe you can have a look at krabappel's build, he has got system.ui working

gallardo5 said:
Just a suggestion, maybe you can have a look at krabappel's build, he has got system.ui working
Click to expand...
Click to collapse
Yep but that's AOSP and not CM12. I also have AOSP with a functioning systemui as well as a working modem.

@ Untouchab1e
Thank you very much for your work! I really appreciate that. I can't wait to have a fully working version!

owh my goodness, I've been waiting for a long time. thank you Mr untouchable.. I'm speechless. I can't wait to see cm12 running on my z3..

btw.. first leo cm12 is now available from fxp blog

iBuzman said:
btw.. first leo cm12 is now available from fxp blog
Click to expand...
Click to collapse
Where ? Link...

iBuzman said:
btw.. first leo cm12 is now available from fxp blog
Click to expand...
Click to collapse
I have tried this, WiFi is working but systemui crashes every time you lock your phone.
---------- Post added at 01:17 AM ---------- Previous post was at 01:17 AM ----------
SweDunda said:
Where ? Link...
Click to expand...
Click to collapse
Available here http://forum.xda-developers.com/showthread.php?t=2959665

I have fixed system ui issues by adb pushing SystemUI.apk from my latest 5.0.1 r2 lollipop aosp build - so I presume any aosp lollipop systemui apk will fix it. (all crashes gone - screen off charging now as I type)
Maybe this is a quick and dirty fix for your builds @Untouchab1e?
After pushing modem files, mba files and ril libs to fxp build my cellular connected up - meaning wifi, radio and SystemUI incl Screen Off/On all working :good: more details posted over in fxp cm12 thread

iBuzman said:
I have fixed system ui issues by adb pushing SystemUI.apk from my latest 5.0.1 r2 lollipop aosp build - so I presume any aosp lollipop systemui apk will fix it. (all crashes gone - screen off charging now as I type)
Maybe this is a quick and dirty fix for your builds @Untouchab1e?
After pushing modem files, mba files and ril libs to fxp build my cellular connected up - meaning wifi, radio and SystemUI incl Screen Off/On all working :good: more details posted over in fxp cm12 thread
Click to expand...
Click to collapse
Cool, wifi works too? Thought the bcmdhd wifi hal was broken for all bcm devices. Nice.

Untouchab1e said:
Cool, wifi works too? Thought the bcmdhd wifi hal was broken for all bcm devices. Nice.
Click to expand...
Click to collapse
yep ?

Yup, wifi seemed rock solid - 3G/LTE was totally on the fritz tho .. But, getting closer gents!

Xperia Z3
hey guys follow ibuzman's solution most of the functions work except one flawed the security under settings is inaccessible

yeah I have that too..
I used adb install to get around not having unknown sources checked.

nolihowell said:
hey guys follow ibuzman's solution most of the functions work except one flawed the security under settings is inaccessible
Click to expand...
Click to collapse
That is due to the AOSP systemui.apk I believe. The reason for the systemui issue in the first place is that the keyguard doesnt connect with the service and hence security settings wont work because the keys cant be handled.

I'll definitely root my z3 if this Rom works and can be used for day to day use..

Hi. I cant download the rom as link seems dead. And thats why im asking, does the sound work with this rom? I flashed cm12 from fxp thread and it doesnt, so I was jist curious, and I will flash it straight away if sound works

gallardo5 said:
Hi. I cant download the rom as link seems dead. And thats why im asking, does the sound work with this rom? I flashed cm12 from fxp thread and it doesnt, so I was jist curious, and I will flash it straight away if sound works
Click to expand...
Click to collapse
Link updated.

Untouchab1e said:
Link updated.
Click to expand...
Click to collapse
Flashrd, for now most of things working, except camera and mobile data bluetooth is not very stable as it has problems with connecting, but once connected (after few tries) its fine
Just to make everything clean, maybe some of issues are my fault because I fkashed something that I should not i fully wiped and flashed your rom, then cm12 gapps from here ( https://s.basketbuild.com/gapps ) and them modem.zip from this thread.
Edit: after some time with it (I will probably leave it as daily driver until it gets on my nerves enough ) I found few other issues:
Some apps have compability issues (e.g. xda loads, xperia z3 forum is still fine but when I go to subforum like advanced development, play store services crashes, and so does xda app. Everything loads in the background, I can see zverything behind the xxx has crashed message, but as soon as I press ok, it quits. Another one is facebook messenger, it is fine when browsing through conversation, but when I try to open one conversation, be it in app or from those small heads, it crashes).
Another issue is youtube (advertisements of course work, but the video I wanted to watch does not, it says "cant connect, press to try again")
Another issue is that every time I try to uninstall or clear data from any app, the phone does a soft reboot (shows bootanimatoon immediately)
The last issue I found is that bluetooth connects to my bluetooth headset, but sound stops working, just like in fxp CM, it just stays at 0:00 no matter what track I try to play.
Others issues are known, like camera or mobile data signal drops entirely for few seconds from time to time but I think it is also known.
I will keep testing it as for now it is workibg enough to be my daily driver so will keep it updated with anything that I find
Found another thing, but I wont really call it an issue and it made me laugh a bit. No matter how full your battery is, phone just keeps saying its low. Battery life is fine, but notification comes after few seconds of cleaning it, and it comes every time. Right now the notification says " battery is low! Battery level : 82%" but lets just call it a laughable feature

@gallardo5 thanks for your detailed feedback. Ive build and uploaded a new build. It would be great if you could check it out and see if there are any changes or improvements. I havent done any huge modifications. But I have been tweaking around with vendor libs and the device configuration and of course, updated CM12 sources which at this point can have a significant impact on functionality.
Thank you. I really appreciate everyone's effort to make this work! I am sure we will get CM12 running well together

LineageOS 15.1 and Treble Progress

Hey everyone
So... because i rather made a "big" of breakthrough today, im gonna share my progress on various projects.
My progress on LineageOS 15.1 (and GZOSP and CrDroid, didnt try more yet) all work pretty fine, basically everything works. Theres just 1 annoying thing (which im hunting down since easter). It can crash rather often during boot. Means: it freezes and then reboots.
See for yourself:
https://www.youtube.com/watch?v=rUUopOYDYjs:
https://youtu.be/l7HEMIreVwE:
A video of CrDroid (recorded with my OnePlus 2 lol)
https://youtu.be/d5XGM9xCrqE:
I also managed to create a seperate vendor partition (yes, i actually repartitioned) by making /system smaller (had 1.5GB left even though on full stock rom, not debloated a single bit). Made it 512MB in size.
This allowed me to actually use it (mount in kernel), and i managed to (nearly) bring Treble support to the V30
With nearly i mean that the GSI boots, but the process "system" crashes (2 libs missing, need to see how i get them to /vendor, currently they are in /system of my lineage build)
The libs are called [email protected] and [email protected]
Here a video of LOS15.1 with Treble Check (yes, that prop can be faked, i know, and its only half true so far i guess)
https://youtu.be/MUNij0sspKM:
What im hoping to achieve with this post:
1) Maybe get a few more people interested in testing (i really need more testers, only have 1 atm, and i need my phone rather often)
2) share my progress, making people hope that the V30 development isnt completly dead
3) Hopefully get a the attention of a few more devs, so we can figure those boot issues out (the reason i didnt release it yet, as it sometimes also freezes when you have gapps flashed)
best regards
SGCMarkus
PS: Ask all the devs you know, maybe someone knows the issue too, and knows a way to fix it
PPS: idk why the embedded youtube links dont work, but i put the links there on their own

Expect it to be used everyday! Beautifully

Wow good work. Hopefully tmobile varient will get recovery someday [emoji849] miss experimenting with roms. Stock on v30 is good with a theme but sometimes i miss custom roms
Sent from my LG-H932 using Tapatalk

So.. tested a build from last night fast before i rushed to the train ?
The GSI now boots successful and seems to be stable. Everything except haptic feedback/vibrator seems to work (i know the reason for that, as it loads the aosp implementation first, but the v30 needs the lge implementation in vendor)
Only saw wifi, bt, nfc was on, had signal (and asked for sim pin), and checked if camera had a preview, it did
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Wow that is really impressive, so if I got you right you have treble working completely beside the vibration?
How stable does it run after a successfull boot?
Is it possible to switch between Stock and Linage after repartitioning?
Are you planing to release pre alpha images too for testing?
I ask too many questions I guess

Doblix said:
Wow that is really impressive, so if I got you right you have treble working completely beside the vibration?
How stable does it run after a successfull boot?
Is it possible to switch between Stock and Linage after repartitioning?
Are you planing to release pre alpha images too for testing?
I ask too many questions I guess
Click to expand...
Click to collapse
stock works normal (use that for now as daily driver), it just ignores the new partition. Also had 1.5GB or so empty space before repartitioning in /system, so that shouldnt be a problem if i used 512MB for that.
Idk how stable it runs yet... i just tested if it boots without errors this morning, restored my backup, and left for university xD
You can have Lineage builds (without treble), but its annoying if it sometimes take 20 tries to boot... and sometimes boot successful 2 or 3 times after another.
Those with treble need (for now manual) repartitioning... have to figure out how todo that without a Linux PC (vm also works)

SGCMarkus said:
stock works normal (use that for now as daily driver), it just ignores the new partition. Also had 1.5GB or so empty space before repartitioning in /system, so that shouldnt be a problem if i used 512MB for that.
Idk how stable it runs yet... i just tested if it boots without errors this morning, restored my backup, and left for university xD
You can have Lineage builds (without treble), but its annoying if it sometimes take 20 tries to boot... and sometimes boot successful 2 or 3 times after another.
Those with treble need (for now manual) repartitioning... have to figure out how todo that without a Linux PC (vm also works)
Click to expand...
Click to collapse
I would be interested in testing the treble ones if possible, if you can guide me how to do the repartitioning or what tools to use that would be no problem for me.
I solely use Linux on my PCs (Arch if that matters) so that is no obstacle for me.
A nice and user solution would probably be a flashable .zip file for TWRP which does the repartitioning directly on the device.

Excited
I'm really excited to get Lineage OS onto my V30. But I just don't think I can make the transition until the Camera is ported. The the only app which can utilize both sensors, 4k video recording and laser focus. I use the ported G camera for pictures right now because of HDR+, and it can record 240fps slow mo. But it can't record 4K video. There is just nothing which can fully replace the stock LG app and use all the camera's hardware properly. Even things like open camera can't use Laser focus. So I just can't make the switch until the LG camera is ported. Also I hope that the QuadDAC will be supported.

GSIs also dont seem to have the boot issues for some reason....
So its neither the ramdisk, nor kernel, nor vendor files.... something in my device tree is wrong then xD
PS: added a poll

Hi SGCMarkus,
thanks for your hard work for this device!
A stupid question: when the device will have your treble suport(with partition modified) will be possible to flash crdroid instead GSI or LOS? the other rom use the /vendor partition?
Thanks again for your awesome work!!

Just wanted to add my 2 cents. Definitely extremely excited about a fully stable and working LineageOS. Even if it doesn't have Trebble. Stability is definitely a must (at least for me) since this phone is a daily driver, but I would love more than words could convey if we had a working AOSP type ROM for this phone. Please keep up the solid work, and thank you in advance! As a dev myself (not android, sorry) who has done volunteer work, I know how important the props are to keep you motivated. So again, awesome job so far, and thank you!

okaiuz said:
Hi SGCMarkus,
thanks for your hard work for this device!
A stupid question: when the device will have your treble suport(with partition modified) will be possible to flash crdroid instead GSI or LOS? the other rom use the /vendor partition?
Thanks again for your awesome work!!
Click to expand...
Click to collapse
All GSIs should work, currently booted a LineageOS GSI, also tried the AOSP one
PS: found the fix for the vibrator... LGs implementation is just stupid lol
Needs ro.product.manufacturer set to LG or LGE, but GSIs dont have that.... only ro.vendor.product.manufacturer is set to LGE, but that isnt enough...

SGCMarkus said:
What im hoping to achieve with this post:
1) Maybe get a few more people interested in testing (i really need more testers, only have 1 atm, and i need my phone rather often)
Click to expand...
Click to collapse
Hey SGCMarkus,
First Off.... Amazing Work!!!!! Rly nice to see, that there is some developing going on. Cant explain, why this phone is like beeing dead to devs.
To get to the Point... I would imediately Stop setting Up my Linux Dev system and would Test 4 you. It is more important to Help the community getting some kickass Roms rather cooking for myself
If you are interested, Just leave me a PN with dl-link and additional Infos.
So Long,
Please keep Up that great Work.
Tipnuck