Hi everyone!
I'm trying to compile a cm-kernel just to match the cpu voltages to my phone (I want to get the lowest stable setting that fits me). I'm wondering: is it normal that every version of cm-kenel out there gives a different error from each other and does not compile? I'm not a linux compile expert, but sometimes it's a printf typo, sometimes it's something bigger.. but I cannot have it compiled. I tried following Cyanogen's wiki and it didn't work with their GIT repository, tried cm-kernel-experimental and now it's sayng:
{
"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"
}
I'm running a fresh Ubuntu 10.4 x86 Virtual Machine. If someone with enough heart is willing to help me I'd be really happy about it
By the way maybe I should grab a snapshot of the code that is known to be 100% complete, like when CM released the final code for the latest CM 6.0.0 .
PS: what bugs me is that psdev.c was edited in Oct 5th 2009 and coda.h in Jul 25th 2008 ... why on hell would it not compile? Using arm-eabi 4.2.1 and 4.3.1 I get here, with 4.4.0 (which I saw is commonly used) I get:
edited in the 3rd Dec 2009... even though this looks like a compiler bug.. I'm lost!
Nevermind for the moment, it was due to the config taken from the phone, now I took it from the original boot.img and it looks like it's working.
Related
I'm running CM7 nightly #38, and just noticed that any screenshots I take just turns up as a blank black image. Is it a bug in CM7 or something I've messed up on my device? Is there anyway I can fix it?
I've tried ShootMe and screenshot from the market and used both jpg and png formats.
I was able to make screen shots a few nightlies ago using screenshot, I think, but I forgot which version I was on when I did that.
Thanks in advance.
It's a known CM7 issue. Not a high priority at the moment.
Thanks, good to know it's not because I screwed something up
I agree that this isn't a high priority issue at all.
They figured out the problem and there is a fix in the CM7 Dev thread, but it's not really intended for end-users. I'd expect Dalingrin's next kernel release to include the fix.
Proof:
{
"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"
}
911jason said:
They figured out the problem and there is a fix in the CM7 Dev thread, but it's not really intended for end-users. I'd expect Dalingrin's next kernel release to include the fix.
Click to expand...
Click to collapse
Can't wait, thanks for the heads up
Please try this one with other devices than Blackstone.
Detailed information about this in my Blackstone thread.
ThaiDai Android Loader is a program for Windows Mobile.
With it you can start Android or you can install Android without doing the usual things: no copy, no edit, no changes etc.
The setup (a normal cab-file) prepares the necessary files on your sd card automatically.
With the program you select what you want to do (install, backup, restore, change device, choose Android Build etc.) and press "Boot". That's it.
Program is installed in autostart folder and will automatically boot into last chosen OS after a number of seconds (default 100 s, you can change of course). Stopping countdown is easy: klick somewhere or change a value).
I included Neopeeks NeoFROYO build as default. Until now (my opionion) best combination of performance and stability. More possible and will provide download links later.
{
"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"
}
when?
avon76 said:
when?
Click to expand...
Click to collapse
In Blackstone thread since yesterday...
first, i would like to thank to you for the development.. lot of thank..
but i have a little problem with the hosting. since iam not allowed to post at the dev section. so i make this thread. i won't ask you something new. but, like i said, i have the problem with the hosting. because almost all the Roms i've downloaded are corrupted. i use IDM, so it's all downloaded completely but they are broke. yea i know i can fix it with winrar. but, it doesn't work either. it fix a lot, but says all of boot.img in almost all the roms i've downloaded was broke (before fixing it, there are more than 90 erors. just the remaining one after fix it). so i just ask anyone who have a boot.img file to provide it for me .
since i'm not willing to use it for any kind of "special purpose". i think it wouldn't violated maclaw's rules.
i have downloaded 5 roms, and only one that working. it was the AOKP kitkat. but when i was trying to flash the Gapps, it wouldn't boot properly. it won't boot at all..
here is the sample proof :
{
"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"
}
after i try to fix it, just remain one :
i need boot.img for these ROMs :
cm10.2_golden.maclaw.20140108
aokp4.3_golden.maclaw.20140110
slim4.3_golden.maclaw.20140112
cm11.0_golden.maclaw.20140111
Hi guys,
I can not install the sdk for windows phone because I get this error. Do you know how to solve it?
{
"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"
}
Thanks
it is worth reading the error messages.
Eh, I wouldn't know what that error meant, and I probably know more about "trust providers" and such than most people here. See if you can find anything about the error by searching online. Also make sure you're fully up to date; it's possible some of your certificates from Microsoft are outdated and that's causing the problem.
The windows phone 8.1 SDK does not work with team foundation server 2013. It is written in the docs and the errors point out to that.
There is also a corrupt ISO with damaged MSI and CAB files floating around on the web which will give you those errors,
So you can also try downloading an other iso that will install without any problems at all
Hey,
you just need to install VS Express 2013 for Windows first. If it still didn't works, download the ISO from the WPCentral forum (mediafire link), it worked for me (i can't post links because i'm new )
Currently, I have a production app, which is using SDK 21.
Since it requires a huge engineering work, to port the app to SDK 23, we make another unstable Alpha release, by using SDK 23
Today, I need to make a critical bug fix release, for our production app.
However, since we have an Alpha app with SDK 23, it prevents us from publishing the new production app, which is using SDK 21.
I try to de-activate Alpha testing, but it just won't help. Please see my screenshot.
Anything I do, so that I can publish my critical bug fixed production app, with SDK 21?
Note, upgrade production app to SDK 23 immediately is not an option, as we realize that requires a huge engineering effort (New permission model, most of our custom made UIs break under SDK 23, ...). That's why we spawn another alpha app.
Thanks.
{
"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"
}