Screen delay issue (kernel issue found) - HD2 Android NAND Development

Screen delay issue (kernel issue found) - HD2 Android NAND Development

Basically, as we all know there is a delay when turning on the screen. I have been looking through various kernel files and trying to find the source of the problem. and I believe that I have found part of the problem!
The first errors that I found happened each time the screen was turned on, in the log it showed....
[ERROR] msm_i2c msm_i2c.0: error, status 63c8 (5C)
[ERROR] msm_i2c msm_i2c.0: Error during data xfer (-5) (5C)
[ERROR] msm_i2c msm_i2c.0: error, status e3c8 (34)
[ERROR] msm_i2c msm_i2c.0: Error during data xfer (-5) (34)
This lead me to believe that it was an issue with the msm files in the kernel...
I then found two of the errors in a file I found on the HD2 Kernel GitHub... the link to the file is also below....
https://github.com/charansingh/cm-kernel/blob/master/drivers/i2c/busses/i2c-msm.c
Code:
if (ret < 0) {
dev_err(dev->dev, "Error during data xfer (%d) @%02X\n", ret, msgs->addr);
msm_i2c_recover_bus_busy(dev);
}
Now I have started C robotics programming quite recently so I was hoping that it would help me here! This loop obviously checks if the variable ret is < 0 and if it is it will display an error message! Now earlier in the code ret was set using
ret = msm_i2c_poll_notbusy(dev, 1);
This led me onto the function
msm_i2c_poll_notbusy....
Code:
msm_i2c_poll_notbusy(struct msm_i2c_dev *dev, int warn)
{
uint32_t retries = 0;
while (retries != 200) {
uint32_t status = readl(dev->base + I2C_STATUS);
if (!(status & I2C_STATUS_BUS_ACTIVE)) {
if (retries && warn)
dev_warn(dev->dev,
"Warning bus was busy (%d)\n", retries);
return 0;
}
if (retries++ > 100)
usleep_range(100, 200);
}
dev_err(dev->dev, "Error waiting for notbusy (%d)\n", warn);
return -ETIMEDOUT;
}
As far as I can see, with no kernel programming history in my life, it sets the unsigned integer retries to 0, then starts a while loop testing
readl(dev->base + I2C_STATUS)& I2C_STATUS_BUS_ACTIVE
If the result of this is false it will return that the bus was busy for so many tries, it then exits out of the while loop returning control to the rest of the function...
otherwise ( in our case ) it will increase the variable retries by one and if there have been more than 100 retries it will have a 10 millisecond delay before returning control back to the top of the while loop. After 200 retries the while loop is no longer valid and then it will exit...
The cause for the around 2 second delay is partially due to the phone waiting until this loop has finished before it has turned the screen fully on! the 100 tries of the 10 millisecond delay equates for 1 second of the delay, so if we could fix the loop problem this WILL increase the speed at which the screen turns on... the other error is caused by
Code:
if (status & I2C_STATUS_ERROR_MASK)
goto out_err;
out_err:
dev_err(dev->dev, "error, status %x (%02X)\n", status, dev->msg->addr);
dev->ret = -EIO;
I do not believe that this error is causing a slowdown but they are related.
The problem always involves the variable status so this probably gives a good idea that whatever sets status must be incorrect...
Anyhow I have never touched kernel scripting in my life, I am 15, so I may be completely wrong, but from what I can see I hope that I am at least partially right!

Wow! Good stuff!

Wow nice find, perhaps you should talk to Tytung & Rafpigna about this as they are the most active kernel chefs @ HD2

patensas said:
Wow nice find, perhaps you should talk to Tytung & Rafpigna about this as they are the most active kernel chefs @ HD2
Click to expand...
Click to collapse
Thanks, I have now contacted them and am awaiting a reply

Kernel source code related to msm_i2c is done by the great dev Cotulla. (and maybe other devs)
I don't participate in his work.
And you're linking to a non-working kernel git in your first post.

but tytung please try to look into this ?
because this issue is really annoying and I dont think cotulla would mind if you do some modifications to his great work ?

Nice! now the only thing left to do is to fix it =))

Farrrk now what....??
-Wrong thread... sorry.

Well, I'm waiting for screen delay issue to be fixed since I installed MAGLDR on my HD2. So it will be just great.
What if just remove this loop and sleeps and recompile kernel? Madness? THIS! IS! SPARTA!

Great found kid!! We have great hope on this!
Hope it gets fixed soon...

I didn't understand anything you just said but .... This is great! And your only 15? That's amazing.
Hope we can fix this problem.
Sent from my HTC HD2 using XDA Premium App

nice work. especially if you are 15.
i would be so happy without the wakeup lag.. >.<

Hah ! That reminds me of an old trick to enable hackintoshes to use USB2...
The PC bios never gave back the bus ownership. So correctly programmed software could not use it.
The fix was to take bus ownership without asking "please".
Here it might be the same idea: just ignore (or need to call msm_i2c_recover_bus_busy earlier)
Once back home, if my kids give me spare time, I'll try to setup a compilation environment and give it a try.

john_duff said:
Hah ! That reminds me of an old trick to enable hackintoshes to use USB2...
The PC bios never gave back the bus ownership. So correctly programmed software could not use it.
The fix was to take bus ownership without asking "please".
Here it might be the same idea: just ignore (or need to call msm_i2c_recover_bus_busy earlier)
Once back home, if my kids give me spare time, I'll try to setup a compilation environment and give it a try.
Click to expand...
Click to collapse
Good idea, im sure that calling it earler and avoiding the loop will reduce the delay, after that is done we need to find a 'clean' hack as calling msm_i2c_recover_bus_busy would probably still add a delay, albeit not as much as if we just left it Good luck in your testing...

You guys speak like you've found the solution lol =D

Well not tonight... bad news came, I have to fix the dishwasher first.
I'll keep you informed.

john_duff said:
Well not tonight... bad news came, I have to fix the dishwasher first.
I'll keep you informed.
Click to expand...
Click to collapse
Hey can the dishwasher remove the screen delay? NO!
only joking ! Im just so excited for this !

white-energy said:
You guys speak like you've found the solution lol =D
Click to expand...
Click to collapse
ahah finding a problem isnt that hard but finding the solution is harder we will probably need some help from experienced kernel coders to help fix it properly

speedyracer5 said:
ahah finding a problem isnt that hard but finding the solution is harder we will probably need some help from experienced kernel coders to help fix it properly
Click to expand...
Click to collapse
Why are you using charansingh's HD2 Kernel GitHub to see the code? Just guessing, it may have .37 kernel code on which work is still going on as its still buggy...
Is there a similar error tytung or Rafpigna or ACA's kernel's git also?

speedyracer5 said:
[ERROR] msm_i2c msm_i2c.0: error, status 63c8 (5C)
[ERROR] msm_i2c msm_i2c.0: Error during data xfer (-5) (5C)
[ERROR] msm_i2c msm_i2c.0: error, status e3c8 (34)
[ERROR] msm_i2c msm_i2c.0: Error during data xfer (-5) (34)
Click to expand...
Click to collapse
Well, I can't argue with that.... I can't understand it either ..
Sounds like you did A tremendous piece of detective work. Nice one.

Related

[Q][SOLVED] PhotoChooserTask Mango Exception

A simple photochooser task application throws a Nullrefference exception(Invalid pointer) and pixel height and width is 0 on mango, on nodo it worked alright.
Am I missing a cast? or this is a bug in mango, and will be fixed?
Here's the code:
Code:
private PhotoChooserTask photo;
// Constructor
public MainPage()
{
InitializeComponent();
photo = new PhotoChooserTask();
photo.Completed += new EventHandler<PhotoResult>(photo_Completed);
}
void photo_Completed(object sender, PhotoResult e)
{
if (e.TaskResult == TaskResult.OK)
{
BitmapImage bi = new BitmapImage();
bi.SetSource(e.ChosenPhoto);
//////////////////////////////////////////////////////////////////////////////////////
var wb = new WriteableBitmap(bi);//Exception here
/////////////////////////////////////////////////////////////////////////////////////
// bi.PixelHeight and bi.PixelWidth == 0;
}
}
private void button1_Click(object sender, RoutedEventArgs e)
{
photo.Show();
}
}
Hope someone can help.
Thanks in advance

This is because you need to set the CreateOptions property of the BitmapImage before you use it to construct the WriteableBitmap.
The default 'create' option on WP7 is DelayCreation (it may be BackgroundCreation in some of the 7.1 betas, but the mango RTM I think is DelayCreation) but either way the problem you're having is that your image has not been initialised yet at the point you use it in the WriteableBitmap's constructor (hence the null reference exception).
The options (depending what you set) let images be only initialised when needed, and downloaded on separate threads / asynchronously, which can help performance (or at least stop the phone blocking other things happening whilst images are loaded). Users also have the ability with the photo chooser to pick images from online ablums, so as you can imagine you also have to handle perhaps a second or two waiting for a download to complete, and of course downloads can also fail when connections drop etc. which you can handle too.
So in answer to your question (off the top of my head, not confirmed it with code) set the createoptions to none, and use the Bitmap's ImageOpened event to construct the WritableBitmap (you may also want to handle the Bitmap's ImageFailed event). Make sure you set up the ImageOpened event before you set the source, i.e.
BitmapImage bi = new BitmapImage();
bi.CreateOptions = BitmapCreateOptions.None;
bi.ImageOpened += new (some event name)
bi.ImageFailed += new (some event name)
bi.SetSource(e.ChosenPhoto);
Hope that helps,
Ian

Thank you very much
Problem solved

