
Announcement
Collapse
No announcement yet.
Announcement
Collapse
No announcement yet.
ENDED - Arnova 7G2 Finless Bob's "GingerComb" Custom ROM Version 2.1 BETA 2
Collapse
This topic is closed.
X
X
-
Originally posted by patalao View PostOk
I just tested this new update from Bob and here is feedback
The battery icon now works but when i download something it shows in the status bar the progress(as normal) but when i try to remove it from status bar by clicking the x it just reboot without reason
that`s the only thing i found so far
thank`s Bob for your hard work and keep on
Comment
-
Originally posted by Finless View Postvrailink, OK so this is a trade off. This file here is what I replaced to get more games working. However for gta3 I see in the debug it is one of the files that crashed. So I am providing the original and you can see if it fixes the game. Realize however it may break others! So what you want to do is this so you can switch back and forth if needed:
1) Download this file libc.so.zip. Unzip it and put it on your SDcard.
http://video.freaktab.com/?subpath=f...me=libc.so.zip
2) Get ES FIle explorer. In settings on ES file explorer setup like this
a) go into "file setting" and turn on show hidden files. Back up one level.
b) scroll down and turn on up to root.
c) Scroll down and turn on root explorer
d) below that turn on mount system as RW
3) On your sdcard rename libc.so to libc.new
4) Copy that into /system/lib
5) Do this step as quick as possible. Rename libc.so to libc.old and rename libc.new to libc.so
6) Hold you finger on the libc.so file and get the pop up. Scroll down and select properties
7) In properties click the change button to change permissions
8) Make sure all 9 boxes are checked!
6) Exit ES file explorer and reboot. See if you can power off rather than a reset.
See if this fixes gta3.
Bob
Comment
-
OK so maybe I changed too much? I did change quite a bit. Wish I knew which item fixed the battery icon and which causes the crashes
If one of you guys could pull logcat that would be great.
Bob"Pzebacz im, bo nie wiedzą, co czynią"
"Прости им, они не ведают, что творят"
"Perdona loro perché non sanno quello che fanno"
"Vergib ihnen, denn sie wissen nicht, was sie tun"
"Vergeef hen want ze weten niet wat ze doen"
"Pardonne-leur car ils ne savent pas ce qu'ils font"
"Perdónalos porque no saben que lo que hacen"
"Oprosti im, jer ne znaju što čine"
"Forgive them as they know not what they do"
Comment
-
Bob,
Logcat attached. Got some strange errors with the Gallery, etc after using the app injector. Hope this helps.
alogcat.2012-07-08-17-50-30+0100.txt
Wanted to add, battery working like a charm now...just some other funny things occuring, confirmed reboot on closing notifications (as others have outlined). So frustrated for you as we're nearly there with this, plus you're the first to get the battery sorted using a honeycomb interface!
Comment
-
bay, did you reboot after injecting apps? The error looks like the dalvic cache was not setup which it does after a reboot.
looking more at the logcat now.
Bob"Pzebacz im, bo nie wiedzą, co czynią"
"Прости им, они не ведают, что творят"
"Perdona loro perché non sanno quello che fanno"
"Vergib ihnen, denn sie wissen nicht, was sie tun"
"Vergeef hen want ze weten niet wat ze doen"
"Pardonne-leur car ils ne savent pas ce qu'ils font"
"Perdónalos porque no saben que lo que hacen"
"Oprosti im, jer ne znaju što čine"
"Forgive them as they know not what they do"
Comment
-
Also per your last post. You did reflash the entire ROM and erase IDB? You did not just flash system.img right? The dalvic cache looks messed up and it is asking for ODEX files that are no longer there
I need you guys to test from clean setups and this also means no titanium backup restores of "data". It's OK to restore APPS but DO NOT restore the "data" with the app or restore "system data" This is super important as I have changed the ROM a lot.
Bob"Pzebacz im, bo nie wiedzą, co czynią"
"Прости им, они не ведают, что творят"
"Perdona loro perché non sanno quello che fanno"
"Vergib ihnen, denn sie wissen nicht, was sie tun"
"Vergeef hen want ze weten niet wat ze doen"
"Pardonne-leur car ils ne savent pas ce qu'ils font"
"Perdónalos porque no saben que lo que hacen"
"Oprosti im, jer ne znaju što čine"
"Forgive them as they know not what they do"
Comment
-
Hey bob, maybe this can help: when going to the application menu and clicking on an app this just restarts the device. I have logcat included: logcat2.zip
Comment
-
Bob,
Yup, I rebooted after injection. Now getting some strange SU errors - which is a real pain. New logcat attached.alogcat.2012-07-08-18-10-21+0100.txt
Originally posted by Finless View Postbay, did you reboot after injecting apps? The error looks like the dalvic cache was not setup which it does after a reboot.
looking more at the logcat now.
Bob
Comment
-
Yes, I flashed the entire rom & erased IDB prior. Will do it again though from clean to check.
Originally posted by Finless View PostAlso per your last post. You did reflash the entire ROM and erase IDB? You did not just flash system.img right? The dalvic cache looks messed up and it is asking for ODEX files that are no longer there
I need you guys to test from clean setups and this also means no titanium backup restores of "data". It's OK to restore APPS but DO NOT restore the "data" with the app or restore "system data" This is super important as I have changed the ROM a lot.
Bob
Comment
-
The logcat has no debug info in it. I also see all kinds of APP calls that are not in the ROM e.g.
com.easy.battery.saver
I see super user calls, all kinds of stuff.
When testing low level stuff I need a clean system. Closing notifications on the status bar is so low level while I am trying to solve the battery indicator, having other apps installed causes a problem and pollutes the logcat.
To catch the status bar notification close error, please do this.
1) Have some notifications on the bar... e.g. like a gplay update or something to a stock APP.
2) OPen the terminal and clear the logcat
$ su
# logcat -c
3) Now do that action that causes the crash.
4) Now I know it is a reboot but pull the logcat file on next power up.
Lets get that fixed then I can look at picture gallery.
P.S. you SDcard looks corrupted! Please check it with windows:
http://www.freaktab.com/showthread.p...Understand-WHY!
Bob"Pzebacz im, bo nie wiedzą, co czynią"
"Прости им, они не ведают, что творят"
"Perdona loro perché non sanno quello che fanno"
"Vergib ihnen, denn sie wissen nicht, was sie tun"
"Vergeef hen want ze weten niet wat ze doen"
"Pardonne-leur car ils ne savent pas ce qu'ils font"
"Perdónalos porque no saben que lo que hacen"
"Oprosti im, jer ne znaju što čine"
"Forgive them as they know not what they do"
Comment
-
Reinstalling clean as I type this. Will get logcat of the error once its finished. Done a full IDB erase and re-flash. Sorry - had to re-install apps (missus wanted to play angry birds whilst we were out!)
Will check SD as well. It needs a cleanup
Originally posted by Finless View PostThe logcat has no debug info in it. I also see all kinds of APP calls that are not in the ROM e.g.
com.easy.battery.saver
I see super user calls, all kinds of stuff.
When testing low level stuff I need a clean system. Closing notifications on the status bar is so low level while I am trying to solve the battery indicator, having other apps installed causes a problem and pollutes the logcat.
To catch the status bar notification close error, please do this.
1) Have some notifications on the bar... e.g. like a gplay update or something to a stock APP.
2) OPen the terminal and clear the logcat
$ su
# logcat -c
3) Now do that action that causes the crash.
4) Now I know it is a reboot but pull the logcat file on next power up.
Lets get that fixed then I can look at picture gallery.
P.S. you SDcard looks corrupted! Please check it with windows:
http://www.freaktab.com/showthread.p...Understand-WHY!
Bob
Comment
-
here is a clean one if you wantdid logcat -c: logcat3.txt closed an update notification and I let the logcat run until reboot. Hope this helps
Comment
-
Ok, reinstalled fresh, erased IDB, etc. Not injected anything, not installed anything apart from alogcat. Logcat attached:
alogcat.2012-07-08-10-28-04-0700.txt
Comment
-
Thanks! I will look at it right now. However I can recreate the problem myself now. I flahsed the ROM using my kernel and tried to close a notification. It locked up for about 5 seconds then rebooted.
So I think I can troubleshoot this one.
Stay tuned.
Bob"Pzebacz im, bo nie wiedzą, co czynią"
"Прости им, они не ведают, что творят"
"Perdona loro perché non sanno quello che fanno"
"Vergib ihnen, denn sie wissen nicht, was sie tun"
"Vergeef hen want ze weten niet wat ze doen"
"Pardonne-leur car ils ne savent pas ce qu'ils font"
"Perdónalos porque no saben que lo que hacen"
"Oprosti im, jer ne znaju što čine"
"Forgive them as they know not what they do"
Comment
What's Going On
Collapse
There are currently 2674 users online. 0 members and 2674 guests.
Most users ever online was 63,956 at 18:56 on 20 March 2025.
Comment