Related
Has anyone tried to use the Google Play Edition RUU for the HTC One (posted here) on their HTC One Mini? The hardware looks similar enough that I'd think it would work. I'm not sure if the lack of NFC is an issue.
Context:
I am a noob to both this forum and Android. I am ready to make the switch, but I want a vanilla Android experience; I'm just not a fan of the Sense UI from what I've been able to play with. I also value smaller, lighter devices, and the HTC One Mini feels perfect to me. I'm an experienced technologist, I've jailbroken iPhones (admittedly less complicated), and I've been a tester for prototype devices at a mobile company I'd prefer not to name (more complicated), so I feel absolutely comfortable with the process of rooting a phone like this. I also value OTA updates, so a Google Play Edition is exactly what I'm looking for.
Any thoughts or suggestions on the subject would be appreciated. I've already gotten several ideas from other posts here. I do apologize if this has already been answered, but I did search and am pretty confident it hasn't been directly addressed.
No, don't do that. Especially not the RUU since that does more than just installing a stock rom.
wrath0r said:
Has anyone tried to use the Google Play Edition RUU for the HTC One (posted here) on their HTC One Mini? The hardware looks similar enough that I'd think it would work. I'm not sure if the lack of NFC is an issue.
Context:
I am a noob to both this forum and Android. I am ready to make the switch, but I want a vanilla Android experience; I'm just not a fan of the Sense UI from what I've been able to play with. I also value smaller, lighter devices, and the HTC One Mini feels perfect to me. I'm an experienced technologist, I've jailbroken iPhones (admittedly less complicated), and I've been a tester for prototype devices at a mobile company I'd prefer not to name (more complicated), so I feel absolutely comfortable with the process of rooting a phone like this. I also value OTA updates, so a Google Play Edition is exactly what I'm looking for.
Any thoughts or suggestions on the subject would be appreciated. I've already gotten several ideas from other posts here. I do apologize if this has already been answered, but I did search and am pretty confident it hasn't been directly addressed.
Click to expand...
Click to collapse
Google Play Edition RUU is recompiled from source nothing to do with Sense 5 and that's mean different kernel that won't boot the HTC One Mini.
You have to wait for an CyanogenMOD available and after that if you don't like it we can build/port AOSP (pure google android).
xpirt
xpirt said:
Google Play Edition RUU is recompiled from source nothing to do with Sense 5 and that's mean different kernel that won't boot the HTC One Mini.
You have to wait for an CyanogenMOD available and after that if you don't like it we can build/port AOSP (pure google android).
xpirt
Click to expand...
Click to collapse
That's incorrect, the GE rom is actually just visually desensed Sense and can be booted with a Sense 5 kernel. It's nowhere close to being AOSP.
CNexus said:
That's incorrect, the GE rom is actually just visually desensed Sense and can be booted with a Sense 5 kernel. It's nowhere close to being AOSP.
Click to expand...
Click to collapse
That makes good sense to me and, in theory, means the Google Play Edition ROM could boot on the mini since the hardware of the same architecture. I think the question is whether the same drivers can be used for the other internals. In other words, we could be able to boot the OS but be unable to use any of the components.
GSM Arena has the full tech specs of the HTC One and the Mini. When I compare these, I see a GPU that, according to Adreno wikipedia article, supports the same OpenGL, OpenVX, and DirectX versions, so I think this would be fine. The chipsets are slightly different and that worries me a bit since that could imply different radios, etc. I'd feel better if I could see a teardown of the mini, but with how miserable the teardown of the full sized version was I doubt they're clamoring to start that.
wrath0r said:
That makes good sense to me and, in theory, means the Google Play Edition ROM could boot on the mini since the hardware of the same architecture. I think the question is whether the same drivers can be used for the other internals. In other words, we could be able to boot the OS but be unable to use any of the components.
GSM Arena has the full tech specs of the HTC One and the Mini. When I compare these, I see a GPU that, according to Adreno wikipedia article, supports the same OpenGL, OpenVX, and DirectX versions, so I think this would be fine. The chipsets are slightly different and that worries me a bit since that could imply different radios, etc. I'd feel better if I could see a teardown of the mini, but with how miserable the teardown of the full sized version was I doubt they're clamoring to start that.
Click to expand...
Click to collapse
Or just wait. An official CM maintainer has a One Mini and will be working on it soon.
jmz said:
Or just wait. An official CM maintainer has a One Mini and will be working on it soon.
Click to expand...
Click to collapse
Correct. And....ohai!
The partition layout is completely different as are the kernel base and ramdisk offsets. If you flash that RUU...you may be heading back to the AT&T store immediately afterwards.
I have most of the prep work completed for cm-10.2....so sit tight while I work out some kinks. I will make a thread in the original android dev forums once its ready for alpha testing.
Sent from my One using xda app-developers app
CNexus said:
That's incorrect, the GE rom is actually just visually desensed Sense and can be booted with a Sense 5 kernel. It's nowhere close to being AOSP.
Click to expand...
Click to collapse
Really?? So the One users can switch from GE to Sense without flashing kernel? No atleast ramdisk changes nothing?
So if we port a m7 sense 5 we can also port GE in the same way?
That doesn't mean we can also base a CM on sense 5 kernel?
xpirt
xpirt said:
Really?? So the One users can switch from GE to Sense without flashing kernel? No atleast ramdisk changes nothing?
So if we port a m7 sense 5 we can also port GE in the same way?
That doesn't mean we can also base a CM on sense 5 kernel?
xpirt
Click to expand...
Click to collapse
Yes. And this is how I was able to port sense to the First so easily. HTC's "AOSP" roms are purely Sense roms with specific apks replaced with AOSP apks. In 4.2+ a lot of changes need to be made to kernel to boot AOSP. Those changes won't necessarily be compatible with sense
Sent from my HTC One using XDA Premium 4 mobile app
boy am I glad I saw this before trying to flash my mini !
GPE for the Mini
h8rift said:
I have most of the prep work completed for cm-10.2....so sit tight while I work out some kinks. I will make a thread in the original android dev forums once its ready for alpha testing.
Click to expand...
Click to collapse
Sorry guys to bump this up but I could not find any further info on this...
Is there any development or is it a deserted project?
Cheers,
ym
ps. BTW is there AOSP rom available for the Mini? Cyanogenmod seems to have heat issues and the wifey is already hot enough so I don't want to give her anything problematic
yourmate said:
Sorry guys to bump this up but I could not find any further info on this...
Is there any development or is it a deserted project?
Cheers,
ym
ps. BTW is there AOSP rom available for the Mini? Cyanogenmod seems to have heat issues and the wifey is already hot enough so I don't want to give her anything problematic
Click to expand...
Click to collapse
Yeah buddy... Try this http://forum.xda-developers.com/htc-one-mini/orig-development/rom-t2825888
Cheers
I would not install any CM-based ROM (CM/Candy*/PacMan/whatever) on M4 until the overheat issue is dealt with. They all have reports of bricked devices, and it looks like any device can (or will, eventually) get cooked any moment sooner or later (some people got theirs bricked after half a year, mine was lost within half an hour).
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
* EDIT: According to tr1gg3r84, CandyROM is not CM-based.
excellent, thanks
pure.by said:
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
Click to expand...
Click to collapse
Excellent suggestion as I was looking for the GPE originally :good:
pure.by said:
I would not install any CM-based ROM (CM/Candy/PacMan/whatever) on M4 until the overheat issue is dealt with. They all have reports of bricked devices, and it looks like any device can (or will) eventually get cooked any moment sooner or later (some people got theirs bricked after half a year, mine was lost within half an hour).
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
Click to expand...
Click to collapse
EH? There has NEVER been any reports of overheating or bricked devices on CandyRom! So I suggest for you to get your facts right before posting.!
AnGrY sCoTsMaN said:
There has NEVER been any reports of overheating or bricked devices on CandyRom!
Click to expand...
Click to collapse
I'm very sorry if that is the case, then I must be mistaken for another ROM; there were a bunch involved in this issue.
But no reports does not mean it has not happened. As far as I know CandyRom is CM-based *, and overheating issue affects all CM-based ROMs the same. Not sure what makes CandyRom different in that aspect. *
Once again, it may happen or it may not. You can either see it as a lottery or a ticking time bomb. Either way, I better go with the ROM that just does not have that possibility by design.
* EDIT: According to tr1gg3r84, CandyROM is not CM-based.
yourmate said:
Excellent suggestion as I was looking for the GPE originally :good:
Click to expand...
Click to collapse
Glad I could help
If you could find some time in a week or two to report back about stability, performance and your overall experience, that info would be much appreciated!
pure.by said:
I would not install any CM-based ROM (CM/Candy/PacMan/whatever) on M4 until the overheat issue is dealt with. They all have reports of bricked devices, and it looks like any device can (or will) eventually get cooked any moment sooner or later (some people got theirs bricked after half a year, mine was lost within half an hour).
In the meantime, bilal_liberty has created a LibertyROM GPE for M4!
GPE is Sense-based and thus safe to install.
Click to expand...
Click to collapse
Yeah get your facts correct before you post Candy Roms isn't even Cyanogen based like the rest you stated and no bricks have been made by using this ROM either. For a GPE I have a booting GPE over Six month ago before I got rid of my M4 with the help from rmbq with kernel but ever release it coz thought it was pointless.
tr1gg3r84 said:
Candy Roms isn't even Cyanogen based
Click to expand...
Click to collapse
I'm very sorry, based on official description provided in CandyROM's threads I thought it was (partly) CM-based. I'm a user, not a developer, so obviously I can't discuss what's under the hood, I have to distinguish based on information developers provide me.
Obviously, I was wrong, for what I apologize. I will correct my previous 2 posts accordingly right away.
pure.by said:
I'm very sorry, based on official description provided in CandyROM's threads I thought it was (partly) CM-based. I'm a user, not a developer, so obviously I can't discuss what's under the hood, I have to distinguish based on information developers provide me. Obviously, I was wrong, for what I apologize. I will correct my previous 2 posts accordingly.
Click to expand...
Click to collapse
Yeah well I should know what I'm on about, after supporting this device for so long before anyone even cared about developing for it....(well there's a lot of so called (Devs) that like to spread rumors about other ROMs to increase their user base) pretty much sick to death of it tbh. Apology accept and cheers for that. CandyRoms is a great ROM supported by over 30 devices and glad to be apart of the team of working hard developers
tr1gg3r84 said:
For a GPE I have a booting GPE over Six month ago before I got rid of my M4 with the help from rmbq with kernel but ever release it coz thought it was pointless.
Click to expand...
Click to collapse
Good for you.
Thanks God, that bilal_liberty's thought it differently and shared it rather than just posting about it
So, i opened this therad because there no persons pushing and Developing custom AOSP Roms for the Galaxy Tab 3.
I'm opening it here because the Android Developing forum is a bit AFK.
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!
Curious..
superboom said:
Also, my first question is,
Why we are not using the Android x86 source, put a little bit from samsung open source and Tab 3 binaries it, and compile it?
Its so hard?
We are the xda-developers, we can do it!
Click to expand...
Click to collapse
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?
chaoskoch said:
Yes, I'm asking myself the same, the Galaxy Tab 3 is such a famous device and out since July, but still there are nearly no ROMs out. Are there any ROMs planned or will this device soon be moved to the low activity section? CyanogenMod officially supported the Galaxy tab and the galaxy tab 2, but it doesn't seem like they are planning to support the galaxy tab 3?
Is there a special reason for that?, I'm just wondering?
Click to expand...
Click to collapse
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...
Willing to get my hands dirty...
safariking said:
you know why we need developers who want to put some time in this device and at the moment we don't have much dev's around here so wait...
Click to expand...
Click to collapse
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.
ush
AnthonyAlmighty said:
The most device development I've done to date has been a simple android app, but I'm willing to get dirty on this one. I just came into possession of one of these devices over xmas, and I never let a good device go to waste. I do have 17 years of programming experience in multiple languages including C++ and Java, and a lot of web-based languages, so I'm hoping to come up to speed relatively quickly.
I'll poke around here and on the net over the next few days and see if I can teach myself, but if someone could point me in the direction of some quick start tutorials for building custom roms, I'll get started.
Click to expand...
Click to collapse
Anthony, I think one thing that is holding people back on this device is a good recovery. The ones available now are painfully slow. I'm guessing there is some power saving mode on the x86 chip that needs to be tweaked to get it performing well. Once that was fixed, it would be a lot easier to experiment with ROMs. -- Bud
Also Interested
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.
Br1cK'd said:
Anthony and all, hi and hello. Thinking of shaking the rust off, as I also just came into possession of a GTab3, 10.1 inch, over this holiday season. I haven't built anything in a long time, but anyone who ran a Vibrant a couple years ago around here, should recognize my handle. I maintained a rom for the Vibrant for quite a while, from Froyo to ICS, then life got busy.
Popping into here today, I'm kinda sad to see there's not much if any in the way of development on this device. Happy to have root, thats a start. cduced was right, we do need a better recovery option, at least one that is faster, though what we have now is workable. TWRP may be slow, but it's something. We were always hung up on doing pure aosp source build for the Vibrant, because Sammy is not known for making their kernel source easily and readily available. Working from an existing zip to kang it is easy, but really thats just the same rom, maybe stripped and repackaged. A source build is the desirable outcome.
Though I haven't begun looking into things for this baby yet, and my adb and build tools are far out of date, I am very interested in working towards a better set of options for this device. 4.2.2 still? I can't believe Sammy hasn't released a 4.3 update, that's sad, but goes to show the lack of support they give their devices, to anyone who's been there you know, but you also know, determined devs can make it a better world.
Anthony, and anyone else interested in trying to improve this device, feel free to PM me, I'm thinkin' we should make a Google Hangout or something, make it easier to communicate.
Click to expand...
Click to collapse
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!
Ideas4ya said:
Hey I want aosp on this device too! At the very least, id like a custom kernel that I can overclock to reduce lag. Ive never created a rom, but I dont think roms are the issue...id be interested in porting roms that already exists...x-note for multiwindow features, or pac-rom for a highly customized device.
Are you still up for the projects? Lets heat these forums up!!!
Click to expand...
Click to collapse
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret
Meteore said:
Thanks guys for give it a try, I'm like the other owner don't understand why there is no interest for this devise didn't check before buy and now start to regret
Click to expand...
Click to collapse
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.
mylifeandroid said:
There are some devs now they just relesed 2 but there tw based there trying it just takes awile because of lack of devs.
Click to expand...
Click to collapse
It's ok I have already seen and tried them :laugh:. I understand the concept of work on something new and the lack of dev it's just that I was surprised because I thought tab 3 was like the others tabs so the development was more evolve.no problem.
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
This is true but there is finally a bit of interest and may come up with some new goodies..... the reason they all have the same updater.script is because of the recoveries.... they need a little more work to get them to work with the x86 architecture
Sent from my GT-P5210 using xda app-developers app
Br1cK'd said:
Not to knock it, but whats been released in the threads, is nothing more than the deodexed build already up there, with some bloat removed. Even the install scripts have, or had, the same text as the original. So really, nothing new. I am looking into possibly kernel cooking for this device, that seems like a good point to start.
No promises at this point, I'm looking into it though.
Truth, Zen4 Style
Click to expand...
Click to collapse
Hey PM me with any test builds of the kernels please.
Sent from my GT-P5210 using XDA Premium 4 mobile app
I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!
Calcu said:
I think someone has to pm restl3ss!
http://forum.xda-developers.com/showpost.php?p=49126542&postcount=90
Let's see what can we do here!
Click to expand...
Click to collapse
Dont understand your post.... the link goes to one of his posts
Sent from my GT-P5210 using xda app-developers app
Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2
Calcu said:
Because in this post (if i'm not wrong) he tells that is making a recovery with 4 guys more.
something needed here xD.
Enviado desde mi Note 2
Click to expand...
Click to collapse
Lol.... I see yeah... I am also in the process of building recovery but its a long time coming. Right now im reading a lot of material on how to build from source as that the route of the prob. Its this damb x86 architecture
Sent from my GT-P5210 using xda app-developers app
Maybe.... we can port something from here
http://www.engadget.com/2014/01/06/micromax/
Enviado desde mi Note 2
Push
If anyone have time, pm me and we can discuss about. I'm not a developer, but we can discuss ideas how to bring cm to the device
This thread can be in violation of the XDA rules, but those were not clear in this regard I have therefore still opened this thread and I would like to ask the MODs to close this thread if it does appear to be in violation of the rules. I also would like to mention that this thread does not have the intention to disrespect any developers and that I appreciate the work every dev has done for the Note 3.
What I would like to be discussed in this thread is the stability of the different Android Lollipop roms. Since most of the devs have not made a seperate thread for their (at this stage alpha) builds of Lollipop. I would like to collect the experiences of the users from these alpha's.
At this stage there are 3 builds of Lollipop that I know of in alphabetical order:
Slayer (it is said to be a port, but since the original rom was for the HLTETMO. I think that it is mostly only a change in the 'device checking' file. The dev has himself stated that he does not intend to make any more builds in the near future it was more a proof of concept. The unofficial thread for Slayer's rom: http://forum.xda-developers.com/gal...m-cyanogenmod-12-lollipop-build-1-16-t2942687
Temasek: this is just an experimental build this dev has posted. I do not have any statement regarding support. Now on preview 2: http://forum.xda-developers.com/showpost.php?p=56934897&postcount=6046
Zion: also just an initial build (I think). Also no statements regarding support. The build from ZION: http://forum.xda-developers.com/showpost.php?p=56900235&postcount=542
I would like the structure of the posts in this thread to be:
Device: hlte/hltespr/hltetmo/hltevzw/hlteatt/hltexx/hlteusc/hltevan
ROM: Slayer/Temasek/Zion
What works: WIFI/Calling/etc.
What does not work/bugs: Random reboots, no network
Other remarks:
Again, if I have offended anyone in anyway I would like to apologise and I didn't intend to do so. Mod's could you then remove this thread.
And most importantly I would like to thank the devs for releasing these builds.
I can't even get temasek's build to boot.
speedyjay said:
I can't even get temasek's build to boot.
Click to expand...
Click to collapse
Booted and with LTE.
temasek said:
Booted and with LTE.
Click to expand...
Click to collapse
Share and share alike my good friend?? Lol
I've been using android 5.0 from slayer por as daily driver, I have HLTE and I have wifi, LTE, bluetooth and all works so nice and beautiful. The main problems are the camera and there are a lot of apps that not work
Today I will to try Temasek's port
Miniprepumen said:
I've been using android 5.0 from slayer por as daily driver, I have HLTE and I have wifi, LTE, bluetooth and all works so nice and beautiful. The main problems are the camera and there are a lot of apps that not work
Today I will to try Temasek's port
Click to expand...
Click to collapse
Port? It's built from source and not a port.
PREVIEW 2 is up.
temasek said:
Port? It's built from source and not a port.
PREVIEW 2 is up.
Click to expand...
Click to collapse
Sorry mistake
Downloading !!
Miniprepumen said:
Sorry mistake
Downloading !!
Click to expand...
Click to collapse
It's a preview so don't get so excited.
temasek said:
It's a preview so don't get so excited.
Click to expand...
Click to collapse
Works very well, LTE works normal, wifi too, I can do calls without any problem, and very very smooth and fast.
Problems for now: There are apps that not work, but very very good job. Thanks really
Edit: camera not works.
Wait where is zion's build? How's google now on all these builds? On Slayer's it's broken / causes reboots
My two cents on the port and on temaseks build.
The port is quite stable and random reboots usually come from incompatible apps or missing libs (as i read). I have managed to rest a lot of apps causing me trouble, but a lot of them are not yet optimized for L. The rom also has anomalies, strange stuff like closing all apps will close system ui (which is a bug not a feature, just in case i confused you). Weird stuff crash, such as Documents, which seems to be the mother of all other apps since it uses it to pick files for attach and e.t.c..
where as temaseks is very fragile. Not sure why but i barely made it to the homescreen, it kept on crashing a lot and rebooting prior to the homescreen.
Both are sort of proof of concepts, the port however is quite damn stable for an initial preview build, and yea, both surprised me with their early appearance
PlutoDelic said:
My two cents on the port and on temaseks build.
The port is quite stable and random reboots usually come from incompatible apps or missing libs (as i read). I have managed to rest a lot of apps causing me trouble, but a lot of them are not yet optimized for L. The rom also has anomalies, strange stuff like closing all apps will close system ui (which is a bug not a feature, just in case i confused you). Weird stuff crash, such as Documents, which seems to be the mother of all other apps since it uses it to pick files for attach and e.t.c..
where as temaseks is very fragile. Not sure why but i barely made it to the homescreen, it kept on crashing a lot and rebooting prior to the homescreen.
Both are sort of proof of concepts, the port however is quite damn stable for an initial preview build, and yea, both surprised me with their early appearance
Click to expand...
Click to collapse
Preview 2?
Tema prev 2 fixes the touch button wake for me. But WiFi + Google now still cases reboot. Google now hotword doesn't seem to work which it does on slayer. All camera apps fc. And the home button still doesn't wake the device. Aside from those it seems near perfect. Thanks a ton!
Sent from my SM-N9005 using XDA Premium HD app
temasek said:
Preview 2?
Click to expand...
Click to collapse
Actually no my friend, i just read it 10 minutes ago and am downloading as i write.
I did not want to spam around and used this thread exactly for expressing opinions, as i know both roms are early stage builds and none of the devs should be bombarded with requests anyway.
Will report back.
I just need spotify working them I'm happy as Larry lol
temasek said:
Preview 2?
Click to expand...
Click to collapse
One hell of a ROM at the moment, havent had a single crash and loaded loads of apps that used to crash in nearly all Lollipop builds. Too bad your ROM doesnt have the flashlight in the notification drawer, was very useful.
Right I must be blind. I can only find the ROM thread that is a cyanogenmod 12 PORT.
Can't even find any other Lollipop ROM!
can someone share the links please?
Hope their compatible with the international Note 3
Suggestion
hom.hom said:
This thread can be in violation of the XDA rules, but those were not clear in this regard I have therefore still opened this thread and I would like to ask the MODs to close this thread if it does appear to be in violation of the rules. I also would like to mention that this thread does not have the intention to disrespect any developers and that I appreciate the work every dev has done for the Note 3......
At this stage there are 3 builds of Lollipop that I know of in alphabetical order:
Slayer (it is said to be a port, but since the original rom was for the HLTETMO. I think that it is mostly only a change in the 'device checking' file. The dev has himself stated that he does not intend to make any more builds in the near future it was more a proof of concept.
Temasek: this is just an experimental build this dev has posted. I do not have any statement regarding support.
Zion: also just an initial build (I think). Also no statements regarding support.
I would like the structure of the posts in this thread to be:
ROM: Slayer/Temasek/Zion
What works: WIFI/Calling/etc.
What does not work/bugs: Random reboots, no network
Other remarks:
Again, if I have offended anyone in anyway I would like to apologise and I didn't intend to do so. Mod's could you then remove this thread.
And most importantly I would like to thank the devs for releasing these builds.
Click to expand...
Click to collapse
We can assume there will be a ton of reports here of what is working and what isn't (probably duplicates or even 5 times the same report as we saw in Unnofficial CM12 Port from Jamal's thread...). I would advise everyone to post phone info after every report. Because there is a confusion of what is working on which model.... You might wanna add this to OP so people can actually see since my post will be long forgotten after pages and pages of comments.
Plus you might add link to Jamal's thread and download links for Zion and Temasek's ROM... Not everyone has those since they are buried in an ocean of posts over at Jamall's thread. @AndroidInsanity here they are:
1. @jamal2367 thread
http://forum.xda-developers.com/gal...m-cyanogenmod-12-lollipop-build-1-16-t2942687
2. @ZION959 cm 12 unofficial
https://s.basketbuild.com/devs/Zion959/L/HLTE/
3. @temasek Build
http://d-h.st/users/temasek/?fld_id=41330#files
SM-N9005 (would be an example, so people know what phone is about. I know some have details listed in signature but not everyone).
and as always noone cares about exynos note 3...
ereneren564 said:
and as always noone cares about exynos note 3...
Click to expand...
Click to collapse
And rightfully so, if you buy an exynos device you should know that developers do not support these devices. Because the documentation of exynos chips is practically non existent. I am sorry, but with regard to custom aosp roms and devices with exynos chip consider this an expensive lesson. For support for these devices complain to Samsung.
Hi guys! I already asked this question but....why a smartphone as S PLUS received Android lollipop and Kernel 3.4.105 and the S advance is stop to KitKat and kernel 3.0.101? Thi our smartphone has absolutely no developer able to do it?:crying::crying:
giovibob said:
Hi guys! I already asked this question but....why a smartphone as S PLUS received Android lollipop and Kernel 3.4.105 and the S advance is stop to KitKat and kernel 3.0.101? Thi our smartphone has absolutely no developer able to do it?:crying::crying:
Click to expand...
Click to collapse
bcz S plus has qualcomm snapdragon Soc (easily available sources ) and our crap has novathor which has no source ...so don't expect any new update for our device...even present source builds are not bug free for i9070 .
this thing made clear many times by many devs
so don't create new thread for this thye of Qs...we have Q&A thread plus search option.
This is amazing news. Although, I'm not sure whether this is going to affect our device or not. It's not that the devs are unable to pull this off, I think it's more of a matter of the practical aspect since most people follow the natural course and update their dated hardware. Nonetheless we can just hope that our device is not forgotten.
Team Canjica not give more support for janice, so no lollipop for S Advance
Janice sources are horrible, could compile lollipop, but with many bugs
uncreator said:
This is amazing news. Although, I'm not sure whether this is going to affect our device or not. It's not that the devs are unable to pull this off, I think it's more of a matter of the practical aspect since most people follow the natural course and update their dated hardware. Nonetheless we can just hope that our device is not forgotten.
Click to expand...
Click to collapse
It's sad to say but it's already forgotten
I say too that our janice is forgotten...But remember this: never say never, although i think that janice can't run lollipop.We already experience lags on jb, cm.If we had 1gb ram,then was other story...but still hard to build lollipop without sources.
We won't get more performance using lollipop, we will get a slow device.
Why you really wants lollipop? Just for the look, isn't it? You can make a theme like that and that's it.
I know that is not allowed,but if anyone need that novathor sources which chinese guy posted on xda few months ago and know how to adapt them for lollipop (if is possible) tell me...i still have them in my pc and I'll never delete them.
What is the rom which is trully fast and smooth ? The answer is GIINGERBREAD. Yeah, it is outdated, but consume less ram, and that we need, free ram.
Force said:
What is the rom which is trully fast and smooth ? The answer is GIINGERBREAD. Yeah, it is outdated, but consume less ram, and that we need, free ram.
Click to expand...
Click to collapse
Have you tried Vanir? I use it for like 6 months now and don't even think about anythink else. Fast, no fancy colorful stuff jumping at me from every menu, good battery life, what more can you want?
In a day or two I'll also put here the kernel I use with Vanir along with my new governor, if you're interested.
mkaluza said:
Have you tried Vanir? I use it for like 6 months now and don't even think about anythink else. Fast, no fancy colorful stuff jumping at me from every menu, good battery life, what more can you want?
In a day or two I'll also put here the kernel I use with Vanir along with my new governor, if you're interested.
Click to expand...
Click to collapse
I'm using first or second version of Vanir and I'm satisfied and i never updated. I installed many apps and became little slow. Gingerbread still better for ram management i think.
Why i use vanir ? Because i see that on this rom the camcorder isn't so darker like other roms, at least for me (after changing exposure). Although i record videos rarely, when i want to do it i don't want darker videos...
I'm interested in your kernel, and i think not just me
PS: i use just vanir and sami os
Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
so basically you have good intentions, no plan and a home server )
what we really need is a unification of all the different but not really different roms and their devs,
then its possible to see a future for long term support for all devices, or at least many.
anyhting else is jsut another project that will or will not die, based on good will and free time of the maintainer, mostly not even reckognized
due to the chaos of fragmented android and even more fragmented custom rom scene.
godkingofcanada said:
Hoping this is the right section since its not device specific.
Experienced or not, it doesn't matter. I've been on XDA for a number of years. And am noticing things from my own experience and talking to others. Its hard to get help sometimes. Not all devs want to talk. Teach. Or help people all the time. Devices are being dropped from support. Maintainers are leaving the scene. Currently I have an Oreo and pie ROM for s6e+ and note 5. With the list of devices being dropped, and surprising amount of people reaching out to me for support, I decided it may be beneficial to recruit a few people who want to develop ROMs. This is a great chance to learn. I would like to pick up at least partial support for several more devices, and need some help to do it. My goal in this endeavor is to continue to provide ROMs to people who need them, while teaching other users to develop. This will help to bring fresh life to the scene, and allow support for more devices to be added. If you are interested reply below or inbox me. There is a google hangouts set up, and other methods of team communication will follow. I also have a home server with a 24/7 connection and no data limits on my internet, and an ftp set up to host files directly and not need third party sites.
Click to expand...
Click to collapse
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I respect your Idea but I don't think something like this is required.You see I had been using linux for 4+ years and was pretty adapted to it when I switched to a Note 3.Recently I discovered the Modding part of it and the huge development of custom roms and kernels.and despite having no clue what I was doing I could easily develop a Kernel without a hassle.I went even one step further and made a halium port for it.Sure it didn't boot the first time but by using methods on xda already discussed in detail I was able to make it work.So,the main thing is that someone like me who has no experience could make a ROM in 3 hours without any complications(Except those who could be solved by googling).Then anybody could do it.Currently there isn't a ROM bug or a issue that hasn't been discussed on either xda or other android development sites.But that doesn't mean we shouldn't help newcomers.But it is rare for someone to look on the other side of development and there is enough documentations for him to do it.Maybe too much.qq
Click to expand...
Click to collapse
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
godkingofcanada said:
You can't just make a ROM for any device is 3 hours. It doesn't always work that way. Especially not if building from source
Click to expand...
Click to collapse
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I just followed a guide.On an XL VPS. With maybe 22GB ram and 16 xeon cores
Click to expand...
Click to collapse
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
godkingofcanada said:
I don't disagree sometimes it is easy. But what if lineage or GitHub don't have all necessary files for the build? And then you need to extract them from your phone manually, or if build won't boot up and needs modifications to the kernel.. fixing drivers that do not work. It's not always so simple as build, flash and finish.
Click to expand...
Click to collapse
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
I did face issues.The End of the guide covered the basics of logging stuff and finding things.They were just as same as debugging a linux OS but yeah you're right as I did face the extracting files(dunno what was supposed to do).So I wrote "extract proprietary vendor code from ROM" and boom lineage gave it to me.Also the guide was only for devices that exist on lineage and sometimes we need to start from scratch.And maybe We both are,Who knows what the future might bring,BTW have you heard about Google's new Boy Fuchisa or something like that.I wanted to talk someone in the field of development about this but nobody was bringing up the non-linux version of Google's OS for smartphones.
Click to expand...
Click to collapse
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
godkingofcanada said:
Yes I heard about it. I stumbled across it by accident looking for a way to shim the s6 edge plus cam on my pie rom. It lead me to reading about vulkan, which showed me a new Google os. It looks nice
Click to expand...
Click to collapse
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Well It seems that it uses a Different type of kernel "microkernel".For someone as stupid as me I don't get it what was the difference between a microkernel and monolithic one on an android device(or a low powered arm processor based board that has a screen attached to it)Will it be performance,Faster loading,Efficiency.I can find a million articles on microkernel vs monolithic but they are in latin for me.But you can just give me the crash course in maybe 3-4 lines.
Click to expand...
Click to collapse
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
godkingofcanada said:
Device drivers, protocol, file systems moved from kernel to user. It's got less code, more lightweight. And it was created with embedded systems in mind. In theory it should be faster, and more suited to small devices like phones with embedded systems. Giving devices their own dedicated kernel finally instead of butchering a Linux kernel to suit their device needs. It's also universal in terms of cross platform
Click to expand...
Click to collapse
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Sent from my Pixel 3 XL using Tapatalk
Atifbaig786 said:
Now that's more like it.I was afraid that android was finally going to commit close source(or suicicde).But since it's open source and I hear good things from you and 4 other guys who have experience in doing stuff I think,Hope and Pray that it might be a good change.Also thanks for using plain English and being a Open guy.Currently I am thinking that 5 years from now someone gonna run into this post and have a little smirk on his face for you who is reading this,Quote and tell me was it good?Was we good?
Click to expand...
Click to collapse
I think the changes appear good. Less stuff locked away in private, more easily accessible to all. Treble has the vendor stuff available to roms that aren't stock, this will make the kernel tiny and easy to build. One by one the barriers people have to overcome to build their own roms are being taken away.