Database Develop

Keypad Light tweak?

http://forum.xda-developers.com/viewtopic.php?t=43822&highlight=keyboard
Is there any current way to perform this kind of tweak for the Wizard? I've just spent 20 mins searching but couldn't find anything related
Cheers!

nope

I have to say, despite it's nice design I'm really starting to get irritated with my Vario now... The processor is uber-slow compared to all other HTC devices, it's not tweakable anywhere near the amount the others are, it has an OMAP processor and thus won't be possible to run Linux etc on it.
I think even after 2 months it's time to look at a new device

blackobsidian said:
it has an OMAP processor and thus won't be possible to run Linux etc on it.
Click to expand...
Click to collapse
That's bull**** - the first (?) Linux smartphone from imcosys runs the TI OMAP 730 with embedded Linux;
http://www.imcosys.com/html/technische_daten.html
It's just a matter of people actually doing the work to port the O/S. Personally I think people who want to run Linux on Device X should just get Device Y which runs it natively - less work, and you support a company that already readily supports Linux on Device X-alikes.
As far as CPU-speed goes, it appears to vary per-reviewer. Some say it's slower, others say it's faster. I guess it'll depend on what you're doing with it.
Not sure what you mean with regards to 'tweakable', though. The only 'tweak' I'm readily aware of that works on e.g. the HTC Universal but not on the HTC Wizard is the keyboard backlight. They both run WM5 and are tweakable to pretty much the same extent as far as the O/S and running software allows.
That said - I obviously rather like mine. -That- said, I can see myself moving to a different device 2-3 years down the road quite easily, especially with all the network upgrades -and- the speed at which new devices are coming out. Wouldn't be too surprised if they're all rather like smaller OQO's by that time.. handheld, good battery, running will Windows XP (probably not Vista yet - hardware specs for that thing are through the roof)