otherworld said:
This is because you need to set the CreateOptions property of the BitmapImage before you use it to construct the WriteableBitmap.
The default 'create' option on WP7 is DelayCreation (it may be BackgroundCreation in some of the 7.1 betas, but the mango RTM I think is DelayCreation) but either way the problem you're having is that your image has not been initialised yet at the point you use it in the WriteableBitmap's constructor (hence the null reference exception).
The options (depending what you set) let images be only initialised when needed, and downloaded on separate threads / asynchronously, which can help performance (or at least stop the phone blocking other things happening whilst images are loaded). Users also have the ability with the photo chooser to pick images from online ablums, so as you can imagine you also have to handle perhaps a second or two waiting for a download to complete, and of course downloads can also fail when connections drop etc. which you can handle too.
So in answer to your question (off the top of my head, not confirmed it with code) set the createoptions to none, and use the Bitmap's ImageOpened event to construct the WritableBitmap (you may also want to handle the Bitmap's ImageFailed event). Make sure you set up the ImageOpened event before you set the source, i.e.
BitmapImage bi = new BitmapImage();
bi.CreateOptions = BitmapCreateOptions.None;
bi.ImageOpened += new (some event name)
bi.ImageFailed += new (some event name)
bi.SetSource(e.ChosenPhoto);
Hope that helps,
Ian
Click to expand...
Click to collapse
Hello, I have the same problem (NullReferenceException) and have read you response, which from what I see it is the solution, but I have a problem; not where I have to go to do I change them that you propose. I would be so kind of explaining to me that I have to continue steps. It English me is very bad and I am using a translator.
I have HTC Trophy the v.th 7740.16 with chevrom and U2M7740 of Ansar.
Thank you in advance and greetings.

Hi,
If you upload your code / project I will take a look and see where the error is.
Si me muestras su código / proyecto, puedo ver por qué recibiras una excepción NullReference
Ian

otherworld said:
Hi,
If you upload your code / project I will take a look and see where the error is.
Si me muestras su código / proyecto, puedo ver por qué recibiras una excepción NullReference
Ian
Click to expand...
Click to collapse
Hello,
The question is that it is not any project, applications do not develop (although I would like). This type of errorr (nullreferenceexception) happens to me since I updated to Mango, so much in v.7720.68 as in v.7740.16 and happens in apps as Morfo, Fantasy Painter, and at the time of choosing fund in Touchxperience. Not if these apps are not conditioned to Mango or if, perhaps, from the record it might change some type of configuration or entering the Xaml of the app to be able to change some fact, end not...
For the little that, an error of the photochooser seems to be, the question is if it is possible to gain access to him and as doing it.
Anyhow thank you very much and a cordial greeting.

Hi,
If it is not a code issue then I do not know what it could be. Are you using a custom rom?
Good luck with it.
Ian

otherworld said:
Hi,
If it is not a code issue then I do not know what it could be. Are you using a custom rom?
Good luck with it.
Ian
Click to expand...
Click to collapse
Hello. Not, I am with official Mango the v.th 7740.16. I have already restored to factory and it continues the error. I believe that it is a question of the update, it must have a mistake in the pitcher of photos or some error with the librerie, do not know...
Thank you anyhow and greetings.

Hello, otherworld.
I continue with the same problem, 'nullreferenceexception' related with 'chooserphoto' in some application. The curious thing is that someone of them me work correctly, I gain access to me librery and it takes the photos, and in others not, as for example Morfo. I do not know if the problem is in the code source of these applications or phone is in me. Is this the code source of Morfo, is it possible to correct so that this does not happen?
Thank you in advance and greetings.

Create your own I9000/S8500 (& all S5PC110 based devices) bootloader&ultimate unbrick

