Database Develop

[Q] Android L (5)

How soon do you guys think a ROM will be made for Nook HD/HD+ after Android L releases? Any guesses? Cyanogen have done a great job with 4.4

That's just going to be a lot of assumptions

sandsofmyst said:
That's just going to be a lot of assumptions
Click to expand...
Click to collapse
Probably why you were the only one to reply xD Thanks man

Just don't like to see 0 replies. That said, there's one now and then that I won't reply to. However, L is of much interest to me and some of the supposed improvements will hopefully be great. Plus L on the nooks would hopefully be even better. So I share your enthusiasm.
The release time could be shorter or longer depending on the amount of porting work to be done. There's other variables too. But someone else might also before cyanogenmod which would be fun.

Thanks for the reply, I agree on L being even better on the Nook varieties. Can't wait!

I was finally starting to look into bumping stock off og my HD9 and saw this... guess I can wait 4-6 months for this to all take shape... I wouldn't want to lose my progress in PvZ2 at this point anyhow

My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.

Goggles2114 said:
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Click to expand...
Click to collapse
With the nook being the nook... you could be right. The latest tech really makes android smooth, not android on the older tech.

OSs don't tend to get faster as they get fancier and the latest tablets and phones have much faster hardware (and more RAM).

Well I mean take a look at the iPhone 4S, it used to be able to run IOS 5 and now it's up to IOS 8 and it's still pretty fast. These companies need to focus as well on making the newer OS work well with older devices. I mean the HD/HD+ is only 2 years old...

Corkerman said:
the HD/HD+ is only 2 years old...
Click to expand...
Click to collapse
It might be 2 years old but the hardware was never really all that great as it wasn't a top-of-the-line tablet when it came out.
Anyway, that's why I'm hoping 5.0 does something to improve performance, but wouldn't expect miracles from it if anything at all. Android just does better on newer hardware.
_________________________
Looks like cm11 m12 improved responsiveness a noticeable amount and finally too. Still not the same amount newer hardware would cause but a welcome improvement.

Goggles2114 said:
My question is whether or not upgrading to L will be a performance boost or if it'll just be bloat on the hardwwre. Won't know til it gets here though.
Click to expand...
Click to collapse
I upgraded my Nexus 7 2013 to 5.0.0_r2, and it is noticeably faster than 4.4.4_r2. With kitkat, art sped up menus and navigation, but not really much else. Lollipop is all art - no dalvik option - and not only are menus and navigation faster, but it seems to speed up apps as well, mainly the Chrome browser. I've been using Lollipop for a couple of weeks now, compiled 5.0.0_r2 with 4.4.4 blobs, and I've been pretty impressed. I just built 5.0.0_r5 from source yesterday with the new 5.0 blobs they released. I haven't had time to install it, but I would imagine the performance to be the same as 5.0.0_r2.
Unfortunately, the Nook HD depends heavily on CM source, and quite frankly, it's a little above my expertise. So I'll just have to wait for verygreen, bokbokan, and leapinlar to give us a lollipop build for the Nook HD and HD+.

cahrens said:
I upgraded my Nexus 7 2013 to 5.0.0_r2, and it is noticeably faster
Click to expand...
Click to collapse
That's great to hear it's indeed faster even though it's on a Nexus! Great job and hopefully the three guys can work some magic into the HD's

Corkerman said:
I mean the HD/HD+ is only 2 years old...
Click to expand...
Click to collapse
In consumer products, that's an eternity.

I've been working with Lollipop builds for a few weeks now, so I have a fairly decent idea of what is involved.
1) sensors.c (touchscreen) requires a minor rewrite.
2) hdmi_audio.c requires a symbol to be dropped (or qcom hardware specified, either/or)
3) selinux rewrites... blehch!
4) hwc, domx ... dunno yet, there's apparently working lollipop compatible source available
5) Changes to build/core/Makefile cause most builds to hang on imgdiff, some reversions are required to get around this.
OK, even with all this, I've only had one build boot enough to get some logs. Ironically it was my very first build.
http://pastebin.com/CNBrENWD
I did end up adding libcorkscrew. Anyway every subsequent build I've done reboots even before being able to get a last_kmsg. I'm at the point now where I believe our kernel will need to be patched to handle gcc 4.8. Changing the build to use gcc 4.7 is doable, but isn't very pretty or nice (too many headers have changed).
Anyone have any other hints or suggestions?

