• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root No sleep has nothing to do with anything

Sorry guys, but IMO the "location manager" is not the "never-sleep bug"..

I've solved all my problems deactivating autosync of Google apps (from power manager widget..)...it seems that from Donut firmware release (in JC6 I've seen the bug, but in Galaxo 1.6.3.1 there is :( ) the autosync NEVER sleeps...
now my Galaxy (with Galaxo 1.6.3.1) works 2-3 days always connected in 2G without recharging...

at the moment I'm thinking on how to hack the autosync option...
does anyone have an idea? are there some parameters to set in sources for autosync?

listen to me...try to deactivate autosync...then look if the "no-sleep bug" still persists....

byee!!
 
Upvote 0
Sorry guys, but IMO the "location manager" is not the "never-sleep bug"..

I've solved all my problems deactivating autosync of Google apps (from power manager widget..)...it seems that from Donut firmware release (in JC6 I've seen the bug, but in Galaxo 1.6.3.1 there is :( ) the autosync NEVER sleeps...
now my Galaxy (with Galaxo 1.6.3.1) works 2-3 days always connected in 2G without recharging...

at the moment I'm thinking on how to hack the autosync option...
does anyone have an idea? are there some parameters to set in sources for autosync?

listen to me...try to deactivate autosync...then look if the "no-sleep bug" still persists....

byee!!

And I solved all my problems by turning network location off. No no-sleep, and I have autosync on all the time. I also have GPS on all the time.

From what I learned, it is the network location. If you just turn it on, the phone will sleep just fine - until you trigger it (by using maps, for example, which will first try to get network location while trying to get satellite data). Network location service will never release the lock, and you won't see anything in logcat, because nothing is happening: noone is requesting anything from location service, it is not doing anything - excepting holding the lock until you reboot the phone. First use of location services after reboot => no sleep again.

I doesn't have to be google maps, it could be browser wanting to know your location, or this share-with-google thing, or some other app. However, I just tried this with maps.

I keep network location and share with google off. GPS works fine (if you have good sight of sats).
 
Upvote 0
Sorry guys, but IMO the "location manager" is not the "never-sleep bug"..

I've solved all my problems deactivating autosync of Google apps (from power manager widget..)...it seems that from Donut firmware release (in JC6 I've seen the bug, but in Galaxo 1.6.3.1 there is :( ) the autosync NEVER sleeps...
now my Galaxy (with Galaxo 1.6.3.1) works 2-3 days always connected in 2G without recharging...

at the moment I'm thinking on how to hack the autosync option...
does anyone have an idea? are there some parameters to set in sources for autosync?

listen to me...try to deactivate autosync...then look if the "no-sleep bug" still persists....

byee!!
no, you are wrong

disabling autosynch does fix issues with galaxo 1.6.3.1 in some aspects
ive never used autosynch or background data unless i use the market and have suffered no sleep regular after calls on jc2/jc4/jc6 and galaxo 1.6.3
had it twice on 1.6.3.1 but not as oftend so im not sure i can blame it on the same bug

some people have reported no nosleep issueson all firmwares but majority do get it. please dont type in bold like you are speaking from fact when you are not.

the majority of us here are very heavy testers and usually the 1st to find issues
 
Upvote 0
Wont install for me'

...
E:No Signature (143 files)
E:Verification failed
sync data...
.Installation failed
same

The same zip with meta-data to use with recovery:

MEGAUPLOAD - The leading online storage and file delivery service

Otherwise you can extract the zip, boot in recovery and then make:
- adb remount
- adb push system/framework /system/framework
- adb push system/app /system/app


did you actaully test this on galaxo 1.6.3.1?
i couldnt run it via recovery so i used to commands you mentioned and gues what?

it fked my phone [bricked}
restored nandroid backup, got it all back to how it was prior to doing it. made a backup. tried it again and yet again killed the phone

i dont think galaxo 1.6.3.1 likes this at all
 
Upvote 0
I did not test the galaxo install. I just signed the zip with the sign tool provided on galaxo site. Better see with the maintainer about that.

Concerning the "bricked" thing, it's not possible as you don't touch the kernel.
If you install (as described) and wipe, with a stock firmware, you should see the logo blinking for minutes, as it will rebuild all your apps.
 
Upvote 0
I did not test the galaxo install. I just signed the zip with the sign tool provided on galaxo site. Better see with the maintainer about that.