Create your own I9000/S8500 (& all S5PC110 based devices) bootloader&ultimate unbrick
Preamble
I present you the results of hours of many people research.
Special thanks to:
AdamOutler
mijoma
TheBeano
midas5
Leave me a message if I forgot to mention someone.
I, nor anybody except you take no responsibility for the things you do to your PC, phone, family, neighbours, dog, cat or fish in the result of reading this and/or using any materials linked and included from here.
What is it?
Info how to bypass secure booting mechanism built in S5PC110 CPU's iROM on lowest level and create code loadable even with totally damaged bootloader, without use of JTAG.
Okay, how useful is it?
I've got no clue, it all depends on you.
{
"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"
}
Our main target, which is almost done, is ability to revive any hard-bricked hardware built on S5PC110 without use of JTAG (for eg. when JTAG pads had been damaged)
Some additional info and history
S5PC110 - the powerful CPU, heart and brain of many great handsets (like Samsung I9000, S8500, S8530, SGH-897, Google Nexus S, Odroid T, while last one is hard to be called HANDset, nvm) has got few booting levels before loading operating system:
-BL0/iROM, non-writable (not-brickable), written during CPU production process, execution starts here on every machine start, executed straight in iROM, using iRAM(iRAM is 96KB big, there is a spelling error in CPU manual), it does select booting source depending on xOM CPU pins (different types of flash memory/UART/USB), loads BL1 from it and validate its integrity using electronic sign attached to BL1 (iROM doesn't check BL1 integrity if CPU's SECKEY registers are null, there was some misunderstanding of these, but as far it appear that most or all S5PC110 units has got SECKEY not-null, and its always equal in Samsung's phones)
Execution begins from 0xD0000000
-BL1/IBL, writable (brickable), executed in iRAM, it does memory controllers setup, loads BL2 and, depending from info in BL1 electronic sign, it does or does not check BL2 integrity, BL1 is usually splitted to 2 stages, separated in iRAM by few KB of 0x00
Entrypoint of stage 1 = 0xD0020010 (while it should be loaded under 0xD0020000, as it does have 16 bytes of header)
Entrypoint of stage 2 during normal oneNAND boot = 0xD0020800 (this is already platform-dependant but doesn't seems to vary between mainboards)
Entrypoint of stage 2 during external usb/uart boot = 0xD0022010 (here we insert our custom code, sticked to the end of stage1, it must have dummy header)
-BL2/PBL, writable (brickable), executed in RAM (external DRAM or SRAM), it isn't in fact unneeded, God one knows why Samsung's developers decided to add one additional stage
Entrypoint = platform&version-dependant, it's usually 0x40204000 on I9000
-BL3/SBL, writable (brickable), executed in RAM, it does platform init, support LCD output, download mode and usually few additional functions, it does load OS image into RAM, prepare hardware to execute it and jumps into OS entrypoint
Entrypoint = platform&version-dependant, it's usually 0x40244000 on I9000
for more info about booting sequence and OM pins please reffer to section 02, chapter 6 of S5PC110_EVT1_UM.pdf in [6]
//editnote: This is my own interpretation of bootloaders levels splitting, it haven't been clearly stated in CPU user manual, but it can be also said that IBL is in one part, and PBL is splitted into 2 stages, one executed in iRAM and second executed in DRAM, that's the matter of thinking. Odroid developers seems to use terminology of the second possiblity.
//editnote2: Confirmed from SGS/Captivate boot.bin reversing - Samsung is dividing and calling bootloaders as I wrote in previous points (2nd stage of IBL, which could be aswell 1st stage of 2-stage PBL does contain "IBL" string) Uboot devs got different calling convention. Well... who cares.
After many (even more than many) research [1] we found out that there is no ther way to change iROM primarey booting source than changing OM pins setup, which are hardware soldered through pullup and pulldown resistors to give 5b'001001 (0x9) which means that primary booting source is OnenandMux(Audi) using X-TAL(USB) oscillator (to be honest I still don't hell get what does it means )
AdamOutler sacrificed Captivate mainboard to locate the pullup and pulldown resistors [2], and in result he modified board to have xOM5=1 instead of 0 which enables UART/USB as primary booting source. This booting method is normally tried only when IBL on oneNAND has been damaged, usually bricked is PBL or SBL, and iROM successfully completes its task, but phone hangs somewhere in the middle.
This enabled Adam to load various data through iROM download mode straight into iRAM. And here comes disappointment - all data we tried to load were validated by iROM code against SECKEY and rejected with "Secure Fail Error", BL1 code loaded by iROM must contain 512 bytes of e-sign, consist of 2 public rsa keys and few sha-1 hashes.
Here comes again days and night of deep code analyze, we found BL1_stage1 in Odroid T U-Boot [4] sourcecode signed by Samsung with stage2 security turned off.
That means any BL1_stage2 can be created and joined to BL1_stage1 in proper way, it will pass all integrity tests and be executed - bingo!
Base code
I've created kind of S5PC110 IBL dev kit. It's attached to the post. All you need to build it is FASMARM (downloadable from [5], its really everything except package in attachement) and you can compile any code basing on s5pc110_example.
There you will find Hello World but it does NOT produce this output to screen nor widely used UART hidden in Micro-Usb slot. It does produce output to UART2 channel, which is hidden in JTAG pads in SGS/Captivate mainboard and it has got special pads under battery in S8500/S8530. BUT if you really are determined to run it, by doing OM pulldown->pullup MOD, and feel like you must immediately see it working, it's about 20lines of ASM code which will blink SGS keypad LED and about 10, by calling iROM functions to get other UART port working.
If you want some reference, follow [3] and [7] (also in previous revisions), there you can find alot of FASMARM code written for S5PC110 (S8500/S8530 to be precise).
How to run it?
Here goes the problem, it is unable to run if you have no IBL brick or no OM5 modification (again, reffer to [2]), there you will also find more instructions. It is also able to run by JTAG. Theoretically produced code should be possible to flash and then run as normal IBL, but that's not really good thing to try without JTAG/OM5 mod to resurrect it.
Postamble
If you want to write something bigger, I'd recommend switching from FASMARM to Codesourcery ARM Crosscompiling environment - everything for S5PC110 is already in Odroid's U-Boot and many Android kernel sources (I9000 for example), ready to compile under Codesourcery. I used FASMARM because it's tiny and simple to create small ASM codes, but doesn't support many functions which are speeding up creating larger code.
We will soon release ultimate unbricking method for SGS/Captivate/Wave without use of JTAG, altough this will require high soldering skills or maybe steady hand, while that second is untested and may burn out something onboard, I'm about to test it in few days on my bricked S8530.
Further reading
[1] Where it all has began - Lets save some bricks
[2] First practical results - The Captivate Development Platform
[3] First S8500/S8530 BL3 hacking - FOTA development thread
[4] What has been used here, and what can be easily ported to any S5PC110 device - Odroid's U-Boot
[5] FASMARM homepage
[6] Samsung Galaxy S (and many similiar devices) Hack Pack by Adam Outler
[7] Badadroid FOTA source tree
[8] Walking in Memphis
Note: I wasn't sure which board should I choose to post it. If any mod/admin find better place for this thread (please note it doesn't reffer to SGS or Captivate only, that's the problem) please move it.
Note2: Post above may change if I decide to better explain something.
Note3: Please post any questions and mistakes you found. I'll be happy to answer it if it helps anybody.

Good job. A flow chart made with OpenOffice.org or something to understand the booting process would make things even clearer.
Does your comment about O-Droid's U-Boot mean even non-Samsung devices that utilize this chip verify the digital signature of BL1/the first stage bootloader?

Master Melab said:
Good job. A flow chart made with OpenOffice.org or something to understand the booting process would make things even clearer.
Does your comment about O-Droid's U-Boot mean even non-Samsung devices that utilize this chip verify the digital signature of BL1/the first stage bootloader?
Click to expand...
Click to collapse
Will think about chart later. Thanks for suggestion.
Also, sorry for leading you into mistake before. Even Odroids does verify BL1 signature, and they verify it against the same SECKEY as SGS, Wave and so on does (BL1 from one fits to all above), also all S5PC110 looks to be EVT1_SEC versions, but Secure Boot Context is usually dropped at IBL level and it does continue non-secure boot.

I am not exactly sure what you mean when you say "Secure Boot Context is usually dropped at IBL level and it does continue non-secure boot.". Does that mean after attempting to boot from oneNAND, UART/USB, and the SD card, it try to boot from oneNAND again without checking the digital signature?

No, I mean that iROM (BL0) requires IBL (BL1) to be signed (most likely always), that allows secure boot without unauthorized boot change possibility. But to make boot fully secure, BL1 should require signed BL2, BL2 should require signed BL3 and BL3 should require signed OS image. In case of most (or even all) SGS handsets, BL1 or BL2 doesn't follow secure booting process and doesn't require signed next level of bootloader.

Great work! Maybe you can add links to compilers and some instructions on how to compile?

AdamOutler said:
Great work! Maybe you can add links to compilers and some instructions on how to compile?
Click to expand...
Click to collapse
Rebellos said:
I've created kind of S5PC110 IBL dev kit. It's attached to the post. All you need is FASMARM (downloaded from [5]) and you can compile any code basing on s5pc110_example.
Click to expand...
Click to collapse
There is nothing more simple - open .ASM file using FASMWARM editor and hit F9 or choose Compile from menu.

Rebellos said:
No, I mean that iROM (BL0) requires IBL (BL1) to be signed (most likely always), that allows secure boot without unauthorized boot change possibility. But to make boot fully secure, BL1 should require signed BL2, BL2 should require signed BL3 and BL3 should require signed OS image. In case of most (or even all) SGS handsets, BL1 or BL2 doesn't follow secure booting process and doesn't require signed next level of bootloader.
Click to expand...
Click to collapse
Ahh. I was thinking of an older thread in which someone stated something about it trying to boot from oneNAND a second time without signature checks, if it and booting from USB and the SD card failed. I hate signature checks.

Master Melab said:
Ahh. I was thinking of an older thread in which someone stated something about it trying to boot from oneNAND a second time without signature checks, if it and booting from USB and the SD card failed. I hate signature checks.
Click to expand...
Click to collapse
It was me. Thats the separate thing. However it was only assumption that second boot is without security check, now I'm nearly sure every booting try is signature checked if SECKEY is not null.
Sorry for misleading again.

Its okay. Maybe we can order S5PC110's from Samsung. If anyone has the soldering skills.

This hardware/software mod should apply to more then just the following devices:
Apple iPhone4, Samsung I9000, S8500, S8530, SGH-897, SGH-i896, SGH-i997, T959, SGH-T849, GT-P1000, GT-i9010, GT-i8350, GT-I917, Google Nexus S, Odroid T, and a few Samsung WP7s..
There's so many it's hard to identify them all.

Master Melab said:
Its okay. Maybe we can order S5PC110's from Samsung. If anyone has the soldering skills.
Click to expand...
Click to collapse
Odroid's team is probably one of few Samsung's customers who buys S5PC110, but I guess they won't sell them in less amount than ~1000.
AdamOutler said:
This hardware/software mod should apply to more then just the following devices:
Apple iPhone4, Samsung I9000, S8500, S8530, SGH-897, SGH-i896, SGH-i997, T959, SGH-T849, GT-P1000, GT-i9010, GT-i8350, GT-I917, Google Nexus S, Odroid T, and a few Samsung WP7s..
There's so many it's hard to identify them all.
Click to expand...
Click to collapse
Odroid T has got jumpers to setup OM pins. ;P

AdamOutler said:
This hardware/software mod should apply to more then just the following devices:
Apple iPhone4, Samsung I9000, S8500, S8530, SGH-897, SGH-i896, SGH-i997, T959, SGH-T849, GT-P1000, GT-i9010, GT-i8350, GT-I917, Google Nexus S, Odroid T, and a few Samsung WP7s..
There's so many it's hard to identify them all.
Click to expand...
Click to collapse
I don't think applies to the iPhone 4. Keep in mind that Apple had a major hand in designing the A4 processor and they like to do things their way.

Master Melab said:
I don't think applies to the iPhone 4. Keep in mind that Apple had a major hand in designing the A4 processor and they like to do things their way.
Click to expand...
Click to collapse
If you look at the a4 processor xrays and board layouts, you will see the same structures. Even the xOM resistors. The board is different, but that's because someone else did the layout. The processor is basically the same and the xOM pins provide debugging capabilities. They are ARM cortex a9 processors otherwise.

Great work so far (especially since you don't have a device), and nice tutorial.
I really hope that this gets a portal spot, and maybe even bigger. This info really needs to get out there and worked on, especially with the possibility of this for so many devices. Good luck to you all.

I think the phone hacking community needs more hardware hacks.

Master Melab said:
I don't think applies to the iPhone 4. Keep in mind that Apple had a major hand in designing the A4 processor and they like to do things their way.
Click to expand...
Click to collapse
A4 processor is slighty modified S5PC110 with different, but in fact similiar model name.
AdamOutler said:
They are ARM cortex a9 processors otherwise.
Click to expand...
Click to collapse
It's Cortex A8*.

I've been following the Captivate UnBrickable Mod thread, this thread, and I'm thoroughly impressed by the work you two (and many others) have done. I've taken an interest in poking around inside my Infuse (see pictures).
My questions are these:
1a. If someone were to successfully create a custom IBL/PBL that boots on the S5PC110, or even go so far as to load U-Boot or similar, would it be possible to flash this modified code onto the oneNAND, overwriting the existing IBL and (if needed) PBL?
1b. Supposedly, the IBL+PBL is "locked" on the Infuse, but gtg465x and I were able to successfully write the IBL+PBL+SBL on my first Infuse, inevitably hard-bricking the device (it's since been warranty replaced, so don't bother asking for my dead/bricked device - sorry!). If I had some way of unbricking my new device conveniently (JTAG for example), I would re-try the method gtg465x used, just to watch UART output and see what was going on behind the dark screen of a bricked Infuse.
1c. Regardless, it seems it would be possible to write anything to any part of the oneNAND if one had the proper tools (JTAG, which I am actually considering purchasing a JTAG device for several reasons!). Correct me if this is not the case.
2a. Has anyone tried intentionally corrupting the IBL? Has anyone tried to reproduce this state to confirm that this enables UART/USB as the primary booting source?
2b. If I had a way to recover my device (JTAG, again), I would like to test this myself.
3a. What cable/device/attachment is needed for the CPU to be able to attempt to boot from UART/USB (given xOM5=1, for example)?
3b. Is this just the standard USB OTG cable, or are you communicating to the device over TTL UART?
3c. What is the CPU physically looking for, exactly, when booting this way?
I suppose my goals are these:
1. I would first like to be able to JTAG my Infuse, as a means to recover from the stupid s*** I would like to do to it.
2. I would like to retry gtg465x's method of writing bootloaders, and confirm that this is possible by using nothing but software on the device itself (i.e. no JTAG), given the device is still operational and rooted.
3. I would like to intentionally corrupt the IBL, theoretically turning the device into a KIT-S5PC110 development board. From here, I could work as a tester on your team, and try loading whatever-code-you-come-up-with on the Infuse and hand you results.
4. Once a working/useful IBL+PBL has been created/ported (such as u-boot), I would like to attempt flashing this onto the oneNAND and be able to boot from this without the need of tethering the device to a PC. Further, this would theoretically allow booting from any device (emmc, for example), which would open the door to many, many possibilities.
5. I'd like to see a Dev take the work from goals #3 & #4 and create a script/package/etc that recreates these two steps. I would be happy to test such a script/package/etc.
6. Once goal #5 is complete, Devs could easily start working on porting alternative operating systems to our devices, without substantial fear of bricking their device (e.g. boot iOS or WP7 from emmc, screw around with that, and then boot back into Android from their NAND when they are done for the day).
Thanks for your time reading through my wall-o-text.

Stupid Request...
Is it possible to access iROM via JTAG?
Please, maybe someone can explain how to do this with RIFF Box...
My device is S8500...
Thanx in advance.
Best Regards

adfree said:
Stupid Request...
Is it possible to access iROM via JTAG?
Please, maybe someone can explain how to do this with RIFF Box...
My device is S8500...
Thanx in advance.
Best Regards
Click to expand...
Click to collapse
I think it's no problem to access iROM via JTAG.
You'll find whole iROM under 0xD0000000 RAM address (don't confuse with oneNAND), it's size is 0x10000 (64KB) (so it's 0xD0000000-0xD000FFFF area)
It is also possible to call iROM functions (code tested by nbates66 confirmed that it's possible to call iROM functions from FOTA, which is BL3 level)
Also you will find iRAM under 0xD0020000, its size is 0x15000 (96KB, there is an error in user manual, or I'm too dumb to access the remaining 32KB)
Please post your results somewhere if you decide to test it.
PS: iRAM is probably cleaned somewhere on PBL (BL2) level (couldn't find anything there from FOTA), so if you want to find some interesting info there, try to set JTAG HW breakpoint on 0xD0020010 execution address (entry point of IBL) and then dump iRAM.

Fixing the OMX driver problem on ICS

I have signed the petition to get Qualcom to release ICS drivers for the marvel device, however, it looks as if they will not be releasing them. So we need to come up with another plan. This thread is to try and start a technical discussion as to how we are going to do this.
Using the information in these posts:
http://www.modaco.com/topic/354020-zte-n880e-first-zte-ics-update/page__st__20
http://forum.xda-developers.com/archive/index.php/t-1588599-p-2.html
http://newsandeducationblog.blogspot.com/2012/05/android-developers-video-videoview.html
http://forum.xda-developers.com/archive/index.php/t-1664335.html
These posts suggest that we are missing some features in get_config and get_extension_index.
For get_config the debug output:
W/QCvdec ( 2751): get_config: unknown param 117440527
117440527 is 0x700000F, which from frameworks/base/include/media/stagefright/openmax/OMX_Index.h
/* Image & Video common Configurations */
OMX_IndexCommonStartUnused = 0x07000000,
OMX_IndexParamCommonDeblocking, /**< reference: OMX_PARAM_DEBLOCKINGTYPE */
OMX_IndexParamCommonSensorMode, /**< reference: OMX_PARAM_SENSORMODETYPE */
OMX_IndexParamCommonInterleave, /**< reference: OMX_PARAM_INTERLEAVETYPE */
OMX_IndexConfigCommonColorFormatConversion, /**< reference: OMX_CONFIG_COLORCONVERSIONTYPE */
OMX_IndexConfigCommonScale, /**< reference: OMX_CONFIG_SCALEFACTORTYPE */
OMX_IndexConfigCommonImageFilter, /**< reference: OMX_CONFIG_IMAGEFILTERTYPE */
OMX_IndexConfigCommonColorEnhancement, /**< reference: OMX_CONFIG_COLORENHANCEMENTTYPE */
OMX_IndexConfigCommonColorKey, /**< reference: OMX_CONFIG_COLORKEYTYPE */
OMX_IndexConfigCommonColorBlend, /**< reference: OMX_CONFIG_COLORBLENDTYPE */
OMX_IndexConfigCommonFrameStabilisation,/**< reference: OMX_CONFIG_FRAMESTABTYPE */
OMX_IndexConfigCommonRotate, /**< reference: OMX_CONFIG_ROTATIONTYPE */
OMX_IndexConfigCommonMirror, /**< reference: OMX_CONFIG_MIRRORTYPE */
OMX_IndexConfigCommonOutputPosition, /**< reference: OMX_CONFIG_POINTTYPE */
OMX_IndexConfigCommonInputCrop, /**< reference: OMX_CONFIG_RECTTYPE */
OMX_IndexConfigCommonOutputCrop, /**< reference: OMX_CONFIG_RECTTYPE */
OMX_IndexConfigCommonDigitalZoom, /**< reference: OMX_CONFIG_SCALEFACTORTYPE */
Is OMX_IndexConfigCommonOutputCrop, so the hardware mpeg4 decoder doesn't understand this index. Going from the source code that calls this, if the call fails then it does something else and carries on
./frameworks/base/media/libstagefright/ACodec.cpp:
if (mOMX->getConfig(mNode, OMX_IndexConfigCommonOutputCrop,&rect, sizeof(rect)) != OK) {
rect.nLeft = 0;
rect.nTop = 0;
rect.nWidth = videoDef->nFrameWidth;
rect.nHeight = videoDef->nFrameHeight;
}
CHECK_GE(rect.nLeft, 0);
CHECK_GE(rect.nTop, 0);
CHECK_GE(rect.nWidth, 0u);
CHECK_GE(rect.nHeight, 0u);
CHECK_LE(rect.nLeft + rect.nWidth - 1, videoDef->nFrameWidth);
CHECK_LE(rect.nTop + rect.nHeight - 1, videoDef->nFrameHeight);
./frameworks/base/media/libstagefright/OMXCodec.cpp:
status_t err = mOMX->getConfig(mNode, OMX_IndexConfigCommonOutputCrop,&rect, sizeof(rect));
CODEC_LOGI("video dimensions are %ld x %ld",video_def->nFrameWidth, video_def->nFrameHeight);
if (err == OK) {
#ifdef SAMSUNG_CODEC_SUPPORT
/* Hack GetConfig */
rect.nLeft = 0;
rect.nTop = 0;
rect.nWidth = video_def->nFrameWidth;
rect.nHeight = video_def->nFrameHeight;
#endif
CHECK_GE(rect.nLeft, 0);
CHECK_GE(rect.nTop, 0);
CHECK_GE(rect.nWidth, 0u);
CHECK_GE(rect.nHeight, 0u);
CHECK_LE(rect.nLeft + rect.nWidth - 1, video_def->nFrameWidth);
CHECK_LE(rect.nTop + rect.nHeight - 1, video_def->nFrameHeight);
mOutputFormat->setRect(kKeyCropRect,rect.nLeft,rect.nTop,rect.nLeft + rect.nWidth - 1,rect.nTop + rect.nHeight - 1);
CODEC_LOGI("Crop rect is %ld x %ld @ (%ld, %ld)",rect.nWidth, rect.nHeight, rect.nLeft, rect.nTop);
} else {
mOutputFormat->setRect(kKeyCropRect,0, 0,video_def->nFrameWidth - 1,video_def->nFrameHeight - 1);
}
I think we can safely ignore this failure for now.
get_extension_index might be a little more tricky. The file vendor/qcom/opensource/omx/mm-video/vidc/vdec/src/omx_vdec.cpp is a video decoder and the code for the get_extension_index is:
OMX_ERRORTYPE omx_vdec::get_extension_index(OMX_IN OMX_HANDLETYPE hComp,OMX_IN OMX_STRING paramName,OMX_OUT OMX_INDEXTYPE* indexType)
{
if(m_state == OMX_StateInvalid)
{
DEBUG_PRINT_ERROR("Get Extension Index in Invalid State\n");
return OMX_ErrorInvalidState;
}
else if (!strncmp(paramName, "OMX.QCOM.index.param.video.SyncFrameDecodingMode" ,sizeof("OMX.QCOM.index.param.video.SyncFrameDecod ingMode") - 1)) {
*indexType = (OMX_INDEXTYPE)OMX_QcomIndexParamVideoSyncFrameDec odingMode;
}
#ifdef MAX_RES_1080P
else if (!strncmp(paramName, "OMX.QCOM.index.param.IndexExtraData",sizeof("OMX. QCOM.index.param.IndexExtraData") - 1))
{
*indexType = (OMX_INDEXTYPE)OMX_QcomIndexParamIndexExtraDataTyp e;
}
#endif
#if defined (_ANDROID_HONEYCOMB_) || defined (_ANDROID_ICS_)
else if(!strncmp(paramName,"OMX.google.android.index.enableAndroidNativeBuffers", sizeof("OMX.google.android.index.enableAndroidNati veBuffers") - 1)) {
*indexType = (OMX_INDEXTYPE)OMX_GoogleAndroidIndexEnableAndroid NativeBuffers;
}
else if(!strncmp(paramName,"OMX.google.android.index.useAndroidNativeBuffer2", sizeof("OMX.google.android.index.enableAndroidNati veBuffer2") - 1)) {
*indexType = (OMX_INDEXTYPE)OMX_GoogleAndroidIndexUseAndroidNat iveBuffer2;
}
else if(!strncmp(paramName,"OMX.google.android.index.useAndroidNativeBuffer", sizeof("OMX.google.android.index.enableAndroidNati veBuffer") - 1)) {
DEBUG_PRINT_ERROR("Extension: %s is supported\n", paramName);
*indexType = (OMX_INDEXTYPE)OMX_GoogleAndroidIndexUseAndroidNat iveBuffer;
}
else if(!strncmp(paramName,"OMX.google.android.index.getAndroidNativeBufferUsage", sizeof("OMX.google.android.index.getAndroidNativeB ufferUsage") - 1)) {
*indexType = (OMX_INDEXTYPE)OMX_GoogleAndroidIndexGetAndroidNat iveBufferUsage;
}
#endif
else {
DEBUG_PRINT_ERROR("Extension: %s not implemented\n", paramName);
return OMX_ErrorNotImplemented;
}
return OMX_ErrorNone;
}
In the debug output the message "OMX_GetExtensionIndex failed" comes from frameworks/base/media/libstagefright/omx/OMXNodeInstance.cpp:
status_t OMXNodeInstance::enableGraphicBuffers(OMX_U32 portIndex, OMX_BOOL enable) {
Mutex::Autolock autoLock(mLock);
OMX_INDEXTYPE index;
OMX_ERRORTYPE err = OMX_GetExtensionIndex(mHandle,const_cast<OMX_STRING>("OMX.google.android.index.e nableAndroidNativeBuffers"),&index);
if (err != OMX_ErrorNone) {
LOGE("OMX_GetExtensionIndex failed");
return StatusFromOMXError(err);
}
OMX_VERSIONTYPE ver;
ver.s.nVersionMajor = 1;
ver.s.nVersionMinor = 0;
ver.s.nRevision = 0;
ver.s.nStep = 0;
EnableAndroidNativeBuffersParams params = {
sizeof(EnableAndroidNativeBuffersParams), ver, portIndex, enable,
};
err = OMX_SetParameter(mHandle, index, &params);
if (err != OMX_ErrorNone) {
LOGE("OMX_EnableAndroidNativeBuffers failed with error %d (0x%08x)", err, err);
return UNKNOWN_ERROR;
}
return OK;
}
So the OMX.google.android.index.enableAndroidNativeBuffers extension is the one we are missing, from the code snippet above this, we can see an
#if defined (_ANDROID_HONEYCOMB_) || defined (_ANDROID_ICS_)
#endif
around the check for this extension, so it has been added since Gingerbread, a diff with the cm7 source tells us that the enableGraphicsBuffers has also been added since gingerbread. The header file /frameworks/base/include/media/stagefright/HardwareAPI.h contains the following:
// A pointer to this struct is passed to the OMX_SetParameter when the extension
// index for the 'OMX.google.android.index.enableAndroidNativeBuffers' extension
// is given.
//
// When Android native buffer use is disabled for a port (the default state),
// the OMX node should operate as normal, and expect UseBuffer calls to set its
// buffers. This is the mode that will be used when CPU access to the buffer is
// required.
//
// When Android native buffer use has been enabled for a given port, the video
// color format for the port is to be interpreted as an Android pixel format
// rather than an OMX color format. The node should then expect to receive
// UseAndroidNativeBuffer calls (via OMX_SetParameter) rather than UseBuffer
// calls for that port.
struct EnableAndroidNativeBuffersParams {
OMX_U32 nSize;
OMX_VERSIONTYPE nVersion;
OMX_U32 nPortIndex;
OMX_BOOL enable;
};
I doubt the gb codec that we do have has support for the Android pixel format.
This gives us two options 1) can we change the stagefright sources to support both, i.e. if the extension OMX.google.android.index.enableAndroidNativeBuffers isn't supported then do what was done in gb.
or 2) write a wrapper for the GB codec that we do have doing the pixel format conversion in software. This again should work, after all the generic gb stagefright code had to do it on gingerbread so it must be possible.
I think option 2 will be the best bet since we will not change any of the generic code to do it. First step will be to create a wrapper that does nothing, but wraps the current codec, then hopefully we can use the various opensource drivers to work out what needs to be done to get our wrapper to work.
This information is all for Decode drivers, this approach might be possible with the encoding driver too, but I have done very little research into that.

It's good that someone is doing research on this............
I think this might help
http://limoa.sourceforge.net/
Click to expand...
Click to collapse
P.S.-You should consult all the people developing ICS for their respective ARMv6 devices
P.S.2-Submitted to portal

Our hardware has MDP 3.0.2 and you need at least MDP 4.0 for the OMX stuff. You need new hardware for this and qcom will for sure not investigate a lot of money for old and dead hardware.

An idea of some wrapper around the GB codecs sounds good, but wouldn't the CPU be eaten doing this?

i think it will be better than nothing (like now)

modpunk said:
Our hardware has MDP 3.0.2 and you need at least MDP 4.0 for the OMX stuff. You need new hardware for this and qcom will for sure not investigate a lot of money for old and dead hardware.
Click to expand...
Click to collapse
I have to admit that I know very little about the abilities of our hardware, and given your excellent work on this ROM I'm sure you know much more, however, our hardware CAN play videos using hardware OMX drivers on Gingerbread why specifically do you think that the hardware wouldn't be up to it on ICS ?

benjamingwynn said:
An idea of some wrapper around the GB codecs sounds good, but wouldn't the CPU be eaten doing this?
Click to expand...
Click to collapse
Well, that might well be the problem, however, I have two thoughts on this:
1) Doing some of the decode in hardware and some in software should be better than all in software (depending on the hoops we have to jump through to get the APIs to match).
2) GB must be converting the output of the GB OMX drivers into some kind of native buffer so that it can display the frames so that would indicate it should be possible.
In the end, until we try we won't find out.