Jon Lee said:
I've been working with Lollipop builds for a few weeks now, so I have a fairly decent idea of what is involved.
1) sensors.c (touchscreen) requires a minor rewrite.
2) hdmi_audio.c requires a symbol to be dropped (or qcom hardware specified, either/or)
3) selinux rewrites... blehch!
4) hwc, domx ... dunno yet, there's apparently working lollipop compatible source available
5) Changes to build/core/Makefile cause most builds to hang on imgdiff, some reversions are required to get around this.
OK, even with all this, I've only had one build boot enough to get some logs. Ironically it was my very first build.
http://pastebin.com/CNBrENWD
I did end up adding libcorkscrew. Anyway every subsequent build I've done reboots even before being able to get a last_kmsg. I'm at the point now where I believe our kernel will need to be patched to handle gcc 4.8. Changing the build to use gcc 4.7 is doable, but isn't very pretty or nice (too many headers have changed).
Anyone have any other hints or suggestions?
Click to expand...
Click to collapse
If it were me, I'd look here http://forum.xda-developers.com/kindle-fire/development/rom-kernel-unofficial-cm12-0-otterx-t2958155 or here http://forum.xda-developers.com/kindle-fire/development/slimpop-otterx-t2957450 for some guidance.
Hashcode is a legend on XDA and he has almost single-handedly kept the very old, TI OMAP 4430 Kindle Fire alive. As for lovejoy777, currently, he has been the most active, hard working dev for that same KF. Hashcode has CM12 working and lovejoy777 has Slimpop.
Since our device is so similar to the KF and Hashcode has contributed to the Nook in the past, looks to be a good resource??? Then again, verygreen could also pop in sometime down the road.
Mike T

It was because of installing CM on a Kindle Fire 2 for a friend that I decided to purchase a Nook (wanted an OMAP).
I checked both threads over but didn't immediately find any lollipop android_device source available.
I was right about the kernel (arm/lib/memset.S?). Only took me a week to figure it out.
I'm not quite sure yet what to make of the second set of logs, but this is where I'm at now.
http://pastebin.com/EXnJpp3L

Jon Lee said:
It was because of installing CM on a Kindle Fire 2 for a friend that I decided to purchase a Nook (wanted an OMAP).
I checked both threads over but didn't immediately find any lollipop android_device source available.
I was right about the kernel (arm/lib/memset.S?). Only took me a week to figure it out.
I'm not quite sure yet what to make of the second set of logs, but this is where I'm at now.
http://pastebin.com/EXnJpp3L
Click to expand...
Click to collapse
One of my first android devices was the 1st gen KF and Hashcode helped make an inexpensive E-reader a very viable android tablet. I would PM Hashcode and/or lovejoy777. Hashcode is usually very busy but he has always been helpful towards other devs, I know he gave some assistance to lovejoy777 with SlimPop.
As for lovejoy777, he's fairly new at development but seems to be very helpful. I think he also may have gotten some help/guidance from MwisBest who built a LP rom for the OMAP 4460 Galaxy Nexus. I mention this because I believe he knows the importance of cooperation among devs. As an aside, while reading his thread I think I read that he was in the process of "cleaning up" his github. So, he could be a good source.
Maybe also PM killersloth. He built quite a few nice roms for our Nooks last year and just recently expressed some interest in trying to get LP on our device. Maybe if you contact him, you guys can make something happen. I'm an old fashioned XDA'er that believes cooperation amongst devs and end users is essential in the community. Every little bit can help.
http://forum.xda-developers.com/showpost.php?p=57255968&postcount=14
Anyway, you seem to be a very sharp guy. I wish you luck in getting LP to the Nook. I wish I could contribute more but I'm more of a file swapper and modder of existing work than a dev. :laugh:
Mike T