See my comments have all been based on various forums I've read, posted on and recieved replies from. Apparently the OMAP architecture is completely different from most other processors and so it's a niche market (meaning people won't bother with trying to do anything good such as Linux, major overhauls of software, overclocking software etc) - Even Anton Tomov's Hack Master software is having issues with the overclocking functionality and keeps getting pushed back and back and back some more.
I have to say I bought my Wizard (MDA Vario flavour) because the design is slick and it was pretty fast in the shop demonstration. I didn't realise that the second I put anything on it, it'd slow down so much.
I've reflashed it with the best and fastest current rom out there:-
VERSION
ROM Version 1.6.7.1
ROM Date 38624
Radio Version 01.13.10
Protocol Version 4.0.13.17
ExtROM Version 1.3.2.102
And although it's faster than the bloated T-Mobile crap that it comes with by default it's still slow (my today screen only has SPB Pocket Plus and Pocket Weather on it but it still chugs occasionally) and it's an absolute nightmare playing something as simple as Arkaball!
"tweakable" I class as something I can mess around with. With my Samsung T100 I completely replaced the casin with a clear casing, reconfigured everything including LED colour and created my own firmware for it etc. I basically like to try and be individual which is why I won't got for a device already running Linux etc.
Tech Knowledge + Gadgets + being a geek = wanting cool stuff
OQO looks nice but huge. I'm looking for a device I can use for business (running a QA department) and as a mobile. Shoulda got myself a P990i... lol

Here's a proposition for your thoughts... if everybody is customizing their device, then not customizing your device makes you more of an individual
That said - yes, if you want that manner of tweakability, you should've gone for a different device. I'm not sure why a Linux-preloaded one would be excluded from the get-go because you didn't put it on there yourself.. it certainly should open up tweaking possibilities.
Overclocking software for the OMAP does exist - and I'm sure AntonTomov will get one out eventually as the number of devices using the OMAP increases. I'm sure the XScale will still be #1 for some time to be with the recent pricedrops and announced speeds (1GHz - vroom).
However, just because it's a different architecture doesn't typically stop the person who go "But does it run Linux? it does now!" on e.g. Slashdot . Of course if Linux was on your mind from the get-go, a little googling around would've readily shown which devices run it natively and which have been successfully made to run it, to whatever extent, and should've based your purchasing decision on that
For what it's worth, the Treo 700w (650? - been a while) was on my list, but once in the shop with the device in my hand, I knew I would grow to hate the form factor within the first week.

ZeBoxx said:
the first (?) Linux smartphone from imcosys runs the TI OMAP 730 with embedded Linux;
http://www.imcosys.com/html/technische_daten.html
Click to expand...
Click to collapse
There are many Linux phones already
http://openezx.org
but the ports to HTC Blueangel and HTC Universal
use more free software
You can also check Linux for OMAP page
http://focus.ti.com/docs/general/sp...mplatedata/cm/splashdsp/data/linux_com_portal

Correction... Everyone on this forum is customising their device... Most people in the real world buy a device and use it out of the box as they don't know or can't be bothered to upgrade it lol.
To be honest with you this is my first PPC device. Before this I was in a job where I didn't want or need the functions and features the PPC has and I had a K750i. Before that was a 7610 and before that a GX20.
I have to admit I was in the process of looking at PPC's when my K750i had an unfortunate incident where my fist went through the screen because it was crashing every 30 seconds... That's why I didn't research as much as I should have before getting my Wizard.
I've learned my lesson though and next time there'll be a LOT of research involved before I buy!
I'm assuming that individual hardware can't be replaced in the Wizard either? i.e. buying a faster processor/mobo etc? My mate's Universal had it's mobo replaced so maybe...
1Gb? Mmmm....
Treo 700w is nice but it was the 990i I meant to say (I updfated it when I realised what I posted lol)

ZeBoxx said:
I'm not sure why a Linux-preloaded one would be excluded from the get-go because you didn't put it on there yourself.. it certainly should open up tweaking possibilities.
Click to expand...
Click to collapse
"running Linux" != running free software platform.
Compare Motorola A780 and HTC Blueangel/Universal.

well, I did say "should". I didn't say it would come with a CD with all the source code on it ready for compilation
We're getting way, way off-topic anyway. Keyboard/button backlights tweaks are as of yet non-existant. Chances are you can tweak it by modifying the driver - but nobody's confirmed or done so. Worst case scenario is that it's all in hardware. For the specific tweak mentioned - no, because the Wizard doesn't have a light sensor. Arguably you could start up the camera ever once in a while and check lighting that way, but it wouldn't be very accurate

Kaiser Video Drivers - Status of development effort

Can we make this a sticky post where the end status of the Kaiser Video driver development stands?
Where does it stand? Has anyone started work on it? How do we get ahold of the information required for developing the driver? Can we determine if the development for this driver is even possible? (Is the hardware completely set up to handle it? Maybe there are hardware design hurdles which makes it impossible to be done - that HTC knows about but cannot or will not currently tell us? Even if the chipset is up to it, maybe there is some other piece of hardware missing like an additional circuit left out? How can we determine this for sure and get the work on this started?
Let's make this a sticky post and only those with specific information should post here...
What pieces of hardware are required for a developer to work on this driver development issue? I am willing to part with my older units (for a price, I was going to sell them) if that would help the effort: (O2 XDA/O2 XDA II/Cingular 8525) - what specific models support this chipset so we know what hardware can be used for the development effort?

There are three sticky posts on the subject of video drivers already - are these needs not met by the Video driver project thread - http://forum.xda-developers.com/showthread.php?t=355345 ?

But not the current status
But not the current status in one place that is easy to find. Maybe there should be a sticky post with only one postingvand only updated - not added to - from time to time - only by the forum admin...

Developing new drivers from the ground up won't happen anytime soon. It's a massive undertaking and I bet much too much even for the fine people here.
Even "stealing" drivers from similair hardware has proven very difficult, though it's most probably possible.
I think our best chance would be if HTC releases a device with MSM 7200/7500 and they deliver it with drivers, then it would probably be a fairly easy task.
As for the hardware the only two things that come to mind would be if HTC bought cost reduced chipsets with non-functional Imageon hardware (if for an example there's a problem with yields and Qualcomm has a stock of partially broken chipsets) or if Qualcomm has different SKUs of the same chipset which they artificially handicap by disbling certain hardware (and thus ell them cheaper).
None of the two theories above are that far fetched actually.
Hardware manufacturers often artificially create multiple SKUs by disabling features in a high end product. (Perfect sample would be CD/DVD burners that are firmware capped to a lower speed that the hardware can actually manage.)
Sma ething happens with videocards. When Radeon 9500 was launched the chip on those boards were actually 9700 chips but with non-functional hardware units (and when ATi were out of those they actually started capping 9700 chips that were 100 % operational).
As for the exact current status I believe the only person who really gave this a try was Chainfire who tried to make the LG KS20 drivers work on a Kaiser without any luck. SO I guess the status is still att 0 % so to speak.

KruseLudsMobile said:
But not the current status in one place that is easy to find. Maybe there should be a sticky post with only one postingvand only updated - not added to - from time to time - only by the forum admin...
Click to expand...
Click to collapse
yes, thats a good idea.

Really there are way too many threads dealing with these issues. Two or three new ones at least pop up every day. As far as I know, there is currently nobody actually working on the drivers. I was, but after putting about a 100 hours in porting the LG KS20 drivers, ultimately without success, I focussed my efforts towards the website. Porting these drivers is most likely not impossible, but it's not an easy task and I personally only know of one person here on XDA who may possibly pull it off and this person does not have one of the affected devices, and even if she did, it might still take a long time to do.
In the meantime, progress is being made with the website, news coverage everywhere, and a lot going on behind the scenes that we honestly cannot say 'out loud'.
Let's first see what the update HTC keeps telling us about brings. And if you need to get rid of bounty money, I would say giving a fair part of it to those of us who have put all this effort and time into making it happen would not be unfair

Chainfire said:
Really there are way too many threads dealing with these issues. Two or three new ones at least pop up every day. As far as I know, there is currently nobody actually working on the drivers. I was, but after putting about a 100 hours in porting the LG KS20 drivers, ultimately without success, I focussed my efforts towards the website. Porting these drivers is most likely not impossible, but it's not an easy task and I personally only know of one person here on XDA who may possibly pull it off and this person does not have one of the affected devices, and even if she did, it might still take a long time to do.
In the meantime, progress is being made with the website, news coverage everywhere, and a lot going on behind the scenes that we honestly cannot say 'out loud'.
Let's first see what the update HTC keeps telling us about brings. And if you need to get rid of bounty money, I would say giving a fair part of it to those of us who have put all this effort and time into making it happen would not be unfair
Click to expand...
Click to collapse
not enough threads IMO

Guys, I can make this thread sticky too if you promise it'll be a catch-all thread, eferring to all the other, referred threads.

Any Hope of a Workaround for US GSM-based Carriers?

I recently purchased a used droid 4 on ebay. Unfortunately it has been upgraded to the OTA release of ICS 4.04. Anyone working on lifting the simlock associated with the version of the bootlocker included with ICS (I'm assuming the bootloader is the origin of this simlock but technically I could be wrong)? Or is it a lost cause because it is signed? I know it's written to protected ram so any workaround would be nontrivial but does anyone have any possible exploit ideas? Motorola is unlocking a couple other models that they have out. Would petitioning them to include the droid 4 in their list of unlockable devices be a surefire path to getting the simlock lifted? Or should I consider this a lost cause and return my droid 4 to the ebay ether?
If anyone is considering working on this issue I would be more than glad to contribute. While I'm no Android expert I have a decent understanding of the OS and work in command line Linux for a living so I'd be glad to help. The selection of qwerty phones today is beyond attrocious.
One last thought. Is the idea of spoofing the carrier a possibility?
Sent from my SGH-T839 using Tapatalk

Hi blackstar,
So, I recently got a Droid 4 off of CraigsList that I wanted to use on StraightTalk, but found out that what I had perceived (that 2G/Edge was working on GSM North America) was incorrect.
They're not completely sure WHERE it's broken at the moment as far as SIM lock. Some have suggested it might be baked in the ROM -- but more than likely it is built into the modem.
Here have been some stabs at it -- and what to do in regards to getting the modem setup/altered.
http://forum.xda-developers.com/showthread.php?t=1916869
A thought, though -- since we have SafeStrap and Root, doesn't that let us essentially bypass the bootloader in some ways? My understanding is that the bootloader was required to boot the device to a "correct" image and lock the load to Motorola's firmware, but SafeStrap/root gave us access to actually overwrite the RAM/memory and replace the existing kernel with a new one for the chance at custom ROMs. So, I'm not entirely sure it has to do with the bootloader.
To me, it seems like something that's potentially baked into their ROM or in the modem firmware. If it's in the modem firmware, it's a matter of figuring out what keys/values need to be adjusted and then run it. There have been talks about AT&T getting the Photon Q (Asanti) -- rumors that were back around April of this year... but we have yet to see it there and no news about it showing up anytime soon. Not sure if they scrapped the keyboard and then shipped it as a different device.
I would imagine that if we can have the lowest level debug logging enabled and plug in an American SIM, you might be able to figure out what is breaking. Not sure how low logcat can go...
That's my understanding of the current situation, from a programmer's point of view (though I don't code for Android). Spoofing might be interesting -- but if it's locked at the radio firmware, I don't think spoofing can adjust the frequencies. But more power to you if you can figure it out (and force me to find ANOTHER Droid 4, haha).
Good luck! Definitely talk with the OP of the Topic I sent you, since s/he has a pretty deep interest in this as well.
OH, and one more thought -- there was a thought to grab an AT&T version of the Bionic and Verizon version, wherein they had the same radios, but different firmware, and do a diff on them to figure out if some settings had changed, and then potentially patch that into the D4. That might be a good strategy, but that would require us to get dumps from a few different people -- something you might be able to facilitate if you guys all work together.
One final thought -- is there any way we could have a sticky'd topic for people to post their findings, so we don't have to keep scanning and finding this?

Much thanks terinfire.
Let me start off by saying I don't have any definitive information with regards to any of the good questions you posed but if I find out anything I'll be sure to update the thread.
I spent a good chunk of the weekend trying to educate myself on the situation. From what I understand (anyone feel free to correct me or point me to the appropriate thread if I'm completely reinventing the wheel), it seems like it comes down to two most likely scenarios. Either Verizon added an MCC/MCN lock in the baseband when pushing out the OTA ICS release or they placed a restriction in the radio interface layer (RIL) of the ICS ROM. My research hasn't quite enabled me to determine which scenario is more likely. My unscientific intuition (and wishful thinking) is that the restriction is in the ROM somewhere in the RIL (if that makes any sense, still learning the Android OS architecture).
I will post what I've mentioned above in the the forum you mentioned; hopefully I can garner an audience. I will also look into getting a sticky topic created.
Not too sure how to implement any of my intuitions noted above with regards to this problem but I will try and learn as it goes.
One more note - so it is claimed that the Samsung Galaxy III for Verizon can be unlocked to use domestic GSM carriers. I've found no confirmation. (https://plus.google.com/103583939320326217147/posts/b7JbBKjJVSQ)
Pertinent links I came across in my research that may be useful:
MCC/MCN Codes: http://en.wikipedia.org/wiki/Mobile_Network_Code
Radio Interface Layer: http://en.wikipedia.org/wiki/Radio_Interface_Layer, http://www.kandroid.org/online-pdk/guide/telephony.html
RIL Header: https://code.google.com/p/linux-on-android/source/browse/radio/headers/ril.h
Qualcomm MDM660Device Specification: http://www.scribd.com/doc/54154049/...odem-Device-Specification-Advance-Information

[Q] Flashing Canadian 4x (P880g)

I've been going bonkers trying to get my p880 flashed to 20a. I tried the LG-KDZ Hacker method first (many times), then the KDZ_FW_UPD method, which also failed. Finally, I tried using LGFlashTool which also failed, but the failure log gave me a hint as to why:
"Invalid Target P880 <> P880g"
Has anyone successfully flashed a Canadian 4x with a non-Canadian firmware?
Can anyone think of a way to do so? Or is there a reason I shouldn't?

Mods? Just delete thread.
Nevermind; I've done a more indepth search and come across all the previous unanswered threads. Mods--you may as well just delete this thread.

Yeah, good luck finding any info on the P880g. No one at XDA is working on it, so the best we can do is pray that LG releases something official for it.

jphillip said:
Yeah, good luck finding any info on the P880g. No one at XDA is working on it, so the best we can do is pray that LG releases something official for it.
Click to expand...
Click to collapse
I asked on their Facebook page and they replied "At this time there is no scheduled upgrades for the Optimus 4X within Canada."
I was a bit surprised at the hostility towards the P880g posts I found. It's not like our variant has its own forum. It's also not like variations in devices are uncommon. Back when I had a G1 (HTC Dream), the Canadian version ran different S/W but could run USA roms without issue--providing your radio and bootloader matched. But that was just a S/W issue. We *may* have different hardware. However, given how small the Canadian market is and that the P880g has only been released here (as opposed to the dozens of countries the P880 is available in), I'd be surprised if our *hardware* was actually different. I haven't been able to track down what chip the P880 uses, so I don't know if it's capable of 1700. If it is, we might be alright running p880 roms. If it isn't, then we'd need some real dev work.
The real issues right now are the locked bootloader and the model check. That's what's preventing us from seeing if a P880 rom would run. I'm no dev but if I can figure out how it does the model check then I'll try and flash v20a and see if I lose connectivity.

Now that makes me curious... check this comparison: http://pdadb.net/index.php?m=pdacomparer&id1=3314&id2=3972
The only difference between the two is Band 4 on the P880g, and Band 9 on the P880... plus Android 4.0.4 vs. 4.0.3 (a minor software update). The listed chips are the same. So what is it in the hardware that makes a difference for frequencies? Is it even hardware, or simply a ROM limitation? Do they have physically different antennas?
Perhaps it is simply a matter of flipping a couple bits in a P880 ROM to enable Band 4, and disable Band 9 and the model check. I wish I had a shred of the technical knowledge necessary to experiment with this stuff.

jphillip said:
Now that makes me curious... check this comparison: http://pdadb.net/index.php?m=pdacomparer&id1=3314&id2=3972
The only difference between the two is Band 4 on the P880g, and Band 9 on the P880... plus Android 4.0.4 vs. 4.0.3 (a minor software update). The listed chips are the same. So what is it in the hardware that makes a difference for frequencies? Is it even hardware, or simply a ROM limitation? Do they have physically different antennas?
Perhaps it is simply a matter of flipping a couple bits in a P880 ROM to enable Band 4, and disable Band 9 and the model check. I wish I had a shred of the technical knowledge necessary to experiment with this stuff.
Click to expand...
Click to collapse
The 'chip' in question is the radio/wireless chip, rather than the cpu/gpu. It's not typically listed on spec sheets, and is the sort of thing you need to do a teardown to find out. For example, if you check out this teardown: http://www.ifixit.com/Teardown/Nexus+One+Teardown/1654/2 , the Qualcomm RTR6285 is the Nexus One's radio chip. Sometimes radio chips will support more frequencies than they use. If the P880 and P880g have the same chip, then accessing frequencies is a software matter and easier for a dev to deal with.
I'm no dev either, but hey, devs are made, not born. I like my P880g as is, but I'd really love to be able to customize it more and or update it as time goes by and 4.0.4 begins to seem a bit long in the tooth.

nemesishaven said:
I asked on their Facebook page and they replied "At this time there is no scheduled upgrades for the Optimus 4X within Canada."
Click to expand...
Click to collapse
I ve checked also with videotron, no scheduled update for their LG 4X firmware

Regarding Z2 (standard), CustomROMs and frequencies

Hi,
since the sourcecode of the Z2 as well as the Pro-version have been released and Custom-ROMs are rolling in, what do you think are the chances of the standard-version getting attention by devs?
This forum seems to mostly focus on the Z2 Pro, not the standard.
The reason for me asking is that the Z2 Pro and Standard both have the Snapdragon 820 built in. Meaning both are capable of supporting the same range of frequencies. The Standard comes with a lot less frequencies (likely due to licensing).
As seen on this forum (http://forum.xda-developers.com/galaxy-s5/general/how-to-add-rf-lte-frequency-bands-to-t2886059), it should be possible to unlock the frequencies the Standard is "missing" when using CM, Remix etc. The result would be a phone with the best bang for the buck but also e.g. LTE/4G-Support for frequencies required in Europe (band 20 in Germany is pretty much mandatory...)
Cheers in advance for any answers

Iam interested too in unlocking band 20

Messing around with the actual radio of an Android phone is pretty tricky stuff, since the radio is a part of the phone that comes with it's own firmware. From what I understand this part is pretty much like an closed box with which the operating system communicates. So addings things that aren' t supposed to be there is both tricky and potentially dangerous.

BTW lover said:
Messing around with the actual radio of an Android phone is pretty tricky stuff, since the radio is a part of the phone that comes with it's own firmware. From what I understand this part is pretty much like an closed box with which the operating system communicates. So addings things that aren' t supposed to be there is both tricky and potentially dangerous.
Click to expand...
Click to collapse
Yeti, the CPU Supports a couple of frequencies that obviously were left out - most likely due to licensing. I can't realen think of anything that bad that could happen...