Concerning the "bricked" thing, it's not possible as you don't touch the kernel.
If you install (as described) and wipe, with a stock firmware, you should see the logo blinking for minutes, as it will rebuild all your apps.

not fully bricked but i had to reinstall.
its not just the signing mate, i applied all these through adb
surely you should test your stuff before you put it out?
jakax said:
It is compatible with Galaxo:
- All changes made in galaxo look to be in scripts, configuration or packaging
- All galaxo files have been resigned, so you should reset to defaults after applying the fix

if youve not tested it, how do you know its compatible?
 
Upvote 0
Because I don't think there are changes concerning these files (in app & system) compared to a stock firmware.
Maybe I'm wrong.

Can you confirm it was not regenerating your apps ?

yes it was in a hung state for 30 mins
i booted back to recovery. did a clean wipe then applies galax0 update then gapps, then i did the adb commands again and same again with a hung state.

after about 15 mins i decided to restore a nandroid backup i took 2 weeks ago and reinstall the 2 or 3 apps i had applied since that backup.

its a dangerous thing assuming something will work without testing it, then telling people it should be fine based on assumption and not experience.
 
Upvote 0
I just took another quick look at a galaxo zip, you should push system/app (in the zip) in /data/app_s
A clean up of /data/dalvik-cache would be good too... even if it should be rebuilt.

Mounting /data for read/write:
adb shell
mount /dev/block/mmcblk0p1 /data

... push the data ...

rm /data/dalvik-cache/* (optional)
sync
umount /data
 
Upvote 0
I just took another quick look at a galaxo zip, you should push system/app (in the zip) in /data/app_s
A clean up of /data/dalvik-cache would be good too... even if it should be rebuilt.

Mounting /data for read/write:
adb shell
mount /dev/block/mmcblk0p1 /data

... push the data ...

rm /data/dalvik-cache/* (optional)
sync
umount /data

im not going to test it, while i appreciate your findings i like to know things work before i apply them

system/app is the same as data/app_s afaik, change one and the other is updated.

I still got one question for Rastaman. Is there any other .odex in your app & framework directories that are not in the zip file
im not entirely sure, at a glance i wouldnt say so and in some cases there are no odex for some apps where there are in your zip file.
 
Upvote 0
Yes, he knows that for certain. Just look at the time this thread was started. 1.6.3. Galaxo with OC was nowhere near, just plain old JC6, JB2 etc. Original no-sleep was because of geolocation bug and that is fixed. There are other no-sleep bugs every now and then. I, for instance, have a ****ed up baseband which tends to stay awake after a phone call every now and then.
 
Upvote 0
There are other no-sleep bugs every now and then. I, for instance, have a ****ed up baseband which tends to stay awake after a phone call every now and then.

Sounds exactly the same as mine. There does appear to be a fix!

Quoting adie from drakaz' forum:
"Basing on my experience it happens most frequently if you disconnect or discard call using right button. It seems that it doesn't occur when you wait for other party to disconnect or use context menu. I made two attempts (incoming call discard) and I was able to reproduce it each time easily. I was using Galaxo 1.6.3.3. On the other hand now it never happens if I use location services."

So far it does seem to work, though not fully tested using the right end call button..
Use the menu button and end a call that way or turn on location services, which is the exact opposite for the fix for the original no sleep bug. :thinking:
 
Upvote 0
I'm on stock 1.6: XXJB2 smallband with JC2 build. I know there's Galaxo and GAOSP but I just like the stock ones better.*

When I apply the steps here (the downloadlink doesn't work anymore but I already downloaded the files some time ago) all goes well but I'm stuck on a boot loop when I reboot the phone. I'm on recovery 6.4 from drakaz. What am I doing wrong?

Any help would be appreciated.
 
Upvote 0
I'm not trying to install any Galaxo or GAOSP because I personally like the stock 1.6 best. On GAOSP my native language (Dutch) isn't supported and navigation doesn't work. GAOSP is really nice but I need the bluetooth functions too much.

So now I'm on I7500XENJE1 (JB2/JC2) which matches all my needs. Only problem is the no-sleep bug. Therefore i rooted the phone with recovery 6.4 from drakaz and I tried the patch which is described in this thread. All goes well except that when I reboot after pushing the system/app and system/framework the phone boot-loops. I made a Nandroid back-up so I can easily restore, but I'd like the phone to sleep more.

I'd really like to know what I'm doing wrong or if anyone has the correct files to fix the no-sleep bug on this rom.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones