Android L: Discussions, Rumors, Android L Developer Preview Port Talk - ONE General

{
"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"
}
Android L
At Google I/O 2014, Google revealed new Android L, set its release date for this autumn and also published an for Nexus 5 and Nexus 7 (2013).​
Links, Reads, Videos
Android L Developer Preview | Android Developers
Android L Developer Preview hands-on by engadget
Top 5 Best Android L Features! - Video by MKBHD​
Android L Features
Material Design
Document-Centric Recent Apps Panel
Enhanced Notifcations (Heads-Up& Lockscreen)
Project Volta (Battery Life Saver)
New Runtime: Android Runtime aka ART
BLE Peripheral Mode
64-bit Support
New Features for Game Developers
Advanced Camera Capabilities
Android L Features | wikipedia.org
Android L Developer Preview Port for OnePlus One
Check this post from time to time!​

Status Updates: Android L Developer Preview Port for OnePlus One
Updates from @iH8ra!n (me):
8.)
iH8ra!n said:
This is how my Nexus 4 looks like!
Thanks to @sykopompos, his amazing Android 'L' Porting Team and Nova Launcher!
Simple. Awesome. Material.
Can't wait to set this up on my OnePlus One (bacon)!
Click to expand...
Click to collapse
7.)
iH8ra!n said:
Hi Dudes!
sykopompos said:
Click to expand...
Click to collapse
This is great news, isn't it?!
Cheers, Best regards and Stay tuned!
Click to expand...
Click to collapse
6.)
iH8ra!n said:
Hi Dudes!
I am finally done with the diff files!
Once a stable base for the port is worked out, these lists will serve as a list for (proprietary) files which need to be swapped out in order to work with one's device.
Best regards, cheers and Stay tuned!
Click to expand...
Click to collapse
5.)
iH8ra!n said:
Hi Dudes!
@sykopompos and I decided to first base this port off of LPV79, upgrade it then to LPV81C and after that, we'll be merging it with AOSP again, so that it'll become more than a port - the same procedure which was done with the Android L Developer Preview port for Nexus 4!
Currently, @sykopompos and I are working on a diff between the /bin and /lib files for the Nexus 5 (hammerhead), the Nexus 7 (flo) and the OnePlus One (bacon). Jump in if you're into it, because work gets done faster when more people are helping!
P.S.: If you are (not) checking this thread often but/and you are only interested in Status Updates regarding the port, just keep checking this post!
Click to expand...
Click to collapse
4.)
iH8ra!n said:
Hi Dudes!
As my Laptop won't be reachable for me this weekend, but you are going to work on the port, I am just sharing what we have right now!
The following is only intended for developers and porters!:
It is flashable but not fully bootable
(edits to the ramdisk are necessary; contact @sykopompos for more info)
It is Android LPV81C for Nexus 5 with proprietary files from OnePlus One added
The kernel (boot.img) is taken from official AOSP 4.4.4 KitKat for OnePlus One
The build.prop and the updater script are edited for OnePlus One
DOWNLOAD
Click to expand...
Click to collapse
3.)
iH8ra!n said:
We are the testers, and everyone can help!
Fortunately, @sykopompos is so kind and explains any step I can overtake for him so he can focus on more serious stuff!
Port is now really progressing!
I am currently flashing test builds to logcat and @sykopompos is focusing on init for kernel right now, so that L will boot properly.
By the way, the.port will be based on LPV81C!
Click to expand...
Click to collapse
2.)
iH8ra!n said:
ANY PRE-REQUISITE FOR THE PORT CAN NOW BE FOUND HERE (my GitHub repo)!!!
ALL INTERESTED DEVELOPERS OR PORTERS SHOULD CHECK IT AND HOOK UP @sykopompos OR @iH8ra!n (me) FOR ANY FURTHER QUESTIONS REGARDING DEVELOPMENT/PORT PROGRESS!!!
Click to expand...
Click to collapse
1.)
iH8ra!n said:
It will be 'up-ported' from Nexus 5's Android L Developer Preview Image. As the OnePlus One uses the same SoC (Qualcomm Snapdragon 801), the same GPU (Adreno 330) and has the same resolution (1920x1080) like the HTC One M8, which is a Google Play Edition device which is the reason for why its device repo and kernel source is uploaded to Google's Git - this is the key, this port may not be this hard to do.
Click to expand...
Click to collapse
Updates from
@sykopompos:
16.)
sykopompos said:
sykopompos said:
Alright!!! Who is ready for a productive night???
...
....
.....
......
Not just yet, caffeine needs to kick in first
Game plan is like so, sync n5 template into a new fork for a bacon rebase while I fix hammerhead (thanks @ramjet73 ) then over to flo to fix the camera there ( thanks @bitstra ) then over to deb to fix the camera there (same solution as flo and was tested) then we will track down the missing file according to @jayfallen 's radio log.
By then bacon should be synced up into it's own fork and I will go buy a pizza. Then time to crack open the bacon and get working on L for it. Once we get that booting, then I can work through the other issues and since I have a loaner to test on personally, just keep going at it
Click to expand...
Click to collapse
There is the game plan but first a question for you guys as a need to know bit of info. How do you get to recovery? Please don't tell me it is finger gymnastics like on the g3.
I will properly have to do several battery pulls over the course of my testing and working.
@iH8ra!n did a ton of prep work already on pulling all the proprietary files and comparing them against hammerhead while I was working on a solid base from hammerhead to use so make sure you thank him because that cut down the research time that I would have had to do.
First we will start with the aosp boot image to get our kernel, bootcfg and ramdisk to put together. We will merge in the permissive sepolicy from hammerhead (no big jumps here just yet on rewriting anything till we get booting, that is an optimizing thing) then once that is out the way, start working on the system, we are going for a basic boot here (it will come with lots of fc that I will have to work through) then once we got the basic, I can't test radio functions cause of the bad Sim pins so I will have to take a break there and get feedback from you guys.
Click to expand...
Click to collapse
15.)
sykopompos said:
You should see the latest build of my L on the n5 now. You guys are in for a treat on the 1+1 soon.
Ramjet figured out the camera bug on the n5, bitstra figured out the camera bug on the n7 so when I get home I'll merge those fixes in, put out a test build for them to approve and then all the nexus devices are done for right now and will go up as official builds. Then I can focus solely on you guys, the g3 (will be basically going up alongside of you guys or maybe even forked from here) and then I'll go back and redo the m7
Click to expand...
Click to collapse
14.)
sykopompos said:
Alright. All my nexus builds got an update tonight now I can push out and start work on this tomorrow
Click to expand...
Click to collapse
13.)
sykopompos said:
Well the n7 and n5 bases are working, just trying to solve the broken su issue on 81c before we go farther with the templates.
I should have my loaner 1+1 by Wednesday or Thursday so we can start plugging away at it.
Figure I will do mako tomorrow, flo, deb and hammerhead also a bit but probably more on Tuesday. (Hammerhead will take the longest time to track down how I broke the camera before so testing new proprietary bins in batches)
I still gotta get to rewriting the m7 boot.IMG like I will have to do for the 1+1 so that will take a little time but it won't take long to get it booting on the base boot.IMG before my rewrites
EDIT (1): Got a fully permissive, root enabled base for n7 and n5 now
Click to expand...
Click to collapse
12.)
sykopompos said:
Right now we are going through a rebuilding phase. My past week of going back through every thing has been eye opening to say the least on a issue with the base so I'm going to demolish the original bases and start back over fresh with the original preview 81c images and build it up from there.
Most of the work will be going on in the mako thread.
I also wanna thank tiny for joining in here. He has been working on the m7 port and his help will be greatly appreciated here also. Once I get the bases together and the loaner 1+1, this should be a breeze
Click to expand...
Click to collapse
11.)
sykopompos said:
N5 is almost done being ported with a few more things to work out but enough for me to use it as the base for the 1+1 so once my sources get done syncing with github, it is time to get to work
Click to expand...
Click to collapse
10.)
sykopompos said:
Still merging the n7 onto the same base as the n4, once that it done, I'll merge the n5 to the base and by then, my loaner should be here so I can skip the basics and jump it right up.
I have been directing @iH8ra!n through all the prep work so he is getting it prepared for me so I don't have any research to go through and can blast right through this
Click to expand...
Click to collapse
9.)
sykopompos said:
sykopompos said:
Going with Hansel and gretal for the theme. Gonna be laying out some bread crumbs and basically merging mako into a flo repo, then taking it back to the flo preview and then merging it back up to where we are with bunny but leaving bread crumbs on the way back up, then clone flo into deb and make deb work plus rebase the m7 guys. Then do the same thing over with hammerhead, then clone it and work up g3 and 1+1. Then merge them all up to 81c with the new frameworks and apps even though we aren't getting much and then merge in all the newest binaries on all builds.
This way we have a common base and they are all at the same place then we can work on merging more aosp in since I can go across the board to every device that it is ported to. I should talk to the lg gee guys and the g2 guys and get them in the same place.
Figure it is a clean up and housecleaning week and that is what baked witch is
Click to expand...
Click to collapse
Here is my game plan while I wait for the loaner 1+1. It probably won't be till the weekend that I get it so that gets me the week to do all this
Click to expand...
Click to collapse
8.)
sykopompos said:
Some progress was made on the m7, cellular radio is finally working now. The bunnies are multiplying
Click to expand...
Click to collapse
7.)
sykopompos said:
Gonna work on the m7 for a bit, seems with the permissive sepolicy we might have caught some headwind with all new selinux denials that weren't there before which means hardware that wasn't trying to start up before is now trying to start and I just need to direct it where to go. This is a possible big step for getting non nexus devices working
Click to expand...
Click to collapse
6.)
sykopompos said:
Finally, friggin finally I got a fully permissive sepolicy on the n4 and not the hack that it was before that had to wait to kick in till after all the hardware was being denied.
Just pushed out b5 for the n4 so now that is done and can switch focus and start work on this
Click to expand...
Click to collapse
5.)
sykopompos said:
Battling a couple daemons on the n4 and getting ready to turn selinux back on for it plus cleaning out some unneeded crud on it.
Do you guys know if there is anything changed in the root files for the specific version of cm vs what is in the available source code? I mean the ramdisk because I will need to compile it and the init to incorporate the changes I need to make to have selinux play nice
Click to expand...
Click to collapse
4.)
sykopompos said:
Still doing a bit of homework and sorting through everything. I only got about 2 hours of sleep in the last 31 hours since I'm switching back to night work so I won't be up too late working on it but I should have something late tomorrow to test out and see where we are.
We will see if we need to change the caf video drivers in the kernel then to play nice the n5 base (can snag the drivers out of the n5 preview kernel source) after I get a first dry run together
Click to expand...
Click to collapse
3.)
sykopompos said:
I'm still chasing a bunny on the n4 so I can correct the m7 problems so I haven't gotten time to look at the 1+ too much yet.
There will probably be some backporting from hammerhead preview kernel to get everything flowing right but it shouldn't stop anything from booting in the mean time.
I gotta fight with selinux a bit again but this time instead of hacking around it, I'm actually going to get it working correctly
Click to expand...
Click to collapse
2.)
sykopompos said:
After playing around on the g3 last night, I saw what I wanted to see. The g3 right now at this point needs some serious housekeeping before it can go anywhere but the one plus one is a lot cleaner of a base without too much junk in it that needs to be cleaned out. It is definitely possible to get L up and ported over for the one plus
Click to expand...
Click to collapse
1.)
sykopompos said:
I'm just doing research at the moment but it seems like the 801 uses the same general board as the n5 just in what I am looking at with my g3 that I just got and combing through lg's source. So at least it shares a cousin which will make it possible. No promises on anything yet, I'm gonna be seeing what I can actually do with the g3 and if so it can share the same base
Click to expand...
Click to collapse

[L][5.0][PORT] Android L 5.0 Developer Preview port for OnePlus One (bacon)
INFO ABOUT THIS STUFF
DISCLAIMER
Code:
/*
*This port is based off of a not yet finished and unstable Android version - expect some quirks!
*
*Your warranty is now void.
*
* I am not responsible for bricked devices, broken hearts,
* thermonuclear war, you getting fired because the alarm app failed, or
* unfulfilled sexual partners. 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 point that finger back at you and laugh. */
WHAT IS THIS?!
This thread is the official Android L Developer Preview Port Thread for the OnePlus One!
This port is based off of Nexus 5's and Nexus 7's (2013) Android L Developer Preview System Images (LPV81C).
This port can be used as daily driver for the vast majority of Android users!
The series is called "breadcrumbs and bunnies" (witches come into the brew later).
The purpose of the series is to start fresh off of the LPV81C system images.
From the beginning, we'll be leaning out anything unnecessary and expand to other non-Nexus/legacy devices afterwards.
Give all your credits for this port to @sykopompos and the Android L Porting Team!
Android 'L'
At Google I/O 2014, Google revealed the new Android 'L', set its release date for this autumn and also published a Developer Preview for Nexus 5 and Nexus 7 (2013).​
WHAT'S WORKING
yet to be tested...
WHAT'S NOT WORKING
yet to be tested...
INSTALLATION INSTRUCTIONS
FIRST TIME FLASHING
Put the latest L-bacon-breadcrumbs-and-bunnies.zip file onto your One's Internal Storage
Reboot into Recovery (CWM or TWRP)
"wipe data/factory reset"
"mounts and storage" -> "format system"
"advanced" -> "wipe dalvik cache"
"install zip" -> "install zip from sdcard" -> choose the L-bacon-breadcrumbs-and-bunnies.zip and confirm flashing procedure
"wipe cache"
"advanced" -> "wipe dalvik cache"
"reboot into system"
first boot may take up to 10 minutes - please, be patient!
UPDATING
Put the latest L-bacon-breadcrumbs-and-bunnies.zip onto your One's Internal Storage
Reboot into Recovery (CWM or TWRP)
"wipe cache"
"advanced" -> "wipe dalvik cache"
"install zip" -> "install zip from sdcard" -> choose the L-bacon-breadcrumbs-and-bunnies.zip and confirm flashing procedure
"wipe cache"
"advanced" -> "wipe dalvik cache"
"reboot into system"
updating procedure may take up to 10 minutes - please, be patient!
DOWNLOAD
Android 'L' for bacon​
CREDITS
AOSP
Google
@zyr3x
@xsasuke
@ben1066
@iH8ra!n
@defconoi
@stuffynet
@adarshahd
@sykopompos
@shubhamchamaria
Android L Porting Team​

iH8ra!n said:
reserved #2
Click to expand...
Click to collapse
First!
Nice initiative, mate.

Good luck bro!

Really? Android L on the opo?
Inviato dal mio OnePlus One

I'm just doing research at the moment but it seems like the 801 uses the same general board as the n5 just in what I am looking at with my g3 that I just got and combing through lg's source. So at least it shares a cousin which will make it possible. No promises on anything yet, I'm gonna be seeing what I can actually do with the g3 and if so it can share the same base

Doesn't the Nexus 5 have the Snapdragon 800 processor instead of the 801?

erdal67 said:
Doesn't the Nexus 5 have the Snapdragon 800 processor instead of the 801?
Click to expand...
Click to collapse
It does but they are both 8974s, doing some research on it, it seems it takes the same basic code when it comes to the hal so it might be possible. I was able to replace all the /lib/hw over on the n4 port from aosp so it should be doable. I gotta do some more research of course and this is all early research so it most likely won't be that easy. I gotta dig through the code a bit more to be sure first though
Sent from my LG-D851
---------- Post added at 08:55 PM ---------- Previous post was at 08:44 PM ----------
http://www.anandtech.com/show/7846/...-snapdragon-800-and-801-clearing-up-confusion
Sent from my LG-D851

Great job on my N4 and Android L. Let these guys do what they do because if they can get it running I am sure it will be right... Thanks for all your efforts :good:

After playing around on the g3 last night, I saw what I wanted to see. The g3 right now at this point needs some serious housekeeping before it can go anywhere but the one plus one is a lot cleaner of a base without too much junk in it that needs to be cleaned out. It is definitely possible to get L up and ported over for the one plus
Sent from my LG-D851

Oneplus One port!
This would be amazing - was using your port for the Nexus 4 (and followed the amazingly long thread!) until it slipped out of my hand and smashed... Luckily, received an invite for the Oneplus one the day before though so got one of these... The only thing it's missing is the Dev preview!!
Would be amazing if you guys could manage a port. I can't help with much but can do the usual n00b stuff like giving feedback and testing... You proved 1000 people wrong with N4 - do it again!!

OneXoid said:
This would be amazing - was using your port for the Nexus 4 (and followed the amazingly long thread!) until it slipped out of my hand and smashed... Luckily, received an invite for the Oneplus one the day before though so got one of these... The only thing it's missing is the Dev preview!!
Would be amazing if you guys could manage a port. I can't help with much but can do the usual n00b stuff like giving feedback and testing... You proved 1000 people wrong with N4 - do it again!!
Click to expand...
Click to collapse
Don't you mean 2 amazingly long threads when you count the general thread that I piggybacked on and took over plus the development thread.
I'm not promising anything on the one plus one, I don't have one so that does limit my ability to work on it plus I haven't fully gone through everything but it does seem like it is possible using the n5 developer port. There really is so much that can actually be done with the developer preview as a base since most used tools are not working on L yet and without L source it is difficult to get things to mesh right.
I won't be dedicating that much time to this as I have multiple projects still going including the n4 port that need to be finished up plus my hours at work will be picking up. Once I do some code reviewing I will have a better idea of what direction to take it on how to get this working.
Sent from my LG-D851
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
Oh BTW, I have gotten multiple offers of a invite to buy a one plus, I just don't have the cash right now to get one
Sent from my LG-D851

sykopompos said:
Don't you mean 2 amazingly long threads when you count the general thread that I piggybacked on and took over plus the development thread.
I'm not promising anything on the one plus one, I don't have one so that does limit my ability to work on it plus I haven't fully gone through everything but it does seem like it is possible using the n5 developer port. There really is so much that can actually be done with the developer preview as a base since most used tools are not working on L yet and without L source it is difficult to get things to mesh right.
I won't be dedicating that much time to this as I have multiple projects still going including the n4 port that need to be finished up plus my hours at work will be picking up. Once I do some code reviewing I will have a better idea of what direction to take it on how to get this working.
Sent from my LG-D851
---------- Post added at 06:08 PM ---------- Previous post was at 06:07 PM ----------
Oh BTW, I have gotten multiple offers of a invite to buy a one plus, I just don't have the cash right now to get one
Sent from my LG-D851
Click to expand...
Click to collapse
Why don't we just raise some funds onto your PayPal, so the process could speed up a bit? We won't get you more time though, so if you have other commitments, that's fine...
Sent from my One using Tapatalk

boober78 said:
Why don't we just raise some funds onto your PayPal, so the process could speed up a bit? We won't get you more time though, so if you have other commitments, that's fine...
Sent from my One using Tapatalk
Click to expand...
Click to collapse
As much as the offer is appreciated, I can't guarantee anything on the port actually working yet and I wouldn't feel right if I couldn't get it going accepting donations for a device I have done no work on.
Does it make it easier, yes having the device and trying things myself to see is a lot easier than having it proxied to me but that shouldn't really hinder much. As I have no intent of developing a custom ROM for the one plus it also would put a hamper on it and if I accept donations for a device than I feel committed that I would have to.
Notice I said custom ROM, there is a development project once I finish up the ports I do intend on as a development resource for ROMs but not a direct ROM for the community. The one plus will be part of that project but so will many other devices, having as many devices as I can to directly do the work would help but it is not a requirement
Sent from my LG-D851
---------- Post added at 06:54 PM ---------- Previous post was at 06:41 PM ----------
My time constraints are because I am at a new job so I have to be a good boy and not slacking off too much with development work just yet. Once I get past my initial time here then I can slack off a lot
Sent from my LG-D851

What is the cost of a one plus one anyways?
Sent from my LG-D851

sykopompos said:
What is the cost of a one plus one anyways?
Sent from my LG-D851
Click to expand...
Click to collapse
300-350 USD plus shipping
Sent from my One using XDA Free mobile app

cchant said:
300-350 USD plus shipping
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
That's actually a pretty good price, I might consider getting one a bit sooner then I was planning to. I was gonna wait till around nexus time to get one
Sent from my LG-D851

sykopompos said:
That's actually a pretty good price, I might consider getting one a bit sooner then I was planning to. I was gonna wait till around nexus time to get one
Sent from my LG-D851
Click to expand...
Click to collapse
It's great as long as you can get an invitation to purchase.
Sent from my One using XDA Free mobile app

cchant said:
It's great as long as you can get an invitation to purchase.
Sent from my One using XDA Free mobile app
Click to expand...
Click to collapse
I've gotten several offers for an invite but I keep passing on them since there is a time limit
Sent from my LG-D851

Related

[UPDATE 7/24][ROM][BL1.2] Honeycomb Android Illuminate for The Gtablet\Zpad T2

Mod Edit: As stated by forum moderator jerdog in post 814:
FORUM RULES:
"Encouraging members to participate in forum activities on other phone related sites is prohibited."
The issue here is that directing traffic elsewhere is against XDA rules, and while there is no requirement to actively support your development efforts here at XDA, saying it probably won't be supported at XDA and that they can get support on your forum is kind of low and has been removed after requesting LBS do so - to which he did not after 2 days.
Click to expand...
Click to collapse
Thread closed.
will test this one. thanks
on v1.6
update 6.20.2011
~watching youtube on app and in browser are hit or miss, you should work on it to be more compatible
~so far so good though, thanks
update 6.21
~facebook FC's
will update this when i find more problems, when i find more time
ninditsu said:
will test this one. thanks
Click to expand...
Click to collapse
cool let me know what you think so far and if you let me know what the things are you missing the most and really need besides Flash. LOL but yeah I want to make this a Honeycomb that is a well rounded Android. So i want the advice of new features and such they have heard about.
Checked out the youtube video, looks pretty sweet. Will try it out tomorrow to see the improvements with hardware acceleration etc.
Edit: Let's see some benchmark comparisons between BoS and Illuminate.
Make sure you do the following
Unzip recover.zip and move recovery folder to /sdcard folder
The recover.zip file can be found in the Roebeets thread
http://forum.xda-developers.com/showthread.php?t=1078897
Regards,
Kenny N
Humm -- I got stuck with the boot loop . I am updating from 3588 stock recovery
Regards,
Kenny N
After half an hour struggling, I am able to load your HoneyComb edition. I am going to play around with it.
To make everyone's life easier.
Make sure you nvflash your device first using the following nvflash image
http://www.mediafire.com/?g7vorg66iiq29vm
1. Download the nvflash image above.
2. Download the recover.zip from (http://forum.xda-developers.com/attachment.php?attachmentid=596319&d=1305415712 ) and extract the recovery folder to SD root
3. Download this honeycomb image and rename it to update.zip and copy it to your SD root
4. nvflash the nvflash image
5. Reboot with Power + Volumn up. This should bring you to the new bootloader
6. Flash the SDCard external update.zip
7. Wipes
9. Restart
G'd luck . Thanks linuxboxsolution for his contribution. I will comment later.
Nice -- OpenGL is working perfectly. The benchmark from Quandrant is 1780. Not great but can't really complain
linuxboxsolution said:
Last Update 6/6/2011​
NOTICE: Flash still not currently Working please see
Click to expand...
Click to collapse
That's funny, I could have sworn you claimed previously to have "fixed flash" too!
Does enabling OpenGL break the stock browser? Or have you done something to work around this issue?
Is the main difference from Roebeet's HCAdam and Vegacomb mashup that is Bottle of Smoke that you have enabled opengl?
This looks very promising, currently running BoS 3.3 and was about to jump to 4.1 but I might have to try this first. My apologies if this has already been covered but what exactly is the difference between this ROM and roe's BoS? How were you able to get hw acceleration on here while BoS lacks it?
Thanks alot for your contribution, and I'll be sure to post my findings later today.
just wondering
so if the opengl is fixed, how come flashed is still hasnt fixed?
i believ robeet said the opengl is what makes flash doesn't work
OpenGL is enabled but not working.. it lacks on driver and without flash no OPENGL.. note on that..
and one more thing.. BoS has HWaccel and working, like gingerbread... the only problem is video HWaccel HD playback..
BoS 3.3 or 4.0+ boot quickly too, smooth UI like that, so i can't really tell what's the difference between the two, except for bootanimation.. LOL
I, for one, appreciate your efforts
Going to start posting in XDA's GTAB forums, at least sporadically. I think enough time has passed and things have changed around here (ie a lot of 1.2 mods are popping up, which I think is a good thing). Plus I'm not really seeing the moderator "changes" that were heavily present in April. So maybe things are back to normal. Maybe.
With that in mind, I wanted to say that your efforts are much appreciated - the end goal is to get a good working HC ROM for the users out there and if you have the ear of some people to make that happen, then that's what counts. I already mentioned in Slatedroid that I plan to pull back a bit after this month with modding the GTAB, so any extra dev / modding work is ALWAYS appreciated, imo.
Thanks again.
Looks awesome, will flash once I get my new PC built >
Thanks roe
So first of all thank you for your work.
But this is different from bottle of smoke because it enables OpenGL right?
Any other changes?
I hate to be a Richard but, can we get some screenies fam?
cgingermany said:
I hate to be a Richard but, can we get some screenies fam?
Click to expand...
Click to collapse
Not quite sure what that means, but if you want to see what it looks like, you can watch the youtube preview. It's at the bottom of the OP or here.
cgingermany said:
I hate to be a Richard but, can we get some screenies fam?
Click to expand...
Click to collapse
Rich, there is an almost 9 minute video in the first post.

AOKP for Gtab AOKP | smb1002/Viewsonic G-Tablet (May 24 | Build 37 | 4.0.4)

If anybody interested in testing the AOKP port to Gtablet, the link is below. It is the AOKP forum. I tested it and I am very satisfied with it. I tested all the ICS versions from different teams but this one is the most stable and functional. Very happy with it.
http://rootzwiki.com/topic/23048-aokp-smb1002viewsonic-g-tablet-may-24-build-37-404/
tibinet said:
If anybody interested in testing the AOKP port to Gtablet, the link is below. It is the AOKP forum. I tested it and I am very satisfied with it. I tested all the ICS versions from different teams but this one is the most stable and functional. Very happy with it.
http://rootzwiki.com/topic/23048-aokp-smb1002viewsonic-g-tablet-may-24-build-37-404/
Click to expand...
Click to collapse
I just flashed build 37 to my Gtab, and it appears to be alot faster and more fluent, than TeamDRH's latest build, (Beta 1.2) which I've been running up until now.
I appreciate their hard work, but found the relatively frequent ROM-slowdowns, to be unbearable. But considering the "no help"-policy Nvidia and Viewsonic seems to have instigated regarding the Gtab, I really do find their work amazing and a crucial step on the way in the further development for the Gtab.
I do have a few questions, which you may or may not be able to answer, however:
1) How come, when I flash gapps, Youtube doesn't appear to be installed?
2) When I search for Youtube in the Play Store, it doesn't show up.
- I'm assuming that this has something to do with the way the ROM authenticates/identifies itself to the Play Store.
- On a sidenote, a few other apps also do not show up, even when searching specifically for them. (LBE Privacy Guard among others)
- I yanked a copy of the youtube.apk from my phone, and while it's not tablet optimized, it works without any apparent problems, so it's not because it doesn't work.
3) The USB-connection, only consists of MTP or Camera-options (like the TeamDRH-ROM) and I seem to be unable to get the Gtab to present itself as a Mass Storage Device, so I might access the internal memory.
(Only way of doing this is booting to Clockworkmod and mounting the internal memory as USB-share)
I appreciate and applaud your effort in bringing AOKP to the Gtablet.
I dont know the exact answers as I just put the link here, I have nothing to do with development. I found this link by mistake and I wanted to share it with people. If you want answers, put your questions directly on the forum rootzwiki .
BTW, I do it in the same way as you (according to problems).
tibinet said:
I dont know the exact answers as I just put the link here, I have nothing to do with development. I found this link by mistake and I wanted to share it with people. If you want answers, put your questions directly on the forum rootzwiki .
BTW, I do it in the same way as you (according to problems).
Click to expand...
Click to collapse
Doh... Dunno how I missed that.
Off to rootzwiki we go...
WOW AOKP to the GTAB
Hello just a few days ago I posted a (Q) in that forum asking if it was possible at all to develop an AOKP rom on the Gtab, then yesterday I basically found out that there was a 4th ICS rom for our devices and it was a AOKP port lol It was just crazy how that happened.
I did wonder, however, why the developer of the rom did not post it here or sdroid. thank you to OP for posting this but i'd mch rather have the developer to ask questions to bout the rom, but I guess Ill just have to head over to rootzWiki.
Anyway, this is pretty awesome that someone made this happen. I dont have AOKP on any other devices but i knew of the rom, and its awesomeness. Its a sick rom and im pretty excites. I think it may run as good if not slightly better than the other 3 ics roms, I just hope they continue to make it better with each release because it has potential.
I recommend that ppl should go check it out.
Hmmmm... might have to check this out...
Thanks for posting it. I never would have known.
Sent from my SN10T1 using Tapatalk 2
installed this last night because im an aokp fan.. seems pretty good... but for me i have the same problems ive had on every ics rom for this tablet. super laggy and sounds terrible? am i the only one who has terrible sound on ics roms? ive gone back to gb every time within a day or two because of the sound.. its just crappy, low volume and distorted sound? gb rocks in comparison.. really bums me out... i keep hoping one of these ics roms will run like they do on my phone, but not even close yet.
pqrs said:
installed this last night because im an aokp fan.. seems pretty good... but for me i have the same problems ive had on every ics rom for this tablet. super laggy and sounds terrible? am i the only one who has terrible sound on ics roms? ive gone back to gb every time within a day or two because of the sound.. its just crappy, low volume and distorted sound? gb rocks in comparison.. really bums me out... i keep hoping one of these ics roms will run like they do on my phone, but not even close yet.
Click to expand...
Click to collapse
Team DRH next release, sound issue is suppose to be one of the main things to be addressed...
Info for OP. Credits to user jjewell.
this should be in the general selection; you did not make this, you are only informing people.
Build 40 is out, I'm really glad there's still development for ours gtabs
Is this for bootloader 1.1 or 1.2?
bigtex06 said:
Is this for bootloader 1.1 or 1.2?
Click to expand...
Click to collapse
I believe that it does not matter on ics ROMs. What is important is that your system partition be enlarged to 250MB and the easiest way to do that is to use the nvflash. See my easy guide http://raywaldo.com/2011/01/nvflash-for-dummies/
Sent from my Nook Tablet using xda premium
It is for BL 1.1.
I am unable to install it under BL 1.2
tsukaza said:
It is for BL 1.1.
I am unable to install it under BL 1.2
Click to expand...
Click to collapse
Did you expand the system partition as I said?
Sent from my Nook Tablet using xda premium
raywaldo said:
What is important is that your system partition be enlarged to 250MB and the easiest way to do that is to use the nvflash.
Click to expand...
Click to collapse
It will need more actually. Full gapps + the face detection code that is installed will use up 262+ MB.
rajeevvp said:
It will need more actually. Full gapps + the face detection code that is installed will use up 262+ MB.
Click to expand...
Click to collapse
Team drh has posted a new nvflash that makes system partition 300mb. People who are having trouble should try it out.
http://www.teamdrh.com/DRH-Downloads/Full_Stock_NVFlash_CWM_5504_300mb_system.zip
Sent from my Nook Tablet using xda premium
ernest-sora said:
Build 40 is out, I'm really glad there's still development for ours gtabs
Click to expand...
Click to collapse
yes, its out, but there is a problem with downloading from google player. so I wait for now...
Since this is based off the kernel of DRH ans their drivers, what's the difference between the two? Is this more stable/faster? What are the benefits to this ROM over DRH?

