[ROM][ICS][06/26] ICS StuNNeR - 1.6.26

mblnx · May 31, 2012

dgfriedl said:
Neo,

[Thanks for the outstanding work!]

I'm not sure if I read it correctly, but in a post today by sfhub (http://xdaforums.com/showpost.php?p=26757432&postcount=400) it appears that the hard-brick can be avoided on any ICS kernel by modifying the ICS libext4_utils.a library and re-linking Recovery and update-binary (or by using GB Recovery and update-binary).

I'm still coming to grips with where things are located in the Android Linux distros and what components people are referring to when they flash a kernel vs a ROM, install root or CWM, and what elements of the OS are engaged when booting into recovery (is it an init level?). Even so, it appears to me that making this change is within your control and would let you safely use any kernel. Is that correct?

I thought this could be a good way to go given the concerns users have voiced with battery life in the CM9 kernel.

-darren

You need to read more, and more, then a little bit more. And I am not going to explain what's already been explained on the other thread. This thread is about stunner, and regarding stunner neo can use cm9 kernel or can use one of franco/hardcore's kernel as they won't trigger the bug and I think he is going to use one of them.

Just stop missreading other threads and trying to turn a very good explanation from sfhub into a one line thing. Even if you relink cwm you can brick your device by using the system factory reset, or by using anything that uses the function on affected kernels.

color_hunta · May 31, 2012

talhamid said:
Please note that I have wiped plenty of times on Stunner without ill effects. I think it's the KingDroid I flashed that did it. But yes, it is best to avoid it at the moment.

While it's good to read that talhamid managed to revive his Note at least sort of -

for your peace of mind, in the creepy name of MMC_CAP_ERASE and for the love of entropy:

if you're running an unsafe kernel stay clear of flashing AND wiping in recovery!

Sent from my GT-N7000 using XDA

Deleted member 267841 · May 31, 2012

Franco r4 is working fine with this rom

rayarny · May 31, 2012

I always installed CWm abyss 4.2 touch on top and rebooted recovery and wiped. Wiping on leaked kernel is a complete no no!! And if you want to restore, the guide by chasmodo is really helpful to not wipe, just restore from 4.2 abyss touch CWM recovery!

I tested paranoidandroid for sometime. Those themes are awesome!! But battery life totally sucked! CM9 kernel isnt battery friendly at all I guess lol..So back on stunner where I get 2 days easy!

kandem · May 31, 2012

bartito said:
Franco r4 is working fine with this rom

Screen rotation works with this kernel? Tell me about battery, more than lp6 or lp5? Thanks a lot!
PD.:waiting for a stunner updateeee

Enviat des del meu GT-N7000

evilmeat · May 31, 2012

Screen rotation not works on franco kernel.

Sent from my GT-N7000

Staxxthedan · May 31, 2012

kandem said:
Screen rotation works with this kernel? Tell me about battery, more than lp6 or lp5? Thanks a lot!
PD.:waiting for a stunner updateeee

Enviat des del meu GT-N7000

Hold your horses man and wait. When the worst comes to the worst I will jump in and help neo

Sent from my GT-N7000 using Xparent Pink Tapatalk 2

GuestK00336 · May 31, 2012

talhamid said:
Anyway then I read the description of MIDTeam's Codename B&G ROM and liked their method of restoring via Nandroid over Abyss Kernel. So I downloaded it and unzipped into the CWM folder on my phone. Then crossed my fingers and started the Nandroid restore.

I looked in the MidTeam thread. What a nightmare. Could you point me to where you gathered this information about the restore from?

talhamid · Jun 1, 2012

TREMER said:
I looked in the MidTeam thread. What a nightmare. Could you point me to where you gathered this information about the restore from?

LOL. Yes I agree the OP in the thread is awfully messy. If you scroll past the screenshots, the credits and the logo, it's right there under the heading "Let's Start".

Hope I understood your question correctly

As for your earlier question, restoring a pre-rooted GB ROM via PC Odin was the first thing I tried. The thing got stuck on 'Writing FactoryFS', indicating there were one or more bad sectors.

See this is what was most nightmarish about all this: CWM, PC Odin, all failing. Never thought that could happen!

dgfriedl · Jun 1, 2012

mblnx said:
You need to read more, and more, then a little bit more. And I am not going to explain what's already been explained on the other thread. This thread is about stunner, and regarding stunner neo can use cm9 kernel or can use one of franco/hardcore's kernel as they won't trigger the bug and I think he is going to use one of them.

Just stop missreading other threads and trying to turn a very good explanation from sfhub into a one line thing. Even if you relink cwm you can brick your device by using the system factory reset, or by using anything that uses the function on affected kernels.

Not the most civil reply.

I take your point about risks that will remain if an "unsafe" kernel is used and for that reason it would make sense to use a recompiled kernel in the standard distro.

The point that sfhub was making still applies here though, because if Neo uses the GB versions of Recovery and update-binary (or re-links them to a modified libext4_utils.a library), users who want to try a Samsung ICS kernel (to get better battery life, hardware support, etc) would still be able to safely flash from that kernel without hard-bricking.

I don't know for a fact that one of the Samsung kernels would be better -- we'll find that out following the next release, but why not make this change to allow for their use?

-darren

abhisahara · Jun 1, 2012

dgfriedl said:
Not the most civil reply.