Moving to Texas in three days, been hectic around here lol.
I had major issues with hwc, selinux, and our old configs. Hashcode must have plowed through it if its running on otter. I'd check his commit history for some tips.
We needed this for prebuilt boot image before
http://review.cyanogenmod.org/#/c/36813/1
I needed it a few weeks back when attempting to build. They might have brought up their own method since then.
I wish they would have called it SlimPop instead of SlimLP ??

A 5.0 build for hummingbird would be nice. Hopefully it won't be hard to modify an ovation build since all the devel appears to be on ovation.

Open source Superuser for Android 6.0

I mostly work with Nexus 6, but since it is so easy to tack on the 5 as well....
Lets just say that this applies equally to Nexus 5 and should be *really* helpful...
http://forum.xda-developers.com/nexus-6/general/root-t3231211
One thing to be aware of... I haven't even tested to see if it boots and won't be able to until Sunday. I can't imagine why it wouldn't though, since the device specific patch is, literally, trivial (works on 6 and 9).
Bugs, features, etc., please use the issue trackers on my or phhusson's github projects, as it applies to the particular components.

doitright said:
I mostly work with Nexus 6, but since it is so easy to tack on the 5 as well....
Lets just say that this applies equally to Nexus 5 and should be *really* helpful...
http://forum.xda-developers.com/nexus-6/general/root-t3231211
One thing to be aware of... I haven't even tested to see if it boots and won't be able to until Sunday. I can't imagine why it wouldn't though, since the device specific patch is, literally, trivial (works on 6 and 9).
Bugs, features, etc., please use the issue trackers on my or phhusson's github projects, as it applies to the particular components.
Click to expand...
Click to collapse
This should be exciting i can't wait to see what comes of this! Good luck to you! :good:

navy676 said:
This should be exciting i can't wait to see what comes of this! Good luck to you! :good:
Click to expand...
Click to collapse
If you try it out, you can find out. I need testers to make sure that everything is working as it is expected to.

doitright said:
If you try it out, you can find out. I need testers to make sure that everything is working as it is expected to.
Click to expand...
Click to collapse
Good luck to your work

Compiling Unofficial CyanogenMod 14.1 for Nexus 6

Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.

David B. said:
Hello XDA Community,
I am interested in using the unofficial build of CyanogenMod 14.1 available here, but I would like to learn how to compile on my own from the repository provided by the developer. Unfortunately, I do not know how to go about doing this. Could someone please help me out? I have looked at the CyanogenMod Wiki entry for how to compile CyanogenMod for the Nexus 6, but the information is out of date according to what I was told in a post I made on Stack Exchange's Android Q&A site. The only thing that I understand about the build process is that I need to use Linux, so I have set up a virtual machine in VMware running the latest version of Ubuntu. Where do I go from here?
Thank you,
David B.
Click to expand...
Click to collapse
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.

zelendel said:
To be honest You will be better off dual booting. Compiling with a VM normally has more issues then not.
Then I would look at Google developer page.
Also keep in mind that compiling from CM means you get all the bugs they never fixed. You would be better off going with AOSP and then finding the features you want to add and then add them yourself.
Click to expand...
Click to collapse
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.

David B. said:
I would love to build my own CyanogenMod based on AOSP and then merge in the features, but I don't even know how to build directly from AOSP.
Honestly, all I really want is stock with all of the additional developer mode features that CyanogenMod has along with root access. I love the ability to use root without extra apps, and wireless ADB is sweet when I'm too lazy to go get my USB cable. And of course, I want to be able to use future versions of Android on my phone even though 7.0.1 is supposed to be the last version for Shamu. Could I somehow merge those aspects together and just pull patches from AOSP, build, and flash?
Also what's wrong with using a VM to compile? I've read that problems occur if you don't have enough RAM allocated to the VM, but I've assigned it 16GB so that should not be a problem. As for attaching my phone to the VM, I am using VMware, which has better support for removable devices than VirtualBox.
I'm sorry if I misunderstand something you said. It's probably obvious, but I know pretty much nothing about what I am doing which means I'm likely to ask lots of questions that seem ridiculous to those that are well-versed in this sort of thing.
Click to expand...
Click to collapse
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.