scottrix said:
Well, that might well be the problem, however, I have two thoughts on this:
1) Doing some of the decode in hardware and some in software should be better than all in software (depending on the hoops we have to jump through to get the APIs to match).
2) GB must be converting the output of the GB OMX drivers into some kind of native buffer so that it can display the frames so that would indicate it should be possible.
In the end, until we try we won't find out.
Click to expand...
Click to collapse
Just wondering, I'm not the most profficient in coding and the like, but what kind of programmer *may* be able to create a script for something like this? Someone with Android SDK and Java experience, or is it C based?

Ko_Ka said:
Just wondering, I'm not the most profficient in coding and the like, but what kind of programmer *may* be able to create a script for something like this? Someone with Android SDK and Java experience, or is it C based?
Click to expand...
Click to collapse
Code is C / C++ look in vendor/qcom/opensource/omx

scottrix said:
Code is C / C++ look in vendor/qcom/opensource/omx
Click to expand...
Click to collapse
Well, I have had some time to play and I have decided to change the code:
vendor/qcom/opensource/omx/mm-core/omxcore/src/common/omx_core_cmp.cpp
this seems to be a wrapper around the OMX codec, just making my edits with ENABLE_GINGERBREAD_OMX_DRIVERS define. Would be nice to come up with a cleaner solution, i.e. one that doesn't need changes to CM source as I doubt we would get modifications upstream, but until I get something working, it will do.
I have got rid of the get_extension_index problem, and some set_parameter problems, however, the underlying driver is giving:
Set Parameter called in Invalid State
Which isn't good since we don't have the source to know why it thinks it is invalid. My next step is to trace through the CM7.2 and CM9 code to work out how they are configuring the OMX driver differently. I should probably point out that my first goal is to get the codec running, I expect the screen output to be incorrect and need some colour format conversion, but one step at a time.
I am currently only looking at Decode, does anyone know if encoding (taking videos with the camera) works with the GB codec (can use logcat to tell if it is using sofware or GB codec).
BTW, there is code in vendor/qcom/opensource, have we asked qcom if they would be prepared to opensource the GB codecs ? they have obivously done it before so might be interested.