I take your point about risks that will remain if an "unsafe" kernel is used and for that reason it would make sense to use a recompiled kernel in the standard distro.

The point that sfhub was making still applies here though, because if Neo uses the GB versions of Recovery and update-binary (or re-links them to a modified libext4_utils.a library), users who want to try a Samsung ICS kernel (to get better battery life, hardware support, etc) would still be able to safely flash from that kernel without hard-bricking.

I don't know for a fact that one of the Samsung kernels would be better -- we'll find that out following the next release, but why not make this change to allow for their use?

-darren

Mate the ROM will use the best suited kernel after the dev has tested it several times. If too much options comes in play then the dev cant test all of them....cant make the rom compatible with each kernel....and God forbid people brick there devices doing all those juggling then there will be many people pointing fingers at the dev!! So wait for the correct time and let the dev do what he does best...develop a stunning rom with the best suited kernel.

Edit - and just to make point a lil more clear - By using the GB version of recovery and updating binaries we are in safe environment but what about the most loved feature...the smoothness of stunner...because by doing the aforementioned you are making the system a GB performance if not worse.

*no offence* but you will get what the dev develops...you dont like it you can move on to something that suits you more! Simple!

Cheers!!

Deleted member 267841 · Jun 1, 2012

kandem said:
Screen rotation works with this kernel? Tell me about battery, more than lp6 or lp5? Thanks a lot!
PD.:waiting for a stunner updateeee

Enviat des del meu GT-N7000

hi,
you're right, screen rotation isn't working, but the kernel is safe and i'm capable to execute wipes and new installs from CWM. I prefer

--

hola,
tens raó, la rotació no funciona amb aquest kernel, però és un kernel segur i em permet fer wipe i noves instal.lacions des del recovery. ho prefereixo, tinc molta mala memòria

Deleted member 267841 · Jun 1, 2012

after a day with this ROM, i love it. is great.
only a small things:

- all photos and videos are duplicated in google gallery app. workaround: use quickpic
- google music app isn't playing my mp3 files stored in sdcard. workaround: use apollo, that shows duplicated files but plays fine
- all my ringtones are duplicated. no workaround for that

any solution to these bugs?
thank's

talhamid · Jun 1, 2012

bartito said:
after a day with this ROM, i love it. is great.
only a small things:

- all photos and videos are duplicated in google gallery app. workaround: use quickpic
- google music app isn't playing my mp3 files stored in sdcard. workaround: use apollo, that shows duplicated files but plays fine
- all my ringtones are duplicated. no workaround for that

any solution to these bugs?
thank's

Duplication of photos and videos: I myself didn't notice it, so you might want to clear data of gallery and then re-launch it.

Music: very simple. Unmount SD card and re-mount it; problem solved.

Ringtones: Funny, I didn't have this problem. Guess that's one you can/have to live with

pinoypower · Jun 1, 2012

bartito said:
after a day with this ROM, i love it. is great.
only a small things:

- all photos and videos are duplicated in google gallery app. workaround: use quickpic
- google music app isn't playing my mp3 files stored in sdcard. workaround: use apollo, that shows duplicated files but plays fine
- all my ringtones are duplicated. no workaround for that

any solution to these bugs?
thank's

+1 on the picture duplication, but mine is only for images I have downloaded. Photos taken by the camera do not appear duplicated. I am also having empty thumbnails on the gallery.

Sent from my GT-N7000 using xda premium

Deleted member 267841 · Jun 1, 2012

pinoypower said:
+1 on the picture duplication, but mine is only for images I have downloaded. Photos taken by the camera do not appear duplicated. I am also having empty thumbnails on the gallery.

Sent from my GT-N7000 using xda premium

gallery problems was solved using quickpick.

pinoypower · Jun 1, 2012

bartito said:
gallery problems was solved using quickpick.

yes. Cheers!

Sent from my GT-N7000 using xda premium

adario73 · Jun 1, 2012

about the duplicated pictures,
i solved moving the DCIM folder from the external SD to internal memory, and then clean application data.

Deleted member 267841 · Jun 1, 2012

bootanimation is not showed with this rom.
normal?¿

rmclardy · Jun 1, 2012

Nav bar buttons

Hi all, ive been scanning through this thread and can seem to see any difinitive thing about the issue i have.

As you can hopefully see from the pics, the issue i have is, when apps written for ICS are open, i get the usual 3 buttons on the nav bar fine. but legacy apps, (that require the menu to be shown in the nav bar) my normal 3 icons go uber small and its impossible to click them.

Any ideas?

im running 1.4.26.1 that was a completely clean install. running in tablet mode with 213dpi.

i have made the nav bar a 5 button arrangement and put blanks in positions 2 and 4, to space them out. though i did have this problem even if i set it to 3 button.

Any thoughts / help appreciated.

[ROM][ICS][06/26] ICS StuNNeR - 1.6.26

Senior Member

Member

Deleted member 267841

Guest

Senior Member

Senior Member

Member

Senior Member

GuestK00336

Guest

Senior Member

Senior Member

Senior Member

Deleted member 267841

Guest

Deleted member 267841

Guest

Senior Member

Senior Member

Deleted member 267841

Guest

Senior Member

Senior Member

Deleted member 267841

Guest

Member

Attachments

Similar threads

Top Liked Posts