zelendel said:
You do know that there is an app for SU built into CM right? So it is no extra apps then any other rom.
Could you yes but it will be lots of work due to what CM changes in the source code. It is one of the many reasons (on top of years old bugs that were never fixed) That many teams stopped using them as a source. The Shamu will be supported by 3rd party developers for a while to come.
Normally ram is an issue but other issues also happen.
I dont know anything about having to attach your device to VM as I have never used VM due to advise from the developers here.
Asking questions is not that big of a deal as long as you do your research. There are tons of TUT on the site about setting up a build setup. Just use the search and spend a few days reading. Mainly where the licenses are concerned. Also commit authorship. Which is you make your own rom it is very important.
Click to expand...
Click to collapse
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?

David B. said:
Okay, so I have done some research and have a solution for how to use root with stock Android, but as soon as stock Android support is dropped from the Nexus 6 I will have to compile it myself which I am not sure how to do and would like to learn. Do you have any suggestions for what to go to learn since everything I am finding is not about compiling, but is instead about using an existing build?
Click to expand...
Click to collapse
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.

zelendel said:
Here you go
https://source.android.com/source/initializing.html
Mind you getting root is more then adding an app for it. You will also have to do some kernel edits.
Click to expand...
Click to collapse
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.

David B. said:
Thanks! I also found this. I have not really looked at it too much yet, but it seems like it has the potential to help me with what I want. Why would I need to make kernel edits? I thought all I needed to do was use TWRP to flash SuperSU after flashing the ROM.
Click to expand...
Click to collapse
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.