Progress, well not quite, but I have found some more out. First in the code:
frameworks/base/media/libstagefright/OMXCodec.cpp
In the class constructor there is this code:
mNativeWindow(
(!strncmp(componentName, "OMX.google.", 11)
|| !strcmp(componentName, "OMX.Nvidia.mpeg2v.decode"))
? NULL : nativeWindow) {
If mNativeWindow is NULL then it doesn't do a get_extension_index for the nativebuffers and grepping the software codecs shows that these don't support it either. It's not the place in the code I wanted to start altering, but let's get something working first. So I added the qcom component name to this list and now get further...... but still no working video. I have been through the code from the component init to the point of failure:
I/OMXCodec( 106): [OMX.qcom.video.decoder.mpeg4] calling emptyBuffer with codec specific data
I/QC_CORE ( 106): OMXCORE: qc_omx_component_empty_this_buffer 1c894, 1f838
D/VCODEC omx_vdec( 106): omx_vdec::empty_this_buffer +
D/VCODEC omx_vdec( 106): omx_vdec::empty_this_buffer vdec_open +
D/VCODEC vdec( 106): vdec_open
W/VCODEC vdec( 106): vdec: failed to allocate pmem arena (5783552 bytes)
E/VCODEC vdec( 106): vendor/qcom/proprietary/qdsp5/mm-video/7k/7x27/vdec-omxmp4/../vdec-common/vdec.cpp:365 *** ERROR ASSERT(0)
and compared it to the cm7 code. I have also installed cm7 and compared the output from a logcat, and still no luck, I have found other differences, however, none have actually made a difference. next step is to output more tracing from cm7 and cm9 to determine if there are more differences. My worry is that there is something else on the system messing with this hardware and initializing it in a different way. Does anyone know if the adreno drivers use /dev/pmem ? as these have changed from cm7 to cm9.

Hm, maybe qcom tech support could help you with the /dev thing. It may sound dumb but qcom are pretty good with stuff like this.
Sent from my Wildfire S A510e using xda app-developers app

omx
You won't find omx in gingerbread.. it was one of ics's new implimentations to enable hardware accelleration. Tis why qualcom released updated firmware to aid devs porting to ics. Pretty much our luck ran out there. The petition died when 1)Qualcomm said omx codecs were not possible for our chips and 2)Arm pulled the old arm11 development layer down.. So, pretty much not possible. Basically as I understand it, it requires adv sim.d or what arm calls neon (or a msm7x27a chip.. we have msm 7x27)
What is possible is what you mentioned. Using gb binaries with a wrapper. This wrapper is called a HAL. Unfortunately, CM has stated the time investment to do this for each cortex a8 is not worth it (and may break cvs); so, their official support (if we should even be able to get it for our beleagured device) would end with gb. And thus ends my input for the evening.
Rob

insink71 said:
You won't find omx in gingerbread.. it was one of ics's new implimentations to enable hardware accelleration. Tis why qualcom released updated firmware to aid devs porting to ics. Pretty much our luck ran out there. The petition died when 1)Qualcomm said omx codecs were not possible for our chips and 2)Arm pulled the old arm11 development layer down.. So, pretty much not possible. Basically as I understand it, it requires adv sim.d or what arm calls neon (or a msm7x27a chip.. we have msm 7x27)
What is possible is what you mentioned. Using gb binaries with a wrapper. This wrapper is called a HAL. Unfortunately, CM has stated the time investment to do this for each cortex a8 is not worth it (and may break cvs); so, their official support (if we should even be able to get it for our beleagured device) would end with gb. And thus ends my input for the evening.
Rob
Click to expand...
Click to collapse
OMX IS in gingerbread (or at least CM7), in fact the requirements for it are cleaner than ICS, ICS requires some google specific extensions. There ARE OMX drivers for the msm7x27, but they don't support the google extensions and so don't work (although it is a little more complicated than that). CM has stated that they will not support ARM6 devices so even if we were to get drivers from Qualcom, CM would not support it. Just cos CM say they aren't going to support it doesn't mean that it is not possible to produce a great ROM, as Ben and Modpunk and others have already proven, if you are looking for a CM supported version then you will need to buy a new phone.
I've been a little busy with other things over the last week or so and hope to get back to this soon.
One question I do have is that if I were to use the GB Adreno drivers on the ICS ROM would the phone still boot ? what would be the problems I'd notice ? not thinking of this as a long term solution, but might help me figure out what is going on, if my current thoughts turn up nothing.
Scott.

scottrix said:
OMX IS in gingerbread (or at least CM7), in fact the requirements for it are cleaner than ICS, ICS requires some google specific extensions. There ARE OMX drivers for the msm7x27, but they don't support the google extensions and so don't work (although it is a little more complicated than that). CM has stated that they will not support ARM6 devices so even if we were to get drivers from Qualcom, CM would not support it. Just cos CM say they aren't going to support it doesn't mean that it is not possible to produce a great ROM, as Ben and Modpunk and others have already proven, if you are looking for a CM supported version then you will need to buy a new phone.
I've been a little busy with other things over the last week or so and hope to get back to this soon.
One question I do have is that if I were to use the GB Adreno drivers on the ICS ROM would the phone still boot ? what would be the problems I'd notice ? not thinking of this as a long term solution, but might help me figure out what is going on, if my current thoughts turn up nothing.
Scott.
Click to expand...
Click to collapse
If I remember correctly (I might be wrong here) using gingerbread drivers broke hardware acceleration.