[DEV] Android App Compatibility for Sailfish OS

(May or may not be the right place to put this)
A place to discuss and attempt to implement Android app compatibility for Sailfish OS.
Now I'm not too knowledgeable about this kind of stuff, I'll need to do more research before I'll be able to help in any meaningful way.
vgrade said:
From a community standpoint I'd much prefer an open solution.
The way the Sailfish stack is designed it leads itself more to an open solution than previous attempts. It uses the android driver libs from original /system , runs an init just as in real android. For example surface flinger would run if you enabled it from init.rc. We can run the original dalvik. So all (and I know its a significant task) that is required is some plumbing to allow switching of surface flinger output to hwcomposer instead of lipstick (the sailfish compositor) and switching touch.
I'd invite anyone interested to join us at sailfishos-porters to discuss further
BR
vgrade
Click to expand...
Click to collapse
UPDATE 1:
I have been working on this lately, and can "boot" into CM11 and get to the setup screen, but the touchscreen, power button and potentially everything else doesn't work as it's still using the sailfish drivers. The only command needed to boot into CM11 is just starting surfaceflinger via "./surfaceflinger" after navigating to /system/bin/ . I did however modify the init.rc file to turn on the android specific services. which I've linked below.
UPDATE 2: using ssh via USB connection breaks when "booting" into CM but using ssh over WiFi does not.
Modified init.rc file
UPDATE 3: Quicksilver is a chromium client for sailfish, and if you build it with NaCl enabled (its currently disabled) then ARChon MAY work. The link to the git repo is below.
quicksilver repo link
UPDATE 4: It's getting close now. Chroot-ing into the android emulator image while also using it's renderer is almost seeing the light of day and we need your help. All info found in this thread.
Some extra posts for context...
The following post is what inspired the vgrade's post (see post 1 of this thread):
kageurufu said:
and Alien is ported over (I know it wont be official, someones gonna do it anyway) this could easily be a daily driver.
Click to expand...
Click to collapse
What makes you so sure of that, AlienDalvik's a proprietary solution, it's not an easy undertaking, IcedRobot really struggled to get anywhere.
I followed it & related/similar for years, but none of them got anywhere really...*
Jolla should be offering AD as a paid add-on via the store, not expecting the community to whisk a decent alternative into reality from thin air.
---------- Post added at 02:27 PM ---------- Previous post was at 02:24 PM ----------
vgrade said:
An open dalvik would be a huge step forwards and any help people can give please drop into #sailfishos-porters IRC
Click to expand...
Click to collapse
Surely a much better "step forward" would be to offer AD as a paid for add-on via the store...
Maybe longer-term you/we can aim for an open dalvik, but there's already too much you're/we're juggling over the next ~12mth.
*google IcedRobot & IcedRobot Dalvik, but here's 3 quick/dirty links:
https://wiki.debian.org/Java/DevJam...do=get&target=icedrobot-fosdem-2011-02-05.pdf
https://github.com/icedrobot
https://twitter.com/hashtag/icedrobot
The old project site doesn't even exist any more, just some junk fitness product:
http://www.icedrobot.org/
Click to expand...
Click to collapse
The next 2 posts below came after vrgrade's response (see post 1 of this thread):
jalyst said:
@vgrade
Interesting, I thought what would be required, is something akin to icedrobot i.e. a complete (openJDK compliant) replacement of dalvik.
Are you saying that something much simpler would be possible (& hence much less work), & would still work just as well?
Sorry for the OT post, last one, perhaps a sep. thread needs to be created here...
Click to expand...
Click to collapse
vgrade said:
Yes , something much simpler.
Please feel free to start a new thread , its there a general area on xda as this would be common to all Sailfish ports, N4, N5 , N7 , Galaxy Nexus etc
vgrade
Click to expand...
Click to collapse
Nice thread. I have not much knowledge about such things here but just to say it BlackBerry OS 10 has also support for Android apps and maybe someone could get done kind of inspiration off their implementation of Android. Just a thought of mine maybe it's completely nonsense what I said but maybe not so.
http://wiki.maemo.org/Apkenv
http://talk.maemo.org/showthread.php?t=87496
Have a look in here., trying to make sense of it myself.
You'd prolly want to get folks like: Mario Torre (IcedRobot), Carstun Munk (libhybris), Thomas Perl (apkenv) involved in one way or another.
Plus some Android guys who are well respected in this community, & who know dalvik/art inside out...
aironeous said:
http://wiki.maemo.org/Apkenv
http://talk.maemo.org/showthread.php?t=87496
Click to expand...
Click to collapse
https://openrepos.net/content/lightdot/apkenv
Yeah but, apkenv is far from being a solution, we need some of the relevant parties engaging here, not end-users.
ARC - App Runtime for Chrome OS, is promising, if anyone knows how to port it over . I can't find any source files, other than ARChon. Could it be this.
nh1402 said:
ARC - App Runtime for Chrome OS, is promising, if anyone knows how to port it over . I can't find any source files, other than ARChon. Could it be this.
Click to expand...
Click to collapse
https://chromium.googlesource.com/a...410.206.0/docs/getting-started-open-source.md
A small set of shared objects can be built which are part of ARC currently.
A fully running system cannot currently be built.
Click to expand...
Click to collapse
EnErGy[CSDX] said:
https://chromium.googlesource.com/a...410.206.0/docs/getting-started-open-source.md
Click to expand...
Click to collapse
I take it Archon works as it works through Chrome, which has similar stuff to Chrome OS.
EDIT: I mean theoretically you could install all the relevant repos to install chromium and then get archon working that way.
nh1402 said:
I take it Archon works as it works through Chrome, which has similar stuff to Chrome OS.
Click to expand...
Click to collapse
Archon is just repack of ARC extensition to make it work under desktop Chrome.
nh1402 said:
EDIT: I mean theoretically you could install all the relevant repos to install chromium and then get archon working that way.
Click to expand...
Click to collapse
installing chromuim to Sailfish os is no trivial task.
I was just stating theoretically speaking. I wasn't suggesting someone should do that, I understand that its not a trivial task. I guess we should wait till they release all the necessary files then, unless they don't plan to then we're back to square one.
I thought I would try and see what happens if I pause lipstick (kill -STOP 950) , and start surfaceflinger (./system/bin/surfaceflinger), and see what happens, turns out it shows that "static-y" image like when you're booting into sailfish.but since sailfish doesn't use surfaceflinger then nothing happens it just stays with that same screen. stop surfaceflinger, and then run (kill -CONT 950), and then start interacting with the screen again, everything goes back to normal.
If I can find out the bare minimum needed to install and run an apk, it could work, but probably won't.
If someone knows what services are needed in order to either boot into android, or to get an app to run, please say so.
EDIT: I can now get to the setup screen of cyanogenmod, but that is it, touchscreen doesn't work and ssh connection breaks. But its recognised as an unauthorised device in adb.
And how about https://github.com/vladikoff/chromeos-apk/ ?
sledges said:
And how about https://github.com/vladikoff/chromeos-apk/ ?
Click to expand...
Click to collapse
That works through Chrome/Chromium.
nh1402 said:
That works through Chrome/Chromium.
Click to expand...
Click to collapse
Chrome OS is a GNU/Linux distro, so would need crosscompiling to ARM and integration effort
sledges said:
Chrome OS is a GNU/Linux distro, so would need crosscompiling to ARM and integration effort
Click to expand...
Click to collapse
Checking the source code documentation still reads "A small set of shared objects can be built which are part of ARC currently. A fully running system cannot currently be built." They could provide an update and release the shared objects at Google I/O later this year but I wouldn't hold my breath.
Is Gentroid worth looking into? https://code.google.com/p/gentroid/
aironeous said:
Is Gentroid worth looking into? https://code.google.com/p/gentroid/
Click to expand...
Click to collapse
Nice find, I would say that it is.
Now there are 3 promising Android solutions
CM (if we can get touch working)
gentroid
quicksilver (if ARChon works on Chromium)