zelendel said:
SuperSU edits the kernel when you flash it. Most of what allows root is in the kernel.
Yes that is a great resource. Just take your time and read it. You could have a working set up and build in about 2 days (given the first sync of the source code could take more then 24 hours depending on your connection.
Click to expand...
Click to collapse
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.

David B. said:
One thing that I still cannot figure out after all of this reading is what to do to get AOSP to build for devices that are not officially supported by it. Granted, this is not a problem for the Nexus 6 right now, but it will be eventually, and I want to know how to handle it when it does become an issue. I've started cloning the repository. My connection gets a top download speed of 60Mbps so it should be reasonably fast.
Click to expand...
Click to collapse
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have

zelendel said:
At that point you will need to know what you are doing as you will have to make the code changes to make it bootable. I hate to say it but the n6 maybe doa after this as anything after 7.1 will need dual partition setup which the n6 doesn't have
Click to expand...
Click to collapse
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?

David B. said:
What's stopping the phone from being repartitioned in the same way you repartition a hard drive?
Click to expand...
Click to collapse
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0

zelendel said:
The main issue is none of the software for the n6 are made to work with it. All the drivers have to be rewritten. Also all of the new Vulcan graphics drivers won't work on the n6. This is why it didn't get all the features of 7.0
Click to expand...
Click to collapse
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.

David B. said:
I had not heard of this before. I was researching it online a bit and I cannot figure out which features are missing from the Nexus 6 version of Nougat. Also, Nougat has to support older hardware for devices that don't support Vulkan, so there's no reason they can't do that for Android O, and it they don't, surely someone smarter than I will be able to hack it together.
Click to expand...
Click to collapse
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things

zelendel said:
That's the thing is android O will only be official supported by devices that can use it. Remember the nexus 6 support ended in October so there won't be an official O release for it.
Will there be a hacked together set up? Oh I'm sure there will be. It will just be without the Vulcan graphics drivers and the new update system which needs the dual partition layout.
The missing features are no background updates, no Vulcan drivers among other things
Click to expand...
Click to collapse
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.

David B. said:
Well if the only things I lose are Vulkan and background updates, I am cool with that. It sounds like Vulkan is intended for games, and since I hate mobile gaming, an adapted build that works with the existing graphics drivers is not a concern at all. As for background updates, I would rather not have those because I like to know when my phone receives updates.
Click to expand...
Click to collapse
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.

zelendel said:
The Vulcan driver will be replacing the graphics drivers for everything soon. I can't think of much as I never use stock software.
Click to expand...
Click to collapse
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?

David B. said:
I am sorry, but I am afraid I do not quite understand what it is that you said. What can't you think of?
Click to expand...
Click to collapse
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.

zelendel said:
There were many features that came with 7.0 like the new advanced doze and some other stuff. I dont use stock software and to be honest most of the stuff from 7.0 wasnt even really worth the update to me.
I have had a nexus since day 1 on and off and this was the first time I wasnt excited about the update. Even less with the new updates coming and google locking android down more as well as them moving most of the new stuff to closed sourced stuff. Heck even just having the bootloader unlocked is causing things not to work.
Click to expand...
Click to collapse
Really? What doesn't work with the unlocked bootloader?

David B. said:
Really? What doesn't work with the unlocked bootloader?
Click to expand...
Click to collapse
Things like android pay and saftynet. They are now starting to look for unlocked bootloaders. then you have those that are blocking apps due to root or xposed.

LG Urbane revival

As with the AW 2.0 Update from today, can we expect getting this forum active again? I am hoping to see an optimized kernel and rooted version of urbane to get maximum performance as i feel especially google assistant has become somewhat sluggish....

endrancer said:
As with the AW 2.0 Update from today, can we expect getting this forum active again? I am hoping to see an optimized kernel and rooted version of urbane to get maximum performance as i feel especially google assistant has become somewhat sluggish....
Click to expand...
Click to collapse
Waiting for kernel sources

Skin1980 said:
Waiting for kernel sources
Click to expand...
Click to collapse
As am I :good::good:
I've had a kernel tree and ramdisk sitting on the backburner since October until AW 2.0 came out, was actually planning on releasing it for 1.5 if we didn't get any update from LG by the end of the month. Of course, now it'll need to be rebased over the new kernel source. Will do a TWRP build w/ f2fs support as well unless someone beats me to it.
little note, if anyone's cp'ing, don't pick the 2 squashfs commits, they're incorrect, just haven't had the time to do that myself

Bluenami said:
As am I :good::good:
I've had a kernel tree and ramdisk sitting on the backburner since October until AW 2.0 came out, was actually planning on releasing it for 1.5 if we didn't get any update from LG by the end of the month. Of course, now it'll need to be rebased over the new kernel source. Will do a TWRP build w/ f2fs support as well unless someone beats me to it.
little note, if anyone's cp'ing, don't pick the 2 squashfs commits, they're incorrect, just haven't had the time to do that myself
Click to expand...
Click to collapse
Looking forward to seeing what you come up with. I too feel that the new update is running sluggishly on my Urbane first generation too. Would GREATLY appreciate your efforts to provide us with a speedier version of it.

Skin1980 said:
Waiting for kernel sources
Click to expand...
Click to collapse
Kernel tree is out

Bluenami said:
Kernel tree is out
Click to expand...
Click to collapse
are there anyware custom roms with aw2 for thr the urbane 2?

I think AW2 is so crap that even customizing is couldn´t be a good system...

mtmello said:
I think AW2 is so crap that even customizing is couldn´t be a good system...
Click to expand...
Click to collapse
i never really tried 1..5. is it better? what can we do with it than? i might give it a try

sebj84 said:
i never really tried 1..5. is it better? what can we do with it than? i might give it a try
Click to expand...
Click to collapse
It is really very hard to tell you what is better in AW1.5 because almost all new thing in AW20 is bad! Gonna try to summarize in few words:
AW20 is a big change in the concept: from the AW1.5, smartwatch is a extension of your smartphone. AW2.0 is almost a smartphone in you wrist. Bad functionality, bad performance and bad concept! (I already have a smartphone and I don´t want another one in my wrist!).

mtmello said:
It is really very hard to tell you what is better in AW1.5 because almost all new thing in AW20 is bad! Gonna try to summarize in few words:
AW20 is a big change in the concept: from the AW1.5, smartwatch is a extension of your smartphone. AW2.0 is almost a smartphone in you wrist. Bad functionality, bad performance and bad concept! (I already have a smartphone and I don´t want another one in my wrist!).
Click to expand...
Click to collapse
ok... i have to say i use the watch as second phone. for my private messaging and calls. than i can leave the work at home.
i think i go wit aw2 better than?

I just joined the smartwatch club and both of mine had AW2.0 .. so i'm not sure how it compares to AW1.5 but I do know I wish it did have more stand alone capability.. I would like to be able to see all my text messages and respond to certain ones and avoid taking my phone out of my pocket..
I do hope there will be more travel here on this forum.. doesn't seem like there is much activity anymore

Android 4.0 For Samsung Galaxy Pocket (Further Development Attempt)

Hello!
I have old Galaxy Pocket, and when i saw that no one even tries anymore to do anything for this little cute phone, I'm gonna do it
And first, is gonna be Android 4.0
i know people already did that... but these version's didn't work fully , all of them had some sort of problems
and that's what i'm gonna try to do, I'm gonna modify and patch one of better version's of ICS for pocket that already exists
so... i guess that's it... I'm gonna update this when i will make some progress

QUIR-Research&Development said:
Hello!
I have old Galaxy Pocket, and when i saw that no one even tries anymore to do anything for this little cute phone, I'm gonna do it
And first, is gonna be Android 4.0
i know people already did that... but these version's didn't work fully , all of them had some sort of problems
and that's what i'm gonna try to do, I'm gonna modify and patch one of better version's of ICS for pocket that already exists
so... i guess that's it... I'm gonna update this when i will make some progress
Click to expand...
Click to collapse
I made a "camera and mic fixed" but, still have bugs...
https://1drv.ms/u/s!AtgktraixCghnkfHvmEO0QWh0fNL?e=HEacm9

So any progress?
I am from the s5830i community and since our device share the same processor, I thought I can come and see if any of your bug fixes would work on the s5830i. Current issue is headphone routing but thing is I don't know if it is an issue for you guys with the Pocket.
Edit: Dug into the android development section a bit and found out you guys have the same front speaker and headphone routing issue.

hey, this is great man . i cant wait (i dont know if that you try to do works on my gt-s5301l or is the same). if you can do for a upper version of android (like 4.2) i would be happy. (do it if you want :v)

They aren't compatible
rodrigo151515151515151 said:
hey, this is great man . i cant wait (i dont know if that you try to do works on my gt-s5301l or is the same). if you can do for a upper version of android (like 4.2) i would be happy. (do it if you want :v)
Click to expand...
Click to collapse
Nope, Pocket (S5300) and Pocket Plus (S5301) have different chipset and then aren't compatible.
There's currently a 4.2 ROM for you device, but it is in very early stage.
I also have a S5301L and I'm trying to make a decent ROM for this device, but the only and hardest problem is the touch driver not working. I'll post here if I can fix that, but seems that this will be really difficult (the original dev leaved the development 4 years ago for the same reason, broken touch).

MaicoLinuX said:
Nope, Pocket (S5300) and Pocket Plus (S5301) have different chipset and then aren't compatible.
There's currently a 4.2 ROM for you device, but it is in very early stage.
I also have a S5301L and I'm trying to make a decent ROM for this device, but the only and hardest problem is the touch driver not working. I'll post here if I can fix that, but seems that this will be really difficult (the original dev leaved the development 4 years ago for the same reason, broken touch).
Click to expand...
Click to collapse
oh, i see. its so good to hear this device will continue having "support" on this days..... ah no mames eres de buenos aires xd

any updates? is your interest in this device still there? best regards

Im very sorry for such a long unactivity , i still have interest in doing that update, i just had several work and device problems and i had to do something about them

It's bad that you also abandoned the firmware. And then I still use the pocket and there is not a single normal firmware

Alexey Orlov said:
It's bad that you also abandoned the firmware. And then I still use the pocket and there is not a single normal firmware
Click to expand...
Click to collapse
The Galaxy Pocket (GT-S5300) uses an ARMv6 processor, that core is nowadays weak and has a lot of limitations (most of them can only be passed by emulation, but as it's a weak cpu the performance would be terrible).

QUIR-Research&Development said:
Im very sorry for such a long unactivity , i still have interest in doing that update, i just had several work and device problems and i had to do something about them
Click to expand...
Click to collapse
Are you still doing it? How is progress going?

I'm trying to keep Galaxy Pocket alive with Custom Roms, but it doesn't work ...

QUIR-Research&Development said:
Im very sorry for such a long unactivity , i still have interest in doing that update, i just had several work and device problems and i had to do something about them
Click to expand...
Click to collapse
Any update?? Please continue if you drop

Last seen: Nov 29, 2021
haizz...