benjamingwynn said:
If I remember correctly (I might be wrong here) using gingerbread drivers broke hardware acceleration.
Click to expand...
Click to collapse
OK, I have put lots of tracing for all omx calls to the binary codec in the omxcore and got logs for this from both ICS and GB. There isn't any difference in the calls and there aren't any differences in the parameters passed to those calls. Looking at include files the structures used in these calls have not changed (which might make the tracing look OK, but the binary data different there by upsetting the GB driver when given ICS structures). My only conclusion is that the ICS drivers for hardware graphics acceleration (EGL, GLES, OpenVG) use more resources from the qdsp5, or affects the qdsp5 in a way that stops the GB OMX codecs working. I believe the ICS graphics drivers from QCom are:
vendor/qcom/msm7x27/proprietary/lib/libsc-a2xx.so
vendor/qcom/msm7x27/proprietary/lib/libgsl.so
vendor/qcom/msm7x27/proprietary/lib/libC2D2.so
vendor/qcom/msm7x27/proprietary/lib/egl/libGLES_android.so
vendor/qcom/msm7x27/proprietary/lib/egl/libq3dtools_adreno200.so
vendor/qcom/msm7x27/proprietary/lib/egl/libEGL_adreno200.so
vendor/qcom/msm7x27/proprietary/lib/egl/eglsubAndroid.so
vendor/qcom/msm7x27/proprietary/lib/egl/libGLESv1_CM_adreno200.so
vendor/qcom/msm7x27/proprietary/lib/egl/libGLESv2_adreno200.so
vendor/qcom/msm7x27/proprietary/lib/libOpenVG.so
vendor/qcom/msm7x27/proprietary/etc/firmware/a300_pfp.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/leia_pm4_470.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/leia_pfp_470.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/yamato_pfp.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/a225_pfp.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/yamato_pm4.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/a225_pm4.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/a225p5_pm4.fw
vendor/qcom/msm7x27/proprietary/etc/firmware/a300_pm4.fw
Of these files I could only find the following in GB:
system/lib/libgsl.so
system/lib/egl/libGLES_android.so
system/lib/egl/libEGL_adreno200.so
system/lib/egl/libGLESv1_CM_adreno200.so
system/lib/egl/libGLESv2_adreno200.so
So I deleted the missing ones and copied the GB ones over the ICS ones. This seemed to give me a "working" system, but with no display. Does anyone know how to get graphics on ICS working without using hardware graphics drivers ? If I could do that it would test my theory that the ICS hardware graphics acceleration libraries (EGL, GLES and VG) are stopping the hardware OMX codecs from working.

Hm this looks promising. The HTC hero uses adreno(?) 100 graphics whereas we use adreno 200, since qcom never released adreno 100 libs it'd be interesting to see how they got hwa on ics.
github.com/teamics
Sent from my Wildfire S A510e using xda app-developers app

benjamingwynn said:
Hm this looks promising. The HTC hero uses adreno(?) 100 graphics whereas we use adreno 200, since qcom never released adreno 100 libs it'd be interesting to see how they got hwa on ics.
github.com/teamics
Sent from my Wildfire S A510e using xda app-developers app
Click to expand...
Click to collapse
More importantly do the OMX drivers work on their build. If yes that would be worth looking into if not why bother, that automaticly eliminates the theory above.
Edit: I actualy looked that up myself and what i saw is Video playback does work on the Hero. However they havent goten HWA working. But thats what i got from the op on the CM9 and CM10 threads might be something im missing. But this seems to prove the theory about ICS libs stoping omx from working on our device. The question becomes now will it ever be possible to have them both working ?

baluuu said:
More importantly do the OMX drivers work on their build. If yes that would be worth looking into if not why bother, that automaticly eliminates the theory above.
Edit: I actualy looked that up myself and what i saw is Video playback does work on the Hero. However they havent goten HWA working. But thats what i got from the op on the CM9 and CM10 threads might be something im missing. But this seems to prove the theory about ICS libs stoping omx from working on our device. The question becomes now will it ever be possible to have them both working ?
Click to expand...
Click to collapse
Looking at the Hero threads it seems that HQ video isn't working either. Does any one know different ?.

scottrix said:
Looking at the Hero threads it seems that HQ video isn't working either. Does any one know different ?.
Click to expand...
Click to collapse
May I add some input?
Eoghan2t7, who's working on porting Firefox OS aka B2G, has looked at the files and has noticed that even though B2G is based off ICS, it uses the Gingerbread OMX libs. Now, we need to see of there's some code wrapped up around it, which allows the GB libs to work on ICS.
If we get that code (if it does exist) then our problem may have been solved.
Here's his quote:
eoghan2t7 said:
hi everyone so far my attempts on getting this to build have not worked so i am going to taking a break at trying to fix the build errors and start reading up on github of ports already done to see what commits are needed etc. i am also puzzled to why the b2g seems to use the gingerbread omx files instead of using the omx files from AOSP ICS so ill be looking into that as well incase there are some code added to it to allow the GB libs to work on ICS since b2g is based off ICS
Click to expand...
Click to collapse
Sent from my HTC Wildfire S using xda premium

[MODS/Q&A ] XenonHD ROM ALL DEVICES