AOSP Rom

Was able to get a ROM built and running based on LRX21V straight from source. Just trying to get a feel on how many people would want to run AOSP. There are some bugs present such as video recording causing the camera to stop working. I think there are binaries missing that Google didn't include in the binaries that are available. Same problem happened on the Nexus 5. Didn't test it much as I just purely wanted to see if it booted.
Also there is a lack of gapps available so I won't be rushing to get anything out. Let me know what y'all think and I'll try to tackle this to get some other options out for us.
Here is the test build for those that want to have a look. This is just a test build so bugs are to be expected. Video recording does not work. Haven't tested it completely as I need a fully working device this weekend. This is for those that have free time to just nit pick and find all bugs in this. Please report back after you are done and let me know what else you may have found that is broken or not working right.
Stock Google kernel (so if you flashed the kernel image to remove encryption your phone WILL be encrypted again)
Built off 5.0.0_r7 from AOSP
Flash ROM, flash gapps and flash SU that is linked below. This will allow root access on the stock kernel.
You can also optionally flash the custom boot image after flashing the ROM, gapps and SU by rebooting to bootloader and fastboot flash boot the custom encryption kernel. That is optional. Be sure to go back in to recovery after flashing the kernel to reflash the SU to make sure it was not overwritten.
Download Rom:AFH Mirror
Download Gapps for Lollipop:http://forum.xda-developers.com/showthread.php?p=56810851#post56810851
Download latest SU: http://forum.xda-developers.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133
I'm tuned in!
Sent from my Nexus 6 using XDA Free mobile app
The development section is kind of depressing me right now (no offense to devs) so bring it!
the.emilio said:
Was able to get a ROM built and running based on LRX21V straight from source. Just trying to get a feel on how many people would want to run AOSP. There are some bugs present such as video recording causing the camera to stop working. I think there are binaries missing that Google didn't include in the binaries that are available. Same problem happened on the Nexus 5. Didn't test it much as I just purely wanted to see if it booted.
Also there is a lack of gapps available so I won't be rushing to get anything out. Let me know what y'all think and I'll try to tackle this to get some other options out for us.
Click to expand...
Click to collapse
Any gapps should work. It can be downloaded from the nexus 5 section
---------- Post added at 09:37 AM ---------- Previous post was at 09:34 AM ----------
Its only been a couple days. And the phone is really scarce. Give it time
estallings15 said:
The development section is kind of depressing me right now (no offense to devs) so bring it!
Click to expand...
Click to collapse
That is pretty offensive. It is a new device and isn't in the developers hand so releasing work without testing their work leads to quality problems.
I don't see you doing any development work and developers don't owe anyone anything as they do all this work as a hobby pretty much.
Sent from my Nexus 6 using Tapatalk
zephiK said:
That is pretty offensive. It is a new device and isn't in the developers hand so releasing work without testing their work leads to quality problems.
I don't see you doing any development work and developers don't owe anyone anything as they do all this work as a hobby pretty much.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I know the reasons behind it, which was the point of the "no offense." I wasn't whining. I was trying to help motivate and encourage OP. He, as well as others, are working on making things happen and I'm excited for it and waiting eagerly for the kernel source to drop.
You took what I said the wrong way, so step off of your soap box, zephiK.
Edit: That reminds me. If any devs need testers, PM me. I'll be happy to help the community out.
Smallsmx3 said:
Any gapps should work. It can be downloaded from the nexus 5 section
---------- Post added at 09:37 AM ---------- Previous post was at 09:34 AM ----------
Its only been a couple days. And the phone is really scarce. Give it time
Click to expand...
Click to collapse
Lol. I know this. Just came from the N5 I guess what I meant is that there isn't a complete package yet. There's a minimal yes that does work. But I prefer the full. Just lazy and hate downloading apps or pushing apps lol
the.emilio said:
Lol. I know this. Just came from the N5 I guess what I meant is that there isn't a complete package yet. There's a minimal yes that does work. But I prefer the full. Just lazy and hate downloading apps or pushing apps lol
Click to expand...
Click to collapse
Ha! That's funny. does r 7 have any significant commits over our revision
Smallsmx3 said:
Ha! That's funny. does r 7 have any significant commits over our revision
Click to expand...
Click to collapse
No. Minor bug fixes for the particular device it was made for but that's it. I did notice on the N5 that there was a significant "miscellaneous" battery drain on r7. Might roll back to r3 if its present since r3 is the one for us (its also the same build for the N5).
zephiK said:
That is pretty offensive. It is a new device and isn't in the developers hand so releasing work without testing their work leads to quality problems.
I don't see you doing any development work and developers don't owe anyone anything as they do all this work as a hobby pretty much.
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
We are working on something [emoji6]
the.emilio said:
No. Minor bug fixes for the particular device it was made for but that's it. I did notice on the N5 that there was a significant "miscellaneous" battery drain on r7. Might roll back to r3 if its present since r3 is the one for us (its also the same build for the N5).
Click to expand...
Click to collapse
Miscellaneous bug again? I wonder if they broke the same thing they already fixed, or if this is something else that is just falling into miscellaneous as well.
Thanks for the work on this!
In for the long haul! Tired of the plethora of gapps on this phone. Somehow I managed to break photos once by removing some google app... Weird.
Sent from my Nexus 6 using Tapatalk
I uploaded the ROM for testing purposes. Please re-read the OP for more info. :good:
the.emilio said:
I uploaded the ROM for testing purposes. Please re-read the OP for more info. :good:
Click to expand...
Click to collapse
Sweet, thanks.
What the Christ is this new file layout?! System.new.dat o.0
Sent from my Nexus 6 using Tapatalk
Rauch said:
Sweet, thanks.
What the Christ is this new file layout?! System.new.dat o.0
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
That's lollipop for ya..
the.emilio said:
That's lollipop for ya..
Click to expand...
Click to collapse
As I wanted to attempt to pre-root and make some changes... Ugh.
Simply installing the SuperSU apk is enough for root, correct? I don't have to re-run CF... Especially since I'm not near a PC
Sent from my Nexus 6 using Tapatalk
Rauch said:
As I wanted to attempt to pre-root and make some changes... Ugh.
Simply installing the SuperSU apk is enough for root, correct? I don't have to re-run CF... Especially since I'm not near a PC
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Yes just use the one I linked to. Be sure to flash it in the same session so you don't lose the custom recovery.
Rauch said:
As I wanted to attempt to pre-root and make some changes... Ugh.
Simply installing the SuperSU apk is enough for root, correct? I don't have to re-run CF... Especially since I'm not near a PC
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Remember its just a test so I recommend waiting until you have access to a PC. Just in case lol
Well, I bit the bullet. Only lost a few downloads.... But anyway.
Sound quality seems.... Different? Also network says its connected to LTE, but its beyond slow. Not sure why exactly.
I'm on the correct APN.
Closing apps, I hear a slight buzz/tap three tomes when hitting the home button.
Sent from my AOSP on Shamu using Tapatalk
carloscibrian4 said:
Did anyone's storage decreased afterwards? My nexus says that there is only 23gb of storage despite being a 64 gb
Click to expand...
Click to collapse
I have a 32gb and that's what I have.... I didn't check before.... Anyone have any idea what storage should be out of the box?
Rauch said:
Well, I bit the bullet. Only lost a few downloads.... But anyway.
Sound quality seems.... Different? Also network says its connected to LTE, but its beyond slow. Not sure why exactly.
I'm on the correct APN.
Closing apps, I hear a slight buzz/tap three tomes when hitting the home button.
Sent from my AOSP on Shamu using Tapatalk
Click to expand...
Click to collapse
I was getting weird audio sounds at first... I don't know if it was the update when I got home that fixed it but it's been non existent since the first couple of hours I had the phone

