Now, I know for a fact that this phone does NOT have OEM support for Android 4.4. However, LG provides a lovely open source program, so I do have two sets of files.
One is for building the kernel for the phone, with all of the OEM-specific files for doing so, including drivers and such.
The other is I believe to be the device tree for the US760, with a bunch of propitiatory code. I'm not sure what exactly is important there.
The latest version of Android this device natively ran on was Froyo, and then didn't receive updates because the device didn't do very well sales wise.
My main question is if using that code is worth it, or if I should just go with basing off of a generic AOSP device tree for the processor and seeing how things go. There's little to no documentation on this phone (GSM/Phone Arena don't have almost any info, doesn't even exist on Wikipedia) so it's a bit difficult to get accurate specs for the device, but here goes.
(From HardReset.info)
Chipset: Qualcomm Snapdragon S1 QSD8650
CPU #1 Type: Scorpion
CPU #1 freq.: 1000.0 MHz (1-core)
GPU Type: Qualcomm Adreno 200
RAM Memory: 512.0 MB
Are those specs even enough to run Android 4.4? I don't mean run well by any means, but would the device even work?
My biggest concern is the dual screens. I don't know if it's a hardware switch or something baked into the kernel or something, but I'm not sure how well it would work if I based off of AOSP, or if only one screen would work, or if the phone just wouldn't boot. Here's a picture or two so you know what I mean.
{
"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"
}
Interested to see if anyone has any wisdom to bestow upon me.
Bit of an update.
Found out that the HTC Droid Incredible would be a great base for a Cyanogenmod rom.
Related
Open webOS 1.0 announced: HP to complete webOS open sourcing by September, Enyo 1.0 and 2.0 code available today
http://www.theverge.com/2012/1/25/2732672/open-webos-10-announced
....HP has gone into detail today on exactly when and how developers will be getting access to webOS code. The company expects the entire open sourcing process to be complete by September, while Enyo, the application framework that debuted on the TouchPad and underpins webOS 3.0, is available as of today along with related developer tools. When open sourcing is complete, the finished product will be known as Open webOS 1.0.
Click to expand...
Click to collapse
{
"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"
}
Hmmm.... interesting. I see that the standard Linux kernel will be open sourced in March. Hopefully they release kernel sources for already-made devices (our TouchPads) so we can get the proprietary drivers (display, camera, etc.)? I know that kernel patches and drivers were released a long time ago, so I'm hoping this expands on that.
If these releases are about releasing source for WebOS devices hoping to build on the platform, then this should really help with the TP, IMHO. If this is only about Open WebOS as a platform, then... yay? I guess it's cool that WebOS is living on haha.
Smith7018 said:
Hmmm.... interesting. I see that the standard Linux kernel will be open sourced in March. Hopefully they release kernel sources for already-made devices (our TouchPads) so we can get the proprietary drivers (display, camera, etc.)? I know that kernel patches and drivers were released a long time ago, so I'm hoping this expands on that.
If these releases are about releasing source for WebOS devices hoping to build on the platform, then this should really help with the TP, IMHO. If this is only about Open WebOS as a platform, then... yay? I guess it's cool that WebOS is living on haha.
Click to expand...
Click to collapse
I'm hoping it means we can get finally some decent AV codes!
This is for anyone who is rooted!!
Lets see those variant's cpu's you have for more undervolting and saving battery:good:.
Where can I find that Variant?
You have to have BLADE kernel by maxwen installed. Then use
Code:
cat /sys/kernel/tegra3_dvfs/cpu_millivolts
and it will be printed on top (process_id) is your variant.
Here is a screenshot from my device:
{
"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"
}
What is a variant, and where did it come from?
This is mainly the type of build quality your chip has and allows a more accurate way to determine how hard you can push you're chip with Undervolting(UV) and Overclock(OC).
Click to expand...
Click to collapse
AP37 have 2 different types (3 and 4) of variant's.Hox has 4 types.
Please note that there are even more variants in each variant. You can easily have a variant 3 and another person has the same but you still have different performance. "They qualified the chips based on random sampling of the wafers and mark the ENTIRE wafers as such. It just means that the "average" performance of that wafer is of certain quality, but it does NOT mean every chip on that wafer would behave exactly the same.... ". Remember the golden rule: No two chips are created equal!
Also people should not blame HTC as they don't test every chip Nvidia made. They only test a few and then the phones will go in to production. So if you want to rage at someone please don't do so at HTC
Click to expand...
Click to collapse
All credit goes to our Blade kernel developer maxwen and timlambo for his poll
I have variant #4 in my HOX+
variant 3. so which is which?
You can try undervolting by using blade kernel.
For example undervolting -50mV:
Code:
echo -50 > /sys/kernel/tegra3_dvfs/cpu_millivolts
For -100 mV just change value:
Code:
echo -100 > /sys/kernel/tegra3_dvfs/cpu_millivolts
My device has variant 3 and undervolted -100mV.Seems stable for my variant.Please just try and post your undervolting results.
Also i will have request for more undervolting support(for now max -100mV supported) for blade kernel from maxwen.
Best regards
4 here
Hello, the main problem is that any app using advanced graphics is crashing on me, so I decided to make a test and downloaded OpenGL ES 2.0 Demo to try.
And the result that I get was unbelievable, there's a gallery of my screenshots.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As for my phone, I already had a long story with it, there's the thread, where you can get all the info on the other site, but I'm not able to post links yet, but if you Google " Screwed up my G+ K3" you can find it.
If anyone can help me to get the GPU to work properly, I would be superthankful, I am already starting to lose my mind.
Seems like your GPU is damaged.
abhinavp649 said:
Seems like your GPU is damaged.
Click to expand...
Click to collapse
Can this be a result of bad drivers or something? I don't really know much about drivers on Android, if there are even some. There's a firmware for another GPU installed, so it might be the cause, but I got no idea how to fix it.
WilliamCZ said:
Can this be a result of bad drivers or something? I don't really know much about drivers on Android, if there are even some. There's a firmware for another GPU installed, so it might be the cause, but I got no idea how to fix it.
Click to expand...
Click to collapse
Very VERY likely if it was anything along those lines it would not be general user serviceable by any means.
Sent from my XT1060 using Tapatalk
siccoblue said:
Very VERY likely if it was anything along those lines it would not be general user serviceable by any means.
Sent from my XT1060 using Tapatalk
Click to expand...
Click to collapse
Well, if I'm getting it right, there's actually nothing to do it that just by my hands then. Since the firmware thinks, that there's another CPU and GPU installed, would flashing to the other firmware (some MT6572 one) work? I had a bad time when trying to port another firmware to it, it didn't boot or I just wasn't able to flash it - was getting errors.
Hello, I've never gone beyond entering developer mode on any of my phones, looking around carefully, then turning that mode off. I own two PH-1 phones, one is in full time service, and I would like to know of a tutorial / step-by-step to do what I need to do to maintain this phone with the images (ROMs?) that are being maintained and updated. I don't need the phone to do anything other-worldly, just keep it updated.
This is the only forum on here I'm allowed to post to, because I've been a listen-only member for a couple years but have never posted. I've just started using Ubunto 20.04 on a new laptop so I can get away from Windows, but I still have a Win7Pro laptop.
Thanks for your recommendations on how to get started -- safely started -- and how to learn what I need to learn.
Also, I just read some of the read-me-first stickys, and please allow this to also be my "Say Hi" email...
"MP"
PS -- I get a captcha, check it, get the green checkmark, but I see *no* image... I'm using firefox w/ NoScript (all scripts enabled for this tab), on an Ubuntu 20.04 laptop.
So no one cares to reply? Did anyone read it besides myself? Whiskeytangofoxtrot
@Messypotamia
If phone's Android OS isn't an A/B-partition-layout-system - what I believe because its Stock ROM is Android 7.1. - then updating a phone's Android requires phone's boot-loader is unlocked. This must get enabled within phone's Developer options - keyword: OEM unlock - what simply sets phone's unlock ability flag to 1 . Additionally it's necessary that ADB ( read: Android Debug Bridge ) gets enabled in phone's Developer options - keyword: USB debugging.
{
"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"
}
Hello, it is me again, testing something interesting on my Ugoos AM6 device.
A Group of developers called F.K. Tech Team have been posted distributives for different Amlogic SoCs.
They have managed to run XFCE and KDE Linux builds on mentioned SoCs.
I have managed to run both of them, but for KDE I had some problems with WIFI, so XFCE is more interesting for me.
The basic process to start distributive is simple:
1. Download archive with needed build from the F.K. Tech Mirror
(I put the link for Ugoos but you can find other devices on their website)
2. Burn flash drive or EMMC flash to plug in your Amlogic device.
Here I usually use balenaEtcher app for Windows PC (can easily google it)
Interface is so simple, so you need just to choose unpacked archive from the folder you have been downloaded and choose USB drive to burn (or EMMC flash)
3. Plug in the flash drive and start your Amlogic device. Some devices start initially from your drive and some of them need to be pushed using recovery button (there is a hole in AM6's housing case for this button)
4. First run may take a time, then follow simple instructions on the screen and in the end you got your XFCE ready to rock!
{
"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"
}
However, it is common problem for such SoCs to appear here too, video acceleration has only software support. So if you would like to check 1080p videos in youtube it is better to run Android or Andrroid TV even for such powerful SoC as AMlogic S922.
Hope guys can Fix it soon. For now, particularly for Ugoos AM6 there is a bunch of Android , Android TV and DualBoot CoreElec Firmwares