{
"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 am going to fill this op with Questions and answers from all devices supported by Team Horizon. Please keep the respect and KEEP ALL NON DEVELOPMENT DISCUSSION HERE OR OUR
GOOGLE PLUS PAGE
Click to expand...
Click to collapse
.
Click to expand...
Click to collapse
Q. I came from 4.1.2 and I flashed your 4.2.1 and I can't access my files now?
A. Well this is because after the 4.2.1 update Google implemented a feature with in its ROM to allow for the use to apply user specific accounts. I suggest reflashing a 4.1.2 ROM, Then mount the phone once booted, Take all of the information you choose to keep and place it on your desktop, Once complete then reboot the phone into recovery and wipe the rm and reflash 4.2.1 once you have flashed rom and gapps, Before you leave recovery wipe the sd card. Once phone reboots then simply replace the information you placed on your desktop to its corresponding folder.
Click to expand...
Click to collapse
Q. my wifi is always on when in standby?
A.Disable wifi optimization, And avoid poor connections in wifi advanced options.. If you have Franco kernel, wifi fast pm helps too
Click to expand...
Click to collapse
Q. HELP I don't have a rom on my SD card and I am stuck in a boot loop what do I do?
A. You need to make sure you have a working adb setup along with all proper fastboot and device drivers installed. Place the rom you wish to flash in the root of the adb folder.
Make sure phone is in recovery mode and that it is plugged into the computer.
Open a command prompt and cd to the directory of the adb folder. ( or simply hold the shift key and right click your adb folder and choose to open command windows here)
now type: adb push (rom.zip) /sdcard/ (replace the (rom.zip) with the entire name of the rom.zip.)
Click to expand...
Click to collapse
Q. How come fast charge is not working or its enabled but not working?
A. Answer is simple, The roms stock kernel doesn't allow for fast charge. you may simply flash Franco kernel and or any other 4.2.1 kernel that supports to to gain functionality.
Click to expand...
Click to collapse
Q. Can I dirty flash (flash ROM without wipe)?
A Yes you may flash the ROM without wiping. YOU WILL HAVE TO REFLASH GAPPS. We don't recommend doing this but if you are pressed for time or its just too difficult then have at it. We will not support complaints from those that choose to go this route.
Click to expand...
Click to collapse
Warez Removed
Q. I have downloaded the ROM but it wont boot?
A. Please make sure you are downloading the correct ROM and completely wiping before flashing!
Crespo- http://d-h.st/users/iceandfire/?fld_id=9532#files
Grouper- http://d-h.st/users/iceandfire/?fld_id=8701#files
Maguro- http://d-h.st/users/iceandfire/?fld_id=8699#files
Mako- http://d-h.st/users/iceandfire/?fld_id=9438#files
Toro- http://d-h.st/users/iceandfire/?fld_id=8700#files
Toro Plus- http://d-h.st/users/iceandfire/?fld_id=9002#files
Click to expand...
Click to collapse
Q. Somebody know, how to disable waking up phone by pressing volume button?I dont like this feature.
A. Menu>settings>display>enable then disable the volume key MOD
Click to expand...
Click to collapse
Q. Where are my Chrono settings for weather and clock?
A. Menu>System Settings>Display>Clock widget
Click to expand...
Click to collapse
Q. Are the round widgets shown in the OP contained in the ROM? If not, are they available anywhere? Also, I cannot for the life of me figure out how to put a lockscreen widget. When I go into the Chronus settings, there are settings for the clock, weather and calendar widgets, but I can only add the clock widget to my device.
A. OK the widget is not included but called one more clock widget. To apply the clock. Lock the screen then place your finger on the clock and slide down till you reach the lock icon or the white outline is the write screen amd let go. Then long press the clock ad delete it. Then click the add widget . After you enabled everything in display then go to chrono in the options onthe lockscreen (the + sign from earlier) and add it. To add muliple widgets then slide down on clock to fill screen then swipe left or right.
Click to expand...
Click to collapse
Q. What is fast charge? what does it do for me? How do I get it to work?
A.
Fast charge is a option baked into the kernel that doesn't allow the phone to be mounted to the pc.
Keeps computer from mounting your sd card everytime its plugged in.
You need to install a kernel that supports it. Stock XennonHD doesn't allow for this. I suggest using Franco Kernel. found here: http://forum.xda-developers.com/showthread.php?t=1367341
Click to expand...
Click to collapse
Q. What gapps do i install on this rom? I installed the gapps from ice not all my apps are there?
A.
Download these gapps: http://goo.im/gapps/gapps-jb-20121212-signed.zip
Because all of the apps missing can be manually installed from the market. He did this to lighten the download.
Click to expand...
Click to collapse
Q. How to create a log cat
A. the code for logcat to output to a file is
adb logcat > name of problem.txt
you can also do
Click to expand...
Click to collapse
adb logcat -f name of problem.txt
how I prefer to do it is this way
Click to expand...
Click to collapse
:
adb logcat -v long > name of problem.txt
with the -v flag & the long argument, it changes output to long style, which means every line of logcat will be on its own line (makes it a little neater, imo)
Note: When outputting to a file, you will see a newline, but nothing printed, this is normal. To stop logcat from writting to a file, you need to press ctrl+c.
Click to expand...
Click to collapse
Here's where using logcat (via adb makes life really easy)
Lets say you find a problem you're having after looking at a logcat.
For example:
When I was trying to use a different ramdisk, wifi wouldn't work so I got a logcat that's almost 1300 lines long (a lot of stuff happens in the background)
So if you are searching for an error in the logcat file (it's always e/ for error, f/ for fatal. Those are the two main things that will break a system.)
D/dalvikvm( 871): GC_CONCURRENT freed 472K, 6% free 10224K/10823K, paused 1ms+6ms
V/AmazonAppstore.DiskInspectorServiceImpl( 871): Available blocks: 21981, Block size: 4096, Free: 90034176, Threshold: 5242880, withinThreshold? true
D/AmazonAppstore.UpdateService( 871): Received action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
W/AmazonAppstore.UpdateService( 871): Confused about why I'm running with this intent action: null from intent: Intent { cmp=com.amazon.venezia/com.amazon.mas.client.framework.UpdateService }
D/dalvikvm( 890): GC_CONCURRENT freed 175K, 4% free 9375K/9671K, paused 2ms+3ms
V/AmazonAppstore.ReferenceCounter( 871): Reference (MASLoggerDB) count has gone to 0. Closing referenced object.
E/WifiStateMachine( 203): Failed to reload STA firmware java.lang.IllegalStateException: Error communicating to native daemon
V/AmazonAppstore.UpdateService( 871): runUpdateCommand doInBackground started.
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateCommand( 871): Not updating key: digitalLocker from: 1334228488057
V/AmazonAppstore.UpdateService( 871): Finished UpdateCommand: digitalLocker
V/AmazonAppstore.UpdateService( 871): Running UpdateCommand: serviceConfig
V/AmazonAppstore.MASLoggerDB( 871): performLogMetric: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
V/AmazonAppstore.MASLoggerDB( 871): onBackgroundTaskSucceeded: Metric logged: ResponseTimeMetric [fullName=com.amazon.venezia.VeneziaApplication_onCreate, build=release-2.3, date=Wed Apr 11 13:10:55 CDT 2012, count=1, value=1601.0]
W/CommandListener( 118): Failed to retrieve HW addr for eth0 (No such device)
D/CommandListener( 118): Setting iface cfg
D/NetworkManagementService( 203): rsp
D/NetworkManagementService( 203): flags
E/WifiStateMachine( 203): Unable to change interface settings: java.lang.IllegalStateException: Unable to communicate with native daemon to interface setcfg - com.android.server.NativeDaemonConnectorException: Cmd {interface setcfg eth0 0.0.0.0 0 [down]} failed with code 400 : {Failed to set address (No such device)}
W/PackageParser( 203): Unknown element under : supports-screen at /mnt/asec/com.android.aldiko-1/pkg.apk Binary XML file line #16
D/wpa_supplicant( 930): wpa_supplicant v0.8.x
D/wpa_supplicant( 930): random: Trying to read entropy from /dev/random
D/wpa_supplicant( 930): Initializing interface 'eth0' conf '/data/misc/wifi/wpa_supplicant.conf' driver 'wext' ctrl_interface 'N/A' bridge 'N/A'
D/wpa_supplicant( 930): Configuration file '/data/misc/wifi/wpa_supplicant.conf' -> '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): Reading configuration file '/data/misc/wifi/wpa_supplicant.conf'
D/wpa_supplicant( 930): ctrl_interface='eth0'
D/wpa_supplicant( 930): update_config=1
D/wpa_supplicant( 930): Line: 4 - start of a new network block
D/wpa_supplicant( 930): key_mgmt: 0x4
(mind you, that's 29 lines out of 1300ish, just for example)
Click to expand...
Click to collapse
I then could do the following with logcat:
adb logcat WifiStateMachine:E *:S -v long > name of problem.txt
and this will only print out any errors associated with WifiStateMachine, and anything which is fatal, which makes it about a million times easier to figure out what's going on!
Click to expand...
Click to collapse
In WifiStateMachine:E, the :E = to look for Errors, the full list of options is as follows:
V — Verbose (lowest priority)
D — Debug
I — Info (default priority)
W — Warning
E — Error
F — Fatal
S — Silent (highest priority, on which nothing is ever printed)
You can replace the :E with any other letter from above to get more info.
In order to filter out anything other than what you are looking for (in this case, WifiStateMachine) you must put a *:S after your last command (i.e. WifiStateMachine:E ThemeChoose:V ... ... AndroidRuntime:E *:S)
Click to expand...
Click to collapse
Q. I am in the download section but what rom is for my device?
A.
Crespo- nexus S
Grouper- Nexus 7
Maguro- gsm galaxy nexus t-mobile
Mako- galaxy nexus 4
Toro- Galaxy nexus Verizon Wireless
Toro Plus- sprint galaxy nexus
Click to expand...
Click to collapse
Click to expand...
Click to collapse
==================================================
Important please read
I. Appreciation
There are many ways to show your support to us. You can:
Press the "Thanks" button.
Hit the donation button and help support the team
Wear our specially prepared banner
Share your opinion about my work and write some feedback in our threads.
Advertise our work to your friends, family, anyone who owns this device.
Rate our threads with 5 stars.
We appreciate all the support you give us, but we don't expect anything
Click to expand...
Click to collapse
II. Sharing
XDA-Developers.com is all about sharing. If you would like to use any part of our work, please feel free to do so but remember to do the following beforehand:
Inform - Please send us a PM or email telling us
Permission - Please, if you do not have permission from us, don't use it. Most of the time, we will allow you to, but if you don't get our permission first, we will report.
Credits - No one wants their work stolen. Please remember to give proper credits when using our work.
Click to expand...
Click to collapse
:
III. Support
If you have any issues or questions, please feel free to post them in the our threads. However, because all of us have social lives outside of XDA, your questions may not always be answered right away. Members who are more experienced in our work, please help out the ones who don't.
If you want to get the fastest and the best answer - ask the question in our threads instead of PM'ing us. Chances are, other users will be able to help you when Team Members don't have the time to.
Click to expand...
Click to collapse
IV. Updates
We are a busy team! Every Team Member has lives outside of XDA. You cannot expect us to sit in front of the computer all day and develop Android. Please do not ask for ETA's. The update will come when we release it. Sometimes, there is a good reason for why we have not released an update in a while. Please be patient with us, we will do as we promise. Updates will come.
Click to expand...
Click to collapse
V. Responsibilities
We are not responsible for your device! We do not guarantee that everything will work the way it's supposed to. Not every device is created equal, what might work on our devices may not work on yours or vice versa. Please be a responsible person when it comes to flashing. This is a mature site, don't act immaturely when your device becomes problematic. If you cry and blame us for "destroying" your device, we will laugh at you. Your device is your responsibility, act like it.
Thanks for choosing Team Horizon, we hope you enjoy our works as much as we enjoy working with them.
Click to expand...
Click to collapse
Click to expand...
Click to collapse

MOD Section
This is going to be a section where I post add ons for this ROM. Enjoy!
Click to expand...
Click to collapse
<---------http://dl.dropbox.com/u/44672998/supporter.png
My Dev-Host Account With All The Add On Downloads!
http://goo.gl/4rscI
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Invered Gapps! 4.2.1
CLICK ME
Click to expand...
Click to collapse
:highfive:

HELP!
Please Help Contribute To This Project. Either Post Question With Answer and I Will Add To OP or PM Me The Stoofz
:highfive:

Great idea Tory, You have been a real asset to the team, thanks for all you do.
Sent from my SCH-I535 using Tapatalk 2

I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2

crispy1 said:
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am on latest franco and fixing to test wifi tether. hold (on gsm tho)

crispy1 said:
I'm transferring this topic from the main page. I'm running 1.5 for Toro and had issues with WiFi tether. I dirty flashed from the prior version. I was running Franco 356. I wiped and restored 12-22 then dirty flashed again to 1.5. This time I'm still running the included kernel. I tested WiFi tether and it seems to work. Thusly, I think the issues may be related to Franco 356. Anybody got WiFi tether working with Franco?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I was able to connect wifi tether and usb tether with the latest franco. Keep in mind that I ALWAYS WIPE before flashing any updates to iron out those pesky little bugs.

pr0xy mAn1Ac said:
I was able to connect wifi tether and usb tether with the latest franco. Keep in mind that I ALWAYS WIPE before flashing any updates to iron out those pesky little bugs.
Click to expand...
Click to collapse
OK, good to know. I'll flash Franco and if it is still broken, I'll clean flash 1.5 followed by an update to Franco.
Sent from my Galaxy Nexus using Tapatalk 2

crispy1 said:
OK, good to know. I'll flash Franco and if it is still broken, I'll clean flash 1.5 followed by an update to Franco.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Please keep us posted on your progress. let me know if I can help.

Quick Unlock
Is quick unlock working? It has not worked for me for a while, but I saw one person say it works. I have done a full wipe with each version. Thanks!

pr0xy mAn1Ac said:
Please keep us posted on your progress. let me know if I can help.
Click to expand...
Click to collapse
I reflashed clean and am still unable to connect. Still on default kernel. I can see the network but I cannot connect even without security. Tried both an iPad and an Android tablet. Blue tooth tether works but that us too slow. I'm out of options. This is a show stopper for me.
Sent from my Galaxy Nexus using Tapatalk 2

crispy1 said:
I reflashed clean and am still unable to connect. Still on default kernel. I can see the network but I cannot connect even without security. Tried both an iPad and an Android tablet. Blue tooth tether works but that us too slow. I'm out of options. This is a show stopper for me.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I have to have tethering. Flashed back to CNA 3.8 and I got it back. May need to hang on to 4.1.2 a bit longer.
Sent from my iPad using Tapatalk HD

crispy1 said:
I have to have tethering. Flashed back to CNA 3.8 and I got it back. May need to hang on to 4.1.2 a bit longer.
Sent from my iPad using Tapatalk HD
Click to expand...
Click to collapse
edited
10char

Navigation bar opacity
I love the whole ROM, been using it for a while. I was very excited to see a translucent menu bar option in the 12/30/12 release. However im not sure of its functioning properly. On the home screen the nav bar is translucent however in any app its a solid black background again. When I zoom using accessibility feature (triple tap) the nave bar goes back to being all but invisible. Is this transparent effect only supposed to do what it does on my case? Thanks man, keep up the good work

Just a quick question pr0xy ... Do I have to wipe data in order to install inverted gapps or can i dirty flash over the 20121212 package? Thx in advance!

Just flash the gapps brother no wiping needed. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2

Ok, another stupid question inc! :/ Proxy - do you know of any place where I could get "Black Facebook" to match the inverted gapps ? Since I kinda prefer it over the stock white FB app ... I could find only some lower versions which are slow and buggy, so ... Thx in advance

Doomhamma said:
Ok, another stupid question inc! :/ Proxy - do you know of any place where I could get "Black Facebook" to match the inverted gapps ? Since I kinda prefer it over the stock white FB app ... I could find only some lower versions which are slow and buggy, so ... Thx in advance
Click to expand...
Click to collapse
It is included with the inverted gapps. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2

pr0xy mAn1Ac said:
It is included with the inverted gapps. Enjoy.
Sent from my Galaxy Nexus using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
No it's not ... That's why I asked

*DUMB NEWBIE QUESTION*
how to flash this rom ?
just tried to flash the rom using TWRP, but it stucks at bootlogo.
now restored the rom and N4 is working normal.
any solution ?
thx in advance.

Random reboots with lineage os

Hey guys I'm fairly new to rooting but I finally got lineage os on my phone at first I thought the ROM was great until I saw it would reboot automatically. I installed a custom kernel to see of it makes it worse or better, then I compared lineage kernel and it still reboots. So it either has to be the apps, or the ROM itself. What do you guys think
Thanks

Does anyone who have lineage os on their one plus 2 experience this too or is it just me
Also even with lineage os my battery said that lineage os and it's kernel took 20% and 10% of the whole battery and it was in the background... What gives
The other kernel I had was the boeffla in case someone is wondering. It is still in beta but my phone was crashing without so I don't think that's the main reason why it's rebooting

With the 20170313 nightly on my Mi4, I have the same problem, yesterday it was several times in the same day

Jsmoov5 said:
Does anyone who have lineage os on their one plus 2 experience this too or is it just me
Also even with lineage os my battery said that lineage os and it's kernel took 20% and 10% of the whole battery and it was in the background... What gives
The other kernel I had was the boeffla in case someone is wondering. It is still in beta but my phone was crashing without so I don't think that's the main reason why it's rebooting
Click to expand...
Click to collapse
I have the OnePlus 2 aswell, I have seen 7-8-9-14+++ random reboots today

With Franco kernel I'm down to 1-2 random reboots each day.

hey, i have the OP2 as well and my phone randomly reboots but 95 % of the time the reboots happen while my phone isn't awake. Also, the reboots tend to happen in sequences: i can get like up to 10 of them in 1 hour and none at another moment of the day... pls help if you know anyhing. ( im using the default kernel i guess. Should I try to install another one ?
---------- Post added at 08:18 PM ---------- Previous post was at 08:01 PM ----------
krugm0f0 said:
With Franco kernel I'm down to 1-2 random reboots each day.
Click to expand...
Click to collapse
Imma try it then, are there any particular settings wich make it better ?

Current version seems more stable : no reboot since the update

Need Help
Hey guys! I built Lineage 14.1 for NX510J by using the source code. But it didn't boot. So I used the boot.img from another LOS-14.1 for the NX510J which can work normally . Although my phone can boot, it rebooted every time when entried into setup wizard. Can someone help me fix it? Any suggestion will be appreciated！

Same here. My phone (Samsung S3) random reboots. Any suggestion?

It looks like there's an open issue submitted on LineageOS JIRA regarding random reboot.
https://jira.lineageos.org/plugins/servlet/mobile#issue/BUGBASH-667
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [d2vzw] from the Bridge of the U.S.S. Enterprise.

Me too: LG G3 D855
Hi All,
I'm also seeing reboots.
Sometimes I go for weeks with no reboot. Other times I get several in an hour. Lately I've even seen them immediately after a reboot, when I unlock the screen for the first time!
I've had this for as long as I can remember, but just got around to mentioning it.
In other respects - thanks guys for the great achievement of LineageOS!
BTW: the last time this happened (this morning) I was running last week's nightly:
lineage-14.1-20171030-nightly-d855-signed.zip
Martin

Random reboots have been a "feature" of cm/Los based roms for years. Which was never fixed. That is why dev teams stopped using them as a base.

zelendel said:
Random reboots have been a "feature" of cm/Los based roms for years. Which was never fixed. That is why dev teams stopped using them as a base.
Click to expand...
Click to collapse
So you are saying that lineageos is inherently unstable and always will be?
What do the development teams use as a base now?

robjg63 said:
So you are saying that lineageos is inherently unstable and always will be?
What do the development teams use as a base now?
Click to expand...
Click to collapse
Unless they go back and fix it (tons of work) then yes. Many started over with pure aosp back in 5.0 - 6.0 so many have their own bases. Some also use caf bases for snapdragon based devices.

So I have a Galaxy note 2 that I recently flashed lineageos on. It's actually been going quite well - but I have noticed random reboots from time to time. Sometimes its ok for a day or two - and other times it might do it a couple of times in a day.
If there are some other packages that have a different base (than Lineageos) is it ok for you to mention them so I can do a bit of research?

I think, the reboot issue is device specific. My moto e (condor) only reboots, when I use the power button for lock & wake. Now I let gravity screen app do that and there are no reboots.

robjg63 said:
So I have a Galaxy note 2 that I recently flashed lineageos on. It's actually been going quite well - but I have noticed random reboots from time to time. Sometimes its ok for a day or two - and other times it might do it a couple of times in a day.
If there are some other packages that have a different base (than Lineageos) is it ok for you to mention them so I can do a bit of research?
Click to expand...
Click to collapse
I am not sure about what is avaiable for that device. Samsung devices were not picked up by all the teams as they were difficult to get working without issues. I would try maybe SLim roms. They are AOSP based. But to be honest. If I had a samsung I would use a stock based rom (even if it is older) this way I dont lose any of samsungs features
kurtn said:
I think, the reboot issue is device specific. My moto e (condor) only reboots, when I use the power button for lock & wake. Now I let gravity screen app do that and there are no reboots.
Click to expand...
Click to collapse
Thats the thing, the causes are different for different devices. This is why it would be tons of work. They would have to start over from scratch. With a pure base and make their changes bit by bit. Testing as they go (which didnt happen alot when it was CM. Depending on who pushed the commit it would just be merged without testing)

zelendel said:
Unless they go back and fix it (tons of work) then yes. Many started over with pure aosp back in 5.0 - 6.0 so many have their own bases. Some also use caf bases for snapdragon based devices.
Click to expand...
Click to collapse
So, could you name a few ASOP ROMs that *don't* have random reboots? Please?

mcatkins said:
So, could you name a few ASOP ROMs that *don't* have random reboots? Please?
Click to expand...
Click to collapse
The only one I can name is Slim roms. Most of the other teams I use have left xda and dont allow their builds here. I personally use Dirty Unicorns but again they are not on XDA.
This also depends on your device. If you have an older device then you may only be stuck with CM/Los as most aosp teams only support devices that someone on the team owns. This way it can be tested in real time and not just "the code should work on every device" frame of mind.

Random reboots on i9505 with lineage os 14.1
My dmesg.log tail reads:
<6>[ 29.992553] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[7] V[5c]
<6>[ 36.075195] [SSP]: debug_work_func(1) - Sensor state: 0x3fff, RC: 0, MS: 0
<6>[ 39.306854] sec-fuelgauge 11-0036: 0x02(0xb6), 0x03(0xf0), 0x04(0x3a), 0x05(0xdf), 0x06(0x00), 0x07(0x00), 0x08(0x00), 0x09(0x12), 0x0a(0x00), 0x0b(0x00), 0x0c(0x6c), 0x0d(0x1e),
<6>[ 39.310455] sec-fuelgauge 11-0036: 0x14(0x00), 0x15(0xff), 0x16(0xfe), 0x17(0x42), 0x18(0x7d), 0x19(0x00), 0x1a(0x01), 0x1b(0xff),
<6>[ 39.310455] sec-fuelgauge 11-0036: sec_fg_get_atomic_capacity: old : 29, current : 29
<6>[ 39.310974] max77693_get_input_current: CHG_CNFG_09(0x17)
<6>[ 39.322479] sec-battery sec-battery: sec_bat_get_battery_info:Vnow(3658mV),Inow(460mA),SOC(29%),Tbat(361)
<6>[ 39.322509] sec-battery sec-battery: sec_bat_monitor_work: Status(Discharging), mode(None), Health(Good), Cable(1), siop_level(100)
<6>[ 39.323516] max77693-muic max77693-muic: func:max77693_muic_monitor_status, ST1:0x3f, ST2:0x0 CABLE:0
<6>[ 47.075164] [SSP]: debug_work_func(1) - Sensor state: 0x3fff, RC: 0, MS: 0
<6>[ 48.058441] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 48.128845] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[5] V[5c]
<6>[ 49.404785] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 49.506958] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[8] V[5c]
<6>[ 52.727386] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 52.786834] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[4] V[5c]
<6>[ 56.678344] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 56.748291] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[5] V[5c]
<6>[ 57.720306] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 57.790283] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[5] V[5c]
<6>[ 58.075164] [SSP]: debug_work_func(1) - Sensor state: 0x3fff, RC: 0, MS: 0
<6>[ 59.085662] synaptics_rmi4_i2c 3-0020: [0][P] 0x01
<6>[ 59.457580] synaptics_rmi4_i2c 3-0020: [0][R] 0x00 M[33] V[5c]
Do they suggest any anomaly?
I kind of suspect my China made extended battery isn't up to snuff

Develop Bugs

welcome