CyanogenMod Forum → Device Req Samsung Galaxy Tab S2

We know there are work in progress to port CM 12 on T810 and T710 but none for T815 and T715
So those like me with T815 or T715 or ... that are looking for CM for their device can post their request in CyanogenMod Forum request page
http://forum.cyanogenmod.org/topic/116361-samsung-galaxy-tab-s2/
Yes; even without phone fuctions is ok for start. I see note 4 exynos got decent cm13 now; I hope no impossible to give it for tab s2 lte. Would be great
Hey, I'm new to this, but I want to give it a shot to try a port for the T715.
I think it should be no problem to make a build without modem support.
So my plan would be to use the source of the T710, if @CTXz allows me to use his sources.
Next I want to try to integrate the modem/ RIL sources, but don't expect too much! I'm completely new to android development and this will be my first project doing myself.
Just did some compilings and ports, but never to new unsupported devices. Maybe with some help it will be possible for me.
Greets, Phil!
Philippovitsch said:
Hey, I'm new to this, but I want to give it a shot to try a port for the T715.
I think it should be no problem to make a build without modem support.
So my plan would be to use the source of the T710, if @CTXz allows me to use his sources.
Next I want to try to integrate the modem/ RIL sources, but don't expect too much! I'm completely new to android development and this will be my first project doing myself.
Just did some compilings and ports, but never to new unsupported devices. Maybe with some help it will be possible for me.
Greets, Phil!
Click to expand...
Click to collapse
Hey, you really don't need to ask to use my sources A mention at the finished ROM would be all I need . However, if you plan to support it, I recommend joining my git group
CTXz said:
Hey, you really don't need to ask to use my sources A mention at the finished ROM would be all I need . However, if you plan to support it, I recommend joining my git group
Click to expand...
Click to collapse
Hey, ok great, thank you!
So let's try it!
A question:
What does one gain and lose by going from stock Samsung to CM12/13?
Thanks!
optionalmgrr.la said:
A question:
What does one gain and lose by going from stock Samsung to CM12/13?
Thanks!
Click to expand...
Click to collapse
That is a very tuff question to answer in just one post and depends on particular preferences. My advise is to Google: Cyanogenmod and TouchWiz.
Sent from my SM-T810 using Tapatalk
danyvw said:
That is a very tuff question to answer in just one post and depends on particular preferences. My advise is to Google: Cyanogenmod and TouchWiz.
Sent from my SM-T810 using Tapatalk
Click to expand...
Click to collapse
It seems the main issue is battery and camera (quality).
i think i messed my t817v. i rooted using odin, and cannot figure out what to do next. it tries to install but gives error message, also my tab wont charge, and when hooked into odin it keeps "adding then removed" over and over again... now i have a tablet that does not work.
any help on this would be awesome.
@CTXz
Philippovitsch said:
Hey, I'm new to this, but I want to give it a shot to try a port for the T715.
I think it should be no problem to make a build without modem support.
So my plan would be to use the source of the T710, if @CTXz allows me to use his sources.
Next I want to try to integrate the modem/ RIL sources, but don't expect too much! I'm completely new to android development and this will be my first project doing myself.
Just did some compilings and ports, but never to new unsupported devices. Maybe with some help it will be possible for me.
Greets, Phil!
Click to expand...
Click to collapse
I would love that!
I also posted a device request at the CyanogenMod Forum.
What you always lose with CM is Bluetooth aptX support for higher quality Bluetooth audio, since they have no licence. And since now there is official MM for the S2 and it - with enough free storage and 3 GM of RAM and root available - really doesn't profit any more from a "slim" ROM than earlier devices did, can anybody point me to a real advantage of CM?
For me CM was never about storage, but about control. As far as possible (for I am no programmer) I want to decide about the rights apps have and don't. It starts with being able to delete them and goes on with being able to restrict their access rights. As far as I remember such privacy guard things are much more easier to accomplish with CM.
Pegaside said:
For me CM was never about storage, but about control. As far as possible (for I am no programmer) I want to decide about the rights apps have and don't. It starts with being able to delete them and goes on with being able to restrict their access rights. As far as I remember such privacy guard things are much more easier to accomplish with CM.
Click to expand...
Click to collapse
But stock MM offers these permission settings now, so what else?
saintsimon said:
But stock MM offers these permission settings now, so what else?
Click to expand...
Click to collapse
My TAB s2 is my first Samsung device.... ( other android devices being nexus 7, xperia z2 / z3, moto g 4G ) ...... I love the tablet but I must say the draw of a supported CM ROM would be the look / feel of stock android and the way the system behaves. Whilst with a rooted device you can remove bloatware, the system itself does not change. All of my other devices have been stock or only lightly skinned....and basically stock once you swap out the launcher.... so I have come to like that. I do find touchwiz to be a little in my face and I do notice the system intrusions a little...... a personal thing of course and I am not complaining as I made the decision to buy it knowing full well what Touchwiz was... but the hardware in the tablet and the price was the draw-card (got the WiFi version here in Aus the first month on sale for $540 ... in comparison, the Nexus 9 was circa $700 and the Ipad Air 2 64gb was $730). My nexus 7 2013 runs MM with less and smoother than the TAB s2 runs LP. I could only imagine what it could do with an ASOP ROM once the bugs were fixed.
Could it be due to a defect usb-port?
optionalmgrr.la said:
A question:
What does one gain and lose by going from stock Samsung to CM12/13?
Thanks!
Click to expand...
Click to collapse
Do u know the difference between WIndows Phone/iPhone and Android, that's the kind of comparison u can use between Stock and CM.
Stock is the cute "little" thing with mostly everything that u may need ready to go.
CM is the smaller in size, much faster and with options to do almost anything u could think in a device.
aaronadams74 said:
i think i messed my t817v. i rooted using odin, and cannot figure out what to do next. it tries to install but gives error message, also my tab wont charge, and when hooked into odin it keeps "adding then removed" over and over again... now i have a tablet that does not work.
any help on this would be awesome.
Click to expand...
Click to collapse
Was this ever fixed?
Why does the SM-T815 run in 32bit mode, even under CM13?

Categories

Resources